GreenMachine

@Marztabator: The bottom line is the same as the top line, except that it has been wrapped in quotes for the .inf file from which you copied it. When you wrap a string in quotes, and that string already has quotes in it, you double those quotes. In this way when parsed the interpreter knows that this represents a quote in the string, and not the end of the string. My line works fine. @willpantin: Thanks!

@XtremeMaC: The RollUp gets the normal HFTYPE1 treatment: it is nothing more, nothing less than a Type I Hotfix. Nothing will be overwritten, and it does not matter the order in which the fixes are run, as long as you include QCHAIN.EXE in the HFTYPE3 directory. (In short, it goes in HFTYPE1.) Do tell the results. Thanks. @visaversa: I looked into your problem from another thread, and you have too much stuff in the directories. I will write a detailed response to your post later tonight, and post an updated version for you to use, with your requested modifications.

I just created my first package from an InstallShield Installer, so I cannot profess to being an expert... Basically, you need everything that you find in the temporary install directory. This includes *.exe, *.bmp, *.cab, etc. Furthermore, if there is a subdirectory in this directory, I have not yet figured out how to make that work. HERE is an example repackaging Sun Java's 1.4.1.04 InstallShield Package. It will differ slightly, both in the names of files selected, and the exact command line, but I think you will be able to transpose it to your application with little trouble. As for pinning, the examples I gave are pages I put together, not threads. If you are interested, you can find all this linked from HERE I wanted to do this example with the latest Sun Java, but the install (a few Mbs larger) contained an MSI installer!

HERE are the steps to create a silent MDAC installation. This is basically the same as a WMP repackacking, except that the command line would be slightly different.

Can't remember if you need it, but do you have something like SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION near the begining of your script?

Eben: Your problems lie in using NON ENGLISH characters. Try either the short form (z.B. STARTM~1) or quotes (z.B. "BigUglyNonAmericanWordForStartMenu"). You may need to "find" the correct version (STARTM~1, STARTM~2, etc) Viel Glück

1) I mean no disrespect, but I am not sure about the extras in those installs. I have not figured out a way to add this command line (with the quote character) anywhere convienient: that is why I repackaged it. 2) You are right: the deployment kit wraps MPlayer into an MSI file. I guess we can wrap that with IExpress... 3) IExpress can be used with about anything: it is not limited to MS products, nor .msi files. I would go with the WMP & MM2 combo for simplicity... Hope that gets you "burnin'" again!

@pmcx9: That's an answer I can respect. I think the tick means that the password never expires for THIS USER, where as the command is a global setting.

No prob: I get blind spots often. The command you should use for the hotfix is: Q823718_MDAC_SecurityPatch.exe /C:"dahotfix.exe /q /n" The command you should use for the 2.8 update is: MDAC_TYP.EXE /Q:A /c:"dasetup.exe /q /n" This are the commands you would use to run silently from the command line. They go in the top line. The next line is just another command line you can run. I doubt there is any difference between them, other that one is first, the other is second. I think the problem is that one expects IExpress to be more complex, but all it seems to do is package some files and a command line, extract the files to a temporary folder, and run the command. You may want to just install MDAC 2.8 instead of the hotfix.

@RoyalBox: Funny thing, I almost never notice these pinned threads. What I have listed for HFTYPE0 is a repackaged version of MDAC 2.8. To repackage it, I simply wrapped it with IExpress, and pass it the command line, resulting in a silent and switchless installation. The main reason I did it this way, is that I could not find an easy way to pass it the command string, which has the quote character in it. I could get the quotes into neither SVCPACK.INF, nor CMDLINES.TXT, nor [GuiRunOnce], nor RunOnceEx in the registry, and I'm trying to remove everything from the .CMD scripts. GuiRunOnce may be the best place to call it - through a script- as it may go faster, but I just grouped it with the rest. The only reason I use Q817778 is that my objective is to have all hotfixes, critical as well as recommended, up to date. If I don't do it, I know some user will ...

OK, I'll see tomorrow. If you are experimenting tonight, you could make these two modifications: ECHO Expand the CABS into working directoriesbecomes: ECHO Expand the CABS into working directories GOTO SKIPCABSand REM If there were any uncompreesed versions of these files, update them as well.becomes REM If there were any uncompressed versions of these files, update them as well. :SKIPCABSThis will NOT create the cabs. That should not matter, as the files un-modified files will come from the cab, and all the service packs are sill run to update the current versions. If this works, and the exact same this with out the modified code causes the error ... bingo: it's the cabs. I'll be around later, so please post any preliminary result, and thanks for YOUR help.

Certainly sounds like a bum or missing switch somewhere. Check that all the hotfixes with blue and white icons use the /Q /U /N /Z switches, and the other use the /Q:A /R:N switches. 817778 should block you if it is in error: not with a browse for extraction prompt, but with an error message. (Looks like someone else has got it working from here, so my theory is kinda shot...) I have also noticed that even when in error, 817778 shows as installed (the error is at the very end of installation). Are any updates installing? Do you see something else happening at this stage?

