nmX.Memnoch

Deja Vu... http://www.msfn.org/board/index.php?showtopic=69306

What RAID controller are you using? Or are you trying to use Windows 2000's built in software RAID (which is not recommended).

A channel is a single connector for devices. SCSI controllers use IDs to determine a drives position (muhc like Master and Slave with IDE, but numbers instead). Each channel has an ID of 0 through 15, with the SCSI controller using one ID for itself (usually 7). SCSI controllers can have anywhere from 1 to 4 channels. With a 4 channel controller you can have up to 60 total devices connected. If you use hotswap drives then you'll likely have some sort of backplane they plug into. This will also take an ID (varies). The good thing about using hotswap with a backplane is that they usually auto assign the SCSI ID to the drive(s)...otherwise you have to manually set each drive, making sure that no two are set to the same ID. See attached screenshot for an example of a system with multiple SCSI RAID controllers, one using the systems internal hotswap backplane, the other attached to two external drive enclosures.

The QuickLaunch settings are stored in the following key/value: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams\Desktop Value: TaskbarWinXP Type: REG_BINARY Data: varies

It's probably the space in your OU name. Try these: dsquery user -disabled | dsmove user -newparent ou="disabled group",dc=etc,dc=etc,dc=etc dsquery user -disabled | dsmove user -newparent "ou='disabled group',dc=etc,dc=etc,dc=etc" Another question...is "Disabled Group" under another OU?

My Intel wireless NICs don't have any problems staying connected to Linksys routers.

I forgot about these registry tweaks as well... Disable ToggleKeys HKEY_CURRENT_USER\Control Panel\Accessibility\Toggle Keys Value: Flags Data: 58 Type: REG_SZ Disable FilterKeys HKEY_CURRENT_USER\Control Panel\Accessibility\Keyboard Response Value: Flags Data: 122 Type: REG_SZ Disable StickyKeys HKEY_CURRENT_USER\Control Panel\Accessibility\StickyKeys Value: Flags Data: 506 Type: REG_SZ

Are you running Active Directory? If so, there are options in Group Policy to prevent Messenger from being used even if it's installed.

