GreenMachine

Remove WindowsXP-KB817778-x86-ENU.exe and you're golden.

Welcome, newbee47, to XPCREATE! As much as I wish it were not true .. XPCREATE is a very stupid program. No artificial intelligence, no learning as time goes on, no sound logic to determine which files my be more "correct". So, if it don't work ... there is most likely an error in the source files chosen. And if it don't work the first time, the second and third won't be much better, unless some files are changed. What we need to do here, is get the most basic XPCREATE CD to work on your system, and that is most certainly possible. From there we add modules until we hit a roadblock. It is always much easier to break something that works, than to fix something that is broken. So ... load the latest version in a clean workspace, run XPCREATE, and post the XPCREATE.LOG file. This file is only deleted at the begining of XPCREATE. It always exists after XPCREATE has run, either in the root of the working directory, or the NEWFILES subdirectory. This file has enough spies in it, that I will be able to find the incorrect files. In the nearly three weeks of this XPCREATE engine, the only code modifiactions have been in the logging / (user) error tracking modules. The problem is in the source files, not in XPCREATE. Post your log file, and let's go from there.

Good work, cram68. Further examination suggests that Kay's troubles may be due to previous hardware upgrades. When changing more than one "primary" hardware component (HDD, CPU, MB, and who knows what else ... ), the third change results in the afore mentioned error. So, if you're counting, this is strike one.

@cram68: Just take a look at Kay's conclusion. I'd say resign yourself to either an "inplace-upgrade", as linked to above, or, preferably, a nice clean unattended install. Well ... another one MIA ... looks like we lost Kay. Hope she finds RaveRod in her travels ...

Firstly, thanks out to MSFN for providing XPCREATE with this workspace. Secondly, thanks to you for visiting. More than Guidelines, I would just like to say a few words how I plan using this forum with XPCREATE. As far as Rules, the only one is to be nice. Certain threads in this forum I consider to be of the General Discussion type, that may touch on many different aspects of XPCREATE or Unattended Installations in general. Other threads I consider to be of the Bug Report type. In order to facilitate error tracking and correction, I will close a thread of the “Bug Report” type once I consider the problem solved, or abandoned. If you would like to re-open the thread, just start a new thread, and PM me about merging the new into the old thread. If you are posting about a XPCREATE problem, the more information you provide, the easier the solution will be to find. If the problem is during creation, a copy of XPCREATE.LOG is often indispensable in diagnostics. If lines appear in the XPCREATE DOS window that do not start with a timestamp, a copy of those lines is helpful. If your problems are at installation time, C:\WINDOWS\SETUPERR.LOG could be useful, as well as other log files found in the Windows directory, and screenshots of error messages. Welcome Onboard, and thank you for flying GreenMachine Productions!

Well, out of respect to 6 million dead, I think that is a fair show of concern and appology for an error that probably got some one's a** fired. Perhaps just a gest, but a very political correct one at that. I applaud the decision, as would my friends family with the little tattooed numbers on the forearms. On a lighter note ... it only shows with Office 2003 ... it doesn't bug XPCREATE!

Must have been a long week ... The reg key that controls the QuickLaunchBar is: (You probably know that ... ) The object is to get these settings into the registry at the right time. You should import from CMDLINES.TXT, or the values will be overwritten with the current values at shutdown, or use the more complicated REG hive load mentioned in the first post of this thread. My suggested solution ... On a working XP, setup the QL bar as you like. Reboot. Logon and export the reg key listed above. Use that reg file to import the key from CMDLINES.TXT.For some background info on the default user and CMDLINES.TXT, you can check out THIS and THIS page.

Sometimes ya really gotta dig to find stuff. 2 questions, Spheris: 1) Is it a typo on the startstate line, that there are no quotes? 2) Is there any reason this would not work from SVCPACK.INF? Sorry to blow the dust off ...

Awesome! Beautiful pic: I remember that stage ... eyes closed ... lots of sleep ... even the biggest scream was not enough to "disturb" ... Don't know why, but it always make's me think of my brother's saying: Kids are like farts - you only like your own. Anyway, FthrJACK, I hope you read this in a few days, after soaking up as much as you can of what is probably the best christmas you've had ... so far! And welcome to the group that can no longer sleep in on the morning of 25/12!

The Using CMDLINES.TXT link has been fixed. You only need $OEM$\$1\Installs if you use GUIRunOnce in WINNT.SIF, otherwise you can run your files from the CD. The C:\Installs directory must be deleted either manually, or from a batch file called by GUIRunOnce, or something similar. You won't find too much reading about CMDLINES.TXT, as there is not too much to it. It is just a text file with simple commands that will be executed at the T-13 point, where setup indicates that it will complete in 13 minutes.

Good work, XtremeMaC. So I would say that for those of us with the "mainstream" languages shoud be fine with the OPK. It is also quite a bit smaller than the redistributable.

Good point. Anyone remember? Downloadable multilingual versions would be nice ...

In the words of Pete Townsend ... it's a legal mater. The only version of DX9 that can be run silently is the OPK version, which is linked to on the MSFN guide. Though I am not sure, I have the impression that the OPK versions ARE localized: you need a different version for Belgium than for Greece. From what I understand, MS has removed the silent option to force end-users to accept the EULA (End Users License Agreement). Concievably, one could quite easily modify the setup program included with with the DX redistributable package, and repackage the files into a silent, switchless installation. Unfortunatly, I am under the impression that MS "frowns upon" this type of modification. For this reason, I do not distribute a solution. I do not know exactly where the DX9 OPK comes from, but there must be one for each language (if I am correct in that it is localized). Perhaps you could create your own with the DX9 SDK, link to on the MSFN front page, half way down on the left.

