Can i do better

[medianOCer]

NEO,

Thanks for the PSU history and etc. Interesting read.

 

Clay,

Heh, I wasn't attempting to pawn you off. I was merely

wishing you the best with the new board/rig.

[NEOAethyr]

I FINALLY figuered out why I'm having performance issues with my video card.

 

Of all things, I'm stuck on agp 2x mode :.

The max bandwith I'm reaching is 1149 right now, was reaching 1600+ some time ago but that got all messed up when I swapped drivers.

 

Not bad for an oc'ed agp2x bus :, reaching over 4x.

Still blows though, I need over 8x just to do certain things, stuff I don't do anymore like 120fps captures but hey I still want that ability.

That and certain things are getting dragged down a bit.

Yumebench is losing one hella lot of score.

 

GTASA, it's performance is quite good right now because of my driver.

Actually it's very good to say the least...

3dmark03, got 12k the other day , and yeah my system is still all messed so that's not my best, only clocked at 550 and 1100 .

I only got that by removing most of my tweaks and using the 3dmark03 profile built into the 8362 quadro driver.

Was a bit surprised to say the least....

Was running at 640x480 though, and dl'ing at the same time with getright though, so whatever, sloppy bench and low res.

 

My driver as is, is'nt the best performer that's for sure, stock driver does better in most areas, however some things are actually doubled in speed...

Probably from tweaking the old quadro2mxr back in the day...

 

AGP 2x :shake:

That blows.

I can't figuer it out either, agp drivers, display drivers.

Nothing fixes it.

I'm wondering if it's the new ver of windows I picked up.., win2k3 r2.

I'm gonna install 2kpro in a while.

That and I gotta take my rig apart, redo the gel on the cpu, redo the noth bridge, redo the enermax psu...

Also got that one cable to redo, and my fans, my tornado is whining, and the one 80mm in front is ticking :.

Got ringing in my ears again blah, because I was to lazy to fix all of it.

Some of my stuff is just to old I think, the tornado is from back in the day when the kt333 1st came out.

 

 

Anyways take a looky at my driver inf so far.

I don't expect you to use it though.

It's a wip, I just wanna show ya how much time I put in the darn thing, still going for a major overhaul ^^.

Lots of stuff to do yet.

Please don't distro it it though, I'm not ready for that.

Don't be scared by the disclaimer at the begining btw.

I'm only doing that so people are a bit scared to mess with it, I'll add the full ver of that later on.

It's there to freak people out a bit so they leave it alone.

[medianOCer]

Hmm, a tweaked display driver eh.

Would that be good for my FX5600

Ultra and worth giving a shot?

 

I'll DL it and take a gander at it,

thanks.

[NEOAethyr]

I can talk about my driver a bit more later on.

If you wanna install it, chnage the driver ver at the begining to what ver you thrown it over on, say to 82.12.

