Can I simply swap hard drives?

[More Cowbell]

I have a computer in my MAME cab running at 1ghz currently. I bought a 1.7ghz computer and want to upgrade to that. Can I simply swap the hard drives or will this confuse the system? I don't want to start from scratch in copying files and configuring. I also have a video card that allows me to use s-video. Can that simply be swapped to the other system too? In my mind this would all work. Is my mind a good resource for information though? Not always.

[Teebor]

What operating system please?

XP- Give it a go, often works out ok. but can be fixed by re-installing over the top usually so settings are kept intact

DOS - should be fine

Vista - Never done it myself but I wouldn't bet on it

[TOK]

I've always done a format and install on a new machine. The thing that might cause you the most trouble are the things built into the motherboard, like if your current system has an NForce chipset and you're installing on a motherboard with something else. It might just detect the new IDE controller and start using it, or it could just totally freak out and won't see the hard drive.

If I was going to try it, I think I'd probably going into Device Manager before the last time I shut down and uninstall all the motherboard related stuff so that they are hopefully just re-detected when you fire up the new machine.

 

[leapinlew]

odds are, it won't work.

You'll want to reformat.

[Ed_McCarron]

XP- Give it a go, often works out ok. but can be fixed by re-installing over the top usually so settings are kept intact

Often?  Unless the mobo has the same exact chipset, XP will crash upon boot.  Real PITA.  Don't think I've seen this work once without requiring a fresh install.

Please tell me I'm missing some simple step that makes life easier?

[XyloSesame]

XP- Give it a go, often works out ok. but can be fixed by re-installing over the top usually so settings are kept intact

Oy, this sounds like a nightmare.

Install fresh on the new machine and use the old drive as additional data storage. Keep the OS on it's own drive. If you UG later, you should be able to install MAME and point it to the existing ROMS on your Data drive.

RE video, if you have the drivers, you should be able to install it in a new box - that's not to say it will work plug-and-play-like, but it should be do-able.

[acro-ii]

You are.
Boot from XP CD with same service pack revision as is on your machine.
Go past the setup option to repair using recovery console.
It scans for the current os.
Then you get a repair option.
It works perfectly.  That's how I fix 90% of the pcs that poeple bring into my office.

XP- Give it a go, often works out ok. but can be fixed by re-installing over the top usually so settings are kept intact

Often?  Unless the mobo has the same exact chipset, XP will crash upon boot.  Real PITA.  Don't think I've seen this work once without requiring a fresh install.

Please tell me I'm missing some simple step that makes life easier?

[XyloSesame]

You are.
Boot from XP CD with same service pack revision as is on your machine.
Go past the setup option to repair using recovery console.
It scans for the current os.
Then you get a repair option.
It works perfectly.  That's how I fix 90% of the pcs that poeple bring into my office.

Hey, Acro, does this leave the registry and installed programs intact?

[acro-ii]

100% yes!
 

[xmenxmen]

I have found computer advise here seems to be very limited....

As long as these system are all running ide drive and not raid controller of some sort, there's really no problem in porting it from one system to another.  Worst case is that you will have to update all the drivers once the system comes up.  I have done this so many time, it's not even funny anymore. 

And in those case where you actually have a non support (by default xp) hard drive controller , then all you need is put the xp cd in there and have it added the drivers during the initial boot (F6), then perform a repair of the os.

Again, the basic home system is not that complex, so swapping between system and getting them to work is pretty much guarantee in xp with very low failure rate.

I say give it a go.


And if you do prefer to install fresh, all you have to do afterward is transfer your mame configuration to the same drive and directory layout and you should be up and running with minimal re-config.

[XyloSesame]

I'm still dubious, but I always start with a fresh install, so I'm not the expert...

Question: Since XP will just be installing controller and bus drivers, does it matter if you use an OEM CD even if you're running a service packed OS?

[Ed_McCarron]

