Kyro...(This time its personal!!!)

G

Guest

Guest
Ok, i remember some news going around a while back that the you couldn't run Kyro II on a 440BX chipset for some reason. I wan't to ask if any of you can point me to some info on that.

(I would like to sate here- for the record - that i realize the AGP 1.0-2.0 mismatch problem, but... you'll see)

First, let me start by confirming the rumor:
A friend of mine got a Kyro II 64MB (Hercules). We installed it in his 440BX mobo (it was a stock DELL so i didn't bother to figure out the details). Anyway, everythin's cool, chugging along, getting semi-good scores on his PIII600. Image quality is exceptional, and we are getting exceptional crispness with that 400Mhz Ramdac. Everythin's fine, QIII is kickin some serious arse.. and then we get to the ultimate test: Tribes 2. Load up Tribes 2-ok. Allright-logon to the servers-ok. The player model loads up- oh my god....wth???? the whole screen starts to tear at random places. Ok, now imagine in your semi-twilight zone complacency, a picture of unimaginable pain for a gamer: an otherwise normal screen (in fact the left edge was perfectly straight) torn to shreds in random places (the right edge has some semblance of straightness, however, at random points the line just stretches out almost off the screen and then fades back in). To give you an example, an artists rendering:

---------
---------
-----------
----------
---------
-----------
----------
---------
---------
----------
---------

(Help? Y/N? Sorry....)

Anyway... so you can play the game and everything except for the horrible tearing (its what i call it... don't kill me). I freak, i donwload 3 sets of drivers, try them all, try them all again. I go to the mobo BIOS and mess with everything down to the freaking AGP aperature. No go. So no more Tribes 2. We leave the card in there. A few days later- the system starts to crash. A week later- byebye comp. The motherboard is dead, no post no nothing. Ok, we order a stock replacement a gratis(free) by DELL. We assemble. Put the card in. The board posts-ok. Windows boot menu (safe mode etc) loads up- Holy SH@T... artifacts, tearing etc. The Kyro II is gone, we replace it with a TNT2-M64 - everything is back to normal. Now if i neglected to mention this- the computer had about a years worth of faithful service in it before we started messing around.

Conclusion: Kyro II fragged my friends 440bx motherboard.

In an after test i stuck the card into an old K6-2 i dug up which had an Ali chipset (AGP 1.0 i believe). Everything ran fine. I didn't have a chance to run tribes 2 cuz the comp sucked too much but everything else seemed cool.

My theory- Kyro II is compatible with AGP 1.0 but not with the BX and possibly other 440 base chipsets.
***--------------Important---
Anyone wanna take a whack at that?
I'm also interested in knowing what you guys think of or have experienced with Kyro II?
And i am very much interested in reading any info you can point me to on this issue.

Thx.

😱 <font color=blue>I for one run Quake 3 on a P133(No MMX)</font color=blue>I have no affiliatioin w/ Intel
 
Don't know if this will help but you might try this <A HREF="http://www.3dspotlight.com/tweaks/kyro2/index.shtml" target="_new">Kyro II tweak guide</A> and this <A HREF="http://www.3dspotlight.com/tweaks/tribes2/index.shtml" target="_new">Tribes 2 tweak guide</A> both at www.3dspotlight.com.

<b>We are all beta testers!</b>
 
I've read those, but thanks anyway. I appreciate the help, but i don't think Tribes 2 is what caused the massive motherboard failure. If you've got any info linking the Kyro II to the BX, that would be REALLY great. (Cuz i've still got the card on my hands and i have no clue as to what to do with it!!!!)

Although i gotta say Tribes 2 had to have been a contributing factor.... Wonder why it was the first to create glitches..... hmm...

😱 <font color=blue>I for one run Quake 3 on a P133(No MMX)</font color=blue>I have no affiliatioin w/ Intel<P ID="edit"><FONT SIZE=-1><EM>Edited by AlphaSan on 10/30/01 10:33 PM.</EM></FONT></P>
 
Well I don't think anyone has suggested that Kyro II actually breaks 440BX boards. I seem to remember some site mentioning instability with that mobo and his review sample of Kyro II but the problem you've suffered is certainly a one off AFAIK. I hear allot of bug reports for Kyro II and I've never heard a story like yours (not saying I don't believe you, just saying what happened to you is very unusual) nor have I seen any real connection between problems with Kyro II and using a 440BX mobo. The fact that it worked well in one system and not in another doesn't neccasarily point to incompatabilities with that particular mobo chipset. For instance I sold a Radeon LE to a friend recently and while the board was fine for me (VIA mobo) it was nothing but trouble for him (ALI mobo). That doesn't mean that Radeon doesn't work with that particular ALI chipset, it could be other stuff like the soundcard, modem, ect etc causing conflicts with the graphics card. All I can do to help off the top of my head is say make sure you disable any sort of caching in the mobo BIOS (Video BIOS cachable, System BIOS cachable ect ect all disabled). Also I think there's a option in the BIOS that needs to be set to UC from UWC or was that UCW??, I can't remember. I suggest taking a look at the Kyro FAQ here (http://www.paraknowya.com/specials/faq/index.shtml) and if that doesn't help go to www.paraknowya.com and post a question in there forum (its a PowerVR specific forum so you'll get better help there then you will here).
 
Been there, and trust me: when i say i've messed with the Bios i've MESSED with the bios. I've tried every available setting (although the bios is not very comprehensive, something you find with dell computers). Naw, but litterally i think i have good reason to conclude that the Kyro has a major problem with the BX, it fried one mobo (which between the strange visual glitches and the timing of the mobo's death is 99% fact, no other changes were made at the time) and had major problems with another. Following that it ran fine with the ALI. I think there is a correlation here. It may not be the BX specifically but there sure as hell is something goin on here.

As for my hastiness, well i saw a little while ago in a post or a news article (god only knows where) that some dude was in the same situation i was (i think he traced it down to a fried north bridge?). BX and all.


😱 <font color=blue>I for one run Quake 3 on a P133(No MMX)</font color=blue>I have no affiliatioin w/ Intel