ToBe

If you have the files in $oem$\$1\Install\muiinst, you should have this in cmdlines.txt: [Commands] "%systemroot%\Install\muiinst\muisetup.exe /i 0407 /d 0407 /r /s" But I am unsure if cmdlines.txt handles variables like that....

@jediscorpian: Here's a list of files from a TabletPC 2005 cmpnents directory. I see that you have a compressed tabletpc.ca_ , extract that to tabletpc.cab: expand tabletpc.ca_ tabletpc.cab As for the other files, compare yours to my list, and see if you can sort them out. list.txt

The install of TabletPC depends on the cd-key. You'll have to call Microsoft about a volume license key for TabletPC. When/if you get it, all you have to do is create a XP Pro volume license cd, with the cmpnents folder from TabletPC on it. You may also have to add the cd2 marker file, 'WIN51IP2', in the root of the cd. When you install with your XP Pro select key, Windows XP Pro gets installed, and if you use your TabletPC vlk, Windows TabletPC gets installed. All from the same media. See more here: http://www.microsoft.com/technet/prodtechn...y/sitpcdep.mspx

Yes, that works, but it doesn't install NeroVision Express or Nero Media Player, only Nero Burning Rom.

Sorry for the short and uninformative answer previously, but I was in a hurry... prathapml describes the differences for you. This winnt.sif installs Windows XP Pro or Home unattended, just stop asking for the cd-key, and then continues: ;SetupMgrTag [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" [Unattended] UnattendMode=DefaultHide OemSkipEula=Yes TargetPath=\WINDOWS OemPreinstall=YES UnattendSwitch="no" [GuiUnattended] AdminPassword=* EncryptedAdminPassword=NO OEMSkipRegional=1 TimeZone=110 OemSkipWelcome=1 [UserData] FullName="Standard User" OrgName="" ComputerName=STANDARD [Identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=Yes Change the timezone, userdata and JoinWorkgroup to what is right for you.

And the fresh copy is the right media? There is retail, volume or OEM media, and if your key is a retail key it won't work with volume or oem media, and the other way around. Just a thought. *EDIT* I see teleri already explained that, maybe I should read the whole topic before replying... *EDIT*

Glad you got it working, I edited my post so it says 'use makecab', if anyone else bumps in to the same problem. I most likely used jcarle's utilities, compression bin, when I cabbed my files, and it modifype's the files at the same time.... Didn't think of that.

Otherwise you will get an error message....

Yep, change this line: [Unattended] UnattendMode=FullUnattended to [Unattended] UnattendMode=DefaultHide and remove the whole line ProductKey=XXXX....

http://www.microsoft.com/technet/prodtechn...y/sitpcdep.mspx

Nice one!

This is one way of getting it to work... http://www.msfn.org/board/index.php?showto...10entry174396

Do you still have AutomaticUpdates=1 in winnt.sif? You must have that as well... That shoud be enough really, but the oobeinfo tweak is just to tell windows that you really don't want to see that page. You don't have any regtweaks that disables Automatic Updates? No autoupdate=off in the [Components] sections of winnt.sif?

Unpack your servicepack to a folder named svcpack in the same folder that you have the files folder of office 2003. Then go to the folder files\setup and add this after the [Product] section in the file setup.ini [ChainedInstall_1] TaskName=ServicePack 1 TaskType=exe Path=FILES\SVCPACK\OHotFix.exe example: [Product] ProductCode=XXX ProductName=Microsoft Office 2003 ProductVersion=XXX Recache=1 [ChainedInstall_1] TaskName=ServicePack 1 TaskType=exe Path=FILES\SVCPACK\OHotFix.exe [MST] ... This will install Servicepack1 after the install of Office... You MUST label the cd/dvd 'office2003patch', otherwise it won't work. But as the above post, it will take much longer to install.

Lol, it is impossible (for me anyway) to find anything about about the /O switch on symantec's website..

When I tried to install NIS 2004 silently, it didn't work with just REBOOT=ReallySuppress /qb, so I looked at the file with a hexeditor and found the /O swith. That made it silent, but I don't know what else it does....

http://www.msfn.org/board/index.php?showtopic=25495&hl=

I haven't found a dirid for %username%, but check gosh's page: Inf files explained Example: %10% is the dirid for the windows directory %16409% is the dirid for all users\desktop for example EDIT: %53% maybe the same as %username%, haven't tried it though?

It's in the deploy.cab of the win2k cd someone on this board told me, can't remember who... anyway's he/she is right.

Try this, it depends on what kind of hotfix it is: @echo off setlocal set PATHTOFIXES=\\w2kserver\Share\update\hotfix\W2KSwe\ %PATHTOFIXES%\KB823353.EXE /Q:A /R:N %PATHTOFIXES%\KB839645.EXE /Q /O /N /Z %PATHTOFIXES%\KB840315.EXE /Q /O /N /Z %PATHTOFIXES%\KB841872.EXE /Q /O /N /Z %PATHTOFIXES%\KB842526.EXE /Q /O /N /Z %PATHTOFIXES%\KB867801.EXE /Q:A /R:N %PATHTOFIXES%\KB870669.EXE /Q:A /R:N %PATHTOFIXES%\qchain.exe Check here for more info: http://unattended.msfn.org/xp/installhotfixes_old.htm Works for win2k as well.

It seems Q873374 is a critical hotfix on all Windows NT systems. I would suggest that you make your unattended cd without the regtweak, and install Q873374 to see that you are not affected by this, and then add the regtweak as the last thing before you rebuild your cd. That way you know everything is ok. I installed IE6.0sp1-KB833989-x86-ENU.exe via svcpack.inf on windows 2000, and WindowsServer2003-KB833987-x86-ENU.EXE on windows 2003, and Q873374 is still listed as a critical hotfix on windows update. When installed all it does is telling me that I am secure... Maybe you have a version of .net framework installed that is affected? This is a tricky one....

Same time 01:01 http://www.microsoft.com/technet/security/...n/ms04-028.mspx @DisabledTrucker It depends on what software you have installed. A clean install of WinXP SP2 is not affected, but Windows 2000 with IE6 is affected, Office 2003 without SP1 likewise, and so on... This "update" for winxp is simply a tool that tells you that you should get updates for the programs you have installed....

Confirmed.. Adding this to the registry fools WU to think that the "hotfix" 873374 is installed: HKLM,"Software\Microsoft\GdiDetectionTool","GDITool",0x00010001,0x1 I've attached a little exe that can be installed via svcpack.inf: [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600 [SetupData] CatalogSubDir="\i386\Hotfixes" [ProductCatalogsToInstall] [SetupHotfixesToRun] Q873374.exe /Q:A /R:N Q885626.exe /Q /O /N /Z qchain.exe What it does is executing this inf adding the regdata [Version] Signature="$Chicago$" [DefaultInstall] AddReg=AddDetectionReg [AddDetectionReg] HKLM,"Software\Microsoft\GdiDetectionTool","GDITool",0x00010001,0x1 If you have any program listed under the two sections of Affected Software/components here: http://www.microsoft.com/technet/security/...n/ms04-028.mspx You need to install that specific hotfix, but this works with a clean WinXP SP2 install. Q873374.exe

*oops* deleted.