-
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
Anything special need to be done before/after flashing your BIOS?
- Thread starter mitchafi
- Start date
ScrapSilicon
Lifer
if your OS is bugfree ..should be fine..
imported_raybay
Member
Re-set to basic settings; be sure your power is secure and that there is no lightning in the area. Beyond that, it is automatic. Watch your screen for error messages or abnormal reports. Then reboot. Check your setup screen to be sure the new BIOS is recorded.
MichaelD
Lifer
Yep. Just to add to that.
NEVER flash your bios while overclocking. That's asking for trouble. I recommend going intot he BIOS first and selecting "Load Optimized Settings", rebooting, then flashing.
Also, make sure the PC is connected at least to a surge surpressor powerstrip; a UPS is the best thing.
Any voltage spike while flashing the BIOS will most probably result in a dead board.
Other than that, it's an easy and fast way to gain new functionality and performance. Go for it.🙂
Alright just made my first attempt at flashing the bios and I get this error:
Rom file ROMID is not compatible with existing BIOS ROMID.
Here's exactly what I did.
1) Used a blank floppy to make a bootable disk
2) Copied Afudos.exe over to the floppy (latest version)
3) Copied Bios Version 1007 onto the floppy (K8V1007.ami)
4) Booted from floppy
5) Typed /iK8V1007.ami
6) Got above error
What did I do wrong?
Rom file ROMID is not compatible with existing BIOS ROMID.
Here's exactly what I did.
1) Used a blank floppy to make a bootable disk
2) Copied Afudos.exe over to the floppy (latest version)
3) Copied Bios Version 1007 onto the floppy (K8V1007.ami)
4) Booted from floppy
5) Typed /iK8V1007.ami
6) Got above error
What did I do wrong?
What is WinFlash? There is this feature called E-Z flash that is supposed to be simple. You press Alt-F2 during post and then type the name of the file and it will automatically flash. However, when I tried it told me it was about to flash R350 Samsung Memory (my 9800 Pro) so I quit immediately. Scared the hell out of me.
Winflash is a program to flash your bios in the windows enviroment. Hold up, lemme check Asus's site...I think they have their own windows flasher...
🙂
Edit:
Ok, apparently stupid Asus and their propietary bioses don't allow for windows based flashing like almost all other branded boards...sigh.
EZFlash is probably your best bet. Put the 1007 bios file (K8V1007.ami) on a blank formatted floppy. Leave the floppy in the drive, reboot, and when the bios comes up hit [ALT] + [F2] and follow the prompts. If that doesn't work, you might have a bios flash protection option that needs to be disabled in your bios.
Edit 2:
It turns out Asus does have a bios updating program that can be used in Windows, and will automatically d/l the bios and update it for you. Here is the link. Thanks to mechBgon for the link! 😎
Asus Update Program
🙂
🙂
Edit:
Ok, apparently stupid Asus and their propietary bioses don't allow for windows based flashing like almost all other branded boards...sigh.
EZFlash is probably your best bet. Put the 1007 bios file (K8V1007.ami) on a blank formatted floppy. Leave the floppy in the drive, reboot, and when the bios comes up hit [ALT] + [F2] and follow the prompts. If that doesn't work, you might have a bios flash protection option that needs to be disabled in your bios.
Edit 2:
It turns out Asus does have a bios updating program that can be used in Windows, and will automatically d/l the bios and update it for you. Here is the link. Thanks to mechBgon for the link! 😎
Asus Update Program
🙂
VirtualLarry
No Lifer
I agree with that, definately don't overclock. I actually down-clock the FSB and disable external caches, and disable some of the other things like "PCI delay transactions", and power-management (I *always* disable that, on all of my systems), and depending on the video card and some other things, I tend to disable caching/shadowing of some UMB regions, and also disable any un-essential onboard periperals.
But I think you meant to suggest loading "Failsafe", or "Default" settings, NOT "Optimized". On some (many?) BIOSes, "Optimized" sets everything (especially memory timings) to the fastest settings, which the current hardware and memory may not be capable of operating stably at. This could almost guarantee a corrupted BIOS flash.
Totally agree. I wouldn't flash a system's BIOS without it hooked to a UPS. The risk is just too great.
To the OP:
I would also suggest, if it is possible to flash the BIOS in DOS, using an old DOS boot disk, then do that. Flashing anything inside of Windows is extremely risky (except storage devices and external modems, because their internal microcontroller firmware actually controls the flash-writing process, not the main CPU). DOS is much safer, since only the flash program is running, nothing else is running in the background. (That's why I also disable un-essential onboard hardware in BIOS before the flash process.)
If you ARE going to flash using a DOS boot disk, use the Win98se one, and put your flash program and new BIOS onto another floppy. Boot the Win98se boot disk, and then copy the flash program and new BIOS *into the RAMDRIVE* that the Win98se boot disk creates. (I suggest saying "no" to loading te CD-ROM drivers.) This largely eliminates the possibility, that you could have disk read errors, while reading the new flash BIOS directly off of the floppy during the actual flash process.
Before the flash, you should run the flash program, and make a backup copy of the current BIOS, and store that onto another floppy or something, don't leave it in the ramdrive. That can help you to make a flash-restore rescue disk on another machine, in case you need it.
Also, make sure to use the command-line switch on the flash program, to clear the ESCD data (PnP config data), and also to clear the CMOS. As an extra precaution, after I flash sucessfully, I also power-off, and use the hardare jumped to clear the CMOS. Then I boot up and use "Set BIOS Defaults" or "Failsafe", reboot, and then start re-setting all of the BIOS setings back to what they should be.
All in all, it should be fairly painless, and some of the things that I've described above are just extra precautions. It won't necessarily fail if you don't do those things, but they can help decrease the risk of a failed flash, or a mis-configured CMOS after a sucessful flash, which can prevent proper booting afterwards.
VirtualLarry -
I disagree on the Windows flashing. It's no more risky than DOS flashing. I've done it tons of times and it's much easier and straight forward for the casual user. If it was so "extremely risky", it wouldn't be included on the motherboard CD's of most newer boards. A lot of people hang on to DOS flashing like it's the only safe way to flash, and that is incorrect. As long as your windows enviroment is sound, you won't have any trouble.
No offense, but you sound like a big time "play it safe" kind of person. You would never flash a bios without a UPS hooked up? I mean c'mon man...
I disagree on the Windows flashing. It's no more risky than DOS flashing. I've done it tons of times and it's much easier and straight forward for the casual user. If it was so "extremely risky", it wouldn't be included on the motherboard CD's of most newer boards. A lot of people hang on to DOS flashing like it's the only safe way to flash, and that is incorrect. As long as your windows enviroment is sound, you won't have any trouble.
No offense, but you sound like a big time "play it safe" kind of person. You would never flash a bios without a UPS hooked up? I mean c'mon man...
Did you just let it download the new bios itself, or did you try to use the file you d/l'ed earlier. You may have snagged the wrong one...maybe for the non-deluxe model?
If the bios updater d/l's from the internet and still won;t flash, you might have an option in your bios that blocks bios flashes. Also, having anti-virus protection on your bios can hinder a flash.
Edit:
Here's a direct link for the 1007 bios for the K8V Deluxe...
Click Me
🙂
Jesus. This is amazing. Messing around with the AsusUpdate utility I checked my bios and realized I have an Asus K8V BASIC. I've been thinking I've had the Deluxe version since I made this computer. Guess I put the wrong thing in the cart on newegg. Well, I'm going to flash now with the right bios. K8V 1003. It appears to be the latest for the basic K8V. Sorry I wasted all your time. I'm a moron 🙁. Also, what's the difference between a K8V and a K8V Deluxe anyways. A few features...or is there a performance difference.
-Moron
-Moron
Here are the product pages for the two boards. It's weird, the USA Asus site doesn't list the K8V basic, just the K8V Deluxe and the K8V SE Deluxe. It is listed on their global site though...
K8V
K8V Deluxe
Just looking at those pages quickly, it seems like the K8V lacks firewire, a Wi-Fi slot, and uses a Marvell GB LAN chip versus the 3Com on the Deluxe.
K8V
K8V Deluxe
Just looking at those pages quickly, it seems like the K8V lacks firewire, a Wi-Fi slot, and uses a Marvell GB LAN chip versus the 3Com on the Deluxe.
VirtualLarry
No Lifer
Well, I would like to disagree with you. 🙂
It *is* more risky than DOS flashing, for the simple reason, that a directly-connected (directly-addressable) flash ROM chip, has certain somewhat timing-critical programming routines. If this programming-loop code is run in Windows (a multi-tasking OS), then it is possible, however unlikely, that some other task could cause the current programming thread to incur latecy that violates the timing guidelines of the programming algorithm for that particular chip. In DOS, which is a single-tasking, pretty-much dedicated OS, there is no additional risk from background tasks interrupting foreground tasks long enough to screw something up.
I'm not going to go so far as to say that Windows' flashing programs simply don't work, because that wouldn't be correct. But DOS flashing programs, barring sudden hardware failure or user error, work 100% of the time. That is not true of Windows' flashing programs. Also, at least when they were first introduced, many of the Windows' flashing programs had severe bugs, as compared to their DOS counterparts.
The name of the game for "safe flashing", is to remove as many unrelated components, processes, etc., as possible, in onder to reduce the risk as much as possible that some external event will screw up the flash process. While a flash-programming is in process, it is alsolutely critical that nothing interferes. This can be virtually guaranteed in DOS, while the same cannot be said of flash operations in Windows.
(I make an exception to this rule, as I mentioned, for devices that contain their own microcontroller. In those cases, the main CPU in the machine simply uploads the new flash-programming data to a buffer onboard the device, and issues the flash-programming-start command, and then the microcontroller onboard the device takes over, and performs the flash process itself. Therefore there is no risk that latencies that could affect the main CPU, will affect the device's microcontroller. Of course, while flashing, you should not attempt to use the device for other purposes, and generally should power-cycle the device before next use.)
Btw, I don't think that I said that it was "extremely risky", only more risky, compatively speaking. That is an observation that I will stand behind, and I believe that empirical evidence will back me up on that - the number of failed Windows' flashes vs. the number of failed DOS flashes, that are not attributable to user error.
Ok, double-checking, I did originally say "extremely risky". Ok, I guess I exaggerated slightly, for the sake of safety. Sorry. I guess I should have said "more risky". I guess I know how flaky Windows' can be at times, and how very timing-dependent flash-programming routines usually are. Modern byte-programmable chips are a lot less risky to flash, than older sector-erase or full-erase chips. Imagine starting the flash-erase process, on the system BIOS chip, and then Windows decides to BSOD, for some reason or another - maybe your HD had a marginal sector in the pagefile, and suddenly your HD decides to report to the host system that the sector has finally turned "bad"... BOOM! Your system is unbootable. That is far less likely to happen in DOS, assuming that your hardware isn't flaky, and your power is good.
(That HD scenario is very real, btw, and cannot be avoided while inside Windows. It can be entirely avoided by flashing from DOS, using a boot floppy and a ramdrive.)
Forgive me, but I pay good money for good hardware. I don't feel like playing "Russian [flash] roulette" with them. You never know when the power might glitch. If it happens at the same time you decide to flash your mobo, your system ends up dead. This can be entirely avoided, by thinking ahead a little. I don't see why doing so, is necessarily wrong.
Besides, it's my personal opinion, that if you value your computer, you would want to feed it "good" power too (to avoid a whole host of other potential power-related problems), so I suggest that anyone with any kind of decent system, owes it to themselves to run with a UPS full-time anyways. I have several. So if you do PC tech work for other people, it's not too much effort to just plug it into the UPS before flashing.
If you have to do work on-site for someone else's machine, and you need to flash the BIOS, then that's, I suppose, a different story. I would present the tradeoffs and risk involved to them, and ask them if I should take more time to do the job (right, by obtaining the UPS, if one is not available then), or ask them to assume all the risk, should the flash process fail due to power-loss if they cannot wait to get the job done. It's their machine, it's their choice. I can advise, but I don't make that choice for them. So I guess when I said "never", I was speaking primarily in the contenxt of my own machines.
You know, everything you said is valid, but you are still taking bios flashing safety to the extreme IMO. I mean there is a chance a tree could fall on your house during the 30 seconds it takes to flash a bios...should I cut down all trees in range before I do a bios flash? Now that I think about...a plane could fall out of the sky...maybe I should flash in a restricted airspace zone? 😛
IMO, bios flashing shouldn't be taken lightly, but you are really making it out to be this life or death major operation that one slip could result in utter doom. Your reasoning is sound, but IMO, you are being way more cautious than needed. If you want to do your bios flashes that way...then fine. Your opinion is valid as is mine, and you are welcome to it. However, I object when someone here is asking for simple bios flash help, and you go on and on with paragraphs of what you think are major safety protocols that need to be followed. I mean we aren't talking mission critical servers here. For a casual user who just wants to flash to the latest bios, either way works fine. As I said, as long as your windows enviroment is stable and sound, you will be fine using windows flashers. The bios chip is not even in use once you get past it in the boot sequence. I do agree they were spotty when they first came out, and I wouldn't suggest a windows flasher in a Win9x enviroment, but all the major board makers are including the windows flashers with their boards, and it's plain and simple, becoming the standard..IMO. As more newer PC's start coming without floppies, I can see this increasing in popularity.
If you are that worried about bios flashing, maybe you should spend $20 on a bios savior, so even if you did have a failure, you would be all set. I think we need to agree to disagree on this. We just have a fundamentally different view on bios flashing. I've done hundreds of bios flashes...using official and non official bioses, with nothing but an power strip plugged into a outlet, and I've never had a problem. I also pay good money for my hardware, and I have even more incentive to be careful because most of my boards and hardware are modded to a degree, so I really wouldn't be able to RMA. Could it happen...sure...is it likely...not really.
Anyways, no hard feelings...we just don't see bios flashing the same.
BTW - Just last week I hot swapped a bios chip and did a flash in windows...I bet that procedure would give you fits eh?
😉
IMO, bios flashing shouldn't be taken lightly, but you are really making it out to be this life or death major operation that one slip could result in utter doom. Your reasoning is sound, but IMO, you are being way more cautious than needed. If you want to do your bios flashes that way...then fine. Your opinion is valid as is mine, and you are welcome to it. However, I object when someone here is asking for simple bios flash help, and you go on and on with paragraphs of what you think are major safety protocols that need to be followed. I mean we aren't talking mission critical servers here. For a casual user who just wants to flash to the latest bios, either way works fine. As I said, as long as your windows enviroment is stable and sound, you will be fine using windows flashers. The bios chip is not even in use once you get past it in the boot sequence. I do agree they were spotty when they first came out, and I wouldn't suggest a windows flasher in a Win9x enviroment, but all the major board makers are including the windows flashers with their boards, and it's plain and simple, becoming the standard..IMO. As more newer PC's start coming without floppies, I can see this increasing in popularity.
If you are that worried about bios flashing, maybe you should spend $20 on a bios savior, so even if you did have a failure, you would be all set. I think we need to agree to disagree on this. We just have a fundamentally different view on bios flashing. I've done hundreds of bios flashes...using official and non official bioses, with nothing but an power strip plugged into a outlet, and I've never had a problem. I also pay good money for my hardware, and I have even more incentive to be careful because most of my boards and hardware are modded to a degree, so I really wouldn't be able to RMA. Could it happen...sure...is it likely...not really.
Anyways, no hard feelings...we just don't see bios flashing the same.
BTW - Just last week I hot swapped a bios chip and did a flash in windows...I bet that procedure would give you fits eh?
😉
VirtualLarry
No Lifer
Well... can you think of one other singular life-critical (to your computer) operation that you could perform, that would be less likely to trigger Murphy's Law? Sometimes the Universe can be a funny thing... but you don't want to end up as the butt of one of its jokes, because the joke will end up on you.
For the most part, it *is* a "life or death operation" - it's like a heart transplant for the motherboard. One major screwup, and you could have a dead mobo.
Sure. Some people don't wear anti-static wrist straps, some don't take any ESD precautions at all.
Some people don't wear seat belts. Hey, I mean really, what are the odds that suddenly someone else's car will lose control and careen directly into yours, causing yours to flip over. I mean, it's never happened to "me", so what are the odds, really? Why bother wearing seat belts, I mean, what an annoying pain. Based on those odds, they sound hardly necessary.
Trust me, you'll change your tune the first time you have a flash go bad, especially if it's a Windows' flash procedure.
Well, in my "professional opinion", those *are* the protocols that needs to be followed.
There's the difference between the "home garage mechanic" take on things, and the "trained dealer mechanic". The results of the work can often be the same, but there are certain additional procedures that can be take to mitigate and reduce unnecessary risk, and ensure a much greater likelyhood of a "guaranteed good flash" operation.
But you *are* taking several major, additional risks, that aren't necessary, and theoretically *could* screw up the flash. By using my method, you eliminate those risks.
Again, refer to my driving without seatbelts analogy. More than likely, you will get to your destination safely either way. But on the off chance, if something *does* go wrong... wouldn't it be better to reduce the risks?
Why would/should I waste additional money? If I use my method, there is a greatly-reduced risk of anything going wrong. Perhaps *you* should consider purchasing a BIOS Savior, you might just need it!
Plenty of people don't believe in seatbelts either, and a slightly-smaller percentage of them also has "never had a problem". (Those who do have a problem, generally don't live to "spread the word" about the issue.)
Fair enough, but I just felt that I also had to give my "professional opinion" in this thread.
I've had to do a "hot flash" too. I suggest using a chip-puller to extract and insert the chip (after using a screwdriver to loosen the DIP slightly, with the power-off at that time of course), tends to avoid possible pin-bending from manual attempts at removal and insertion.
I would never do a hot-flash while booted in Windows though. You never know when a possible mis-insertion of the chip could cause a hard-freeze of the entire system, and you could lose data. (Since stuff is going on in the background in Windows - darn those pesky unnecessary additional risks eh?)
With DOS, no big deal, just immediately power-off and start the procedure again with a boot floppy. No risk of extra potential data-loss from the procedure.
Dude....stop..please. This is the most long winded discussion of a simple issue...EVER. You have your opinion....I have mine. I have been doing bios flashes for more than 10 years with no issues. Like I said above...you want to be that careful, fine. It is NOT needed for everyone else to follow such guidelines...if they want to fine.
No offense, but you seem to like to make a simple issue into a big discussion with long winded replies that make you look technically superior. If you want to think you are..then fine by me.
Ohh..and you use a chip puller to change the bios chip...WOW! I never knew that! Oh wait...I bought one like 8 years ago, and another a few years after that for the newer style chips. As for not doing anything in Windows with the bios chip out...you do realize once you get past the loading part of the bios and boot into the OS, the bios chip is DOING NOTHING AT ALL.
Regardless, all your precautions are a moot point if you simply bought a bios savior. Then it would make no difference if the flash got messed up....oh and it's only $20.
*shrug*
You strike me as the type of person that is over cautious about everything...ever hear the saying.."No risk, no reward?"
Well, I guess I'll give up now, I'm obviously not up to your technical level...so I should quit while I'm behind.
*sigh*
:roll:
PSA:
***VirtualLarry is now the resident Bios expert. Unlike the rest of us hacks, he is a trained professional, and is ultra safe. Your best bet is to take anything he suggests as the "official" and "proper" way to do things.***
Also, all further advice by me should be totally disregarded if it runs contrary to what VirtualLarry suggests as he is obviously technically superior to me and most of what I say is just pure crap anyhow. Plus, my responses are too short and to the point anyhow.
Thanks.
:disgust:
No offense, but you seem to like to make a simple issue into a big discussion with long winded replies that make you look technically superior. If you want to think you are..then fine by me.
Ohh..and you use a chip puller to change the bios chip...WOW! I never knew that! Oh wait...I bought one like 8 years ago, and another a few years after that for the newer style chips. As for not doing anything in Windows with the bios chip out...you do realize once you get past the loading part of the bios and boot into the OS, the bios chip is DOING NOTHING AT ALL.
Regardless, all your precautions are a moot point if you simply bought a bios savior. Then it would make no difference if the flash got messed up....oh and it's only $20.
*shrug*
You strike me as the type of person that is over cautious about everything...ever hear the saying.."No risk, no reward?"
Well, I guess I'll give up now, I'm obviously not up to your technical level...so I should quit while I'm behind.
*sigh*
:roll:
PSA:
***VirtualLarry is now the resident Bios expert. Unlike the rest of us hacks, he is a trained professional, and is ultra safe. Your best bet is to take anything he suggests as the "official" and "proper" way to do things.***
Also, all further advice by me should be totally disregarded if it runs contrary to what VirtualLarry suggests as he is obviously technically superior to me and most of what I say is just pure crap anyhow. Plus, my responses are too short and to the point anyhow.
Thanks.
:disgust:
VirtualLarry
No Lifer
I felt I had to correct the inaccuracies of your post, and explain my corrections, because you didn't seem to understand why they were inaccurate.
(Basically, it boils down to the *fact*, that there is less risk from flashing using a DOS boot disk or a recent-date BIOS's built-in flash support, then using a Windows' flasher. This is not simply my opinion, it is stated on a number of respected technical websites, that if a user is capable of doing so, that flashing in DOS is better and less risky. Many guidelines also suggest connecting a PC to a UPS during a flash procedure, if possible.)
Ok, fine. I was simply suggesting that as an additional tip. I've never seen that suggested or described anywhere as part of the "hot flash" procedure. I've found from personal experience that it makes hot-flashing easier and less error-prone (less risk of bent pins), or some pins not making contact when inserting.
Not true. The data stored in the flash ROM is copied to shadow RAM during boot (actually, decompressed, BIOSes expand to a much larger resident RAM image than their ROM size these days), that is true.
However, the physical chip/socket, is still part of a live circuit. The processor might not be accessing the chip, but if you mistakenly connect or fail to connect some pins, you could cause a hard-freeze at the hardware level.
You really don't get what I'm saying, do you? A BIOS Savior does nothing at all, to mitigate the risk of dataloss during a hot-flash procedure while in Windows, for example.
Yeah, exactly. I think that is the most perfect way to sum up how you approach risk-factors during critical operations. Me, I try to be careful and professional about things. You? Well, I'm not going to tell anyone how to do things, but perhaps someone can learn somethiing from my suggestions.
Sorry, I don't see the point of treating PC maintenance and repair, as a risk-filled thrilling experience like skydiving or extreme mountain-climbing.
You and I both know that I said nothing of the sort.
Well, maybe they should... if you consider your methods to be ones that intentionally add a "thrilling risk" to the operation in question.
You should continue to drive without seatbelts too, I mean, no need to decrease the "thrill" of driving, right?
PS. Ever heard the phrase "safety first"? I'm guessing, probably not. That's really the only point that I've been trying to make, this entire time. If you don't agree with that philosophy personally, fine, I can agree to disagree. But at least be honest with other readers of this thread, and admit that you *are* willingly taking *more* risks, by your method, even though it may be faster and more concise to explain.
PPS. Would you go to a doctor's office, and allow them to stick a needle in you, without applying the proper topical antiseptic first? I mean, it's so much more hassle, and complicates the procedure. Plus, assuming that the person keeps their skin clean enough anyways (analogy to a "clean" Windows' installation), there really shouldn't be any (truthfully, "any additional") risk involved.
I'm not trying to claim any technical superiority, I just want people to get their facts straight, that's all.
Especially considering the context in which this was originally brought up, by a relative newbie, then it would seem that the safer procedure should be suggested, because there is far less risk involved for them to possibly screw up with. If you know what you are doing (and I have no doubt that you do, as well as I or any other technical professional), then a streamlined procedure, even one involving more risks, could be acceptable, as long as one is very careful not to screw up. However, I don't personally trust myself 100%, especially when operating on someone else's equipment, so I try to minimize the risk of failure as much as possible.
Edit: fix - unbolded quote
Edit 2: If anyone doesn't believe me, and wants to find out for themselves, with a second opinion, ask around on the Wims' BIOS forums, about what they think about Windows' flashers vs. DOS/BIOS ones.
Edit 3: For the record, Insane3D's post, the tenth in the thread, seems perfectly correct to answer the OP's question. I take no issue with that. He obviously knows what he is talking about as well. I just took issue with one major point that I mention below.
Short summary:
How this all apparently got started, was that MichaelD erroneously suggested loading "Optimized Settings" in the BIOS before flashing. I'm sure that he probably meant "Default" or "Failsafe", because sometimes Optimized sets the tightest memory timings possible for the chipset, which may be unstable with the currently-installed RAM, thus leading to a corrupted flash. I also added my own thoughts on flashing using a DOS boot disk. Among those thoughts, I commented on the relative un-safety of flashing a BIOS from within Windows.
Insane3D then commented that flashing from within Windows was no less safe than flashing from DOS. I took issue with the technical correctness or lack thereof in that statement, thus leading to this whole big mess in the thread, as I tried to explain the technical reasons and possible scenarios why his statement was incorrect, along with me admitting that I had exaggerated the issue slightly with one of my original posts.
I guess if something like this is ever FAQ'ed, then it should cover the simple, fast, but risky method, as well as the complex, slower, but safer method.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 25K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 24K
-
-
