gosh

yes, since cmdlines is in the $OEM$ folder you should use oempreinstall=yes, although sometimes cmdlines will run even without that line. -gosh

just because microsoft says they don't support it doesn't mean you can't do it. Bob Qin, hmm, that sounds chinesse. Email support is handled in china, so you probably got someone in china that copied and pasted his reply to you. I say don't waste the time trying to integrate ie. Just use iexpress to make an .exe and run it using GuiRunOnce or a similiar method. -gosh

make a boot disk with cdrom support then make a flat (copy the files to the hard drive), run smartdrv, then run winnt.exe and go from there. ms article 311755 i think shows the steps to make a flat. -gosh

I just make a cd from scratch to ensure no files are corrupted. The more programs you use the more variables you have which will result in a higher chance of something going wrong. -gosh

Anyone know what this does? On windows xp home edition sp2 it's included in sysoc.inf. It's only in home, not pro. It first appeared in sp2 beta build 2111 i believe. However in non of the beta builds does it include startoc.cab, which includes all the files. What's the point of startoc.inf if no one can use it? Is this a new version of windows, Windows XP Starter Edition? ; This is the Setup information file to install Starter Edition components ; Copyright © 2004 Microsoft Corporation -gosh

I've had that many times. Usually it's caused by xp hanging on a service, such as BITS or UPNP, or a service you disabled in MSCONFIG. Just wait a minute then you'll notice all the services will start. Either ignore it or use msconfig to narrow down the offending service. -gosh

Go look for yourself http://www.microsoft.com/technet/prodtechn...sp2preview.mspx -gosh

I could add an insult but alan already beat me to it. -gosh

The method described should work fine, although i think OemPnPDriversPath should be removed. The only reason you would need OemPnPDriversPath is to avoid duplicate files. What i would suggest is once your make your mydriver.cab, remove any duplicate files from driver.cab or sp1.cab. Also, i would think you would want any .inf's copied to the inf folder (11) during install so setup can see them. I don't think setup would extract an inf to install drivers. See what happens is at the 32 min mark of setup, setup does the PNP detection and enumeration. Setup also installs the infs from syssetup under [DeviceInfsToInstall]. Once setup finds some hardware, it tries to find the right inf in the windows\inf folder. I would think the inf would need to be there rather than in the .cab file. Once setup finds the right inf it reads it and extracts the needed files from the .cab you made. As far as the 1 and 100, 1=original media, 100=updated file (service pack). With slipstreamed media this shouldn't matter whether you use a 1 or 100. -gosh

Don't use beta products, they might have bugs -gosh

Did you get any errors when u ran that command? Typically the installshield file will be setup.exe. Setup.exe might be compressed in that .exe file you mentioned. What i would do is try to extract that .exe file you mentioned, and look for a setup.exe. You might find setup.exe by running the .exe file, then going to %tmp% and looking for it. Then run setup.exe -r, and go through the prompts and you should get the .iss file. If you would provide a download link i could download the file you mentioned and try to get it working for you. -gosh

You shouldn't modify the msgina.dll because like you said anything can change it. What you should do is name your custom msgina.dll to whatever.dll and add whatever.dll to GinaDLL registry key. -gosh

That's a bug in XP that will never be fixed because it's such a low priority. Even if you clear all the MRU's you still still see addresses in the address bar by clicking on it and clicking the down arrow. The only way i know to disable this is to uncheck the Web addresses box in autocomplete. -gosh

There's microsoft articles on that error. Simply extract the file mentioned in the error. I should warn you guys however, that 90% of the time ths error is caused by faulty hardware such as bad ram, etc. So keep that in mind, don't spend too much time troubleshooting a possible hardware issue. -gosh

My website has detailed info on how to add custom wallpaper to your install. -gosh

Profileitems only makes start menu shortcuts. -gosh

erd commander is just winpe with a different shell. You could try the standard ways of running batch files in winpe. Check winternals website, they might have an article showing you how to do tihs. Since erd commander uses a documents and settings folder, maybe you could add stuff to a startup folder? -gosh

You could use your product key during setup, then at the end of setup in GuiRUnOnce or RunOnceEx you could run sysprep -mini i believe is the switch, to prompt the user for information such as name. One of the sysprep switches will clear the product key and prompt you for it again, i think it's sysprep - reseal? I'm not a sysprep expert but that might work for you. -gosh

A new service pack WILL overwrite those files. ANytime you make an unattended cd you should always document what you have done step_by_step so you can do the same steps later if you have to. -gosh

A lot of the stuff you said isn't relevent, such as the computer name conflict. I would first try system restore. Then i would try safe mode w/ networking. Sometimes just booting into safe mode will fix an issue. Next i would use taskmgr to see what process is using all the cpu uage. It sounds like you might have a virus or something that wants to use the inet. You could also try updating the NIC drivers, try another user profile (user account), run sfc /scannow (not in safe mode), uninstall any firewalls/antivirus/things like that, check event viewer for any errors. -gosh

Check the properties of the printer on the print server, there should be a way to log to a file, and it should say the log file there. Otherwise search microsoft's site to see exactly how to enable logging. I think by default it only logs to event viewer. -gosh

I've seen that with zip disks when xp assigns a zip disk drive C. Check event viewer for any errors, and search google on the errors. You might need to reinstall windows. Is your new hard drive drive c? Is your 2nd hard drive formated? -gosh

Yes, it's either the cd idents or something is wrong with your txtsetup.sif. -gosh

It's iexplore, not iexplorer ;/ -gosh

I doubt the trojan has hooked into the welcome screen because it only runs under the system context. The welcome screen is only a resource file - logonui.exe, the actual logon is processed by winlogon.exe. Someone could have used a 3rd party gina, however. Look at the GinaDLL registry key, if you find it delete it. If you suspect your system has been compromised i recommend backing up all the data and formating. And make sure you do whatever you do with your network cable UNPLUGGED if you have broadband. While online the hackers can see what you are doing and possibly cause more damage. **** hackers. -gosh