You are.
Boot from XP CD with same service pack revision as is on your machine.
Go past the setup option to repair using recovery console.
It scans for the current os.
Then you get a repair option.
It works perfectly.  That's how I fix 90% of the pcs that poeple bring into my office.

XP- Give it a go, often works out ok. but can be fixed by re-installing over the top usually so settings are kept intact

Often?  Unless the mobo has the same exact chipset, XP will crash upon boot.  Real PITA.  Don't think I've seen this work once without requiring a fresh install.

Please tell me I'm missing some simple step that makes life easier?

Live and learn.  I'll give it a shot.  Thanks!

[knave]

One added step that might help...

Make sure you change to the default VGA video card drivers before you swap.

This will make your install of the new GPU easier and possibly avaid any headaches.

-now just a bit of opinion-
While this can work, I always want my pc's to be squeeky clean.
I reccomend installing XP fresh and adding your old HD as a slave to copy your files. 
For mame you should get all your configuration settings. 

Either way do yourseld a favor and change the VGA driver whenever you change Video cards.

Oh and I know PC gamer did a walkthrough on how to do this in XP so I'm sure there are other guides out there.  Do a little Google-fu and you should find out all the steps needed to totally swap out your hd without a new install.

Good luck

[xmenxmen]

I'm still dubious, but I always start with a fresh install, so I'm not the expert...

Question: Since XP will just be installing controller and bus drivers, does it matter if you use an OEM CD even if you're running a service packed OS?

In most case no.  Typically once you get the system up and running, you will go and update the drivers anyway. 

Only case I seen it matter the most is when you try to do a repair on the system.  What happens here is the repair process will actually go out and delete the system files that's install in the windows directory and reload it from the cd.  The problem here is that there's files/drivers from other area that are still at the higher service pack.  They tend to conflict sometimes and cost the system to become unstable.  If the system does come up and you are able to re-apply the service pack, it normally does take care of the problem. 

To avoid this completely I do recommend one to slipstream the service pack into the I386 directory or cd.  Just do a google search on slipstream xp if you need more details.

[More Cowbell]

Thanks for the advice. I'm running Windows 2000 on both systems. Does that make a difference to the XP-releated suggestions? I'm thinking that adding the hard drive as a slave and copying everything will be the most bomb-out proof way of going.

[XyloSesame]

does it matter if you use an OEM CD even if you're running a service packed OS?

Only case I seen it matter the most is when you try to do a repair on the system.  What happens here is the repair process will actually go out and delete the system files that's install in the windows directory and reload it from the cd.  The problem here is that there's files/drivers from other area that are still at the higher service pack.  They tend to conflict sometimes and cost the system to become unstable.  If the system does come up and you are able to re-apply the service pack, it normally does take care of the problem. 

To avoid this completely I do recommend one to slipstream the service pack into the I386 directory or cd.  Just do a google search on slipstream xp if you need more details.

However, your advice and Acro's advice both point to performing a repair from an XP CD. If you don't have a slipstreamed disc, you risk the conflicts and instability as stated above. Correct?

[leapinlew]

I've done plenty of installs and new machine upgrades. I don't have much luck installing a pre-installed OS on another machine. I wouldn't even mess with it if you value your time.

Setup a new machine properly and then copy over the files you want.

[XyloSesame]

I wouldn't even mess with it if you value your time.

Well said.

[More Cowbell]

Time was what I was really trying to save so if this is going to be more headache than time saver, I say to hell with it. Copy and paste, here I come. Glad I didn't just try plugging things in and switching things on.

[leapinlew]

Time was what I was really trying to save so if this is going to be more headache than time saver, I say to hell with it. Copy and paste, here I come. Glad I didn't just try plugging things in and switching things on.

Which of your dozens of arcade games is this?

[FunWithFire]

Couldn't you just put your old HD in the new machine as a slave drive?

[missioncontrol]

I have done this so many time, it's not even funny anymore. 

I must be doing it wrong, I never have found a HDD swap funny 

[Jouster]

