viaagp fails to load

Thanks for the reply. The way I have transferred this system was exactly
what you described; repair install followed by MB chipset driver
installation. All the P4C800 functionality appears to be good, this viaagp
thing just bugs me because its not quite right.
BTW, I do find mobo's that I like; they occasionally die a dreadful death
and require replacement and I move the disks to preclude reinstallation of
all the application software that has built up over the years. Otherwise I
would be tempted to do a fresh install and lose this viaagp thing entirely.

Ron

"Mercury" <me DeleteThis @spam.com> wrote in message
news:d2tttl$e93$1@lust.ihug.co.nz...
 > Do a system backup - ghost is a good idea, then:
 >
 > Do a repair install followed by re-installation of chipset drivers, other
 > drivers, servicepacks and critical updates.
 >
 > If you upgrade the mobo, you need to do a repair to cause the PNP hardware
 > detection to rerun in full.
 >
 > I suggest u find a mobo you really lke and stick with it.
 >
 > If you hack the services in the registry you may live through it, but this
 > is error prone and may result in a dead system. A repair is a no brainer,
 > just make sure you have raid drivers on hand and feed them in via f6 if
 > needed.
 >
 > The P4C800 is a very good board...
 >
 >
 >
 > "no_one" <no_one DeleteThis @earthlink.net> wrote in message
 > news:hpn4e.699$An2.205@newsread2.news.pas.earthlink.net...
  >> I get this message in the system section of the event viewer: "The
  >> following boot-start or system-start driver(s) failed to load:
  >> viaagp".
  >> I have an ASUS P4C800-E deluxe motherboard and an NVIDIA Geforce4
  >> MX420 AGP video card. The Boot disk has been transferred from a previous
  >> ABIT motherboard with VIA 4 in 1 drivers. I have performed repair
  >> installs on the OS sveral times over the past year as the motherboards
  >> have changed several times. Am I correct to assume that this is a
  >> hangover from the ABIT install? What can I do to remove the attempt to
  >> start this driver; I don't see it under component services. I do see
  >> several calls in the registry referencing viaagp and viaagp.sys
  >>
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: viaagp fails to load 

no_one wrote:
 > Thanks for the reply. The way I have transferred this system was
 > exactly what you described; repair install followed by MB chipset
 > driver installation. All the P4C800 functionality appears to be
 > good, this viaagp thing just bugs me because its not quite right.
 > BTW, I do find mobo's that I like; they occasionally die a dreadful
 > death and require replacement and I move the disks to preclude
 > reinstallation of all the application software that has built up over
 > the years. Otherwise I would be tempted to do a fresh install and
 > lose this viaagp thing entirely.

I suggest you do that clean install. The viaagp is a remnant of chipset
drivers from old setup. Possibly you could just uninstall it from device
manager, then delete the viaagp.sys from harddrive. But then again, there
are probably other drivers lying around, and maybe some even get loaded at
bootup totally unnecessary.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: viaagp fails to load 

In article <Twv4e.727$lP1.259@newsread1.news.pas.earthlink.net>, "no_one"
<no_one.TakeThisOut@earthlink.net> wrote:

 > Thanks for the reply. The way I have transferred this system was exactly
 > what you described; repair install followed by MB chipset driver
 > installation. All the P4C800 functionality appears to be good, this viaagp
 > thing just bugs me because its not quite right.
 > BTW, I do find mobo's that I like; they occasionally die a dreadful death
 > and require replacement and I move the disks to preclude reinstallation of
 > all the application software that has built up over the years. Otherwise I
 > would be tempted to do a fresh install and lose this viaagp thing entirely.
 >
 > Ron
 >

I have no idea if this will help, or is even on the right track.
You could have a look around for info on this. Assuming the VIA
thing is a startup item. If the VIA thing was an ordinary driver
that was triggered by the presence of enumerated hardware, I
doubt you would be seeing it right now.

(Keywords: MSCONFIG - System Configuration Utility -
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run )

<a style='text-decoration: underline;' href="http://groups.google.ca/groups?threadm=e1ZPy7DxEHA.2568%40TK2MSFTNGP11.phx.gbl" target="_blank">http://groups.google.ca/groups?threadm=e1ZPy7DxEHA.2568%40TK2MSFTNGP11.phx.gbl</a>

As the thread suggests, the uninstaller is the first thing to try.
Manual alteration of the registry or system files is just
asking for trouble - if you have had experience and success
with doing stuff like that in the past, then go for it.

One reason for me suggesting this, is I'm not at all sure that
a repair install will remove any "startup items". The repair
install would likely assume a startup item is part of the
users applications installs.

Paul<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: viaagp fails to load 

The msconfig program (start, run, msconfig <enter>) lists all startup items.
You can selectively disable one or more and test out new settings. Check the
system and win.ini files for RUN= or LOAD= entries - these are unlikely.

In device manager (Start, ControlPanel, System, Hardware) you can click Show
Hidden devices on the view menu. It is often helpful to View / By Connection
to see currently non running devices. There may be many greyed out entries
(not running). In general, don't remove (press DEL key) them unless you know
the device is causing an issue. EG you may have a sony camera USB & 4 USB
ports. There could then be 4 occurrences of the sony camera USB connection -
1 for each port.

Report back...