Once again ... I spoke too soon: I did not look at the first link you posted, and I thought it was an english to french translation, which is why I posted a French website. I thought you were french speaking. If you are looking for POE (Plain Old English) Aaron's guide should be more than enough: http://unattended.MSFN.org (Sorry Aaron ... ) I'm not surprised you could not understand it: those automatic translators are ... different

Suggested Reading ...

You should really set the taskbar (as well as your other explorer preferences) and export the file yourself. In any event ... here is mine: HKCU.REG

No, the reg tweak does not do that. The shortcuts are initialized by the corresponding programs (IE, WMP, Outlook, etc.)

Strange ... it is definitly OK for me, and I slipstream, and then call the hotfix from SVCPACK (as always ... ). Must be the slipstreaming that makes the difference. Maybe the engineers got bored at MS, since there was no December update, and they are playing with us!

I assume you mean Q810217, not Q810271. I have it slipstreamed with the rest of the Type I fixes, and it does not show up in WU, and it is in the registry with Updates (as in updates applied). If it still shows in WU, perhaps the fix is not applied if the Front Page Server Extensions are not installed, and the when WU does not see it, it says it is needed. This would be similar to the USB update: it does not copy the updated file (in VPC) because there in no USB support. But WU still says it is needed. In my case, WU looks at the files (which have been slipstreamed), and even though they are not used, they are the correct version, so no warning. ... just a theory ... in any event, I have not had any problems slipstreaming it into the distributions, as I do all the other Type I. And I am very surprised that this is listed as "critical" even without the extensions installed. Perhaps these bugs will mysteriously work out of WU, as we have seen others do!

I believe this is a case similar to the update 811114, which is critical, but only if IIS is installed. This may even superceed 811114, I'll look into it further. In any event, it is an update for the Front Page Server Extensions, which are not installed by default. I don't think many users here have selected to add that Optional Component, thus no talk about it. Your SVCPACK.INF looks OK to me. EDIT:: Upon further review: Windows Update now lists that update for me, as well, on a VPC session that did not need it last week. Go figure ... There is also a "new" recommended update listed: 826942, for updated WiFi.

My problem with Sun Java is that it insists on creating files and directories at the root of my user profile directory. I searched all over Sun's site off and on for a week, and could not stop the files from being created, or at least define their location, even though the documentation indicated it was possible. May have just been me, but it bothered me so much I gave up on it: which is a shame, because it would make sense to use the "original", maintained java. Anyone figured out a way around these issues? (I don't remember the exact files created, but I believe the names started with ".jp". I believe there was a cache directory, and a trace log). Do you still have these files in the newer versions? @Spooky: If my memory serves me correctly - it was over a year ago - I was able to have both installed, and choose which plug-in to use in IE. I would bet that the tool is part of the Sun/MS settlement.

It'll be back soon ... try this for now ... EDIT:: It's back ... (Il faut faire qqls chose pour cet avatar ... )

@shareef59: Bug # 1 - the DOTNETFX directory is not used ... harmless, but corrected. You should not need to repack any of the hotfixes or updates: XPCREATE will do that for all except DirectX9. DX9 OEM Preinstallation Kit switchless installer is linked from the Current Hotfixes page. For other applications that you repackage yourself using IExpress, the actual switches depend on the application you are installing: IExpress can be instructed to run silentely and launch the command line you specify. I have a couple of examples, but they are "down" for the moment, as I am restructuring the site. What are you planning on repackaging? MSJava: You cannot install the newer version of MSJava without previously installing MSJava. By combining the older and newer MSJava installers, a package is created that will install MSJava in one easy step, on all Windows PCs. (Thanks again, baliktad). The new version is named: MSJAVAWU.EXE. The old version is named: MSJAVX86.EXE. This is a script that performs the method described HERE I like the Green as well! Might throw a little red in there, just for the season! Good luck!

@stimpee: MDAC hotfix is now slipstreamed, and must be placed in it's own directory, which is named ... MDAC. 822603 can be run with other Type I hotfixes, though VPC will report it "not installed". You should get an ISO (not IMG) file. Let me know if the problem still exists. You do not need both the MDAC update and the MDAC_TYPE new version (2.8 - does not need a hotfix). You can now choose the source directory, CD or HDD. About what you are doing ... It will be interesting to see the combination of slipstreaming the hotfixes, and cutting down whole install. I would guess you are the first to use XPCREATE in conjunction with JDeboeck's scripts. You tell us ... One thing I will point out, that small distribution size was not a design consideration. The hotfixes, though slipstreamed, are still included in their "native" form. This will not effect the final installation size, but it will effect the distribution size. if you require even "lighter" slipstreaming, RaveRod (God rest his soul ... ) wrote up a nice Slipstreaming Guide. It is here somewhere. @shareef59: I think you could, fairly easily, package your IE install with IExpress into a silent, single file application. Do it once, and from then on install easily and simply, whenever, wherever. Put it in HFTYPE0, so it will install for all users (default user - propagated to new users). The download links should now be OK. If not, I messed up ...

Did someone wake me? Sorry, stimpee and shareef59, I'm finishing off a major update that will answer most of the outstanding issues. Please check back tonight. Sorry for the delay. Thanks