[GreenMachine]

The "Old" XPCREATE has been officially retired, and the "new" XPCREATE is here for all. All of the bells and whistles of earlier versions have been removed, and will be considered for addition only after this streamline version passes all of your tests.

Also gone is the user interface, and for the moment XPCREATE is run from the command line, or clicking on the program itself. Any user specific parameters are found in the XPCREATE.INI file, along with explanations of their meanings. AutoUpdate has also been disabled in this version. You will need to manually download your hotfix files, and place them in the correct directories.

The web site has been updated, and trimmed, to correspond to this XPCREATE version. There is not that much there, so please have a read before asking questions.

The "old" XPCREATE is no longer available for download, and I will be neither answering questions about it, or modifying it in any way, so please don't ask. Your suggestions for the new version are, as always, welcome and encouraged. For this reason the old XPCREATE posts have been merged into a single thread, and the thread has been closed.

AaronXP and MSFN have set aside this seperate forum for XPCREATE. For that reason I no longer ask that you post all your questions in one thread: go wild! If you do not find a thread with a question similar to your's, start a new thread.

[SoreGums]

Dude! I was like "wtf where's it all gone :S" (I just discovered the Slipstream wizbang intergrate everything XP setup cd's 8 hours ago, and XPCreate 1.5 hours ago)

Then I discover its all being redone!! How awesome is this, what timing!!!

Your project in combination with the MSFN guide is exactly what I've been looking for for quite sometime. (known about these things for about 2 years now , I've just finally decided to figure out how to do it.)

Well looking forward to this new version!

Question: this new version going to have an option to use a SP1 CD all ready as I've got a Dell OEM XP SP1 cd. I was trying to figure out the options in the old xpcreate . . . but the new version is here I'll just wait and see what happens.

[GreenMachine]

This is the Total Control Version: If you don't want or need to slipstream SP1, just don't add it to the lot, and you're fine.

Welcome to MSFN, and Good Luck!

[Wraith]

Yay. Big new releases all around.... time to give her a go ;-)

[pulpfixtion]

Can I ask why you did away with the old version. I personally thought the GUI and web update was a dream.

[techtype]

Just made a CD with this release. It worked fine!

[pulpfixtion]

Can you add a link here to this release please
many thanks

[Alanoll]

why must he add links when the links are on his website?

Just click the big XPCREATE in GM's signature

[ColMaki]

@GM:

Great work and many thx for the hours put into this version. I have to say that I found XPC by chance, and since then I'm hooked to unattending.

[GreenMachine]

@Wraith: Why do you think you were in on the testing? I wasn't going to post if it didn't work for you, not after last time ... You should be OK, the slipstreaming engine has not changed since.

@pulpfixtion: As Alanoll said, the links are on my page, linked to by my signature. If you have signatures disabled, you can simply use the WWW icon below the "missing" signature. This is not to draw traffic to my site, but to avoid leaving dead links on these pages.

@techtype: Aren't you getting bored again? First time, every time! Get almost all of it in before the reboot: I know you like that!

@ColMaki: Thanks, and your welcome!

As I said previously, this version seems very solid. In the last weeks testing, most all of the failed creations were results of incompatible hotfixes, updates and installs. SATA drivers are integrated by default, and having supported drivers in the $OEM$ directory tree is enough to trigger SATA integration. I'm interested in hearing if anyone has had any success or failure with this.

I have also been testing XPCREATE with Windows 2K. The results are as expected: XPCREATE is Windows 2K compatible in nearly all aspects. Again, the key is determining the correct hotfix/update combinations. As IE should be updated to IE 6.1, all critical updates concerning IE/OE cannot be slipstreamed, and cannot be applied before a first reboot, when IE 6.1 is in place.

I am still finding eratic behaviour installing IE 6.1 via an IExpress package called from SVCPACK. Specifically, it appears that the install fails as it is unable to contact the IE file server, to check for missing files / updated files. I will probably post a thread looking for answers in the Unattended Forum if the mystery continues. If you have any experience with this, or IEAK installations, and you know how to prevent this behavior, please let me know.

