nmX.Memnoch

No problem.

If you never plan on uninstalling the hotfixes then yes, they can be safely removed.

The motherboard is a component of the computer. A new motherboard in the same computer is just an upgrade to the existing computer. The end result won't be two computers, it will be one upgraded computer.

Start the install with the file you downloaded but don't click on Next or anything else. Open Windows Explorer and go to C:\Documents and Settings\<your user name>\Local Settings\Temp\. Look for a .msi file with the date/time that you started the install (so within the last minute or two). It should be named something like 6a3a75.msi. Copy that file to your Desktop and rename it to hmtcdwizard.msi. Cancel the install you started in Step 1. Now when WinXP asks for the file just point it to that one.

He's changing motherboards as well though, so it's advisable to do a fresh install. However, a Corporate edition and you don't have the CD? Something tells me it's not a legal install anyway.

Yes, you need to have an IP address configured for both computers. Set the Windows 2000 machine's IP to 192.168.0.1 and set the Windows 98 machine's IP to 192.168.0.2. Set the gateway for both machines to 192.168.0.1. You'll also need to know the DNS servers for your ISP because you'll have to configure them as well. You don't need to configure a Proxy server within IE because you're not actually running a Proxy server. ICS will turn your Windows 2000 machine into a router/gateway for other machines on your network. If you add anymore machines to your network just configure them the same way as the Windows 98 machine, but increment the IP address by one for each machine (i.e. next machine's IP would be 192.168.0.3). As for the on-demand dialing, I'm not sure...it's been a really long time since I've messed with a dial-up connection. When I did have dial-up I had that working, but that was so long ago that Windows 2000 was still in beta and was still known as Windows NT 5.0 at the time. At any rate, if it doesn't work having to manually dial the connection then you won't be able to tell if on-demand dialing will work...so let's get the manual method working first.

Even if he doesn't plan on overclocking he should splurge on a better PSU. That's one piece of hardware that has the potential to take everything with it if it goes...which is why you should always buy a quality PSU.

I was going to recommend the same NEC drive. This Poineer one is also good. I have an "older" A08 and looooooooove it. http://www.newegg.com/Product/Product.asp?...N82E16827129164 As for media, I usually stick with Memorex, but that's just my personal preference.

It does allow multithreading with a hyperthreaded P4/Xeon. From my understanding it'll even allow for a dual core CPU, but I haven't had the opportunity to test this. What it doesn't allow is SMP, or multiprocessors. Just thought I'd clear that up.

XP should work fine on that board. Did you get a blue screen error when you tried to boot it?

Use the attachement. Change the .txt extension to .reg. net_chm.txt

Add this to your logon script: powercfg /hibernate off They may need admin privs to do that though.

This shouldn't happen by default. It usually indicates one of two things: 1. His account is locked out. If he can logon and access network resources without a problem then this isn't the case. 2. The Exhange Server authentication settings are "incorrect" in his Outlook Profile. Check to see if it's set on "None". If it is, change it to NT Authentication. This should pass his credentials through automatically. If it's not either one of those then we'll need more information to help.

Windows will show that you have a floppy drive unless you disable that setting in the BIOS. This is because floppy drive controllers are "dumb" compared to PATA/SATA/SCSI controllers. I disable both the floppy controller itself and the option to tell the system what kind of floppy drives you have connected. Yes, the red stripe goes on pin #1 of the connector. Usually on the floppy it is on the OPPOSITE side as compared to HD/CD. (but there is always a "1" near the connector) jaclaz The stripe almost always goes closest to the floppy drive power connector. I have seen a few *cough*Sony*cough* floppy drives where this wasn't the case though. If the cable was incorrectly attached the activity light on the floppy would stay on all the time. I don't have floppy drives in any of my PCs anymore...but I did pick up an external USB floppy drive for that very rare occassion where I need one. This is the one I got: http://www.compusa.com/products/product_in...9956&pfp=SEARCH I could've gotten a cheaper one but I needed it right away when I got it (one of those very rare, but important occassions). They weren't kidding when they said it's a 2X speed either...that's the fastest floppy drive I've ever used.

How long did you have the first drive before you bought the second drive? It could be an incompatibility of the firmware versions on the drives since you purchased them at seperate times. It's generally advised to purchase the same make and model of drives for RAID setups, and purchase them at the same time.

It'll work but you run the chance of running into driver/registry/other issues. For instance, you'll have old drivers from the old board hanging around that you don't need anymore. Plus you'll probably have to load additional drivers for everything on the new board to work correctly. Reinstalling on a motherboard swap is highly recommended...unless you're swapping for the exact same motherboard make/model (i.e. in the case of an RMA replacement).

No problem. One of the recent critical patches changed the way .CHM files are handled on network shares. The only way to get it to work again is with that registry setting.

Is the .CHM file on a network share? If so copy and paste the below into a .REG file, then import it... Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions] "MaxAllowedZone"=dword:00000001

443 for SSL sites. Possibly 8080 as well.

Also try installing it with a regular (read: non-nLited) XP CD. As suggested, do this with and without the RAID. True that.

The /PERSISTENT:NO should take care of it...but yeah, having a log off script just to be sure doesn't hurt either. Personally, I use KiXtart scripts for my logon scripts. It allows you to do much more than just mapping drives. You can have a single script for your entire organization and still map drives depending on what group they're in. KiXtart gives you plenty of functionality. I'll post a cleaned up copy of my logon script if you're interested in seeing what you can do with it. http://www.kixtart.org/ A lot of people actually copy KIX32.EXE to all of the workstations but this isn't necessary if you're in a pure Windows 2000/XP environment. You can just call it from your NETLOGON share.

That's why I said theoretical throughput. The thinner SATA cables are much easier to route and can be much longer than that of PATA cables (not an issue in most computer cases though). I know I'll take my 10K RPM Raptors over a 7200 RPM PATA drive any day. clonesauce, you can tell by looking up the specs on the motherboard. Do you know the manufacturer and model number?

It's OEMLOGO.BMP. OEMINFO is for the INI file that contains "support" information.

Of course you can use IP printing...it's just tricky. Install the printer as if it were actually on LPT1. Then redirect LPT1 to the network device: net use LPT1: \\SERVER\Printer_Name /PERSISTENT:YES If you don't currently have the printer shared off of a server then you'll have to either install it on a server with an IP printer port or pick a workstation to install it on and share it from. Another option is to install it twice on the workstation...once for IP printing and once for LPT1 printer. Share the IP printing one, then use the net use command to redirect LPT1 back to the shared printer. We had to come up with this same work around for an old 16-bit application that we aren't quite rid of yet. Soon, but not soon enough...

Nope.