Ultimate Amiga
Network Boards => AMOS Language Discussion => AMOS Factory => AMOS Professional Forum => Topic started by: Brick Nash on June 08, 2016, 06:14:33 PM
-
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!
-
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.
-
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! :)
-
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.
-
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.
-
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.
-
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! :)
-
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)
;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
-
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)
;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!
-
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
-
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 ;D )
-
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!
-
What are you using as your base workbench install?
I would recommend something like ClassicWB
... Can't remember the URL at the mo!
-
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!
-
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?)
-
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?)
Ahh sorry, It's running from my virtual hard drive on WinUAE.
-
Ok nearly there! Got all the Classic WB stuff downloaded and all going well but it says in the instructions to put an uncompressed 3.0 or 3.1 ROM into the new ROM folder and rename it kick3.ROM.
I'm not even sure what an uncompressed ROM file is so I just used one from my ROMs folder, duplicated it and renamed it then put it in the folder but the ROM doesn't work and either flashes up a flickery green screen or it looks for a replacement and the 'Eyes' boot screen comes up and just sits there. All the rest is in place and I have a WB 3.1 disk in the drive.
Sorry to keep coming back and asking all these questions, I really don't like doing it but the instructions on the web page didn't say where to get an uncompressed ROM file or even give a link. I tried a Google search but unsurprisingly it didn't turn up much.
-
Are you avaiable to join the chat room or something?
the kickstart roms are still 'copyright' so that's why the dont give you links.
I am surprised that Classic WB needs it though, as previously it just wanted a Workbench disk.
-
Make sure you're using a 3.1 kickstart rom if you're using WB3.1
-
Further investigation suggests you have used the ClassicWB.uae config within the download package?
I would ignore that, if you already had a working Workbench setup.
Here's a guide:
1) Create a New UAE Config
2) Pick Expanded A1200 setup
3) Give lots of fast memory or Z3 memory to it (a total of 32meg is good)
4) Check this works and load the "jumping disk" kickstart screen. If not, return to the emulator menu and manually select whatever Kickstart 3.1 rom you are using (although Kickstart 3.0 would also work fine)
5) under Hard drives, use ADD HARDFILE and select System.hdf as the first drive (DH0)
6) then add one more , with ADD FOLDER (wherever you like) as DH1 , with a label like "Storage" .... you could even make this your system Dropbox/Google Drive folder, so that you can share it across systems. (I do this regularly, plus it means my projects are constantly backed up)
6b) if you really want, add a third folder as a Harddrive for random stuff you download but are not precious about!
7) Unpack the previously provided AMOSPRO folder to your second 'drive' (folder) location, on your host machine (i don't know if you use windows or OSX tbh)
8 ) Boot your new setup, and fingers-crossed it will load fine.
On first load it might ask for a valid Workbench disk to be inserted for verification (it sounds like you probably have an ADF for this anyway) ... also if you have the full set of disks for Workbench 3.1, this allow you to get the most from the "install"
You might also get asked about a few other install questions... For now i would suggest the following selections:
iGame image pack: "REMOVE"
Colour Pallet: "Default 16"
Theme Option: "NONE"
Old Icons: "DISABLE"
Copper Background: "ENABLE"
StackAttack: "ENABLE"
AntiClick: "ENABLE"
FreeWheel: "ENABLE"
When it says it is done, remove the ADF and hit "reset"
9) When you make it to your new workbench setup, find your way to CLI prompt (There is one on the desktop called "SHELL")
check that AMOS Pro is where you think it is, with
CD DH1:
DIR
hopefully you'll see the AMOS_Pro Folder mentioned before
ED s:assign-startup
add the assigns to this, and then use Escape, then X to save and exit (i have changed the second line to fit this tutorial)
;BEGIN AMOS Professional
Assign AMOSPro: DH1: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
reset again, and then click on the DH1: drive, AMOS_Pro folder and try launching...
-
Further investigation suggests you have used the ClassicWB.uae config within the download package?
I would ignore that, if you already had a working Workbench setup.
Here's a guide:
1) Create a New UAE Config
2) Pick Expanded A1200 setup
3) Give lots of fast memory or Z3 memory to it (a total of 32meg is good)
4) Check this works and load the "jumping disk" kickstart screen. If not, return to the emulator menu and manually select whatever Kickstart 3.1 rom you are using (although Kickstart 3.0 would also work fine)
5) under Hard drives, use ADD HARDFILE and select System.hdf as the first drive (DH0)
6) then add one more , with ADD FOLDER (wherever you like) as DH1 , with a label like "Storage" .... you could even make this your system Dropbox/Google Drive folder, so that you can share it across systems. (I do this regularly, plus it means my projects are constantly backed up)
6b) if you really want, add a third folder as a Harddrive for random stuff you download but are not precious about!
7) Unpack the previously provided AMOSPRO folder to your second 'drive' (folder) location, on your host machine (i don't know if you use windows or OSX tbh)
8 ) Boot your new setup, and fingers-crossed it will load fine.
On first load it might ask for a valid Workbench disk to be inserted for verification (it sounds like you probably have an ADF for this anyway) ... also if you have the full set of disks for Workbench 3.1, this allow you to get the most from the "install"
You might also get asked about a few other install questions... For now i would suggest the following selections:
iGame image pack: "REMOVE"
Colour Pallet: "Default 16"
Theme Option: "NONE"
Old Icons: "DISABLE"
Copper Background: "ENABLE"
StackAttack: "ENABLE"
AntiClick: "ENABLE"
FreeWheel: "ENABLE"
When it says it is done, remove the ADF and hit "reset"
9) When you make it to your new workbench setup, find your way to CLI prompt (There is one on the desktop called "SHELL")
check that AMOS Pro is where you think it is, with
CD DH1:
DIR
hopefully you'll see the AMOS_Pro Folder mentioned before
ED s:assign-startup
add the assigns to this, and then use Escape, then X to save and exit (i have changed the second line to fit this tutorial)
;BEGIN AMOS Professional
Assign AMOSPro: DH1: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
reset again, and then click on the DH1: drive, AMOS_Pro folder and try launching...
I got as far as removing the ADF and resetting but I just get a black screen. I left if for a few minutes to make sure but it just stays that way.
Everything installed fine and I had no errors at all so I don't know what could have happened. I did use the System.hdf from the FULL setup folder, maybe I should have used the UAE one instead? :S
I'll try again tomorrow, maybe it's something daft I haven't set yet.
Just want to say thanks for all the help so far. You've really gone out your way and I appreciate it!
EDIT: I got the WB running but I get a Copper error message on startup #80000008 Wait for disk activity to finish. If I try to reboot it comes up with a software error message but I if chose suspend I can navigate around ok.
As I say I'll pick this up tomorrow, tis bed time! :)
-
so the Classic WB install process worked ok? You clicked through the questions?
You still havent said if you are using Windows/OSX, WinUAE / FS-UAE etc....
that might help, as it sounds a lot like the issues are with the UAE setup you are using.
There should be no problem using the FULL ClassicWB HDF...
I forgot to say, you should of course keep saving the UAE config after making changes to the Harddrive setup / memory etc.
-
so the Classic WB install process worked ok? You clicked through the questions?
You still havent said if you are using Windows/OSX, WinUAE / FS-UAE etc....
that might help, as it sounds a lot like the issues are with the UAE setup you are using.
There should be no problem using the FULL ClassicWB HDF...
I forgot to say, you should of course keep saving the UAE config after making changes to the Harddrive setup / memory etc.
Yes it seems to have worked, I went through the questions as instructed. I'm not had a good look about yet and I'm about to get tore into it but bar that copper error on startup everything seems to be ok.
Sorry I forgot to mention I'm using a Windows 7 system.
EDIT: Ok hit a snag already, the AMOSPRO folder isn't showing up. In Part 7. of your instructions I wasn't quite sure what you meant by 'unpack' as in unzip in windows? I unzipped the file and placed in in the same folder in windows as the .hdf file. I don't know the way to actually add it to the .hdf file within a windows environment itself.
EDIT EDIT: Ok I've been at this all morning and still no joy. I added a new directory which was the Windows folder that contained the AMOS_Pro folder and I just copied it all over to a WB Drawer within the hard drive. I set the assigns in the assign-setup and made sure they pointed to the correct place but if I try to run AMOS Pro it says it can't find the interpreter_config file, but it's there...I can see it in the folder next to the AMOS_Pro launcher.
EDIT EDIT EDIT: I've actually managed to get everything running on my old WB setup as the saved assigns from the new one are being recognised but the extensions don't seem to be loaded into Amos. All the .lib files are there and the assigns are definitely pointing to the right places.
Do I need to actually go into the interpreter config within Amos and set the extensions in their slots manually? I would try to do this but I was under the impression that each extension needed a specific slot number.
Was it always this tricky back in the day? :P
-
yes, your old setup would need the interpretter config changed manually.
if you wanted to add the extensions (notably AMCAF) the slots you would need are listed here:
http://www.ultimateamiga.co.uk/index.php/topic,9066.msg40853.html#msg40853
However, in the classicWB setup, can you post some screenshots after running a few commands?
- ED s:assign-startup
- DIR dh1:
- DIR dh1:AMOS_Pro
it sounds like the assigns are wrong given this comment
"I just copied it all over to a WB Drawer within the hard drive."
-
yes, your old setup would need the interpretter config changed manually.
if you wanted to add the extensions (notably AMCAF) the slots you would need are listed here:
http://www.ultimateamiga.co.uk/index.php/topic,9066.msg40853.html#msg40853
However, in the classicWB setup, can you post some screenshots after running a few commands?
- ED s:assign-startup
- DIR dh1:
- DIR dh1:AMOS_Pro
it sounds like the assigns are wrong given this comment
"I just copied it all over to a WB Drawer within the hard drive."
Well my way didn't work. I loaded the extensions in manually then rebooted but I get a disk read error #80000004 when I try to launch Amos Pro. :(
Here are my assigns. I put the same ones in the user-startup file of the old setup too. The Stuff:AMOS_pro is just where I keep the drawer with all the Amos pro files in it. It's where I copied all the other files like the libs and stuff too. Al the extensions .libs are in the correct folder, I manually checked it on both setups.
(http://i75.photobucket.com/albums/i295/Krenzathal/assign-startup_zpslcxmspbv.png)
-
you are missing a space in the first AMOS Pro assign line, and it has a colon on the end that should be removed.
Assign AMOSPro: Stuff:AMOS_Pro: >nil:
^^ this first line is critical and would explain why AMOS cannot find the interpretter config
Second line has an underscore (the second one) that shouldnt be there also
-
you are missing a space in the first AMOS Pro assign line, and it has a colon on the end that should be removed.
Assign AMOSPro: Stuff:AMOS_Pro: >nil:
^^ this first line is critical and would explain why AMOS cannot find the interpreter config
Second line has an underscore (the second one) that shouldn't be there also
Still getting the same results on both setups unfortunately. The old WB setup is still giving a Program failed (#80000004) error and the Classic WB setup still can't find the Interpreter Config.
On both setups it keeps asking me to insert volume AMOSPro on boot up so I guess I've made a mess of things somehow. :(
EDIT: Yep it seems to be the part I've highlighted in italics for each case that it can't find - Assign AMOSPro_System: AMOSPro: >nil:
-
That tells you that the AMOSPro: assign is not correct.
... this si the first line, that i mentioned was missing a space etc.
can you please type into CLI .... DIR Stuff:
and send a screenshot, along with an updated one for ED S:assign-startup
-
(http://i75.photobucket.com/albums/i295/Krenzathal/Stuff_zpsstygddkw.png)
(http://i75.photobucket.com/albums/i295/Krenzathal/assign-startup_zpspjz7iwwf.png)
BTW, thanks again. I know this must be a pain in the arse!
-
you say "on boot" ... do you mean on laoding amos, or on loading Workbench?
Can you give me the result of
DIR AMOSPro:
thanks
-
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.
-
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")
-
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 -
(http://i75.photobucket.com/albums/i295/Krenzathal/assign-startup_zpsnrk6tsf1.png)
-
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? ;)
-
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?
(http://i75.photobucket.com/albums/i295/Krenzathal/assign-startup_zps1rln16ik.png)
-
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.
-
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! :)
-
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 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. :(
-
looks like it uploaded as 0kb .... have tried again
-
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.
-
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.
-
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...
https://drive.google.com/open?id=0B4272ME-kTRMZFNKUmhrVkQzX2s
https://drive.google.com/open?id=0B4272ME-kTRMckR2eDBRZXR0LVk
-
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. :)
-
sorry to hear that news :(
Hope you are keeping OK.