tguy

Cool. Thanks. I'll have to play with this.

You could map a drive to the other PC using the 'Connect using a different user name' option.

Check here.

Might check this article: http://www.windowsitpro.com/Articles/Print...ArticleID=22357

Check this link: http://www.winternals.com/products/repaira...002.asp?pid=erd

That would violate your EULA for WIN2K. Not a topic to discuss here. For more than 10 connections MARSDEN is right, you need to buy a server.

If you are running Active Directory you can use GPO's to stop this behavior.

See this link for Security and these for performance: http://www.microsoft.com/technet/prodtechn...e/perftune.mspx http://rdweb.cns.vt.edu/public/notes/win2k-tcpip.htm http://www.serverworldmagazine.com/monthly...inetuning.shtml These should do for a start.

Most machines that USB support will allow you to turn off USB ports in the BIOS. You could try their first. Otherwise, Group Policies or software like the XP_SecurityConsole might do what you want.

Sounds like some kind of group policy is set to not save changes to the desktop environment. That, or possibly something like Autoarrange is turned on.

I believe it is the number of connections attempted to any XP SP2 workstation at a given time. This is not really new, I believe Win2K Pro had the same limitation. Hope this helps.

$Docs $Progs are not supported in a WIN2K setup.

Windows Update all the way, I would want a fully patched server before I make it a domain controller so a minimal number of vulnerabilities are exposed.

Microsoft Windows 2000 and 2003 Administrator's Companion. Windows XP Inside Out Three good books I keep in my library.

If you still get stuck, append this to your command line: /L*v\"%temp%\pcsinst.log\" It will create a log file in verbose mode called pcinst.log in your temp directory. You can open up the log and review for errors.

McAfee 8.0i is what we use internally.

Might want to also run the usual gammut of spyware apps. Spybot, Ad-Aware, MS Anti-Spyware Run a virus scan as well.

If you name the second drive say D: you can create a folder called D under the $OEM$ folder ($OEM$\D) and put the files in there that you want to copy or install and it will work. You can nest folders under D as well. Good luck.

Try adding this line to your Components section: [Componants] AutoUpdate=off

You could also use vbScripting to do it like below: Set fso = CreateObject("Scripting.FileSystemObject") Set drv = fso.Drives.Item("c") drv.VolumeName = "SERVER_SYS"

Here is a link that uses Microsoft's shell scripting objects to create shortcuts. It's nice because it has predefined classes for things like: All Users\Desktop etc. http://cwashington.netreach.net/depo/view....tType=component

It is basically the same as the other versions of Windows except: Limited to 2 GB RAM Limited to 2 Processors Cannot act as a 2000 or 2003 domain controller Does not provide other common services to install etc.... Here are some links: http://www.microsoft.com/windowsserver2003...reeditions.mspx http://www.microsoft.com/windowsserver2003...ticleindex.mspx

You could also try Ranish Partition Manager. I think version 2.44 is about the latest. Search the web, you will find it. I have used it in the past, it works well. However, Microsoft's diskpart.exe utility does work well and is very flexible.

Look into .udf files that can be used with unattend files to do what you want.

I'm having a little trouble understanding exactly what you are asking but from the sounds of it, you want to know where to put a batch file that will launch setup????? You can launch setup from a batch file from a network share, or from a DOS based shell environment from say a DOS 6.22 floppy disk or formatted partition. Why would you need two unattend files? If you need a second command file that will install other applications you can use any number of methods discussed on this forum. Use the search feature to locate your answer and examples of how-to accomplish the task. As for the WINNT.SIF file, it will handle the entire installation and can call external scripts and programs to complete the installation. To have it execute during installation put the file on a floppy or copy it into the i386 directory.