<html><body><div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:12pt"><div><span>Remove the drive from the laptop (generally, very easy to do).</span></div><div><br><span></span></div><div><span>Attach it to a SATA - USB adapter for around $20 at MicroCenter, plug it into a USB port of a Windows box and use native Windows utilities to operate on it.</span></div><div><br><span></span></div><div><span>http://www.microcenter.com/search/search_results.phtml?Ntt=sata+usb+adapter&submit.x=0&submit.y=0</span></div><div><br><span></span></div><div><span>NTFS is a proprietary format, best to use Windows-native tools on it as the (generally reverse-engineered) GNU utilities can cause real damage sometimes.<br></span></div><div><span><br></span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div
style="font-family: Courier New, courier, monaco, monospace, sans-serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> "dshaw@famece.com" <dshaw@famece.com><br> <b><span style="font-weight: bold;">To:</span></b> CLUE's mailing list <clue@cluedenver.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Wednesday, March 7, 2012 4:17 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [clue] NTFS logical structure corruption?<br> </font> </div> <br>
Hi all,<br><br>Thanks for the thoughtful replies. First, a couple of clarifications. The<br>errant drive is the internal drive in a laptop, so making the filesystem<br>available on-line, or mounting the drive on a different machine, are more<br>difficult-to-implement suggestions than I'm willing to go for at this<br>time. In part this is because overall, the machine seems to run fine. I'm<br>just worried that something may be amiss that will lead to additional<br>troubles in the future.<br><br>Jim Ockers wrote:<br><br>> I assume you've done CHKDSK C: /F and rebooted,<br><br>Correct. Many times, with different options, using the DOS tools available<br>under XP/SP3. Nothing is ever reported.<br><br>> If you boot the machine from a Windows XP<br>> CD and enter the recovery console, can you<br>> delete the file?<br><br>I haven't tried this yet, but will try to get to it tonight.<br><br>> If you fire up Norton Ghost<br><br>ok—- so here's some
data I didn't put in my initial message. The only real<br>backup software I've worked with is Maxtor's Maxblast, a free copy that<br>came with a Maxtor drive. It is supposedly smart enough about NTFS to know<br>whether it can do "logical" backups or sector-by-sector backups. It can<br>create a C drive image without complaint, and browsing that image, I can<br>enter the problem folder and see the file I can't delete. Maxblast can<br>even restore the whole image without complaint, but with the same outcome<br>on the C drive when I'm done. A look at disk defragmenter graphics before<br>and after the restore suggests Maxblast was doing a logical file rebuild,<br>but I suppose it could switch back and forth as needed... And<br>unfortunately, there's no "restore everything but" option.<br><br>> Also there were some command line utilites<br>> like CACLS.EXE that would let you manipulate<br><br>Right. I’ve tried manipulating the situation with
them as well. In<br>addition, I have a suite of commercial UNIX utilities for Windows loaded<br>on the machine to help me get anything done, and have used them as well.<br>This was how I found the problem in the first place, when I tried to run a<br>"find C:" and it failed when it ran into the bad directory. Now I having<br>to run find with a "-prune" clause to avoid it.<br><br>> Can you find a version of WINFILE.EXE (the<br>> old Windows NT file manager) from Windows NT<br><br>Have not tried this. Any suggestions where I might such a thing that would<br>run under XP?<br><br>> the reason I mention Ghost is because it's had<br>> really good NTFS support just about from the beginning.<br><br>Thanks for this recommendation. If nothing else works I may get to this.<br>My gut level is to ignore the whole thing. I'm just worried that with all<br>the multiply-hard-linked files I'm seeing that something else is wrong.<br>Whether any of this is left
over from the virus cleaning I have no idea. I<br>have another laptop with XP and a copy of Fedora loaded on it that I<br>should be able to get running tonight. I'll see whether that produces any<br>interesting comparisons.<br><br>Davis L. Willson wrote:<br><br>> 1) Use CHKDSK to repair the filesystem<br>> 2) Use TAKEOWN to take ownership of the<br>> files and directories you can't access.<br>> 3) Use ICACLS to give Administrators:Full<br>> Control and SYSTEM:Full Control on them.<br><br>I thought I had tried all these approaches already, but I'll try to take<br>another shot at it tonight.<br><br>Dave Shaw<br><br><br><br>_______________________________________________<br>clue mailing list: <a ymailto="mailto:clue@cluedenver.org" href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>For information, account preferences, or to unsubscribe see:<br>http://cluedenver.org/mailman/listinfo/clue<br><br><br> </div> </div>
</blockquote></div> </div></body></html>