Complete advice for beginners?

[Sulfurious]

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.

[Dynaletik]

At the moment I use Windows Post Install Wizard to install my applications. You only need AutoIT for those programs that do not have silent switches etc.

[Sulfurious]

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.

[MHz]

Do RunOnceEx.

You will learn more, with this method, then the GuiRunOnce method. It does batch scripts, as well as registry methods. Autoit can be also used for any or all of it, whether using gui or silent. Autoit with silent installs, can cope with any issue, like popup windows etc with ease. And do not use the $OEM$ for your installers, it is a waste, install them from cd, using the cd letter find command, in the help guide.

Once you have done an unattended like this. You will have learnt some good basic knowledge. Then you could use one of the 3rd party utilities to make another disk, for other reasons.

[Sulfurious]

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

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\zz110]"1"="C:\\Install\\DirectX9b\\dxsetup.exe /opk"

"@="DirectX 9b"

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.

[Ctwizzy]

I second WPI. Use WPI to get a general feel of how things work, when you want to get more into it switch over to RunOnceEx.

[Sulfurious]

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.

[Sulfurious]

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.

[Ctwizzy]

WPI just does its own thing. Open up config.js to see your entries.

WPI is a sluck GUI interface for uA, and you can also customize the way it looks.

Most AutoIt Scripts have allready been created, and there are very few apps which need it anyways.

VB - Dont bother. VB is powerful but as of next year MS is no longer supporting it. Learn something that might be around for a little while longer (WSH - JS/VBS).

Seems like your trying to run before you can even crawl. Making a uA cd takes time patience and a lot of testing. Dont rush it or youll end up spending 99% of your time debugging when you should have just took it slow.

Good luck

[TheeBeets]

At the moment Im using Wpi as Im making a Dvd with many applications and it gets it a sleeker look but if I knew exactly what I wanted to install I would use Runonce but it's all about personal choice. Trust me making a disc honestly isnt as hard as you would think

[Coolsights2000]

I can't believe you are all still pushing that use the runoneEX style...

INCORRECT way to do business you need to install programs on the other side from the HKCU run...

As far as advice to you get another hard drive to play with...... and try the stuff ..... find what you like best.......

Not all programs are created equal... so you will have to figure out where it likes to be installed at....... some you can just copy the folder and run the program... some have to install then enabled..... some can be enabled from the silent install with some files and register keys.......... AND THERE ARE SOME PROGRAMS that DONOT support a silent install so don't even do it that way......

I'm injecting stuff into the hive setup myself.........

I also use the cmdlines.txt to do the presets..........

I use the other files that comes with windows to set up the unattended and install the updates, in the SVCPACK.INF

Then I switch on the hidden default desktop ....... and do my silent installs from the HKCU run........ ALL ACCOUNTS are created from the hidden profiles,, Hard to explain it here,,, once you create a profile no one else will get what you install... LONG story once you understand how the register works you will go DOH.....

the hidden profile is like a cd player tray that has a cover over that CD .. once you go past the first install and create a new user a cover goes on and it never gets changed...... I take the plastic cover offf....... So now any users profile you create gets all the settings,,,,, EVEN the admin acounts is B.S. I have a thread some where explain this...

I have been playing for a long time on and off at this and I change stuff around all the time........

As a bonus get a extra hard drive to play with .. I run moble docks,, and use nero with some DVD-RW

NOTE

The Biggest thing is read the post here and say thanks you for your input,, I read and play then keep what works the best for me........

Pick a topic and do a search then play.. I have found allot of good stuff by doing a search here Allot of my silent install on how to are from here for example like the netfx sfx package.. etc etc,,,,,,,,,

Enjoy Mac!

P.S. you will never be done cause I never have had a week that something didNOT have a update... So if you update like I do you will need to use a RW....

[Astalavista]

Seems like your trying to run before you can even crawl. Making a uA cd takes time patience and a lot of testing. Dont rush it or youll end up spending 99% of your time debugging when you should have just took it slow.

I agree completely dont try to run yet...

unless u have a good mentor or tuitor. Right wink wink.

[Ctwizzy]

LoL, Yeah I got lucky. One member (cannot disclose names to avoid them getting barrarged with pm's) helped me out a ton.

Most of the members here @MSFN are real nice and will help. Just search first, look over the advanced search options as well. 90% of all problems can be solves with a search.

Good luck

[Sulfurious]

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.

[Sulfurious]

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.