W98 starts to boot then screen goes blank

[msmindy1]

Well, guys, just a quick answer on this one.

This system that I'm working on will boot, give a good beep like all is well, then it gave the errors that vxd files were missing (vnetsup.vxd, vredir.vxd, and dfs.vxd). I found these on the internet and copied them to windows/system. The errors are not showing up, but still a blank screen. I tried to install windows again, won't read d: drive.

I'm basically just going to reformat and reinstall windows. The user has no files to save and says it's okay. Just wondering though, if anyone would know what this is?? Just curious as I've been working with it all day and just has me frustrated. I can't find anything on the internet that might explain it.

Thanks. You guys are great! I tried looking this up on the forums, but couldn't find anything.

 

[Jontmke]

Sounds like the Hard drive got hosed. Run a scandisk, boot with a floppy, then run the reinstall of Windows.

JON

 

[jmatt]

http://support.microsoft.com/defaul...port/kb/articles/q166/8/32.asp&NoWebContent=1

CAUSE
This problem can occur if you install Dial-Up Networking, Dial-Up Adapter, or Virtual Private Networking and then cancel Setup while the Copying Files dialog box is displayed. The Dial-Up Networking files are not copied to the hard disk but the file names are added to the registry. When the computer is restarted, the files are requested and cannot be found.

 

[msmindy1]

jontmke: I had ran scandisk, booted with a floppy and tried to install the windows files from disk, it won't read the d: drive. So, I'm thinking that I just need to fdisk and reinstall windows.

jmatt: I read that, but I cannot get to the desktop to do that. And I have forgotten half of the half of dos that I knew so I'm struggling there some! I think she said that all that her husband did was shut it down while it was still on the internet (and of course, they never do anything wrong), so I'm sure that is the answer then as to why.

Thanks for the answers and the prompt response.

 

[mudskipper]

msmindy1 -- Those errors are due to the networking crud, but have you tried going into safe mode? See, normally, when the listed errors come up, they won't stop you from booting into windows.

Sounds to me like a dual problem -- the errors listed, and possibly a video resolution/refresh issue.

Mudskipper
-----------------
Groucho said it best- "A four year-old child could understand this!
Quick! Run out and find me a four year-old child: I can't make heads nor tails out of this!"

 

[msmindy1]

mudskipper: that's just what I thought, that you could get past those errors also. I was thinking video also, but you can see the errors and the windows splash screen is fine. Then after I copied the vxd files to the system folder, I no longer see the errors, but still see the splash screen and hear a beep, then nothing. Would that be video? How could I change the video resolution? Can't get to safe mode. I tried also to get into the bios, it wouldn't let me.

 

[mudskipper]

Well, you would normally go into safe mode (because safe mode on win98 will only come up as 640X480 & 16 colors). From there, you can hit apply, reboot, and then reset them in normal mode.

If you can't get into safe mode, then this may not be the issue....

You say that you see the windows splash screen and THEN hear the beep? Does it do that when going into safe mode also?

Mudskipper
-----------------
Groucho said it best- "A four year-old child could understand this!
Quick! Run out and find me a four year-old child: I can't make heads nor tails out of this!"

 

[fluxvoovoo]

If you can't get into bios then you probably have an issue with either the cmos or processor (I gather from your post that the memory is at least passing it's initial check). If you can access the windows boot options try running a step-by-step w/confirmation boot (say yes to running a bootlog). Pay attention to where it stops booting (sounds kinda like it would be after it loads the windows drivers and passes the video over from the bios to the much more demanding windows GUI.) In any event...then reboot to c: if possible and type in the following: edit bootlog.txt If it is capable of this you will be presented with a very long and detailed view of the boot process. It will hopefully show you at the end what - where and when was the event that stopped the boot. Keep the possibility of Virri in mind also. This could have an effect on how you perform your format - restore. What make of computer is this?

 

[msmindy1]

This is a built to spec computer, AMD 1200, I think.

Never could get it to boot to anything, so I fdisk'd and formatted, reinstalled windows, etc. Running good now.

Thanks for your answers. I will keep them in mind for next time!

Mindy

 

[jmatt]

Thanks for letting us know Mindy