problems with latest 4-in-1 drivers

qwex

Member
Oct 17, 2000
180
0
0
I just installed the latest VIA 4-in-1 drivers, (all 4) in hopes that it would fix the ddhelp.exe crashes. well, now I can't get into windows (Win98SE). the desktop begins to load, then a thin horizontal light green line appears on the top of the screen. I can move the mouse around, but that's it. I tried rebooting a few times, same thing. I have a kt7-raid with an athlon tbird 900...I tried booting into safe mode to uninstall the drivers, but there's no uninstall option...any help?
 

holdencommodore

Golden Member
Nov 3, 2000
1,061
0
0
You should be able to uninstall the drivers - just run the VIA 4-in-1 driver setup again, but this time select uninstall...
Have you tried reinstalling the video card drivers - these have to be reinstalled every time the VIA AGP driver is installed - and this driver is included in the 4-in-1 driver package...
Good Luck! :)
 

qwex

Member
Oct 17, 2000
180
0
0
I can't reinstall the video drivers (radeon 32meg DDR) because I can't get into windows...if I boot into safe mode I can, but then I can't access the DVD drive to install them. I'll try running the setup program again though
 

siroutbak

Junior Member
Oct 29, 2000
12
0
0
I had the same problem with my system, try booting into safe mode (hit F8 before it starts to load windows) and do this...

http://www.apushardware.com/faqs/kt7faq/faqboot.html

I get a blue screen with a green line at the top after restarting.
Tape detection seems to cause this problem. Removing MSBackup will not solve this problem in itself, and so it is necessary to remove, or preferably rename, the following files.

[C:\windows\inf ]
pnpwfdc.inf
pnpwide.inf
pnpwtape.inf
pnpwppt.inf

[C:\windows\system\iosubsys ]
drvwq117.vxd
drvwppqt.vxd
drvwcdb.vxd

See also "Windows 98 hangs or reboots during startup or at desktop!" below.

Windows 98 or Me hangs or reboots during startup or at desktop!
This again has been reported as being due to a problem with the Seagate device driver files. One user who is a small system builder has reported that renaming drvwppqt.vxd and drvwq117.vxd solves the problem. They experienced the problem on motherboards from seven different manufacturers and found the above solution to be successful.