GreenMachine

No worries. My days of frequent and numerous updatse are over!

Guess I missed that one on the XPCREATE.INI page of the web site. It has been updated. Look there.

For the Java, it should display a message, but not requir user intervention. If it does, then I doubt it is installing. SP1 or SP1A? I stand by my Current Hotfixes List: Those are the right hotfixes. As I recall, some cannot be found in Windows Update Catelog. you need to hijack them from Windows Update, either find the files after an update, or find C:\Windows\Windows Update.txt with the links. The file placed in SVC-MDC should ONLY be the on listed on the site.

Workload, and headaches ... Anything is, of course, doable. Everything is not.

Still with us, MoonPie2000?

I have looked at it a bit. I had some trouble slipstreaming it, but simply used the downloadable ISO XP test version, with SP2 pre-slipstreamed. They are still playing with different ideas, and I am not going to get too invloved till at least RC2, so as not to waste time solving the same problems as Microsoft. It is at least a few months behind in hotfixes. In any event, I certainly will not support it until Microsoft does.

The problem is somewhere in the MSFN's server, but seems to work fine most of the time. I do not want to manage mirrors, or try to remember where my code is posted on the Internet, so for the time being this will remain the only downloadable copy. For the time being, I would like to ask that you don't post copies of XPCREATE, except as was done here: temporarily, and in an "emergency". Thanks!

It is true. Things may appear to be OK, but this easily results in slipstreaming the hotfix files without updating the registry with the necessary information. XPCREATE is NOT a non-destructive process.

Welcome. Can't wait to be rid of that 817778 ... been bugging me since it came out ...

Welcome, MoonPie2000! Attach the file LOGFILES.CAB, found in the NEWFILES directory where you ran XPCREATE, and I will have a look-see ...

The /integrate switch. Perhaps it should be called the /xpcreate switch? I have seen some of those ideas before ... If you look at the article linked to in the first post of this thread, there is both the "new" method, /integrate, and the manual method, as in steps 6 through 13. The /integrate switch basically automates this procedure. What will happen when two of these fixes replace the same files, and then are installed out of order, remains to be seen. The questions are: Which version is in the source. Which version is present at run time. Which order are they listed in SVCPACK.INF. As for using the new update.exe with the old hotfixes, I would be surprised if it works. It would depend if they made a generic inf file parser that is backwards compatible for the hotfixes. As for the long file names, that is a error in design of the hotfix, not the hotfix installer. Much as I hate 8.3, I still use it as a rule in all that concerns the system, and all the files XPCREATE creates for the installation. I wonder how that question will be addressed ... A step in the right direction? Perhaps. One thing I can say for sure, is that given the same source files and hotfixes, XPCREATE will produce a CD distribution that is faster to install, and smaller on the CD, and has more file version integrity than the /integrate switch version.

Long enough for the Welsh, too! Gotta fix that server ...

Apparently there is sometimes that problem. Reports are that using a download manager eliminates the error. It works fine for me at the moment. The servers are beyond my control, but they are never "down" too long.

XPCREATE run and tested first ... then send your error messages to jdeboeck!

Just to be clear: DO NOT USE CDROOT AS XPSOURCE (Strange and mysterious happenstances will occour ... )

This is the fourth type of hotfix (Type I, Type II, Type DA, and now Type NEW). The idea is nice, but having it happen accross the boards seems like wishfull thinking.

Behaviour by design ...

SVC-X2M should be fine.

It don't matter to me what they are called: I never go looking at them once installed. However, Microsoft tests have shown that it does prevent certain problems. Good enough for me: thier test lab is a lot bigger than mine. At some point in the decision chain, given that all else is equal, it must make a difference, it's only logical. Put the exact same driver in two different directories, and see which one gets installed ... As for using different subdirectories, my personal preference is to throw them all in the same 00x directory, providing there are no name conflicts (which, surprisingly, are rare). This also keeps the OEMPnPDriversPath much cleaner in WINNT.SIF.

Read THIS post, particularly the NOT SVCPACK.INF SUPPORTED section.

You can add and re-burn, but unless you follow 8.3 UPPER conventions, be careful of your CD File System options. You can use CDROOT as XPSOURCE, but that would be very silly: You would loose the previous SVCPACK.INF DOSNET.INF would have many double listings TXTSETUP.SIF would be all screwed up if you added SATA drivers in short FUBAR ... XPCREATE is quite simple to set up with system files on one side and user files on the other. Adding a new update is as simple as dropping it in the correct directory, and go. One minute user intervention, and 30 minutes wating. Just enough time for a beer, or a couple vodka's, da?

Sadly, most of the time that fixes the problem. There have been almost no core logic changes to XPCREATE for a long time ...

Sounds like Alanoll's been reading too many of my posts: he's starting to sound like me! XPCREATE don't know nothin': it is looking for files where YOU were supposed to put them. Like the man said: follow the minimal steps, listed on the site, and if that does not work, attach LOGFILES.CAB to your post, explaining exactly what went wrong.

Now you got it! See you in a day or two!

Virtual PC. On the Links Page: http://greenmachine.msfnhosting.com/XPCREATE/links.htm I think you'd best spend a day or two reading before you ask too many questions ...