Stop 7B bluescreens, or HAL bluescreens? That's the key difference. Typically XP won't boot for two reasons - HAL, or disk controller. You removed the disk controller issue, so I'd bet the HAL changed.
What did you have, and what did you upgrade to?
What did you have, and what did you upgrade to?
bob4432
Lifer
- Sep 6, 2003
- 11,726
- 45
- 91
this was some time ago and i can't recall the hardware, then i found this way and have been using it since, sorry i can't be more specific
so you are saying that instead of the sysrep when i build my a64 machine, from my current p4 rig, i should just put in the new m/b & cpu combo since the hal and hdd controller will be the same, and all should work fine?
what about all the old drivers, i thought that is what sysrep took care of
I'd be surprised if the HDD controller would be the same. Are you sure they're really the same? If both are the same and the ACPI mode is the same (I roll that into "make sure the HAL's the same" but I note in http://support.microsoft.com/default.aspx?scid=kb;en-us;302577 that MS does not do this) then yes, that will let you boot the box, and from there you can splash your drivers onto the box.
Yes, that's exactly how I do it. My systems have the same HAL/ACPI, so I simply take my RAID setup, move it to the new hardware, and I'm good to go after a little bit of driver redetection and some reboots.
I don't. DriverCleaner and such are a waste of time, IMHO. The load of the basic driver is completely PnP/dynamic in 2000 and later OSs. For add-in programs (ie stuff that lives in the system tray and the like) just use add-remove control panel to get rid of it.
It does that and much, much more - you can preinstall a hundred drivers on that system, and it will intelligently parse them all and pick and choose the right ones, among a hundred other things (want to change your license key/PID? Easy). Sysprep is a wonderful tool. The problem is that it redoes a lot of things in your computer that you may not want redone for a one-off move - it basically makes the computer unique again, and removes a lot of personalization.
I think it's massive overkill for the very simple task of moving a motherboard.
I think it's massive overkill for the very simple task of moving a motherboard.
- May 21, 2003
- 14,644
- 10
- 81
How? The process is: supported by MS (where your method isn't), quick, and easy.
It takes less than 10 minutes to run, and that's including downloading it. The HAL issues isn't a problem on many machines, most are APIC HALs, like yours.
I mean really, if you don't have faith in this process, you are going to HATE Vista's installer. It's 95% the same, the Vista installer doesn't have the HAL issue which will be nice. As an added bonus, much of what you learn about sysprep here will transfer to Vista. You'll be that much closer to knowing how to edit the Vista setup.
I think it's worth learning and being familiar with the process for that reason alone... At the very least, this is another tool in your bag, use it or not.
Originally posted by: Phoenix86
How? The process is: supported by MS (where your method isn't), quick, and easy.
It takes less than 10 minutes to run, and that's including downloading it. The HAL issues isn't a problem on many machines, most are APIC HALs, like yours.
I mean really, if you don't have faith in this process, you are going to HATE Vista's installer. It's 95% the same, the Vista installer doesn't have the HAL issue which will be nice. As an added bonus, much of what you learn about sysprep here will transfer to Vista. You'll be that much closer to knowing how to edit the Vista setup.
I think it's worth learning and being familiar with the process for that reason alone... At the very least, this is another tool in your bag, use it or not.
RE: Your support comment. Please read: http://support.microsoft.com/default.aspx?scid=kb;en-us;828287 This states that the Sysprep method isn't supported for machines in production, so I don't see why you mention supportability.
What really happens when you move motherboards? If the HAL/ACPI isn't the issue, why wouldn't it boot? The typical error is a STOP 7B, inaccessible boot device. And by preloaded the hard disk drivers, you remove that as a problem.
In other words, why use Sysprep if you don't need to, when there are easier ways?
I have full faith in Sysprep. I know what it does and how it works, and I've supported it for a year, and I've used it in production environments as the architect to design a process that, by now, I'm sure has resulted in thousands of flawlessly sysprepped PCs. And I don't think most people here really want to learn about Sysprep if doing a one-off move.
I believe it's overkill for such a simple operation. Again, as long as the HAL is the same and the destination machine will boot from a standard IDE driver or the default IDE driver, typically noaction must be taken. If that's not the case (but the HAL is the same), just preload the correct disk driver.
I think we'll have to agree to disagree on this one.
FYI, (for XP) you don't need the PnP switch anymore now that everything's PnP; it's mostly for older ISA devices. It's automatic.
Using nosidgen would probably be wise too, in case any software cares about the SID on the box changing.
- May 21, 2003
- 14,644
- 10
- 81
I think that line about production machines has recently been added. Though that's VERY good info I wasn't aware of. Thanks.
Nope, those are about the only issues I have seen.
I'm not saying there are problems with your method, and perhaps it's faster. Both seem to be fast enough, however. I think we'd be comparing processes that both take minutes to perform.
Like I said there really isn't much to learn, run an exe, select some options, move the hardware, boot, provide new drivers. Not any more complex or difficult to learn than your process. You don't have to understand how it works to follow the process. If you do learn how it works, you can apply that knowledge elsewhere. Doubly so with Vista.
Really you are making it sound like it take hours or something. Overkill or not we're now beating a dead horse.
Unfortunately it appears you quoted my post prior to my edit being saved; it changed a bit; review if anything interesting changed.
- May 21, 2003
- 14,644
- 10
- 81
About the PNP switch, I should comment that more. It does add a bit of time to the detection process, but my mind was firmly set in "compatiblity" mode there. Just as soon as I recommend to remove it, I'll see a post "So I have this ISA something or other".
As far as SIDs go, I'd rather people kept them as well. Will change it (shortly, no time now ).
As far as SIDs go, I'd rather people kept them as well. Will change it (shortly, no time now
).
bob4432
Lifer
- Sep 6, 2003
- 11,726
- 45
- 91
ok, i went ahead and did do the sysrep way just to learn it and checked the mini-setup, pnp and also the nosidgen. i booted up loaded the newest bios for my board and all appeared to go ok. then windows just restarted without getting past the boot screen. the next time it asked me if i wanted to start in safe mode so did. during the safe start up i get a message that states "Press ESC to cancel loading SPTD.sys" then asdfjkd9.sys and then a347bus.sys. if i let safe mode start up all the way i just get a little window that says "the system is not fully installed. please run setup again" with just an ok button. if i hit ok, it starts all over again and just stays in this loop.
the hardware i went from was the rig in my sig wit ht turned off to a nf3/opteron 144 setup. i transfered over my scsi card, but both the optical drive and storage hdd are now on different controllers if that matters.
i still have an image if i need to restore from it but if possible i would like to do it all in the new rig since i changed cases too.
thanks in advance for the assistance,
bob
the hardware i went from was the rig in my sig wit ht turned off to a nf3/opteron 144 setup. i transfered over my scsi card, but both the optical drive and storage hdd are now on different controllers if that matters.
i still have an image if i need to restore from it but if possible i would like to do it all in the new rig since i changed cases too.
thanks in advance for the assistance,
bob
Want to go back to the image so we can see if it will work that way? You'd just need to confirm the disk controllers are the same (ie I assume the 36GB SCSI disk is your boot disk) and the HALs are the same, and you should be all set.
bob4432
Lifer
- Sep 6, 2003
- 11,726
- 45
- 91
that is what i will do. i am actually in the process of using acronis boot disk, navigate to my server that has a 01/04/06 image of the c drive and go from there, and yes, the scsi hdd is the boot drive.
any idea why it is in this constant reboot loop?
thanks,
bob
I'll let Phoenix86 answer that one.
Let's see if we can get it working. Do you know if the HAL is the same? That's an obvious first step, although since you've a backup image, it can't hurt to try.
Let's see if we can get it working. Do you know if the HAL is the same? That's an obvious first step, although since you've a backup image, it can't hurt to try.
bob4432
Lifer
- Sep 6, 2003
- 11,726
- 45
- 91
Originally posted by: dclive
I'll let Phoenix86 answer that one.
Let's see if we can get it working. Do you know if the HAL is the same? That's an obvious first step, although since you've a backup image, it can't hurt to try.
in theory and according to the ms website it is the same as it was a acpi uniprocessor hal with ht off and acpi mulitprocessor hal on
according the the ms website, those two are ok together. the only weird thing is is that when i would click on the device manager, it just said hal.dll and not a specific that was listed on the ms website.
i will try the acronis image now...
http://support.microsoft.com/default.aspx?scid=kb;EN-US;237556
should get you started. It's under "Computer" in DM that you find the HAL; you don't need to go any further. If both are "ACPI Uniprocessor PC" you should be fine.
should get you started. It's under "Computer" in DM that you find the HAL; you don't need to go any further. If both are "ACPI Uniprocessor PC" you should be fine.
bob4432
Lifer
- Sep 6, 2003
- 11,726
- 45
- 91
still having the same issue. with the image i was able to get into safe mode, but still the same issues when starting up with the .sys files....now the machine in safe mode is showing acpi multriprocessor....it seems like pnp is not turned on...i can't find in the bios the "pnp os" option, could that be causing this problem?
at this point should i try the repair route? anything i need to do inparticular for it?
i do have a mepis linux live cd...do i need to move a file from one disk to another?
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 24K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter