We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Corupt Win.ini file

otisbird
otisbird asked
on
Medium Priority
332 Views
Last Modified: 2010-04-12
What would cause my win.ini file to corupt?  I use win 3.11, have a 133 motherboard, pentium clone (amp, I think).  When it corupted I lost my fonts & color.
Comment
Watch Question

Commented:
There are any numerous ways to corrupt a file..
..Check the HD for bad blocks,etc...
..was the pc powered off while in a running state?
..Did a driver installation/or any win app fail during install?

just to name a few possible ways...

Commented:
Try to boot windows 3.11 at dosprompt with this command
win/b
and see file BOOTLOG.TXT
P.S.. If you win.ini become to larger than 32 kb your system will be corrupt.

Commented:
A common problem is if you are running some kind of caching software with write-cache enabled. If you then exit windows and immediatly turn off the power, the cache will not always be flushed to disk, leaving corrupt files behind.

Author

Commented:
Now I need more information:  Scorch
What is 'powered off' while in running state?  Do you mean turned off with out going out of windows?
What is 'driver installation/ or any win app fail during install?'

Blackman:
What is an example of 'software with write enable'.  Then I may understand about 'flushing the disk'.

Author

Commented:
More questions.  This is for Tessib:
I booted from dos promt with win/b.  It just took me to windows.  Was it suppose to take me to dos shell or something?  Or were am I looking for BOOTLOG.TXT file?
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
If windows freezes up and you say NOT to press reset....what do you do to get it started again?

Commented:
Try to do it "soft way" - by Ctrl-Alt-Del. If it doesn't work ONLY
then press Reset. Anyway, if you forced to reboot while you in
Windows, run Scandisk right after reboot to ensure that all
damages were repaired (you may skip Surface Scan tho').
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.