it said it wanted to do a 502 to 503 upgrade
I let it
it also wanted to copy the puppy.sfs over to the same location as the savefile and I said yes.
let it start up and was ok.
stopped my testing process here.
I wanted to find where the new puppy file was being placed
![Question :?:](./images/smilies/icon_question.gif)
Eventually found it. What it is doing is creating a new zxxxxxxx directory for 503, copying the 503's zdrv.sfs AND puppy.sfs here **NOT** as it says it's doing (copying to the same location as the savefile).
copied manually to the correct place and rebooted
everything came up ok on reboot.
so that is the problem
![Exclamation :!:](./images/smilies/icon_exclaim.gif)
shutdown for now.
Will go back to my testing processes later today, update this message if necessary.
regards
scsijon
ps zdrv hash is correct.
pps @BarryK for his pc problem, from a vague past memory, doesn't the default setting for memtest actually start testing at either 256K or 640K and work upwards, I seem to remember that you need to tell it to actually test below that, and different again for the bottom ram blocks, and this had to be done from a floppy start, it couldn't do these low areas from a hd start. Another thing to check is if the two "directories" on the hd have the same info, I do remember having a 214 install giving random problems when the second directory was out of sync to the first as linux will use the second copy in r/o mode if the first copy is "in use".