Make backups first of whatever you want to keep...just in case.

I would doubt that you could simply plug a HD into another system...especially one that is completely different...and have it work right off the bat as the main drive...secondary or data drive, sure.  The HALs wouldn't match and most likely you'll get a BSOD (Blue Screen Of Death).

If the systems are close in setup, it might work...either use the repair console method...or just fresh install it.

Jouster

[MrMojoZ]

You are.
Boot from XP CD with same service pack revision as is on your machine.
Go past the setup option to repair using recovery console.
It scans for the current os.
Then you get a repair option.
It works perfectly.  That's how I fix 90% of the pcs that poeple bring into my office.

This is not currently working, once you finish the repair you can no longer install windows updates. Have you done a repair in the past month? I've seen about seven fail.

[boykster]

backup whatever you want to not lose....swap the drive and go directly to the recovery console (make sure to have an XP disc handy)

from the recovery console (assuming C is boot drive and D is cd drive with xp cd in it)

copy D:\i386\hal.dl_ c:\windows\system32\hal.dll
copy D:\i386\ntoskrnl.ex_ c:\windows\system32\ntoskrnl.exe

reboot.  Drivers and other stuff will be re-setup and you <should> be good to go.

Always backup data first though.....

[Green Giant]

Don't know if I got here to late, but I have never had trouble with this.  I have cleaned up friends computers in the past that had been so infected with viruses that they wouldn't run at all.  I dropped their harddrives in my machines, much faster and capable of running with all the other junk running, and ran some stuff to clean it up.

I find you just wait a little while and windows will recognize just about everything.  After I fixed their harddrives I just dropped it back in their machine, no problem.  The only thing I could possibly see going wrong is if you have several game controllers hooked up getting reassigned different device id's.  This isn't the darkages of computers, XP won't freak out and blue screen if it finds all new hardware.

Worst comes to worst, you will have the XP file system corrupted and have to install on a new harddrive.  Once the new OS is on there you can still add the old harddrive in the system as a backup and copy the files over that way.  I have also done that a million times on many machines.

[MrMojoZ]

  I dropped their harddrives in my machines, much faster and capable of running with all the other junk running, and ran some stuff to clean it up.

  This isn't the darkages of computers, XP won't freak out and blue screen if it finds all new hardware.

Thats not how it works nor does it reflect the issue being discussed. You lucked out in that your IDE controllers were close enough to not cause a problem. What happens when most drives are swapped between motherboards is XP will blue screen on boot, there is no hardware recognizing period. We used to fix with a windows repair but that has not been working, going to try Boykster's method next time I see a system that needs it.

[Green Giant]

  I dropped their harddrives in my machines, much faster and capable of running with all the other junk running, and ran some stuff to clean it up.

  This isn't the darkages of computers, XP won't freak out and blue screen if it finds all new hardware.

Thats not how it works nor does it reflect the issue being discussed. You lucked out in that your IDE controllers were close enough to not cause a problem. What happens when most drives are swapped between motherboards is XP will blue screen on boot, there is no hardware recognizing period. We used to fix with a windows repair but that has not been working, going to try Boykster's method next time I see a system that needs it.

I have done this 8 or 9 times all with motherboards built in the last few years with success on them all.  On servers this actually works even better as I have done this hundreds of times with many different operating systems on several types of servers.  Suse has many problems but Windows always worked great.  That is why I said in the past it would have caused problems.  The biggest problems I found was the video driver not getting recognized immediatley, but with some luck, windows will find something suitable and install it for you.

As for the issue being discussed, that covers it exactly.  He wants to just swap out the drives without doing any time consuming work.  This method should first be done using the vga video, but once up and running it should be able to install the correct drivers and use svideo.  And if it doesn't work, all of the information will not be lost.  As long as the bare minimum of hardware, keyboard mouse and monitor, is plugged in when booting the new computer, it should work.

[leapinlew]

