I know this has very little to do with CPU,s, but I really need to get this problem sorted out, so here it goes. Today I got my new broadband modem, installed the USB drivers, plugged it in, but I needed to win98 CD. So I cancelled and decided to find the CD and try again later. Well, I found it and tried to install but I couldnt change the driver, so I ended up uninstalling thw whole thing and restarting. However just before it got to the windows startup screen It came up with errors something like 'the System.ini file is refferring to files (filename) but they are not present. To resolve the problem try reinstalling the software. Well, Ithought it must be the modem so I reinstalled it successfully but the problem continues. Also now when I get into windows I get an error message saying that it cannot startup 'Microsoft Networks' from the system.ini file. Even if I disable this in msconfig it still seems to come up each time. Considereing I cant get rid of these problems and I dont know which piece of software the registry is looking for (probably something to do with freeserve, but I dont know what), is my only option to reinstall the OS?
Please help me, If my dad finds out Ive screwed his computer hell go mental, im not looking forward to telling him
Wow. It sounds like a bad uninstall. You could try complaining to the maker of the modem, but that's always a crap shoot on how helpful they'll be.
I'd say try completely uninstalling the software <i>and</i> drivers for this modem. Make sure your system doesn't have any trace of it. Then after a reboot (just to give the uninstaller a full chance at uninstalling everything) run sysedit and make sure no entries for your modem or the software that was installed with it is in there. Then if that doesn't fix it, back up your system registry and delete any mentions that are also in the registry using regedit. (Sysedit and Regedit can simply be run from the command prompt or using Start->Run... from the desktop.)
If that doesn't fix it, all that's left is to either reformat or hope that the modem manufacturer has a fix.
At least that's all that I can think of at the moment. Unfortunately, I'm not going to be able to help any futher, since I'm about to leave and be gone for days. Heh heh. But hopefully it's enough or someone else can help as well. Good luck.
[EDIT]And I can't stress enough, before you change <b>any thing</b> in Sysedit or Regedit, be <b>sure</b> to backup the files somehow in case you end up editing the wrong thing and breaking something else. If all else fails and no one else can help, use something like Google to search for more information before you do something that you're uncertain of.[/EDIT]
Ok, I was playing around with a few things, trying to get rid of the files, and after I made a copy of the system.ini file I forgot to change the name. So the computer messed up and Windows wouldnt start because it couldnt find the system.ini file. Ive just formatted and reinstalled windows, but atleast everything works perfectly now Thx for the suggestions though, broadband ADSL is sweet
1. Copy all the CAB files from the Windows installation disc to a folder on your hard disk. If Windows ever asks for the installation disk just point it to that location. You won't need to search for the disc. (This is really helpful when you are trying to fix CDROM problems and your system can't read the installation disc).
2. This next suggestion wouldn't have fixed a mis-named system.ini file but when softare installations go badly sometimes you can fix it by restoring a backup copy of the Windows registry. To do this with Windows 98SE boot to the DOS command prompt and type "scanreg /restore". Choose a copy of the registry dated just prior to the mishap. Only the five most recent copies are saved, including the current one which presumably is bad, so don't restore that one or you will lose one backup copy. <b>[edit->]</b>You shouldn't restore a backup copy of the registry unless your problems are severe.
3. If you want to track down the cause of Windows 9x boot problem try this. After the failed attempt reboot the system booting to the command prompt. Type "attrib bootlog.txt -h". This changes the hidden attribute and makes the file accessible. Type "edit bootlog.txt". You will now be able to see exactly when in the process Windows failed to boot. Hopefully you may also learn what caused the failure. (Well, sometimes it helps). When you are done don't forget to reset the hidden attribute. Type "attrib bootlog.txt +h".
<b>99% is great, unless you are talking about system stability</b><P ID="edit"><FONT SIZE=-1><EM>Edited by phsstpok on 12/15/02 00:14 AM.</EM></FONT></P>