X-Savior

I don't know what everyone else thinks but This Thread should be moved to "Sticky" Very useful information for anyone who is looking to integrate drivers on a permenant basis. What do the Other 2400 People to have read this Thread Think? B)

Right On! I will read it tonight! I am now experimenting with XPlode to create a full menu system to let you choose what software to install during the Install Process. It is GREAT!

Sorry Someonesmind! I was not having a good day, and it look to me that you were trying to insult me. My bad if I mis-understood. I was trying to make a point that I am NOT a wanna-be. I understand we are all here to learn a thing or two and improve our skills. Sorry!

Ok Buddy! First of all, I am not a novice my ANY means. I have been using this site for much longer than I have been signed up for. I registered when I felt I could contribue, unlike some people who like to shoot their mouths off! Secondly I didn't see you helping when I helped lead ground-breaking research in Driver Integration's. You might wanna catch the thread, Maby learn a thing or two before you open your mouth. Most "Script Kiddies" think they know everything, beacuse someone else handed them the tools without doing the background research to understand the "Why" behind the "How". If you think I am one of those people you better get your head out from down below because I spent a LONG time making everything I know about Unattended from scratch and learning what I know through proper trials and research. In my experience, it is the people who have nothing better to do than bash other's who are the one's that have have the least to contibute. These people are great at re-spewing what other people say trying to sound "Special" but have no REAL Intellectual abilities. Sorry to burst the bubble but sometimes the truth hurts!

STrange, it double posted on me.

Thank You VERY MUCH Silver! You caught me by surprise... I am quite familiar with the prompt but you blindsided me with that one. Problem Solved! That saves us a HUGE amount of time. Thank you for contributing!

Hey All. Well, I have already larned too much about XPlode now to just shelf it. I REALLY like it. I t is NOT for the beginner though. You really need to read between the lines to deal with the more advanced features. I think it should include more samples AND have much more complicated ones to help understand the WHOLE picture. But once you get the hang of it you can convert your whole application install process into XPlode in only an hour. Just lots of Cut-n'-Paste. I am sure WPI and WAIT are good too. Good for the "Mainstream" of users. I have nothing bad to say about XPLode. To make it really good I recommend getting a freeware program to extract Icon's out of files to use. It make it look REALLY spiffy when you have the Icon for each program beside it. Kinda the "Pro" look.

Sorry, I jsut don't like "Auto" on something I can't control. I prefer to add the drivers my self so I have 100% Control over what is going into MY install. Just don't want my of my work being changed.

Yea, The documentation took a little getting used to. The format was a little confusing but after studying the XML It all started to make sense. I think it SHOULD include a Basic Noobie Tutorial to get people started. No Big Deal. I can't see what everyone is complaining about. If you can't figure it out, you shouldn't be using it.

Ok, I will look into them. I started playing around with XPlode and WOW!!! It is exactly what I wanted. A Full GUI Interface to select the programs to install AND several Pre-Set Selections. After a few hours of studying the XML's I started to get the Knack of it. It is actually VERY easy to use and can be easily adapted to an exisitng install. Are any of the other programs good with a full GUI?

Well Said Erik! We have spent a LONG time with this. From what our Research tells us is that the drivers MUST be integrated into windows PRIOR to install. This way Windows thinks that they were ALWAYS there. As far as EXISTING OS's, the only think I can think of is what Erik is currently working on. If you replace the DRVINDEX.INF post install. It MIGHT work if you create a CAB with your drivers and add the INF to the INF folder and then Modify the DRVINDEX.INF WHat do you think Erik? Might it work?

Hi There, I have spent a long time with this and have helped develop a solution for this... B) Hope it helps. http://www.msfn.org/board/index.php?showtopic=41841 This has been a HUGE breakthrough in Integrating Drivers and creating your own CAB and have windows think it is apart of windows.

XPlode??? What's that? Never heard of it.

Hi there, I am about to make my MCE 2005 Version 2 DVD. On my Version 1 I used Batch file method and it worked great. But, I like the flexibility and looks of the Run Once Method. But my problem is... I would like to create a Menu to select the Individual Software or have a couple of options (Basic, Lite, Full) Depending on what I desire on the machine. Anyone have any experience with this matter?? Thank You!

Good Work Erik! At Last, the Mystery is solved. I didn't expect the results though. VERY interestting. @Erik Interesting Idea. I might adapt part of your idea. Yes, it does save space, I agree, but the Extra 15 - 20 Mins on install time.... Is it worth it? After All, any major install will already be on a DVD so there is more than enough space to accomidate any setup. I am currently at about 3.8 GB Now and It is a HUGE install. I still think maby we should follow through with creating the Cab in advance and have it copy it 2 times. Then we do not need all the files and folder RAW in the $OEM$ folder. You only need Chipset and Mass Storage. Just a thought... Also, Glad to hear about the alternate DRVINDEX.INF, I wonder what it is created from? How did you modify it? Just added your CAB file? or the entire file listing as per my method? @Bashrat Thank you for taking the time to look into creating the program. It would be a HUGE time saver. Also, I downloaded your latest Driver Pack to update my existing install. Wow, you made some changes. I used Method 2 and Manually integrated the stuff the way I wanted. The only pain was putting ALL the directory's in the WINNT.SIF, I am not prepared to re-work this install. I will be starting my MCE 2005 Version2 disc soon and I am going to use RUN ONCE method for software and try combining your method with mine.

