| Author | Message | ||
     david Username: dude Registered: N/A |
I am trying to make an image clone of a harddrive that has been damaged. The image file creation is fine until about 25% of the way through when I get errors like this in a popup:- Winhex - drive [h:] winhex.exe - Device Time-Out The specified I/O operation on \device\hardisk 1\DR2 was not completed before the time out period expired. and three options are presented:- Cancel, Try again, Continue I set the option to log silently but it still notifys me of this error. I've tried searching for information on it and have checked the manual as well. If I've missed a reference too it my apologies but what are the options here ? can I get winhex to keep going automatically? Also is it possible to shorten the timeout period etc ? Which key should I be clicking, cancel or continue or try again, as I tried cancel and it seemed no different to pressing continue. Thanks. David. | ||
| Stefan Fleischmann Username: admin Registered: 1-2001 |
This is an error message box created by Windows, not by WinHex. Are you using a licensed version of WinHex? Cannot find your e-mail address in our database. | ||
| david Username: dude Registered: N/A |
yes sorry the copy is licensed, I purchased it using another email account. I've updated my account details to reflect that email addy. So its a windows problem, kinda fiqures  Anyway After a fair bit of time clicking on Continue its stopped popping up and the imaging is preceding, slowly, but its going on with out intervention anyway. Do you know if there is a work around for this? I have a vague memory of having stumbled across this kind of problem before but on a windows 98 machine not XP pro. Thanks David. | ||
| Stefan Fleischmann Username: admin Registered: 1-2001 |
This message box cannot be suppressed by WinHex, sorry, and I don't know a work-around. I would try clicking Retry in such a situation and would expect some loss of data with both other options. | ||
| david Username: dude Registered: N/A |
I'd expect some data loss anyway the drive was in bad shape to begin with. Would it be better if the imaging of the drive was done in a command line environment? From what I'm reading windows seems to act as a buffer making it harder and slower to image a drive. if so is there another (preferably faster still going) way of doing it availiable ? An somewhat of OT was Winhex around in the late 80's on Apple machines ? meant to ask when i purchased. | ||
| Jens Kirschner Username: admin3 Registered: 4-2004 |
No, actually, the Windows drivers usually make way better use of the available hardware speeds compared to classic DOS options (there are better drivers available for DOS as well, but hardly ever used because you'd have to put that together on your own). However, Windows might be a hindrance trying to communicate with the disk's volumes. For non-forensic purposes not an issue, though, usually. WinHex was invented as a Windows hex editor and has never been meant to be run natively on other operating systems. |