gosh

What you want is AltStartup -gosh

Reinstalling won't touch the winsock. One way you can fix that is to get a good winsock registry from another computer and import onto yours. -gosh

if you can't install either xp or 98 after formating you have a hardware issue. If you just get a black screen youre looking at 1) bios, 2) display 3) general hardware -gosh

Background Last January i decided to build a build environment for my custom xp installs. I was very happy with the results, but at the time I decided to not release it because the mentality has switched towards programs that automate installs for you. People don't seem to want to learn how to unattend xp; instead they just want to download a program that does everything for them. However, months have gone by and I've changed my mind. There is a lot of value in my build process so i've decided to finally share it for those who love learning. So what is a build environment? The way Microsoft builds a new build of windows is they have each team (the ie team, the shell team, etc) put the latest code they have on a network share. Then Microsoft runs a complicated batch file that auto generates files and adds comments to the right files, and digitally signs the files. All that is automated. What i did is basically replicate the same premise. I made a batch file that once run, builds a custom xp install as an ISO image file, and optionally burns it. The original batch file calls other batch files that auto compress files, auto removes files, auto copies everything over. Why would you want a build environment? One of the most frustrating things in unattended install is when you make a bunch of changes to your source files, then when you run a test you get a blue screen. Then the question becomes, "Which change caused the blue screen"? If you've made a lot of changes since your last test, this could take a long time to narrow down. With a build environment, you can selectively remove components of your build to make it easy to see where it's failing. Also, when i make unattended installs the last thing i do is copy over fresh source files from a cd to guarantee that no files are corrupt. There's nothing worse then spending 2 months making a custom install only to find out that after all that testing a file got corrupt or is missing. With a build environment, you can copy a fresh i386 folder without reapplying any customizations. Custom install choices My build environment auto creates a custom string file that specifies what windows components to remove. This file is created each time you run the build process. Look in the \Scripts directory. To use Download the zip file and edit the paths mentioned in BuildXP.bat. This build environment is for the original version of XP (or is it sp2?). You will need to copy the right versions of files for your version of XP. For reference Even if you don't plan on using my build environment for XP, i included excel files i used to remove XP components. You can incorporate these excel files into your own unattend installation. Download Go to http://www.freehomepages.com/gosh2/ and click on the zip file that's 1 meg -gosh

We need more info here. For both computers post the following: ip address subnet default gateway \\otherpcname - what error do you get? \\otherpc'sipaddress - what error do you get net view \\otherpcname - what error do you get net view \\otheripaddress - what error do you get? network stack: what protol is being used for file sharing? what client is being used? is file sharing enabled on both? are firewalls on either computer? is the windows firewall enabled on either computer ping othercomputername ping othercomputeripaddress -gosh

Ive never had that problem so must be a problem with nlite, post in the nlite forum. -gosh

Does the SP2 come with documentation such as an updated ref.chm? If you extract the sp3 it should be in one of the folders such as Docs. -gosh

https://www.microsoft.com/uk/windows/produc...rs/default.mspx -gosh

happy birthday bro -gosh

I just have A+ and MCP. Certs dont matter. Certs are written by microsoft PR to sell you microsoft products, not really to learn anything. -gosh

If you manually add these settings after the install does it work? If it does, then it means something during setup is resetting these values. You didn't say when during the install you apply these settings. You might need to apply them later during the install. -gosh

You can try modifying intl.inf which is what setup runs. I dont know if it works but you can try it: See setuplog.txt after setup to see what params unattend setup passes to intl.inf. Just search the log file on intl.inf -gosh

SP2 for XP comes with an updated ie6 i believe. You shouldnt need to update ie6 during unattend install, unless youre talking security update. -gosh

Well Mr programmer since this is a HKCU setting you could simply delete HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Toolbar Then stop explorer.exe in taskmgr and run explorer.exe to reload the shell. Or it sounds like a policy. Make sure you don't have any shell policies that could cause this. -gosh

I explained how windows xp sets root permissions in http://www.msfn.org/board/Locking_C_drive_...ll_t105820.html It might be possible to specify what sid you want, either by modifying the default security template used by setup, or by possibly editing the SAM (HKLM\Sam). It would take experimenting to figure this out. The problem with security settings is they are applied on the fly during setup, so if you modify a security setting in a template it might be overwritten later by another setting. Setup makes setup security.inf that it applies, but this file doesn't exist on the xp cd, setup creates it dynamically during setup. -gosh

Windows XP uses a special inf just for applying ntfs permissions to the root of the drive. rootsec.inf obviously you could modify this file to change the default permissions. HOWEVER, you should never do so. If you accidently screw up the root ntfs permissions, such as removing or denying the everyone group: 1 - The computer might not boot 2 - You can't change this back using recovery console since it doesn't have a command to modify ntfs permissions 3 - You can't reinstall windows because it won't be able to write to the root of the drive 4 - You can't do a parallel install because you can't write to the root of the drive Only solution would be a format. And yes, i've worked on 2 incidents where the customer stupidly did this and had to format. So my advice is don't do it! -gosh

How about the basics. Does it shutdown ok in safe mode? -gosh

Never touch the ntfs permissions on the root of the drive! You can seriously screw things up. If you can't install from the root you have other issues. Post the exact error you're getting. Make sure your logged in as admin, or right click on the exe and 'run file as'. And again, as i mentioned before - when a program gives you a permission error it could be related to registry permissions! Check the registry permissions on HKCU\software\diskeeper and HKLM\software\diskeeper. Something should be logged in event viewer and setupapi.log. -gosh

You can remove IE very easily by following methods documented by me and programs on this website. However, why would you? A lot of apps assume ie is installed, if it isn't some apps might not run. Windows without IE is like a car without seats. -gosh

You're talking about SID's. There are some sid's built in, but most users will have a unique sid. defltwk.inf has a list of all the built in sid's -gosh

Oh home edition won't have secpol.msc. Just manually enable file sharing. Everything the wizard does you can do manually. It's not worth spending a lot of time troubleshooting. -gosh

Searching GOOGLE i find http://support.microsoft.com/kb/324852 -gosh

make sure winpe.cab is in same folder as waik msi file -gosh

Sysprep should let you reseal the box so they get the OOBE to enter in there name, etc. -gosh

if i remember right, when xp was launched i was told to run the wizard you need a user right. I forget which, but open secpol.msc, and go user rights assignment, and make sure your user account has the right settings here. It's important that when you get a permission error, it could be caused by registry or file permissions. For example if a registry key just has system listed for permission, then you could get a weird error related to permissions. I'm not sure what registry keys or files this wizard uses. Possibly a reinstall of windows would reset the permissions. -gosh