| Author | Message | ||
     Todd Gabler Username: rudiger Registered: N/A |
I ran Trace on a 250GB drive. At approx. 1.3million URLs the runtime error 203 appears. The program quits. I have run this on an I7, 3GB RAM, XP machine and a dual core 64, 4GB RAM, Vista. Same error on both machines. How can I work around this? can I recover the partial file somewhere? Todd Gabler Rudiger Investigations rudiger@hughes.net | ||
| Stefan Fleischmann Username: admin Registered: 1-2001 |
I'm afraid you can't get around this error, and no file is written anywhere when X-Ways Trace reads from a file or disk to collect URLs. Usually X-Ways Trace would collect information about such an error that I could use to track it down, but in this case apparently that didn't work for some reason. I'm sorry. | ||
| Todd Gabler Username: rudiger Registered: N/A |
OK. Is there another method to acquire the URL history with Winhex or XWAYS forensics? | ||
| Stefan Fleischmann Username: admin Registered: 1-2001 |
If you applied Trace to the entire disk and the error occurred when a URL was found somewhere in free space or slack space (you cannot know, but it's possible), then you could at least get all the URLs from all existing index.dat files if you open them with File | Open Folder. | ||
| Todd Gabler Username: rudiger Registered: N/A |
Might I suggest that a future release of Trace write the results to an appendable file on the examiner's disk instead of storing it in RAM. That would eliminate this problem. | ||
| Stefan Fleischmann Username: admin Registered: 1-2001 |
Yes, you might, but it would be a big change in the software. |