I am having startup problems on my desktop running Windows 98SE.

I was transferring files (along a crossover cable) from my laptop to my desktop and tried to open Winamp. Winamp wouldn't open - every time I clicked on it I got a dialog box saying that the program had to terminate. I restarted my computer in the hopes that the problem would go away. But now it's not starting up properly. Instead of the usual high-resolution log-in screen with black background (my prefs), I get a low-resolution network log-in screen (asking for my network password) with Windows default bluish bacground and an error message (SSDPSRV caused an invalid page fault in module MSVCRT.DLL at 0167:7800f79e.). Once I click through that message and the network login, I get another error message: RUNONCE caused an invalid page fault in module MSVCRT.DLL at 0167:7800f79e (followed by "EXPLORER caused," etc.). Then just bluish screen and a huge pointer.

I can't start up in safe mode (holding either control key does nothing), but can access the CMOS settings. Any help you can provide would be greatly appreciated.

Tapping F8 whilst booting will usually get you to the start menu and hence Safe Mode (Ctrl key does not work on all machines).

DerekW

HOW TO RESTORE SYSTEM TO PREVIOUS REGISTRY IN WINDOWS 98

1. Start the Computer with Win98 Boot Disk in Floppy A: drive
2. Choose option #2. Start Computer without CD-ROM support
3. At A:\> Prompt, type C: and press [Enter]
4. At C:\>CD Windows \Command
5. At C:\>Windows\Command\>SCANREG /RESTORE [ ENTER]
6.Restore a Good Registry Entry from the Blue Registry Checker window
7.choose a date to restore before problems occured

If the Win98 Boot disk method is used to do the Scanreg /Restore command, [Unlike Starup in MS DOS Mode or Command Prompt Only or Safe Mode Command Prompt from Windows 98 Starup reached on CTRL/F8 on Power On] typing Scanreg /Restore at C:\> and pressing [ENTER] might return "Bad Command" on the DOS Prompt.

Geez, I often miss the obvious. Good plan OtheHill....

DerekW

Thank you for your help, Derek & OtheHill.

I managed to restore to a registry from before the problems occurred, but I'm still having the same problem. Any ideas?

Hmm, I had high hopes for scanreg /restore.

Did you managed to get your way in to Safe Mode? I can see it getting tricky if you are unable to do so.

DerekW

Hi, If you are saying that you couldn't get Winamp to run on the computer you copied it to: Most Windows programs will not run if only copied from one machine to another. They would have to be re-installed. Sometimes the error messages will tell you what they are missing and you can transfer them and get going. You may have to move several DLL's etc one at the time to get it going.

Luck, Jim

Hey, Derek,

I managed to get into safe mode, but the same thing happened. But now I don't seem to be able to access the start menu.

Also, I don't know if this would help or not, but my computer now takes an inordinate amount of time to get past the Windows 98 splash screen.

JimPIM
Transferring files rather than installing also means that there are no registry entries which are essential to most programs. I don't think the poster said he had transferred WinAmp itself by files alone, but perhaps this can be clarified.

pfadfaog
What now happens when you try to get to the startup menu? Can you further clarify what exactly you were doing which caused this and what program(s) you were using? It reads as if for some unknown reason you decided to start WinAmp in the middle of a file transfer, when presumably some other program was handling the transfer itself. Is that right?

DerekW

Sorry I wasn't clear. I installed Winamp & have been using it for awhile.

As for more detail about the situation: When the issue occurred, I'd been copying files from my desktop to my laptop (with Windows Explorer). I tried playing one of those files (an mp3) with Windows Media Player, which said that it couldn't play the file. I then tried to open Winamp to see if it would play there, but Winamp wouldn't open (just got a dialog box saying Winamp had to terminate). I restarted my computer to see if that would clear the problem up. My computer didn't boot back up properly, though - I haven't been able to do anything in Windows since.

Originally, I assumed that one of the mp3s had a virus in it, but my laptop is working fine and I've run a couple virus checks on it - which it's passed.

Sorry for the confusion, and thanks for the continued responses.

I think you should give that scanreg /restore one more go. Make sure you choose a date/time before you started this excercise.

If you are in Safe Mode just type scanreg /restore

DerekW

Now when I type c: all I get is "Invalid drive specification".

More detail with your last post.

Also, try putting a blank floppy in the drive and see if you are still able to switch to A:

DerekW

I have two boot disks: a Windows 98SE boot disk and an Ultimate Boot Disk.

When I start up with the Windows 98SE disk, I get an A:\> prompt. When I type c: I get "Invalid drive specification".

When I start up with the Ultimate Boot Disk, I get a 6-option menu (1. Normal, 2. Logged (\BOOTLOG.TXT), 3. Safe mode, 4. Step-by-step confirmation, 5. Command prompt only, 6. Safe mode command prompt only). Choosing the latter option, I get an A:\> prompt. When I type c: I get "Invalid drive specification".

I am beginning to wonder if any of this had anything to do with what your were doing at all.

Can you see the C drive in CMOS?

DerekW

Ah, good idea. I do not see the c drive in CMOS. Oy.

Hmm, could be the HD itself has died....

A few things to try:

Look inside the box to make sure the HD cables are still on tightly. Might as well check all connections while you are in there.

Reset CMOS to defaults (noting any of your own pet settings first).

A new CMOS battery is very cheap and usually easy to replace - just in case it is CMOS that is screwed.

Other than that lot (or anything anyone else comes up with) then I'm afraid we get back to HD failure again.

DerekW

... err, by HD cables I meant where they fit to mobo as well of-course.

DerekW

Sure - little else is of any import until the drive registers in the BIOS. Battery trouble alone wouldn't cause this, as the drive should be redetected upon startup. Possibly a bad or loose cable (no harm in checking that) - otherwise, it may have quit

Ah, Jim - zeroing in on the heart of the issue (as usual)

... the interests and rights of some individuals take precedence over the interests and rights of others

Report Offensive Follow Up For Removal

Yes, you are of-course quite right about the battery.
I was being far too hopeful.

DerekW