allen2

rundll32.exe advpack.dll,LaunchINFSection infname.inf,DefaultInstall should do it. Replace infname.inf with the path and name of the .inf file.

Sc.exe should do it if it still in vista.

Does the rpc service is working ? If no the computer might be infected by some virus. Also try to reboot as it's a MS computer....

Do you manage your wireless network ? What is you wireless card ? Does the drivers of your wireless card need the sp2 ? If so perhaps finding an old version of the drivers would do.

Printmig should do the job. Anyway you can save the registry entries and the drivers needed and copy them to each computer. Something like regshot would do the job to find difference in the registry.

You should need to configure the firewall at least for the dns.

Did you also checked if each of your users own his own profile(all the files) ?

I don't think you'll find one at least from the open source version because it has to be compiled with mingw which actually is only 32bits and apparently won't be 64 bits soon. You might find one in SFU (Microsoft windows services for unix) if there's a 64 bits version of SFU.

Link agregation and teaming with fail on fault allready exist with many network cards. I don't think two network card will be usefull for most people.

You should do a netstat -ano if you're using XP after closing all applications but letting open dialup. -"n" will remove the resolution and give real port -"o" will give you the process number which open the connection on your computer. It's easier to close a port or a connection if you know which process opened it. Also "a" will give you all connection even the listening ones which might not interest. if you closed all your applications, netstat -ano should only show listening connections. If you're using a windows 2000, do a netstat -an after closing all applications and you still have some established connections, you'll need something like sysinternals tcpview. Of course you can directly try it even on an XP Computer.

If users with roaming profiles loose their wallpaper, it means they don't have the rights to modify their roaming profile or they don't own the files in the roaming profile. For the other problem, if the users are members or the local admin group of their computer, the should be admin of this computer. In AD there are two admin groups entreprise admins and domain admins, the one which has the most of rights is the entreprise admins group. Anyway roaming profiles are allways a bad idea.

There's a simple work around. Restore the image within vmware with somethin like Live state recovery desktop which can restore a ghost image to different hardware or virtual machine.

His computer should have got recovery CDs and licenses numbers for office 2000.

First try to identify if you card is really a sb live 5.1: here. Then choose the right driver.

The problem perhaps come from the boot.ini. Check in recovery console what map gives you for the windows partition and see if it's the same in the boot.ini.

Some motherboard have an antivirus protection which can protect the MBR. If you activate it you will be prompted when a program want to write the MBR. I don't know if this will help.

Also getting native 64bits drivers for win XP64 is usually tricky. Some hardware doesn't have 64 bits support (yet).

Jt.exe should do the job but i didn't get to disable a job but the help say it can. It can be downloaded from here. You could delete and recreate the task with a vbs.

To put pagefile.sys to another drive, i simply modify the path for the pagefile.sys in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management PagingFiles=d:\pagefile.sys

I don't know why but if you can ping the gateway from your friend computer then try to ping your computer from your friend's computer and ping his computer from yours. Did you check if your firewall was enabled ? Also check if you and your friend ips/subnets are similars.

On the task tab you should have to uncheck active if you want to disable it.

In a dos box,do a ipconfig. You should get the default gateway address. Then try to ping the default gateway address. If you can ping it, then it's either a firewall problem or another software pb. If you can't ping it, perhaps your network card doesn't get an ip from dhcp or simply doesn't work at all.

You might want to look at Cdshell or syslinux. Also a faq for bcdw 2.0 is here, it'll perhaps help you.

Botten anna There's also a video.

To authentificate to a share you'll still need to have the computer netbios name at at least here: net use * \\computer_dns_name\share /u:computer_netbios_name\user