Change from 8.3.6.3 to 8.2.1.2, I think, somehtign like that(May be to many dots, you'll know)

 

Also since it's the latest driver I had to add new files, if it yells about missing files, just skip those, it'll be fine.

I have to figuer something out for that.

I was never expecting more files to be needed for the driver ^^.

Driver speed i good in some places, bad in others, however quality is top notch, no other driver will get you this quality that I can say for sure.

 

 

 

I've been messing around a bit.

I removed the enermax for now, because I noticed I had a ultra ata read error on one of my hd's , though I never saw any error in the my windows logs, so it must of happened out of windows.

Which is very odd, because that drive is'nt touched out of windows, except for startup, if I use it.

 

So before I removed the enermax I messed around with 505, trying to add my latest bios stuff to it to test dividors and the cpu name thing(which btw is still buggy, the name, dividors work better).

It was freaking out on me, corrupting my bios like no other, and modbin was freaking out too which is very odd..

 

I also tried the 121 bios, corrupted my stuff too..

Bad day lol.

 

Get this, my pmc flash chip, went bad on me for a min there, I could'nt flash to it at all.

I'm running on it now though oui .

 

Ok...

I added old code of mine to the bios, from the alpha bios, very old romsip mod(forgot one half of it too but it seems allright lol), also some other newer mods.

Changed up the defaults a tiny bit, flashed it.

Ran 270 memtest stable.

 

The bios is quick as heck, even though I'm using a slack romsip ver.

Hd quickness galoor, bandwith is not bad at all for this type of romsip it's very nice .

Also, no more warm boot issue for me at all.

 

Totally forgot to mod the bpl too....

 

I went into windows to check it at 266, which I have'nt actually done yet, with s&m.

When I went to do the idle tweak I noticed the reg was allready set!!!

 

This bios really boots like no other bios.

Has more supported cpu's then the newer bios'es(non mobile mp's!, more duron's as well(mp durons!).

Idle tweak built in.

 

Overall quickness is so much better, like I said bootup, no warm boots.

Hd speed, dvdrw speed.

Video playback speed!, skiping ahead in the video is seemless probably 90% of the time.

 

 

Next rev of my bios, gonna be based on 505.

I know why people had bad experiences with 505 though.

With it's stock romsip, it's a real pain to deal with for sure, totally screwed in alot of ways.

I can't blieve I got 280 gaming stable with that romsip long ago :, I know I had odd cmos saves though..., I had to use them just to boot it I can remember that.

 

 

Anyways if anyone wants to test out 619 ver's too when the time comes I'm all for it.

I can figure out if it's my romsip, or if it's the bios ver with that winbond then.

 

I love this 505 bios though, as long as the romsip is modded it's not a prob to deal with.

[Clay]

@Median: Aww... I know "Bro" I jus' like to pull yer' leg once inna' while.(Heh I hope ya' don't mind too much really. LOL) I need all the luck I can get. One of my buddies said the problem w/my board could be a leakin' cap but without a tester it's really hard sayin'.

[NEOAethyr]

Heh...

 

This bios thing is a major hassle right now :.

Still working with it though.

 

This is the best I come up with so far:

 

 

01 : 1 A ----Table 1

02 : 2 A |

03 : 2 A |

04 : 1 A /

05 : 2 X __Table X1

06 : 1 X /

07 : 1 Y ---Table Y1

08 : 1 Z __Table Z1

09 : 2 Z /

10 : 1 Y ---Table Y1

11 : 2 Z __Table Z2

12 : 1 Z /

13 : 1 B

14 : 2 B |

15 : 2 B |

16 : 1 B ----Table 2

 

 

Still confuses the heck out of me lol.

At least it works...

Well, lower bandwith by 100megs and less stable, but the good thing is, low timings are working.

So I do know it's partially wokring, must be my romsip it's self.

 

Anyways...

Screw that.

 

I'm getting some more heatsinks tomarrow.

I guess my buddy even has a at64 939 stock heatsink for me to use on my north bridge lol.

And a another nf2 mobo heh.

He also has bonding gel, so I'm gonna glue some sink to my mosfets.

 

Anyways looking to replace my south bridge heatsink, my north bridge heatsink, sink up my mosfets too.

 

That means I gotta find some clean sandpaper...

Probably will just buy some I guess.

Gonan need that, and some spare parts like pots.

For those vmods and stuff .

 

I'm gonna have to find all the pics on all that, I probably got them all though but still.

I should mod my south bridge voltage as well..., I may need that.

 

I got so much to do...

I gotta finish up the 6600gt bios, because my bud has one too and he's been waiting for me to come over and hook him up.

I also gotta mod his abit nf2 bios.

The other nf2 he's got is a asus, I'm guessing that's the one I'm getting I have no clue, does'nt matter to me, still a decent socket a.

 

Gotta finish up my driver a bit too, but no way...

I did however get quadro nvs quad view working, whatever it's called.

 

Tons of crap ^^ :.

 

 

As a side note.

I checked out many diffrent romsips today.

 

I've tried hellfire's before.

It's not bad.

I need to recheck but there might be some major issues with lower fsb's.

I'm halfway 250 stable with it, but 200 was bsod city.

 

My suzuna rev's.

Man man, these just outright suck right now.

I'm allmost sorry I even put them out, kinda glad I did because I know of the timing issues now.

There's issues in these that are'nt detectable by prime, superpi or s&m, or memtest.

It sucks, very bad in stability in some areas.

Ie, corrupt memory in dos, I've been seeing it lots lately.

 

Tictac's...

Horrible.

No offence, I know the guy did alot for abit boards.

He was a nice guy it seemed as well.

 

The nvidia reference c18d 3.20 bios.

God aweful.

Not even 200mhz stable with my normal timings.

Allmost freaky.

I was afraid I was gonna corrupt my bios.

 

 

Anyways since I found how bad my bios really is, I gotta get it to the point where it's freaking useable lol.

I mean sure, I can get 275 prime stable, but that means nothing when I actually goto mod a bios even at 250 with slack timings and the file gets corrupted while in dos :.

I can't even use suzuna to make a new bios, I have to use a half baked bios I made just to doit lol.

 

 

I'll catch you guys later , tomarrow I'm getting all sink'ed up lol.

So many things to do, blah.

[kitfit1]

Does that mean that 1.3 is a bit dodgy at 250 and above Neo? Only asking because a mate has just managed to get my Infinity back in working order. When he drops it back to me i thought i'd use it as a test rig for bios's, got a spare XP1700 plus my Ballistix to play around with. Saves causing any probs with my main rig.

[NEOAethyr]

Edit:

Actually it was dodgy at 250 and lower :.

I dn how high I needed, but I know that a super high fsb was good at one time for little bit there.

And that 250 was pure crap.

Totally wierd I guess.

Maybe to much latency at 250?

 

Anyways forget this, read below ->

 

;;;

 

 

Wel...

I managed to figuer out the aggressive and optimal tables of all things, I'm loving it .

 

Complete turn around for my bios here.

 

In one, the aggressive setting, I have hellfire's, the ver that you get when you setup the cpu interface on aggressive.

On the other ver, a working alpha.

To some extent, I'm not used to this...

 

In any case, hellfire's 3eg rev3 is working perfectly.

My alpha, which is like suzuna s2, is not totally working perfectly but hey.

At least it boots 275.

I have to work on that optimal interface a bit.

 

This is major though.

I mean, I just took care of half the tables right there, I don't have to fool with them ever again except for test bios'es for those peeps with diffrent ram .

For the official releases I'll keep them in working order on that interface.

Ie, from time to time I may ask people to test a beta bios to see if we can't inprove that aggressive setting table .

 

Very good stuff.

 

I'm so not used to playing with one table though, I allways thaught of it like 2 tables, 1 and 2.

Not just 1, or 2.

 

This is how it goes:

Table 1: Optimal

Table 2: Aggressive

 

From there you can repeat that 8 times making up the 16 tables.

I have no idea what is what on that, ie the fsb's and such, but I do know what is optimal and aggressive.

 

Next bios is gonna rock .

Good for those with other types of memory, like mine, and good for those with memory like the winbond.

 

 

I'm very exited, I can test a change, and if it's not to my liking, I can swap interfaces and know I'm good to go heheh.

 

 

I also added the 5.2.22 sata raid 5 rom to my bios.

It starts up and all, however since I don't have any sata drives, I cannot truly test it.

However, it is a motherboard rom ver so I don't see why it woud'nt work.

So I have no idea about that.

 

I dl'ed the 5.0.64 ver's.

I compared them, the mobo ver is identical with the non raid and raid5 ver's.

However, the raid 5 and non raid ver's are bigger, this is where the diff's are.

The diff's are very very minor, only a few offset changed, I think it was like 8 diffs in total or something.

 

This 5.2.22 ver only had 2 ver's, not 3.

A raid 5 pci board thingy ver, and an intergrated motherboard ver.

I would assume both are raid 5 and all.

Should work just fine really, I think we can get raid 5 on these motherboards with any issue at all.

 

 

The name on my bios...

It was to long, the:

DFI LANParty NFII Ultra Infinity B Rev. A [suzuna v1.2-1T] [NVDAMC v3.20 2T]

Way to long.

I've grown found of the little epa logo, the lanparty one, I hate the full screen logo stuff, I never like those...

Anyways my name covers over the epa logo lol :.

So the long name has got to go.

I will make it simple next time.

Something like:

Suzuna v1.3 [NVDAMC v3.20 XT]

 

The XT, not copying another person's bios name lol...

It's because there's either 1t for the bpl/nvdamc, or there's a ver that's a selectable cmd rate .

Why I'm gonna call it XT, because dfi bios'es use the 3.19 ver that's modified, that allows you to select the cmd rate from the bios .

 

The progress with the romsips, and the fact that 505 does:

The cpu idle tweak, all by it's self, I only added to it a bit.

 

Has some strange addon for stability...

The 3.20 bpl now allows me to use any slot combination with inproved stability over the 3.09 bpl.

So no alt ver's just for diff slot configs.

 

 

Another good thing.

No warm boot issue here on my end.

However, the startup takes another cycle of the leds most of the time , that I can live with.

 

Supports more cpu types.

However it means dropping support for semprons, not a big deal.

 

Oh and better working dividors, but still not that great, works for 250 thogh as the newer bios'es don't work well if at all most of the time with those...

 

 

I'll release 1.3 as soon as I get a decent optimal interface going .

From there we can inprove both memory types.

I can make test bios'es for those with other types, so I can get an idea of what can or cannot be done with them

 

It's very possible we can get the votlage requirements lowered on those winbonds with just one change.

However, we need to know just how far we can go with it before it effects the timings.

Many goodies to come .

I'm out of my bad mood lmao.

 

Gonna have to rename that cpu interface thing though, to something like memory type or something I dn.

[kitfit1]

Sounds like you've really got on top of it this time Neo :nod: It also sounds, if i've read correctly, that this version will be the best so far and is likely to be good with my VX(UTT-CH5)? Am i reading that right? How long do you think it will be to release?

 

Edit:if it helps at all, i use the hardwired L12 mod to start at 200fsb. I just noticed over in the bios section that you were having a problem at 133-166.

[NEOAethyr]

Yeah I found something very strange out about the lower fsb's and a certain romsip offset ^^.

 

The hellfire romsip is probably ok down to 100mhz, maybe.

I would assume it's good since my older bios(alpha) used the same value.

 

 

Anyways for one, I got the alpha working right as the optimal table.

I screwed up a tiny bit at 1st, I'm not used to having the romsip offset a bit like this, it's off by one byte so sometimes it's hard to look at in this 505 bios.

 

I then managed to get suzuna working as the optimal setting .

Which is very cool, suzuna and hellfire in one bios, very nice...

 

 

Anyways the version of suzuna I put in there was 1.2.

Which has problem of course, but I know the offset that I would need to chnage to make it say 1.1 or whatever.

 

Anyways this one offset...

I'm stable 275x8, 4-4-2-3, 9-14, 0-0-2-3-3-6-3.

 

Now, I'm unstable with these timings everwhere:

3-3-2-3, 9-13, 0-0-2-2-0-6-3.

This doe'snt mean that it's bad for timings...

 

250 and 266 hardlock at the 275 timings above.

Yet 275 is stable?!

 

Get this, if I use the above tigher timings, on 266, I don't hardlock, however I'm not s&m stable where as I should be.

 

250 just plain hardlocks regardeless.

 

 

This one offset, at 1st I thaught I need a high fsb.

But when I saw 266 pass memtest, I thaught ok, it's both fsb and timing related, I need a fast system to run it.

 

From what I can tell, it seems alpha timing and fsb related.

It needs to be very fast to even run ^^.

 

A romsip that only really takes off around 270 min, this is just a guess.

That and it totally hardlocks at anything lower.

That my friend is very odd, but neat hehe.

 

 

I thaught about it for a bit.

I start off from the aggressive table, hellfire's, then move to a fsb where it can be used, and then change to optimal(same time as setting up the fsb works fine).

That would be allright, since anyone with tccd or what not would like high fsb's anyways.

 

But..

I don't think I can go that far just yet.

It's to much of a stretch from say 250x fsb stable to 275.

No one would beable to figuer out how to get that stable, when jumping from one fsb which is relatively small compared to the other.

So I'll proably use a diffrent value from s12 or 11.

Something in the middle.

As long as it's safe for 250 and up, or just past 250.

266 is a bit much but it's a good area, I'm thinking more or less if 258 is stable on the optimal min, and up, that's good.

 

 

I think the reason why I had so much trouble with the lower fsb's before, and trying to mod bios'es lately, is that my 1st beta, used such a value.

But since I was in the midlle of testing, I was'nt sure of it, so I would step the fsb down to say 200, or 240, etc, whatever I picked at that time.

Which was very bad.

 

I have a way of testing it though.

To make sure it's gonna be ok for a lower fsb.

I mean there's allways prime, superpi, memtest and s&m.

But like I was saying those won't cut it, they help though.

I found that doing something simple like modding the defaults in a bios with modbin, enough of them like I would normally do, shows me right away if it's got issue at that lower fsb.

So I would test the new value in prime, superpi, and s&m 1st, then make a test bios(which I would throw away) to make sure it can handle it's own.

I got one such value, my 1st test bios used it.

I have not tested this method though on 250.

 

Frm that value I was able to use 266 with 2.9v instead of 3.0v.

Memory bandwith was slightly up.

Much more stable.

 

 

It's gonna be a good bios .

I will make sure to test slack alpha's as well, and the like to double check on the optimal table.

 

As for the winbond .

I bet it's gonna be pretty good .

I have not chnaged a single thing in hellfire's romsip.

The only thing that may effect it is my bpl romsip's.

They do effect the main romsip's for sure...

It helps the hellfire bios on my end.

 

For instance:

11-3-2-3, 11-13, 0-0-2-2-0-0-3.

At 250, it's stable with everything test wise.However, after gaming in gtasa for a while, it'll exit out.

If I replace the default 619 bpl romsip that the hellfire bios has, with mine, it won't exit .

 

All my video stability mods, and a few other stability mods(some speeds ups too, they about even out though), are in that bpl romsip.

The main tables were a pain to mod all the time so most of my work started in those 4 tables.

 

I just gotta mess with the optimal table a bit more and I'll release it .

Maybe even tomarrow but I can't promise that though.

I was gonna go over my buds house but I guess I can't until friday, so I have until then to play with it.

I'll probably have a relaseable ver before I leave.

That way people can try it out while I'm gone.

[synthesist]

This is one astounding thread.............................

 

Good Grief

 

Syn

[kitfit1]

This is one astounding thread.............................

 

Good Grief

 

Syn

 

You have'nt read it all the way through have you Syn :eek2: