Sulfurious

Fascinating. That would explain a few things. I always created a new admin account because I noticed that what I installed on the default one would not neccassarily show up on futute accounts. Now I understand why. Very nice. Some questions though. In spending every spare evening on researching this stuff, I am leaning more towards learing the .inf stuff. Can someone clear a few things up for me? If I use winnt.sif and the guirunonce can I use .inf files? If I use winnt.sif, not using guirunonce but using runonceex instead, can I still use .inf files? I can see the differences between the guirunonce and runonce methods, and I can see how using an .inf can put reg values in or out, and how they can be installed by right clicking on them. I haven't found the thread yet that tells me this: Do I edit the default hive .inf's on the source cd at all? Or am I using cmdlines.txt to call the setup.inf? I know both will work, and I see that a lot of threads show many different .inf's for different purposes, such as killing services. Am I calling a setup2.inf from the cmdlines.txt file, and then a setup3.inf after that? Soooo much info here, and the threads all have 75+ posts. Takes a long time to dig around, and after the first 3 or 4 pages of the thread, I am heading down a different trail. Is there a MASTER thread on the different methods of using .inf's and the proper sequencing? I have resorted to copy/pasting a LOT of this site in an attempt to put some order to all these bit's and pieces of examples. Oh well, at this rate another 3 or 4 weeks and I should have it compiled enough to see what each method does, when to sequence it, and some basic examples of them and thier diffences to couterparts. Not that the guide isn't good, because it is. I just need to know a bit more. A control freak to absurd proportions I am. Why. Why. Why. Curiosity killed that cat and all. Sheesh this is a huge site, and a huge topic. Sure am having fun tho. Thanks for any new pointers. sul.

This is what I was referring to. Swithcing on the hidden default desktop. Perhaps I just missed the thread that spoke of this. Are you talking about the admin desktop? I don't understand, but I am curious about it. sul.

Okay, so here is the summary I have come up with. Bearing in mind that the guide give the specs, or Goshs website for the .inf stuff. INF METHOD step1: create file runonceex.inf--put in i386 dir step2: edit txtsetup.sif and add "runonceex.inf=1,,,,,,,20,0,0" (makes runonceex.inf copy to %windir%\inf) step3: also add to txtsetup.sif "AddReg=new.inf,newhive" step4: create file new.inf--put in i386 dir step5: edit txtsetup.sif and add "new.inf=1,,,,,,,_x,,3,3 step6: edit dosnet.inf and add "d1,runonceex.inf" and "d1,new.inf" step7: if installing xp, edit new.inf and add extra entries--if new.inf is even needed. May not be needed at all. This should now add all entries to runonceex and on first logon will start executing installations. OR CMD METHOD step1: create winnt.sif, with NO [GuiRunOnce], but all other desired entries step2: create cmdlines.txt save in $Oem$ step3: create RunONceEx.cmd save in $Oem$--populate with install strings OPTIONAL step4: include for-do loop in RunOnceEx.cmd to assign cd drive letter (for installing apps from cd) step5: create blank text file on cd root for above loop step6: place app installs in custom dir step7: edit RunONceEx.cmd,replacing %systemdrive% with cd variable and set app install paths to custom dir Okay, so how is that. Another question. All these files that are being created, most seem to go in OEM for the CMD version. If I change the app dir to something like "software", do the runonceex files stay in the OEM, or can they go into the custom app dir? Same goes for the .inf's. The syntax in the examples appears to point to an \apps directory. Can any of these inf's be put along with the apps? Or do they have to live in a specific spot. Feel like I am getting a bit of a handle on it. Seems like the .cmd method is easier, syntax wise. Thanks for any help. sul.

Right. On VB, I own no other type other than scripting, so for access interface, at the moment I am stuck. Not so bad I guess. .net doesn't look too disimilar. As for running before walking, umm, I am sort of jogging here. I have already slipstreamed sp2 and ryans package into my source. Works great. I have absolutely no problems with adding my own regs. Matter of fact, this all started when I decided to collect all of my little tweaks/edits/etc and put them into a database so I could make a batch/regentry file to do that. I use taskkill and stuff to do different stuff. I can usually extract out a programs reg entries and do a copy/paste adding those entries to get it to work. But, with more and more stuff going to msi installation, seems the reg entries are scattered about. Really make it tough to gather, and a lot of them are in places unique to this computer, guid's or something. So, seeing that I could actually include some installs in the setup really tweaked my curiosity. Except it is somewhat confusing. WPI seems to be a mesh of something like safexp, nlite and a prog I used to use called AutoMenuStudio. Coolsights2000, you gonna keep that reg entry for the master profile to yourself? Or, at least what do I use for a search criteria. I figured that most of these would go under the all users or default users profile as there is only one account for me. extra harddrive???? lol. I have 4. And I have xp on 2, 98se on one, and am messing with ubuntu (linux) on the other. My plan was to install the tests on the slave. So then, as a consensus: To start this little roadtrip--just stick with wpi, or try runonceex, or inject hives, or guirunonce. Not that I can't just do one, but I am trying to let other's experience guide me a little bit. Why do a bunch of work on something that most others have figured out is restricted. Maybe I just need some more coffee. Again, thanks for replies gents. sul.

Okay, WPI is cool. Already edited the program list a bit. A question though. For the sake of learing this first, is there a way to view my options like an .inf, or does this program keep the stuff to itself and just run my options at install. Not that it won't hurt to edit this one up, but if the end result is going with .inf files, would like to use this to build those so I can see what it is doing. Maybe I just need more coffee. Or maybe I should stop trying to learn vb, autoit, js, vbs, access crap and unattened installs in the same week. Sheesh. Or, maybe I should just drink more coffee:wacko: sul.

Okay, think I got it here. The .inf method seems a bit more complex, but offers more methods. The .cmd is just adding reg entries to the runonceex key, essentially still a batch file. Then the run once event fires each entry, which happens to be installation calls. So, the .cmd file is pretty straight forward, add the key which installs the app. Maybe using the winnt.sif to further enhance some install options, and then using something like nlite to even further tweak stuff. Or, using some .inf files to have more options on what to tweak, having more control over registry settings, and in general being able to do things that a .cmd cannot or is difficult. And the addition of using them like a template, as well as correcting the original microsoft .inf's from the source cd. Sound right? Sounds like going .inf may take a bit more to master, but appears to offer more. sul.

Good advice. I have been plunking with that guide, and it mentions with the runonceex to make a runonceex.cmd file, and then gosh's site on learning runonceex calls it a runonceex.inf. They look totally different. I sorta see the logic behind it. Add regkey entry for runonce, passing the parameters of what to install with what switches. And then a thread from DaveXP, with a code snippet that says Looks like runonceex again. I am not confused exactly on what to put into the file, just which file type exactly to use. And I did read up on that installing from cd and not using the OEM folder, which is definately the way to go for me. Any insight? sul.

Yeah, nlite is tough. Wished I had found that long ago. I have a bunch of batch files that attempt to set a lot of preferences for my reinstall. And friends are always wanting my tweaks (helps to do your research). So, I am excited to have a tool that I can slightly tweak an install for someone who doesn't know much, and really give a hard tweak to someone who does. Beuty part is they install it with thier key, and they don't have to do a thing. Very cool. Oh, rock on with opera MCT dude. It rules....by far. sul.

OK. I will check that out. Maybe I need to rephrase my prior question. After reading a bunch of stuff on this forum, I gather that either way of installing programs will work. Whether it be runonceex or not. However, CAN either be used in most every circumstance, or is one limited in some fashion, therefore making the other the 'defacto' standard. I guess that is what I have not found. Both appear to work, but from you guys who have tried both, which seems to be the all around champ? sul.

Hey. I have browsed the heck out of this sight, and have read a lot of threads and tutorials on an unattened install cd for xp pro sp2. Still a bit confused as to which method of installing apps and such is really recommened. Some state batch, some like runonceex. I know a bit of batch, and scripting is just something new to learn. Which one, for strictly sp2, is really the best "overall" choice? And, should a program not be able to install with one method, can I still use the other? I am more interested in getting all the apps I always put on a machine to be pre-installed. I also read about AutoIt and InstallRite. Are these still needed with the runonceex method. Is there a thread (I did not see it if there was) that gives a synopsis of the different methods, do's and dont's, will's and wont's? Not that I need to be directed to the threads that acutally tell me how to do each one, I have seen those. Just something that will let me make the decison on which one to focus on. Thanks for any help sul.

Stumbled upon this forum after finding nlite. I had no idea there was so much I could do with an xp install. I have been using ghost with great success for years, and for a quick restore it would still be better. But this stuff about slipstreaming updates and installing software has me burning the midnight oil. Sounds like a lot of fun. see you around. sul.