GreenMachine

Just put the chipset drivers into in FILESCD\$OEM$\$1\DRIVERS\001, add DRIVERS\001 to the OEMPnPDriversPath in WINNT.SIF, and you should be fine. In short, standard procedure. RAID is special case, as they need to be "integrated" into the source. Hope that get's you going!

Dutch is drolly? What about all the "build your own" German Words? Or in German: Selbstzusammengebautewoerter. Or the need to read sentences from the end, just to know the verb before you read the other three lines? Or in German: Umgekehrteverdamtelangesaetze? Now you all know why I migrated to the south! Right, visaversa?

Hmmm ... what does the EULA say? I must say, I don't really see how that will help. The directories needed by the user are SPACKS, and SVC-*, and what goes there is outlined on the Web Site. There are not that many choices where to put files, nor that many files you could (should) add, and these are ONLY the MS hotfixes. In terms of additional, user specific files, you should integrate these files in the standard unattended manner. The trouble begins when you try to use tools for purposes that they are not intended for: XPCREATE can integrate most hotfixes fine, and those that it cannot are well documented (e.g. 817778). It was not meant to be the Total unattended CD answer. I must repeat myself: make the failsafe CD (that should ALWAYS work), and then add your modifications. In this way, all you need to debug are your own additions, which are simply copied to the CD by XPCREATE, and not integrated in any way.

Looks like you figured it out! As for a directory for First Logon programs, XPCREATE is NOT concerned with what happens after setup. You are on your own there: that has been documented many times on MSFN, is not particularly challenging, and would be the begining of unlimited requests to have XPCREATE do the whole nine yards. Try programs like XPlode or WIHU for your post-install needs.

I know, I know ... The lists are out of date, and I'm on the road, away from my lab. Just toooo much trouble to test and download from a laptop with a mobile phone for a connection. Soon ... Thanks to those of you that do try to help out the others. For now, just add the missing updates to the correct directories, and all should be OK.

Yes, Bodhammer, SWFLASH should be the only thing missing. It will be deleted from the list: it seems to change too often. Too much work, too little return. The option to add it yourself will continue to function. Thanks, Souka, for pitching in!

SP2 should work, but I am not going to bother with the beta versions for the reasons listed above. Once released, I expect to have it working ASAP (or after vacation, whichever comes last ... ).

I thought I had straightened out the long file names problems. I will double check for the next release. I guess the BootImage File question has since been resolved.

Ah ha! So it was YOU! I'm afraid I'm going to have to flame you till heavens end. Wait a minute ... Aren't you the moderator? Ooops ...

I saved XPCREATE.LOG from the link above, and much to my dismay it was an HTML page, not a log file at all. Please attach the file LOGFILES.CAB, and I will look at it. Furthermore, if you have not tried a failsafe XPCREATE run, with only the hotfixes listed on the Current Hotfixes page, please do so first (i.e. NO custom REG/CMD files.)

Nice work, 1dimitri. Thanks! I'll add this to the lists, as soon as the lists are updated.

That's an interesting idea: nLite as a Setup Manager replacement. Thanks, Nuhi!

Looks like you found the problem, rikai. If not, post back. I do not use any ISO editors, as I don't really see the reason. I prefer to create each ISO individually, as Alanoll suggests. The time factor is minimal, and it certainly seems to be a "cleaner" solution.

Seems that the page has indeed changed. I am not sure where the TweakMP download went. Perhaps it is included in another update, or pulled for other reasons. If I find out, I will post more info. Sorry.

Strange about that ESP and ESN thing. I will look into this when updating the Hotfix Lists (soon ... ).

Thanks, Glowy, for pulling the link down. Thanks, visaversa, for your help with the list. I hope to get the lists all straightened out soon, but it may not be to very soon. Till then, I hope posts like these will help everyone figure out what goes where.

Thanks, it_ybd! So far so good. The best part is, that I still have a couple weeks to go!

Correct you are, 1dimitri, there is a minor error in the code that results in the symptoms you describe. This will be fixed in the next release of XPCREATE. Thanks for pointing it out! Concerning your modifications, thanks for sharing that. However, please read THIS post.

I know that XPCREATE is written as a Command Script, and that as such, it is difficult to resist viewing, or even (gasp) modifying it. However, both of those are no-nos. Upon installation of XPCREATE, those restrictions are outlined in the EULA (End User's License Agreement) that must accepted before installing XPCREATE. I am depending on the user's honesty, a decision that seems less and less prudent as I see all the suggestions for code modification, or read how XPCREATE worked fine "after changing" the command script. I know that this may be disappointing to some, or even "wrong" to others. However, XPCREATE remains the intellectual property of it's creator. I am willing to share the fruit of the many, many hours of coding, testing, and refining that have gone into XPCREATE. Willing to share, but requesting that a few simple conditions be accepted. If you do not agree with these "conditions", please just forget about it, and move on elsewhere. There are other alternatives. If you think that there is a need for improvement, and that the process should be different, why not create your own? That is a most respectable alternative to "stealing" the work of others. So, in regards to various suggestions as how to "modify" XPCREATE, where well intentioned Users will show their modifications to XPCREATE, please refrain. Additionally, as everyone's coding techniques are different, and mine are the result of over 20 years in the business, thus quite "developed", or at least I am quite "set in my ways", use the standard procedure: outline the problem clearly in terms of the problem itself, not the XPCREATE code. Define the solution as desired results. Most people who "code" for a living do not take kindly to others that are not involved in the product telling them how the code should be improved. I am no exception. Again, I do understand that most of those with modifications consider that they are helping, and I thank them for this attitude, and desire to help. But the most help to me would be to NOT modify my code, and to explain in clear terms how you feel that XPCREATE should be different. Many "features", or lack there of, are for a reason that may be far from obvious to those less familiar with the coding and testing that goes into XPCREATE. Thank you for your understanding, and Happy XPCREATIONS!

That Wraith: always full of good ideas! I took your suggestion!

Still kickin' ... somewhere on I-71 ... Just a quick update: The hotfix lists have not been updated, that's why the newer hotfixes show on Windows Update. Who knows if SP2 works? Try it and see, but don't bother posting error messages, as I will not "officially" support it, until it's "official", and I've tested it. The errors/questions posted are probably all solvable with proper configuration, and the right set of hotfixes. Not enough to make me take time off vacation and debug. That's all for now. Bonne Route!

Can I play, too? FOR /F "TOKENS=3" %%I IN ('REG QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "SourcePath" ^| FINDSTR "SourcePath"') DO SET INSTALLCD=%%~dI

Vamos a la Playa !!! ... Tapas, San Miguel y Chocolade ...

As I understood, there IS a difference in the spoken word. Allez, dit, next you'll be saying that the Wallons speak French, une fois ...

That's easier than Flemish. This cat is NOT away ... get off the table ...