You need the long switch for WMP9. The WMP9 & MM2 combo was downloaded from MS OEM site, as well as the DirectX. The WMP9 is simply the web version. WMP9 & MM2 was created by MS, but you can use the Entreprise Deployment Tools (don't remember where to get it...) to create a similar package, adding things to WMP9 like updates and hotfixes, MM2, TweakWMP as well as preferences, and it is not very difficult. Someone with a french or dutch flag started a thread on that subject, probably 5 pages back at least. I make execs similar to these, using the same tools, (IEXPRESS).

C'mon you lazy dogs: Almost everyone here knew the answer. How come it needed forty views and an administrator to get a simple answer? This switch does not effect the file copying. That is OEMPreInstall.

I was not being sarcastic, and now I am jealous. I don't remember so well: I played with that update for a couple of days, and it never worked right. Do you do anything special? Have you slipstreamed SP1 or SP1a? Are your hotfixes installed in any special order? Is this one near the begining or the end? Are you using the standard SVCPACK.INF method outlined by Aaron? Is there a clue you can give me as to why you can do it, and I cannot? XP Home or Pro? Corporate, retail, or OEM? Has anyone else got this working OK? I have only seen problems with it here.

Funny how easily I become dependent. Can we get them back again, again?

@visaversa: PM me your WINNT.SIF, and any other files you add when using the XP Creator script (less the hotfixes and service pack), and I will see if I reproduce it on my machine. I doubt it has to do with the repackaging itself, but perhaps the contents of a cab. Also, if you can print out a complete directory listing BEFORE running the script, that may help. (DIR /S > LOGFILE.TXT). If this is too much to mail, you can put it on a server someplace and sent me a link. Perhaps someone knows what is happening at T-25 during setup. Anyone?

Don't mean to burst your bubble, but I like this method: NET ACCOUNTS /MAXPWAGE:UNLIMITED

I would like to see this: [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600

Strange, I have no idea why I had the Jet SP7 fix there. I must have needed it at one moment or another. now it is gone. However, this morning WU did tell me I need 829558, and that is on a fresh out of the box installation. I do all the recommended updates as well (don't ask ...), so perhaps this is a critical update to a recommended update.

'Mal hin gucken: CMDLINES.TXT

I would say that is the culprit. I don't use VBS files, so I don't know how the interpreter treats them. CMDLINES.TXT does not copy anything, unless you do it explicitly from your batch files. However, it makes more sense to me to leave the install files on the CD if you are installing at this point, and in that case you would perhaps be better off ejecting the CD as your last command, not your first. In terms of setup itself, there is no difference between ejecting at the begining or end, and if you do it last, you will know that you have CD access till the end. This may be important, as the current directory when parsing CMDLINES.TXT is <CD>:\$OEM$. I use uxtheme.dl_ that I downloaded here somewhere, and just put that into the I386 directory before creating the CD. This avoids the on the fly copying (which I have never tried)

All done. Thanks, DaveXP. That is just the MDAC 2.8, repackaged with IExpress. Nothing fancy, but it works fine. It is about 5.3 Mb. Eliminates the need for the 2.7 patch as well.

Wait for me and MDAC! (You see what I meant about 192.168.*.*) Loading ...

Good eye! I was in the middle of updating that page when I loaded it last night, and said to myself, "Nah, no-one will see it" Yes, I am in the middle of changing it, but I will not post it until it is where I like it. I will use the same HF1 & HF2 directory structure for including hotfixes that are to be run from the RunOnce section (i.e. 817778, which works no where else). Other additions include a directoy to add users: any file there will result in a user with password=username, both normal and administrator, MSI silient installation directories, etc. It is about 95% now, but testing is slow - start VPC at night, check in the morning. I thought about splitting into sections, and decided not to. I want to start from known conditions every time. I do not like the idea of re-slipstreaming, so I want to start with the CD files each time. This is not the killer: the time consumer is the MakeCab re-packaging of DRIVER.CAB. 26 minutes on my PIII. Furthermore, I see no need to re-run the script after the hotfixes are in place, unless a new hotfix comes out, and then, as I said, I want to start clean. That said, I use the resulting CD layout, in the CDROOT directory, to make any modifications I desire, and then simply run the MAKEISO.CMD file to create the new ISO in a few minutes. I don't really see the conditions where this solution is not sufficient, but you may. Perhaps when I get really motivated I will allow for a few parameters to be passed, that will jump to certain entry points. I'm glad that you modified the code to make it work as you like. I tried to keep the code clean for just that reason. True, I do prefer not to have it public if I am going to have to answer for it, but it is no big deal. No reason not to use SR1. I insist on the fact that this is just a large hotfix, nothing more nothing less, given a fancy name to sooth the masses. You must have also noticed, see-er of all, that the hotfix numbers where hot linked... Thanks for the research and coding: I just cut and pasted your list. I will update the documentation later tonight. Last note: I have no idea about the BSOD. I have not seen one for weeks. Nor have I tested SP2.