gosh

Do a regular install, and at the 1 min mark where it says "please take out any floppy disks and press OK to restart setup", open regedit and export this key: HKEY_LOCAL_MACHINE\system\Setup Then in your runonceex import the registry key, and it'll run oobe on next reboot If you want to be nice post the .reg file you make so i can add it to my records. -gosh

I've always used this code and it's always worked for me. I have the code run last, and anything that takes a long time to install such as nero i put at the top of the list. HKLM,"%RunOnceEx%\ZZcleanup",2,,"%11%\cmd.exe /c rd /S /Q %10%\Apps" -gosh

I would think winbom.ini would let you do that. Or there should be an inf to do that. If you install winpe locally then you'll be using the recovery console directory. I know you can change the keyboard layout in recovery console. Recovery console actually loads as a keyboard driver.... -gosh

http://news.independent.co.uk/uk/this_brit...sp?story=508517 -gosh

nice job gtaylor. -gosh

well according to http://support.microsoft.com/?kbid=271135 it sounds like the dll is missing for {011BE22D-E453-11D1-945A-00C04FB984F9}. In regedit i see the file is wsecedit.dll. If i understand this right, make sure the file exists and extract a new copy. SFC /scannow. Worst comes to worst just reinstall windows. Or try google. -gosh

Why would you need devcon? Setup uses SetupAPI which logs to setupapi.log, this should be enough information to go from. If you have NIC drivers that use an inf and 5 files, put the 6 files in the i386 folder. Edit dosnet.inf and add the 6 files: d1,file1.ext d1,file2.ext in txtsetup.sif add: filexxx.inf = 1,,,,,,,20,0,0 driver1.sys = 1,,,,,,,4,0,0 driver2.sys = 1,,,,,,,4,0,0 etc I would think that would do it. When setup does PNP enumeration it should find the inf, and the inf should copy everything correctly. I do things the hard way. If you want the easy way use the OemPnPDriversPath unattend switch. Search the forums for examples of how to do that. -gosh

How about troubleshooting? Copying all the system32 dll's isn't really a good way to troubleshoot a problem. Boot into safe mode. If that works, use sigverif to isolate the faulty driver. Search support.microsoft.com on the blue screen error to see the common causes. Use xp's msconfig to do a clean boot. Basically, do the basics. And you didn't say if all 100 pc's are using the SAME image. Usually when erratic problems happen, people are using different images. Make sure all the computers are using just one image. Troubleshooting isn't finding a reghack or file to fix a problem. Troubleshooting involves isolating the problem, and attacking the problem in a linear fashion. Looking for a quick fix or reghack isn't troubleshooting. -gosh

All a hardware profile is is a copy of the current control set, which is only used for drivers. To use different software and desktop appearance you want another user profile. -gosh

yes, that info maxxpsoft quoted is for registry keys for the control panel cpl's, it's not related to sysoc.inf. -gosh

I'm a little unclear what you want me to change that to. But either way, my site is done and im pretty much done so im trying to avoiding changing things unless there's a very good reason to do so. But not just you, i've had people PM me asking me to change stuff, and i've told them the same thing - im done with the site and pretty much done posting new stuff here. -gosh

I worship the all holy god of saintly heaven, GOSH for short. PM me for details. -gosh

a lot of misinformation. First, you don't have to use messenger at all. RA is installed by sessmgr.exe, it creates the RA account. To use RA you can use any version of messenger, outlook express, or your friend can copy and paste the invitation to you. Disable the stupid windows firewall. If you suspect a software firewall is causing the problem, simply boot both computers into safe mode w/ networking, no firewalls will run in that environment, and you'll still have network access. Next, verify basic connectivity. Get your friends ip address and ping him. If that fails, do a trace route. Now remember that it has to have the right ip address. If your friend reboots or signs off dialup, you'll need to get a new invitation. To make sure you have the right ip open the invitation in notepad. And of course verify the HelpAssistant account isn't disabled or removed. http://www.wown.com/j_helmig/wxprmass.htm -gosh

use my services.inf to reset the default services. If you don't know what you're doing, don't fu** with your computer. -gosh

Update your video card drivers, and lower the hardware exceleration (using dxdiag.exe > video tab). If the hardware exceleration fixes the issue, it could be a driver issue or general hardware failure. If you have another partition, do a clean install of windows on it, to rule out bad hardware. Under system properties uncheck 'auto restart' on blue screen. Since youre getting a blue screen, something running in kernel mode is causing the problem (could be user mode but doubtful). That leads us to drivers. An old incompatible driver could be the problem. Boot into safe mode, and try to play the game there. If that works, it's either a bad video card driver, or 3rd party driver. If it's not the video card driver, use sigverif.exe to isolate unsigned drivers. Search support.microsoft.com for information on how to do this. -gosh

Computers won't kill you, cell phones will. They cause cancer and brain tumors, that's why i never use a cell phone or cordless phone. You all laugh at me now but see who's still alive 20 years from now. -gosh

All that does is disable you from changing the homepage from inetcpl.cpl. You could still use regedit or an .inf to change the registry key for homepage. -gosh

CD burning is installed via cdrom.inf. If you wanted to, you could manually edit the file to remove cd burning support, but that would be a big waste of time. There are reghacks as mentioned above that can be used to disable cd burning. -gosh

Welcome -gosh

Just add the w9xupg folder or whatever it's called to the cd. Or install win9x, then use my reduce source and add it to the cd. In your answer file you'll want 9xupgrade=yes i believe is the correct switch, should work. Just remember you probably won't want to use oempreinstall=yes and 9xupgrade=yes in the same answer file. -gosh

ya, like aaron said. Using winimage you can make a 2.88 meg image, then you can add files to it. Partition magic 8 should only be about 2 megs. -gosh

Do you really need to put your name all over the screenshots? LH4053 had .net framework in a .cab file, i assume you just edited an inf file to install it, right? That's useful you found a way to include .net framework in winpe, but it's not that big of a deal, and you didn't provide any way for anybody to verify you did it so the screenshots are worthless. -gosh

delete ntoskrnl.exe from driver.cab and/or sp1.cab -gosh

You're not modifying driver signing by a reghack right? XP won't allow reghacks to do that, you need to use driversigningpolicy=ignore in your answer file. Here's what you do. Delete setupapi.log. Go into device manager, rip out the monitor, and refresh. Go back to setupapi.log and see what inf it's using. If you wanted to you could modify the inf, to change the display name or anything else you want. It's possible a newer driver on the manufactors website might fix this issue. -gosh

Have you tried asking your question in the opera forums, or asking opera if they have a way to silently register the app? If you bought the app they should provide you with at least email/chat support. -gosh