Discussion Locked

missing system.ini file

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
when I go to boot I get the message that the system.ini file is damaged or mising. What steps do i need to take?

7 replies

by rsoft

First of al, try sysedit. If you can't find it, use Run.. in the Start menu and type in sysedit.

If it shows system.ini, look at it carefully. Look for weird characters (the one's not on your keyboard).

If it isn't that bad, try to fix it yourself. If it is bad, or you can't find the file, look further.

Is it a new system (at least, recently installed)?: reinstall, not that fast, but very safe.

Do you have a similar system somewhere (same configuration, same apps, same everything)? Locate the system.ini on that system and copy to the exact same location on your system.

If you're still out of luck, the best (and probably only) thing to do is reinstall.

by info

You will have to reinstall your windows...

You can just reinstall it over the one you already had... will will probably not lose anything if the system.ini file is the only one corrupted!

by timp999

Before you go through all of that, try using one of the boot disk tools to see if you can "Back your computer up" to an earlier time. Windows ME does this for you, but other version don't provide an easy way to do it.

A tool called the "UltimateBoot Disk" will do this for you. I'm sure there are many others, that's just the first one that comes to mind. If your system backs up its registry frequently, often you can repair it just by restoring an older version of the registry.

In the future, consider adding a line to your autoexec.bat that reads somthing like:

copy c:\windows\system.ini c:\windows\system.bk /Y

This will copy your .ini file to a backup each time you reboot. the /Y switch tells it to overwrite the previous backup, since it will be using the same name.

There are utils that do this too, if you are not dos-friendly.

Whichever path you take, good luck!

Tim

This discussion is closed to new replies.