GreenMachine

At the moment, you MUST place your SATA drivers in, or below, FILESCD\$OEM$\$1\DRIVERS in order for integration to succeed. Next XPCREATE update will fix this.

SVC-X2M it is. Personally, I just add the winipcfg.exe (the actual program, not the installer) in SYSTEM32, and create a shortcut in System Tools, as installation, as such, is not required.

Hmmm. First glance at the log files did not ring any bells here. I will post a version of XPCREATE with even more logging, hopefully before the weekend. If you can wait, we can work on it then.

I would say it is a matter of personal esthetic preference: both can accomplish the same installation results. RunOnceEx looks prettier, GuiRunOnce is simpler. I use RunOnceEx, as I have it all automated. If I were to do it by hand, I would certainly consider GuiRunOnce. My two cents ...

@xracer: Looks like you got it working ... I haven't looked over your log files, but if you are still having XPCREATE issues (and not reg tweaks / custom install issues), please post back. @shareef59: Thanks for the help! @daywalker03: Not sure about your IE thing. If you have it narrowed down to the WINNT.SIF file, try creating a new one with SETUPMGR.EXE. XPCREATE itself does not change file associations or the like: it only adds the files you place in the corresponding directories.

I use it for both 2K Server and 2003 Server. See current hotfix listing on web site. (Welcome to MSFN!)

SWFLASH.CAB has not changed, and is still version 7,0,19,0. The error states clearly the missing file in question ... check your XP source.

Most points to cyberdiamond! $OEM$ should be placed as FILESCD\$OEM$ for a CD install, and FILESCD\I386\$OEM$ for a network install. This results in <CDROOT>:\$OEM$ and <CDROOT>:\I386\$OEM$, respectivly. If you used the latter structure, this would result in SATA integration problems, as the SATA drivers are searched for in FILESCD\$OEM$\$1\DRIVERS. This will be remedied very soon ...

That was helpfull ... 442 posts to look through ... Gosh did post a hack (not a reg tweak) to do just that. My best recollection is 2-3 months ago. Spheris posted in the same thread, which was never very big. If you do find it, please post a link to that thread, for the next person who comes HERE due to a search.

... there is always a log file, somewhere ... XPCREATE.LOG ... I don't debug without it ...

Welcome, xracer, to XPCREATE and the world of GreenMachine! ... Attach the XPCREATE.LOG file to your next post ...

You guys are making me dizzy ... First, here are the hotfixes I use: Directory of D:\XP\SVC-HF1 24/12/2003 18:17 427,368 Q32201~1.EXE Q322011_WXP_SP2_x86_ENU.exe 05/03/2004 03:34 1,137,512 Q32318~1.EXE Q323183_WXP_SP2_X86_ENU.EXE 05/03/2004 03:31 882,536 Q32797~1.EXE Q327979_WXP_SP2_X86_ENU.EXE 24/12/2003 18:18 601,448 Q81024~1.EXE Q810243_WXP_SP2_x86_ENU.exe 31/12/2003 17:30 795,496 Q81111~1.EXE Q811114_WXP_SP2_x86_ENU.exe 24/12/2003 18:18 1,018,216 Q81499~1.EXE Q814995_WXP_SP2_x86_ENU.exe 24/12/2003 18:12 537,376 Q81502~1.EXE Q815021_WXP_SP2_x86_ENU.exe 10/02/2004 22:58 2,914,040 WINDOW~1.EXE WindowsMedia-Q828026-x86-ENU.exe 31/12/2003 17:30 1,460,512 WINDOW~2.EXE WindowsXP-KB810217-x86-ENU.exe 24/12/2003 18:12 1,051,936 WINDOW~3.EXE WindowsXP-KB820291-x86-ENU.exe 24/12/2003 18:12 354,080 WINDOW~4.EXE WindowsXP-KB821253-x86-ENU.exe 24/12/2003 18:12 349,472 WI1487~1.EXE WindowsXP-KB822603-x86-ENU.exe 24/12/2003 18:12 433,952 WI3664~1.EXE WindowsXP-KB823182-x86-ENU.exe 24/12/2003 18:12 346,400 WI5427~1.EXE WindowsXP-KB824105-x86-ENU.exe 24/12/2003 18:13 2,223,200 WI5522~1.EXE WindowsXP-KB824141-x86-ENU.exe 24/12/2003 18:13 305,248 WIB420~1.EXE WindowsXP-KB825119-x86-ENU.exe 24/12/2003 18:16 9,442,912 WI5525~1.EXE WindowsXP-KB826939-x86-ENU.exe 25/12/2003 15:05 1,089,120 WI9567~1.EXE WindowsXP-KB826942-x86-ENU.exe 24/12/2003 18:16 365,664 WI95C6~1.EXE WindowsXP-KB828035-x86-ENU.exe 15/04/2004 14:23 3,231,000 WID2E4~1.EXE WindowsXP-KB828741-x86-ENU.EXE 24/12/2003 18:17 2,961,504 WI3666~1.EXE WindowsXP-KB829558-x86-ENU.exe 04/04/2004 13:55 3,706,648 WI7333~1.EXE WindowsXP-KB833998-x86-ENU.EXE 15/04/2004 14:17 2,710,296 WI3275~1.EXE WindowsXP-KB835732-x86-ENU.EXE 15/04/2004 14:18 2,972,952 WIB1DF~1.EXE WindowsXP-KB837001-x86-ENU.EXE Directory of D:\XP\SVC-HF2 24/12/2003 18:19 369,504 js56nen.exe 15/04/2004 14:11 1,996,032 OE60SP~1.EXE OE6.0sp1-KB837009-x86-ENU.exe 15/04/2004 14:08 386,816 Q831167.exe 03/02/2004 01:59 2,907,904 Q832894.exe 29/12/2003 22:06 1,393,488 HU1002~1.EXE hu1002_pro.exe Directory of D:\XP\SVC-MDC 13/01/2004 23:26 2,095,288 ENU_Q8~1.EXE ENU_Q832483_MDAC_x86.EXE Directory of D:\XP\SVC-MSX 15/01/2004 03:19 1,911,952 HMTCDW~1.EXE HMTCDWizard_enu.exe Directory of D:\XP\SVC-PRE 24/12/2003 18:43 11,751,280 DX9NTOPK.EXE Directory of D:\XP\SVC-WMP 08/01/2004 00:09 10,135,688 MPSETU~1.EXE MPSetupXP.exe Directory of D:\XP\SVC-WMS 05/02/2004 03:17 1,001,536 MMSSETUP.EXE Directory of D:\XP\SVC-X2M 16/04/2004 16:31 <DIR> .. 16/04/2004 16:31 <DIR> . 08/01/2004 01:59 12,580,696 mm20enu.exe 07/03/2004 16:33 7,372,408 setup.exe 08/01/2004 01:54 24,265,736 dotnetfx.exeThis should be everything, except 817778, which I install via GuiRunOnce. @Bluelane: The "new" switches are not implemented by XPCREATE. The "old" switches work fine. I have heard rumours that these poorly thought out "new" switches will be dropped, and I hope they are ... Also, there should be no need to manually edit the SVCPACK.INF file ... @mdes: Something surely looks wrong if you get the directories you described. I am not convinced it is XPCREATE, but I will try to test the French Version soon ... If you take out these two updates, or one of them, is everything else OK? The WININET.DLL file slipstreamed onto the CD is the correct version, as you noticed.

