allen2

What kind of system you're trying to install on ?

Depency walker or listdll should help you.

http://www.sis.com/download/agreement.php?id=155792

Most of P2P software use a lot connexions a the same time and since SP2 XP has a limited number of thesse connexions. It can by modified by editing a reg key but i don't remember which one. Look on the MS website.

If there's already a firewall, you should disable the firewall on DC and fileserver as it may create problems if you don't allow people to connect on the services you set on the server.

If you 're going to use a gpo, you should be able to make what you without specifying the password in a plain text file. IE: when you're using startup script in the computer policy, the script will run with local system account so it will have all local rights.

Also sharing the root of drives isn't very secure and not recommended.

Why not simply disable the task manager with a gpo ?

Fast explanation: If you made your own .exe, you just need to modify the reg key HKEY_LOCAL_MACHINE\SYSTEM\Setup cmdline= to point to your .exe. Detailled explanations: This reg key has to be modified before burning your winpe cd. You'll need to start regedit the select HKEY_LOCAL_MACHINE, then do file load hive go to i386\system32 sub folder of your winpe folder, then select setupreg.hiv (this is the system hive for winPE). Put a name when asked like systemPE. Then got to HKEY_LOCAL_MACHINE\SYSTEMPE\Setup and edit the value cmdline to your liking. Finally select HKEY_LOCAL_MACHINE\SYSTEMPE and go to file unload hive. Then burn your CD like you usually do.

Fast explanation: If you made your own .exe, you just need to modify the reg key HKEY_LOCAL_MACHINE\SYSTEM\Setup cmdline= to point to your .exe. Detailled explanations: This reg key has to be modified before burning your winpe cd. You'll need to start regedit the select HKEY_LOCAL_MACHINE, then do file load hive go to i386\system32 sub folder of your winpe folder, then select setupreg.hiv (this is the system hive for winPE). Put a name when asked like systemPE. Then got to HKEY_LOCAL_MACHINE\SYSTEMPE\Setup and edit the value cmdline to your liking. Finally select HKEY_LOCAL_MACHINE\SYSTEMPE and go to file unload hive. Then burn your CD like you usually do.

Yes there is a very simple way if all your computers are in the same domain and reboot some times: Create a gpo with a startup script .cmd (computer, windows parameters,scripts): the script will be like this: net user administrator password Replace password with the password you want.

If he just need to access documents, you could just add a batch in his startup folder to map the domain2 if his computer is already member of domain1. The batch should like this: net use K: /d /Y net use K: \\domain2server\share /u:domain2\user2 password2 With user2 and password2 the login/password of the user in the domain2.

I'll add to Takeshi answer this : if you're using a windows 2000 to rescue another os, you'll simply need to launch regedt32, select the key HKEY_LOCAL_Machine, go to menu file load hive and then select your defective windows drive and go to winnt or windows then system32 then config and select the file system (for HLKM\system) or software ( for HKLM\software) then you'll be prompted to enter a name (entre whatever you want). Launch regedit and you'll see under HKLM\"whatever you wanted" the loaded registry. XP and 2K3 regedit will allow you to do this without the need of regedt32.

If you don't want to stick with vbs, you could try shutdown.exe (in the 2k resource kit and with XP/2K3) or psshutdown.exe (from sysinternals). All you need to do is a batch and use the task scheduler. The batch could be: for /f "delims=;" %%i in (listcomp.lst) do (psshutdown \\%%i -u user -p password -r -f) and lisctomp.lst would be the list of the computername or ipadress (one per line). Note that the user and password are not needed if you use for the scheduled task a domain admin account and if the machine you want to reboot are all in the domain.

Most of the time the .inf file in the drivers contains the defaults speed setting. Changing it directly in the .inf should then allow to have the speed automatically set but be carefull modifying an .inf will more likely break the driver signin check and you'll need to allow the driver to install. Another way around is to read from the .inf the needed reg entry and to set it after driver install.

FAT32 is faster by design: no need to create entries for rights, audit when storing or reading data. When tweaked NTFS can be almost as fast.

You can also do it with the netsh.exe utility.

It's perhaps a problem with audio drivers. It can easily find out if it's processor overheating problem simply by looking at the temp right after the crash and in normal operations. To be sure it isn't ram related, he should just need to fill all the ram with programs and check if they crash.

Try to boot from the XP CD and go to the recovery console. There list the services and stop the spamkiller one if it exist. If this doesn't solve your problem, check files timestamp in C:\windows\system32\drivers, then compare with other spamkiller files and if you find some with the same date, you can try to rename them one after another and try to boot between each try. You can do the same with files in system32 but this is going to be long.

You can also use dsquery and other dstools if you're using windows 2003. I found a lot of bug in csvde when exporting a lot of data.

Check if there is enought space on the system hard drive. And and give us more informations: - did you checked the eventlogs ? - does the system boot in safe mode ? - did you do something just before the server began to do this ?

Of course but some programs require a page file.

You should first use something like gspot to be sure if it's really an avi. Gspot will identify any kind of avi. Then if it fails it may be a .mkv or .mov renamed.

Permission using local domain group cannot be set on a share on a member server. They can be used on any DC. If you're using trust relationship between domains, you'll see that you can only add users from other domain to a local domain group. So if you have only DCs, using global domain group is not needed.

From the log it seems you're trying to do windows update with firefox. I think this is the problem did you tried to update with IE6 ?