| Author | Message | ||
     Patrick Jonke Username: pjonke Registered: N/A |
Hello, I need to write 0x00 to every address in a defined block that is >4GB in size on an unformatted (physical) CF drive that is connected via Firewire. If I open in In-Place edit mode under WinHex 14.2, define the block, and then use Fill->0x00, it runs for a few seconds and then I get the message "Error #21 Cannot write to Hard Disk. The device is not ready." This happens whenever the defined block is larger than 0x10000 bytes in size. If I try the same thing under Linux, "dd if=/dev/zero of=/dev/sdb bs=2048b skip=1b count=16b" completes the task in about 75 seconds, so the connection and drive media seem ok. Any ideas what is wrong? Patrick | ||
| Stefan Fleischmann Username: admin Registered: 1-2001 |
I could not reproduce this here when I just tried with a very large block. The explanation "The device is not ready" originates from Windows, and WinHex merely relays it. Perhaps it helps if you pick one of the two alternative disk access methods in Options | General Options. | ||
| Patrick Jonke Username: pjonke Registered: N/A |
Using "Option 1" fixed the problem. Wiping 1GB with WinHex now takes the same amount of time as it did with DD (about 75 seconds). Does Option 1 cause any problems when used with In-place mode? I saw some weird things occur if I made more than 1 change to an open disk; e.g., if I defined a 1 sector block and altered the bytes, scrolled away from that sector, and then returned to it later, the sector in question would not have changed but the previous sector would(!)? This problem seemed to stop if I always closed and then re-opened the in-place disk after each change. Patrick | ||
| Stefan Fleischmann Username: admin Registered: 1-2001 |
Wasn't aware of such a problem, and cannot reproduce it here. If you could describe ot even more precisely, I would appreciate it. | ||
| Patrick Jonke Username: pjonke Registered: N/A |
I think it was some kind of screen update problem. I was in a section of the disk where there was 1 sector (e.g., sector "N") with data. The sectors both before and after "N" were all 0x00. If I defined N in a block and then filled it with zeros, the byte display would change them and show them in a purple highlight color. I then scrolled away from N using the slider. However, when I jumped back (using go to sector ->), the data that was originally in N was now in N-1! N was still all 0x00. This stopped happening if I closed the disk and then reopened. After that, if I jumped back to N, the bytes were still 0x00 and no longer in purple highlight, and N-1 stayed 0x00. Strange... Patrick |