Can't launch Amos/AMCAF Extension fault

[Brick Nash]

you say "on boot" ... do you mean on laoding amos, or on loading Workbench?


Can you give me the result of

DIR AMOSPro:

thanks

When Workbench starts up.

I tried the DIR AMOSPro: but it then asks to insert volume AMOSPro (just like on WB startup) and then when I push cancel it says " Could not get information for AMOSPro. Device (Or volume) is not mounted!" in the Shell.

I didn't think a screenshot was necessary for that.

[Hungry Horace]

right, so either the assign-startup is not running, or you need to re-type the line:

Assign AMOSPro:  Stuff:AMOS_Pro  >nil:

you could try removing the >nil:  at end, and then it should tell you about any problems on startup


EDIT: Scrap that. i can see the fault from your last screenshot, you didn't remove the colon at the end, that i mentioned  (it is at the end of  "Stuff:AMOS_Pro")

[Brick Nash]

right, so either the assign-startup is not running, or you need to re-type the line:

Assign AMOSPro:  Stuff:AMOS_Pro  >nil:

you could try removing the >nil:  at end, and then it should tell you about any problems on startup


EDIT: Scrap that. i can see the fault from your last screenshot, you didn't remove the colon at the end, that i mentioned  (it is at the end of  "Stuff:AMOS_Pro")

Still getting exactly the same result on both counts unfortunately. I must've done something wrong when setting it all up but it's definitely all there in the folder.

I tried removing the >nil but absolutely nothing changed and no new information was given.

Here's my latest assign -

[Hungry Horace]

Dir  amopro: should now work


In the second line you are missing a colon before the space before >nil:
You did have this in a previous screenshot


ASSIGN AMOSPro_System: AMOSPro:

You understand what Assign does, right, and why the syntax is really important?

[Brick Nash]

Dir  amopro: should now work


In the second line you are missing a colon before the space before >nil:
You did have this in a previous screenshot


ASSIGN AMOSPro_System: AMOSPro:

You understand what Assign does, right, and why the syntax is really important?

Of course, it's like a path or pointer. It's just silly mistakes I'm making, my dyslexia makes my brain skip over written text sometimes, almost like a blind spot. It's a pain, manuals & textbooks are torture but coding actually helps a lot!

Ok I solved the launch problem. I was looking at the interpreter config.AMOS file and not the AMOSPro_Interpreter_Config file which was missing. I checked the original folder but I couldn't find the file there so I copied one from a floppy image and it allows me to launch Amos now but in the Classic WB setup The Interpreter config within Amos won't allow me to load a default configuration due to a disk error it says but in my old setup it launches fine and all the new extensions are still in their slots but it says on startup that only 4 extensions have been loaded.

The Amiga really makes you work doesn't it?

[SamuraiCrow]

The Amiga really makes you work doesn't it?

Yes and no.  Remember that Amos started as a port from the AtariST so it has a crazy amount of work that wouldn't have been necessary if it had been started on the Amiga directly and used Amiga libraries.  Also, it is backward compatible to Workbench 1.3 which is not very fully developed compared to the later versions.

[Brick Nash]

The Amiga really makes you work doesn't it?

Yes and no.  Remember that Amos started as a port from the AtariST so it has a crazy amount of work that wouldn't have been necessary if it had been started on the Amiga directly and used Amiga libraries.  Also, it is backward compatible to Workbench 1.3 which is not very fully developed compared to the later versions.

Oh I wasn't having a go, it was just a joke as to the hard time I'm having right now getting this to work. Amos is great, I'm actually very surprised at how nice a package it is for 1992 despite it's few bugs. I'll always love the Amiga and of course the community which has been a help that is more than words can describe. If I could buy people beers over the internet I would!

[Hungry Horace]

The file doesnt live in the AMOS_Pro folder it seems....


1) unpack the attached ZIP file in your Stuff: drive
2) open CLI and type *exactly* the following:

copy stuff:AMOSPro#?Config S:




Hopefully this should fix any problems on the ClassicWB setup

[Brick Nash]

The file doesnt live in the AMOS_Pro folder it seems....


1) unpack the attached ZIP file in your Stuff: drive
2) open CLI and type *exactly* the following:

copy stuff:AMOSPro#?Config S:




Hopefully this should fix any problems on the ClassicWB setup

The file appears to be corrupted. Tried downloading it a few times.

[Hungry Horace]

looks like it uploaded as 0kb .... have tried again

[Brick Nash]

looks like it uploaded as 0kb .... have tried again

Thanks for the re-upload, that sorted any launch problems on the Classic WB nicely. The extensions still don't appear to be installing though. They are in their slots on both setups and I'm sure all the assigns are correct but it's only saying there are 4 on Amos launch and it's still saying the extension is missing when I try to run your tutorial.

[Hungry Horace]

you are going to have to share your HDF and Stuff files with me on Google Drive or something.

I did invite you to share a folder using the email address you have on here, so hopefully you already have my address, otherwise i will PM you it.

[Hungry Horace]

I have literally just done the following:

- Mounted and installed Classic WB full HDF
- set up my own STUFF: drive as DH1:
- unpacked the AMOSPro folder from my link above
- Added the assigns to S:Assign-Startup
- copied the interpretter config files to S:

... Alll worked fine , with 12 extensions loaded.... really cant work out why your setup isnt working.


Here are new links to the SYSTEM.HDF and STUFF folder I used...

<removed>

[Brick Nash]

Hi, many apologies for the late reply. I unfortunately had a bereavement in the family over the weekend so things have been up in the air.

I've added that shared folder to my google drive I've uploaded my .hdf file to it. it's called "hdd1.hdf". I'll have a look at the other stuff when I get home.

Once again many thanks for all the help and apologies for the rather quick in and out nature of this message but I just wanted to inform that I wasn't ignoring anyone.

[Hungry Horace]

sorry to hear that news 

Hope you are keeping OK.