Print

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

[Brick Nash]

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.

[Brick Nash]

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.

[Hungry Horace]

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.

[Xertese]

Make sure you're using a 3.1 kickstart rom if you're using WB3.1

[Hungry Horace]

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...

[Brick Nash]

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!

[Hungry Horace]

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.

[Brick Nash]

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? 

[Hungry Horace]

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."

[Brick Nash]

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.

[Hungry Horace]

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

[Brick Nash]

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:

[Hungry Horace]

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

[Brick Nash]

BTW, thanks again. I know this must be a pain in the arse!

[Hungry Horace]

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


Can you give me the result of

DIR AMOSPro:

thanks