webmedic

there is a big problem wiht using com files. When you compile your batch files there are things that dont convert over so some com files will wimply not work. It would seem as though most of the theings we do in our cmd files are not compatable with the compile process. Well at least some of ti is not.

Yes I finally got it loading from commands.txt and doing a few other things. You are correct in that it does not seem to like doing msi files. I wonder why that is but it skips them completely as far as I can tell. I can get around this though by doing it wiht a cmd file and just calling that.

here in this thread http://board.MSFN.org/index.php?showtopic=8363 I've done it all for you. I've also tested it on shutle, gigabyte, epox, aopen, and soltek motherboards with built in raid. I installed windows directly to a serial ata maxtor drive on the aopen board and also on the shuttle i have installed it to an actual raid array using a high point raid controler. For the other motherboards I jsut tired it as a hard drive controler. If anybody has any others they would like added to it then let me know. I can add them pretty easily.

yes it was limited to 256 characters but I do mine more or less like this and I have allot of drivers and it works fine.

I got that bit of code from nephlim and it works like it is. Not sure why but it does the other ones were done by me.

thanks for the update on this yes I use a combination of this. I actaully use cmd files for a few things and then laod the inf files from the cmd files. and i had also durring experimanting found the same command lines you use above although I had not found the command trick for the winnt.sif. One more thing I use cmd files to install anything that needs the iss file( ie anything that uses install shield), As for the rest I have found a little utility for minimzing the command propmt and it works pretty good. You simply give a command and it hides the window.

well just make sure that your drivers are included and you have the driver path set correctly in your winnt.sif. Also make sure to have he sys file for your drivers in the i386 directory. As for my fiels yes they should work perfectly. They will still identify your hardware most likely if not send my your drivers and I'll add them. One thing to rememeber is that it would most likely be best to leave them alone like it is. That way if you ever get anything new there is a good chance the drivers will be covered for your new hardware.

ok here goes when you save your theme you can have a background set in it. But you an also use this in the registry. ;[HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Desktop\General] "BackupWallpaper"="c:\\windows\\web\\wallpaper\\Sunset.jpg" "Wallpaper"="c:\\windows\\web\wallpaper\\The Beach.jpg" I do both I set the theme in my winnt.sif and also use this to set a background. You know this will set it as default for all users. I apply this in my root reg tweaks which I apply in my through commands.txt before anybody logs in. I'll do a write up on how to do commands.txt and give my cofig files. I use this so I can get arround using any autologin in my winnt.sif.

hm posssibly.

No i dont. You see a private key is something you have to generate yourself. The thing is that microsoft most likely has their own keys and they are all internal to them which means that you and i have no way of getting them to sighn the binary with to begin with. I had not thought about that.

hm interesting i never would have thought about doing it that way. Let me know if it works. That would be handy for repalcing all kinds of files.

Thanks I'm not sure I downloaded it the last time or not. I would need to repalce it before that though to be able to make it so that themes install like we want them to. I'm researching on this now.

You had to ask that. Ok here goes you have ot create a theme that uses the msstyle you want and then select that theme. Now the bad part I have my install working great with everything installed as default user and it autologs in and everything. The problem is that you can't replace the uxtheme.dll soon enough in the install to have any of the styles be automaticly setup when you finaly boot in but everything else about your theme will work and you can simply right click on the desktop and select the theme or msstyle you want. I have tried this multiple ways but about my only option left is to use that wfp hack you posted and simply shut it off and then turn it back pon after install. That would ease things up a bit. By the way was that dll one of the ones you could replace or no. If it is I could turn off wfp maybe soon enough in the install to have this all work. I'm guessing here but I Think it may work.

yup this in your winnt.sif [shell] ; DefaultStartPanelOff = Yes ; DefaultThemesOff = Yes ; defaultthemesoff = yes will override this setting CustomDefaultThemeFile = "%systemroot%\Resources\Themes\MyTheme.theme" Rember if you shut all the other things off them well your themes wont work. if they include visual styles.

Yes those are fine.

Yes that is correct.

ah thats nothing wait till you see the next thing I'm going to post about. It'll take few days but I'll have it all automated and other good stuff. There will also be a allot of inf file usage to pretty it up and also a few other little things to hide cmd files. I hope I have enough time to get it done. I just posted the other stuff because so many have been asking for it.

Try checking this thread for a better way to do your service packs. http://board.MSFN.org/index.php?showtopic=8363

