I have the rev1 board, maybe they're a little more fussy about it? anyways.. mine would not boot with 400 fsb unless I got mch to like 1.55 at least.Quote:
Originally Posted by Laughy
Printable View
I have the rev1 board, maybe they're a little more fussy about it? anyways.. mine would not boot with 400 fsb unless I got mch to like 1.55 at least.Quote:
Originally Posted by Laughy
Afaik it's not yet available to the "public". Only a handful of selected people have it. I guess it'll turn up sooner or later...Quote:
Originally Posted by kenograndmaster
Hmm, it seems like my boot problem has something to do with the multiplier option. If I leave the mp of my E6600 on 9, 386fsb can post. If I set it to eight or less, then the screen stays black. This is probably a bios issue then...
Yes . This happens when you change the multiplier to a lower one . It's what i get also .Quote:
Originally Posted by CopperCAT
An one other thing ... The multiplier doesn't seem to change at all.
Try to change to 8 and boot to memtest+ . You'll notice that the CPU speed is with 9X multi .
I tried some DOS benchmarks and the change of multi doesn't change anything.
So , i'd say that the multiplier option is broken .
The explanation is that the multiplier at bootup is 9x, and then the bios changes it to what you set in the bios:Quote:
Originally Posted by Stelios
http://www.xtremesystems.org/forums/...9&postcount=12
nvm
All the rom files look like that depending on what software you use to look at them. I think it's kind of silly to go to all that trouble just to deceive you-- don't you think? What does he possibly have to gain by getting "lawrywild" cred?Quote:
Originally Posted by lawrywild
Anyway, did you try loading it up with Asus Update (the Windows version) so it can at least tell you what version the Bios is-- I hope that you verified it was bogus by more than just looking at it with a hex/text editor.
Also sounds likely that the file didn't get sent completely.
I have the same problem with my machine, and it's driving me crazy. Natalia has the same issue with her P5WDG2 as well. I am trying to track down the common factor between these boards (besides that they are from Asus).Quote:
Originally Posted by Physicsman
So far, one of the possible culprits could be the Raptors in RAID0. She has 2 Raptor 150s in RAID0. I also have 2 Raptor 150s in RAID0. You have 2 Raptor 74s in Raid0.
Which RAID controller are you using? The Intel one, or the JMicron one?
nvm
lawry, there are a dozen reasons why a file wouldn't be complete-- he could have attached a partial FTP download, or something. All I'm saying is that it's kind of ridiculous to say you have something, and then deliver something fake, unless you offered to send him money for it or something.Quote:
Originally Posted by lawrywild
I can't make a judgement either way on the file, but a PM to Nemesis saying, "Hey, this file doesn't look complete/wrong" is better than calling him out publicly and saying don't ever buy or trust this guy.
It's not like he cheated you-- you didn't send him money did you? Anyway, getting way off topic here. Bottom line: It sounds like you got a partial file. Reasons why it could be a partial file are numerous, only one of which (highly unlikely) is that he deliberately misled you for intentions unknown.
Once is a random occcurance. Twice is a coincidence. Three times, maybe, and there's a pattern forming. This could go a long way with some of these posts on these forums too. "A lightning bolt exploded outside, and my FSB can now be overclocked an extra 1MHZ!!!!! EVERYONE, GO PUT UP LIGHTNING RODS FOR MAXIMUM OC!!" :)
Sweet, I'm on it! :DQuote:
Originally Posted by lkraven
nvm
I finally fixed it! I bought a new video card (BFG 7600GT), put it in and everything works perfectly. I don't know why the old card wasn't "happy" on the motherboard. Good luck with your troubleshooting. In answer to your question, I am using the Intel RAID.Quote:
Originally Posted by lkraven
Thanks for posting in the forum that I tried to send you a non-released bios. I probably won't get anymore prerelease's but I'm sure you will.
http://img151.imageshack.us/img151/3...nchmarkkv8.jpg
A simple error using web based email to upload an attachment resulted in an incomplete file. I'm currently @ work and was unware of the problem. Considering that the bios is not to be public and you asured me you wouldn't post it, I would have never thought I would get blasted in the forum in this nature. This is unfortunate, & unappreciated.:stick:
http://img140.imageshack.us/img140/5...nchmarkce7.jpg
that's not right. :(Quote:
Originally Posted by The Nemesis
The 1405 is out already, 1404 is old news. ;)Quote:
Originally Posted by kenograndmaster
I admit to being a SATA noob since I'm upgrading from pre-SATA days :eek: but can someone help.
I have WinXP booting fine on a PATA WD Caviar attached to the Jmicron IDE. But when I try to add my Raptor to any intel/jmicron SATA port to get it running as a 2nd data drive (I'll copy the boot image to the Raptor later), I get various errors. Either I get 'no boot drive', probably because BIOS detects the unformatted Raptor as the boot drive, or when I attach it to the EZ_RAID connectors there is a Secondary Master Hard Disk Error then an eventual boot to Windows but even then the Raptor is not recognized in Disk Manager.
I have tried IDE configuration setting SATA and the SATA+PATA in BIOS but no luck. How can I get a Raptor up and running with my PATA boot drive, without setting up a RAID?
Specs: Intel E6600 (week 28); Asus P5WDH ('new rev', bios 1305); G.Skill 2GBHZ; eVGA 7900GT KO; Seasonic S12 430W; Western Digital WD3200JB and Raptor 74GB; Asus DVD-E616A2; Pioneer DVR-111D; Antec Solo; WinXP SP2.
Ouch man that really sucks. What a hater. :slapass:
Isn't this easily resolved by changing the order of HDs on the HARD DISK DRIVES page of the BOOT section of the BIOS?Quote:
Originally Posted by Tamerlane
-phil
Maybe try running it off the slave drive ICH7R connectors which are the black ones, not red, and not the orange ones either. The two black SATA ports are for data drives (not boot) and those should be used for any non-raid extra disks. Then in your bios the IDE CONFIGURATION set "configure SATA as.." to "AHCI"... boot into windows from and reload the chipset drivers from the Asus CD.. the AHCI driver should load up and your raptor should work fine.Quote:
Originally Posted by Tamerlane
Thank you both for the quick responses. Somehow it's working now thanks to some fiddling in both those areas of bios and moving the raptor back out of the ez_raid ports. Another problem was the motherboard making my (obviously non-booting) USB memory stick the boot drive every time it was left in after a Windows reboot... ugh.
Care to share? ;)Quote:
Originally Posted by bingo13
t
Why are people being a stinge with these damn BIOS's? put them up so i can host them for others...
Given how quickly they are revising them, they are obviously a work in progress and pretty beta. I'm keen but not that keen if you know what I mean...