Hey all! Well, I have already integrated Mass Storage Drivers and am crateing a new CAB file and integrating it all with as many 64-Bit drivers as I can get my hands on. As per the Method I helped develop on this Thread... http://www.msfn.org/board/index.php?showtopic=41841 This method does not require the need for a WINNT.SIF file to add extra drivers. As far as Software, We will have to see. I am interested to hear from anyone who has attempted yet. I am starting this weekend on with my setup. That way when the Retail arrives at the end of the month I can transplant my work into that one.

Hey All! B) @Erik Good work. I installed windows about 5 times making small changes before I realized I made a spelling error. I would like to know about the Subdir's as well. This would finish it off nice. Well, I think we have now achieved our goal. What Direction should we go with this now? WHat about disabling the Driver Search (Internet) that comes up. Unless it is not a big deal. --- Last night I made a full out CAB file with everything except for Chipset & Mass Storage. I figure we should keep the usual way for them. It's not like your gonna change the MB very often w/o re-installing the OS. Just the drivers for things that are changed more often (Video Cards, Network, USB, Sound, Etc.) I had no problems at all. It found the Driver's. Also, during OS install it will scan the New CAB anyways and install the drivers in it. SO technically you could have EVERYTHING in the CAB and it would work fine. I think it will not work during TEXTMODE though. So Mass Storage will still need to be integrated individually. What we need now is a simple program to make upgrading the CAB file a simple process. I am not good with this department so... I am asking anyone who reads this... If you can make a program to scan a directory, and list all the file names it finds in a .TXT file. That way we can then copy and paste out of it and into our DRVINDEX.INF it will make maintaining the CAB a very simple matter. @Bashrat Any Idea's??? I think this would not be a Big Issue to create this. Should simplify for you as well. --- So now I am starting on a whole new setup this weekend. I will start creating a x64 DVD with all the 64-Bit drivers I can find. I am using RC2 right now but when I get the Retail at the end of the month I will "Transplant" my work into that Version. I am going to use the new Technique we have discovered and see if I can refine it further and try and learn more about it. BTW: I have already made some Progress with x64!!!! ***Cheer!!!***

Ok, no prob. Just to let you guys know, I jumped the gun a little. I did a ful out CAB file with lots of drivers. I then removed them from $OEM$\$1\Drivers Good News... The Drivers were detected on Initial OS install and used them to install existing Hardware. AWESOME. Solution for an overcrowded TXTSETUP.SIF with too many directory references. Bad News... With what I mentioned the USB LAN did not detect and install post OS install. I am starting to return to the NON-Streamlined way of doing this to find where it makes a difference. ??? I added the USB100M.SYS back into the TXTSETUP.SIF and didn't make a difference. I will try adding it to DOSNET.SIF instead. What EXACTLY is the purpose of DOSNET.SIF??? I know TXTSETUP.SIF is to copy all the files to the proper location and DRVINDEX.SIF is a database of all the device drivers and where to find them. We will see what tomorrow brings. ********************************** EDIT: ********************************** SORRY! No Problem. I made a Typo and never caught it. I am trying it again right now but it will turn out fine with my method.

Hey Guys! @Erik Very interesting what you are doing... What does this do? Havn't seen that before. START %CDDRIVE%\WINXP\OEM\bin\WatchDriverSigningPolicy.exe %CDDRIVE%\WINXP\OEM\bin\SetDevicePath.exe %SystemDrive%\DP Also, Any luck with Sub Directory's? I am VERY interested in this as well. I have been too busy to get into testing it though. Been trying to refine the technique I outlined. ---- @Rogue Yea, I would also like to know what you have done to the Registry. I tried your idea with changing it and it made no effect. Maby I am missing something. Also, can you explain more about your script. What exactly does it do? ----- Ok, now for what I have recently learned. We can trim down the steps. Now that this system works I have looked at what can be cut out. I was very surprised. This is my NEW revised method. I think it will simplify using lots of drivers. I am ready now to begin adding LOTS of peripherals to it now. This is all that is required in total... DOSNET.INF [Files] d1,Extra.cab DRVINDEX.INF [Version] CabFiles=Extra,SP2,Driver [Extra] Usb100m.sys [Cabs] Extra=Extra.cab TXTSETUP.SIF [SourceDiskFiles] Extra.cab = 100,,,,,,,39,0,0 DriverCabName=Driver.cab,SP2.cab,Extra.cab [FileFlags] Extra.cab = 16 Ok, so then I just add a copy of the *.Cab to... $OEM$\$$\Driver Cache And the *.INF to... $OEM$\$$\INF Done. So as you see, all the work is done creating the Initial CAB and then you just make entry's in the DRVINDEX.INF to reflect the added Drivers in the [Cab Name] section. This should keep updating and changing the Cab File very simple... Now, if we can get the Sub Directory's to work then we have it made. (Outside of trying to have Windows try and find the Drivers without asking to Search the Internet (I think I Read something about that) and Have Windows Search for the Drivers FIRST. Hopefully some of you have made more progress. ---- @Bashrat What is your take on this, Any Info useful to you?

I agree, but it DOES make a difference. If the CAB is not in BOTH locations windows will NOT find the drivers and install will fail. I have tried removing either one and it quits working till I return the file again. This is VERY strange but the way it seems to be. Next, I would like to figure out how to have the drivers install without searching for them and have it NOT ask to find them on the internet. It will then truely be Plug-In-Play. Anyone have any experience to help us move this up to the next level? PS) Thanx Rogue for the Pat on the Back.