On servers this actually works even better as I have done this hundreds of times with many different operating systems on several types of servers.  Suse has many problems but Windows always worked great. 

On Windows Servers this is just about the worst thing you can do. Seeing as how many servers require you to install the controller during setup and windows won't have the drivers native. This is when you need a floppy... and ONLY A FLOPPY (goofy crap).

That is why I said in the past it would have caused problems.

In the past we didn't have plug and pray and this wasn't an issue at all.

it should work.

Famous last words.

I'm glad you got everything to work Green Giant. I'm not calling you a liar, just saying my experience has been different. Completely different.

[MrMojoZ]

I have done this 8 or 9 times all with motherboards built in the last few years with success on them all.  On servers this actually works even better as I have done this hundreds of times with many different operating systems on several types of servers. 

And I've done it hundreds of times with Windows XP, we are not discussing other operating systems. IT DOES NOT ALWAYS WORK. The other posters in this thread can back that up.

[xmenxmen]

Don't know if I got here to late, but I have never had trouble with this.  I have cleaned up friends computers in the past that had been so infected with viruses that they wouldn't run at all.  I dropped their harddrives in my machines, much faster and capable of running with all the other junk running, and ran some stuff to clean it up.

I find you just wait a little while and windows will recognize just about everything.  After I fixed their harddrives I just dropped it back in their machine, no problem.  The only thing I could possibly see going wrong is if you have several game controllers hooked up getting reassigned different device id's.  This isn't the darkages of computers, XP won't freak out and blue screen if it finds all new hardware.

Worst comes to worst, you will have the XP file system corrupted and have to install on a new harddrive.  Once the new OS is on there you can still add the old harddrive in the system as a backup and copy the files over that way.  I have also done that a million times on many machines.

This is so true.  Either everyone on here are quite in experience to this stuff or just have crappy luck. 

And to the one mentioning HAL, if you look at his system, you can see that he's going from a 1ghz to a 1.7ghz, both are single cpu and either one has more than one core, so HAL is not a problem!

[leapinlew]

This is so true.  Either everyone on here are quite in experience to this stuff or just have crappy luck. 

And to the one mentioning HAL, if you look at his system, you can see that he's going from a 1ghz to a 1.7ghz, both are single cpu and either one has more than one core, so HAL is not a problem!

Why don't you tell me what you think HAL means, and then I'll tell you what it really means.

[leapinlew]

Man...

that damn cowbell really knows how to get a nerd fight started.

[MrMojoZ]

