legacycentral bbs

Let me give you all a tip. If you are running windows 2000, XP, or any other NT based M$ OS, and decide to change your motherboard.....read this:
http://support.microsoft.com/default.as ... -us;824125

It'll save you some time and headache. I wouldn't say it's a flawless solution, but it'll get ya back up and running.

The mb on my server has seen better days. It only registered one of the processors, even though both were good. So I swapped out that board for one Devin sent me. After fooling with it last night till like 3, I got things working today. It works, however there's some little things that are weird.

It needs to be redone, but at least it'll give me some time to figure out what I want to do about getting some new hardware for it.

Depending on how much stuff you have on your server, I would reccomend getting the MB up and running then installing a clean install of whatever OS you are running. It will save you from having driver/device conflicts.

Thats what I do. Just back-up everything to a networked drive and then fdisk and install.

To each their own though.

Yeah I can do that, it's not a big deal...but I was feeling sort of lazy. The reason I didn't was because I don't intend to keep this hardware setup too long, plus I had wanted to upgrade to windows 2003 server.

Plus this server has a lot of shit running on it, and a decent amount of configuration/security setup required. So between those two things....I didn't really feel like doing it twice.

The server's up and running. I think the main issues I was having was due to the fact that things were configured previously, however when I reinstalled windows, it set them back to default settings but never removed the existing configurations. So they showed configured, but weren't.

I feel you on that.

What are you running as far as hardware is concerned....what do you plan on running in the future?

Hey whenever you change the motherboard, and sometimes when you change the processor and, as I have recently figured out, dvd burners there is a quick fix.

Just do a repair install. It will fix the hardware checks and fix the registry settings. Its a not so well known fix. I learned about it when working for my school as one of their lab techs.

It LOOKS like your reinstalling the OS, but your not, its a repair install (not the same as the repair console in DOS that you can get to). All your programs will still be there.

This works on XP and Server 2003.

Edit for additional information:
(I read the rest of the article and it sounds like that's what it is saying. Sorry. I shouldn't have just skimmed the title before I wrote my response.)

-Ryan

Also, I don't think you can just upgrade from server 2000 to 2003 can you? I think you have to completely reinstall the OS.

Josh, any time windows detects a major hardware change, you have to reinstall. It's a fail safe built in to keep people from stealing hard drives.

I still can't get over the "windows server" part

0perose wrote:I still can't get over the "windows server" part

Windows 2003 is very good..for being Windows. I wouldn't put it on a Unix level..but close.

Manarius wrote:Josh, any time windows detects a major hardware change, you have to reinstall. It's a fail safe built in to keep people from stealing hard drives.

I haven't had that problem...And I've swapped a HD onto an entirely new computer

wiscon_mark wrote:I haven't had that problem...And I've swapped a HD onto an entirely new computer

That's what the Microsoft guy told me. It happened to me when I swapped Motherboards. Happened again when I swapped Processors...

guess it depends on a lot of things, my OS was W98...

subawhatsubawho wrote:I feel you on that.

What are you running as far as hardware is concerned....what do you plan on running in the future?

I was running an old Abit BP6 board. Dual celeron 533, 512 mb of ram, IDE raid 0. This was setup back in 01.

As for future....don't know yet.

georryan wrote:Hey whenever you change the motherboard, and sometimes when you change the processor and, as I have recently figured out, dvd burners there is a quick fix.

Just do a repair install. It will fix the hardware checks and fix the registry settings. Its a not so well known fix. I learned about it when working for my school as one of their lab techs.

It LOOKS like your reinstalling the OS, but your not, its a repair install (not the same as the repair console in DOS that you can get to). All your programs will still be there.

This works on XP and Server 2003.

Edit for additional information:
(I read the rest of the article and it sounds like that's what it is saying. Sorry. I shouldn't have just skimmed the title before I wrote my response.)

-Ryan

I tried the repair option first.....that's what I expected to work, however it didn't.....I've done it before, but it didn't work this time.

The upgarde option took care of it...however I think I messed some stuff up before hand, which is why I had some issues...

georryan wrote:Also, I don't think you can just upgrade from server 2000 to 2003 can you? I think you have to completely reinstall the OS.

Yeah I think you can upgrade....it wouldn't be an ideal path, but I think it'd work.

Manarius wrote:Josh, any time windows detects a major hardware change, you have to reinstall. It's a fail safe built in to keep people from stealing hard drives.

I believe what you're referring to is built into XP and 2003, and not 2000. It has to deal with windows activation, and such. If a hardware change is detected, you have to reactivate windows. However I don't know what the level of hardware change causes you to have to reactivate.

wiscon_mark wrote:guess it depends on a lot of things, my OS was W98...

98 (9x) was great....you could just swap a mb and other stuff in, and it'd detect all the new hardware.

Josh is right...on most of the new WIN stuff it makes a "list" of your hardware and sends this list to MS when registering your OS. If you have the OEM license then it isn't too hard to upgrade your system as long as you don't mind talking to someone in India for a few hours.

"Thank you for calling Smell computer tech support...how may I help you today?"

"I hear that someone is there 24 hours a day 7 days a week to answer my tech support questions!"

"Yes....I am here 24 hours a day 7 days a week to help you. Oh my. I work alot."

"Did you just say you are there 24 hours a day 7 days a week."

"Yes...it is just me."

The list doesn't get sent to MS I believe. Your specific harware setup creates a unique identifier that is stored in the registry. When that changes, the OS requires reactivation.

What does get sent to MS is the number of times you've activated the product though. How they keep track of all that stuff, I don't know....and have they changed it since I've last looked into it.....it's possible.

Legacy777 wrote:The list doesn't get sent to MS I believe. Your specific harware setup creates a unique identifier that is stored in the registry. When that changes, the OS requires reactivation.

What does get sent to MS is the number of times you've activated the product though. How they keep track of all that stuff, I don't know....and have they changed it since I've last looked into it.....it's possible.

They forget how many times they've activated it....I've activated this version of windows at least 6 times and they just ask me why and then they activate it.