Unattended install, SATA drivers, and NO Floppy I finally got it to work!
Posted 07 January 2004 - 01:55 AM
i didn't get any emails about replies, so i forgot to check this thread *blush*
ok.. some info about what i did? sure.
(appologies for offsite link)
the my solution is this => http://forum.abit-usa.com/showthread.php?s=&threadid=29161
and for a detailed run down of the research ( a very mind-numbing read) ...
so in the end, i _did_ get the OS to auto-copy the driver files over to the correct places by using the [MassStorageDrivers] line.
like i said - it's been a few months (october?) since i last mucked around with this ... but i've been trying for a year.
>>Why don't YOU do a search at www.microsoft.com for txtsetup.sif
heh keep your cool, buddy. did that a long time ago. anyways, i really don't want this to turn into a flame/troll topic. I was only trying to suggest other ways to solve the same problem - other ways which i believe are more stylish and less of a hack. Yes - we have to hack certain things to get our results (eg. the UXTHEME example above). I'm just hoping people continue to try and find more elegant and less troublesome ways to get the same solution - that is what this website is all about.
Please, have a read about what i posted up, and i hope u have some luck - please post any comments.
Posted 07 January 2004 - 05:10 AM
14) add the following line under [HardwareIdsDatabase]
PCI\VEN_1095&DEV_3112&SUBSYS_61121095 = "Si3112r"
15) add the following line under [SCSI.Load]
si3112r = si3112r.sys,4
16) add the following line under [SCSI]
si3112r = "Silicon Image SiI 3112 SATARaid Controller"
Oh and of course, pointed the oem...path in winnt.sif to the $OEM$ folder...
Works fine for me
Posted 07 January 2004 - 12:19 PM
New to this forum.
I got a question for you guys, How in the world do you get the info for the fills you need to add to your files for the SATA installion.
This is from first post.
". Modifying installation files
The first file to be modified is TXTSETUP.SIF which is in the i386 directory. This file tells Windows what files to load during the text-only portion of setup. We are going to modify the file to make Windows think that Microsoft put these new driver files in i386 and load them accordingly. Open up TXTSETUP.SIF and do a search for [SourceDisksFiles]. In my file it was on line 181. Now add this text EXACTLY AS SHOWN.
iaStor.sys = 100,,,,,,3_,4,1,,,1,4
si3114r.sys = 100,,,,,,3_,4,1,,,1,4 "
What I want to know is how to find this information.
iaStor.sys = 100,,,,,,3_,4,1,,,1,4
si3114r.sys = 100,,,,,,3_,4,1,,,1,4
The numbers at the end. The rest of the information I'm able to find within my setup files for my SATA controller which is the Promsie 367. Build in for the P4PE MB from Asus. Smillar your guys, but my controller is differnet and doesn't use the two newer chips from Intel.
thanks for any info.
Posted 07 January 2004 - 04:12 PM
Go to your deploy.cab on your Windows Xp Cd (SUPPORT\TOOLS) and extract the file to whereevery you want to. Look for the file called ref.chm and open it.
Yes it's a help file, but this file explains in detail everything you can do to winnt.sif.
Great little pieces of info like how to make sure MSN 4.6 and Explorer 7 aren't installed and so on.
Give it a look. There is a lot that you can make changes to the installation of windows and how it work without having to make reg files to be loaded durning installation.
Hope it helps out,
Posted 07 January 2004 - 04:33 PM
the good thing with that ref.chm help file is that it lists a huge bunch of things u can not install, much more than then .sif wizard program.
Posted 08 January 2004 - 11:37 AM
Here's a link to a web site that explains a bit of it, but not all. Still looking for more info on it, but no luck.
Guess the Credit for this goes to Gosh.
I'll post more if I can find anything more about the last few numbers, but they don't look to important.
Beleive only this part "1,,,,,,_x,2,0" is what you really do need to config so that your drive install properly at the textmode of windows so you can see your SATA drive's or RAID drive's.
Posted 17 January 2004 - 07:34 PM
Thanks again for your post. After trying various things, i have settled on a "lite" version of this method for use in XPCREATE. The changes I made:
1) I dumped the TEXTMODE directory as well as all of the TXTSETUP.OEM files, as they seemed to be too often the source of error.
2) I added all the text to TXTSETUP.SIF in one block, with it's own headers, to the end of the file. Make automated editing a breeze. As you noticed there where already multiple SourceDisksFiles sections. Windows parses all elements from multiple instances of a header together before processing the file itself.
For what it is worth, the steps I took are listed on THIS page.
Thanks again, raskren, for getting me started on this, and for your clear instructions.
Posted 18 January 2004 - 03:55 AM
Somehow it seems much "cleaner" without hunting down the INF sections, and I was not looking forward to writing that script. Thanks go out to jdeboeck for pointing out that multiple instances of the same section header were not a problem.
I actually started out using all the steps you listed, and removed or "simplified" them after that was working. And I NEVER liked those TXTSETUP.OEM. I think the key is that TXTSETUP.OEM requires editing depending on File Systems, and in a fresh CD install, you do not need to pre-determine the File System. I have not heard of anyone having succes with this file. (Except Pure Krome, but after looking at that method I determined that "hacking" TXTSETUP.INF was a whole lot cleaner than hijacking the XP install, and adding three different copies of TXTSETUP.OEM: Sorry, I had to conclude that this way is much less of a "hack"). I DO NOT believe that the WINNT.SIF / MassStorageDrivers was designed to be used for CD installs, rather for network or SysPrep installs.
Posted 19 January 2004 - 12:21 AM
Same here. After seeing just about everyone's install fail from CD that's the only conclusion I can come to.
I do have a hard time thinking of this as a hack. MS left txtsetup.sif as a plain text file when they could have encoded it in a binary and forced us to hex edit it. I'd call that a hack but not just editing a text file. Is creating winnt.sif a hack? Or cmdlines.txt? If Microsoft wanted to add new F6 drivers to the CD themselves I'm sure this is how they would do it. Once everything is put in its place the install is literally seamless.
Posted 23 January 2004 - 05:42 PM
Pure Krome, on Jan 5 2004, 11:42 PM, said:
Hello you jackass, no need to be a dick to people. The Winnt.SIF method only works on certain PCs, those that have the RAID/SCSI controller specified. If they don't, it errors out. It's also very hard to set up and have work right, it took me a helluva long time. The txtsetup.sif method worked first try for me, and it worked great.
Posted 30 January 2004 - 11:55 AM
Dude, I give me my full support!!!! Your method worked for me right out of the box. I also have an ABIT IC7 MAX3 board and wanted to install unattended (without F6 input). 1 pass, no errors. Thnx.
Now,,,on,,, to figure out why Photoshop 7.0 is not installing.....................
The Old Dude
Posted 06 March 2004 - 06:37 AM
Raskren - you specified that we should add the following lines to txtsetup.sif:
[SourceDisksFiles] iaStor.sys = 100,,,,,,3_,4,1,,,1,4 si3114r.sys = 100,,,,,,3_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_8086&DEV_24DF&CC_0104 = "iaStor" PCI\VEN_1095&DEV_3114&SUBSYS_61141095 = "Si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_288510F1 = "Si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_047AA0A0 = "Si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_0478A0A0 = "Si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_0479A0A0 = "Si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_90181695 = "Si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_F642270F = "Si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_100415BD = "Si3114r" [SCSI.load] iaStor = iaStor.sys,4 si3114r = si3114r.sys,4 [SCSI] iaStor = "Intel(R) 82801ER SATA RAID Controller" si3114r = "Silicon Image SiI 3114 SATARaid Controller"
I'm btw also adding SI3112A SATA drivers as well as Highpoint 372 RAID drivers to my installation. When I look at the TxtSetup.oem & .inf files of those drivers and look at the corresponding sections you mentioned above, it looks a bit different than the way you have described it. Here's an excerpt of the SI3112A SATA driver sections from the TxtSetup.oem & .inf files of the drivers I'm using:
[SourceDisksNames] 1="Silicon Image SiI 3x12 SATALink Driver Installation Disk",SI3112.sys,, [SourceDisksFiles] SI3112.sys = 1 SI3112.mpd = 1 SiiSupp.vxd = 1 SilSupp.cpl = 1 SiWinAcc.sys = 1 (both of the above taken from the .inf file) [SCSI] ; HwComponent section Si3112_XP = "Silicon Image SiI 3x12 SATALink Controller for Windows XP/Server 2003" [Files.SCSI.Si3112_XP] driver = disk1,si3112.sys, Si3112 driver = disk1,SiWinAcc.sys, SiFilter inf = disk1,SI3112.inf dll = disk1,SilSupp.cpl catalog = disk1, Si3112.cat [HardwareIds.SCSI.Si3112_XP] id = "PCI\VEN_1095&DEV_3112&SUBSYS_31121095", "Si3112" id = "PCI\VEN_1095&DEV_3112&SUBSYS_34238086", "Si3112" id = "PCI\VEN_1095&DEV_3112&SUBSYS_311215D9", "Si3112" id = "PCI\VEN_1095&DEV_3112&SUBSYS_B0021458", "Si3112" id = "PCI\VEN_1095&DEV_3112&SUBSYS_01661028", "Si3112" id = "PCI\VEN_1095&DEV_3112&SUBSYS_82141033", "Si3112" id = "PCI\VEN_1095&DEV_3512&SUBSYS_35121095", "Si3112" id = "PCI\VEN_1095&DEV_3512&SUBSYS_01661028", "Si3112" [Config.Si3112] value = ProblemDevices, "", REG_SZ, "" value = ProblemDevices, "Maxtor 4D060H3 DAK05GK0", REG_SZ, "MaxMode = UDMA-5" value = ProblemDevices, "ST320012AS", REG_SZ, "Mod15Write" value = ProblemDevices, "ST330013AS", REG_SZ, "Mod15Write" value = ProblemDevices, "ST340017AS", REG_SZ, "Mod15Write" value = ProblemDevices, "ST360015AS", REG_SZ, "Mod15Write" value = ProblemDevices, "ST380023AS", REG_SZ, "Mod15Write" value = ProblemDevices, "ST3120023AS", REG_SZ, "Mod15Write" value = ProblemDevices, "ST340014ASL", REG_SZ, "Mod15Write" value = ProblemDevices, "ST360014ASL", REG_SZ, "Mod15Write" value = ProblemDevices, "ST380011ASL", REG_SZ, "Mod15Write" value = ProblemDevices, "ST3120022ASL", REG_SZ, "Mod15Write" value = ProblemDevices, "ST3160021ASL", REG_SZ, "Mod15Write" (the above lines taken from the TxtSetup.oem file)
Now if you compare these with those you posted the headers are obviously a bit different as is the information contained under them. There is also an additional header [Config.Si3112] which contains info specific to the 3112A controller as well. My question is: even if the info in my files isn't exactly the same as what you posted - would there be a problem adding these lines as is (in accordance to Greenmachines guide) to my txtsetup.sif? It seems to be stating the same info only in a different manner. Or do the lines to be added have to be exactly as you posted? If so, what's the reason for this?
Sorry about the long post but I need to get clarification on this point to really understand what's going on here...............
Posted 06 March 2004 - 07:12 PM
It looks like all your driver files belong in Windows\System32 so here's what you need to add:
[SourceDisksFiles] SI3112.sys = 100,,,,,,3_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_1095&DEV_3112&SUBSYS_31121095 = SI3112 [SCSI.Load] "SI3112" = SI3112.sys,4 [SCSI] SI3112 = "Silicon Image SiI 3x12 SATALink Controller"
You'll need to add the rest of the device ids in the format above. You should put the rest of the driver files (other than .sys) into $OEM$\$$\System32 so they get copied over as well.
Good luck, and if I don't respond here feel free to send me a PM and I'll glady try and help.
Posted 17 March 2004 - 06:49 AM
- ← Slipstreaming Vmware LSI Drivers into Sysprep for Hardware Independent
- Device Drivers
- Windows 7 Some Drivers Install, Others Don't →