Some NICs support methods of teaming, load balancing, and/or failvoer via the drivers (all Intel Server Adapters support these features). Using the Intel driver features it "teams" the adapters to make a single connection for the OS (think of a set of RAID'ed drives, you only get the one drive). The driver and application handle splitting up the traffic. Server 2003 has features built in to support this with any pair of network cards. I've never used it but it supposedly works very well. However, on a typical home network you're not going to notice any difference using either method. There are several reasons for this. One of those being that the PCI bus doesn't have the throughput for even a single Gigabit NIC. PCI Express is different, but you still won't notice the difference on a typical home network. And you most certainly won't notice the difference on a single cable modem connection because even a 10Mbit NIC is plenty fast enough for those.

That CPU is not compatible with his current motherboard. See my previous post.

You have to tell dsmove what you're moving. dsmove "cn=disabled_account,ou=current_ou,dc=etc,dc=etc,dc=etc" -newparent "ou=Disabled Group,dc=etc,dc=etc,dc=etc"

2000 Server will work. Since you're running Windows 2000 Terminal Services the only reason to purchase TS CAL's would be if you have any Windows 9x or Windows NT 4.0 clients that need to connect. For Windows 2000 and Windows XP clients all you need to do is activate a terminal services license server (TSLS)...and since your TS Server will be on a domain the TSLS has to be done on a domain controller.http://www.microsoft.com/technet/prodtechn...c/tslicens.mspx Note that Server 2003 TS CAL licensing is different. If you move the terminal server to Server 2003 you'll have to run the TSLS on a 2003 box and you will be required to purchase TS CAL's for all clients.

Found this potential fix here.

Open Windows Explorer and go to %SYSTEMROOT%\inf. Now find a file called sysoc.inf. Open it with Notepad (double clicking should work). Find the following line: AccessOpt=ocgen.dll,OcEntry,optional.inf,HIDE,7 Remove HIDE so that it looks like this: AccessOpt=ocgen.dll,OcEntry,optional.inf,,7 Now save the file. This will make it show up in Add/Remove Programs | Add/Remove Windows Components under the Accessories and Utilities option. It won't actually uninstall the Accessibilty Options, it just disables them. It's always driven me nuts that you can't just uninstall them.

Did you try the suggestions I gave you before?

The 1.2GHz Celeron is a Tualatin core based CPU. The problem is that your motherboard doesn't/can't support Tualatin based PIII's or Celerons. Intel changed the power requirements and a few other things between the Coppermine and Tualatin based PIII's/Celerons. Looking at Chaintech's site this is almost certainly the case. The 6AIV2T version of the board added support for the Tualatin based Socket 370 CPUs. However, all is not lost. There's a company called PowerLeap. They make adapters that will let you use newer CPUs on older motherboards. The adapter you need is the PL-Neo/T. Don't pay attention to the price on that page...that's the price for the adapter with a 1.4GHz Celeron.

There's one thing that hasn't been mentioned yet. It's possible you damaged the CPU core when you put the new heatsink on.

The 945 series chipsets support 533MHz CPUs as well...and will provide for 64-bit if he decides to upgrade the CPU later. Personally, I'd be looking at the Asus P5PL2. It even supports the newer 65nm dual-core CPUs so it should have a pretty good life cycle.

If you give the STOP code like cluberti asked we can tell you exactly what the problem is. Also, have you tried "Last Known Good"?

You have to remove them from the top level directory. The "remove" option is greyed about because the directory is inheriting permissions from it's parent directory. Keep going up in the directory structure until you find the directory that isn't greyed out...this will be the top level for those permissions.

Socket 478 processors are becoming more difficult to find. I'd say drop the motherboard and replace it with a Socket 775 board. This'll give you more options when you decide to upgrade that Celeron.

I'll refer back to KiX again for this one... Select Case InGroup("group_name1") AddPrinterConnection("\\server\printer1") AddPrinterConnection("\\server\printer2") SetDefaultPrinter("\\server\printer1") Case InGroup("group_name2") AddPrinterConnection("\\server\printer1") AddPrinterConnection("\\server\printer2") SetDefaultPrinter("\\server\printer2") Case InGroup("group_name3") AddPrinterConnection("\\server\printer3") AddPrinterConnection("\\server\printer4") SetDefaultPrinter("\\server\printer3") Case InGroup("group_name4") AddPrinterConnection("\\server\printer3") AddPrinterConnection("\\server\printer4") SetDefaultPrinter("\\server\printer4") EndSelect As you can see, you can add multiple printer connections and then specify which one is the default printer.

See Knowledge Base Articles: http://support.microsoft.com/?kbid=184006 http://support.microsoft.com/?kbid=314463 You can format a FAT32 partition larger than 32GB with Windows 2000/XP, but you can not create a partition larger than 32GB with Windows 2000/XP. Also note that you can not format FAT32 partitions larger than 32GB during install.

They reason they're "Unknown" is because the user doesn't exist. The string of characters you see is what's called a SID...or Security Identifier. Each user account and user group has a unique SID. If you delete the account and recreate it with the same logon name, the SID will still have changed...this is why you'd get a new user profile in such a case. You can delete those without any problems because, as I said, those users don't exist anymore. It's left over NTFS permissions from your previous install.

You're dorking around with directory and file security when doing it this way. Windows XP applies different security permissions when installed on FAT32 than it does when installed on NTFS. Installing straight to NTFS is much more secure. It also does not fix the security permissions when you run the convert. I've been doing NT based OS installs for years...from 3.51 on...and I've never, ever, had it do this. That really doesn't make any sense at all since the drive letters get assigned before you tell it what file system you want to use. You can't even format it until the partition has been created and a driver letter has been assigned.However, sometimes when you create a partition after it's already assigned the CD/DVD drive a letter it'll put the CD/DVD drive in the middle (Drive/Partition 1 will be C:, CD/DVD will be D: Drive/Partition 2 will be E:). But there's a simple workaround for that. Start install and create all of your partitions. When you notice that the drive letter is messed up, F3 out of the install and restart it. This will fix the drive letter ordering because the partitions where already created before Setup was started. Note that it usually only does this when you have to press F6 to install the drive controller drivers because it's already reserved C: for your primary drive but it can't see anything else so it just assigns the optical drive to D:. I've tried it, and it seems FAT32 is faster on almost any size of drive, but with larger drives the difference decreases. I timed the copying of 512Mb from memory onto a file on two identical 120Gb hard drives, one formatted with FAT32 and the other with NTFS. The difference between FAT32 and NTFS was approximately 1.5 seconds.1.5 seconds is well within the margin of error. File copies aren't an exact science. The same file may take 3 seconds longer the next time you copy it...or it may happen 5 seconds faster. Yes, it supposedly supports a 16 exabyte file on a 16 exabyte volume. Of course, this hasn't been proven since we aren't anywhere close to being able to create files or volumes of that size yet.