CD32 KS ROM V3.1 .EXE

EXE do this interleaving? YES so, let's try with real CD32 Roms CD32 KS ROM v3.1 - CRC32 1E62D4A5 CD32 extended ROM - CRC32 87746BE2 INTERL CD32 KS ROM v3.1 + CD32 extended ROM Bad checksum: i got C9DA5A71 instead of A4FBC94A INTERL CD32 extended ROM + CD32 KS ROM v3.1 Bad checksum: i got 4BBF6ACC instead of A4FBC94A CD32 ROM (KS + extended) REAL DUMP definition taken from WinUAE source so i think that this. It is different than normal interleave: A = KS ROM B = EXT ROM byte 1 of A byte 0 of A byte 1 of B byte 0 of B byte 3 of A byte 2 of A byte 3 of B. romPath = c: HyperSpin Games Commodore Amiga CD32. Apparently, the problem was to create the extended one with Remus as well ( I was using the original 40.60 before).59 rows.rom CD32 Kickstart ROM v3.1 rev 40.60.rom [. Now it doesnвЂ™t boot the TF330, so investigating what else is required (beside cd32 exec) in Remus.ДЇor the record, I managed to make it work on the CD32 with the TF. Physical kickstart shows the splash screen :-) It doesnвЂ™t require an additional byteswap and the two banks have to be exchanged from what the tool proposes. Will test more in the coming days and possibly try HxD to manually cut in half. I don't really know what the usual 'HI/LO split' does so I am going to investigate. It seems to me that the rom should be divided in half (I mean not ODD and EVEN) and then these two half should be byte-swapped before burning them on the 27C800 respectivelly as bank #0 and bank #1. The problem is now to burn the physical rom. I didn't test more than that, so there might be something else not working. It shows the CD32 splash screen and then boot to the Workbench 3.2. I pointed WinUAE to that as a single 1MB rom without extended one. In my case, both approaches returned a 1MB rom with CRC 65DE0458. I later noticed that the Eprom Tool v 0.90 includes a juicy 'Create Amiga CD32 rom' which performs the same with a couple of clicks.

CD32 KS ROM V3.1 WINDOWS 10

I downloaded the Windows 10 flavour of the srec_cat and removed the back-slashes The LIV2 script that reinauer posted works just fine. Combined the above 512KB with the 512KB CD32 3.1 extended rom. I am not sure whether there are other modules to be added/replaced. With the new Remus, started from the A1200 KS32 modules and replaced the exec with the one on the CD32's adf. These are the findings, in case they could be somehow useful:

I am fully aware this approach is not supported, therefore consider this as a kind of test So far, no success on the real hardware, but it works on WinUAE. Yesterday I decided to test the KS 3.2 on the CD32. Now, when first 262144 bytes are taken from file B, how the seguence goes on? So i think that this is the correct interleaving:ДЄll first 16 bytes are taken from file B (CD32 extended ROM) in this sequence: 1 0 5 4 9 8 13 12 17 16 21 20 25 24 29 28ДЇOR x=0 TO. The correct first 16 bytes that you reported is: If you see image above, the INTERL does the correct interleaving as you said because first 7 bytes of CD32 KS ROM v3.1 and CD32 extended ROM are eguals (and so it's normal that result have duplicate pairs) Maybe the problem is with INTERL? i think it use byte of 16 bits, maybe i must try an interleaving with byte of 8 bits? The correct CRC32 for CD32 ROM (KS + extended) REAL DUMP is a4fbc94a INTERL 'CD32 ROM (KS + extended) second half' 'CD32 ROM (KS + extended) fisrt half' result INTERL 'CD32 ROM (KS + extended) first half' 'CD32 ROM (KS + extended) second half' result Have the same CRC32 of half parts of the two roms above (391640-03.u6a and CD32 ROM (KS + extended))

Cd32 Ks Rom V3.1