Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Brick Nash]

I was attempting to install the AMCAF extension and it went fine until it asked for a help file I couldn't find.

Now I can't launch Amos, it comes up with an error message saying "Can't Load extension: Use default interpreter Config."

I did a quick hunt about and came across another thread on this forum in which SamuraiCrow says it's the installer script which is broke and to install it manually, but I don't know how to do that.

Thanks!

[Lonewolf10]

A trick I learnt from someone was to compile the AMOS Interpreter program, that way problems like that can be fixed without reinstalling AMOS or having loads of AMOS config files in the S drawer

Installing extensions is easy (ish), use the attached file and do the following:

 - make sure the extension (e.g. AMOSPro_AMCAF.Lib) has been copied into the APSystem drawer (found in the AMOSPro drawer)
 - remove the ".txt" from the end of the name of the attached program, it's actually an executable!
 - run the attached program
 - select "load other configuration" and then find the file "AMOSPro_Interpreter_Config" in the "S" drawer (usually within the AMOSPro drawer itself, or possibly within the System drawer depending on your setup)
 - select the extensions option (I forget the precise phrase)
 - select slot 8 and check the filename matches the extension file name (e.g. AMOSPro_AMCAF.Lib) exactly
 - click the top-left option (should close the current window and return to main menu)
 - now click "Save Configuration"
 - a confirmation message should come up about exiting AMOS for the new extension to work. Ignore it! The program is normally run within AMOS, not on it's own
 - click top-left option (Quit?) to exit the interpreter setup program
 - if everything was done correctly (and your version of the extension is not corrupt or hacked in any way) then AMOS Pro should work now.

[Brick Nash]

Thanks for the reply.

I ended up just re-installing to get things back to normal but I did try your method as it seemed the same as the one I used to install TOME4 but when I tried to load up Amos again I got the same error message.

Not sure what's wrong but it seems AMCAF doesn't like me!

[Xertese]

Thanks for the reply.

I ended up just re-installing to get things back to normal but I did try your method as it seemed the same as the one I used to install TOME4 but when I tried to load up Amos again I got the same error message.

Not sure what's wrong but it seems AMCAF doesn't like me!

AMCAF kinda sucks and i have been following you and i am not sure you need it.
Causes more problems than it solves especially at compile time.

[Hungry Horace]

AMCAF kinda sucks and i have been following you and i am not sure you need it.
Causes more problems than it solves especially at compile time.

Sensing quite a bit of negativity here Xertese?

What problems have you had?

AMCAF has lots of great extra functions and a lot of replacements which are faster than the AMOS originals. It's worth doing the manual install which should resolve these issues.

Brick Nash - are you using an emulated setup via a hard-drive folder?  If so, i would happily share my pre-installed folder for you.

[Xertese]

Sensing quite a bit of negativity here Xertese?
What problems have you had?
AMCAF has lots of great extra functions and a lot of replacements which are faster than the AMOS originals. It's worth doing the manual install which should resolve these issues.

I take on board what you have said but respectfully disagree.
Maybe it's just the way i have things setup which is why i experience difficulty using AMCAF at compile time or it could just be the compiler itself.
I agree AMCAF has some useful functions and if you're happy not compiling then yeah sure and if you manage to get an Amos prog to compile with AMCAF instructions you're a better coder than me.

[Brick Nash]

AMCAF kinda sucks and i have been following you and i am not sure you need it.
Causes more problems than it solves especially at compile time.

Sensing quite a bit of negativity here Xertese?

What problems have you had?

AMCAF has lots of great extra functions and a lot of replacements which are faster than the AMOS originals. It's worth doing the manual install which should resolve these issues.

Brick Nash - are you using an emulated setup via a hard-drive folder?  If so, i would happily share my pre-installed folder for you.

Yes I'm using WinUAE which boots straight to workbench via an emulated hard drive folder. I'm certainly interested in AMCAF as anything that speeds things up would be cool as it seems to be the main issue in Amos and certainly I've found a speed drop with any more than one bob on the screen but of course my code is horribly inefficient right now as I'm just focusing on getting things working rather than working well. I would highly appreciate you sharing your folder with me as I'd at least like to try it out!

[Hungry Horace]

Historically, there have been some problems with people getting AMOS / Extensions installed via Hard drive, as the in-built installer doesnt seem to work vey well with modern or emulated setups.

I have always installed everything 'manually' and now just regularly 'clone' that setup!

This is my main Amos Pro folder, you are all welcome to download:

https://drive.google.com/file/d/0B4272ME-kTRMQ2YwSmhhT3o1X1U/view?usp=sharing

I have these extensions installed:

Music Extension V2.00
Picture Compactor V2.00
Requestor V2.00
Compiler Extension V2.00
IO Devices Extension V2.00
Tome V2.24+
AMCAF V1.50beta4
Club Extension V2.9+
Ercole V1.7
Turbo Plus V2.15
Power Bobs V1.1
PlaySID Library Wrapper V1.01


To make it work, you do need to set up the various ASSIGNS to wherever you place the final folder.  You can put these in the  S:USER-STARTUP script or S:ASSIGN-STARTUP (if you happen to have this)

Code: [Select]

;BEGIN AMOS Professional
Assign AMOSPro: System:Programs/AMOS/AMOS_Pro/ >nil:
Assign AMOSPro_System: AMOSPro: >nil:
Assign AMOSPro_Accessories: AMOSPro:Accessories >nil:
Assign AMOSPro_Tutorial: AMOSPro:Tutorial >nil:
Assign AMOSPro_Examples: AMOSPro:Examples >nil:
Assign AMOSPro_Productivity1: AMOSPro:Productivity1 >nil:
Assign AMOSPro_Productivity2: AMOSPro:Productivity2 >nil:
Assign AMOSPro_Compiler: AMOSPro:Compiler >nil:
Assign AMOSPro_Extras: AMOSPro:Extras >nil
;END AMOS Professional

