can't get AGP to install from 5.13A driver suite

alvinmoneypit · #1 (**permalink**) 22-11-07, 01:31 AM

So I'm having the dreaded infinite loop with my video card and I'm checking things. I see that my AGP controller says "VIA to AGP controller" but I check the driver details tells me Microsoft from 2001.

I figure this is a problem so I get out my downloaded Hyperion Pro 5.13A package and load it, but when I get to screen 3 where it tells me what is actually there I see no AGP driver, just SATA, PATA, RAID, and one other. So I use my zip program and browse the contents of the Hyperion package and see the AGP folder in there.

I decide to go for it and set just that folder on the desktop expanded with my unzipper.

I go to xp Device manager and update the driver with one out of the "wndows xp folder buried 2 folders deep in my extracted files, but I'm wondering because I saw a tech note at the viarena site that says the agp driver for xp has the "NT" at the end of the name just before the extension.

So I go ahead and reboot, I tried to log onto my Catalyst control center for the card and it crashes where it normally does, in the "3D" section. However, I reboot again and this driver appears to be working fine as I type on the internet which I could NOT do earlier with "full hardware acceleration" on, albeit I haven't tried any games or hardcore 3D operations yet.

I checked device manager again and it now says "VIA to AGP2.0/3.0 controller and has a 2003 date on the details screen, but I don't think I'm running AGP 2.0 or 3.0 on this card, at least my motherboard tech specs aren't saying its 2.0.

I tried to upgrade to the driver I found in the folder above the one which says, "driver" in the 'agp' folder I extracted from the hyperion installer because it had the "...NT.dll" ending in the name so I thought, "this must be the correct driver", but windows xp refuses to recognize it as such.

So, I'm wondering a couple things:

1) How can I install the correct AGP driver properly when the installer refuses to list it in the installation process?

2) Will running this "2.0/3.0" AGP driver cause me problems at some point when I'm not running an AGP 2.0 MB?

I already looked at the "staying out of the loop" instruction and have done most things there, some things were ruled out because I had done them in the past at some point.

Thanks for all responses.

al

Sosgez · #2 (**permalink**) 22-11-07, 08:40 AM

I have a similar problem. I want to install an NT AGP driver, but there is no *.inf or sys file, and the other OS versions won't install, eg XP, Win2000.
The release notes for HyperionPro 5.13A list NT4 as one of the supported OS's, but the required files are not present.

alvinmoneypit · #3 (**permalink**) 23-11-07, 05:56 AM

I see nobody jumped in to help us.

This remains frustrating since I had a similar problem with my old motherboard running NO SATA, a KT 266 chipset with older drivers on a Gigabyte MB and the same video card. I worked and worked on it. Thought it might be a driver conflict with the modem then. Never did resolve it. The tech at the shop fixed it over night with no parts charges. They never would tell me what they did, but I bet it was simple. On the other hand, I took it to a shop before hers, and they could NOT fix it but could only reinstall XP - but those guys were preoccupied with their server business. She is now out of the bidness, the woman who got it working, so what am I left with?

candle_86 · #4 (**permalink**) 23-11-07, 06:58 AM

if you have AGP4x or 8X that is the right dirver. AGP4X is AGP 2.0 and AGP8X is AGP 3.0, so there isnt a problem there

alvinmoneypit · #5 (**permalink**) 23-11-07, 04:11 PM

thanks, then that is at least its the right class of driver.

I wonder if somehow windows is not reporting that I have AGP 8x even though its represented correctly in the BIOS and its found in Everest reporting tools? I have no idea how these installation programs work, but I see that is one possibility. If so, then the problem is with Windows why my card doesn't work.

A guy called "The guru of 3D" has written/hacked some of these vendor drivers for both Nvidia and ATI video cards he says they work better than the original drivers and I downloaded the one I need but I was thinking if my system is not seeing my AGP at all, then this wouldn't help either. I haven't tried his driver yet.The guru of 3D

Chivo · #6 (**permalink**) 26-11-07, 07:24 AM

Do you have an exact link to the driver? Can't seem to find it

Thanks!

alvinmoneypit · #7 (**permalink**) 26-11-07, 03:43 PM

Here is the link to the omega drivers. Modded drivers. You should have browse modded drivers. They also have the latest ATI drivers as well as some VIA drivers.

tcsenter · #8 (**permalink**) 27-11-07, 07:11 AM

Quote:

Originally posted by: alvinmoneypit
So I'm having the dreaded infinite loop with my video card and I'm checking things. I see that my AGP controller says "VIA to AGP controller" but I check the driver details tells me Microsoft from 2001.

This probably was not the date of the AGP driver. There are actually two drivers installed for the VIA AGP controller. One is the PCI bus driver supplied by Microsoft, the second is the actual AGP driver (whether supplied by Microsoft or VIA).

The driver tab of device properties will report the provider and date information for the PCI bus driver, which is always provided by Microsoft and dated 2001. If you want to know the date of the actual AGP driver, you have to click on Driver Details, then select the driver listed under PCI.sys, which should have been UAGP35.SYS if you have XP with SP2 installed.

UAGP35.sys is the Microsoft Universal AGP Driver that was first released with SP2. VIA discontinued its own AGP driver in favor of the UAGP driver from Microsoft. This is why VIA has not released a newer AGP driver for XP/2000 since 2003. The only VIA AGP driver to receive any updates since 2003 is for Windows 9x (98/ME). This is also why the Hyperion 4-in-1 will no longer install the VIA AGP driver for XP/2000 on Northbridges that are covered by the UAGP driver (PCI DEV_ID = B198).

KT600 should be fully compatible with UAGP35.sys. There is some uncertainty whether Microsoft's AGP driver is better or more stable than VIA's own AGP driver. There have been reports that the VIA driver was better, but most have reported that there is no apparent difference or even that the UAGP driver was more stable.

I would recommend the UAGP driver because ATI and NVIDIA almost certainly make driver programming decisions on the assumption that any VIA AGP Northbridges covered by the UAGP driver would be using it instead of VIA's. But if the VIA driver does work better in your case, you can't argue with success.

There also seems to be an unusal number of 'issues' cropping up with ATI AGP cards whenever ATI releases a new driver, which ATI keeps saying they will resolve in the next driver or are "currently investigating" (for over a year now). The usual ATI recommendation to 'please install one of our older drivers that worked just fine' is getting a bit old if not insulting.

alvinmoneypit · #9 (**permalink**) 28-11-07, 05:58 PM

Hi Man,

I looked all over in device manager for the "UAGP35.sys" driver and I didn't see it listed in PCI Bus, PCI bridge to pci controller, I did see a reference to "B198" though in the associations of one of the devices. I also found it in system32 folder so I know its there, I'm just not sure if it's hooked up correctly.

Could you tell me exactly where to look again?

thanks.

al

Engine · #10 (**permalink**) 29-11-07, 04:07 AM

On a fresh install with a KT600 chipset I had nothing but issues with the 5.13. Went back to the 5.10 then the 5.14 came out. I deceided to give it a try, what a difference it made all for the better. I also manually loaded the AGP driver. I also have the latest ATI driver.