If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#46
|
|||
|
|||
Replace Mobo in XP??
relic wrote:
| jim wrote: || "philo" wrote in message || ... ||| ||| |||| You may also want to look into running a repair installation after |||| switching to the new hardware. This will allow you to keep |||| programs and settings while getting around the driver issue. |||| Bob |||| |||| |||| That seems to be the easiest solution. ||| ||| ||| ||| I agree, the repair installtion only takes a few minutes... ||| and all you need do afterwards is re-apply the updates || || No, the two together take at least an hour. | | Not for someone who knows how. 4 Minutes here. -- Gazwad Freelance scientist and people tester. Guardian: alt.os.windows-xp Moderator: alt.warez.uk www.gazwad.com |
Ads |
#47
|
|||
|
|||
Replace Mobo in XP??
-Cryogenic-© wrote:
| Ron Martell wrote: | || The "Repair Install" approach is well proven and is safe. | | He doesn't want that. He wants someone to hold his hand and do it | /his/ way. If you don't he'll hide in the corner with his dead PCs | and suck his thumb. Marginally more acceptable than shoving his thumb up his arse and pulling out a disk drive. -- Gazwad Freelance scientist and people tester. Guardian: alt.os.windows-xp Moderator: alt.warez.uk www.gazwad.com |
#48
|
|||
|
|||
Replace Mobo in XP??
"Ron Martell" wrote in message ... "jim" wrote: That page is by one of the old foggie "can't be done" set. The article impeaches itself early on with "Since the repair install in my opinion is an absolute necessity when changing a motherboard or moving a hard drive with XP installed, " Check the URL in my opening post here by someone who is actually working the issue I'm interested in: www.mostlycreativeworkshop.com/article11.html You are of course free to do whatever you want with your own computer. However postings in these newsgroups also serve as advice to others regarding the issues discussed and I for one am not about to advocate high risk procedures where safer alternatives exist. The simple fact is that the approach you advocate will in many cases result in computers being crashed/smashed/trashed because of the hardware changes. Utter nonsense. What's being discussed trashes nothing. It work or it doesn't. There are and have been a bunch of wackos running around saying "it doesn't work so don't dare try it". The real message from these folks is "I tried it once and couldn't make it work so don't dare show that it can be done and expose for my short comings". The "Repair Install" approach is well proven and is safe. AND SLOW. |
#49
|
|||
|
|||
Replace Mobo in XP??
"relic" wrote in message news jim wrote: "philo" wrote in message ... You may also want to look into running a repair installation after switching to the new hardware. This will allow you to keep programs and settings while getting around the driver issue. Bob That seems to be the easiest solution. I agree, the repair installtion only takes a few minutes... and all you need do afterwards is re-apply the updates No, the two together take at least an hour. Not for someone who knows how. Wrong. Why don't you contribute by having a look here and commenting: www.mostlycreativeworkshop.com/article11.html |
#50
|
|||
|
|||
Replace Mobo in XP??
Really?
I have swapped quite a few motherboards with XP Pro. When XP restarted it detected all the new hardware and installed (or asked for) any new drivers that were needed. Never had a problem... On Wed, 28 Apr 2004 20:14:04 -0700, "jim" wrote: I'd like to ask some questions about replacing/changing a mobo in an XP pro system. I've done some research on this issue and have come to the following conclusions. XP is not quite as Plug & Play as 98[SE] was in this regard. One can not just take the OS HD and put it in another box and expect it to boot and re-find everything and install all the appropriate drivers etc. like it would in 98SE. The limitations appear to be in two areas. The first is the HAL which is a function of the CPU and number thereof and presence/absence of ACPI mobo BIOS. The second is the HD drivers. I've found all sorts of site/articles regarding how to do this and fix these issues for the mobo ATA controller case. Other HD cases seem to be tractable using the F6 install drivers(SCSI technique). One that seems to be similar to many others regarding the mobo ATA HD issue is: www.mostlycreativeworkshop.com/article11.html My conclusion is that one should make the registry and file additions on any XP system so that failure recovery on new hardware is more convenient at a later time. Am I missing something here or is that about right. The second issue is that HAL. If the old and new systems are single CPU ACPI mobos then everything works. It makes no difference is one is a VIA chipset and Athlon and the other an Intel chipset and an Intel CPU. Do I have this right so far? If one is going from a single CPU case to a new P4 supporting HT then one must force in a new HAL for multiprocessor ACPI. Apparently that can be done in Recovery console or by putting the HD in another system where files may be manipulated before attempting a boot on the new mobo. Right so far? Are the above the only two issues? Will all the other gadgets and chipsets etc. be redetected and appropriate drivers installed? Will one be able to boot and move forward in most all cases if the above two issues are dealt with? |
#51
|
|||
|
|||
Replace Mobo in XP??
jim spewed forth with the following drivel: "relic" wrote in message news jim wrote: "philo" wrote in message ... You may also want to look into running a repair installation after switching to the new hardware. This will allow you to keep programs and settings while getting around the driver issue. Bob That seems to be the easiest solution. I agree, the repair installtion only takes a few minutes... and all you need do afterwards is re-apply the updates No, the two together take at least an hour. Not for someone who knows how. Wrong. Why don't you contribute by having a look here and commenting: www.mostlycreativeworkshop.com/article11.html No YOU are wrong. Do you really think your little webpage will prove WE can't do what we say we can? Only morons cannot do as Relic suggests. I guess that makes you a moron. You are a nitwit and a poor loser. Now slink away. -- Buster Gatekeeper: alt.os.windows-xp |
#52
|
|||
|
|||
Replace Mobo in XP??
"Zknb" rtjeopr.com wrote in message st.giganews.com... Really? I have swapped quite a few motherboards with XP Pro. When XP restarted it detected all the new hardware and installed (or asked for) any new drivers that were needed. Never had a problem... Yep, that's what many report even when the mobos use different chipsets. If the multiprocessor and/or ACPI situation chnages then things aren't quite that easy but still tractable. I'm trying to gather more information from folks on exactly what works transparently and what needs a like help with respect to HW changes. What were the characteristics of the old and new mobos in the cases you've tried? On Wed, 28 Apr 2004 20:14:04 -0700, "jim" wrote: I'd like to ask some questions about replacing/changing a mobo in an XP pro system. I've done some research on this issue and have come to the following conclusions. XP is not quite as Plug & Play as 98[SE] was in this regard. One can not just take the OS HD and put it in another box and expect it to boot and re-find everything and install all the appropriate drivers etc. like it would in 98SE. The limitations appear to be in two areas. The first is the HAL which is a function of the CPU and number thereof and presence/absence of ACPI mobo BIOS. The second is the HD drivers. I've found all sorts of site/articles regarding how to do this and fix these issues for the mobo ATA controller case. Other HD cases seem to be tractable using the F6 install drivers(SCSI technique). One that seems to be similar to many others regarding the mobo ATA HD issue is: www.mostlycreativeworkshop.com/article11.html My conclusion is that one should make the registry and file additions on any XP system so that failure recovery on new hardware is more convenient at a later time. Am I missing something here or is that about right. The second issue is that HAL. If the old and new systems are single CPU ACPI mobos then everything works. It makes no difference is one is a VIA chipset and Athlon and the other an Intel chipset and an Intel CPU. Do I have this right so far? If one is going from a single CPU case to a new P4 supporting HT then one must force in a new HAL for multiprocessor ACPI. Apparently that can be done in Recovery console or by putting the HD in another system where files may be manipulated before attempting a boot on the new mobo. Right so far? Are the above the only two issues? Will all the other gadgets and chipsets etc. be redetected and appropriate drivers installed? Will one be able to boot and move forward in most all cases if the above two issues are dealt with? |
#53
|
|||
|
|||
Replace Mobo in XP??
"Ron Martell" wrote in message ... "jim" wrote: That page is by one of the old foggie "can't be done" set. The article impeaches itself early on with "Since the repair install in my opinion is an absolute necessity when changing a motherboard or moving a hard drive with XP installed, " Check the URL in my opening post here by someone who is actually working the issue I'm interested in: www.mostlycreativeworkshop.com/article11.html You are of course free to do whatever you want with your own computer. However postings in these newsgroups also serve as advice to others regarding the issues discussed and I for one am not about to advocate high risk procedures where safer alternatives exist. The simple fact is that the approach you advocate will in many cases result in computers being crashed/smashed/trashed because of the hardware changes. Utter nonsense. What's being discussed trashes nothing. It work or it doesn't. There are and have been a bunch of wackos running around saying "it doesn't work so don't dare try it". The real message from these folks is "I tried it once and couldn't make it work so don't dare show that it can be done and expose for my short comings". The "Repair Install" approach is well proven and is safe. AND SLOW. |
#54
|
|||
|
|||
Replace Mobo in XP??
"relic" wrote in message news jim wrote: "philo" wrote in message ... You may also want to look into running a repair installation after switching to the new hardware. This will allow you to keep programs and settings while getting around the driver issue. Bob That seems to be the easiest solution. I agree, the repair installtion only takes a few minutes... and all you need do afterwards is re-apply the updates No, the two together take at least an hour. Not for someone who knows how. Wrong. Why don't you contribute by having a look here and commenting: www.mostlycreativeworkshop.com/article11.html |
#55
|
|||
|
|||
Replace Mobo in XP??
Really?
I have swapped quite a few motherboards with XP Pro. When XP restarted it detected all the new hardware and installed (or asked for) any new drivers that were needed. Never had a problem... On Wed, 28 Apr 2004 20:14:04 -0700, "jim" wrote: I'd like to ask some questions about replacing/changing a mobo in an XP pro system. I've done some research on this issue and have come to the following conclusions. XP is not quite as Plug & Play as 98[SE] was in this regard. One can not just take the OS HD and put it in another box and expect it to boot and re-find everything and install all the appropriate drivers etc. like it would in 98SE. The limitations appear to be in two areas. The first is the HAL which is a function of the CPU and number thereof and presence/absence of ACPI mobo BIOS. The second is the HD drivers. I've found all sorts of site/articles regarding how to do this and fix these issues for the mobo ATA controller case. Other HD cases seem to be tractable using the F6 install drivers(SCSI technique). One that seems to be similar to many others regarding the mobo ATA HD issue is: www.mostlycreativeworkshop.com/article11.html My conclusion is that one should make the registry and file additions on any XP system so that failure recovery on new hardware is more convenient at a later time. Am I missing something here or is that about right. The second issue is that HAL. If the old and new systems are single CPU ACPI mobos then everything works. It makes no difference is one is a VIA chipset and Athlon and the other an Intel chipset and an Intel CPU. Do I have this right so far? If one is going from a single CPU case to a new P4 supporting HT then one must force in a new HAL for multiprocessor ACPI. Apparently that can be done in Recovery console or by putting the HD in another system where files may be manipulated before attempting a boot on the new mobo. Right so far? Are the above the only two issues? Will all the other gadgets and chipsets etc. be redetected and appropriate drivers installed? Will one be able to boot and move forward in most all cases if the above two issues are dealt with? |
#56
|
|||
|
|||
Replace Mobo in XP??
jim spewed forth with the following drivel: "relic" wrote in message news jim wrote: "philo" wrote in message ... You may also want to look into running a repair installation after switching to the new hardware. This will allow you to keep programs and settings while getting around the driver issue. Bob That seems to be the easiest solution. I agree, the repair installtion only takes a few minutes... and all you need do afterwards is re-apply the updates No, the two together take at least an hour. Not for someone who knows how. Wrong. Why don't you contribute by having a look here and commenting: www.mostlycreativeworkshop.com/article11.html No YOU are wrong. Do you really think your little webpage will prove WE can't do what we say we can? Only morons cannot do as Relic suggests. I guess that makes you a moron. You are a nitwit and a poor loser. Now slink away. -- Buster Gatekeeper: alt.os.windows-xp |
#57
|
|||
|
|||
Replace Mobo in XP??
"Zknb" rtjeopr.com wrote in message st.giganews.com... Really? I have swapped quite a few motherboards with XP Pro. When XP restarted it detected all the new hardware and installed (or asked for) any new drivers that were needed. Never had a problem... Yep, that's what many report even when the mobos use different chipsets. If the multiprocessor and/or ACPI situation chnages then things aren't quite that easy but still tractable. I'm trying to gather more information from folks on exactly what works transparently and what needs a like help with respect to HW changes. What were the characteristics of the old and new mobos in the cases you've tried? On Wed, 28 Apr 2004 20:14:04 -0700, "jim" wrote: I'd like to ask some questions about replacing/changing a mobo in an XP pro system. I've done some research on this issue and have come to the following conclusions. XP is not quite as Plug & Play as 98[SE] was in this regard. One can not just take the OS HD and put it in another box and expect it to boot and re-find everything and install all the appropriate drivers etc. like it would in 98SE. The limitations appear to be in two areas. The first is the HAL which is a function of the CPU and number thereof and presence/absence of ACPI mobo BIOS. The second is the HD drivers. I've found all sorts of site/articles regarding how to do this and fix these issues for the mobo ATA controller case. Other HD cases seem to be tractable using the F6 install drivers(SCSI technique). One that seems to be similar to many others regarding the mobo ATA HD issue is: www.mostlycreativeworkshop.com/article11.html My conclusion is that one should make the registry and file additions on any XP system so that failure recovery on new hardware is more convenient at a later time. Am I missing something here or is that about right. The second issue is that HAL. If the old and new systems are single CPU ACPI mobos then everything works. It makes no difference is one is a VIA chipset and Athlon and the other an Intel chipset and an Intel CPU. Do I have this right so far? If one is going from a single CPU case to a new P4 supporting HT then one must force in a new HAL for multiprocessor ACPI. Apparently that can be done in Recovery console or by putting the HD in another system where files may be manipulated before attempting a boot on the new mobo. Right so far? Are the above the only two issues? Will all the other gadgets and chipsets etc. be redetected and appropriate drivers installed? Will one be able to boot and move forward in most all cases if the above two issues are dealt with? |
#58
|
|||
|
|||
Replace Mobo in XP??
"jim" wrote:
I'd like to ask some questions about replacing/changing a mobo in an XP pro system. I've done some research on this issue and have come to the following conclusions. XP is not quite as Plug & Play as 98[SE] was in this regard. One can not just take the OS HD and put it in another box and expect it to boot and re-find everything and install all the appropriate drivers etc. like it would in 98SE. Not true. Windows 95/98/Me required specific detailed steps in order to *successfully* replace a motherboard. Usually this involved at least manually deleting all relevant items from Device Manager or (even better) deleting the HKEY_LOCAL_MACHINE\Enum key from the registry. Otherwise there would be a proliferation of obsolete and duplicated items in Device Manager which could adversely affect performance. The limitations appear to be in two areas. The first is the HAL which is a function of the CPU and number thereof and presence/absence of ACPI mobo BIOS. The second is the HD drivers. I've found all sorts of site/articles regarding how to do this and fix these issues for the mobo ATA controller case. Other HD cases seem to be tractable using the F6 install drivers(SCSI technique). One that seems to be similar to many others regarding the mobo ATA HD issue is: www.mostlycreativeworkshop.com/article11.html My conclusion is that one should make the registry and file additions on any XP system so that failure recovery on new hardware is more convenient at a later time. Am I missing something here or is that about right. The second issue is that HAL. If the old and new systems are single CPU ACPI mobos then everything works. It makes no difference is one is a VIA chipset and Athlon and the other an Intel chipset and an Intel CPU. Do I have this right so far? Nope. Totally wrong. Can you fix a Ford with Chev parts? If one is going from a single CPU case to a new P4 supporting HT then one must force in a new HAL for multiprocessor ACPI. Apparently that can be done in Recovery console or by putting the HD in another system where files may be manipulated before attempting a boot on the new mobo. Right so far? Are the above the only two issues? Will all the other gadgets and chipsets etc. be redetected and appropriate drivers installed? Will one be able to boot and move forward in most all cases if the above two issues are dealt with? See http://michaelstevenstech.com/moving_xp.html for factual information about how to do this in Windows XP. Ron Martell Duncan B.C. Canada -- Microsoft MVP On-Line Help Computer Service http://onlinehelp.bc.ca "The reason computer chips are so small is computers don't eat much." |
#59
|
|||
|
|||
Replace Mobo in XP??
"jim" wrote:
I'd like to ask some questions about replacing/changing a mobo in an XP pro system. I've done some research on this issue and have come to the following conclusions. XP is not quite as Plug & Play as 98[SE] was in this regard. One can not just take the OS HD and put it in another box and expect it to boot and re-find everything and install all the appropriate drivers etc. like it would in 98SE. Not true. Windows 95/98/Me required specific detailed steps in order to *successfully* replace a motherboard. Usually this involved at least manually deleting all relevant items from Device Manager or (even better) deleting the HKEY_LOCAL_MACHINE\Enum key from the registry. Otherwise there would be a proliferation of obsolete and duplicated items in Device Manager which could adversely affect performance. The limitations appear to be in two areas. The first is the HAL which is a function of the CPU and number thereof and presence/absence of ACPI mobo BIOS. The second is the HD drivers. I've found all sorts of site/articles regarding how to do this and fix these issues for the mobo ATA controller case. Other HD cases seem to be tractable using the F6 install drivers(SCSI technique). One that seems to be similar to many others regarding the mobo ATA HD issue is: www.mostlycreativeworkshop.com/article11.html My conclusion is that one should make the registry and file additions on any XP system so that failure recovery on new hardware is more convenient at a later time. Am I missing something here or is that about right. The second issue is that HAL. If the old and new systems are single CPU ACPI mobos then everything works. It makes no difference is one is a VIA chipset and Athlon and the other an Intel chipset and an Intel CPU. Do I have this right so far? Nope. Totally wrong. Can you fix a Ford with Chev parts? If one is going from a single CPU case to a new P4 supporting HT then one must force in a new HAL for multiprocessor ACPI. Apparently that can be done in Recovery console or by putting the HD in another system where files may be manipulated before attempting a boot on the new mobo. Right so far? Are the above the only two issues? Will all the other gadgets and chipsets etc. be redetected and appropriate drivers installed? Will one be able to boot and move forward in most all cases if the above two issues are dealt with? See http://michaelstevenstech.com/moving_xp.html for factual information about how to do this in Windows XP. Ron Martell Duncan B.C. Canada -- Microsoft MVP On-Line Help Computer Service http://onlinehelp.bc.ca "The reason computer chips are so small is computers don't eat much." |
#60
|
|||
|
|||
Replace Mobo in XP??
"one_red_eye" wrote in message Do you intend to do this on many computers? Yep, as a general maintenance/recovery/upgrade technique. |
Thread Tools | |
Display Modes | |
|
|