GreenMachine

That's what I do! As well as ignoring those that cannot write a legible post. Saves a lot of aggravation, and cuts down the work load as well. But remember: I warned you ... (How do you spell choke? R I V E R A ! We know who his daddy is!)

Now that I think of it, I seem to remeber something about the path to the EULA being hardcoded into the text-based portion of setup. For that reason, you cannot change the directory structure. XPCREATE, I fear, will NOT work with these MSDN versions. WIN2003 and WINXP WINNT.SIF are quite similar, but not "exactly" the same. Still, you do not even need WINNT.SIF. VLK = Volume Licensing Kit. It does not require activation. I got my version from the MSDN collection. The easiest solution would be to simply get a hold of the 6 month trial version of Windows 2003, and use that. That is what I do.

In a day or two: I have most all of the new updates for Windows 2000 and Windows XP worked out, except Windows Media Connect.

Same for me. This is the last update I am "missing" in Windows XP, and am working on it now. Thanks, Glowy.

I would certainly add everything on the working floppy. It could be one of the "other" files that are missing. You can find SETUPMGR.EXE in the SUPPORT\TOOLS\DEPLOY.CAB file on the Windows CD. Oh yeah ... Welcome to MSFN, ngtzewei!

I don't quite understand why it works for you ... The problem I was having I have traced to the file SHLWAPI.DLL that is in the update 841356. The file that shold be slipstreamed is in one of the sub-directories. The SHLWAPI.DLL in the root of the patch is much too old. Instead of trying to figure out how to slipstream the correct file version, I have created a new SVC directory for Type I Hotfixes that are applied from SVCPACK.INF, but not slipstreamed. This was the same solution to the OE updates that are added to the SVC-POS directory. Another thing I noted was that the update KB873377 can be used to replace the update KB834707. I add that to SVC-HF1, and have had success with it. So, in the end, I do have everything installed, Windows Update and the Baseline Security Advisor come up quite clean. I will post the updated "Current Hotfixes" Web Page, as well as the latest XPCTEST version in a day or two. Thanks, Bilou, for the help!

Don't get me going ...

It aint over till the fat lady sings, though I have started cheering for the Cards. (We still have the Pats: 19 in a row ... at the moment ... 7:0)

It seems that the KB841356 update is giving me problems. Can you, Bilou, confirm that this is installing OK for you? When I slipstream it, I never get to the shell, even after multiple forced reboots. I hope it is not due to the fact that I am using the un-released version - but I believe you are, as well. Are you?

The New Version was fine ... until this latest round of hotfixes came out. Now I am trying to get it working for those. As for Windows XP Media Center Edition 2005, I don't have a copy, so I cannot say! I would imagine it would be fine ... As soon as I get these last "kinks" out, I'll let those interested take it for a run.

Sorry, slimy, but I don't really do "requests". As for what you requesting, you have complete control over what is installed, either by using your own download list, or by not using a download list at all (DLAUTO=NO), and simply adding the files you desire.

Nice words? Must must have been me!

XPCREATE takes care of getting the "text-mode" driver setup. Afterwards, the driver in OEMPnPDriversPath is loaded. It sounds like this is where your re-booting is occuring. There is really nothing XPCREATE can do at that point. It could be incorrect drivers, unsigned drivers, or some hardware issue. Do those drivers work with the F6 method?

Get the boot image (BOOT\XPCTBOOT.BIN) from your XP XPCREATE directories, and put it in the BOOT directory, and point XPSOURCE to the source (E:\ENGLISH\WIN2003\ENT). That should do it ... I use the MSDN VLK version of XP, which is a bootable CD. XPCREATE is not designed to work "automatically" with non-bootable CDs.

Of course, no offense to RyanVM. I'm sure he understands. The point is just that my debugging is in XPCREATE, not in XPCREATE in combination with other programs that modify the same files. Simply GreenMachine keeping the work load in check.

Is this a trick question? I'll bite, what are the differences ... On a more serious note, please take the time to research and read about the different programs you mention, and formulate your own opinion. I am not very good at holding hands ... Also, please take the time and trouble to use correct grammer and spelling: I honestly have trouble understanding mispelled posts with no punctuation.

Thanks, jobbie, for saving The Lazy GreenMachine from searching to far and hard!

Thanks, jobbie. I'm still looking into this, but what appears to be happening is that Windows Media Connect makes a call to WMP 10 Setup, which in turn reports the error. A simple test that you could perform (and report the results!) would be to take your installation that gives the warning, and re-XPCREATE it, removing only the Windows Media Connect Update. Another thing: Whether you select OK or Cancel from that error/warning message, Windows Media Connect still will install. This supports the hypothosis that WMP is displaying the error, but as I said, I believe it is only the WMP 10 / WMC combination that causes this behaviour. If anyone else has any further info, please post!

Suggested reading for information: http://greenmachine.msfnhosting.com/XPCREATE/ Suggested reading BEFORE posting: http://greenmachine.msfnhosting.com/XPCREATE/help.htm

Thanks, Bilou. I am looking into both that error, and finding a way to add Windows Media Connect to Windows XP at the moment. It looks like you saved me some work there. For some reason, with that update (if that is the "bad" one) my attempt to start RunOnceEx during installation with IE SP1 does not work. This results in the RunOnceEx problem I described earlier. I have about another hour free now, otherwise I will continue tomorrow. More later ...

Hmm ... First: Welcome to MSFN, DONALDSTEIN! Now, without meaning to be obnoxious ... I cannot make heads or tails of your post. Perhaps breaking it up into a few simple, clear sentences would help this slow brain of mine. Also, here is some highly recommended reading to do before posting: http://greenmachine.msfnhosting.com/XPCREATE/help.htm Let me know ...

Has anyone had any luck installing Windows Media Connect unattended? I have tried from SVCPACK.INF, both before and after installing Windows Media Player 10. Both times an error message about System Restore not being enabled appears. This is the same message WMP 10 displays when the /DisallowSystemRestore switch is not used. WM Connect is a single MSI file wraped in an IEXPRESS installer. You can extract the MSI using the /C and /T:<path>. Perhaps an MST transform file? If anyone has any work-arounds, I'm all ears!

Thanks once again, Bilou_Gateux. I am currently working on updating the XP SP2 list, then I will do the 2K lists. I am not sure what is hanging your installation, but most often it is a call from RunOnceEx (Windows puts many there). My suggestion would be to start Regedit when you press CTRL-ALT-DEL, and see what is left there. The command in question will not be shown there, but the next command will be. Then run setup again, and interupt with SHIFT-F10, at around the end of setup, look at the registry again, and see which command is just before the ones you previously noted. I'll report back when I make some progress on my end.

Welcome to MSFN, crucial! The phenomenon you describe is due to the fact that both drivers are the same version number/date. The Windows version does not include the control panel applet and such. The only work around I can think of off the top of my head is to somehow fool Windows into thinking that your version is newer. Perhaps editing your INF file? Beware that this may break the code-signing, and you may need to instruct Windows to use unsigned drivers. As soon as a newer Nvidia driver is available, this issue will be resolved. My guess is that will happen before I figure out a better work around. Good luck, and let us know if you find a solution!