[prathapml]

Use the normal methods (winrar SFX, or iexpress) - extract the entire IE6 SP1 setup files into a known place, and run this command, for example:

%systemdrive%\install\MS\IE6sp1\setup.exe /q:a


That works for me (none of that wanting to connect somewhere, its standalone) - adapt it to suit whatever method you use to automate XPCREATE.
GM, I'm sure you've tried that before.

[mdes]

@GM: Thanks for this new release, it is working fine except for the following:

• Q327979: Parameters error at T-13 (very strange because the generated SVCPACK.INF contains "327979.EXE /Q /U /O /N /Z" which seems correct!?) EDIT: I'm really stupid, I put this HF in HF1 AND HF2
  
• I put INSTALL.EXE (Messenger) in SVC-WMS\ instead of MMSSETUP.EXE.
  
• I didn't put MSXML V3, V3 SP4, V4 SP4 updates, MBSA Setup; and I started from WinXP+SP1.
  
• But I add then DotNetFx langage pack in SVC-X2M, MSJAVWU & Q820223 in SVC-HF2

Windows Update shows me only:

• Messenger 4.7
  
• 817778 (I tried to put it in SVC-HF1\, but I got a lot of errors at T-13).

Edit: It seems I put a shortcut to Install.exe
So, except for 817778, everything seems to be OK

This post has been edited by mdes: 19 February 2004 - 12:02 PM

[GreenMachine]

prathapml, on Feb 19 2004, 04:17 PM, said:

... %systemdrive%\install\MS\IE6sp1\setup.exe /q:a ...

Funny, I didn't try that. I was caught up in the switches defined in the IEAK guide. (/S:""e#"", etc.) But that one looks fine so far, though I have only tested on VPC. Thanks!

@mdes: That's as good as it gets, just the 817778 missing. Note that INSTALL.EXE, the WIndows Messenger 5 install, should go in SVC-X2M. SVC-WMS will only work with the 4.7 update. Also, the Current Hotfix list is ALL those I have tested, and not all are needed. In fact, certain combinations are redundent or conflictual.

[benthos]

Great work GreenMachine...

Worked flawlessly with XP PRO English.... (save of course for 817778)
Currently trying it with XP Pro French and then will try Home in english and french.

[GreenMachine]

Cool! You might want to look at mdes' post about the language pack and the Q820223 update, otherwise the French update set is the same as the English set. As for Home/Pro, I don't think there are that many different. There is the Help File Update.

Good luck, and let us know how the Home version goes.

[Wraith]

GreenMachine, on Feb 20 2004, 01:47 AM, said:

@Wraith: Why do you think you were in on the testing? I wasn't going to post if it didn't work for you, not after last time ... You should be OK, the slipstreaming engine has not changed since.

Heh, was just messin'

I needed to make a new distribution anyways, so what else am I gonna use if I'm lazy?

[Sunil]

works like a charm

[mdes]

My files (FRENCH) for WinXP+SP1:

-NotIncluded\SVC-HF1\WindowsXP-KB817778-x86-FRA.exe
             \SVC-X2M\install.WindowsMessenger5.exe

BOOT\XPCTBOOT.BIN
FILESCD\I386\WINNT.SIF
SPACKS
SVC-DAH
SVC-DAS
SVC-EXE
SVC-HF1\Q322011_WXP_SP2_x86_FRA.exe
        \Q327979_WXP_SP2_x86_FRA.exe
        \Q811114_WXP_SP2_x86_FRA.exe
        \Q814995_WXP_SP2_x86_FRA.exe
        \Q815021_WXP_SP2_x86_FRA.exe
        \WindowsMedia-KB828026-x86-FRA.exe
        \WindowsXP-KB810217-x86-FRA.exe
        \WindowsXP-KB810243-x86-FRA.exe
        \WindowsXP-KB820291-x86-FRA.exe
        \WindowsXP-KB821253-x86-FRA.exe
        \WindowsXP-KB822603-x86-FRA.exe
        \WindowsXP-KB823182-x86-FRA.exe
        \WindowsXP-KB824105-x86-FRA.exe
        \WindowsXP-KB824141-x86-FRA.exe
        \WindowsXP-KB825119-x86-FRA.exe
        \WindowsXP-KB826939-x86-FRA.exe
        \WindowsXP-KB826942-x86-FRA.exe
        \WindowsXP-KB828028-x86-FRA.exe
        \WindowsXP-KB828035-x86-FRA.exe
        \WindowsXP-KB829558-x86-FRA.exe
