DiscardME

If you are talking about repartitioning your single physical disk (C:) into 2 logical drives, then you will need a 3rd party app. Repartioning existing logical drives is not natively supported on XP, unless you are extending, spanning or striping two physical disks. EDIT: If you just want to add a d: drive without touching your first physical disk, you can install a second physical disk in your box and use Disk Manager in Computer Management to import it. Pretty simple solution. Many retailers are selling decent size hard drives for 50 to 60 cents a GB.

Logons are logged at the authenticating domain controller in the security event log. There are options in Group Policy to enable the specific events you want logged. Computer Configuration - Windows Settings - Security Settings - Local Policies - Audit Policies. Look for events 540 and 576 for successful logins. This can be auditied either from the DC or from the local machine. Either way - you just need to enable auditing. If you go to Microsoft Technet, you can run a search on it, or you can always use google to find step by steps. Hope that points you in the right direction

If you are running windows xp and/or active directory, you can hide the all programs menu via group policy. If you have a stand alone XP box, you can do it with the local policy snap in via the same method.

What RC build of XP SP2?

There are a number of resources on the web, have you googled it? Most are dealing with a different scenarios, but they give a guidline on how to config your boot.ini and all that jazz. I would go that route... most are for linux/windows coexisting, but most give the basics. Just out of curiousity, why are you wanting to build a dual boot between 2khome and 2kpro? I can understand linux and pro or 98 and pro as dual boot systems... but if I were you, I would just use Pro and call it good. If you want to have a home version installed for programming testings, you could always use virtualPC 2004 or VMware and save yourself the hassle of a dual boot system.

Let's dispense with the obvious stuff first: When you run a ping against your host header A record, you recieve a response from the correct address? Are you running all your headers over the same port (default: 80) using "all unassigned" addresses? Are using SSL at all? Are there any unicode characters in your header name? (so your headers should only consist of A-Z, a-z, "." and "-")? Are there any spaces in your header names? Do you have any events in the Event Viewer for the w3svc service when the service starts? For your domains, are you the authorative party or is an external company handling it? Are you using a CNAME or an A record for the header DNS entry? Are you testing from the local machine, or client on the intranet or a client from the internet? Are using WINS at all? If so, do you have the header in your WINS server? Have you cleared the DNS and WINS tables on the server and on the testing client after each change/resolution? DNS: ipconfig /flushdns WINS: nbtstat -R After each change on the host headers in IIS, do you restart or manually refresh? WINS: nbtstat -RR The reason I ask all this obvious inane stuff is because host headers are generally easy, it is the registration of the associated resolution records that can screw it up. Once you have IIS setup with the headers, you can make a change to your hosts file on the local server to see if the headers work. If they do, then you can work your way out. What kind of troubleshooting have you done beyond the Microsoft procedure for the host header setup?

I know it is late on this topic, but I am running a LAN party this weekend... and I had to install UT2004 on 5 machines and I didn't want to move 6 CDs back and forth. The only thing I wanted to do was type in the unique key from all 5 cases. So on my game server, I copied each CD to a subfolder within my root UT Share (CD1, CD2, CD3, CD4, CD5, CD6). I then ran setup.exe from the CD1 folder. With ZERO changes to any file or folder, the setup went throught the entire set without prompting for a CD. It was a nice suprise! Just burn that set to a DVD and you should be set.

Stick with Northwoods. Prescotts run freaking hot and there is little performance gain. Right now - best bang for the buck is the Northwood P4 2.8. Best video card is the Radeon x800 pro... but if you want cheap, I would go with the 9600 XT. I prefer ATI, but that is only because I have had awesome support from them. I'm biased.

Are you an admin on your machine? You have to be a member of the administrators group to configure power settings.

The sata raid drivers should be under %system%\system32\drivers directory. Have you tried the recovery console? It will prompt you for the drivers, then detect the install, then using the prompt, copy them over manually or try a repair. If you have a fresh install, it would only take 40 minutes to do a reinstall without skipping that step. That would probably be the easiest way. Hope that helps.

Also go into your BIOS, (F2 on Dell I believe), and restore default settings. Go into your device manager and check your DMA modes on the IDE drive channels. Set them to DMA mode. PIO is sometimes used and can impact drive operation. Call Dell. You may have a faulty mobo. Hope that helps

Mviking~ That is an interesting issue. For questions 1 & 2: The only DFS whitepapers I have seen are available from Microsoft or ITpapers.com, there may be more out there, but ITpapers is a good place to start (free registration req). I have not seen domain spanning specific articles, but I also haven't seen anything that would prevent your DFS from spanning parent/child domains. How is your DNS namespace configured? All vanilla (AD integrated, KCC defined replication, etc.)? Or do you have any custom configurations there as well? Are you able to connect to the server\share from the remote directly (circumvention of the dfs namespace)? A great way to troubleshoot is to check sysvol for your domain/subddomain. \\company.com\sysvol, \\branch.company.com\sysvol. What user groups do you have setup on your DFS root? Domain Users, Authenticated Users, or a custom group setup? For many issues, the sysvol and the dfs are a great comparison for troubleshooting, since they operate in a very similar manner. Permissions are generally important. I would give the root of the DFS authenticated users and domain users as a troubleshooting step, then work outwards. Establish as general permissions as you can on the dfs root. Make sure your file folder permissions are all in sync as well at every link location. For question 3: I would start with Ultrasound for general observation of our your replication structure. I have used it extensively to solve a myriad of issues at my company on both the sysvol and dfs roots. Then I would hit this page for a number of utils (Ultrasound link is on this page too): FRS Tools I hope that helps, I know it is not probably as specific as you would like, but it could offer a starting point.