sfc/scannow

Can't i run the sfc from a boot-floppie command..??

 

I would "guess" not, since it is a windows app, and after booting you would be in DOS.

Why do you want to do this?

 

i want to refresh any corrupted files.

can sfc br run from the RUN box inside w98..??

 

SFC is NOT a good tool to "refresh" corrupted files. It is a tool that needs to be run regularly before and after installs/uninstalls in order to be useful.
Just running it out of the blue will result in many misleading messages.
As well, it is well known to report files as being corrupted when in fact they aren't.
Also, be aware that you do not want to (necessarily) restore files from the Windows CD. Files such as DLLs will be badly outof date, and need to be restored from the net or from the installation folder for the specific progam that updated it.

And yes, SFC can start from the RUN box.

Are you having specific problems that have led you to do this??

 

Well, it's not my puter....but it had AOL and Norton on it and she removed it and don't know exactly ow cos i wasn't there.

But for starter's;
wucrtupd and Odbcinst are corrupted and internet explorer IE6 will not open. The whole thing is a mess i guess cos all kind of wierd stuff is happen and it has a upto date AVG running. I thought if i could re-new corrupted or missing files it would help.

 

I have supplied this snippet from time to time when sfc subject comes up, but I don't know if this was before the help-net hacker incident or after, so here it is again......

Here's some friendly handy dandy advice to accompany an SFC use recommendation:

Sfc is best left, used as an extractor for file replacement and a "Helper" tool ONLY. For those who have no foreknowledge or familiarity with their OS files, drivers [.dll's etc.] it will be very confusing and intimidating. In addition, in many cases, be down right dangerous when it comes to inflicting cases of "Versionitus ".

If you do not use it often and routinely to update the baseline file such as after all upgrades/updates, new installations or uninstalls you can easily be over whelmed by all the files that get flagged.

Don't get me wrong, this can be a good tool for a troubled OS but it takes a great deal of upkeep and a thorough understanding of how the baseline file list and files of description: altered/changed, corrupt, and deleted are determined.
For example:

Altered files= If System File Checker detects a change in date, time, size, or version, it considers the file to be........

Changed= a change in date, time, or version, file will be reported as changed. SFC can not determine if this was a good/bad, planed or unplanned. It is up to you as the user to determine if this change was an due to an unplanned overwrite, virus, system glitch etc. or an "expected "/planed change as a result via an update/upgrade or install.

Maybe Corrupt= You are always notified of damaged files. A file is identified as damaged if its date and version match, but the "CRC" [File size: A checksum added to a file entry whenever a file is written to disk, used to see if the file has changed] value does not match the baseline. Usually, if a file is flagged as corrupt your best bet is to err on sfc determination that it is corrupt. You should have enabled the option to always backup file before replacement in case of mis- judgment.

Deleted=self explanatory.
NOTE*I had this option enabled but have since disabled it as I frequently install and uninstall app's and games. This got to be more of a nuisance than an aid.

========To sum up=======
This tool should only be used as a helper app unless:
*You have formed a habit of running this as part of a regular routine to keep the "baseline list" up to date such as after an update/upgrade/install/unistall,
*Or are specifically using it to check for "file corruption flags" due to current application problem]. Any file flagged as corrupted or changed should be further investigated before taking sfc's word that it needs replacement. If a file is flagged as such just click sfc's "ignore option" for now, until you can confirm it is not part of a recent install or update.
note*Generally never replace a newer version file with an older one.

ADDITIONAL NOTES*
1]there are always exceptions to every rule and there are even workarounds for the exceptions.
2]Usually, if a file is flagged as corrupt your best bet is to err on sfc determination that it is corrupt. It has a backup option that will offer to backup any file you replace so this is reversible.
3]known bug in original win98 SFC has been fixed with updates or winSE, but if you have not employed such updates:
You must be careful to browse[point] to specific cab folder when dealing with certain key file replacements as indicated by links below: http://support.microsoft.com/suppor...s may also take care of the Odbcinst problem.

 

Gads goddez1, thats a great article......and thx for the info.

"Ok ", then whats the best way to fix my problem..?

 

opps....

Been updating my original post and have missed your reply while typing. You may also have overlooked the bottom of my post where I have made a couple of suggestions. Did you give these ago?

 

Sure, i'll give it a go tomm. first thing when i get over there.

Thanks

 

[Before using advice below and if your friend is using office 2000 or higher, try the "office repair" function.

..................
If the IE repair still leaves your mdac files crippled. You may find this helpful:

You may need to install the latest mdac files for your system. Or perhaps just run the "Component Checker" and see what it reports. Only problem is I am on winXP and I don't know what version is recommended for win98xx. You may have to research this further. [?Component Checker as mentioned below...????]

RESOLUTION
Download and install the latest version of the Microsoft Data Access Components (MDAC). This package updates all ODBC and the newer OLE DB drivers and resources on the system. The latest version of MDAC can be downloaded from the following Microsoft Web site:
http://www.microsoft.com/data/download.htm
NOTE: You cannot install MDAC separately in a Windows 2000 computer because MDAC is part of the system components.

You can also diagnose and reconfigure your current MDAC installation by using the Component Checker tool. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
307255 INFO: Component Checker: Diagnose and Reconfigure MDAC Installations
REFERENCES
You can find information on individual DLLs at the following Microsoft Web site:
http://support.microsoft.com/servicedesks/fileversion/dllinfo.asp?sd=GN

 

Odbcint is a part of Microsoft Data Access Components and Jet. Not just any version of that file will work, and it is not included with the IE setup cabs.
This page has the complete MDAC 2.6 install file you could use. I installed this version on 98SE when running 5.5 SP2, and am now running IE6 SP1.
The critical update can be downloaded here.
I agree with goddez1 about using SFC, especially now that the correct version of some system files can only be found in the IE setup files. A bad case of versionitis can easily be created.

 

Thanks markp62,
Seems I am just typing to darn slow today........ was trying to supply link for MDAC files but you beat me to it, in a manner of speaking. Glad you added your imput as I didn'tknow which version the poster would need.

Thanks again...

=============
Here comes some nfo overload..............

Thinking outloud:
If the original problem started on an AOl uninstall, I wonder if the IE being used was a branded AOL version. Don't know nothing bout AOL or it's companion IE, but I thought this may worth throwing out there for some consideration. If this is AOL\IE related others more familiar with this duo and any known problematic glitches with an unistall will have to take over from here. Just thought I'd throw this in the mix for a heads-up consideration.