UNATTEND.TXT vs. WINNT.SIF
-
- Posts: 53
- Joined: Wed Sep 20, 2006 4:31 pm
UNATTEND.TXT vs. WINNT.SIF
I understand the concepts of each but am confused when and where to make the changes and the protocol of the divisions within the files.
Might someone give ma a one-liner as to the difference and when to use each?
Thanks!
Might someone give ma a one-liner as to the difference and when to use each?
Thanks!
-
- Posts: 53
- Joined: Wed Sep 20, 2006 4:31 pm
Seraph,
Thanks. I'm reading about the configuration options and I realized that they are about the same. WINNT.SIF for a CD install, etc.
I'm modifying the UNATTEND.TXT from the subdirectory where I allowed nLite to prepare from my original WinXP w/SP2 CD. Naming it to WINNT.SIF has caused me several different errors and I now know that UNATTEND.TXT is completelly ignored if I create an ISO and load that into my virtual machine.
I can't seem to find the proper voodoo to get the changes I've made utilized during the integration and ISO creation. What might you think is wrong?
Thanks. I'm reading about the configuration options and I realized that they are about the same. WINNT.SIF for a CD install, etc.
I'm modifying the UNATTEND.TXT from the subdirectory where I allowed nLite to prepare from my original WinXP w/SP2 CD. Naming it to WINNT.SIF has caused me several different errors and I now know that UNATTEND.TXT is completelly ignored if I create an ISO and load that into my virtual machine.
I can't seem to find the proper voodoo to get the changes I've made utilized during the integration and ISO creation. What might you think is wrong?
Hard to say without having a look at it, but you can find a lot of information in REF.CHM within DEPLOY.CAB.
-
- Posts: 53
- Joined: Wed Sep 20, 2006 4:31 pm
Been reading REF.CHM and still haven't gotten the hang of it yet.
Here's my WINNT.SIF, if you please:
; Microsoft Windows
; (c) 1994 - 2001 Microsoft Corporation. All rights reserved.
;
; Sample Unattended Setup Answer File
;
; This file contains information about how to automate the installation
; or upgrade of Windows so the Setup program runs without requiring
; user input. You can find more information in the ref.chm found at
; CD:\support\tools\deploy.cab
;
[Unattended]
Unattendmode = FullUnattended
OemPreinstall = NO
TargetPath = *
Filesystem = LeaveAlone
UnattendSwitch=Yes
[GuiUnattended]
; Sets the Timezone to the Pacific Northwest
; Sets the Admin Password to NULL
; Turn AutoLogon ON and login once
TimeZone = "020"
AdminPassword = *
AutoLogon = Yes
AutoLogonCount = 1
[LicenseFilePrintData]
; For Server installs
AutoMode = "PerServer"
AutoUsers = "5"
[GuiRunOnce]
; List the programs that you want to lauch when the machine is logged into for the first time
[Display]
BitsPerPel = 16
XResolution = 800
YResolution = 600
VRefresh = 70
[Networking]
[Identification]
JoinWorkgroup = IBMPEERS
[UserData]
FullName = "Your Name"
OrgName = "Your Organization Name"
ComputerName = *
ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
Here's my WINNT.SIF, if you please:
; Microsoft Windows
; (c) 1994 - 2001 Microsoft Corporation. All rights reserved.
;
; Sample Unattended Setup Answer File
;
; This file contains information about how to automate the installation
; or upgrade of Windows so the Setup program runs without requiring
; user input. You can find more information in the ref.chm found at
; CD:\support\tools\deploy.cab
;
[Unattended]
Unattendmode = FullUnattended
OemPreinstall = NO
TargetPath = *
Filesystem = LeaveAlone
UnattendSwitch=Yes
[GuiUnattended]
; Sets the Timezone to the Pacific Northwest
; Sets the Admin Password to NULL
; Turn AutoLogon ON and login once
TimeZone = "020"
AdminPassword = *
AutoLogon = Yes
AutoLogonCount = 1
[LicenseFilePrintData]
; For Server installs
AutoMode = "PerServer"
AutoUsers = "5"
[GuiRunOnce]
; List the programs that you want to lauch when the machine is logged into for the first time
[Display]
BitsPerPel = 16
XResolution = 800
YResolution = 600
VRefresh = 70
[Networking]
[Identification]
JoinWorkgroup = IBMPEERS
[UserData]
FullName = "Your Name"
OrgName = "Your Organization Name"
ComputerName = *
ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
-
- Posts: 53
- Joined: Wed Sep 20, 2006 4:31 pm
I appreciate the guidance but I'm really getting frustrated at this point.
When using setupmgr.exe, I allow the default subdirectory and point the files to be copied to my XPcd subdirectory and the process completes properly.
I see the unattend.txt file properly created with the attendant unattend.bat file and the I386 subdirectory. Following that, I point the Integrator to the x:\windist subdirectory and allow it to complete to finisih, make the ISO and load it into VMware creating an environment, but immediately I get a dialog box asking for the diskette containing SP2 to be placed into the A: drive.
I've successfully created integrated ISOs that load properly onto my system but for the life of me I cannot seem to get the information I enter into setupmgr.exe to transfer across correctly as it should.
Can someone please give me some insight where I am going wrong?
It;s not that I am not reading the suggested FAQs, etc. but just am not comprehending all that I have read.
When using setupmgr.exe, I allow the default subdirectory and point the files to be copied to my XPcd subdirectory and the process completes properly.
I see the unattend.txt file properly created with the attendant unattend.bat file and the I386 subdirectory. Following that, I point the Integrator to the x:\windist subdirectory and allow it to complete to finisih, make the ISO and load it into VMware creating an environment, but immediately I get a dialog box asking for the diskette containing SP2 to be placed into the A: drive.
I've successfully created integrated ISOs that load properly onto my system but for the life of me I cannot seem to get the information I enter into setupmgr.exe to transfer across correctly as it should.
Can someone please give me some insight where I am going wrong?
It;s not that I am not reading the suggested FAQs, etc. but just am not comprehending all that I have read.
- willpantin
- Posts: 37
- Joined: Wed May 31, 2006 9:27 am
- Location: Newnan, GA, USA
Have you solved your problem yet?
Best bet for you is to follow the Unattended guide at msfn.org, step by step. It is made simple there for you.
Hard to say exactly what you are doing wrong, with the info given, but sounds as though it may be a very basic mistake. Are you placing the winnt.sif file in the I386 directory? Are you making a "bootable" ISO image?
Best bet for you is to follow the Unattended guide at msfn.org, step by step. It is made simple there for you.
Hard to say exactly what you are doing wrong, with the info given, but sounds as though it may be a very basic mistake. Are you placing the winnt.sif file in the I386 directory? Are you making a "bootable" ISO image?
-
- Posts: 53
- Joined: Wed Sep 20, 2006 4:31 pm
ViVa gave me a copy of his WINNT.SIF and I slightly modified it THEN PUT IT INTO MY I386 SUBDIRECTORY.willpantin wrote:Have you solved your problem yet?
Are you placing the winnt.sif file in the I386 directory?
I thought setupmgr.exe did that for me. It's really amazing how small details like that can get left out.
So, the WINNT.SIF is functioning for me (I saw the machine name I assigned my peer appear in the dialog box soliciting an administrator's password) so I know it's not tripping up the installer. So, I'm off for the deep end now. <g>
Thanks for your concern. I seem to be getting the impression that WINNT.SIF is hand crafted whereas UNATTEND.TXT is manufactured from the inputs in setupmgr.exe.
Slowly but surely.
If I remember right, Setupmgr assumes a network install and creates unattended.txt.
When you changed it to a CD install you need to rename it to winnt.sif.
All CD installs look for winnt.sif, not unattended.txt.
In the SUPPORT\TOOLS directory on the XP CD, you'll find a help file called ref.chm.
It has a lot of info.
Dave
When you changed it to a CD install you need to rename it to winnt.sif.
All CD installs look for winnt.sif, not unattended.txt.
In the SUPPORT\TOOLS directory on the XP CD, you'll find a help file called ref.chm.
It has a lot of info.
Dave
-
- Posts: 53
- Joined: Wed Sep 20, 2006 4:31 pm