TheTechGuide Forum
General Category => Software => Topic started by: Anonymous on August 06, 2002, 02:48:52 AM
-
Can we make msbatch.inf file for windows XP with
auto-insert serial number?
-
Remember that msbatch.inf only works for 95, 98 and ME. For the NT world (NT4, 2000 and XP) you will use winnt.sif instead. Create the unattend.txt file from the generator or make it from scratch if your familiar with the structure and rename to winnt.sif
After that put in on a floppy or burn into the i386 folder.
Hope this helps,
-
How do you make one of these files?
-
SUPPORTTOOLSDEPLOY.CAB for 2000 and XP. I think the same for NT4 but don\'t have a copy with me at the moment. As for the Dos version (9X, ME) I think it is located under a tools folder as well. Again don\'t have one of those CD\'s with me at the moment. I will post if I find one.
-
Ok that would be to create a
copy and paste the bottom to the text.txt file and save, then rename it to WINNT.SIF and place it in you i386 dir/folder
but i WARN YA...it sux. Because now in XP it seems you have to use Winnt32.exe to select a folder to install to and you cannt run that from boot...you must be running windows already.
if you read my recent post here about the unattend.bat you would understand my difficulties in this crap. in windows 2000 you could type Manual and it would ask you for the directory to install to. or if you do what is told here patch the PID in win2k to 240 to kick out the PID request you could just do that. but if you want to have it all done for you automatically then you zhit out of luck
just copy the below and edit what you want and save the .txt as WINNT.SIF...this is from XP\'s..it sux though
;SetupMgrTag
[Data]
AutoPartition=1
MsDosInitiated=\"0\"
UnattendedInstall=\"Yes\"
[Unattended]
UnattendMode=ProvideDefault
OemPreinstall=No
TargetPath=WINDOWS <--this is bullzhit and there\'s no way around it...i guess for now. you can name it to whatever you want and it will work but dont try to name it as a invalid character like ? or / it will boot up and kill it. i thought i could be clever by doing that and have it possibly default back to ask for a correct location but it didnt work...just made me stop the install and i was and still am highly disappointed.
[GuiUnattended]
EncryptedAdminPassword=NO
[UserData]
ProductID=AAAAA-AAAAA-AAAAA-AAAAA-AAAAA
FullName=\"doink doink\"
OrgName=\"bonk bonk\"
[GuiRunOnce]
Command0=blah.bat
[Identification]
JoinWorkgroup=thissux
[Networking]
InstallDefaultComponents=Yes
-
Ok to follow up you can be retarded and open up the location of the Product key dialogue box and just add it in there. i found it one day and it worked. i tried it once but never tested it. im sure it will work because it works in almost any situation only problem i thought of is that setup might detect it\'s been altered and error out...but even in this case i still doubt that would happen for windows install i dont believe does CRC sort of things. that is why you get some corrupt files after install sometimes. again im pretty sure it will work. it works in Visual Studio.NET and that is a more costly application, but there is another way to do that in .NET which is legal and just auto inserts it for you that works and is how i use it right now. you can unattend that too which i think just about anybody that has to install that pretty much does.
this is all good if you want to bypass just have to right the key number on the cd or make a .txt named with the cd key or in it. but again this is not my concern. i careless right now about the damn key.
-
Hey Space,
I was thinking about your comments. First, the line MsDosInitiated=\"0\" should be \"1\" if placing in the i386 folder. I seem to remember that even booting into dos to install leaving it a 1 makes the file work still. Of course I could be wrong. For everyone else 0=Dos boot disk, 1=CD install.
;SetupMgrTag
[Data]
AutoPartition=1
MsDosInitiated=\"0\"
UnattendedInstall=\"Yes\"
[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
;OemPnPDriversPath=driversnetE100B
TargetPath=WINDOWS
Filesystem = convertntfs
extendoempartition = 0
[GuiUnattended]
AdminPassword=\"password\"
EncryptedAdminPassword=NO
AutoLogon=Yes
AutoLogonCount=1
OEMSkipRegional=1
TimeZone=4
OemSkipWelcome=1
[UserData]
ProductID=12345-12345-12345-12345-12345
FullName=\"Twinkie\"
OrgName=\"Tech-Hints\"
ComputerName=Default
[Url]
Home_Page=http://www.tech-hints.com/
Quick_Link_1_Name=\"MS HomePage\"
Quick_Link_1=http://www.microsoft.com/
[FavoritesEx]
Title1 = \"Tech-Hints.url\"
URL1 = \"http://www.tech-hints.com/\"
Title2 = \"The Tech Guide.url\"
URL2 = \"http://www.thetechguide.com\"
Title3 = \"Bart\'s Site.url\"
URL3 = \"http://www.nu2.nu\"
Title4 = \"Flames site.url\"
URL4 = \"http://www.geocities.com/the_flames\"
[Branding]
BrandIEUsingUnattended=Yes
[Identification]
JoinWorkgroup=WORKGROUP
[Components]
accessopt=On
calc=On
cdplayer=On
certsrv=Off
certsrv_client=Off
charmap=On
chat=Off
cluster=Off
deskpaper=On
dialer=Off
fp_extensions=Off
freecell=On
hypertrm=Off
iis_common=Off
iisdbg=Off
iis_doc=Off
iis_ftp=Off
iis_htmla=Off
iis_inetmgr=Off
iis_nntp=Off
iis_nntp_docs=Off
iis_pwmgr=Off
iis_smtp=Off
iis_smtp_docs=Off
iis_www=Off
indexsrv_system=Off
media_clips=Off
media_utopia=Off
minesweeper=On
mousepoint=On
mplay=On
msmq=Off
mswordpad=On
netcis=Off
netoc=On
objectpkg=Off
paint=On
pinball=On
rec=On
reminst=Off
rstorage=Off
solitaire=On
templates=Off
TSClients=Off
TSEnable=Off
vol=On
[Networking]
InstallDefaultComponents=Yes
As too only running when used in a Windows enviroment. That should only happen if you name it winnt32.sif, of course I never did try that. Why upgrade all the old problems. Clean install is the best way to go.
If you want to know what else you can do with XP unattend open the file \"ref.chm\" from inside deploy.cab. It is a M$ help menu that can walk you through all the extra\'s you can throw in. A lot better than the 200 odd page Word Document they use to include. At least I think so.
-
I took this straight from the ref.chm in the deploy.cab
\"MsDosInitiated
Value: 0
Informs the Windows Setup Loader that an unattended Setup is running directly from the product CD. The value must always be set to 0. If you do not set the value to 0, Setup fails at the beginning of GUI-mode Setup.\"
ive never set it to 1 but i imagine that would make it a local drive install for a network or whatever.
but it must be set to 0.
Twinkie i can\'t lie to you though i have never set it to 1 so really don\'t know. I imagine if you did set it to one it would be a tricky install and you would have to have your 2k install disk on the drive already. I know ive never changed the value to 1 and it\'s worked...so far.
Either way this doesnt fix the problem of have XP install 2k into its choosen folder.
Ive been thinking about it and the only way to do that would be to go ahead and install win9x onto a cd, boot that, and on the same cd have a 2k install withit and then upgrade...which is close to stupid :-) (but i might try it :-P). Im in the situation where ever directory that is named WINDOWS or WINNT or something else like WIN is another and SYSTEMOS is already holding either a 9x or nt4/2k install. I want to upgrade them all but this would sux to have to do a upgrade. I just don\'t like to upgrade because the registry will still be \"dirty\".
-
I love it when people check my work. That was a bug in the Win2000 Multiboot project. XP must be set to \"0\" as Space says. Thank you Space.
-
someone mentioned a winnt.sif generator for unattended setup, can anyone tell me where to find it please?
Thanks.
-
Why not just use
;SetupMgrTag
[UserData]
ProductID=12345-12345-12345-12345-12345
FullName=\"\"
OrgName=\"\"
-
You can\'t just use that...because the setup must load the WINNT.SIF and read for what the setup type is...no setup type defined it default\'s back to normal setup...or so i would think.