Sign in with
Sign up | Sign in
Your question

Win2k Pro takes 10 minutes at splash screen

Last response: in Windows 2000/NT
Share
Anonymous
a b \ Driver
March 1, 2002 4:11:04 PM

Right after I install the VIA 4-in-1 drivers and Direct X 8 (not sure which one is causing the problem) Windows 2k will take 6 minutes or more to get past the win2k splash screen where the blue bar loads.

Anyone know whats going on?

<A HREF="mailto:cdm_ipgamer@hotmail.com">cdm_ipgamer@hotmail.com</A>
March 1, 2002 11:08:42 PM

Try looking at speedy boot stuff <A HREF="http://www.geocities.com/btvillarin" target="_new">here</A>. I got 2K and XP boot in 30(+/- 5) seconds, using the same thing got 98se boot just over 20 seconds. All boots calculated from beep till usable desktop.

<font color=red>Handsome A7V133 looking for long term relationship with a XP CPU. Prefer non smoker.</font color=red>
March 2, 2002 1:09:18 AM

Extra Info:

Could be a problem because of the VIA drivers.

According to John Gatt from the VIAARENA Team:

<font color=purple>"All the STD VIA drivers are in W2k SP2 so you dont have to install them on most VIA chipsets with SP2 the only time you will is if you are using a NEW chip set like P4X266 or KT266A and it is only the INF file you need to install our KT333 will need the IDE drivers too to support ATA133.
Some people find the VIA drivers Faster than the STD ones in SP2 but as thay are the same drivers as in the 4 in 1's I dont see how the only newer driver you can get for it in the IDE 3.14 driver.

So no you don't have to but you can if you want."</font color=purple>

I found his comment on this <A HREF="http://forums.viaarena.com/messageview.cfm?catid=3&thre..." target="_new">page</A>.

I've installed both DirectX 8.0a and 8.1 on many systems with Win2K in the past ... so I'd have to hazard a guess and suspect the VIA drivers are causing the problem. Unless you accidentally installed the wrong version of DirectX, and picked up the Win9x files.

If you are not using ATA/100 hard drives, and the VIA drivers are causing you problems ... there are a couple of choices you can make. One would be to try an older version of the VIA drivers, which can be found on this <A HREF="http://www.viaarena.com/?PageID=2" target="_new">page</A>. The other is to just use the native Windows drivers in Service Pack 2, which will support ATA/66.

In the meantime, to correct the problem, you might try booting to a Command Line (type F8, when Windows normally begins to start during the boot) and select "Last Known Good Configuration".

If this doesn't work, try to remove the drivers with Add/Remove Programs, preferably in Safe Mode. Then reinstall Service Pack 2.

Note: If you installed DirectX <i>before</i> you installed the chipset drivers, that could also have caused the problem.

What kind of information do you see in thie Event Viewer, under "Application" and "System" after Windows finally reaches the desktop? (Right-click My Computer, and choose Manage from the menu.) And are there any obvious conflicts in the Device Manager, such as with the IDE controller?

By the way ... you never mentioned which version of the VIA drivers you installed, or the make of your mainboard. The type of board, the chipset, and the brand can be critical to discovering the source of a problem, even if it is driver-related. Not all hardware responds the same way to the same software.

Let us know how it goes!

Toejam31

P.S. By the way, AndrewT ... excellent idea. :smile:

<font color=red>My Rig:</font color=red> <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new"><font color=green>Toejam31's Tantalizing Tantric Toy</font color=green></A>
<font color=red>Second Rig:</font color=red> <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=15942" target="_new"><font color=green>Toey's Dynamite DDR Duron</font color=green></A>
____________________________________________________________

<font color=purple>"Procrastination on your part does not constitute an emergency on my part."</font color=purple>
Related resources
!