PDA

View Full Version : Second problem new computer


PhilSlick
11-02-2002, 04:11 PM
Ok, my computer just froze, so I'm still having major problems. Anway, I just built a new computer for my first time and am thinking that this may be the last time. I seem to be having one problem right after the other. I have been getting help from someone thankfully, from the boards, and I'm very grateful for it. Seems that now I'm having another problem though.

I formatted the new HD I have and installed Windows without a problem, I think. I'm not sure if I'm leaving out a step when I do it or if it suppose to be like this, but when I check the space on it in Windows, 80GB HD, it says that I have 74.5GB for the max capacity. Is this normal or is there something I'm doing wrong when I format it? I have never done this before so I'm not sure if I need to partition it differently or something. I just go to fdisk and then go from there. That's really not the main problem though.

Here's the problem. After I install Windows, I try to load the motherboard drivers. When I try to go into setup, or the auto run kicks in, I get this error: The MENU.EXE file is linked to missing export OLEAUT32.DLL:VarNot." I then tried to go into the files and use the individual setup's. After I did one setup I ended up with startup errors, something like VNS.vxd and DNS.vxd errors or close to that. This has been the most complicated part and I'm not quite sure what to do from here. I appriciate any help that anyone can give me. Thank you very much.

Win98
1.8GHZ P4
ATI Radion 8500LE
256MB RAM
80GB WD HD
P4S5A mainboard

James Bond 007
11-02-2002, 05:44 PM
Can you got into safe mode or are you attempting to do this from dos?If you can get Windows to run the try this go into the control panel and open the system icon click on the tab that says device manager expand all, by clicking on the + symbol, are there any icons with an exclimation point (should be a yellow circle with a exclimation point).This would indicate hardware conflict.If there is I can explain the rest of the procedure later.

PhilSlick
11-02-2002, 07:02 PM
The last post I meant to put Here's the main problem not here's the problem as obviously there are two on there. Oops.

Well, at first I thought that this was a repeat post from the other one, then realized it wasn't. I can get into Windows with some minor problems which I will explain in a moment. Actually, maybe I should explain it now just in case I have to reinstall Windows once again.

Once I tried to install the stuff from the motherboard disk I got the error as mentioned. After I did that then I tried to install something else. After I restarted the computer I got these errors, exact not close to this time: unable to locate vnetsup.vxd, vredir.vxd, dfs.vxd. After Windows started up, just before it asks for the password, I then got this missing file error, msn32.dll. Hopefully these can be replaced without reinstalling Windows again, but I'm not quite sure how to do that.

Ok, now the conlfict thing. When I open up device manager I have a question and a !. The device is PCI multimedia audio device. But messing around, don't know if I fixed it, and installing some stuff off of the CD, I think that the problem is fixed. I know the conflict is no longer there. Thank you for the suggestion of checking that though. I would have never thought of doing that.

Now if I could only install the rest of the drivers off of the CD and get rid of the problem above, I think everything will be ok. I better knock on some wood first as I seem to still have one problem after the other. I tried to restore the registry, to see if it would get rid of the above problem, with the vnetsup.vxd and such, but instead I just found that I know have to reinstall the ATI drivers and the Direct X drivers. Not a big deal though as long as I don't have to reinstall Windows. Oh please tell me that I don't have to do that. I don't know though as again it's not recognizing the full 80GB. Again, I still don't know if this is normal or not though. Thanks again.

Budfred
11-02-2002, 07:11 PM
It is normal for it to see the 80gig hard drive as less. While the hard drive companies measure capacity one way, Windoze does it another. Basically it has to do with how a kilobyte is really 1024 bytes and the hard drive makers measure based on how that adds up, but Windows measures in terms of what it can actually use and this is always less.

Any way, something like that. I am not sure of the details, but there was recently a couple of threads about this issue, so you could search for them if you want to know more. The main thing is: don't worry about it.

Budfred

ranchdog
11-02-2002, 07:16 PM
Due to the differences in allocation tables

the full amount rated of a Harddrive will

not be reached.

You got lucky on this one as some 80Gig units

will work out as 72 Gig with the allocation

tables. Bytes, Sectors, etc.

Keep working on the drivers problems,

everything will smooth out with patience. ;)


RD.

PhilSlick
11-03-2002, 12:24 AM
I hope so. I have the sound and video drivers down now by the looks of things, but my main concern is now those errors that I get at start up. If I knew how to replace these and get the rest of those drivers loaded, as I seem to have some errors going on, then I think everything will be fine. Until then, I will be keeping the Asprin around.

PhilSlick
11-03-2002, 03:44 AM
Well, it looks like things are going much better. For once the Microsoft site actually had some good information. The errors that I was getting on startup seemed to be coming from the Client For Microsoft. Following the directions, I uninstalled Client and reinstalled it. Now no problem there. One more problem down.

It looks like the motherboard drivers aren't that important, at least not the ones that are remaining. It looks like some of the drivers did install, and could be what caused the problem with Client, while others are just for the modem and such. Some things that I don't need to worry about. Now all I have left to do is download all the updates for both Windows and the DVD ROM, transfer the HD files, tomorrow, and I should be good to go. Thanks to all who have helped me and have given me ideas. I wouldn't have made it this far without your help. I was stuck for some time. I'm sure that I will be back asking for help as I still have to transfer the files over from the old HD, as I stated before. If I have problems with that, or more like when as things have been going, then I will be back asking for help. Probably won't be on this same board though as it's a different subject, but none the less, I will be back. Thanks again.

crasher
11-08-2002, 12:52 PM
Hey, Philslick.

I have the same exact message when booting up.
"unable to locate vnetsup.vxd, vredir.vxd, dfs.vxd. After Windows started up, just before it asks for the password, I then got this missing file error, msn32.dll."

What did you do?

PhilSlick
11-08-2002, 03:46 PM
Well, other then this driving me crazy at first, I actually think I was able to find the answer on the Microsoft's pages. Surpised me. Yoda74 also answered this problem on the clean 98 thread so I'm just going to borrow from him since it's quicker to ctrl c then it is to type everything again. Thanks Yoda74

Allright do this:
Click the Start button, point to Settings, and then click Control Panel.
The Control Panel window appears.
Double-click the Network icon.
Click Client for Microsoft Networks to highlight it.
Click Remove.
Click OK.
You may receive a message that the network configuration is incomplete.
Click Yes.
Click the Start button, click Shut Down, click Restart, and then click OK.
Click the Start button, point to Settings, and then click Control Panel.
The Control Panel window appears.
Double-click the Network icon.
Click Add.
Click Client.
Click Add.
Click Microsoft from the Manufacturers list.
Click Client for Microsoft Networks.
Click OK.
Click Apply.
Click OK.
Click the Start button, click Shut Down, click Restart, and then click OK.

That should take care of it