Upgrade a 3.1.1 VM to 3.2
 

Hi all,


I'm trying to upgrade to AmigaOS 3.2 in an emulated A1200 in Amiga Forever. I have plenty of space on the SYS: volume, labeled Workbench3.2: (it's a 1GB hdf with only the OS installed). I have the contents of the CD on a read-only virtual hard drive.


I double-click the AmigaOS3.2CD:Install/Start Here icon, then launch the installer from the Install3.2: volume it creates. Go through the options, it gets to its first step (copying icon.library) then it throws up a requester saying "Volume Workbench3.2 is write protected". Retry doesn't work.


Information... on the Workbench3.2: volume says it is Read/Write. list says everything in it has rw-d or rwed flags. Amiga Forever says it is read/write. I can write files in memacs and save them to the volume, and then delete them from the CLI. Only the installer thinks it's read only.


Anyone encountered this and got a workaround? Thank yoU!

That's a bad name because it is also the name of one of the installation floppy disks.

You should name your boot partition System3.2 or WB3.2 or Workbench32 or so. But not Workbench3.2.

Thanks Thomas :guru I made that change and indeed it works.

Glad you got it sorted :great
I know 3.2 is supposed to work with the 3.1.4 Rom (or even the 3.1 Rom)
So what are you doing with the ROM?, just using 3.1?
Or you hacking it in some way (please explain how) to get a full 3.2 install in AF?

Cheers

I’m using the 3.1 rom. I copied the 3.2 one from the CD into place but haven’t yet worked out how to configure AF to use it.

I believe the docs tell you how. I'm actually going to work on that tonight but you more than likely have to use a CD install for it work - the CD install uses virtual disks and loads everything for you - hopefully it will be a straight forward install.

3.2 install work great. The only issue is that now I have a 3.1 ROM that is actually a
3.2 ROM. So if you don't want to mess up your ROMs don't do this and/or save off your ROMs first.

Ahhh. so you had to do as suggested in this thread http://eab.abime.net/showthread.php?t=107002
and rename your 3.2 ROM?
Oh well... as I said in the other thread, prob easier to just build my 3.2 Env in WinUAE (which is what I have done, wont bother with AF).

Actually ... No.

3.2 overwrote the ROM itself. I saved the ROM directory off before I did
the update so I had 3.1 preserved but I would have to switch back and
forth if I wanted or want to use 3.1 v 3.2 - so your solution with WinUAE
is the better option.