gosh

The obvious question is did you reinstall windows with the same version already installed? Ie OEM installed but used retail cd. Thatll screw activation -gosh

If you're having the issue on 2 different computers, then it could be a problem with: 1) Your router 2) Your ISP -gosh

You could install the device in XP and look at setupapi.log to see what .inf and driver it is using. Windows will copy the 3rd party inf's to windows\inf as OEMX.inf where X=next number available. Just open these inf's and they will usually say the name of the original inf. Then you could put these inf's into your server 2003 install and server 2003 should find the device and prompt you for drivers. -gosh

I just made remotenetwork.bad from the original CHM file from the windows XP OPK. But that is for the original version of windows PE, the newer version would be totally different. -gosh

http://blogs.dotnethell.it/vincent/IE-Team...-1.__12543.aspx We are targeting 1H08 to deliver IE8 beta 1, -gosh

setupdd.sys usually means bad ram SOOOOO maybe you should increase how much memory you are giving the VM. -gosh

XP Pro has schtasks.exe too. -gosh

In windows\inf, delete any PNF files, infcache.1, any oemX.inf files and reboot Delete setupapi.log, remove the device from devman and see what's being logged in setupapi.log -gosh

Just change HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList Or copy the old profile to the new profile. -gosh

right click inf\srchasst.inf and install it regsvr32 C:\WINDOWS\srchasst\srchui.dll Check HKCU\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer make sure you have FileFindBandHook, etc -gosh

powercfg /? -gosh

There should be something logged in event viewer. Is it sticking on the welcome screen? If so what does it say when it sticks? -gosh

you can go online only with safe mode w/ networking, and only if you have a LAN or cable connection. The PPPoE driver does not initialize in safe mode, and neither do modem drivers. -gosh

acpi is with the bios so im guessing you need a bios update -gosh

was this upgrade related to bink's site being down and neowin.net being hacked? -gosh

Since this was posted in the unattended forum you can modify the inf files to not install certain networking components. I dont remember what inf file installs netbios, but in general the inf's that start with net are related to networking. Netoc.inf lists most of the common networking inf's. -gosh

are you integrating any windows updates that use tcpip.sys? -gosh

control keymgr.dll -gosh

It could be a file mismatch with one of your runtimes. Download the C+ runtimes. http://www.microsoft.com/downloads/details...;displaylang=en -gosh

The program could be corrupted. You could try redownloading nlist and reinstalling it. Do you get this error with any other programs? -gosh

XP home is going to have Owner instead of Administrator. If the account is not on the welcome screen try ctrl+alt+del and type in the username. if that works then it's a registry key hiding it. Tweakui lets you hide the account. The registry key is under winlogon, specialaccounts. -gosh

That's very good. I always keep a copy of winfile because it handles permissions differently than windows explorer. Winfile was excluded from xp for this reason... -gosh

Infalways is the section in syssetup.inf that installs core os components such as movie maker. By default you cannot modify syssetup.inf but you can modify the other inf files such as sr.inf. You could "dummy" out sr.inf to not install system restore. However since i built that build environment i found out there is a hexed syssetup.dll out there that lets you modify syssetup.inf (nlite uses this). One plan i have is to move the stuff in infalways to sysoc.inf to make them optional components. The problem with removing stuff like system restore is, what if you want to use system restore post install? I think my next build environment will use a hexed syssetup.inf and a custom syssetup.inf (you can also rename syssetup.inf by hexing syssetup.dll) -gosh

That's just Active Desktop Right click on desktop > properties Desktop tab Customize Desktop Web Uncheck anything there -gosh

Did someone say Inf? Yes, you can. You're on the right track. First you need to know what PNP ID. You can get that by simply removing the device in devman and rescanning, it'll be listed in setupapi.log. Once you have it you can search your inf directory for "containing text" with the PNP ID. Then copy the .inf and the driver file mentioned to where you want to install. If you put it into the inf folder windows should auto detect the device. If it's not digitally signed, setupapi will copy the inf as oemX.inf (where X is the next available number) to your inf folder. I don't see why you would want to run anything from the command line though, plug and play will auto do everything for you. -gosh