Forum Home
Press F1
Thread ID: 9567	2001-06-04 10:14:00	Scandisk failure still not solved	Guest (0)	Press F1

Post ID	Timestamp	Content	User
13610	2001-06-04 10:14:00	Thank you Terry Porritt for your reply , re: Scandisk problem -I got Microsoft Power Toys to work as a cabinet viewer as you suggested & used this to reinstall scandskw.exe from my Windows 95 CD - still the same problem persists. I even uninstalled it & then searched for it, once I was sure how to extract it from the CD, to check that the extracted file had in fact replaced the original program. Does scanning the drive in Dos mode still scan the same as a Windows scan? If it does, maybe I need to be happy with this?	Guest (0)
13611	2001-06-05 01:31:00	Well, Ive had a chance to do a bit more digging. K1W1 may be right in that a file could be corrupt, however you have shown it's not scandskw.exe. This program is less than 5KB, and is only a stub, calling up code from shell.dll and dskmaint.dll. It may be that one of these files is flaky. Since you now have cabview installed you could try extracting both of these files from your Win95 CD and putting them in c:\windows\system. Try dskmaint.dll first, and if there is still a problem, then shell.dll. The files should be in Precopy2.cab (Win95 release 2.1 OEM disk, maybe somewhere else on another disk.) There is still another consideration, the problem you have is typical of a program running in the background, and it affects defrag in the same way. There could be something that has not in fact been turned off when you try to scandisk. One contender for this is apparently the Microsoft Office Find Fast utility, which if you have it should be paused from the Find Fast icon in Control Panel. Do you have a similar problem with defrag? Scandisk from DOS is not quite the same as from Windows. The Windows version checks both the primary FAT (file allocation table) and the backup one, and if there is a problem uses the better one. DOS always uses the primary copy of FAT.	Guest (0)
13612	2001-06-06 14:32:00	As you don't seem to be making any progress on this problem,I would suggest a visit to the Knowledge Base at microsoft.com is probably in order.	Guest (0)
1