[quote author=xmenxmen link=topic=71670.msg736481#msg736481
This is so true.  Either everyone on here are quite in experience to this stuff or just have crappy luck. 

And to the one mentioning HAL, if you look at his system, you can see that he's going from a 1ghz to a 1.7ghz, both are single cpu and either one has more than one core, so HAL is not a problem!
[/quote]

No it isn't true. I can predict the out come of motherboard swaps between SiS, Via, Intel and Nvidia chipset matings. Can you?

Inexpirienced.   I have to do motherboard swap outs everyday (thank e-machines).

[HaRuMaN]

Isn't HAL the computer on 2001: A Space Oddessy?   

[MrMojoZ]

Isn't HAL the computer on 2001: A Space Oddessy?   

I'd say you were closer to the truth than xmenxmen. 

[gonzo90017]

In my experience swapping hard drives rarely works. Only when the motherboards have the same chipsets has it worked. In my earlier computing days when I tried swapping them with different chipsets I have gotten the blue screen. But i've never tried it using his method so I can't say if it doesn't work.

Hey Green Giant why not just install your friends drives as slaves and clean them that way instead?

[More Cowbell]

Man...
that damn cowbell really knows how to get a nerd fight started.

Yes, my plan is working perfectly. Next thread... Kirk or Picard. Let's get ready to rumblllllllllllllllle!
This is for my original, scratch-built MAME cab, Lew. The other ones are running the classics so they don't need much power.

[xmenxmen]

Inexpirienced.  I have to do motherboard swap outs everyday (thank e-machines).

Did u do one today???

[Green Giant]

Hey Green Giant why not just install your friends drives as slaves and clean them that way instead?

That only works when I am trying to save their files.  This is my prefered method, but when you have 200GB of material, you need a big disk to handle the transfer.  Swapping out the harddrive in the new computer will only take a few minutes, and if it doesn't boot up, no problem, everything will still be there.  The biggest concern is setting up the video, if the video card remains the same, not using onboard, plug and play may very well recognize it.

On Windows Servers this is just about the worst thing you can do. Seeing as how many servers require you to install the controller during setup and windows won't have the drivers native. This is when you need a floppy... and ONLY A FLOPPY (goofy crap).

Windows Server OS is the best at recognizing new hardware and new drivers without using the floppy.  Other OS's have trouble sometimes.  Typically the most important systems will be transferred including video, keyboard, and mouse on servers.  I worked for HP on servers for two years and we did this stuff constantly.  After several servers you can get some slowdown, but once or twice never has problems.  The only time you will need the drivers are for the onboard lan which typically never shows up.

And in the few times it wants the floppy, you can just virtually connect a floppy through the network and upload the driver directly without an actual floppy drive.

Oh, and Picard.

Everybody is so testy today, I never said you are all liars, I just said I have had success swapping out harddrives into completely different computers.  The original question asked if it could work to save him time, I think it can.

[xmenxmen]

This is so true.  Either everyone on here are quite in experience to this stuff or just have crappy luck. 

And to the one mentioning HAL, if you look at his system, you can see that he's going from a 1ghz to a 1.7ghz, both are single cpu and either one has more than one core, so HAL is not a problem!

Why don't you tell me what you think HAL means, and then I'll tell you what it really means.

I don't know, so why don't u tell me.     And while you are at it, tell me how many of those home pc that are not "ACPI". 

[leapinlew]

This is so true.  Either everyone on here are quite in experience to this stuff or just have crappy luck. 

And to the one mentioning HAL, if you look at his system, you can see that he's going from a 1ghz to a 1.7ghz, both are single cpu and either one has more than one core, so HAL is not a problem!

Why don't you tell me what you think HAL means, and then I'll tell you what it really means.

I don't know, so why don't u tell me.     And while you are at it, tell me how many of those home pc that are not "ACPI". 

I know you don't know.... everyone knows you don't know. 

Pretty much every machine I've been working on for the last half a dozen years or so have been ACPI compliant. Not sure what that has to do with what were talking about, but whatever. If you've had luck swapping drives around from one computer to another good for you. I've tried to do it plenty of times and it pretty much always bombs out unless the recipient computer has identical hardware. 

[Avrus]

How many of you are hardcore enough to remember?

xcopy32 /s /e /r /h /c /k /y

[XyloSesame]

How many of you are hardcore enough to remember?

xcopy32 /s /e /r /h /c /k /y

And how many have graduated to robocopy?

[Teebor]

The worst experience I have had was when I was building 30 identical PC's from the same batch, I built the first one with windows XP and then cloned it to the remaining 29.  Alhough the hardware was identical in every respect none of the rest of the machine would work, I think it was due to the memory addresses being slightly different on each machine which caused it to crash.

However I have removed a windows XP drive from two completely different machines with different chipsets and because they were so different windows XP had to re-detect everything and worked ok.

Windows 2000 used to be even better at it then windows  XP, windows XP sometimes flakes out, at which point if you re-install the OS back over the top of itself it rebuilds the hardware portion of the registry, changes a couple of settings in the software part back to defaults but leaves everything else intact.

Of course none of this works if you are using SATA or raid as its effectively a complete start from scratch as it normally fails.

[acro-ii]

Yes it IS working.  I did 2 yesterday, and both went fine.

 

I do agree, it isn't guaranteed to work, but it is my FIRST choice, as it is so much easier than reloading.  If it does not work, I'm only out about 30 minutes.  If it does, it saves me twice that much!

You are.
Boot from XP CD with same service pack revision as is on your machine.
Go past the setup option to repair using recovery console.
It scans for the current os.
Then you get a repair option.
It works perfectly.  That's how I fix 90% of the pcs that poeple bring into my office.

This is not currently working, once you finish the repair you can no longer install windows updates. Have you done a repair in the past month? I've seen about seven fail.

[xmenxmen]

How many of you are hardcore enough to remember?

xcopy32 /s /e /r /h /c /k /y

And how many have graduated to robocopy?

yet again, I don't.     But I surely remember ncopy and hcopy.

[xmenxmen]

This is so true.  Either everyone on here are quite in experience to this stuff or just have crappy luck. 

And to the one mentioning HAL, if you look at his system, you can see that he's going from a 1ghz to a 1.7ghz, both are single cpu and either one has more than one core, so HAL is not a problem!

Why don't you tell me what you think HAL means, and then I'll tell you what it really means.

I don't know, so why don't u tell me.     And while you are at it, tell me how many of those home pc that are not "ACPI". 

I know you don't know.... everyone knows you don't know. 

Pretty much every machine I've been working on for the last half a dozen years or so have been ACPI compliant. Not sure what that has to do with what were talking about, but whatever. If you've had luck swapping drives around from one computer to another good for you. I've tried to do it plenty of times and it pretty much always bombs out unless the recipient computer has identical hardware. 

Generally I would take the time to educate, but this case, I will just won't.  If you can't figure out what changes actually cause the replace of the HAL and what doesn't, that's really your problem. 

If u are calling bull or whatever u like to call, that's good for you.  There's reason why some can do certain thing better than other.  I will leave it at that.

That's all my comment for this thread.. 

[MrMojoZ]

That's all my comment for this thread.. 

Good, while hilarious it is best to keep Mis-information to a minimum. The amount of cores don't cause the swap out blue screen, only the change in controllers.

[MrMojoZ]

Yes it IS working.  I did 2 yesterday, and both went fine.

Verify that windows updates can still install.

[MrMojoZ]

Windows Server OS is the best at recognizing new hardware and new drivers without using the floppy. 

And in the few times it wants the floppy, you can just virtually connect a floppy through the network and upload the driver directly without an actual floppy drive.

He is talking about controllers that require F6 during the windows install. IE any SATA raid or newer SCSI controller. And once again we are not talking about installing devices while booted into windows, all these problems prevent the OS from loading at all. There is no hardware detection if you blue screen during bootup or if the OS installer can't see a HD.

[unclet]

I did not read this whole thread, but wanted to mention that I always have two drives in my cabinets.  The first hard drive (C:) is small and is used for the operating system only.  The second hard drive (D:) is where all of the emulator stuff is installed.  If I ever upgrade to a new computer (I did this twice so far), then I reformat the first hard drive (C:) and install the new operating system.  After the computer comes up fine then simply plug in the second hard drive (D:) and the drive is recognized and all emulator stuff exists and is configured already.

[acro-ii]

Yes it IS working.  I did 2 yesterday, and both went fine.

Verify that windows updates can still install.

Yes, the ones from yesterday did.  One last week did not.  It's an easy fix if it does not, I run a nice little utlity called dial-a-fix, and reset all windows update stuff(.dll's and all).  Then you're good to go.

