| Author |
Message |
   
Jimmy Weg
Username: jw
Registered: 7-2006
| | Posted on Friday, Apr 18, 2008 - 22:25: | |
Using the Winhex 14.9 add-on, I opened my system volume (XP64) and attempted to wipe slack. I receive a message of "Unable to lock the drive. Other programs may be using it. Access is denied. Continue anyway?" If I continue, I receive an Error 21, with the Abort, Retry, and Ignore options. I aborted at that point, pending guidance. No other applications are running that would seem to prevent the operation. Thanks. |
   
Stefan Fleischmann
Username: admin
Registered: 1-2001
| | Posted on Friday, Apr 18, 2008 - 22:40: | |
> No other applications are running that would seem to prevent the operation. According to your description, it seems like one of the most complex operating systems on this planet was running from that volume, and that operating system consists of an incredible number of program files. You could try editing and writing just a single sector, e.g. in free space. If writing certain sectors or all sectors on that volume fails, then sorry, then you could still try v14.8, but maybe WinHex is simply unable to write to that volume directly. |
   
Jimmy Weg
Username: jw
Registered: 7-2006
| | Posted on Friday, Apr 18, 2008 - 23:08: | |
Thanks, Stefan. 14.8 was able to initialize slack. I was, however, able to edit bytes among several free space sectors with the 14.9 add-on. Perhaps the most complex OS on Earth is less finicky about free space ;-). |
   
Stefan Fleischmann
Username: admin
Registered: 1-2001
| | Posted on Friday, Apr 18, 2008 - 23:50: | |
OK, I will try to make it work in v14.9 as before. Here under 32-bit XP v14.9 still manages to wipe slack on the Windows/C: drive. |
   
Don Camillo
Username: willybilly
Registered: N/A
| | Posted on Sunday, Sep 14, 2008 - 21:26: | |
Hi, I tried to do the same with a test version of Winhex yesterday - Tools - Disk Tools - Initialize Directory Entries on Vista 64 bit. The first problem was the same as described above, Winhex said that it was unable to lock the drives - no problem: Abort - Continue. The second greater problem: Independet from what I chose (Abort / Continue) the message appeared again and again. It was an endless loop. The program could not be closed - the only chance was to kill winhex. One more of the bugs where I wonder that I am really the first who discovers this.... |
   
Stefan Fleischmann
Username: admin
Registered: 1-2001
| | Posted on Sunday, Sep 14, 2008 - 22:24: | |
1) Ability to write sectors in partitioned disk areas is not guaranteed under Windows Vista. 2) Clicking the black "x" in the upper right corner of the small progress indicator window aborts ongoing operations in WinHex and X-Ways Forensics since these programs exist. > One more of the bugs where I wonder that I am really the > first who discovers this No, this is not a bug, and our opinions do not only differ in this case. |
   
Don Camillo
Username: willybilly
Registered: N/A
| | Posted on Monday, Sep 15, 2008 - 20:00: | |
2) well, this should be the standard procedure - in the last test it only ended after the following message: Exception situation type 216 occurred at memory offset 004A28D9 when I [please complete]... and our opinions do not only differ in this case I know, and this is the reason for "Don Camillo". The name has only a symbolic NOT a political meaning. For those who don`t know where the name comes from: http://en.wikipedia.org/wiki/Don_Camillo |
   
Stefan Fleischmann
Username: admin
Registered: 1-2001
| | Posted on Thursday, Sep 18, 2008 - 20:39: | |
(Exception error addresses without the exact version number are meaningless for us, unfortunately, that's why the program asks you to e-mail the error.log file.) |