ok now for the raid controlers and also the correct way to add hotfixes right to the install. NOTE: THIS NEEDS TO HAVE SERVICE PACK 1 ALREADY INSTALLED. I'm working on some more scripts that will autoinstall most of this for you but for now it is a little manual but not to bad. Download this prep files and this ide raid dirvers the prep you can unzip anyplace but the IDE_RAID.zip needs to go into your $OEM$\$1\DRIVERS folder. Now goto your prep directory in there you will find the folders 1, 2, and 3. Your hotfixes go into these. They are in the same order as listed above. Old style hotfixes in the first directory, colorfull icon type in the second directory and the mdac in the third. They all need to be renamed to KB######.exe and Q#######.exe were ###### is the number of the kb of q file. Next look at the \prep\files folder. You will need to extract your sp1 cab from your 1386 folder into the prep\files\sp1 folder. Look into the prep\files\sys folder This contains raid corntoler files that will be slipstreemed into the install. It also contains my winnt.sif and my txtsetup.sif as well as dosnet.inf. You should not have to edit dosnet.inf or txtsetup.sif as these should work for you already. NOTE: txtsetup.sif is the file that loads your raid drivers and I have already added as many as I can get my hands on accept for a new one I got today. If you are having problems let me know and I'll add your raid drivers to this install. Edit the winnt.sif however you need to. Leave the driver paths alone if you dont know what you are doing. If you do know what you are doing make sure to leave the drivers\IDE_RAID one or else you will loose your raid as soon as you boot into the graphical mode for the install. That is about it. Next goto prep and run the do.cmd file. This will do all the work and leave your finished files in folder 5. Simply copy everything in folder 5 into your i386 folder and that is it you will have both ide raid and hotfixes slipstreamed into your install.

Yup thanks for all the good hints. I did add extras so that it would handle the newer hotfixes. Also to note that the next post I'm working on will cover a much better way to do it that I also got allot of it from others on this forum biut again I added to it and expanded on it till it is were it is now. Actually thaks for the reminder also as My memory is not what it should be and I would not have been able to say who I got it from.

OK depending on how you want to do hotfixes there are two ways to do it that are much better than being done by most here. the first is through hotfixes.cmd I have it setup with 3 different hot fix directories the old style go in Hotfixes1. The new style with the colored icons go into Hotfixes2 and last but not least the last hotfix for mdac goes into hotfixes3. CLS @echo off ECHO Installing All Pre-SP2 Hotfixes... ECHO Please Wait... CD "%systemdrive%\install\Hotfixes1 for %%i in (*.exe) do start /wait %%i -u -f -o -z -q -m ECHO Done. ECHO Installing All Pre-SP2 Cumulative patches... ECHO Please Wait... CD "%systemdrive%\install\Hotfixes2 for %%i in (*.exe) do start /wait %%i /Q:A /R:N ECHO Done. ECHO Installing All Pre-SP2 Extra patches... ECHO Please Wait... CD "%systemdrive%\install\Hotfixes3 for %%i in (*.exe) do start /wait %%i /C:"dahotfix /q /n" /Q ECHO Done. EXIT this will allow you to add as many hotfixes as you want without running into troubles you will never have to manually add them again. Now for the more involved way it is better to do it this way but for some reason I have not been able to get the mdac hot fix to install properly. There are no erros or bad things it simply does not install correctly. as it can not find the installer. OK here goes. Will continue in next post. to this thread.

also you have the wrong file paths in your files they all need to be changed. for instance you have this [GuiRunOnce] \$OEM$\$1\SOFTWARE\SOFTWARE.CMD \$OEM$\$1\SOFTWARE\SVCPACK.CMD it need to be changed to this [GuiRunOnce] %systemdrive%\SOFTWARE\SOFTWARE.CMD %systemdrive%\SOFTWARE\SVCPACK.CMD this needs to be changed in all your cmd files also. oh and one more thing. try this for you hot fixes. if you want them installed that way. CLS @echo off ECHO Installing All Pre-SP2 Hotfixes... ECHO Please Wait... CD "%systemdrive%\install\Hotfixes1 for %%i in (*.exe) do start /wait %%i -u -f -o -z -q -m ECHO Done. ECHO Installing All Pre-SP2 Cumulative patches... ECHO Please Wait... CD "%systemdrive%\install\Hotfixes2 for %%i in (*.exe) do start /wait %%i /Q:A /R:N ECHO Done. ECHO Installing All Pre-SP2 Extra patches... ECHO Please Wait... CD "%systemdrive%\install\Hotfixes3 for %%i in (*.exe) do start /wait %%i /C:"dahotfix /q /n" /Q ECHO Done. EXIT I have it setup with 3 different hot fix directories the old style go in Hotfixes1 . The new style with the colored icons go into Hotfixes2 and last but not least the last hotfix for mdac goes into hotfixes3. Hope this helps.

well there you go the only way to d othat is to have the file associations already setup in the registry and unfortunatly since we are installing most of that kind of stuff for the first time there is no associations. Nice try though. I've got a few more goodies up my sleave I hope we will see though I can pretty much promise you that those kind of things will not ba able to be done at that point in the install.

lol you can not use window blinds themes only the visual styles. this does noit replace having windows blicnds it only lets you use xp styles.

before we go any further wiht this there are some installers that this thing does not like for those cmd files will still need to be used but i have found a little command line program that allows you to execute cmd files without the window. I also found another one that will tree the command so you can do multiple things with it. For instance you could aslo log what is going on in the batch file. to a txt file for later viewing. Only problem is that this loging is not available for for any normal installers run through the inf file. As for running them through winnt.sif this should do the trick. This is untested though. I am currently converting most my install stuff to this. Run("C:\WINDOWS\rundll.exe","setupapi,InstallHinfSection DefaultInstall 132 path\to\inf\file\install.inf") Let me test that though first to make sure but it should work. I'll run up the scripts real quick and test it in virtualpc. I'll snapshot it in irfanview for you guys.