English Amiga Board - View Single Post

desiv · 06 October 2018, 20:15

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...
We could edit that script (which I started to do) to add the ".4" to the names.
That does get it farther along.
But 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 .4's or rename your disks) solution. ;-(
I am guessing someone would have to look at everything that install script is doing. Files might be gone and/or moved to other disks.

Hmmm..

OK, just for fun I tried editing the scripts just to allow me to use the 3.1.4 disk images..
er...
Not what I'd call a success..
I did get pretty far, but I could see errors. Not finding files it was looking for on disks...
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).

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.

06 October 2018, 20:15	#3
desiv Registered User Join Date: Oct 2009 Location: Salem, OR Posts: 1,767	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... We could edit that script (which I started to do) to add the ".4" to the names. That does get it farther along. But 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 .4's or rename your disks) solution. ;-( I am guessing someone would have to look at everything that install script is doing. Files might be gone and/or moved to other disks. Hmmm.. OK, just for fun I tried editing the scripts just to allow me to use the 3.1.4 disk images.. er... Not what I'd call a success.. I did get pretty far, but I could see errors. Not finding files it was looking for on disks... 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). 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. Last edited by desiv; 06 October 2018 at 21:14.