GreenMachine

I don't mind! Strange about KB840374.EXE and MSJAVAWU.EXE. I don't see that at all. And KB840374 only updates the Help Center ... I do not understand. What do you mean "REMOVE and XPCREATE"? If you are refering to the various methods of REMOVING files from the XP Source, I cannot help you there: never tried it.

Yes, the MBSA is a much better tool than the Windows Update. What you will always see, is the 3 hotfixes that cannot be validated and WMP with one file version higher than expected.

Care to test me!? Three month trial?

Everything is installed fine. You do not need vbs56nchs.exe, as it is already there, and causes the other (js56nchs.exe) to appear uninstalled. If you want both, rename vbs56nchs.exe to jbs56nchs.exe, and that is OK too. So ... either REMOVE vbs56nchs.exe, or rename to jbs56nchs.exe.

You do not need any of them. XML V3 and V4 are not the same thing. Sometimes one is called for, sometimes another. If you install MSXML3USA.MSI (maybe there is a Welsh version!), you should install the update as well. I see no reason not to install them all, so I do. Windows Update does not complain about them missing, but the Baseline Security Anayzer does.

Greetings, ziboy, and welcome to MSFN! vbs56nchs.exe is your problem. You do not need it. It overwrites the js56nchs.exe registry entries, though they do not replace the same files. Took me a while to catch that one ...

Hope I don't have to put more spies in the program to insure Source Integrity ... I don't mess with the source: I copy it from CD to HDD, and use it as is from there. I understand certain peoples desire to "have it thier way". However ... getting everything just right with a given set of files is a job in itself. Getting everything just write with an unknown set of files is a task I care not undertake, thus my reluctancy to even look at errors unless I am sure of the source code integrity. So please, if someone decides to muddle about with the source code, state that up front. I may, or may not, be able to help, but I will not be a happy camper if I have to discover it on my own ...

Bitte schoen! I thought that was clear about $OEM$ being inside FILESCD. Maybe have to re-word it. Ooops, now I see what you mean. Fixed. What problem did you have with 837272? Didn't install? Files not found? Someone else mentioned an issue with this one, but it works fine for me ... Please let me know what is not working, so I can fix it, or update my list. As for 819638, that is a MS Project update. Special case, and not the XP OS, so ... not my problem! Thanks for pointing out the "weak" points!

Now THAT'S what I like to hear! Might just have to close and pin this one ...

If you were having issues, you would know already, during slipstreaming or installation. If you made it to Windows Update, and that looked OK, you should be fine. The method used in the MSFN guide, however, is specific to the Security Rollup, and does not allow for slipstreaming a second hotfix. As SP2 approaches, the Rollup will become redundant, thus the MS method of SVCPACK.INF can be used.

Sorry, those logs don't show anything suspicious to me ...

Thik of it this way: XPCREATE is for setting up the OS, XPlode is for setting up the applications. I quote from the Web Site ...

Still don't understand why with SP2, the May Updates do not show as needed, even though they are not in the SP2 codebase. Or are they ...

Oh, that hotfix. The "rubbishy options". XPCREATE sill uses the standard method for this: it is backwards compatible. As for the "/integrate" switch, I do not use it, as XPCREATE does a cleaner integration. Yes, it does make a mess. Fortunatly, only XPCREATE sees it, as GreenMachine never needs to look at the results (after testing). As for MSJVM, I test it with SP1 with MSJAVAWU.EXE, the MSJVM update, and SP1A without. I have not yet tried SP1A, and the baliktad MSJVM "package". Nor have I experienced any boot hangs.

I know: it is tough to find them SP2 hotfixes. Slipstream or not, it is still beta software. I haven't had an SP2 machine yet that made it to the "Must Activate" stage.

Actually, the problem is not in CDIMAGE, rather in the TXTSETUP OS, which cannot find the files from the tables. That same CD shows everything fine in Windows. It is a delicate balance, and I have it the way I want it to work for me. There are other ways ... I only have 8.3 UPPER names ... It was just so long before I found out that something else existed, that I can't manage to right my ways. Yes, the /N switch. Run the files through that once, and you can be sure to never have a problem! What strange hotfix? I use the Current hotfixes list on the XPCREATE web site. Does one of those not work for you as listed?

I noticed tha too, now that you mention it. What I don't understand, is why it shows no updates needed, even though it came out before the May updates? MS04-15 does not show anywhere using SP2/WUV5. What I meant, is before it is RTW, the code must be frozen for a certain time, at least a couple months, so updates will already be needed once released. Just as did the Security Rollup.

Once you do, clue me in! All's well that ends well.

No, it is not installing. I do not understand why there is so much trouble with this one. I have added code to the next version to gracefully crap out if everything is not as it is expected. The downloaded file is fine: it has not changed for months. The error message you see is that it cannot find the XP copy of SWFLASH.INF that is to be updated. This is expected to be in the I386 directory of the CD: CDROOT\I386\SWFLASH.IN_ (compressed). XPCREATE is unable to extract SWFLASH.INF that is inside this file. Why, heaven knows ... Either the file does not exist (then you are not using an Original XP CD, and that is one of the pre-requisites), it has become corrupted (doubtful ... ), or the expand utility has a bug (possible), or even anti virus software. The only other ideas I have is to try on another PC, or just remove SWFLASH.CAB and fahget about it.

Yes, cyberchicken, I, too, sympathize for you. Especially when the solution is so simple ... I should have got the tip when I saw your code in lower case. I always write DOS code in UPPER, use 8.3, and often use XCOPY with the option to rename to NT4 names. There is also the option to create the ISO with other programs, that may (or may not) have better luck.

Another problem ignored till it went away! You should be able to use the quotes just fine in WINNT.SIF. As a matter of fact, I'll bet that the usage or non usage of quotes in Setup Manager's WINNT.SIF ia arbitrary. I think you only need them when there are spaces in the value.

Still waiting on you to send me one of them Tab's ...

Don't let me stop you from testing XPCREATE with it now, and sharing your findings!

Baliktad wrote a posting about merging the two MSJVM to come up with an installer. Search for a topic started by him. Must be over a few months old by now. Once you create that package, it shold be able to go into SVC-PRE, assuming you build it correctly with IEXpress.

Actually, I updated the site after I read your message. I also think I forgot to include it in my distributed version of XPCREATE. Still, I think XPCREATE is a nice name for all yor CDs ...