SVC-HF2\hu1002_pro.HelpUpdate.exe
        \js56nfr.JScript5.6Update.exe
        \msjavwu.exe
        \q330994.OECumualtiveUpdate.exe
        \q820223.exe
        \Q832894.IECumualtiveUpdate.exe
SVC-MDC\FRN_Q832483_MDAC_x86.EXE
SVC-MSX\HMTCDWizard_FRA.exe
SVC-PRE\DX9.EXE
SVC-SWF\swflash.cab
SVC-WMP\MPSetupXP.MediaPlayer9.exe
SVC-WMS\MMSSETUP.WindowsMessenger4.7Update.EXE
SVC-X2M\dotnetfx.exe
        \langpack.DotNetFx.exe
        \mm20fra.MovieMakerII.exe
        \setup.JournalViewer.exe

[Geezer]

I'm bashful to post here, but since the old thread is closed...

This post relates to Win 2k and the "Old" XPCREATE, version 22.01.2004 01:00.
I don't think we're going to have a fully unattended 2k without runonce. I haven't tried the latest XPCREATE, but from what I understand it doesn't support runonce.

Quote

boehmri Posted: Feb 13 2004, 10:22 AM
Some time back, GM indicated that support fow W2k and windows 2003 "might" be added at a later date. I've been using the "old" version of xpcreate to manage w2k. GM has eliminated support for RunOnce in the current version, and that's where a conflict arises. W2k, by default, ships with IE5.01. I consider IE6 to be a requirement. Certain patches can NOT be applied until AFTER IE6 is installed. This requires RunOnce functionality.

My work builds on boehmri, you will have to refer back to the old thread (see his post Feb 17 2004, 06:28 AM)

@GM: My IE6 install was made using IEAK with guidance from twinkies site. http://www.tech-hints.com/ie.html
I didn't add any custom components. Mine installs unattended without _any_ command line switches, but I can't remember exactly how I did that, and I'm at a different location. Will redo and post if you want. From the \Builds\FLAT\WIN32\EN\ I just made an iexpress package with all the files, which calls ie6setup. The resulting exe package is 71,092,224 bytes. It goes in SVC-EXE, just like boehmri. I tried it in SVC-PRE (old version, remember), and it didn't "take". There might still be some way, I just havent found it.

STATUS AND THANKS
-------------------------
I got my 2k unattended working!!! Great stript. I love the way it handles the hotfixes. I chose the right tool. I'm still working on some minor issues, but I feel like I already waited too long to post thanks.

The goal, of course, is no missing critical/recommended hotfixes/updates, fully unattended.

@boehmri. Thanks much for your help. I had a feeling you could help with your "manage w2k" (confident and competent), and I was right. I was already halfway there when I saw your post, but I have referred to it several times.

NOTES
--------
A few points:
1) There is a small bug in XPCREATE 22.01.2004 (it was fixed in XPCNEW):
The two lines
IF /"%OVERWRITEOEM%"=="YES" SET HF1SWITCH=/O /Q /N /Z
Should be
IF /I "%OVERWRITEOEM%"=="YES" SET HF1SWITCH=/O /Q /N /Z
That causes the setting for OVERWRITEOEM in XPCREATE.INI, to be ignored. At first, I thought it was the cause of some problems I was having, but now I don't think so. Nevertheless, something to be aware of.

2) No one seems to have mentioned, that if using Runonce, you need to get Reg.exe into WINNT\SYSTEM32. It's not there in my 2k. I do this by putting it into FILESCD\$OEM$\$$\SYSTEM32.

