Hubert

Hey guys, I'm planning another WinXP reinstall, and plan to use my Promise IDE RAID controller. I forget the model number, but it's an ATA133, not supported natively by WinXP AFAIK. Anyhow, on a fresh reinstall, I know I need to press F6 to get that RAID/SCSI menu. It then prompts you for a disk to put in A: My question now, I don't really want to reinstall my floppy drive (I will if I have to), so is there any way to slipstream the latest RAID drivers in the WinXP CD? RANT: I dunno why MS insists in keeping the floppy alive anyways. I don't think it would have been that hard to code the install to prompt for a driver CD, or a location on your hard drive. Oh well.

gj me. Thanks for the linkage.

The ZENITH is expensive though, but we managed a 16x200 OC (not stable). Stable OC was about 16x190.

Granite Bay would certainly be one of the better choices, but there aren't a lot of "enthusiast GNB boards. They're more workstation-ish. We've had a lot of success with the Chaintech 845PE ZENITH.

Hey all, I have a project this weekend to reformat and reinstall a NT4 server. The server is actually very clean as it is, and the only reason for the reinstall was to switch domains. It's in an old domain, then the company switched names, and would like to have it join the new one. It is not a domain controller, nor does it do anything like DHCP, WNS, DNS, etc... It is simply a member server that has the network SAN attached to it for fileserver purposes. Can I simply remove it from the current domain, and have it join the new domain without any worries about the SIDs or any other Window-isms?

duhmez, Yup, that did it. Worked like a charm. Thanks for the help everyone.

Hmm, well, it may be heat. I'd try Adam's suggestion and check the BIOS. If the shutdown temp is set too low, that could cause a problem. Now, I'm assuming this hasn't happened before with this PC, so what has changed since you first experienced this problem?

By shutting down, I am assuming it just turns off abruptly (no "shutting down Windows" message)? It can be one of three things... either a flakey PSU, dirty power lines (surges in your wall outlet), or overheating. Those are my guesses.

Thx guys. It's a pure member server (with a SAN attached). The idea is to have it moved into the new domain (with the SAN). The SAN is used to store home directories, mandatory profiles, and miscellaneous files. The netlogon is handled by another server all together. I don't plan on changing the name of this server or anything. There isn't any software running that requires any security accounts in the old or new domain. Basically, what I was planning to do was go into the network properties (my NT is rusty, so bear with me), remove it from Domain A, then make it join Domain B. I'll reboot, log in with the Domain B admin account. If I need to, I'll go into server manager of the Domain B PDC, and add the server. Am I missing anything?