GreenMachine

DriverGuide Toolkit identifies and lists drivers installed on your computer and, when connected to the Internet, allows you to search DriverGuide.com (and other sources) for driver updates and manufacturer sites. In addition, it allows you to backup your currently installed drivers for safe keeping. Backing up your Windows driver files means that they will be available to you the next time you need to reinstall the driver or the whole operating system. DriverGuide Toolkit places the driver files in one organized location of your choosing. Upon second reading, I think this does not answer your question ... still a nice tool to have ...

Thanks, Ice M., I think virindi will get to that, as I am still squating someone else PC. Virindi?!? Thanks!

@Jjazz: Thanks for the link, the msiextract looks interesting. WGet is OK, but iOpus is easy, and is working fine for me now, If it ain't broken ... (don't fix it). The mssecure.xml contains all the info for MBSA and HFNetChk. It's place is in the analyzing of installations, not creating them, but there are certainly many ways in which it could be used. @Virindi: Those are good ideas ... but don't really add to the functionality of the final creation: they just make it "easier" for the user. I did, once upon a time, have a notion of current/outdated version, and an "Update XPCREATE" option in a, heaven forbid, menu. For the moment, the current version seems "rich" enough. @Ice M.: The problems arise because iOpus will only save in 8.3 file name format. Your ideas, even if often bruskly rejected, are more than welcome. Keep them coming!

Getting closer ... thanks for the results of your experiments!

@mattozan: Caught you! Unfortunatly, trial and error is often the best debugging technique. I do want to mention that P1A is (supposedly) the same as SP1, less the MS Virtual Java Machine, and some indeo codecs. It has nothing new, and in general, people prefer to install SP1 to SP1A (well, at least I do ... ) Do post when you find the trouble maker!

Thanks again! Perhaps I'll make better instructions or a package to help ... but not before the weekend. One help is to create an installation with only XP and SP1, go to Windows Update to get the patches, and then look in Windows Update.log for the URLs.

Sorry ... Put all the files where there are supposed to be (as shown in the Current Hotfixes List) Run XPCREATE and test the created Windows XP (VMWare / VPC is fine) If the "test" version of XP looks good in Windows Update, you have the correct hotfixes. Run the MAKELIST utility attached above in the directory you used to make the XPCREATION (your "main" PC, not the new XPCREATED PC) OK? Thanks again!

Cool! Put the files in the SVC-* directories, as XPCREATE will use them. I would suggest creating a "good" XP Installation, that shows OK on Windows Update, and then just run the utility mentioned above. Thanks!

Just like the old XPCREATE, RIS has a Green User Interface? I believe people can overcome the TUI aspect, but learning PERL is not a task for the lame, and will immediatly eliminate a great many of the "Hobbiest" users here. I also see an obstacle in the software/hardware requirements: servers, perl interpreter engines, etc. That said, it is, of course, an admirable project, where I have looked more than once, and probably a very good alternative to the RIS method.

I've never looked into NSIS, but it looks like more work than I am interested in to write an actual installer. However, it does mention scriptable. I am not sure if that refers to installer creation, or the installer program. Thanks for the idea, Mei.

We will have to look into that KB837272 hotfix. Could it be the wrong version? Something is preventing the creation of the report (.RPT) file. Is there any anti-Virus software running? Again, trial and error will find the problem: add your software until XPCREATE displays these errors. One last point I must stress: most of the software modification as of late has been additions to data written to the XPCREATE.LOG file, as I "live and learn" with "error reports" from the forum. The file LOGFILES.CAB has been created to make posting this log file more efficient. Please post it when reporting errors, it really takes a lot of the guess work out of my end.

Waiting on you ...

XPCREATE does not correctly install the WININET updates without QCHAIN. This is in part due to the fact that an earlier update (Q831167) has a later file version than another IE update (Q832894). Note these are both Type II updates, which, I believe, does not include QCHQIN functinality.

@Bilou: I sent you a PM ... If anyone else has any experience in MUI, please post your thoughts on this subject here, as well as any other helpful information you may have.

Welcome to MSFN, mattozan! First create a CD WITHOUT WINNT.SIF, CMDLINES.TXT, and anything elst that is not listed in the failsafe list of the Current Hotfixes page of the Web Site. Once you have the basic CD working correctly, add your tweaks and apps. Let me debug XPCREATE, not user files and reg tweaks, and remember, please, everyone, walk before you run: Make a functioning baseline CD, and then add your customizations.

There should be no need for deleting directories or other methods to reduce the size of the source CD. Obviously, I side with Alanoll: User Error. Attach the LOGFILES.CAB file to your next post. I suspect the answer is inside ...

@Alanoll: The DX9 update/repack may be the answer, though I doubt Spheris is gonna like it! A bit tough, because the files are in a CAB inside and IExpress package, but there should be a way, assuming the CAT files get updated first. Maybe this weekend ...

Yes, I have seen this. I tried once to do an upgrade with an XPCREATION, had similar results, and determined that there were too many errors and warnings. XPCREATE IS NOT UPGRADE COMPATIBLE.

I don't recognize the source, and I wonder about the file WINBETA on the root of the CD. What exactly is an MCE CD? All missing updates are WMP updates. Did WMP 9 get installled? You also have DLAUTO set to NO, so XPCREATE is not verifying the hotfix checksums. You are, of course, sure they are the right files? Lastly, you are running an outdated version that has a bug in the SATA drivers code (SATA not added to CD). So ... download the latest version, remove all the files in the FILESCD directory (for now), give it a run, and let me know ... The file LOGFILES.CAB is simply a copy of the XPCREATE.LOG file in compressed form - save yourself a step in zipping. EDIT:: Looks like WMP was the culprit ...

I'm back on line, but it'll still be a few days till I have a development machine going.

Thanks, Alanoll. Too bad though: I liked it better when MBSA ignored this "pesky suckah" ... Maybe this week I'll have a chance to delve deeper. Maybe next ...

Thanks again, Virindi, keeper of lists! It can happen that the patch is updated, thus MD5 changes, and there is no information on Microsoft's site. This would be the case if the hotfix installer changes, but the fix itself does not. Those with errors, please post if your problem has or has not been resolved.

Thanks, visaversa, and Ice M. for the updates! No, lets see if I can't shame a few more freeloaders into helping out ... COME ON! Tools here: http://www.msfn.org/board/index.php?showto...ndpost&p=139066

DOPATH=YES/NO If set to yes, XPCREATE will update the OemPnPDriversPath line in WINNT.SIF, according to the INI file (DRIVERDIR=), and the INF files present in and below the given directory. Welcome to MSFN, cyberdemon!

To clarify my example ... CD is originally D, you change it to K:, with an alias poining to D:, so that setup can find the files to continue. Data was originally E:, you change it to D:, with (or without) an alias to E:. So ... does D: point to the alias of K:, the CD, or the DATA disk D: ? Changing driver letters fron the command line is tit, but avoiding the conflicts is not.