"Paul" <nospam.DeleteThis@needed.com> wrote in message
news:nospam-0504051620510001@192.168.1.178...
 > In article <Twv4e.727$lP1.259@newsread1.news.pas.earthlink.net>, "no_one"
 > <no_one.DeleteThis@earthlink.net> wrote:
 >
  >> Thanks for the reply. The way I have transferred this system was exactly
  >> what you described; repair install followed by MB chipset driver
  >> installation. All the P4C800 functionality appears to be good, this
  >> viaagp
  >> thing just bugs me because its not quite right.
  >> BTW, I do find mobo's that I like; they occasionally die a dreadful death
  >> and require replacement and I move the disks to preclude reinstallation
  >> of
  >> all the application software that has built up over the years. Otherwise
  >> I
  >> would be tempted to do a fresh install and lose this viaagp thing
  >> entirely.
  >>
  >> Ron
  >>
 >
 > I have no idea if this will help, or is even on the right track.
 > You could have a look around for info on this. Assuming the VIA
 > thing is a startup item. If the VIA thing was an ordinary driver
 > that was triggered by the presence of enumerated hardware, I
 > doubt you would be seeing it right now.
 >
 > (Keywords: MSCONFIG - System Configuration Utility -
 > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run )
 >
<font color=purple> > <a style='text-decoration: underline;' href="http://groups.google.ca/groups?threadm=e1ZPy7DxEHA.2568%40TK2MSFTNGP11.phx.gbl</font" target="_blank">http://groups.google.ca/groups?threadm=e1ZPy7DxEHA.2568%40TK2MSFTNGP11...x.gbl&l</a>>
 >
 > As the thread suggests, the uninstaller is the first thing to try.
 > Manual alteration of the registry or system files is just
 > asking for trouble - if you have had experience and success
 > with doing stuff like that in the past, then go for it.
 >
 > One reason for me suggesting this, is I'm not at all sure that
 > a repair install will remove any "startup items". The repair
 > install would likely assume a startup item is part of the
 > users applications installs.
 >
 > Paul<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: viaagp fails to load 

BINGO! I was not aware of the "hidden device" view under the Hardware
window. I found the entry for Via AGP Bus Filter and removed it. Reboot
and no error! It was only a nit, but I figured that it couldn't be good to
always fail to load something.


Thanks again

Ron

"Mercury" <me RemoveThis @spam.com> wrote in message
news:d2vg9k$gdb$1@lust.ihug.co.nz...
 > The msconfig program (start, run, msconfig <enter>) lists all startup
 > items. You can selectively disable one or more and test out new settings.
 > Check the system and win.ini files for RUN= or LOAD= entries - these are
 > unlikely.
 >
 > In device manager (Start, ControlPanel, System, Hardware) you can click
 > Show Hidden devices on the view menu. It is often helpful to View / By
 > Connection to see currently non running devices. There may be many greyed
 > out entries (not running). In general, don't remove (press DEL key) them
 > unless you know the device is causing an issue. EG you may have a sony
 > camera USB & 4 USB ports. There could then be 4 occurrences of the sony
 > camera USB connection - 1 for each port.
 >
 > Report back...
 >
 >
 > "Paul" <nospam RemoveThis @needed.com> wrote in message
 > news:nospam-0504051620510001@192.168.1.178...
  >> In article <Twv4e.727$lP1.259@newsread1.news.pas.earthlink.net>, "no_one"
  >> <no_one RemoveThis @earthlink.net> wrote:
  >>
   >>> Thanks for the reply. The way I have transferred this system was
   >>> exactly
   >>> what you described; repair install followed by MB chipset driver
   >>> installation. All the P4C800 functionality appears to be good, this
   >>> viaagp
   >>> thing just bugs me because its not quite right.
   >>> BTW, I do find mobo's that I like; they occasionally die a dreadful
   >>> death
   >>> and require replacement and I move the disks to preclude reinstallation
   >>> of
   >>> all the application software that has built up over the years.
   >>> Otherwise I
   >>> would be tempted to do a fresh install and lose this viaagp thing
   >>> entirely.
   >>>
   >>> Ron
   >>>
  >>
  >> I have no idea if this will help, or is even on the right track.
  >> You could have a look around for info on this. Assuming the VIA
  >> thing is a startup item. If the VIA thing was an ordinary driver
  >> that was triggered by the presence of enumerated hardware, I
  >> doubt you would be seeing it right now.
  >>
  >> (Keywords: MSCONFIG - System Configuration Utility -
  >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run )
  >>
<font color=green>  >> <a style='text-decoration: underline;' href="http://groups.google.ca/groups?threadm=e1ZPy7DxEHA.2568%40TK2MSFTNGP11.phx.gbl</font" target="_blank">http://groups.google.ca/groups?threadm=e1ZPy7DxEHA.2568%40TK2MSFTNGP11...x.gbl&l</a>>
  >>
  >> As the thread suggests, the uninstaller is the first thing to try.
  >> Manual alteration of the registry or system files is just
  >> asking for trouble - if you have had experience and success
  >> with doing stuff like that in the past, then go for it.
  >>
  >> One reason for me suggesting this, is I'm not at all sure that
  >> a repair install will remove any "startup items". The repair
  >> install would likely assume a startup item is part of the
  >> users applications installs.
  >>
  >> Paul
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: viaagp fails to load 

no_one wrote:
 > BINGO! I was not aware of the "hidden device" view under the Hardware
 > window. I found the entry for Via AGP Bus Filter and removed it. Reboot
 > and no error! It was only a nit, but I figured that it
 > couldn't be good to always fail to load something.

It's very good that it didn't load, as the driver was totally inappropriate
for the system.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: viaagp fails to load