[Green Giant]

Windows Server OS is the best at recognizing new hardware and new drivers without using the floppy. 

And in the few times it wants the floppy, you can just virtually connect a floppy through the network and upload the driver directly without an actual floppy drive.

He is talking about controllers that require F6 during the windows install. IE any SATA raid or newer SCSI controller. And once again we are not talking about installing devices while booted into windows, all these problems prevent the OS from loading at all. There is no hardware detection if you blue screen during bootup or if the OS installer can't see a HD.

Yes, I realize you are talking about the harddrive controllers which must be there to see the drive.  Like I said above, when this was a problem we just remotely connected a virtual floppy or cdrom, completely outside of any operating system, and dropped in the drivers necessary.

This probably is a problem with crappier servers like Dell and IBM, but with our hardware, we never had issues.

[leapinlew]

Windows Server OS is the best at recognizing new hardware and new drivers without using the floppy. 

And in the few times it wants the floppy, you can just virtually connect a floppy through the network and upload the driver directly without an actual floppy drive.

He is talking about controllers that require F6 during the windows install. IE any SATA raid or newer SCSI controller. And once again we are not talking about installing devices while booted into windows, all these problems prevent the OS from loading at all. There is no hardware detection if you blue screen during bootup or if the OS installer can't see a HD.

Yes, I realize you are talking about the harddrive controllers which must be there to see the drive.  Like I said above, when this was a problem we just remotely connected a virtual floppy or cdrom, completely outside of any operating system, and dropped in the drivers necessary.

