Jump to content

NEOAethyr

Members
  • Content count

    1,396
  • Joined

  • Last visited

About NEOAethyr

  • Rank
    Certified Geek

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. NEOAethyr

    PSU Brands to Avoid!

    Just PC. Made by a company called Channel Well. Anyways my buddy nicked named it, right after he saw the name: "Con Me Well" I nicked named it: "Jusa Pieca Crap" "Corn Well"
  2. NEOAethyr

    Nforce 6.86 chipset drivers are out

    ftp://download.nvidia.com/Windows/nForce/standalone/6.86 Wierd how the sub dir's don't have there date changed... Old sw ide/sata driver. The audio driver seems to be the latest though, I think. Good find racewayzx.
  3. NEOAethyr

    Starting overclocking

    Hey dude, back off the cpu multi. Goto 8.5x, which is around 2125mhz. For that should only need 1.45v vcore for. If you need more, then by all means, you shuoold'nt need more then 1.65v absolute max. From there, which everything getting less hot, and less cpu probs, and less pull from the cpu, it'll be easier on you. Why you guys allways wanna max it out lol... I mean from the get go. You gotta start low and work your way up . So work on an everyday use setting, something with the stock vcore for that cpu, not the bios stock, but your cpu's rated vcore. Let it prime. Once that's all settled, go up a multi or 2 until you reach around 10x or more. Then lower it and go up the fsb. If you have to, to get a feal for it. Go down to 200mhz fsb, and try 12x and 12.5x. To check the cpu... This part is the hardest to explain... When you get yourself into trouble, the system stability will go down the drain. It will never recover. I mean it could but... It's the cmos, it gets corrupted somehow majorly. This is the hard to explain part. You have to clear the cmos. Seems easy right? Well it's not. The cmos is finiky. You may have to clea that sucker many times before it's right again. So how do you tell it's corrupted? Well... Look for the vcore, or vmem, that's one sign. If it's higher or lower then the bios'es stock, then it's a bad cmos after clear. Other ways to tell are by jumping to something that's tight, like 266x8 maybe or whatever. It may not boot right after a clear, but it should(just a possible example). Well, clear it again and try that fsb setup again, it's supposed to boot. It may be 250 in your case, stuff like that. For example, you know it's memtest stable, and prime stable...(say it was). Well it shoudl boot, but it does'nt. Clear that cmos, don't even try forcing it, it'll be problematic in the long run. For example you'll probably have some errors in s&m when there should be none. That's how I've caught that one. Sometimes, even if it seems all good form the get go, it may not be. Ie the s&m errors. Clear a few more times and they are gone, multble runs of s&m too. I no longer bother on that though, I mean clearing to get stable. I just ensure that stuf seems normal and I go ahead anyways. As long as it boots, and as long as everythign itn eh bios setup seems normal, continue on. Something I noted today. Clearing the cmos and holding insert to boot does'nt clear the cmos as good on avg as compared to just clearing the cmos. I dn why, like I would know... I noticed it when modding spd's. Holding insert 75% of the time allowed me to oot an invlaid spd, and everytime it had th ewrong stock vmem and vcore. This would'nt happen everytime, but... When not holding insert, it did it right the 1st time. Not saying it will clear correctly 100% at all times this way, but it's got a betetr avg of doing it right. That is, if you can boot initally without holding insert, some people can't. A status update on my part. Enabled the PLL, phase lock loop on both my sticks of memory. Tested on my adata, before hand and never realized it. It's ok. The samsung I dn. I will test with memtest and lower cas and such when I get my dvdrw back in, that should be good enough I would think, the rest needs testing at 280... A PLL is somehting that checks and redoes phase.. Err... Well, it monitors the crystals, the clock. If it's off, it compensates and makes it correct. There's a pll on the mobo for this, on the left hand sie of the mmeory slots. In the box labled neuro ic pad. That's a pll chip I'm pretty sure. Both my memory stick, matter of fact, all sticks of memory since sdram I've seen pll chips on them. So I dn why they were disabled stock... I enabled them so later on, I can modify the heck out of one stick, without having to mod the other. Because if I mod only one stick's clock reference timer, it gets so fast that the other stick falls behind and sometimes dissapears, no joke. It makes my adata more stable at 280 anyways. I checked when I actually had 280 prime stable and s&m quick tests stable. What else... Oh, was priming, dual priming, 1024-1024k and 4096-4096k setups for 4 hours. Meaning 8hrs each. I logged out though after that time peroid to try some windows mods to find that it exited those and my dialup connection... Did it at 266x9 @ 1.65v . I forgot if I verified this vcore or not, so I'm doing it. I want lower vcore. And I want my system stable... I think my latest bios sucks or something I dn, I don't have my burner hooked up so I can't flash to an older bios to check.
  4. NEOAethyr

    Video Card, 3D, and high FSB OC

    SW ide's from the 5.10 pack are bad news. The newest ones are ok, should be ok for everyone, but maybe not. In general though, if the new ones are working, they are working good . Charlie22911 Like I said, I don't trust most general user info's off the net. However that one on that one setting is correct. After looking up info's in forentsics I found the info on it. Good enough to go by. Power on cycle count specifically means how many times the drive has been powered on from standby or from being powered off. Smart data is located most of at all times, on the hd platters them selves. I've done some wacky stuff with my hd's though. Like full copies, apperently that's not the norm lol... So far I've found these: SMART Specs: ftp://ftp3.ds.pg.gda.pl/people/macro/S.M.A.R.T./8035R2_0.PDF ftp://ftp3.ds.pg.gda.pl/people/macro/S.M.A.R.T./8055.PDF 8035 is THEE spec. However it has no mention of what attirb's are commen and such, attib's are diff per disk... NDST Specs: http://www.seagate.com/docs/pdf/whitepaper...anced_smart.pdf http://www.seagate.com/docs/pdf/whitepaper..._Tech_Paper.pdf You have motivated me . It appears I need to figuer out what program is correct with SMART data. I've been going with everest for along time, however recently I noticed huge errors in it's hd info. Like it reporting 600 bytes per sector lol, which is impossible. I know because I've tried 256 and 1024 and windows freaks. You can re-write smart, and I'd like to. To start from scratch. For one, my 40gig seagate, I give it over a 16 million value on one of it's smart values when I was low leveling it by hand. : I'm gonna check this out: http://sourceforge.net/project/showfiles.php?group_id=64297 There's some progs out there to redo data too so I gotta figuer that out. Btw guys. My idea of what tRTP was wrong. It's not just tRAS. I thaught a tRAS of 11 allows tRTP of 0. However if I slack other main timings I can go lower as well. So I dn. Still, tRC and tRFC I think I got that down, but I have yet to truly test that still :. I was able to use for example 11-3-2-3 with tRC of 8 at 275 so I dn, I will figuer it out someday. Anyways I will check you guys later. Check out my pcr's btw . The genric data in them is quite good. I will work on them as time see's fit.
  5. Gothic Case All video card on the nv chipset do 00h latency best. However some cards have a slow as heck bios, like the 6600gt's. So by default, they have a hard time handling it. When they are working right however, the best value for the bios ver of the latency, 0dh btw, is 0. On via chipsets I think it was 38h or 40h was optimal, for both ati and nv cards, I tested them...
  6. nf2 tweaker was way off. I have'nt worked on these in a long time though. I got more stuff to doit, but have'nt got to it at all. So it is as it is. [COMMENT]=Made by NEOAethyr. [MODEL]=nForce2 Ultra 400 [VID]=10DE:nVidia [DID]=01E8:AGP Bridge ;;;;; Header Region : [bytes : 0h - 39h] [16 Dwords] ;;;; Main Header Region : [bytes : 0h - 15h] [4 Dwords] ;;; 00h ;; Vendor ID Register : [bits : 0 - 15] [Word] [00:7]=Vendor ID (Bits: 8-15) FFFFh=Device Error [00:6]=(Same As Above) [00:5]=(Same As Above) [00:4]=(Same As Above) [00:3]=(Same As Above) [00:2]=(Same As Above) [00:1]=(Same As Above) [00:0]=(Same As Above) [01:7]=Vendor ID (Bits: 0-7) FFFFh=Device Error [01:6]=(Same As Above) [01:5]=(Same As Above) [01:4]=(Same As Above) [01:3]=(Same As Above) [01:2]=(Same As Above) [01:1]=(Same As Above) [01:0]=(Same As Above) ;; ;; Device ID Register : [bits : 16 - 31] [Word] [02:7]=Device ID (Bits: 8-15) [02:6]=(Same As Above) [02:5]=(Same As Above) [02:4]=(Same As Above) [02:3]=(Same As Above) [02:2]=(Same As Above) [02:1]=(Same As Above) [02:0]=(Same As Above) [03:7]=Device ID (Bits: 0-7) [03:6]=(Same As Above) [03:5]=(Same As Above) [03:4]=(Same As Above) [03:3]=(Same As Above) [03:2]=(Same As Above) [03:1]=(Same As Above) [03:0]=(Same As Above) ;; ;;; 04h ;; Command Registers : [bits : 0 - 15] [Word] [04:7]=Address / Data Stepping 1=Wait Cycles Enabled [04:6]=Parity Error Response 0=Disabled 1=Enabled [04:5]=VGA Palette Snoop 0=Disabled 1=Enabled [04:4]=Mem Write&Invalidate CMD 0=Disabled 1=Enabled [04:3]=Special Cycle Recognition0=Disabled 1=Enabled [04:2]=Bus Mastering 0=Disabled 1=Enabled [04:1]=Memory Access 0=Disabled 1=Enabled [04:0]=I/O Access 0=Disabled 1=Enabled [05:1]=Fast BackToBack Cycle 0=Same Only 1=Diff Allow [05:0]=System Error Line (SERR#)0=Disabled 1=Enabled [06:7]=Fast BackToBack Capable 0=No Support 1=Supported [06:6]=User Definable Features 0=No Support 1=Supported [06:5]=66MHz Capable 0=No Support 1=Supported [06:4]=New Capability List 0=No Support 1=Supported ;; ;; Status Registers : [bits : 16 - 31] [byte] [07:7]=Detected Parity Error 0=None 1=Error [07:6]=Signaled SystemError Line0=None 1=Error [07:5]=Received Master Abort 0=None 1=Aborted [07:4]=Received Target Abort 0=None 1=Aborted [07:3]=Signaled Target Abort 0=None 1=Aborted [07:2]=Device Select Timing 10=Slow 11=Unknown [07:1]=01=Medium 00=Fast [07:0]=Data Parity Error 0=None 1=Error Detected ;; ;;; 08h ;; Revision ID Register : [bits : 0 - 7] [byte] [08:7]=Revision ID [08:6]=(Same As Above) [08:5]=(Same As Above) [08:4]=(Same As Above) [08:3]=(Same As Above) [08:2]=(Same As Above) [08:1]=(Same As Above) [08:0]=(Same As Above) ;; ;; Class Code Registers : [bits : 7 - 31] [Word + Byte] [09:7]=Programming Interface [09:6]=(Same As Above) [09:5]=(Same As Above) [09:4]=(Same As Above) [09:3]=(Same As Above) [09:2]=(Same As Above) [09:1]=(Same As Above) [09:0]=(Same As Above) [0A:7]=Sub Class [0A:6]=(Same As Above) [0A:5]=(Same As Above) [0A:4]=(Same As Above) [0A:3]=(Same As Above) [0A:2]=(Same As Above) [0A:1]=(Same As Above) [0A:0]=(Same As Above) [0B:7]=Base Class [0B:6]=(Same As Above) [0B:5]=(Same As Above) [0B:4]=(Same As Above) [0B:3]=(Same As Above) [0B:2]=(Same As Above) [0B:1]=(Same As Above) [0B:0]=(Same As Above) ;; ;;; 0Ch ;; Cache Line Size Register : [bits : 0 - 7] [byte] [0C:7]=Cache Line Size [0C:6]=(Same As Above) [0C:5]=(Same As Above) [0C:4]=(Same As Above) [0C:3]=(Same As Above) [0C:2]=(Same As Above) [0C:1]=(Same As Above) [0C:0]=(Same As Above) ;; ;; Latency Timer Register : [bits : 8 - 15] [byte] [0D:7]=Latency [0D:6]=(Same As Above) [0D:5]=(Same As Above) [0D:4]=(Same As Above) [0D:3]=(Same As Above) ;; ;; Header Type Register : [bits : 16 - 23] [byte] [0E:7]=Header Type [0E:6]=(Same As Above) [0E:5]=(Same As Above) [0E:4]=(Same As Above) [0E:3]=(Same As Above) [0E:2]=(Same As Above) [0E:1]=(Same As Above) [0E:0]=(Same As Above) ;; ;; BIST Registers : [bits : 24 - 31] [byte] [0F:7]=Built In Self Test 0=No Support 1=Supported [0F:6]=Initialize Built In Self Test [0F:3]=Completion Status [0F:2]=(Same As Above) [0F:1]=(Same As Above) [0F:0]=(Same As Above) ;; ;;; ;;;; ;;;; Header Type Dependent Region : [bytes : 16h - 39h] [12 Dwords] ;;;; Header Type : 01h ;;; 10h ;; Base Address Register 0 : [bytes : 10h - 13h] [1 Dword] ;; ;;; 14h ;; Base Address Register 1 : [bytes : 14h - 17h] [1 Dword] ;; ;;; 18h ;; Primary Bus Number Register : [byte : 18h] [1 Byte] ;; ;;; 19h ;; Secondary Bus Number Register : [byte : 19h] [1 Byte] ;; ;;; 1Ah ;; Subordinate Bus Number Regsiter : [byte : 1Ah] [1 Byte] ;; ;;; 1Bh ;; Secondary Latency Timer Regsiter : [byte : 1Bh] [1 Byte] [1B:7]=Secondary Latency Timer [1B:6]=(Same As Above) [1B:5]=(Same As Above) [1B:4]=(Same As Above) [1B:3]=(Same As Above) [1B:2]=(Same As Above) [1B:1]=(Same As Above) [1B:0]=(Same As Above) ;; ;;; ;; I/O Base Register : [byte : 1Ch] [1 Byte] ;; ;;; ;; I/O Limit Register : [byte 1Dh] [1 Byte] ;; ;;; ;; Secondary Status Register : [bytes : 1Eh - 1Fh] [1 Word] [1E:7]=Fast BackToBack Capable 0=No Support 1=Supported [1E:5]=66MHz Capable 0=No Support 1=Supported [1F:7]=Detected Parity Error 0=None 1=Error [1F:6]=Signaled SystemError Line0=None 1=Error [1F:5]=Received Master Abort 0=None 1=Aborted [1F:4]=Received Target Abort 0=None 1=Aborted [1F:3]=Signaled Target Abort 0=None 1=Aborted [1F:2]=DEVSEL# Timing 10=Slow 11=Unknown [1F:1]=01=Medium 00=Fast [1F:0]=Data Parity Error 0=None 1=Error ;; ;;; ;; Memory Base Register : [bytes : 20h - 21h] [1 Word] ;; ;;; ;; Memory Limit Regsiter : [bytes : 22h - 23h] [1 Word] ;; ;;; ;; Prefetchable Memory Base Register : [bytes : 24h - 25h] [1 Word] ;; ;;; ;; Prefetchable Memory Limit Register : [bytes : 26h - 27h] [1 Word] ;; ;;; ;; Prefetchable Base Upper 32 Bits Register : [bytes : 28h - 2Bh] [1 Dword] ;; ;;; ;; Prefetchable Limit Upper 32 Bits Register : [bytes : 2Ch - 2Fh] [1 Dword] ;; ;;; ;; I/O Base Upper 16 Bits Register : [bytes : 30h - 31h] [1 Word] ;; ;;; ;; I/O Base Upper 16 Bits Register : [bytes : 32h - 33h] [1 Word] ;; ;;; ;; Capabilities Pointer Registers : [byte : 34h] [1 Byte] ;; ;;; ;; Reserved : [bytes : 35h - 37h] [1 Word + 1 Byte] ;; ;;; ;; Expansion ROM Address Register : [bytes : 38h - 3Bh] [1 Dword] ;; ;;; ;; Interrupt Line Register : [byte : 3Ch] [1 Byte] ;; ;;; ;; Interrupt Pin Register : [byte : 3Dh] [1 Byte] ;; ;;; ;; Bridge Control Register : [bytes : 3Eh - 3Fh] [1 Word] [3E:7]=Fast Back To Back Enable 0=Disabled 1=Enabled [3E:6]=Secondary Bus Reset [3E:5]=Master Abort Mode [3E:4]=VGA 16Bit Decode [3E:3]=VGA Enable [3E:2]=ISA Enable [3E:1]=SERR# Enable [3E:0]=Parity Error Responce [3F:3]=DiscardTimer SERR# Enable [3F:2]=Discard Timer Status 0=No Error 1=Timed Out [3F:1]=Secondary Discard Timer 0=32768 Clks 1=1024 Clks [3F:0]=Primary Discard Timer 0=32768 Clks 1=1024 Clks ;; ;;; ;;;; ;;;;; ;;;;; Device Dependent Region : [bytes : 40h - FFh] [] Edit: Might as well mention what I got. I got all PCI-SIG docs related to stuff like this. Microsoft src code for pci config space handling. Then for cards themselves, actual code for those nv card's pci config space, older ones but hey(Up to and including the gf3). Which includes scratch as well which is neat... :. Just have'nt had the time. Edit: Messed around a tiny bit and added base class values. Sub clas I don't think I an do with the constraints in wpcredit, it does'nt give me enough room for descriptions. I checked and they are halfway accurate. But..., they need to be worked on more. I prmised to release them quite a while back but never did. Well, I dn if you guys understand why or not, it's because I have to read through a few books and src code to figuer it all out. Then making a pcr file out of them, with corect spacing, best as possioble descriptions within that small confined space, etc. I was wokring on a system where I could copy and past diff portions of headers related to other devices. Making it the end all pcr thihng I dn whqat to call it. So I could copy portions out and have them 100% accurate depending on the device. And clean. I hav'nt re-checked the mem controller or anythign like that though in some time, so... That sort of stuff me be half @ssed right now. Plus there was stuff I need to check on this asus I got to the side. I need to make dumps of it for more reg's, because it's got bios options this lpb don't have. Blah blah blah blah. I'll attach them anyways, only my nvidia ones. The 00F1h one is another half @ssed one. I never did work on that one very hard, nor very long. Some of the stuff I guessed... I can add power states to all devices later using this src code from ms I got. Oops, one small typo in the base class, ohwell for now. Also there's min grant and max latency in the nb and one of the mem controllers, they probably don't belong there.
  7. NEOAethyr

    hard drives & raid - benchmark and compare!

    Ok... Got both my western digital drives hookd back up. Figuered out that cooling the top of the drives does'nt cool as well as cooling the bottem. My 1600jb, benching before messing around with it, then after and then again and again... Well, upside down yields less then 0.0ms access time diff, somehting like 0.0xms. Somehting I can't even see the majority of the time with the benches, but it's notcieable during windows startup. The fake xp style progress bar when loading windows. And in gaming it's slightly noticeable. During benching, the 1st time I put it upside down, I got 0.1ms less. To give you an idea: The arm would swing down to the center of the disk: 19.8ms, 10% usage The arm would swing up to the center: 19.8ms, 12% usage Upside down(lable down): 19.7ms, 8% usage Upside right, lable up: 19.9ms, 10% usage Nothing to go by right? After hooking it up by it's self, it's was'nt that great either, not the best of te above, while upside down. After becnhing with both disks in, I got 19.8ms and 12% usage again. Windows startup when alone and now together again is lower though. Instead of the middle of the bar, it's probably 3 spaces, I did'nt count. Same was with it alone, faster, but faster on avg. Gaming alone was better, but there was high latency, but it was all good. Gaming together, was'nt much diffrent then it was before I moved to my new case. Not done doing that one at all... Anyways, seemed slightly better. Both hd's are upside down. I notcied this one before, but shook it off and did'nt care, now I'm thinking about redoing it... The swap. I have dual 1 gig swaps, 1 each per drive on there primary partition. Latency seems halfway between the 2 disks. Slow gaming loading on avg, but ok gaming. When on the 1600jb, quick loading, but some added latency while gaming. I belive if I go back to using only one swap on the 1200jb, my latency will go way down, and i'll have the quick loading. Last time I benched the 1200jb, a bit ago, it was 13.2ms of latency, with 6% cpu usage. I had setup 2 swaps incase one drive failed temperarly. However, for the time being, I think I will setup windows to only use one of those until I need the other one if such an occurance happens again. Power on time count seems lower on the 1200jb now, instead of over 10000 or 11000, whatever it was, it's 9889(not great). I think the power on cycle count is lower too, but I'm not sure. I should of checked before hand... I can allways flip them around later and do a through check. The temp thing, one other thing I notcied is that the motor it's self on my 1600jb is 1c hotter then reported by smart. At the time it was 5c above ambient, now smart for that drive is 1c above ambient... Anyways, cooling the botten half of the drives seems most important... Sorry, I hope you guys don't mind the non raid chatting for a moment. It's all hardrive related... Been years since I did any serious hd bences, since back when I had 1gig drives... Edit: After trying both hd's swap file, alone with both hd's installed. Maybe 5 bars to load windows on the xp stle loading screen with the 1600jb. 3 bars when using the 1200jb. 2 bars when using both. Gaming loading was no better either way, tiny tiny bit better on both drives. The 1200jb is the lower latency, but slower drive, the 1600jb is the higher latency but faster drive. It seems I need to put them back on there own pata controller channel, instead of sharing one like they are now(I've had it like this for some time now, about when my load times when up for gaming). It does seem that using a dual swap, on 2 good drives per say, actually does better then only having one swap. Kinda surprising... On raid however one swap would defently be best.
  8. NEOAethyr

    hard drives & raid - benchmark and compare!

    Yeah it must be the windows subsystem performance. Strange that we can sustain so much though. Then again those are in 64k chunks, but still, it's reading/writing out a 256m sized like file so.... Using the nv drivers here. Onboard. That was my 1200jb, I forgot what partitions were what at that time. I'm on my 1600jb right now. Using it as my only drive, I'm moving to a new case... No hd bays or anything . Net yet anyways. Here's what it looks like, I'll attach the image. I don't have the time to crop it correctly, just enough to get it to fit as an attahcment. I don't have any fans on my drive ... I bet it'll do better with more i/o depth. Anyways I gotta get and work on my rig more. I did some benches comparing the diffrences between how you have a hd set. Normal - lable up. Upside down. And both sides. Only for one hd, only 1 pass each. Seems as if arm pointing down towards the center or upside down is best on this hd. I will test my other 2 drives though to try getting a better idea, the diff seems very nil. I'm just curouis since I'm setting upa new case and all, as to what way my hd's should be set in my case. Oh yeah, I figuered out why hd tach said I had 0% cpu usage. It was because I was runnig 2 instances of prime and etc at the time.
  9. NEOAethyr

    Monitor Turning Green

    No I did'nt look around. I thaught it may of been a box. In any case, I still stand by you cannot adjust by graphs alone. Anyways you got your prob sorted out it seems. Edit: Anyways adjusting by software is not professional in the least. It must be done by hardware. But blah blah lol .
  10. NEOAethyr

    hard drives & raid - benchmark and compare!

    Nah I could'nt of been getting that high of performance. I just benched with atto on one of my drives, the messed up one. And I'm getting 58megs a sec reads and 55megs a sec writes with 256m sizes "files". That's on one of my 2 temp file partitions though, very small partition(4 gigs). I probably get around 40m a sec or maybe slightly higher in real world on my bigger 100gig partitions. Hmm maybe I had that backwards... Anyways as an edit... Just tested very half @ssed using atto but wihtout direct I/O. Holy freaking crap... Reached over 500megs a sec and 700megs a sec. I will post a screeny. Editing to add the pic. Not best of course, on the net, all that etc etc, unclean partition, blah blah. More wierd results. Ok, wierd results with atto and hd tach, any other programs?
  11. NEOAethyr

    ATTO Hard Drive Benchmark Application

    Well, I was thinking about getting it, I just remembered about it. I allready got the HD Tach one... So I reg'ed for it, a pain really, kept redirecting me to relogin... Figuered that out, found the link. Then I checked my logs..., found the direct link. Closed out my firefox winows and tried in getright twice to see if I could resume and dl it without cookies. Semed all good. Went to go post the direct dl for others , in that raid thread, so other poeple did'nt have to go threw that and saw this thread . I just benched one of my partitions too. Works out allright, I like the program so far. Anyways I hope it helped ExRoadie . Darn typos. Mmm taco's.., I gotta eat, laters
  12. NEOAethyr

    ATTO Hard Drive Benchmark Application

    Well I'll be of all things... I just reg'ed, using a bs reg and stuff wfor the offical atto site, and got me a dd for that benching program . And I was gonna post it here, thinking it's not a huge deal, it's only the free benching program we're after... So.. http://www.attotech.com/software/secure/wi...hbautil_320.exe Dl this one and check it yourself .
  13. NEOAethyr

    hard drives & raid - benchmark and compare!

    To add onto what ExRoadie said, windows also monitors I/O. In many ways. 1st bing the main I/O counters for disk operations. The 2nd being the performance counters for the hardrive controller. The crc32's, like ExRoadie said. Last access times... File creation dates... Truncated extentions... Long file names and times stampes for FAT... 8.3 ver's of the file names for NTFS... NTFS USN journals... Disk performance counters...(yes many of these, many many). I'm sure there's much more. Not even including the workload over IRQL's when using the ones related to drive access. ExRoadie, actually windows will continue to fall back all the way to pio mode, the errors will not stop . Every single time I've ever seen that issue happen, it's not because of the transfer mode(Well in your case sorta, but it still fell back all the way to pio did'nt it? ). So hence, it will fall back all the way eventually. Once you hit pio mode, all heck breaks lose, since some controllers absolutely hate pio mode. That and the lower the transfer mode you go, the lower the peak bandwith, and the more cpu utilization used to transfer files. Oh yeah indexing.. Yep. There's tons of that, the service, the indexing logs.., etc. Even then it's still there. Kobalt 2hrs to copy 160 gigs.. Wow man, that's along time... I'm not bragging or anything but it takes me at tops 40mins to copy around 120gigs, normally around 20-40mins, depends on how much I copy. I dn the exacts, but 2hrs is very very long, it's never taken me that long to do a straight copy. I mean it may take me all night to copy stuff to here and there, remake partitions, etc etc, to get it all setup. Then once it's all setup, copying the files to there correct location does'nt take to long. For example a 80gig partiton to copy to a 100gig partitoin only takes me around 20mins probably. Another 20mins to do my other drive's big partition. Ruffly anyways, maybe add another 10-20mins, I forgot. Not an hour though. I just did this about a month ago... It takes much longer on this seagate, it's a really old drive though. To tell you the truth. It's probably the I/O size setup. To little and you get more cpu utilization. Less on small teeny tiny files. But truthfully, look at an avg game and see how many huge files there are... Even in windows, though most files are small, small enough where 32k cluster would be optimal, but in real world performance, in my case anyways, 64k straight up wins in all cases. Cluster size. MBS/Block mode. Stripe size. In any case you have it all said and done so whatever .
  14. NEOAethyr

    Monitor Turning Green

    Bs it would'nt. You cannot adjust by looking at graphs alone.
  15. NEOAethyr

    hard drives & raid - benchmark and compare!

    Hey I hope you guys don't mind me coming in here and chatting a tiny bit... I don't have a raid setup, nor plan on getting one. But..., I'm interested in collecting good hd benching programs. I'm also interesting in getting those new seagate 7200.10's... In the future though. Anyways I dl'ed the free ver of hdtach right, and I got some odd results. Can you guys check this? : http://www.savefile.com/files/8371150 The sustained read scores seem a tad high, for these drives I think. Not a huge deal, but the cpu utilization of 0%? I don't think that's right... Plus my scores are hiher then ref scores in that program, which seems kinda odd because normally ref scores in a program are at best. Mine on the other hand, well, look at the pics, I was dl'ing torrents, dual priming... I did'nt mod anything to do with the pci bus or hd controller, latency or grant wise, or anything like that at all. Using the onboard ide controller on the nfii lpb, with sw ide's ver 667. Both ports filled up, the 2 wd's on the same controller, the segate with my dvdrw. All of my drives are filled up mostly, one with around 30gigs free, the other around 20gigs. The seagate has around 20gigs free. I was'nt at high speeds or anythuing, 250mhz fsb, slack timings, 2.1ghz cpu. You get the idea, nothing special, slow actually. I'm just wondering if I should try a diff program. Edit: Hmm, hmmm.. That 1600jb of mine, I wonder if that's why it has a hard time being detected sometimes after I clear my cmos. Maybe... I have all my drives on there side right now. The 1200 and the seagate are setup where the arm swings up to the center. The 1600 the arm would swing down to the center. I wonder if I reverese that if I can fix that sucker... And bring it's ramdom access time back down. I should bench it the oppiset way, then upside down and upside right... I'm puting together another case for myself, snapped a dremal bit so I have to wait still, but if the drives prefer being setup in one direction I'll have to go with that... I will check that out later on today or tonight or something, when I got time anyways. I gotta do tons of cleaning in my house today :.
×