| Author | Message | ||
     Paul Mullen Username: pcguru Registered: 1-2006 |
I wrote the following simple script, which works fine on every drive I tried it on until now, when I tried to run it on a 150 Gb NTFS partition. CloseAll //Select drive to search Open "E:" read-only Create "C:\CLIENTS\19207\IEHISTORY2006.DAT" 0 NextObj //drive to search //Loop through drive { Find ":2006" Down IfFound move -0x68 Read Hitrec 256 nextobj // output file write HitRec nextobj // back to search drive Else //not found ExitLoop EndIf } [unlimited] On this drive (total of 302,777,992 sectors) it seems to be working fine (last hit was around Sector 120000000) until the search gets to around 85% (with V11.5 it got to sector 258,651,912 with V13 SR12 it was at sector 258657511). Then it just hangs - computer won't respond at all to keyboard or mouse. | ||
| Stefan Fleischmann Username: admin Registered: 1-2001 |
> Then it just hangs - computer won't respond at all to keyboard or mouse. Could be physical damage on that particular hard disk. | ||
| Paul Mullen Username: pcguru Registered: 1-2006 |
That's what I thought at first, until I made a copy on to another disk and the same thing happened. Then I tried to repeat the search using a physical disk and realized that Winhex reported my 160 Gb drive as 128 Gb. Since there was a Dell utility partition at the start of the drive, it is hanging when it gets to about 128 (binary) Gb. Turns out that although the bios (and my DOS applications) see the full size of the drive, and Windows XP had SP2 and the latest Atapi.sys, the drive was attached to a Promise Ultra 100 TX2 card, which Xp thinks is a SCSI controller, and was using a Microsoft driver dated 2001. Clicking on driver update said no later driver available, even if I gave it the latest Promise driver. Unfortunately Promise don't pay for the Windows compatibility logo on their drivers, so XP won't load them unless you force it to. Oddly XP's Disk Management saw the full size of the drive. So if any reader is using a Promise controller card, it would be a good idea to check you have the latest drivers loaded. Also since Winhex displayed the exact drive model, even down to the firmware revision, it would have been nice if it could have warned me that there was a size discrepancy! |