Thanks man...Quote:
Originally Posted by sesdave
Printable View
Thanks man...Quote:
Originally Posted by sesdave
XP is reinstalled now using enhanced ide mode and not AHCI. I looked but it seems the only ide drivers for this mode are the preinstalled microsoft drivers.
The raptor is slower so the os is a bit less responsive but I can now watch videos without major stuttering, there is still occasional minor stuttering but it is mostly gone. I have concluded AHCI shouldnt be used when PATA drives are connected and possibly even when incompatible SATA drives are connected. I disabled write cache on the raptor but its still currently enabled on all the other drives.
i have two rapters in raido i have no problem watching videos
:up: and so far so god
Well, it'll be sad to only get 18 months out of my P5W if I have to replace it to use a Penryn. I'd have to settle for a quad CPU with hyperthreading rather than dump the motherboard too. Already I see awful performance just using 802.11G to transfer files to the C2D computer, where moving my USB mouse around to the right spot becomes an adventure, so I want more guts. I can't always use Vista due to hardware incompatibility so no amount of thread handling improvements there mean much to me. Maybe if I run a cable through the attic things would work better all around, but that still costs more than I want to spend. Not sure where the next upgrade really needs to go.Quote:
Originally Posted by sesdave
Amazon is delaying the $79 power supply to December 21 as "unavailable", despite listing other vendors as low as $119, so I'm stuck at a very reliable 30% overclock (~2.4Ghz) until then, when I might be able to get back to 2.87Ghz to help overcome performance issues...
So I tried flashing this thing back to 0701 and 1707 to support my Conroe.
No go. Assus' flash utility refuses to go back claiming the BIOS is too old and I should "download the newest BIOS".
Go manually for ASUS BIOS c/o:D
use your afudos off your asus cd i did revered back to 1707 from 2205 works great still waiting for my es chip to come good luck rich
reflash to older BIOS details http://www.xtremesystems.org/forums/...sh#post2143429Quote:
Originally Posted by uOpt
Having recently changed from a P5W to P5K board and WinXP to Vista x64 I have been doing some googling for info and you may find this of use if you are running or thinking of installing Vista on the P5W.
This is a link to a great guide which will let you tune Vista http://forums.techpowerup.com/showthread.php?t=24912. These tools are also useful TweakUAC and EASYBCD v1.6. TweakUAC lets you switch off or supress UAC - EAsy BCD has numerous tools and allow configuration of multi boot with other operating systems.
Multiboot with WinXP - I found that just installing Vista x64 in a seperate partition on boot drive with Winxp caused HD data corruption - seemingly this is a know problem and EASY BCD is the solution. Here is a link to a complete multiboot install guide. http://apcmag.com/5023/dual_booting_xp_with_vista
Acronis disk manager is another tool that will also shrink the Winxp partition to allow creation of another on the boot drive.
working very well :clap: & zero problems
So what is the decisive thing here that makes you able to go backwards? That you rename the file? Or that you use AFUDOS 2.11?Quote:
Originally Posted by sesdave
yeah the 2205 bios is suik my problem is on the voltage control.
In my experience both are required. Plenty of other posts in this thread with the same instructions. havent seen following this processs not work yet!.Quote:
Originally Posted by uOpt
I'll give it a shot, but I am 99% sure I already used 2.11 in my failed attempt.
Somehow I feel like a lab rat being trained by Asus.
What do you guys think, will 1707 most likely work? We have one with a quad ES on 1701, so probably yes. Or should I go 0701? Remember this is one-shot for me. If I aim after ES murder and before Core2Celeron support I'm bricked until I ebay some junk CPU :)
Hi, I have a "problem" that i dont know if it has been reviewed in the thread already, but since this thread has more than 200 pages well... i have just bought this motherboard and i flashed it to the 2004 bios, overclocked perfectly my E4300 to 3.0Ghz Rock Steady, im useing it with 4GB of Corsair XMS2 PC5400C4 memory modules all "overclocked" to 834 mhz since in bios there isn´t a plain 800 mhz option, i know this modules are 675 mhz marked, but they do 800 mhz with a hand tied in the back, im useing 2v in them for stability reasons only, since they work fine at 1.9v most of the time, only orthos makes them fail after some time of running it... well the thing that bothers me a little its that in bios post and in windows operating systems only reports me 3.2 GB of ram, when in cpu-z and other programs they see the 4GB i have installed, i know the lower memory showing in system panel its for the lack of PAE in windows 32 bit systems, so i installed as second OS Windows Vista 64 bits to "see" my 4GB, but to my surprise in this board still tells me that i only have 3.2 GB of ram, even in this 64 bit system...
This is the first board that gives me this "problem" (since still has a quite good performance, but you know, i want to see my full 4gb in control panel :p: )
Thanks all in advance for your replys to my problem, and hope someone can help me to set bios or something to see my 4GB of ram as i see a screenshot in this last page showing 4GB in Vista 64.
:)
use AFDOS207 from here:Quote:
Originally Posted by uOpt
http://mainboard-drivers-and-utiliti...7-For-Dos.html
then flash with these commands
afudos /ip5wdh.rom /pbnc /n
that will do it , worked for me to get me back to older bios...
you need to enable the memory remap feature under the memory settings. I believe it is right under the hyperpath 3 setting...Then during post you will see all 4 gb of memory...Quote:
Originally Posted by Black Scorpion
uOPT,
"...decisive thing here that makes you able to go backwards? That you rename the file? Or that you use AFUDOS 2.11?..."
AFUDOS 2.11/2.17 does not seem to have "revision check" as later DOS flashers.
- there are some sensitivities between BIOS'es CPUs/OS/features, which may be the reason later flashers discourage backward flashing.
- examples: [1707 + JMicron ROM + Vista SpeedStep]; [2004 + Enhance memory compatibility]; [1602 + Enhance HDD compatibility]
- see P5WDH BIOS section for more details: http://support.asus.com/download/dow...Language=en-us
- renaming target BIOS to "p5wdh.rom" is the default filename "CrashFree" process looks for, on floppy or USB drive.
Have been lucky and have not had problems with new BIOS'es, including latest 2205.
- have tested BIOS reverting, all the way back from FEB, 2007.
- ref: http://www.xtremesystems.org/forums/...postcount=3823
BlackScorpion:
- adding to MarcusTaz's post about Vista 64b, RAM and Memory Remap, see the following:
http://www.xtremesystems.org/forums/...postcount=4178
http://www.xtremesystems.org/forums/...postcount=4179
im using bios 1707 right now with a 6400 es works good but speed step dosent let me change it may have to try 1601 bios :yepp:
Thank you MarcusTaz and bichi for your replys.
Problem solved !!!
:up:
anybody tried one of the GO stepping quads in this board yet, if so hows the fsb wall compared with the 320ish fsb of the old q6600s
320 wall? I've got a B3 and could do 350 FSB on it no problems. Would crap out above that.Quote:
Originally Posted by GLENBOY
I have a G0 on order and will be able to report my findings soon (hopefully).
I did not check out my stepping but I have a Q6600 running stable @ 378 FSB 3.4GHZ 1:1 on the memory... Not about to pull off my Swiftech water cooled block to check my stepping but next time I do maintenance I will be sure to look at the cpu...
400FSB was my goal but I cannot get it to run stable @ 3.6GHz
If you bought the chip retail, you can look on the bottom of the box to get the stepping and information.Quote:
Originally Posted by MarcusTaz
or CPUZQuote:
Originally Posted by ae804
I dont watch the videos from my raptor it is just used for the operating system and main apps.Quote:
Originally Posted by w2richwood
Although it is easy to blame the hard drives everything was just fine on the amd64 in fact my old amd64 system has a very slow old hard drive in it right now and has no problems whatsoever, I just watched a dvd mounted from an iso image on a hard drive (in this system) and sad to say it has stuttering, again not as bad as when using AHCI but enough to ruin the experience.
This is feeling like a downgrade as far as watching media is concerned, the OS itself runs faster vista certianly runs faster from when I tested it but watching movies is a poor experience.
To make things worse the amd64 runs on a budget asrock board whilst I paid for a premium board for the upgrade.
Is it the pci-e bus is saturated or something? dont know, I am going to try disabling speedstepping next and if that makes no difference I will try different display drivers, I wonder if the onboard mem controller on the amd64 is making all the difference, I certianly feel like selling this new hardware and going back right now, upgrading is supposed to be an enjoyable experience :(
The hd I watched the dvd from is mounted on the ich7 sata controller.
Is there a better bios other then 1407 that allows for better OC? Or should I keep 1407 as "it's as good as it gets"
Thanks for specifying the detail of why we use 2.11/2.17 and rename the BIOS for reversion BIOS flashing. Your memory retention is better than mine - it works so I had forgotten the detail!Quote:
Originally Posted by bichi
Ok guys, I am in dilemma. I want a Q6600 after price cutting but do not know what stepping. On the one hand this is B3 stepping available now and compatible with my current stable bios (1901). But this stepping seems not to OC as good as G0. On the other hand G0 require 2205 BETA bios which may cause problem with Vcore regulation. And for the time being, it is hard to get a G0 stepping. So what to do: get B3 now or wait for better bios and better Go availability?
Does somebody have some experience with B3, G0 and new bios? Any help appreciates.
Solving Vcore issue:Quote:
Originally Posted by happ
Disable EIST and all that junk, as per standard
Disable multiplier then re-enable it - vcore options will now be available
Set desired vcore
Save "overcloking profile"
On every entry to the BIOS load the "overclocking" profile you saved, go and disable multiplier, then re-enable it again, everytime you want to change vcore.
It works good that way. Oh, and it does not save a setting in the "onboard devices" section; onboard sound is disabled on each bios entry, so it has to be enabled too. Although, that will be solved when saving the profile.
What a hassle! Is there chance to get a normal bios from ASUS that support G0 any soon?Quote:
Originally Posted by k0nsl
hi all, just joined, been reading this forum for a while though. I wanted to start OC'ing my setup, but unfortunately a couple days ago I ran into some weird trouble. I've had this setup for almost a year running without issues, but now I can't post after a cold boot. All the comp does is spin up all fans, mobo led on, pioneer drive on, Benq drive off, hdd's spin up. Thought maybe the Benq was at fault, but disconnecting it doesn't help. Disconnected other dvd drive, no luck. Disconnected all hdd's, first just de pata, then one sata, then 2 satas, then all, no luck posting. Tested the seagates with seagate's hdd tool, no problems there. Rebooting several times has brought my comp back to life without apparant reason a couple times, but sometimes I had no luck at all getting it back up and running. The only thing that does work 100% is powering down the comp completely, so flicking the I/O switch on the PSU after powering down and let it sit there for i'd say at least 5 hrs. After that i can start up the comp, post, and get a standard boot into windows. I've had it running 24/7 after this issue for at least 10 days, just restarting the comp every now and then, and no problems at all. I ran orthos(5+hrs), memtest(over night), everest(several hrs) to test ram, changes ram slots, tested with just one ram stick, no luck, ram seems fine to me. In your opinion, what would be the most likely cause for this issue? I tried finding info on the net, no luck, i hope someone here has some ideas. I'm considering testing another PSU, but i would have to buy another one, so yh, i'd rather not. Btw, bios is 0701, never bothered upgrading since this worked fine for me so far. One other weird thing, the lian li has a 3 step fan switch on the front, going from step 1 to 2 makes the fans stop spinning, from 2 to 3 fans spin up, from 3 back to 2, fans spin, from 2 to 1, fans spin, maybe just a problem with the casefans+switch? Never had that problem before though. Not sure if I should post this somewhere else on this forum, if so, sorry in advance. All help very appreciated :up:
Holy crap, I just realized that you need the latest beta bios to run the G0s....:shakes: I may have to try them out this weekend to see how bad they really are.Quote:
Originally Posted by happ
I'm pretty sure 2103 also works with G0...
True, but it is beta too.Quote:
Originally Posted by lawrywild
Yeah but it has a lot less issues than 2205. I think an official bios will be out within a week or two so hold off on the Q6600's is my opinion (and what I'm doing). Once we get an official and working bios then most shops will have all G0 stock and everything will be good to go :)
Can't wait :D
Hi,
I got a Q6600 B3 a couple of days ago form ebuyer, I took a gamble on the stepping but to be honest I am not that bothered its not a G0.
Currently its clocked up to 3GHz and I'm happy with that.
Had to raise the vcore a tad for full stability.
If it had of been a G0 I would have been forced to upgrade to 2103 or even worse 2205....I am using 2004 at the moment.
Temps when idle seem to hover at 33c for the cpu and 50c for the cores (reading from Everest).
ok my es 6400 work with bios 1707 but will it work with anything later then 1707 bios
Ok, I don't want to go on your nerves, but before I go my one-way flash:
I need 410 FSB (x9) for that build, otherwise the whole thing is useless to me. Is that realistic to get out of a random P5W DH or do I better save my energy?
Thanks to Intel excluding lower multipliers from Core2Celerons I can't test before flash :mad:
410 should be no problem with a average-to-good clocking chipset
Yeah the only P5W DH I've had that couldn't do 410 was one I busted by running it for a few hours with the nb heatsink dislodged. :D
The worst ones do 420 out of the box, nicer ones 440-450.
Exactly, I think I will wait too.Quote:
Originally Posted by lawrywild
Why are people using such old bioses and reveresing the new ones?
Isnt the new ones good? :eek:
Q6600 B3 @ 3.3 Ghz 367x9 Can't hit 377 though(auto spd timings) .. almost boots at 3.4Ghz(378) but then reboots.
3.3Ghz is stable though.
Hits 3.2Ghz at 4.4.4.11 np :)
ASUS P5W DH Deluxe.
My P5W DH did 416Mhz x 6 .. but can't get the same memory to hit 416Mhz at 8 or 9 x.
US
4GB ram or 2GB?Quote:
Originally Posted by UnknownZA
I can't see myself hitting 370 fsb with 4GB. Hoping for 333 though :)
I got an early P5W DH that has limited vMCH but it did 410 with an E6300 and the limiting factor was the Corsair memory that failed tests at anything over 410. If I had known, I'd have gotten 'better' memory.Quote:
Originally Posted by uOpt
I've never seen a chart indicating OC ranges for different CPUs, but if my less-than-desirable MB can do it, a newer one should also be OK...
4x1Gb Team Elite 800 DDR2Quote:
Originally Posted by lawrywild
http://www.hardware.info/en-US/produ..._DDR2800_2_GB/
My timings for 333 is set slightly different. 4.4.4.11 and not 4.4.4.12
My 3.2Ghz
http://forums.prophecy.co.za/attachm...20-675-936.jpg
Intel Q6600 B3 @ 3.2Ghz
Asus P5W DH Deluxe 2004 Intel 975X @ 1426Mhz
Asus GTS8800 320MB @ 675/936
Team Elite 800Mhz 4x1Gb - 356Mhz(712)
Zalman CNPS9700L Cooler
WindowsXP 32-Bit
3DMark06 - 12415
I'll post my 3.3Ghz tomorrow.
US
Oh, awesome. Good news for me then :cool:Quote:
Originally Posted by UnknownZA
What's the deal with the memory dividers on this board?
I should have 1:1, 3:4, 3:5 and 1:2.
When selecting 200 MHz FSB with a 800 MHz FSB CPU:
- 400 1:1
- 533 3:4
- 600 WTH?
- 667 3:5
- 800 1:2
When selection 300 MHz FSB with the same CPU I get more memory dividers:
- 450, yeah, right. Should be 1:1
- 600
- 750
- 800
- 900
- 1000
- 1200
What gives?
What are you complaining about? You get more memory dividers... what's bad about that?
600 @ 200fsb is the 2:3 divider
450 @ 300 is the 4:3 divider
Why should it be 1:1? You have 1:1 as well.
I really don't get what you're moaning about.
I don't understand why I get more memory dividers when I up the FSB from 200 to 300, while still using a 800 MHz FSB CPU. My understanding is that you don't get memory dividers lower than 1:1 if you have a 800 MHz CPU.Quote:
Originally Posted by lawrywild
The math doesn't go in the 450:300 case.
Results from benchmarking indicate that 450 in the 300 case is actually 1:1 and that "600" in the 300 case is actually 4:3 == effective 400 MHz (800 in DDR speak).
Probably because DDR2 doesn't exist at lower than 400Mhz rated ddr2 frequency.Quote:
Originally Posted by uOpt
(300/4)x3 = 225 x2 (DDR) = 450Mhz
Works to me :confused:
4:3 on 300mhz isn't 400Mhz, that would be 3:4....
I don't really understand you. Higher mhz = higher bandwidth. What are you comparing to? 975x memory performance is a lot better than other chipsets.
I am comparing with my BadAxe1 with the 4 major memory timings being the same. It's very clear that Asus' labels are not what you get. I'll post some numbers Monday.Quote:
Originally Posted by lawrywild
Looks more like the BIOS is just checking all available FSBrates and starts by showing from lowest to hightest. Weird that it gives more dividers but thats not bad news at all...the lower the FSB the more useless are some high Dividers^^Quote:
Originally Posted by uOpt
iLL
I have 4 sticks of OCZ 1066 DDR2 simms 1GB each I can use any 2 sticks and run memtest64 for at least 5 cycles (about 3 hours). However if I use all 4 simms at 1066. 800 or 667 the test will fail after about 10 to 15 minutes. I tried bumming up the voltage on the RAM from 2.20 for 2 sticks to as high as 2.35 volts for 3 sticks without any success. Any ideas?
Bios version P5W-DH-ASUS-Deluxe-2004,and FSB 330
Thanks,
ERIC
Try increasing the MCH volts. 4 sticks put more stress on the memory controller and the board. I had similar problems and ended up changing to aQuote:
Originally Posted by egandt
P5K but plenty of people are running 4x1GB no problem on the P5W.
Anyone have a quad running on this board? I have Q6600 G0 on order and an old revision P5W DH, with the lower MCH voltage options. I would be happy with 3.6 ghz, so around 400 FSB, doubt I'll be able to get higher without the higher MCH. I don't really want to buy a P35 board with X38 around the corner...
Here is a link to simple pencil mods to enable you to increase all your voltages if you need to.Quote:
Originally Posted by miochza
http://sg.vr-zone.com/?i=3876.
I have now bios 2105 , but it seems that everytime i boot my computer the bios resets , and i have to start my pc up by entering bios setup and choose Exite and DISCARD changes . I've tried everything , even changing the battery.
I wanted to flash up an older bios , but i couldn't do it with Asus Update or Asus EZ Flash , and Asus DOS just jammes .
PLEASE HELP ME :( :confused:
So, has anyone tried BETA BIOS 2206, yet?
Anyone wants to share what's changed?
Thanks!
Hadn't seen such a bios until now, thanks for link.
Rapidlink: http://rapidshare.com/files/45776470...eluxe-2206.rar
The search tool is your friend:Quote:
Originally Posted by TheSysX
http://www.xtremesystems.org/forums/...sh#post2143429
Hi there, i have a problem with VOLT DROP on the cpu/vcore,
i have a QX6700 @ 1.35v bios, during load in windows this drops to
1.30/1 and its very anoying in trying to get stable overclocks,
i could rase the vcore manuly but i want to use speedstep etc,
so this leaves with with no options to ajust the vcore,
is there anyway i can fix this? ive tried the pencil mod with no avail.
You must be not using a HB pencil or pencil modding the wrong resistor as the mod works if done correctly.Quote:
Originally Posted by lockeh
i take it you mod the one with the yellow line acorss it
i been doing the one above, using the method show in his link LOL
Quote:
Originally Posted by sesdave
Quote:
Originally Posted by GFORCE100
that pic doesnt resemble the layout of my board in that area?
Thanks man , problems solved now , but i can't get anymore with my E6600 above the 3 Ghz , normaly i could do 3.7 easy , how would that comme ??Quote:
Originally Posted by nicepun
BUMP.Quote:
Originally Posted by Bloke
May I ask whereabouts this is located on my board lol? :DQuote:
Originally Posted by GFORCE100
I tried them, they are buggy (i.e. vcore which wants to stay on Auto each time you get into BIOS and the HD Audio which disables each time you get into BIOS) but other than that I don't see anything better. I'll stick to 2103 until something good comes out.Quote:
Originally Posted by Bloke
think i killed my put the back plate on for my tt bt and now all it dose is move the fun a lil then off have to restart the power to get it to do it again . tryed clearing cmos deffrent cpu took the baack back ofthink it has a short but cant see when any ideas guess its new mo time
?????????????????Quote:
Originally Posted by w2richwood
2103 DOES support Q6600 G0!Quote:
Originally Posted by nicepun
http://www.ocforums.com/attachment.p...8&d=1183759000
SL9UM B3 CPUID String = 06F7h
SLACR G0 CPUID String = 06FBh
Awesome :cool:
found here: http://www.ocforums.com/showpost.php...9&postcount=37
Quote:
Originally Posted by miochza
I have a Q6600 and the best I can get is :
378 x9 3.4 Ghz stable @ 1.475 vcore
ram running @ 1:1 756mhz
FSB term voltage 1.40
MCH 1.75
I can get it to 395 FSB and the mem to 6400 just about 800mhz @ 1:1 but I have to put in 1.60 (this board like 1.54) on the Vcore and the proc gets a bit to hot pusing 70c on OCCT, above the 65.. but as soon as I punch in 400fsb, BSOD even if I get into windows it is extremely unstable...
Hey, not bad - which mobo BIOS version and which Q6600 stepping are you using?Quote:
Originally Posted by MarcusTaz
What the guy said above and what cooling?Quote:
Originally Posted by MarcusTaz
Bios 2206 Beta available:
ftp://ftp.asus.com.tw/pub/ASUS/mb/so...eluxe/2206.zip
Hi; I think I could use some help here :D
I am experiencing a rather weird situation atm.
I'm running my CPU at 3.6Ghz (9x400), and it is perfectly orthos stable when I test in small FFT's. But when I try doing large in-place FFT's to stress some RAM as well, it errors at about 8 minutes each time.
I have now ran memtest and it seems my RAMs are perfectly stable as well :O
Here's my voltages:
vcore: 1.450
vMHC: 1.55
vFSB: 1.40
vDIMM: 2.05
vICH: 1.05
I'm about to try 1.65 on the vMHC and 1.20 on the vICH now, think that might be the problem?
It's the cpu that's unstable. Small FFTs is not great at picking up errors on core 2's.
Was just playing around with my AMI bios tools and found out how to add support for G0 to older bioses :)
Shouldn't be hard to add Penryn support if asus decide not to do it for us ;)
Quote:
Originally Posted by MacClipper
Running 2004 bios and CPU is cooled with Swiftech H20-120 PREMIUM @ newegg for $149 in an Antec P180 case. Stepping I did not read the chip before I installed and mounted it, sorry but from the box I have a
SL9UM (I read that this has the lower thermal threshold :down: )
FPO/Batch L645G523
Version: D80856-003
Hope that helps... :up:
Going to try the new bios.
lawrywild, what do you think Asus is trying to accomplish by writing these new bios for this board? I mean 2004 seems very stable to me and if you go to Asus website our board is not even listed as a current product... I just paid $200 for this board (I am a late commer to Intel as I just sold my AMD rig) and it is not even listed as a current product, lol. I mean in all seriousness, what are they trying to accomplish? Oh and I am not complaining trust me, lol just thinking out loud here...
Here we go, I just modded 2004 bios to support G0 and some other mysterious cpu (penryn?). Anyone know what CPUID 0671h is?
If anyone wants to try this bios, I will send but use at own risk..
Larrywild no comment on why they are still writing new bios for our board? Sorry if it is an ignorant question..
Well, how exactly am I supposed to answer that question? I don't work for asus...
NP sir just asking.. It was an open ended question, like your opinion? No big deal moving along...
Oh and thank you for this great thread, it has helped me much!
Well, they are still producing the board, people keep buying them and alot of us own them. And we're still hoping for mem sub timing support.Quote:
Originally Posted by MarcusTaz
I can't remember if that image is of the P5W DH but it does show what you should be doing, with a HB pencil that is.Quote:
Originally Posted by lockeh
I would have to look at my board to see if the image is indeed that of a P5W DH but from memory I believe that various Asus boards look the same in terms of the voltage regulator section of the board.
I can confirm the mod works, as when I set 1.3750 in the BIOS, I get 1.37-1.38Vcore under load. Before it would vdroop considerably.
The info how this can be done is within this forum, just that not all threads state which resistor and how in plain English.
It's still a current mobo retailing at the shops, not quite EOL yet. Asus does support recent EOL mobo with BIOS updates for some time too, one reason why I buy their mobos.Quote:
Originally Posted by MarcusTaz
btw, yours is prob. a B3.
Lawry, send away if it's stable for you :P
I tried it, seems to work fine, can't spot any changes.Quote:
Originally Posted by Peanuts
Not sure why people say it disables the onboard audio or doesn't allow changing Vcore, haven't noticed anything like that here.
I don't have a G0 to test atm. I'm modding this 2004 into 2006, it has some extra stuff filled out like board revision etc.Quote:
Originally Posted by Gig4moller
If you want a customised bios tell me what you want in it. Is your board rev 1.03G?
I guess so, haven't bothered to check, all I know is that I have the 1.85vMCH revision :D where do I see?
And nah dont need anything special, just g0 & penryn support would be awesome :)
I don't know what the penryn microcodes are yet so that's not happening yet.
Then just G0 is awesome aswell :)Quote:
Originally Posted by lawrywild
it was the 2205 beta bios that did this so it looks like 2206 is ok thenQuote:
Originally Posted by GFORCE100
I'm running this stable at the moment :)
http://img4.shareavenue.com/getimage...c564ea4d59692a
Have my babies if you send that one to me :D
I'm gonna be able to flash it with AsusUpdate tho I hope? :p since I dont have a floppy drive
I'll leave this running till tomorrow morning, just to check everythings perfectly stable etc.
Should be able to, I just used EZ-Flash 2 with a thumbdrive.
PS: Best to flash from the original 2004 to modded 2004. So that you retain the original 2004 bootblock.