dencorso

+1 for NTLite You should register (TM or whatever) that fast!

Well, it sure seems as if both onboard GLANs are toast! And that would be why they were disabled. As for the heatsinks, you probably can either use other models or with some luck, remove them, mount the drive bay then mount them once more? A PIC of the problem would also be much welcome. So XP did run with no complaint after all? Great!

Maybe because, AFAIK, no single-core AMD is x64?

Be as it may, RegDelNull will find and, if told so, get rid of the so-called "undeletable" registry entry, so it cleans the partial infection.

Yeah, it's no fun... but life's like that. BTW, do buy a VIA VT6105, instead.

Considering less is more... nMoar

No, if all is working, I see no need to upgrade the BIOS now. Moreover, unless you need to do it because something does not work, it's not a priority and anyway it can be done latter at any time, if you ever decide to. But if the processors or part of the RAM are not correctly detected, then (and only then) it would be 1st priority.

Yes. I understand that. But... AFAIK, Powershell does NOT *itself* work on 9x/ME, that's my point. You see: 9x/ME support ended on Jul 11, 2006... while PowerShell was initially launched Nov 14, 2006... so, at least officially, it surely wasn't ever meant to work on 9x/ME. This being so, I'm pretty sure if nobody ever posted about PowerShell on 9x/ME (and that *is* the case) means nobody ever even unofficially has managed to have it run on 9x/ME.

Well, if you already added the new processors, then turn it on, with no HDD. If the new processors are recognized OK, you'll will see their recognition by the BIOS and the RAM count. Once you know that happens, you may go ahead. If the board refuses to POST, then you should go back to the processors it came with and try again. If it then POSTs, then a BIOS update should be needed. Of course, "POST" means "Power On Self-Test" and to POST means to perform it. As for the BIOS version, the easiest way is to use CPU-Z to determine it... or to use this old app, from true DOS (it can be run from a floppy!).

Sure. And I bet Powershell 1.0 does not run in native 9x/ME. Perhaps it does run, sort of, under KernellEx, but even if it does, I doubt there's even one user with Powershell installed in 9x/ME, or we'd already have heard about it here... Good to see you here, Mr. Jinje! And, BTW, do y'all remember RegDelNull?

First of all, take the IDE clone out of the room and store it safely. No matter what happens, don't even bring it into the room again, before consulting with us. Only use it again, in case of need, after we've collectively decided the best course of action. This is as important as actually having the clone! That said, I have a question, because I'm not much familiar with SuperMicro boards (I've serviced no more than half a dozen machines using them in all my life, they are really rare in around herel): does your old hardware post, then attempt to boot from removable media when there's no (viz. none at all) HDD conected to it? And if so, does it provide info on the monitor (say, display the memory test and the detected hardware) before parking on a message like "insert bootable media and press any key"? Or does it just beep and stop without providing any useful info? I ask that because probably your new (used) board behaves in the same way... So that, at this point, I'd test the old system for useful info with no HDD and if it actually provides it, then remove the old board and put in the new with the processors and memory it came and have it post to see it's OK, then substitute the processors and repeat this process... until I'd made sure all the new (used) hardware is working fine. Then, and only then, I'd proceeto add the SCSI subsystem (board and HDDs) and try to boot XP from it. I say this because, as you bought the best processors that board can use, you may have to flash the BIOS to its latest version, before the board can use them. If so, it'll post OK with the original processors it cam with, but fail to post with the better ones. I've seen that happen more than once. As soon as you're sure the new hardware is OK, I think you're ready to add the Windows XP disk.

Yes! I was thinking abour removing the card with the HDDs still connected to it. But disconnecting the drives has the same effect, of course.

Were I you (whom I clearly am not), I'd clone the disk again (and just after cloning, remove it from the system). Then I'd reboot the normal system to make sure everything is OK. Then I'd remove the SCSI controller and HDDs, add the IDE containing the clone stand-alone and try to boot the system again, this time using the IDE (which should be the only HDD on the machine at that point). All going well, you can say you've mastered the cloning part of the process. Them we should agree on a procedure for the board exchange, before you actually attempt it. What we're trying to do is to have you avoid the pitfalls we know are potentially there. Prevention is always better than recovery, right?

Another option is Damien Guibouret's Partition Saving... It runs from WinPE, from linux and even from DOS, and seems to me very full featured, and is likewise free. I don't have 1st hand experience with it, though, because I'm a long-time Ghost user.

Queen - The Great Pretender

Great news! You both rock!

It's moving for me both here and at its original location. It's just a real clever animated .gif, so it should be moving for you, too. Try to reboot the system and see whether it starts moving again, then let me know, OK? Good luck!

Repair Install would send your system back to SP2 (or SP3, if you do what submix8c suggested). Repair Install is not an option IMO. My idea of using a 2 HDD was for you to get the new board working (even if without a case) before decomissioning the old one... if you intend to actually move the SCSI card and the HDD(s) connected to it to the new board, an image (two, actually, just in case) should suffice. In any case you need a PE or some other means of booting either PC without using your current instalation, in order to be able to redeploy the image so many times as it may prove to be needed.

I do believe big things may happen by accident, although I always marvel at how Murphy's Law (which is not really a law) appears to hold most of the time. However, in the specific case of Win 8 and all its derivatives (whatever they may be called: Update, SP, etc.), sometimes it seems to me as if MS had put a goat in the house... so that I'm tending to agree with you on this one. However, instead of just putting Metro in, they also took away the interface everybody loved, and part of the eye-candy (aero-glass) to obtain maximum effect, and will bring it all back slightly bettered (or even just as before) latter on, just to be hailed as geniuses and saviours. And why would them do so? Precisely because they do not have anything really better than 7 to offer, so they flop 8 to send a later windows soaring into the clouds (did I say clouds?).

CAUTION is advised! Lots of it! It's almost a sure bet XP won't "just work"! Make a full image of your XP boot drive (preferably a dumb byte-by-byte image of the whole drive). Verify that it's good and save it. Make another image, just like the first one. Restore it to a same-size same-geometry (preferably same-brand and same-model) HDD, swap it with yours in your current board an see that it works OK. When you've mastered producing working clones of your current XP (without destroying the original), then you'll be in grade to experiment safely with your new board. Transplanting XP from one board to another is tricky when the're reasonably similar (as may be your case, althought it's sometimes difficult to define "reasonably similar"), and is utterly impossible when they are too different (but only trial-and-error can tell whether a board is "reasonably similar" or not). Replace Motherboard on a Windows XP System Move Windows XP Hard Drive or Change Motherboard Without Getting a Blue Screen STOP 7B Error - Raymond.CC KB314082 - You receive a Stop 0x0000007B error after you move the Windows XP system disk to another computer How to change your motherboard and avoid reinstalling Windows XP (Intel to AMD) (I think most of this latter article does not apply to your case, however...)

If you can run scandisk in true DOS and it finds no error, then I have news for you: What's happening in Windows is that "some software is actually writing to disk from time to time". Really. And only you, who are on site, can find what is it.

No. If at all, early Aug MS may actually release Windows 8.1 Update 1 SR1, but that's still far from certain.

+Lite

. . .