 [How To] Multi-boot DVD Guide, Updated and with cool features |
  May 21 2006, 12:48 PM Post
#1 | |
| André Guimarães Casal  Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771   | Hi all! There is currently an open pool on if I should update this guide with the latest methods or leave it as it is. I would like your feedback  This is (probably) the most complete and updated guide on how to build a Multi Boot DVD. I'll be updating it as i can. Hope you like it changelog Aug, 18 (2009)
Aug, 20 (2007)
- Automatically create multi-boot folders and files - Install all your software directly from your CD/DVD (so it won't be copied to the HD, saving time) - You'll have just one Install.cmd file to update/maintain all your software - Determine which software gets installed in which OS - Still be able to use the OEMPreInstall=Yes and [GuiRunOnce] in winnt.sif to launch some other stuff that you may need - You can slipstream drivers to every OS you want, having only one copy (BTS's DrivePacks integration being researched) - You'll still be able to use any post-install methods you like (RunOnceEx, kTool, WPI, WIHU, XPlode, etc) This guide is compatible with the following methods and tools: - nLite - RyanVM - HFSLIT - BTS's DriverPacks (Method 2 is recomended so you can have only one copy of the drivers and slipstream them to all the OS's.) - Windows Post-Install Wizard (WPI) - kTool - WIHU - XPlode This guide is compatible with the following OS's: - Windows Server 2003 (Standard, Enterprise, Web & Data Center) - Windows XP SP1 - Windows XP SP2 - Windows XP Home - Windows XP Media Center - Windows 2000 - Windows 98 Before we start: Keep it simple, for boot menu use CD Shell, use simple winnt.sif files, etc. You should beautify, only after you'd successfully completed and booted from all OSs. Some beautifying options are at the end of this guide. What you will need: - Time and patience, don't expect to get everything to work the first time - Various operating system CDs or ISOs - Sufficient drive space (5+ GB to be safe) (I used +/- 20GB for my DVD) - CDImage (GUI'ed version) - Seems the link is not working, search google instead - CD Shell - Hex Workshop to hex-edit files. - Optional - VMware (Shareware), Virtual PC (Freeware) or Qemu (Freeware) (for testing purposes) - Any ISO burning software, like CDBurner XP (Freeware) Work on one operating system at a time. Test once you have that operating system added to make sure everything works right, then move onto the next OS. It will save you time if something goes wrong and you'll know where to look. You can only test your DVD once you've passed the "Creating the ISO" section. Good luck! Let's get started: Let's set up our folder structure: - In your C:\ (or the root of your OS drive) create this folder structure: ------------------------------------ DVD\BOOT\ DVD\SETUP\ ------------------------------------ DVD is the root folder and SETUP will store all of the CDs (DVD\SETUP\XP\Professional for example) - Extract the CD Shell.zip file and move the BOOT folder into the DVD folder (DVD\BOOT\) - Move the TOOLS folder into the BOOT folder (DVD\BOOT\TOOLS\) - Copy all the contents of the XP Pro CD to DVD\SETUP\XP\Professional. Automatically create multi-boot folders and files (thanks to geitonaki) - Download geitonaki's SFX file - Execute it and browse to your DVD folder. When finished it will open create_boot_folders.cmd, modify it to your needs. - It will create the PRO1 boot folder, modify setupldr.bin, modify txtsetup.sif, create the PRO1.bin boot sector and copy the WIN51, WIN51IP and WIN51IP.SP1 (WIN51IP.SP2 if Service Pack 2) tag files. (Notice that PRO1.bin has to have exactly 4 letters UPCASE) CODE call create_boot_folder.cmd C:\DVD\SETUP\XP\Professional C:\DVD PRO1 FOO 0 - Create a text file, inside PRO1, with NotePad, and rename it to winnt.sif. This will make winnt.sif create a tag file that identifies the OS being installed. In this case, the tag file will be XPPRO.TAG, but you can specify whatever you want: QUOTE [GuiUnattended]DetachedProgram="%SystemRoot%\System32\cmd.exe /c @ECHO something>%SystemDrive%\XPPRO.TAG" Creating RunOnce.cmd - Create a RunOnce.cmd file inside DVD\SETUP\XP\Professional\i386\CMD\ and paste the code in. - RunOnce.cmd looks for Install.cmd on the DVD and calls it. QUOTE @echo off You can use the RunOnceEx method for this. RunOnceEx only runs at first logon, so applications may need reboot. The method above goes around that, it's "rebootless"!for %%i in (c d e f g h i j k l m n o p q r s t u v w x y z) do if exist "%%i:\software\Install.cmd" call %%i:\software\Install.cmd exit Launching RunOnce.cmd from Svcpack.inf - Add these lines to svcpack.inf inside DVD\SETUP\XP\Professional\i386\: QUOTE [SetupData]CatalogSubDir="\i386" Notes:[SetupHotfixesToRun] CMD\RunOnce.cmd - Svcpack.inf may come as svcpack.in_, just use the eXPander utility (thread here) to extract the svcpack.inf inside it, then delete the svcpack.in_. - As you can see Svcpack.inf will launch RunOnce.cmd at T-13 stage. - You'll have to addapt the [ProductCatalogsToInstall] in svcpack.inf according to the new CatalogSubDir="\i386" because it may point to a different location (in which case you'll get an error message during installation). If you don't have any file references under [ProductCatalogsToInstall], then just don't worry about it. - Use the eXPander utility to transform svcpack.inf back to it's compressed svcpack.in_ form, which is smaller (this is optional). Creating the Install.cmd file - Create a Install.cmd file inside DVD\SOFTWARE\ and paste in the following: QUOTE @echo off REM next line makes sure the *.TAG extension is identified setlocal enableextensions REM checks for the XPPRO.tag file and go to the corresponding section: if exist %SystemDrive%\XPPRO.TAG call :XPPRO REM checks for the XPPRO2.tag and go to the corresponding section: if exist %SystemDrive%\XPPRO2.TAG call :XPPRO2 REM checks for the SERVER2003.tag file and go to the corresponding section: [if exist %SystemDrive%\SERVER2003.TAG call :SERVER2003 REM End goto :end :XPPRO REM Here we'll add the software to install to the XP Pro version. Example: REM "%~dp0" refers to the full path the Install.cmd is in, so you don't have to worry about drive letters start /wait %~dp0\Software\Program1.exe /s start /wait %~dp0\Software\Program2.exe start /wait %~dp0\Software\Program3.exe /qn REM End this section REM end of this section : goto :end :XPPRO2 REM Here we'll add the software to install to the XP Pro Unattended version. Example: [color=#333399]start /wait %~dp0\Software\Program1.exe /s start /wait %~dp0\Software\Program2.exe start /wait %~dp0\Software\Program3.exe /qn REG IMPORT %~dp0\Software\Tweaks.reg REM End this section REM end of this section : goto :end :SERVER2003 REM Here we'll add the software to install to the Server 2003 version. Example: REG IMPORT %~dp0\Software\Workstation.reg start /wait %~dp0\Software\ProgramA.exe /s start /wait %~dp0\Software\ProgramB.exe REM End this section REM end of this section : goto :end :end REM Here we'll add the options for every OS. start /wait %~dp0\SOFTWARE_ALL\AntiVirus.exe start /wait %~dp0\SOFTWARE_ALL\Firewall.exe /s REM Applying tweaks to the registry. Independent of the TAG: REG IMPORT %~dp0\Software\Tweaks.reg del /f /q %SystemDrive%\*.TAG del /q /f %SystemRoot%\*.bmp del /q /f %SystemRoot%\system32\dllcache\*.scr del /q /f %SystemRoot%\system32\setupold.exe del /q /f %SystemRoot%\system32\presetup.cmd exit Install.cmd checks for any tag file and when it finds performs the associated task. As you can see, aplications are installed directly from the DVD (not copied to the HD) thus not needing the OEMPreInstall=Yes or [GuiRunOnce] in winnt.sif, that you can still use to launch some more stuff that you may need, and saving time  Finishing Up DVD Layout: Ok, now check if your DVD layout is similar to this, if it is, everything is ok. Keep in mind that this is just a sample layout. This layout includes XP Pro and Server 2003, but you may add as many as you like (or as many as it fit's on DVD). C:\DVD\ - Multi boot DVD Source C:\DVD\BOOT\ - CDShell folder C:\DVD\i386\ - Windows XP Pro reduced source folder (OPTIONAL) C:\DVD\PRO1\ - Boot folder 1 for XP Pro C:\DVD\PRO2\ - Boot folder 2 for XP Pro C:\DVD\3ST1\ - Boot folder 1 for Server 2003 C:\DVD\3ST2\ - Boot folder 2 for Server 2003 C:\DVD\SOFTWARE\SOFTWARE\ - Folder where software is placed C:\DVD\SOFTWARE\Install.cmd - CMD file that takes care of the software installation C:\DVD\SOFTWARE\SOFTWARE_ALL\ - Folder where software for all OSs is placed C:\DVD\SETUP\XP\Professional\i386\CMD\RunOnce.cmd C:\DVD\SETUP\Server2003\Standard\I386\CMD\RunOnce.cmd Creating a boot menu (CDShell): It's time to create a boot menu. CD Shell scripting it very simple and I believe that if you read my example you'll find it very easy to modify to your needs. Creating the ISO (CDImage): Now we only need to create the ISO so we can test our DVD. I'll follow the non-GUI CDImage tutorial, but you can use the GUI'ed CDImage version if you like. Put the cdimage.exe in the same directory as the DVD: ------------------------------------- C:\CDImage.exe C:\DVD ------------------------------------- And automate the process: Make a batch file that you can run whenever you want to make the ISO. To create a batch file open Notepad and paste the below code into it. Save the file as whatever you want and then just change the extension to .bat, like C:\makeiso.bat. QUOTE DEL C:\*.ISO Ok, time to test your ISO with VMware (for example) and add another OS!start cdimage.exe -lDVD -t01/01/2006,12:00:00 -b\DVD\BOOT\loader.bin -h -n -o -m \DVD C:\AIODVD.iso EXIT Extras Add an Unattended option: This section will teach you how to add an option which let's you install Windows unattendedly. - Copy the PRO1 folder and PRO1.DAT file to "Copy of PRO1" and "Copy of PRO1.DAT" - Rename it to PRO2 and PRO2.DAT - Hex-edit PRO2.dat and scroll down until you see "PRO1" in the right hand side. Replace PRO1 with PRO2. - Hex-edit setupldr.bin inside the PRO1 folder and Ctrl+H, then search for Type: "Text String" "PRO1" and replace it with PRO2. - Save the file, choose not to back it up. - Click "OK" and then choose "Replace All". It should say "4 Occurrences Replaced". When done, save the file and choose not to back it up. - Edit winnt.sif to include the unattended options. This may be a good time to read the ref.chm file in Microsoft Deployment Tools, it explains how to set up winnt.sif for an unattended installation. You can use your winnt.sif file to skip some boorings steps of your installation like typing the serial number, defining your language and keyboard or even skip all the steps with the UnattendMode=FullUnattended command. After you created your winnt.sif add these lines to it, so it TAG's the OS being installed: QUOTE [GuiUnattended]DetachedProgram="%SystemRoot%\System32\cmd.exe /c @ECHO something>%SystemDrive%\XPPRO.TAG" - Ok, so now we have a second boot option. Its time to add that option to the boot menu, so you can actually choose it. Just open up your DVD\BOOT\cdshell.ini and add these lines to it:QUOTE XP_Pro: print c "\n\cXXMicrosoft Windows XP Professional \n" print "1) Regular \n" print "2) Unattended \n" XP_Pro_Key: if $lastKey == key[1]; then chain /PRO1.DAT if $lastKey == key[2]; then chain /PRO2.DAT Add Windows 98 Follow this guide, by chon_. Add Drivers: Follow this guide, by a06lp. Additional Resources - Setup Billboard Screens (or learn how to make your own here). - Microsoft Deployment Tools at Microsoft and Rapidshare. They contain the ref.chm file that has info for WINNT.SIF configuration, along with other utilities. Explanation of how it all works: Understanding The Boot Process - CD Shell lets you choose which XXXX.DAT boot sector to access (located on the DVD root) - The boot sector (PRO1.DAT for example) says where to load the SETUPLDR.BIN file (located in each of the boot folders) - SETUPLDR.BIN has instructions on where to access txtsetup.sif (on the same folder) which accesses the appropriate DVD\SETUP\XX folder and starts the text-mode setup for Windows Timeline T-39 - Depending on the boot folder, winnt.sif's DetachedProgram creates a tag file identifying the OS. T-13 - Svcpack.inf launches the RunOnce.cmd inside ...\i386\CMD\ of every OS. Install.cmd checks for the tag file and then performs that TAG's associated task. And that's it, i'll be updating as i can  Hope it was usefull to you This post has been edited by andregcasal: Sep 7 2009, 05:50 AM Attached File(s) |
 |   |
 |
Replies
(40 - 59)
| Jan 11 2007, 03:20 AM Post
#41 | |
| Member Group: Members Posts: 143 Joined: 7-February 06 Member No.: 87234  |
nice andregcasal I will test soon and hope if anything doesn't work for your help. Have been looking here before (several months ago)...thought this subject was dead...but no. nice. |
| | |
| Jan 11 2007, 05:27 AM Post
#42 | |
| Group: Members Posts: 6 Joined: 7-January 07 Member No.: 120751  |
Nice guide, big thx
This post has been edited by OzOne: Jan 11 2007, 10:52 AM |
| | |
| Jan 11 2007, 07:37 AM Post
#43 | |
| André Guimarães Casal Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771 |
TheExterminator let me explain All extensions that end in *.in_ are compressed files. These files can be uncompressed with WinRar and the *.inf file within is the one you want You can open *.inf files are simple text files, so you can open them with Notepad. Now there may or may not be *.in_ files in your installation source. If there's only *.inf files, then you don't have to uncompress anything, easyer  I hope I answered your question Pliek, i'll be here if you need me This post has been edited by andregcasal: Jan 14 2007, 06:21 PM |
| | |
| Jan 11 2007, 10:34 AM Post
#44 | |
| Newbie Group: Members Posts: 31 Joined: 7-January 07 From: Denmark Member No.: 120778  |
Okay, But when i paste this in CODE [SetupData] CatalogSubDir="\i386" [SetupHotfixesToRun] CMD\RunOnce.cmd I will Chance my CatalogSubDir="\i386\svcpack" And it will not work. QUOTE (andregcasal @ Jan 11 2007, 02:37 PM)  TheExterminator let me explain All extensions that end in *.in_ are compressed files. These files can be uncompressed with WinRar and the *.inf file within is the one you want You can open *.inf files are simple text files, so you can open them with Notepad. Now there may or may not be *.in_ files in your installation source. If there's only *.inf files, then you don't have to uncompress anything, easyer I hope I answered your question This post has been edited by TheExterminator: Jan 11 2007, 10:35 AM |
| | |
| Jan 11 2007, 04:20 PM Post
#45 | |
| André Guimarães Casal Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771 |
Oh yes, i believe i understand your question now. If you change CatalogSubDir="\i386\svcpack" to CatalogSubDir="\i386" just edit your svcpack.inf from CODE [SetupData] CatalogSubDir="\I386\svcpack" [ProductCatalogsToInstall] KB873339.cat to CODE [SetupData] For example CatalogSubDir="\I386" [ProductCatalogsToInstall] svcpack\KB873339.cat This post has been edited by andregcasal: Jan 11 2007, 04:20 PM |
| | |
| Jan 11 2007, 05:40 PM Post
#46 | |
| Newbie Group: Members Posts: 31 Joined: 7-January 07 From: Denmark Member No.: 120778 |
Thanks alot, why the hell i dont think on this. Thanks alot again, and again and for the great guide you have made. I have made a .cmd file where it download all update from microsoft, will you have it. ?? QUOTE (andregcasal @ Jan 11 2007, 11:20 PM) Oh yes, i believe i understand your question now. If you change CatalogSubDir="\i386\svcpack" to CatalogSubDir="\i386" just edit your svcpack.inf from CODE [SetupData] CatalogSubDir="\I386\svcpack" [ProductCatalogsToInstall] KB873339.cat to CODE [SetupData] For example CatalogSubDir="\I386" [ProductCatalogsToInstall] svcpack\KB873339.cat |
| | |
| Jan 11 2007, 05:43 PM Post
#47 | |
| André Guimarães Casal Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771 |
Welcome  What you mean by all updates? Service packs or hotfixes? Does your .cmd file checks the installations source to determine which updates it needs? |
| | |
| Jan 12 2007, 12:34 AM Post
#48 | |
| Newbie Group: Members Posts: 31 Joined: 7-January 07 From: Denmark Member No.: 120778 |
Is hotfixes. The file download it to you computer and install it with you xp cd QUOTE (andregcasal @ Jan 12 2007, 12:43 AM) Welcome What you mean by all updates? Service packs or hotfixes? Does your .cmd file checks the installations source to determine which updates it needs? |
| | |
| Jan 12 2007, 02:49 AM Post
#49 | |
| Newbie Group: Banned Posts: 25 Joined: 9-January 07 Member No.: 121038 |
Thanks for the amazing valuable information guys
|
| | |
| Jan 12 2007, 06:26 AM Post
#50 | |
| André Guimarães Casal Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771 |
Well, i would appreciate if you could post this to us And i would post it in the guide too Glad to help Black Wolf |
| | |
| Jan 13 2007, 04:25 PM Post
#51 | |
| Newbie Group: Members Posts: 31 Joined: 7-January 07 From: Denmark Member No.: 120778 |
OKay, Here A The Long Code To The .cmd File QUOTE (andregcasal @ Jan 12 2007, 01:26 PM) Well, i would appreciate if you could post this to us And i would post it in the guide too Glad to help Black Wolf Attached File(s) |
| | |
| Jan 13 2007, 05:28 PM Post
#52 | |
| André Guimarães Casal Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771 |
Actually amazing, with "for" cycles and everything  It could be very useful Although RyanVM has that covered This post has been edited by andregcasal: Jan 13 2007, 11:02 PM |
| | |
| Jan 14 2007, 11:36 AM Post
#53 | |
| André Guimarães Casal Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771 |
Updated  New exciting improvement |
| | |
| Jan 15 2007, 01:45 PM Post
#54 | |
| Group: Members Posts: 6 Joined: 7-January 07 Member No.: 120751 |
It's possible to add RyanVM Update Pack with your method ?
|
| | |
| Jan 15 2007, 02:53 PM Post
#55 | |
| André Guimarães Casal Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771 |
Absolutely In fact i was thinking of adding that method to the guide. It doesn't have directly to do with multi boot, but it sure should help.
This post has been edited by andregcasal: Jan 15 2007, 02:53 PM |
| | |
| Jan 15 2007, 05:56 PM Post
#56 | |
| Group: Members Posts: 6 Joined: 7-January 07 Member No.: 120751 |
I added the ryan updatepack and after Windows copied files I have this error: 
error2.JPG ( 8.32K )
Number of downloads: 9I added too: IE7 with nlite + Directx 9 + Codec Pack + Java 6 And WMP 11. This post has been edited by OzOne: Jan 15 2007, 06:00 PM |
| | |
| Jan 16 2007, 05:47 AM Post
#57 | |
| André Guimarães Casal Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771 |
Keep in mind that the the RyanVM update pack is the first thing you should do to your source. Use before anything else. If that's not the case, then it seems you have some bad reference to a drive that isn't there. Don't know exactly what it is, but I'd say some of you CMD files (if you have some) has a reference to something other than C:\ (or the drive you'r installing to). Not exactly sure, but take a look at your CMD files and check for errors. Hope it helps |
| | |
| Jan 16 2007, 11:40 AM Post
#58 | |
| Group: Members Posts: 6 Joined: 7-January 07 Member No.: 120751 |
I have just added ryan update pack and modify my svcpack.inf: now it's work Thx
|
| | |
| Jan 16 2007, 10:23 PM Post
#59 | |
| Newbie Group: Members Posts: 17 Joined: 15-January 07 Member No.: 121874  |
Hi guys. I'm using this guide to streamline our SOE Build process and hopefully save our Field Service agents some time when rebuilding machines from scratch. I've been able to use these instructions to make a dual boot CD, which creates 2 different versions of our Windows XP CD by duplicating the source files for different installations. My unattend answer file uses the runonceex method to install our applications, and as such I'm unsure if it's really compatible with the instructions. I'd rather use the same DVD to build all four versions of our SOE, as they are all windows XP service pack 2 based. I've attempted to make setup call the correct batch file to make the registry entries in runonceex by using the .TAG file method, in order to differentiate between each SOE version. The issue I'm having, is I've followed the instructions for creating the TAG file, however setup isn't creating the file at all. My winnt.sif file is as follows: CODE ;SetupMgrTag [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" [Unattended] DetachedProgram="cmd.exe /c @ECHO something>%SystemDrive%\DTPR.TAG" UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes UnattendSwitch="Yes" ResetSourcePath=e:\i386 TargetPath=\WINDOWS Repartition=No WaitForReboot="No" OemPnPDriversPath="Drivers" DriverSigningPolicy=Ignore FileSystem=* [GuiUnattended] AdminPassword=adminpassword EncryptedAdminPassword=no OEMSkipRegional=1 TimeZone=255 OemSkipWelcome=1 AutoLogonCount=2 [UserData] ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX FullName="company" OrgName="company" ComputerName=* [RegionalSettings] LanguageGroup=1 SystemLocale=00000c09 UserLocale=00000c09 InputLocale=0c09:00000409 [Identification] [Networking] InstallDefaultComponents=Yes [Shell] DefaultStartPanelOff = Yes [Components] AccessOpt = on ; accessibility wizard Calc = on ; calculator CertSrv = on ; certificate services compontents of the certificate server CertSrv_Client = on ; web client components of the certificate server CertSrv_Server = on ; server components of the certificate server CharMap = on ; enables insertion of symbols and characters into documents Chat = off ; chat client Clipbook = on ; clipboard viewer Complusnetwork = on ; COM+ network access DeskPaper = off ; desktop wallpaper Dialer = on ; phone dialer Dtcnetwork = on ; DTC network access Fax = on ; Fax components fp_extensions = on ; Front Pager Extensions fp_vdir_deploy = on ; Visual Interdev RAD remote deployment freecell = off ; freecell game hearts = off ; hearts game hypertrm = on ; hyperterm IEAccess = on ; installs visible entry points (shortcuts) for IE IEHardenAdmin = off ; harden IE for administrators, power users IEHardenUser = off ; harden IE for users Iis_Common = off ; common set of files needed by internet information services Iis_Ftp = off ; ftp service Iis_Htmla = off ; html based administration tools for iis Iis_Inetmgr = off ; microsoft management console based administration tools for iis iis_nntp = off ; NNTP server. iis_nntp_docs = off ; NNTP server docs. iis_pwmgr = off ; personal web manager, valid only for w2k professional iis_smtp = off ; SMTP server. iis_smtp_docs = off ; SMTP server docs. iis_www = off ; www service iis_www_vdir_printers = off ; Web printing components iis_www_vdir_terminalService = off; Installs terminal Services Active X control into the virtual directory IisDbg = on ; script debugger indexsrv_system = off ; indexing services, requires iis_common, iis_inetmgr, iis_www and com = on inetprint = on ; internet printing, requires iis_common, iis_inetmgr, and iis_www LicenseServer = off ; Disable Terminal Services licensing. media_clips = off ; Sample Sounds Media_Utopia = off ; utopia sound scheme minesweeper = off ; game mousepoint = off ; mouse pointers Mplay = on ; Windows media player msmq_ADIntegrated = off ; Integrates MSMQ into AD msmq_Core = off ; MSMQ core components msmq_HTTPSupport = off ; Enables MSMQ to use HTTP msmq_LocalStorage = off ; Allows messages to be stored locally msmq_MQDSService = off ; Provides AD and site recognition msmq_RoutingSupport = off ; Provides MSMQ routing msmq_TriggerService = off ; associates message arrival with com objects msnexplr = off ; Installs MSN Explorer msmsgs = off ; Disables Windows Messenger MsWordPad = on ; Word Pad NetCis = on ; microsoft com internet services, requires iis_common, iis_inetmgr, iis_www and com = on NetOc = on ; additional optional networking components, requires [NetOptionalComponents] section ObjectPkg = on ; object packager OEAccess = off ; hide Outlook Express icons Paint = on ; MS Paint pinball = off ; game rec = on ; sound recorder reminst = off ; remote installation services rootautoupdate = on ; OCM update root certificates RStorage = off ; remote storage services enable the use of tape libraries as extensions of ntfs volumes solitaire = off ; Solitaire game spider = off ; spider game Templates = on ; document templates TerminalServer = off ; Installs Terminal Services on SERVERs only TsClients = off ; if TsEnable = On then tsClient files for creating client disks, appx 10MB TsWebClient = on ; Installs the ActiveX component for terminal services. requires IIS vol = on ; volume control wmaccess = off ; show Windows Messenger shortcuts wmPOCM = off ; show Windows Media Player shortcuts Wms = off ; windows media technologies components Wms_Admin_asp = off ; windows media technologies server administration tools web components wms_admin_mmc=off ; Windows Media MMC snap in Wms_Server = off ; windows media technologies server, requires Wms_Admin zonegames = off ; Installs MS Game Zone internet games [NetOptionalComponents] LPDSVC = 1 [IEPopupBlocker] BlockPopups=No I know setup is calling the winnt.sif file to do the Windows installation, as setup does not ask me any questions - and all the options are configured correctly in the operating system after installation, however setup is still not creating the .TAG file as required. The winnt.sif file is being placed in the PRO1 folder as suggested... Any suggestions? This post has been edited by dunkie12: Jan 16 2007, 10:27 PM |
| | |
| Jan 17 2007, 07:48 PM Post
#60 | |
| André Guimarães Casal Group: Members Posts: 181 Joined: 25-November 05 From: Aveiro Member No.: 80771 |
Hello dunkie12  The problem is very simple... You have DetachedProgram="cmd.exe /c @ECHO something>%SystemDrive%\DTPR.TAG" instead of DetachedProgram="%SystemRoot%\System32\cmd.exe /c @ECHO something>%SystemDrive%\XPPRO.TAG". Hope it helps This post has been edited by andregcasal: Jan 17 2007, 07:49 PM |
| | |
 |
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:
| Lo-Fi Version | Time is now: 21st November 2009 - 07:57 PM |
All trademarks mentioned on this page are the property of their respective owners
MSFN is not affiliated with Microsoft
Copyright © 2001-2009 msfn.org
Privacy Policy
MSFN is not affiliated with Microsoft
Copyright © 2001-2009 msfn.org
Privacy Policy