Microsoft ScanDisk Log file generated at 08:00AM on Monday, September 06, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 35 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:07AM on Monday, September 06, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 02:18PM on Monday, September 06, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 26 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:59AM on Tuesday, September 07, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 4 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:55AM on Wednesday, September 08, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 24 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 03:20PM on Wednesday, September 08, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 16 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:00AM on Thursday, September 09, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 3 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:04AM on Thursday, September 09, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:36AM on Thursday, September 09, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 12:36PM on Thursday, September 09, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 3 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 12:40PM on Thursday, September 09, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system The free space was being reported incorrectly. ScanDisk successfully fixed the free space count. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 03:28PM on Thursday, September 09, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 14 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 03:37PM on Thursday, September 09, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 04:16PM on Thursday, September 09, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 05:24PM on Thursday, September 09, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 6 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:06AM on Friday, September 10, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 10 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:19AM on Friday, September 10, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system The free space was being reported incorrectly. ScanDisk successfully fixed the free space count. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:57AM on Saturday, September 11, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 31 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:10AM on Saturday, September 11, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 04:22PM on Saturday, September 11, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 22 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive E for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not find any problems. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 04:36PM on Saturday, September 11, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 9 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:09AM on Monday, September 13, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 13 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 09:00AM on Monday, September 13, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 5 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 12:22PM on Monday, September 13, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 15 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 03:06PM on Monday, September 13, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 22 lost clusters in 5 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:01AM on Tuesday, September 14, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 268 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:56AM on Wednesday, September 15, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 35 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:02AM on Thursday, September 16, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 23 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 12:45PM on Thursday, September 16, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 19 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:29PM on Thursday, September 16, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 25 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:02AM on Friday, September 17, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 4 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive E for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not find any problems. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:50PM on Friday, September 17, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 29 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive E for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not find any problems. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:05AM on Saturday, September 18, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 12:31PM on Saturday, September 18, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 16 lost clusters in 5 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive E for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not find any problems. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:17AM on Monday, September 20, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 14 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:58AM on Tuesday, September 21, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 31 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 02:21PM on Tuesday, September 21, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 297 lost clusters in 5 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive E for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not find any problems. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 05:01PM on Tuesday, September 21, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 31 lost clusters in 3 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive D for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system The free space was being reported incorrectly. ScanDisk successfully fixed the free space count. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:59AM on Wednesday, September 22, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 6 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 10:18AM on Wednesday, September 22, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 10 lost clusters in 3 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:55AM on Thursday, September 23, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 48 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:03AM on Thursday, September 23, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 09:52AM on Thursday, September 23, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 5 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:17PM on Thursday, September 23, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 39 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive D for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not find any problems. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:55PM on Thursday, September 23, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 14 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:00AM on Friday, September 24, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:55AM on Saturday, September 25, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 34 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 09:37AM on Saturday, September 25, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 2,851 lost clusters in 5 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 10:08AM on Saturday, September 25, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not perform any tests. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:52AM on Monday, September 27, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 1,296 lost clusters in 7 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive E for problems, with the following results: Directory structure ScanDisk did not perform any tests. File allocation table ScanDisk did not find any problems. File system ScanDisk did not perform any tests. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:09AM on Monday, September 27, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive E for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not find any problems. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:40AM on Tuesday, September 28, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 16 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:45AM on Tuesday, September 28, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:48AM on Wednesday, September 29, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 3 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 10:52AM on Wednesday, September 29, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 34 lost clusters in 3 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 10:59AM on Wednesday, September 29, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 2,214 lost clusters in 4 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 04:16PM on Wednesday, September 29, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 16 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 04:45PM on Wednesday, September 29, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 4 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:42AM on Thursday, September 30, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 09:15AM on Thursday, September 30, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 04:59PM on Thursday, September 30, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 11 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 06:52PM on Monday, October 04, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 5 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 06:59PM on Monday, October 04, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There was one lost cluster. ScanDisk reclaimed the lost cluster as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:55AM on Tuesday, October 05, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 9 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive D for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not find any problems. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:43AM on Tuesday, October 05, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 2 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:56PM on Tuesday, October 05, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not perform any tests. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:06AM on Wednesday, October 06, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 28 lost clusters in 3 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:21PM on Wednesday, October 06, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not perform any tests. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 07:29PM on Wednesday, October 06, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 294 lost clusters in 5 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:04AM on Thursday, October 07, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not find any problems. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:32AM on Thursday, October 07, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 23 lost clusters in 2 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive D for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not find any problems. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 02:21PM on Thursday, October 07, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 11 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive E for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not find any problems. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 04:17PM on Thursday, October 07, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 270 lost clusters in 3 chains. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. ScanDisk checked drive D for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system ScanDisk did not find any problems. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 06:22PM on Thursday, October 07, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 2 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests. Microsoft ScanDisk Log file generated at 08:10AM on Friday, October 08, 2004. ScanDisk checked drive C for problems, with the following results: Directory structure ScanDisk did not find any problems. File allocation table ScanDisk did not find any problems. File system There were 7 lost clusters in one chain. ScanDisk reclaimed the lost clusters as free space. Surface scan ScanDisk did not perform any tests.