viagart.vxd missing after VIA update

"Orson Cart" wrote in :

I have VIA chipset PC running 98SE. I read somewhere that the to get the
latest supported drivers for 98SE, one should install the VIA Hyperion
drivers 5.11A then 5.13A (but only the IDE component).

I use Via mainboards, but mine (ITX, MII12000) only need the v4.56 driver set
so I don't know about the later ones. If you hunt for an unofficial W98
service pack called "sesp21a-en.exe" you might find all the bussmaster
drivers you need. I found that with files in that thing (plus others from the
W98 install files) I could build a W98 core that didn't need the Hyperion
'4in1' driver set at all. Same might apply to you. If you can Ghost the OS to
a backup image file, try experimenting...

Take care with what you read, including this. Research your mainboard's
driver requirements, and get drivers as directly advised and sourced by Via.
They rarely suggest one set, then upgrade with part of another. You may have
seen some bad advice elsewhere. Even if you try something else (like that
unofficial upgrade) you need to start with the Via defaults so you know it
starts out working right. Latest driver is not always best, especially on an
older system...

So I installed 5.11A, but when Windows boots, get a text message
complaining that windows registry or SYSTEM.INI refers to this
device file blah blah
and the offending file is viagart.vxd

I've seen that file many times in the past, but weirdly it's not on my main
system now so clearly some things don't require it because mine works well.

It finally says hit any key to continue; when I do so, Windows will
proceed to boot, and seems to run. It is a hassle if I must hit
a key every time that I start the PC.
So why is VIA Hyperion driver not doing its job?

It might be. Check the system properties, examine for any warnings, or driver
details that mention files not found. If that's all apparently working
properly the Viagart.vxd call is just what it says it is, an unsatisfied call
from registry or INI file. Likely something removed the file but not the
call, which suggests that mixing driver installs might be a Bad Thing. There
may be other problems. Tf the earlier version works, stay with that. Try
copying huge files, and large sets of small ones. If the copy doesn't choke
itself into seizure, the odds are eveything is fine.

Can I find the reference to viagart.vxd and remove it?


Yes. Look for its name in SYSTEM.INI, if it's there, try putting a semicolon
at the start of the line it's on, and save the edit. Also, in the registry,
see if it is named under
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD, if so, export its
key to file so you can put it back at need, then delete the key.

I have VIA chipset PC running 98SE. I read somewhere that the to get the
latest supported drivers for 98SE, one should install the VIA Hyperion
drivers 5.11A then 5.13A (but only the IDE component).
So I installed 5.11A, but when Windows boots, get a text message
complaining that windows registry or SYSTEM.INI refers to this
device file blah blah
and the offending file is viagart.vxd
It finally says hit any key to continue; when I do so, Windows will
proceed to boot, and seems to run. It is a hassle if I must hit
a key every time that I start the PC.
So why is VIA Hyperion driver not doing its job?
Can I find the reference to viagart.vxd and remove it?

Also, check that it really IS viagart.vxd and not viagart.sys because if it's
'sys' then you likely need it, it's the AGP miniport driver. It comes with
the buss driver set, not the VGA driver set. To avoid confusion, always start
with Via's own direction for version used on a specific mainboard. Even if a
file from a later driver can help you gain something, you won't gain much,
and if you try to do it by mixing whole install sets, you basically risk
unleashing hell. Via may have changed their recommendations themselves at
times, but they always assume a driver set will be chosen once, for a clean
install, because who wants to try to cover eventualities they have no control
over? If you want to be sure it works, go with the same clean starting
conditions that they assume will exist.

In other words you might never be sure any of this works unless you're
willing to start over after getting their best direct advice and files.