ROM 3.1 (a500 version) problems

[ref]

Agenda:
I am using an old scsi card on my windows PC to plug my real scsi a590 harddisk to winuae, so I could install everything from UAE, then move my harddisk to my real amiga. I want to make sure installed programs will work under emulation thus trying to set up rom3.1 on 68000.

Problem:
I am having trouble replicating my real amiga setup on WinUAE, maybe somebody would help.

My real amiga setup is, A500+ with ROM 40.63 (OS3.1 for A500), icd adspeed, 1mb chipram, a590 with 2MB ram installed (total 3MB ram) and it works like charm.

The problem is if I set a similar config with the same rom images I'm using on my a500, UAE doesn't boot and stays in black or grey screen. Winuae doesn't like my 16bit ROM I guess. does anybody use a500 version of ROM 3.1 on winuae?

thanks

[thomas]

does anybody use a500 version of ROM 3.1 on winuae?

Yes, all the time. Your problem is not related to the ROM.

You should provide the usual info, config file, log files.

[fitzsteve]

Yes, I test all the time my A500/A600 setups on winuae with 40.63 rom and have no issues.

[lesta_smsc]

I have booted to 3.1 on A500 purely through softkick and had no problems...

[mark_k]

Originally Posted by ref

The problem is if I set a similar config with the same rom images I'm using on my a500, UAE doesn't boot and stays in black or grey screen. Winuae doesn't like my 16bit ROM I guess. does anybody use a500 version of ROM 3.1 on winuae?

Post the config file you're having trouble with here.

[ref]

There is no need for config file, because I can replicate the same problem with going into quickstart, select a500+ from the dropdown list, start the amiga, see if it works, then restart, change the rom with a500 ks 3.1 rom and it crashes the amiga (winuae is also crashes at this point time to time).

All reports points to that my rom file is corrupted, wrong or somehow incompatible. it is a 512kb file too.

[thomas]

If it is shown as "KS ROM v3.1 (A500,A600,A2000) rev 40.63 (512k)" in the drop down menu by WinUAE, then it is not corrupted. This identification is done by checksum and I doubt that it is possible to do random corruption and keep the checksum at the same time. If you don't select it from the drop down menu but from a file requester, then it might be corrupted but I doubt this, too, because a corrupted ROM would either not work at all or start with a red screen for the same reason as above (wrong checksum).

If you still think it is corruption, then it has to be an intentional manipulation.

[Toni Wilen]

winuaelog.txt (not winuaebootlog.txt) is still required. It will 100% identify if rom is wrong. (Misc panel, tick logging option before starting emulation).