[Brick Nash]

Historically, there have been some problems with people getting AMOS / Extensions installed via Hard drive, as the in-built installer doesnt seem to work vey well with modern or emulated setups.

I have always installed everything 'manually' and now just regularly 'clone' that setup!

This is my main Amos Pro folder, you are all welcome to download:

https://drive.google.com/file/d/0B4272ME-kTRMQ2YwSmhhT3o1X1U/view?usp=sharing

I have these extensions installed:

Music Extension V2.00
Picture Compactor V2.00
Requestor V2.00
Compiler Extension V2.00
IO Devices Extension V2.00
Tome V2.24+
AMCAF V1.50beta4
Club Extension V2.9+
Ercole V1.7
Turbo Plus V2.15
Power Bobs V1.1
PlaySID Library Wrapper V1.01


To make it work, you do need to set up the various ASSIGNS to wherever you place the final folder.  You can put these in the  S:USER-STARTUP script or S:ASSIGN-STARTUP (if you happen to have this)

Code: [Select]

;BEGIN AMOS Professional
Assign AMOSPro: System:Programs/AMOS/AMOS_Pro/ >nil:
Assign AMOSPro_System: AMOSPro: >nil:
Assign AMOSPro_Accessories: AMOSPro:Accessories >nil:
Assign AMOSPro_Tutorial: AMOSPro:Tutorial >nil:
Assign AMOSPro_Examples: AMOSPro:Examples >nil:
Assign AMOSPro_Productivity1: AMOSPro:Productivity1 >nil:
Assign AMOSPro_Productivity2: AMOSPro:Productivity2 >nil:
Assign AMOSPro_Compiler: AMOSPro:Compiler >nil:
Assign AMOSPro_Extras: AMOSPro:Extras >nil
;END AMOS Professional

Thank you, that's very generous and helpful of you. There's quite a few here which I planned on getting anyway so this is great!

[bruceuncle]

Note that the AMOSPro executable attempts to do these assignments every time AMOS is started.  It checks whether the AMOSPro: assign exists and bases the others on the default directory structure.  It fails them silently if there's any problem.  So all you need is the single assignment for AMOSPro:, but it must be present in the interpreter config file - a script file with just that assign won't work.
The AMOS Pro installer 'magics' a program called something like 'Find AMOS' (not at my PC, but the name and icon are pretty obvious in the same directory as AMOSPro) which puts the appropriate entry into the interpreter configuration file.  Then you don't need any script file.  I don't know where that little program comes from as it's not obvious on any of the installation disks.  I assume it's probably unpacked from some data file during the install.
I'll post a copy when I'm back at my PC. 
If you haven't used the AMOS Pro install, just plonk it in the same directory as the AMOSPrp executable and launch the icon.
Sent from my Lumia 640 using Tapatalk

[bruceuncle]

The AMOS Pro installer 'magics' a program called something like 'Find AMOS' (not at my PC, but the name and icon are pretty obvious in the same directory as AMOSPro) which puts the appropriate entry into the interpreter configuration file.
If you haven't used the AMOS Pro install, just plonk it in the same directory as the AMOSPro executable and launch the icon.

Oh well, I got both the file name and the directory wrong! 

The file is  Locate_APSystem and the correct directory is /APSystem.  I've attached a zip of the program and its icon.  Put it in your /APSystem directory and launch it in Workbench.  It tells you what it's doing and puts the appropriate path in the interepreter config file.  AMOS Pro will then make all the necessary assigns each time it starts up with no need for script files.  The expected directory structure is the one the AMOS Pro installer creates.  So if, for example, AMOS is installed in a directory named "AMOS_Pro", the directory structure would look like this:

     /AMOS_Pro
          /Accessories
          /APSystem     <-- Put Locate_APSystem here
          /Compiler
          /Examples
          /Extras
          /Productivity1
          /Productivity2
          /Tutorial

The assigned names are identical to the install disk volume names.  So AMOS Pro could run from floppy drives as well as an HDD install (but it would be painfully slow for anyone not used to waiting for floppy drives and disk swapping  )

[Brick Nash]

Hey folks sorry for replying so late, I've only just got around to trying to install these extensions.

I'm having an old issue though in that I just cannot edit any kind of startup file in workbench. Using 'Ed' with the user-startup or any file always without fail brings up a yellow Recoverable Error message and It leaves me sort of stuck at a brick wall now. I tried typing in 'Edit' with the filename instead but that just seemed to bring up a blank text editor with nothing in it.

All these problems and bugs are starting to kill my creative drive a little but I'm absolutely determined to keep going!

[Hungry Horace]

What are you using as your base workbench install?

I would recommend something like ClassicWB

... Can't remember the URL at the mo!

[Brick Nash]

What are you using as your base workbench install?

I would recommend something like ClassicWB

... Can't remember the URL at the mo!

The 'About' section in the drop down lists the WB as version 40.42 and the Kickstart as 37.175. It's my own fault for not sorting this sooner, as I say I had this issue before but didn't take the time to fix it.

Once again thanks for the help. I feel like a bit of a nuisance but I'm eager to get this working!

[Hungry Horace]

I kind of meant, did you install it yourself from ADFs or is it running from disk etc.

this is the website with pre-installed workbench setups:

http://classicwb.abime.net/

I find the "FULL" package to be adequate for AMOS.

Then you can use the ZIP setup I linked above, and the ED command should work to add the necessary assigns. (Although keep in mind, you could do this directly on Windows/OSX if you are using a UAE setup?)