Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
im doing a new install on a new Barebone system i can install win98se on the HD fine and firewall/popkiller ect . and everything is runing fine no excalmation marks in device manger/no errors at boot but everytime i go into scandisk it says i have errors i know now from experience that running scandisk to many times with fix errors can end in disaster for your OS.now that im back to a clean install for the 3rd time.How can i fix this problem? If i go into start then shut down and choose restart in DOS command. can useing this method case my files or other things become corrupt or missing. like running it in windows.Pleas help im tired of doing Fdisk/format/install over & over lol

DOS's Scandisk can sometimes do better .
Toggle F8 ( when , verifying DMI pool message comes on ) or Press
Ctrl during bootup , depends on your computer , choose Command prompt
only ( NOT Safe mode Command prompt ), then at the C: prompt , type Scandisk /Surface & press
Enter .
When finished , type win & press Enter .http://users.iafrica.com/c/cq/cquirke/scandisk.htm

hello well up to this point i havent looked to see what errors scandisk was fixing ive been useing the fix it option when a scan is done thats were i learned that in windows that can become a night mare at least for me it has been.when scandisk widow is open where do you look for the errors that where found?

Rule number one, always, always find out what Scandisk is fixing.
Read Johns link above to find out what damage may have been caused by a "fix".This is why one should always turn off autofix. Knowing after the fact, is a bit late.
If you had logging set, then the file is called c:\Scandisk.logIf you don't, and since these errors are always happening, run it again.

Ok i ran scan disk with out the fix option and this is waht im getting
1.This drive contains one or more backup copies of the file allocation table {FAT}
the copies should be the same but arent
Repair/Ignore2.The allocation chain for VFPODBC.DLL in the C:windows/system folder indicates that part of this file or folder is stored in an invaild loaction your computer uses the allocation chain to track where each of your files and folders is stored
Repair/delet/ingore3.the C:windows/system folder conaains incorrect information about VFPODBC.DLL
The file is differnt size than recorded do i wante to change it to right size
Repair/delet/ignoreany ideals on what to do next & thank you for your help

Start by deleting the file VFPODBC.DLL and reinstalling it.
It is Visual FoxPro ODBC driver, version 6, that is part of a MS MDAC install package, BUT you may never ever need this file.
Use this site to determine the version of MDAC installed, and then post back and we will see if we can find the correct reinstall, just in case.
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/fq99-025.asp
Then, rerun scandisk. If you get a FAT mismatch, allow scandisk to Fix this. The 2 fats should always be in synch. And also see if any other errors are detected.
If not, run scandisk again, but this time in Thorough mode, to determine if the drive has bad sectors that you continue to install over.

Ok i went to the web site above and read what it says about MDAC files and i think i understand.Can i go to start and find files & folders and get to one of the .dll files to see what version i have installed and f so what would be a good one to search for to see.and im not sure about the sample pages were loaded or not i guess one step at a time.Also should i go ahead and let scan disk fix the FAT thing first before doing the MDAC find and fix or do them in the order they were found when i did scandisk

Leave the MDAC issue to the end. As I said, the DLL that you deleted (or are going to delete) may never ever be needed.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |