That MS AGP4x VIA patch...

[antareus 0]

Tried the patch out a bit with games, it made a nice difference in games, Tribes was nauseatingly fast indoors (either that or it was because I just woke up ) and I tried UT as well, I didn't see much improvement. Afterwards, however, I hard locked while using Internet Explorer, so I reverted back to Normal performance settings on my A7V. Any comments?

[JediBaron 0]

Mine worked too, but then I pushed my d3d really hard with the new Venom demo 1024x768-32bit and it went kuput. I had no problems at all with any OpenGL program. I also had to set mine back.

As for luckups in ie, are you using a usb mouse? There is a known issue with the AGP 4x and MS Optical mice in IE on the A7V. It affects both Win9x and Win2k (ME isn't even worth mentioning, I'm just going to pretend that it doesn't exist and maybe it will go away The 9x OS took a HUGE step back with that incarnation.) Maybe that has something to do with your lockup.

[antareus 0]

Crikey, you're right, I'm gonna look stuff up on it...I have my Explorer hooked up to the USB port, seems smoother than PS/2, but can you tell a difference? Not sure whether I'd want a superslick mouse cursor or higher FPS.

 

Thanks.

[tristan777 0]

u could use a program like PS2Rate and kick the refresh rate up, and u prolly wont really notice the difference from usb. i don't. except for the fact that my mouse works, and my computer doesnt crash.

[JediBaron 0]

Cool, it's not just my 21 A7V's I've never tried going back to the PS/2 port with mine. The truth is since it only happens under those conditions (one more condition that I forgot to mention - you have to be wheeling in ie), I'm assuming that it's a really small timing flaw in the USB when you change to Optimal Performance. It seems to be such a small error that possibly just later releases of Intelipoint might just filter it out, or perhaps a new Via USB filter will. But the most likely candidate to fix it will no doubt be a BIOS upgrade, so till then . . . Normal it is I've never had any of my 21 A7V's lockup from the mouse in Normal mode in any OS.

I have seen some obscure references to the problem possibly being caused because no PS/2 mouse is plugged in. I find this to be highly unlikely because I assume that Win9x and Win2k doubtfully use the mice in the exact same way. So I'm realitively sure that it's a hardware glitch. I've never gotten the wheel to lockup in any other app but IE, but no other app gets as much wheel action so it's hard to say. On my Win98SE systems, though, I did note that it accured a lot more often. Basically it seemed to average out to 3-4 hours of IE use (no reboots of course), yet on my Win2k machine it would only happen after like 20 or more hours of IE use. Possibly the Win2k machine just limits the glitch better (or maybe it's just a lucky fluke ).

 

[This message has been edited by JediBaron (edited 01 November 2000).]

[tristan777 0]

21 A7Vs? hehehe. man wish i had 21 A7Vs. i would need a few houses to power them all though. hehe

 

i also don't like the fact that USB gets all slow and choppy whenever the computer's workin hard. it seems that whenever it's accessing the hard drive alot or something the mouse gets all choppy. i think my old serial mice used to do that to me too. anyway, i supose i'll stick to what works for me. that's ps2.

[JediBaron 0]

Ya know, I've never noticed if the USB slows down during heavy IDE usage. I would think that it would be imperveous to any slowdowns like that being as the IDE and the USB are supposed to be tied into the bus on their own paths just like the AGP and memory are tied in on their own paths. This may mean that the chipset is using the IDE route for the USB also, and that they're not seperate. Very strange indeed, I'm going to see if I can dig up any flowcharts from Via to see if that's the case. . .