bilemke

well just returned.. voted... Anyway, something not so critical I have been trying to figure out in all the sp2 betas... When I slipstream, the new autorun exe for sp2 has the option to install .net framework. Problem is, when I click it, it doesnt do anything.. Never has in any build.. Not a part of windows technically (optional component on the cd), but anyone have any comments to that?

oh how exciting I cant wait.. must fight... the temptation.... to format my... my drive.... a:\>format c: /q ........... Nah.. I can wait. haha

I am personally making two setups (AIO of sorts). One with all the updates slipstreamed, and one original cd with the update isntallers on it with a batch file to run them all silently. I do this only because after slipstreaming (because of admin install) you no longer get benefit of local install cache like the retail/stock cds.

very nice post.. however, you can update the Office Web Components with the other files in the office 2003 sp1 isntalelr. ie.. OWC11...

True. Slipstream got me thinking slitpstreamed vs stock iso image.. I see, you were refering to a disk image as in preinstalled like ghost.. If you have a volume license vs of windows or still using 2k, I would say a disk image should work fine. Windows will handle most of the differences in hardware that could come up by redetecting hardware. I personally like a very clean install, as in windows only sees (or has seen) my hardware in that particulair machine. It is the same reason I hate upgrading windows from one version to another. Much cleaner install in the end, not left overs of the old mixed with the new.

Slipstreaming really is only adding updates (service packs, and hotfixes), integrating things to the level discussed in this forum and others (drivers and programs etc) is much more then slipstreaming. I have had this debate too. Several of my friends use the same cd i create and use their pro key. So I only make improvements to the cd, not so much customizations. General things agreed apon to be good. Like disbaling services by default (ie... Messenger). I add drivers for core components like raid controllers need to atleast get windows installed, but not sound, video or network. Those things change way to often and are much larger. Raid drivers change, but not nearly as much.

hmm.. it might actually be posible.. my external firewaire hd is seen in text mode setup.. it i will even let me try to install to it.. maybe thats too different though.. i am not a fan of usb storage.

I just tried something I posted in this thread Here. I can use added raid drivers from cd or from files copied to hd via oem folder or other means. This can be done with or without unattend setup and still allow you to load more drivers via f6 if you have not already integrated them (or if newer comes out and say you dont have the time to integrate the new ones?). This is a combination fo the M1 method of integrating drivers and the great little tool Pyron made (look to first post of the thread above). Repeat from my post in that thread: 1. Modify txtsetup.sif similair to method in M1 setups described in thread here and Microsoft KB article here. This should take care of text based portion of setup. 2. Follow insctuctions in this thread for using Pyron's creation. This should take of the gui portion of setup.

sweet.. if you can show me how you got 1.0 working i might be able to make needed changes to 1.1

without knowing what you mean by "cant delete them" (i assume it say access denied), you may need to change the permisions on that registry key to allow you to delete it.

Hmm. this thread got me searching.. GreenMachine pointed to http://support.microsoft.com/default.aspx?...kb;en-us;817616 Microsoft documented modifications to txtsetup.sif. I beleive they intended this for only adding support to the recovery console. This shows a relationship to the M1 methods. However, another thread in this forum points to http://support.microsoft.com/default.aspx?...kb;en-us;817616 Now Microsoft describe driver integration (not the recovery console) in particulair. This is almost exactly how both M2 methods work. Thus I beleive (like Compaq/IBM example mentioned) this is the official way to integrate the drivers. The M1 methods produced here, will work, I don't see a problem with most drivers as the difference in the M1/M2 methods is very minor. A added benefit to the M1 method is if you use the cd produced from it to install the recovery console on your system, it should have support for the raid/sata controller already. A cd produced using the M2 method would fail as I do beleive the unnatend info is not called in to play when install the recovery console. I rarely use the recovery conolse so I can not veryify this (use windows pe, BartPE).

Interesting summary page.. I note menioned by trainee... This would be ideal, right now even the best integration requires some hack job of a unattended install.. Even chaning registry entries to point towards folders full of drivers. Before trying using a unattended install almost a year ago I had done enough modifying to the windows install to install promise fasttrak tx2000 drivers. It was so seamless that windows did not notice the files were different then the rest of the stock/retail files(note, were WHQL drivers, so no issues with unsigned drivers). I did not nead a floppy or any unattended file. No modified registry entries in hive files or anything. Involved editing txtsetup.sif and one of the main stock windows driver inf files.. like scsipnp.inf I think... Anyway, besides that, just added primary .sys files and I was off. It worked regardless if any unattend option was used or even if a unattend file was present. Problem was when I tried to expand the technique, it partially failed on drivers from almost any other manufacturer except promise? To this day, from when I switched to OEM/Unattend methods described here, I have searched for a method close to the one I described above. One that would work with or without unattended setups. Further note, I could hit f6 and put a floppy in with a driver for the same hardware, and setup would ask if I wanted to use the "integrated" drivers in the windows setup or use the ones from the oem floppy.

I think i may have asked before.. not sure.. I have tried int he past to get the .net frameword to isntall using the netfx.cab that is present on xp sp2 cds in a pro (corp/retail .. whatever) or home install (not mce or tabletpc). netfxocm.in_ (netfxocm.inf) is what does it for mce and such, but it only is called on for those two variants of xp, not home or pro. This would prevent the need for a seperate redist isntall being placed on the cd. Only alternative, tried and worked as documented by many others in this forum, delete netfx.cab and put redist installer on cd and call from one of the many unattended install methods. Any ideas anyone?

Hey, easy way to make inf formated registry changes.. Use WillyPad to convert standard regedit exports (reg files) to inf. Been using it for a while but keep forgetting I have it. I have downloaded the thing about 5 times in the last 6 months after researching a way to make inf based reg files easier.... Check it out, freeware, sorta... WillyPad

Not to downplay what has occured in this thred, but i think serialz wanted to achive something different. all that has occured here is to change the source path for the oem pnp drivers.. Still requires unattended. Do it without unattended and i would both be impressed and excited. I have done it for ide controllers. But the driver can only be access during install of windows. If you add hardware after windows boots the first time, it doesnt see the added drivers correctly so you have to point it to the driver files.