Welcome back, mdes, you have ben quiet! Indeed, Q831167 is installed before Q832894. Sort for Type II hotfixes is alphabetical. You could change the names to adjust installation order. However, my tests show that this does not present a problem. I assume file copies based on date, and QCHAIN prevent any version error. There really should be no need to repack anything ...

Should look like this: The problem is in the XP source, not the XPCREATE integration or SWFLASH.CAB file: cdroot\i386\swflash.in_ is not found.

Thanks, PorlyBe, for cleaning that up. There is not really a clean or orthodox way to completly slipstream the hotfixes into the XP distribution, and avoid running the actual installers as well. As AaronXP says, you should add the /O switch for speed (XPCREATE does). There have been different posts for slipstreaming different updates (DX9, WMP9, ...), but I have not tried them: just seen a few threads with those titles.

Welcome, ComputerGuy! That link is to a page by member baliktad, one of my favorite MSFN posters! Should work fine: always has for me. Thanks for adding that, for those that may not have seen it yet.

Hmmmmm ... that code looks too familar ... never mind ...

OK. Keep me posted.

You are welcome! Remember, SVC-X2M ...

Sorry, I did not see anything, but I am certainly not an expert. Lke I said ... create a basic, working XPCREATION, and then add things till you find the one that is breaking your Internet access. I also believe it is more likely to be a configuratin issue than an installation issue.

As I recall, you can put it in SVC-X2M. Do NOT include the 4.7 WMS update, and you should be OK. Welcome to MSFN!

Beta software = you are on your own. Looking at your log files suggests that the hotfixes were not slipstreamed. Something went wrong. You could start with the list on the web site, create a working XP distribution CD, and then make changes one at a time, until you find the one in error.

But ... I thought that was YOUR job!

@Outer: As suggested. post your log file. Also, a link for Dot Net Framework V2 would save me looking, and then I can test it myself.

@mniceguy81: I really have no idea about your Internet access problems. I would think the problem is either in your Internet Explorer settings (if Netscape works fine, this would confirm), or your firewall/router/LAN settings (depending on how you are doing it). On the XPCREATE web site, there is a page about adding SATA drivers. Your other drivers would be added in a similar fashion to that of a normal unattended CD, with the exception that the $OEM$ directories should be placed in the FILESCD directory, to be copied to the CD at creation time. I will not be posting any 1-2-3 steps at this time, and, unfortunatly, if you require this, XPCREATE may not be your best alternative. As for the Internet Access problems, you might have more luck posting in one of the other forums. My schedule is very full these days, so my help here will be limited to error correction, and not user assistance. Sorry ...