Aaron

Some people in here IIRC have run a silent installation on the executable rather than installing via the INF method.

well done tris!

This is an open discussion to find answers, can't see why it needs to be closed? Anyway, rumours are about there will be a mini service pack, which is likely to be called sp1b, or perhaps a security rollup package to cover the 35MB of updates that's available on WindowsUpdate after SP1 is installed.

I'm building a PC next week, and the motherboard I'm getting has a SATA 150. I for one won't be using SATA yet, as SATA hard drives are currently expensive, and only offers a small speed improvement. I could get converters for my existing IDE Hard drives to work on SATA, but I'm not really bothered. Faster SATA upgrades will be available next year and the year after.

it should work during autoinstall if the catalyst drivers were installed via the OemPnPDriversPath

When I started this project, I used to use UnattendMode=ProvideDefault and found this to cause some other parts of winnt.sif to take no effect at all, such as [Components] and [Display]. Changing UnattendMode to FullUnattended fixed it

Welcome to MSFN Jason

The ATI Control Panel drivers will only have a successfull installation if the Catalyst 3.6 drivers were installed during GUI-mode Setup

in theory yes

I think ]Bonkers[ did one for ZoneAlarm last week. Found it: http://www.MSFN.org/board/index.php?act=ST...70&t=7681&st=10

It should be possible, people have installed applications using cmdlines.txt before, and all apps need to put info into the registry. Only thing I heard about is that you cannot put keys into HKEY_CURRENT_USER

Do you mean sr.inf? %SystemRoot%\System32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 path/to/sr.inf replace path/to/sr.inf with necessary path You should execute this from a batch file, save it as sr.cmd and place the path to sr.cmd from winnt.sif's GuiRunOnce

What about running the add users batch via cmdlines.txt? It will run at the end of GUI-mode setup before rebooting and logging in to run the unattended batch

Yes, you can disable a service after installing an app/driver that installed the service beforehand. If you applied your main regtweaks before the nvidia installation, then you can make a seperate registry file just for disabling the Nvidia helper service to run just after the nvidia drivers have been installed.

You can also use >> hotfixes.log to output all the info of the process, and any errors that occured. I.E. If you have a hotfixes.cmd run it with the >> %systemdrive%\hotfixes.log: hotfixes.cmd >> %systemdrive%\hotfixes.log This will create hotfixes.log in C:\ (or the drive windows is installed on)

Rock Music booo, long live Trance!

Because the Home version is made for Desktop Operating Systems only.

It's been a great 2 years, with the 2nd year being much better so we're going from strength to strength All the best for the next year to come! :punk:

Thanks for explaining, looks all clear to me now! Has anyone been able to prevent setup from logging into the default admin account, and force Setup to login with your own created username to run the batch in? I was thinking about running the autologin registry tweak from cmdlines, or deleting the default admin account via net commands but I'm not so sure about that.

Muting your Microphone in Volume Control happens sometimes, check to see if the Mute box is unchecked.

Download MSFN.ico (Save Target As...)

Try AutoPartition=1 and Repartition=Yes I'd suggest trying this on a test PC in the case of accidently overwriting the partitions on your primary PC There are also some more references to this in ref.chm (in your deployment tools), such as: FileSystem = ConvertNTFS or LeaveAlone Reading further, I checked AutoPartition again and found: AutoPartition Installs Windows to the first available partition that has adequate space for a Windows installation and does not already contain an installed version of Windows. It seems this will only take effect if Windows doesn't exist on C:\

If you're out of options, then you can use an app that will take a snapshot of your files and registry 'before' and 'After'. It then creates an exe making the necessary changes it found in the 'After' snapshot. Symantec's AI Snapshot can do this. There is also a freeware app called Auto-It, but I'm not sure if it does the above.

This thread is only for completed setup screens. Finding out and asking questions on how to create your own Windows XP Setup screen can be found in this thread. Please provide the file in a compressed cab format (WINNTBBU.DL_) complete with a seperate preview screenshot.

Sure, I'll make a sticky topic for completed setup screens