Guest David B. Posted August 16, 2007 Posted August 16, 2007 Re: Hard Drive Change As I said, to each his own. I don't really care how any one does it, I was just offering another solution to a common problem. -- ---- Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm How to ask a question http://support.microsoft.com/kb/555375 How to Post http://www.dts-l.org/goodpost.htm _________________________________________________________________________________ "Gary S. Terhune" <none> wrote in message news:eNrHj4D4HHA.1164@TK2MSFTNGP02.phx.gbl... > Five to ten minutes to install a PCI card (the hardware), then. when the > drivers install is complete, shut down, remove the card, install the new > mobo (won't count that time), restart and install all the new drivers > (also a wash), then, after the thing is done, remove the card? OK, maybe, > if you're really fast. But I doubt it. > > Whereas a Repair install takes about two minutes to initiate, then you go > do something else for half an hour. Ditto the Updates. And there's no > guessing whether your method will even work. > > -- > Gary S. Terhune > MS-MVP Shell/User > http://www.grystmill.com > > "David B." <brooks.dj@nospam.hotmail.com> wrote in message > news:e%23YE6ED4HHA.4476@TK2MSFTNGP06.phx.gbl... >> Installing a driver for a PCI controller takes the same amount of time as >> a repair install and reinstalling all the Windows updates? Few I think >> would agree with that. My method is 5, 10 minutes at most in preparation. >> A repair install, half an hour roughly depending on the machine, Windows >> updates another half hour to an hour or so depending on your connection >> speed. It really is a time saver and almost always works. I have even >> swapped AMD boards for Intel boards with this method, with no repair >> install. This method gets around the hard drive controller >> incompatibility issue only, if it blue screens for some other reason, >> which I have found is rare, it's usually because one forgot to uninstall >> drivers (sound, nic etc) before the final shutdown before the swap. >> >> -- >> >> ---- >> Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm >> How to ask a question http://support.microsoft.com/kb/555375 >> How to Post http://www.dts-l.org/goodpost.htm >> _________________________________________________________________________________ >> >> >> "Gary S. Terhune" <none> wrote in message >> news:e9xVxhC4HHA.2312@TK2MSFTNGP06.phx.gbl... >>> Hmmm... Seems to me that the hardware changes your method requires would >>> take near as much time as a Repair install. Certainly a lot more >>> hands-on time. Dunno... >>> >>> -- >>> Gary S. Terhune >>> MS-MVP Shell/User >>> http://www.grystmill.com >>> >>> "David B." <brooks.dj@nospam.hotmail.com> wrote in message >>> news:OeBAQXC4HHA.1164@TK2MSFTNGP02.phx.gbl... >>>> What ever floats your boat, I'd rather not waste the time if I don't >>>> have to. >>>> >>>> -- >>>> >>>> ---- >>>> Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm >>>> How to ask a question http://support.microsoft.com/kb/555375 >>>> How to Post http://www.dts-l.org/goodpost.htm >>>> _________________________________________________________________________________ >>>> >>>> >>>> "Gary S. Terhune" <none> wrote in message >>>> news:eof0ITC4HHA.484@TK2MSFTNGP06.phx.gbl... >>>>> So, there goes your "whether it successfully boots or not after a >>>>> motherboard swap is 100% related to the old and new hard drive >>>>> controller." >>>>> >>>>> All in all, I think I'd prefer a Repair install. >>>>> >>>>> -- >>>>> Gary S. Terhune >>>>> MS-MVP Shell/User >>>>> http://www.grystmill.com >>>>> >>>>> "David B." <brooks.dj@nospam.hotmail.com> wrote in message >>>>> news:eYjM03q2HHA.1208@TK2MSFTNGP05.phx.gbl... >>>>>> In rare cases maybe, I have had probably a 95 to 99% success rate >>>>>> using the method I outlined. >>>>>> >>>>>> -- >>>>>> >>>>>> ---- >>>>>> Crosspost, do not multipost >>>>>> http://www.blakjak.demon.co.uk/mul_crss.htm >>>>>> How to ask a question http://support.microsoft.com/kb/555375 >>>>>> How to Post http://www.dts-l.org/goodpost.htm >>>>>> _________________________________________________________________________________ >>>>>> >>>>>> >>>>>> "John John" <audetweld@nbnot.nb.ca> wrote in message >>>>>> news:e9Anuho2HHA.1184@TK2MSFTNGP04.phx.gbl... >>>>>>> That is not correct. It may be correct to say that drive controller >>>>>>> differences is the most common cause but there are other issues that >>>>>>> can cause Windows XP not to boot when it is moved to different >>>>>>> hardware, especially if you move it form fairly old to much newer >>>>>>> hardware. >>>>>>> >>>>>>> While it is correct to say that in 100% of cases if the drive >>>>>>> controller is different Windows will not boot, it is incorrect to >>>>>>> say that different controller are the sole and only cause and that >>>>>>> they are 100% responsible for boot failures when moving Windows XP >>>>>>> to new hardware. 0x7B errors are not exclusively, 100% the sole >>>>>>> possible error when moving Windows XP to new hardware, and it is not >>>>>>> the only 100% thing that makes it necessary to reinstall Windows! >>>>>>> >>>>>>> John >>>>>>> >>>>>>> David B. wrote: >>>>>>>> It is the difference in the hard drive controller that causes the >>>>>>>> BSOD after a motherboard swap, that is the only thing that makes it >>>>>>>> necessary for a repair install, the procedure I stated above proves >>>>>>>> this and I have used it many times to avoid the need for a repair >>>>>>>> install (in an upgrade situation). I would do a bit of testing >>>>>>>> before making the statement you did, you will find out that your >>>>>>>> wrong. >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >> > >
Guest Gary S. Terhune Posted August 16, 2007 Posted August 16, 2007 Re: Hard Drive Change Understood. I'm just adding to the discussion. -- Gary S. Terhune MS-MVP Shell/User http://www.grystmill.com "David B." <brooks.dj@nospam.hotmail.com> wrote in message news:u9EE97D4HHA.5316@TK2MSFTNGP04.phx.gbl... > As I said, to each his own. I don't really care how any one does it, I was > just offering another solution to a common problem. > > -- > > ---- > Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm > How to ask a question http://support.microsoft.com/kb/555375 > How to Post http://www.dts-l.org/goodpost.htm > _________________________________________________________________________________ > > > "Gary S. Terhune" <none> wrote in message > news:eNrHj4D4HHA.1164@TK2MSFTNGP02.phx.gbl... >> Five to ten minutes to install a PCI card (the hardware), then. when the >> drivers install is complete, shut down, remove the card, install the new >> mobo (won't count that time), restart and install all the new drivers >> (also a wash), then, after the thing is done, remove the card? OK, maybe, >> if you're really fast. But I doubt it. >> >> Whereas a Repair install takes about two minutes to initiate, then you go >> do something else for half an hour. Ditto the Updates. And there's no >> guessing whether your method will even work. >> >> -- >> Gary S. Terhune >> MS-MVP Shell/User >> http://www.grystmill.com >> >> "David B." <brooks.dj@nospam.hotmail.com> wrote in message >> news:e%23YE6ED4HHA.4476@TK2MSFTNGP06.phx.gbl... >>> Installing a driver for a PCI controller takes the same amount of time >>> as a repair install and reinstalling all the Windows updates? Few I >>> think would agree with that. My method is 5, 10 minutes at most in >>> preparation. A repair install, half an hour roughly depending on the >>> machine, Windows updates another half hour to an hour or so depending on >>> your connection speed. It really is a time saver and almost always >>> works. I have even swapped AMD boards for Intel boards with this method, >>> with no repair install. This method gets around the hard drive >>> controller incompatibility issue only, if it blue screens for some other >>> reason, which I have found is rare, it's usually because one forgot to >>> uninstall drivers (sound, nic etc) before the final shutdown before the >>> swap. >>> >>> -- >>> >>> ---- >>> Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm >>> How to ask a question http://support.microsoft.com/kb/555375 >>> How to Post http://www.dts-l.org/goodpost.htm >>> _________________________________________________________________________________ >>> >>> >>> "Gary S. Terhune" <none> wrote in message >>> news:e9xVxhC4HHA.2312@TK2MSFTNGP06.phx.gbl... >>>> Hmmm... Seems to me that the hardware changes your method requires >>>> would take near as much time as a Repair install. Certainly a lot more >>>> hands-on time. Dunno... >>>> >>>> -- >>>> Gary S. Terhune >>>> MS-MVP Shell/User >>>> http://www.grystmill.com >>>> >>>> "David B." <brooks.dj@nospam.hotmail.com> wrote in message >>>> news:OeBAQXC4HHA.1164@TK2MSFTNGP02.phx.gbl... >>>>> What ever floats your boat, I'd rather not waste the time if I don't >>>>> have to. >>>>> >>>>> -- >>>>> >>>>> ---- >>>>> Crosspost, do not multipost >>>>> http://www.blakjak.demon.co.uk/mul_crss.htm >>>>> How to ask a question http://support.microsoft.com/kb/555375 >>>>> How to Post http://www.dts-l.org/goodpost.htm >>>>> _________________________________________________________________________________ >>>>> >>>>> >>>>> "Gary S. Terhune" <none> wrote in message >>>>> news:eof0ITC4HHA.484@TK2MSFTNGP06.phx.gbl... >>>>>> So, there goes your "whether it successfully boots or not after a >>>>>> motherboard swap is 100% related to the old and new hard drive >>>>>> controller." >>>>>> >>>>>> All in all, I think I'd prefer a Repair install. >>>>>> >>>>>> -- >>>>>> Gary S. Terhune >>>>>> MS-MVP Shell/User >>>>>> http://www.grystmill.com >>>>>> >>>>>> "David B." <brooks.dj@nospam.hotmail.com> wrote in message >>>>>> news:eYjM03q2HHA.1208@TK2MSFTNGP05.phx.gbl... >>>>>>> In rare cases maybe, I have had probably a 95 to 99% success rate >>>>>>> using the method I outlined. >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> ---- >>>>>>> Crosspost, do not multipost >>>>>>> http://www.blakjak.demon.co.uk/mul_crss.htm >>>>>>> How to ask a question http://support.microsoft.com/kb/555375 >>>>>>> How to Post http://www.dts-l.org/goodpost.htm >>>>>>> _________________________________________________________________________________ >>>>>>> >>>>>>> >>>>>>> "John John" <audetweld@nbnot.nb.ca> wrote in message >>>>>>> news:e9Anuho2HHA.1184@TK2MSFTNGP04.phx.gbl... >>>>>>>> That is not correct. It may be correct to say that drive >>>>>>>> controller differences is the most common cause but there are other >>>>>>>> issues that can cause Windows XP not to boot when it is moved to >>>>>>>> different hardware, especially if you move it form fairly old to >>>>>>>> much newer hardware. >>>>>>>> >>>>>>>> While it is correct to say that in 100% of cases if the drive >>>>>>>> controller is different Windows will not boot, it is incorrect to >>>>>>>> say that different controller are the sole and only cause and that >>>>>>>> they are 100% responsible for boot failures when moving Windows XP >>>>>>>> to new hardware. 0x7B errors are not exclusively, 100% the sole >>>>>>>> possible error when moving Windows XP to new hardware, and it is >>>>>>>> not the only 100% thing that makes it necessary to reinstall >>>>>>>> Windows! >>>>>>>> >>>>>>>> John >>>>>>>> >>>>>>>> David B. wrote: >>>>>>>>> It is the difference in the hard drive controller that causes the >>>>>>>>> BSOD after a motherboard swap, that is the only thing that makes >>>>>>>>> it necessary for a repair install, the procedure I stated above >>>>>>>>> proves this and I have used it many times to avoid the need for a >>>>>>>>> repair install (in an upgrade situation). I would do a bit of >>>>>>>>> testing before making the statement you did, you will find out >>>>>>>>> that your wrong. >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >> >
Recommended Posts