3) Unlike boehmri, I put js56nen.exe in HFTYPE2 (aka SVC-HF2). Works fine.

4) With q330994 in RO-HF2, I also experienced the blue-screen lockup reported by beohmri and MaaR. My solution is to call a batch from GUIRUNONCE in WINNT.SIF. It works. Note that although no reboot is needed for Q330994, you do need to reboot for most other hotfixes installed from RunOnce.

Actually, unless we can avoid runonce altogether, I would put all post-svcpack, Type 2 hotfixes into GuiRunonce. This could be fairly easily automated into the script, which I plan to do unless runonce can be eliminated.

RESULTS
----------
Post-install, I ran three tools: hfnetchk.exe, MBSA 1.2, and Windows Update.
- HFNETCHK.EXE: This says that a couple of files (CRYPTDLG.DLL and msadce.dll) have an "invalid checksums", even though the file version is correct. I think hfnetchk is wrong, or is too nit-picky.
- MBSA: Cannot confirm that (819696) installed. I understand that it is included in DX9.0b, so I ignore this. Says that "MSXML 3.0 SP3 The latest service pack for this product is not installed. Currently SP3 is installed. The latest service pack is SP4." I am ignoring this for the moment.
- Windows Update: As boehmri said, js56nen.exe, is not detected by Windows Update after completion. It recommends an update. I confirmed that the updated file is, in fact, installed.

So here we have three tools, and three results. Is there something wrong with this picture?

TO DO (for me)
------------------
- Try to get NVIDIA WHQL driver to be installed unattended (I already have OemPnPDriversPath pointing to it).
- Add a few tweaks and apps, for example, Adobe Reader.
- Get it working on XPCNEW and/or latest XPCREATE (no menu).
- Unattended XP.

MOTIVATION
---------------
Why am I using Win2k. Simple, my company has 50 seats of Win2k. We operate on a revolutionary "zero cash" business model, which is closely linked to the "all profit goes to the owner/founder's latest pet project" strategy. Therefore, we are always a few years behind the IT curve. We only get XP when we get a new box. We even have a few 98SE boxes. Confession: I'm not actually in IT. I'm a programmer, engineer, and technologist. Basically I am looking for ways to improve our IT management, and efficiency and productivity in general. Maybe I can divert some of the savings to MY pet projects!

Final word
------------
@GM: Sorry I was a little harsh, earlier, about the documentation.

Gday all.
-Geezer

[GreenMachine]

@Geezer: Well, all them words built up inside, perhaps YOU should write the documentation!

I have to disagree: if being a programmer, engineer, and technologist is not actually being in IT, my definitions have been all wrong. Take a look HERE to see where it all started ...

I'm glad you got it working as you needed. As a programmer you can understand my reluctance to go back over code that has already been forgotten. There are some flaws in the code I am aware of, and have not corrected. However, I have tested the new version with Windows 2000, and am satisfied with the results. Upon first reboot, there are 4 critical hotfixes remaining, all related to IE. Considering the 15 Critical and 9 Recommended on a clean SP4 CD, that is not too bad. Though I have not done it myself, you should be able to simply edit WINNT.SIF in the GuiRunOnce sections (is that what you meant?) to include these 4 hotfixes, and you are done. Though it is not as easy as having the scripts generated, I think it is a fairly painless alternative.

I did finally create an IE package, with only 2K updates. This is about 12 Mb, and is all you need unless you will be updating your 9X boxes with the same install file. However, the article you referenced did mention the ability to add hotfixes. I am doubtful that the 4 hofixes that remain can be installed in this fashion, but if they could, that would reduce the need for any RunOnceEx or GuiRunOnce handling. Might be worth a shot ... In any event, attached is a list of the files that I would recommend. I think you can achieve what you want just fine with the current version, so please give it a shot.

Good luck, and keep us posted!

Attached File(s)

•  ShowDir.txt (1.8K)
  Number of downloads: 77