This probably is a problem with crappier servers like Dell and IBM, but with our hardware, we never had issues.

It sounds like your installing the OS using an installer program... like Smartstart. If so, I could see being able to use a virtual floppy, but heres the scenario

You swap the drive from one superior HP server to an equally good HP. The new HP is using an entirely different drive controller and needs to be manually installed during the OS.

There... tell me how you swap drives and make that work. Since you never have issues, I'm curious how this accomplished. The way I see it - you swap the drive and then need to do some software CD Booting magic.

[Green Giant]

Windows Server OS is the best at recognizing new hardware and new drivers without using the floppy. 

And in the few times it wants the floppy, you can just virtually connect a floppy through the network and upload the driver directly without an actual floppy drive.

He is talking about controllers that require F6 during the windows install. IE any SATA raid or newer SCSI controller. And once again we are not talking about installing devices while booted into windows, all these problems prevent the OS from loading at all. There is no hardware detection if you blue screen during bootup or if the OS installer can't see a HD.

Yes, I realize you are talking about the harddrive controllers which must be there to see the drive.  Like I said above, when this was a problem we just remotely connected a virtual floppy or cdrom, completely outside of any operating system, and dropped in the drivers necessary.

This probably is a problem with crappier servers like Dell and IBM, but with our hardware, we never had issues.

It sounds like your installing the OS using an installer program... like Smartstart. If so, I could see being able to use a virtual floppy, but heres the scenario

You swap the drive from one superior HP server to an equally good HP. The new HP was using an entirely different drive controller that was manually installed during the OS.

There... tell me how you swap drives and make that work. Since you never have issues, I'm curious how this accomplished.

Since you sound familiar with HP servers, you must know about iLO.  It operates completely separate of the other hardware assuming you aren't on a brand new prototype server.  Using that I can connect any number of devices and drop in any media format I want. 

But it sounds like you are talking about sata to scsi and the like.  That can't be done without putting in a new controller for the drive connectiong, and switching those out is a pain in the arse.  Most of the time the newer versions of a controller will recognize the older model, but when they don't smartstart can usually fix it with the correct drivers.

But when going scsi to scsi or sata to sata, it will usually work with Windows 2003 95% of the time.

[leapinlew]

Windows Server OS is the best at recognizing new hardware and new drivers without using the floppy. 

And in the few times it wants the floppy, you can just virtually connect a floppy through the network and upload the driver directly without an actual floppy drive.

He is talking about controllers that require F6 during the windows install. IE any SATA raid or newer SCSI controller. And once again we are not talking about installing devices while booted into windows, all these problems prevent the OS from loading at all. There is no hardware detection if you blue screen during bootup or if the OS installer can't see a HD.

Yes, I realize you are talking about the harddrive controllers which must be there to see the drive.  Like I said above, when this was a problem we just remotely connected a virtual floppy or cdrom, completely outside of any operating system, and dropped in the drivers necessary.

This probably is a problem with crappier servers like Dell and IBM, but with our hardware, we never had issues.

