Malvineous
Experienced Member
Hi all,
To save removing the ROM chips from my 286 board and dumping them in an external device, it seems like an easy option is (or was, until I tried it) to just use DEBUG.EXE to write the ROM data to a file.
Unfortunately when I try this, it either drops every second byte, or the machine locks completely!
I am doing this:
When I do this, the machine locks up almost immediately and I end up with a zero-byte file. Dumping the memory to the screen with the "d" command works fine. Writing less data (a few hundred bytes) also locks the machine up. I tried it with ROM BIOS shadow on and off with no difference.
If I try to dump the video ROM instead, by changing the address to C000:0 then the system doesn't lock up, but every second byte is 0x00 in the resulting file! Again, using "d" to dump the memory to the screen shows it all looks fine.
Is there some trick to correctly setting up DEBUG's "w" command?
To save removing the ROM chips from my 286 board and dumping them in an external device, it seems like an easy option is (or was, until I tried it) to just use DEBUG.EXE to write the ROM data to a file.
Unfortunately when I try this, it either drops every second byte, or the machine locks completely!
I am doing this:
Code:
n BIOS.BIN ; Write to a file called BIOS.BIN
rbx
1 ; Write 0x10000 bytes (64kB) - upper 16-bits
rcx
0 ; Lower 16-bits
w F000:0 ; Write now, starting from F000:0000
When I do this, the machine locks up almost immediately and I end up with a zero-byte file. Dumping the memory to the screen with the "d" command works fine. Writing less data (a few hundred bytes) also locks the machine up. I tried it with ROM BIOS shadow on and off with no difference.
If I try to dump the video ROM instead, by changing the address to C000:0 then the system doesn't lock up, but every second byte is 0x00 in the resulting file! Again, using "d" to dump the memory to the screen shows it all looks fine.
Is there some trick to correctly setting up DEBUG's "w" command?