Damaged system.ini, errors reinstalling windows

Damaged system.ini, errors reinstalling windows

Post by shuert » Mon, 22 Sep 2003 08:39:06


Hi all,

After a week of trying to fix computer, I feel like I'm at my wits
end. Last week I got an error message that read : "A device file that
specified in the system.INI file is damaged, it may be needed to run
windows.You may need to run the windows setup program again. If the
file is included in another software package, you may need to
reinstall the software that uses the file XXXXX" and listed about 10
files that were missing. After some extensive research on here, I
found the instructions to fix the system.ini file. When I got to
copying the system.cb to system.ini - I received a "file not found".

So, I thought next I'd try reinstalling Win98 SE and ran scandisk and
it fixed a multitude of problems. Once I got to the windows 98 setup
screen, I got an error that said I had a corrupt .cab file possibly
due to low memory, hardware problem or a virus. I ran virus check,
nothing. I did some more research and found how to extract the .cab
files by copying Win98 setup to my c drive. I followed the
instructions and received the following error "extracting error:
cannot open file".

I am baffled. If anyone could help me, I'd really appreciate it. I'm
new to all of this, and I'm getting quite frustrated. :(

Thanks in advance,
Stephanie
 
 
 

Damaged system.ini, errors reinstalling windows

Post by H Leboeu » Mon, 22 Sep 2003 20:48:27

This article is intended for windows 98 (pre se) try to make a system.ini
file and see if you can at least get to your explorer.

Creating a New System.ini File Without Third-Party Drivers
You may need to create a new System.ini file if, after using standard
troubleshooting procedures to determine the cause of a problem, the
System.ini file becomes incorrect, missing, or damaged.
http://www.yqcomputer.com/
--

Henri Leboeuf
Web page: http://www.yqcomputer.com/ ~hleboeuf/index.htm

 
 
 

Damaged system.ini, errors reinstalling windows

Post by Ben Myer » Tue, 23 Sep 2003 10:09:28

Start the computer and make a note of the first file mentioned.
Extract a fresh copy of this file into the "c:\windows\system\vmm32"
folder, then restart. If the error message for this file no longer appears,
extract fresh copies of the remaining files.

Ben