Those Roms are encrypted and can not be used right away. This is indicated by the ROM.KEY in that directory and the roms also are too big, 524.288Bytes is the correct size.

You can a) install AF to a computer, your decrypted roms should be in a directory like C:\Users\Public\Documents\Amiga Files\Shared\rom or b) use https://github.com/abcbarryn/decrypt-amigaforever but you have to compile it yourself

I have since tried again with uploading a new HDF file and this worked so thanks very much.

However this is not the end of the challenge. Like you I discovered that if you then make any changes to the custom system and 'save' them the system does not boot and just goes to the insert disk screen and then you have to upload again the new HDF file. I have discovered that if you just make a change to the custom system config and click 'use' this is okay but as soon as 'save' is clicked that's it you muse upload the HDF again.

I have emailed the always very helpful A1200NG team and supplied them with  three short YouTube videos showing the challenge. I am sure I will hear back after the Christmas holidays.

Thanks once again for your help.

the vias on the tracks don't look the best, especially the middle one, but if I were you I would check all of them under and around the integrated circuit

That that perticular track will not be issue, as other halve is still connected to layer via.

Cleaned the heads and formatting a (preused) disk did work. Knocking on wood

Coming back to my own settings:

- Standard A4000 machine spec, all on Automatic other than noted below
- ROM A4000 KS 3.2.3 (47.115)
- CPU speed set to 25Mhz (I found having this set to "Maximum" negatively impacted game/demo performance, despite being quicker to boot)
- Networking disabled
- JIT disabled
- Zorro 3 memory enabled with 1GB restricted option
- No "storage" options other than the AGS hdf added

Save states do seem to be problematic, I tested myself and saw the same fall back to the A600GS menu.

Also reconfirmed that altering options around the machine spec causes the hdf boot to fail, requiring it to be removed and re-added. I think this issue may have been raised somewhere before in relation to RDB hdf files