New motherboard - reconfiguring Windows
-
Can you tell me the old MB versus the new MB model? Why did they say they could not replace with the original? (Remember who I work for....)
______________________________________ Computer programmers are like umpires. No one knows your name until you screw up.
leckey wrote:
Can you tell me the old MB versus the new MB model? Why did they say they could not replace with the original?
The old MB is an N1996, Micro Star model MS-7184. The new MB doesn't have any distinguish info that I could see. I would have hoped that eMachines would have a database of the hardware configuration to match with the serial # or the PO, but no such luck. When I talked to eMachines, they only asked me about the CPU socket and RAM. Unfortunately, I didn't see the model # on the old MB until just NOW!!! The major differences are AGP thing and the old MB had a firewire connector to the front panel, plus audio in/out going to the front panel. Both are minor losses. Marc
-
Marc Clifton wrote:
Can Windows be "retrained" as to the new and different MB hardware, or do I need to reinstall Windows?
Yes, I have done this many times at work. You may want to boot into vga mode. One problem you will have is activation as XP or better will not probably not activate on the new motherboard without calling Microsoft and explaining the issue.
Last modified: 1hr 14mins after originally posted --
John
Yeah, on the plus side(?) though, the phone system is computerized not outsourced. With a system builder license I just had to enter my serial and say that the old board was doa, and I wasn't being bad and installing on multiple boxes.
-- If you view money as inherently evil, I view it as my duty to assist in making you more virtuous.
-
leckey wrote:
Can you tell me the old MB versus the new MB model? Why did they say they could not replace with the original?
The old MB is an N1996, Micro Star model MS-7184. The new MB doesn't have any distinguish info that I could see. I would have hoped that eMachines would have a database of the hardware configuration to match with the serial # or the PO, but no such luck. When I talked to eMachines, they only asked me about the CPU socket and RAM. Unfortunately, I didn't see the model # on the old MB until just NOW!!! The major differences are AGP thing and the old MB had a firewire connector to the front panel, plus audio in/out going to the front panel. Both are minor losses. Marc
Okay, so he probably has one of the following models: H6412 T6412 H6524 J6448 T6524 Here is the deal...there is NO substitution for that motherboard. Have him call back the number and tell him the Gateway part number for the MB is 104571.
______________________________________ Computer programmers are like umpires. No one knows your name until you screw up.
-
Yeah, on the plus side(?) though, the phone system is computerized not outsourced. With a system builder license I just had to enter my serial and say that the old board was doa, and I wasn't being bad and installing on multiple boxes.
-- If you view money as inherently evil, I view it as my duty to assist in making you more virtuous.
I have had the dead board problem once with a friend so I had to call. At work we have a corporate version of XP and other site licenses that do not have activation although we do make sure our license count is at least as many as we are using.
John
-
Marc Clifton wrote:
Can Windows be "retrained" as to the new and different MB hardware, or do I need to reinstall Windows?
Yes, I have done this many times at work. You may want to boot into vga mode. One problem you will have is activation as XP or better will not probably not activate on the new motherboard without calling Microsoft and explaining the issue.
Last modified: 1hr 14mins after originally posted --
John
John M. Drescher wrote:
One problem you will have is activation as XP or better will not probably not activate on the new motherboard without calling Microsoft and explaining the issue.
I have called MS so many times they have me on their database. ;) Honestly, the same copy of XP has been upgraded in hardware so many times it is insane. I explain the situation, brag about my upgrade a tad to make them think I am one of those update-every-week-geeks, and then no problem. I could probably say I am a tech, which is closer to the truth. :) But MS has never given me any problems over the hardware upgrades.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
The history: My neighbor's MB was wiped out with a lightning strike that came in through her phone line. I replaced the MB, but the company (e-machines) didn't send an identical MB (which, apparently is pretty impossible). Windows boots up in Safe mode, but in normal boot, it blue screens, undoubtedly because of differences in the MB, like there's no AGP on this MB. The question: Can Windows be "retrained" as to the new and different MB hardware, or do I need to reinstall Windows? Marc
One trick that has sometimes worked for me is to go into device manager in safe mode and remove all the drivers letting windows re-detect everything on the next boot.
This blanket smells like ham
-
The history: My neighbor's MB was wiped out with a lightning strike that came in through her phone line. I replaced the MB, but the company (e-machines) didn't send an identical MB (which, apparently is pretty impossible). Windows boots up in Safe mode, but in normal boot, it blue screens, undoubtedly because of differences in the MB, like there's no AGP on this MB. The question: Can Windows be "retrained" as to the new and different MB hardware, or do I need to reinstall Windows? Marc
Do you really want to fix/repair/reinstall to a HD which has "survived" a lightning strike? Think about that for a moment.
Todd Smith
-
Do you really want to fix/repair/reinstall to a HD which has "survived" a lightning strike? Think about that for a moment.
Todd Smith
Todd Smith wrote:
Do you really want to fix/repair/reinstall to a HD which has "survived" a lightning strike? Think about that for a moment.
The drive, CPU and memory all appear to be functional. Marc
-
Okay, so he probably has one of the following models: H6412 T6412 H6524 J6448 T6524 Here is the deal...there is NO substitution for that motherboard. Have him call back the number and tell him the Gateway part number for the MB is 104571.
______________________________________ Computer programmers are like umpires. No one knows your name until you screw up.
leckey wrote:
there is NO substitution for that motherboard
So I noticed. :) I've found a company in the UK that sells the exact MB , so that'll be the way I'm going to go. Marc
-
Okay, so he probably has one of the following models: H6412 T6412 H6524 J6448 T6524 Here is the deal...there is NO substitution for that motherboard. Have him call back the number and tell him the Gateway part number for the MB is 104571.
______________________________________ Computer programmers are like umpires. No one knows your name until you screw up.
hmmmm. emachines won't allow anything else to be used as a substitute and send the wrong board by mistake? Or, there's nothing on the market that is an exact substitute?
-- If you view money as inherently evil, I view it as my duty to assist in making you more virtuous.
-
Todd Smith wrote:
Do you really want to fix/repair/reinstall to a HD which has "survived" a lightning strike? Think about that for a moment.
The drive, CPU and memory all appear to be functional. Marc
You're still playing with fire though. If it's under warranty I'd stick the drive in a second box to recover data and try to make the vendor replace everything. IF it's not covered I'd warn the owner about the risk and image the drive just to be safe.
-- If you view money as inherently evil, I view it as my duty to assist in making you more virtuous.
-
You're still playing with fire though. If it's under warranty I'd stick the drive in a second box to recover data and try to make the vendor replace everything. IF it's not covered I'd warn the owner about the risk and image the drive just to be safe.
-- If you view money as inherently evil, I view it as my duty to assist in making you more virtuous.
dan neely wrote:
IF it's not covered I'd warn the owner about the risk and image the drive just to be safe.
Ah, I'll do that. I've already made a backup of the data when I verified the drive wasn't dead after the lightning strike. :) Marc
-
hmmmm. emachines won't allow anything else to be used as a substitute and send the wrong board by mistake? Or, there's nothing on the market that is an exact substitute?
-- If you view money as inherently evil, I view it as my duty to assist in making you more virtuous.
There may be a substitution on the market, but I checked our master database and Gateway(emachines) does not list a sub for that MB. Unfortunately we use a third party for our parts replacements. We have had issues with them in the past.
______________________________________ Computer programmers are like umpires. No one knows your name until you screw up.
-
John M. Drescher wrote:
One problem you will have is activation as XP or better will not probably not activate on the new motherboard without calling Microsoft and explaining the issue.
I have called MS so many times they have me on their database. ;) Honestly, the same copy of XP has been upgraded in hardware so many times it is insane. I explain the situation, brag about my upgrade a tad to make them think I am one of those update-every-week-geeks, and then no problem. I could probably say I am a tech, which is closer to the truth. :) But MS has never given me any problems over the hardware upgrades.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
I've had to phone for activation after online activation failed exactly once, for our MSDN subscription key IIRC. It was a quick friendly conversation and since then we've had no trouble reusing the MSDN key on any amount of different hardware, both physical and virtual.
DoEvents: Generating unexpected recursion since 1991