#Amiga Workbench 3.1 Hdf install#
It would be easier to fix if it was all.) Also, you need to check for files that OS 3.1.4 might install that OS 3.1 didn't. (I'm not sure if ClassicWB strips out ALL the Commodore files, or just some/most. You also might have to copy extra files if ClassicWB leaves some 3.1 files in it's archive. You'd have to make sure that you tweak the script to get the right files from the right disks. IF they are actually fairly similar, then a change to the current ClassicWB install script might still work. I'm also thinking that what someone would need to do is create a clean OS 3.1 and also a clean OS 3.1.4 and do a DIFF to see what is different (filenames/versions, paths, assigns, etc). (I've already tweaked the install script to just accept the new disk names in place of the 3.1 and that doesn't work.) They are different enough that I am sure a "simple" install script change won't work.
You will need to understand the differences.
#Amiga Workbench 3.1 Hdf how to#
I think the issues hinge on the changes between the OS 3.1 and 3.1.4 installs. The Green Amiga Alien guide on how to set up a hard disk in WinUAE with Workbench 1.3, Workbench 2.x, Workbench 3.1 with all the enhancements/add-ons (Picasso96, MagicWB/New Icons, Scalos, whdload etc. I keep trying to come up with a "simpler" solution, but I'm not coming up with one. Now, the resulting HDF with it's aborted install did seem to reboot and go to a WB, but I am sure it is a VERY SAD mixed up 3.0/3.1.4/broken stuff mess and wouldn't be happy long term. It did continue until I got to the Install3.1.4 disk, which it didn't like (looking for BRU, not a disk name this time). Not finding files it was looking for on disks. I did get pretty far, but I could see errors. OK, just for fun I tried editing the scripts just to allow me to use the 3.1.4 disk images. Files might be gone and/or moved to other disks.
I am guessing someone would have to look at everything that install script is doing. We could edit that script (which I started to do) to add the ".4" to the names.īut I am also seeing some errors in it not finding files it is looking for, so that probably means there isn't a super simple (just edit to add some. Create a Single Partition Hard Disk File, called LXF.hdf and it will be 256MB in size.Initial look at a Classic WB startup-sequence shows that it is looking for disks named "Workbench 3.1" and the new OS disks are named "Workbench 3.1.4" so. Click on the Amiga logo in the top left of the window and select HDF Creator.Ģ. For our virtual Amiga 1200, we are going to install a 256MB hard drive using FS-UAE.ġ. With the release of the 6 we saw built-in IDE interfaces and 600HD and 1200HD models were on the shelves, offering a whopping 40MB IDE hard drive. Install Workbench to a Virtual Hard DriveĪ hard drive was a luxury for the earlier Amigas. Change fonts, set the screen resolution, change input settings and set system sounds. Prefs is where we can configure the Amiga. Inside the Workbench 3.1 disk there are a number of folders. Workbench 3.1 as used on the A1200 and A4000 was a big deal. Don’t get us wrong, Workbench 1.3 was what we used with our Amiga 500, but it felt rather childish when compared to later releases. Workbench 2 onwards was where the Amiga Workbench saw the biggest shift from being just an operating system, into a powerful and efficient design. Windows, Icons, Menu and Pointer, and it has a shell interface that feels at home for Unix / Linux users. It features all of the design stylings that we are familiar with. The Amiga operating system is called Workbench and it is a GUI similar to Apple’s operating systems of the era. Click Start to power on and boot the Amiga. Insert the emulated Workbench 3.1 ADF disk image via Floppy Drives. On the main Launcher screen, under Amiga Model select A1200 and 3.0 CPU.Ħ.