It sounds like your installing the OS using an installer program... like Smartstart. If so, I could see being able to use a virtual floppy, but heres the scenario

You swap the drive from one superior HP server to an equally good HP. The new HP was using an entirely different drive controller that was manually installed during the OS.

There... tell me how you swap drives and make that work. Since you never have issues, I'm curious how this accomplished.

Since you sound familiar with HP servers, you must know about iLO.  It operates completely separate of the other hardware assuming you aren't on a brand new prototype server.  Using that I can connect any number of devices and drop in any media format I want. 

But it sounds like you are talking about sata to scsi and the like.  That can't be done without putting in a new controller for the drive connectiong, and switching those out is a pain in the arse.  Most of the time the newer versions of a controller will recognize the older model, but when they don't smartstart can usually fix it with the correct drivers.

I suppose we've now come to the end of the thread.
The question was: Can I simply swap hard drives?
The answer - maybe. Depends on your hardware.

Also - Picard rules.

[More Cowbell]

I did not read this whole thread, but wanted to mention that I always have two drives in my cabinets.  The first hard drive (C:) is small and is used for the operating system only.  The second hard drive (D:) is where all of the emulator stuff is installed.  If I ever upgrade to a new computer (I did this twice so far), then I reformat the first hard drive (C:) and install the new operating system.  After the computer comes up fine then simply plug in the second hard drive (D:) and the drive is recognized and all emulator stuff exists and is configured already.

Actually, I like this idea a lot. I have a few small hard drives hanging around and this would make it easy to simply move a drive or copy it completely and set it up quickly and easily.

[XyloSesame]

I'm curious how this accomplished.

I'm all for learning new tricks as I do this type of thing every day in a professional environment, but I lost interest in the "hows" and "whys" when everyone started talking about the possibility (and probability) of using third-party utilities. Add that to the fact that you would never have a clean machine after the OS redetects and installs new drivers, and I'm out.

Teach me a new trick that does things the right way, works outside of a sealed environment (iLO), and saves time. Not shortcuts that may or may not work and will certainly leave residual.

I suppose we've now come to the end of the thread.
The question was: Can I simply swap hard drives?
The answer - maybe. Depends on your hardware.

Again, Lew, well said.

[Green Giant]

Also - Picard rules.

I knew we could come to an agreement.

[MrMojoZ]

The repair issue and fix walkthrough:

http://windowssecrets.com/2007/09/27/03-Stealth-Windows-update-prevents-XP-repair

[leapinlew]

And here are some Kittens:

[ahofle]

FWIW, I've upgraded a motherboard/CPU and booted with the old HD with no problems either in XP.  My thought was it wouldn't hurt to try seeing as how my alternative was to wipe the hard drive and reinstall everything anyway.  It ended up working, and I saved countless hours of reinstallation (OS and programs).  I'm not saying it always works, but it doesn't hurt to try.

[ahofle]

I did not read this whole thread, but wanted to mention that I always have two drives in my cabinets.  The first hard drive (C:) is small and is used for the operating system only.  The second hard drive (D:) is where all of the emulator stuff is installed.  If I ever upgrade to a new computer (I did this twice so far), then I reformat the first hard drive (C:) and install the new operating system.  After the computer comes up fine then simply plug in the second hard drive (D:) and the drive is recognized and all emulator stuff exists and is configured already.

Actually, I like this idea a lot. I have a few small hard drives hanging around and this would make it easy to simply move a drive or copy it completely and set it up quickly and easily.

Unfortunately, this only works with programs like MAME.  Most programs install shared DLLs,  OCXs, have tons of registry keys, etc.  So you will still have to reinstall those programs.  I would imagine most emulators would be fine though.

[MrMojoZ]

If you really want to make sure your cabinet is covered get it setup like you want it then use a program like Ghost to image the drive. Plop that image on a bootable DVD and you can restore your cabinet PC anytime you feel like it.

[knave]

Ghost is awesome...been using it for years, won't ever go back...