Ok Guys, This is new info and I will read inot what you guys are talking about kater tonight. But none the less I have Reached our goal with a very simple solution. Eric, you were on the right track but I was broad-sided last night with some interesting results. Here is what I have done... 1) I placed the INF in the $OEM$\$$\INF folder DOSNET.INF [Files] d1,usb100m.sys d1,extra.cab DRVINDEX.INF [Version] CabFiles=SP2,Driver,Extra [Extra] usb100m.sys [Cabs] Extra = Extra.cab TXTSETUP.SIF [WinntDirectories] 241 = "Driver Cache" [SourceDiskFiles] extra.cab = 100,,,,,,,241,0,0 usb100m.sys = 100,,,,,,,,3,3 usb100m.cat = 100,,,,,,,44,3,3 DriverCabName=Extra.cab,SP2.cab,Driver.cab [FileFlags] Extra.cab = 16 Then I learned that you also but have the New .Cab file in WinntDirectory 39 (\Driver Cache\I386) So, what I have been missing is the fact that if you have just the *.sys in (\Driver Cache) it will work fine like that. But if you use a .Cab for the Drivers then there MUST be a copy of the Cab in Windows\Driver Cache AND Windows\Driver Cache\I386. So tonight I am going to modify the TXTSETUP.SIF to try and copy the new Cab to BOTH locations. Otherwise you can use the $OEM$\$$\Driver Cache for one and then use the TXTSETUP.SIF to copy the other to the proper location. If either cab file was missing the OS would fail to find the driver. I founf this VERY strange. There seems to be something VERY important with the \Driver Cache directory when looking for Drivers. How does this sound to you people?

Hi, I Voted no but after thinking about it a little more, I think it would be a good idea. I have a full blown install DVD and also I am creating a Lite version on a CD for a basic install with good driver support.

Great Work Eric! Ok, I will take the ball and run with it today. I ran a few tests last night. I could not get Windows to look into the Extra.cab I made. The ONLY way it worked was to add the driver to /Driver Cache and the INF to \Inf. I remove ALL traces of USB100M.SYS in all the 3 main files we have been dealing with and then it stopped working. So... It seems we MUST have a reference for it no matter what in the TXTSETUP.SIF I think. Or, it might be the DRVINDEX. That might make more sense for it there. I will take your info and try some new installs today. Cheers!

Hey There, This all sounds very interesting. I think we might be on to something here. I tried to make a cab (Prior to learning about this program). My test did not work. It seems for any driver to install all it needs is the INF in the INF folder after the OS Install and the *.SYS in the \Driver Cache folder. THAT'S IT! So to make a Cab properly my test should work. I will test tonight. I made all the references to my "Extra.cab" ande the install did not kick up a fuss at all. I referenced it in several locations. I wrote them down but can't find them now. The file was placed properly with the other Cab's in /Driver Cache. Ok, found it. I Referenced in DOSNET.INF [FILES] D1,EXTRA.CAB DRVINDEX.INF CABFILES=SP2,DRIVER,EXTRA [EXTRA] USB100M.SYS [CABS] EXTRA=EXTRA.CAB TXTSETUP.SIF EXTRA.CAB = 1,,,,,,,39,0,0 DriverCabName=Driver.Cab,SP2.Cab,Extra.Cab Then I added the INF file to $$\Inf Does this look corrent to you guys? I don't think I overlooked anything. Install never kicked up a fuss so I assume everything was in order.

Yea, I saw what it was but I forget too. So, with the method I outlined you should be able to include ANY drivers. I am most concerned with Peripheral's and stuff like that. I would still like to persue creating an additional cab... something like Extra.cab and integrate it. I think Windows checks the cabs before asking to search for the drivers I think. Now, can you use Winrar to create a Cab file or are they SPECIAL Microsoft files. I know WinRAR can look into them an extract the files. Do I just create a new file and start adding drivers to it and then reference it like Drivers.cab and on XP Pro I think there is SP2.cab and something else. I am taking what I have learned about my MCE 2005 DVD and making a XP Pro DVD re-done from the ground up. That way I will be ready to go for 64-Bit when it arrives... YAAAAAA!!!! Anyone have any suggestions to improve on my methods?