GreenMachine

So, we get a choice? Coherency, or spelling?

That must be Canadian for "I didn't add the drivers"!This page should answer your SATA questions: http://greenmachine.msfnhosting.com/XPCREATE/raid.htm As for the Downloader Link, I would suggest you use the latest XPCREATE test version instead. I am not sure that the Downloader link will be resurected.

Before I can support localized version of Windows for Hotfix Downloading, I will need to know the 3 letter code (ENU = English-U.S), as well as the contents of the PRODSPEC.INI file: ; ;Note to user: DO NOT ALTER OR DELETE THIS FILE. ; [SMS Inventory Identification] Version=1.0 [Product Specification] Product=Windows Server 2003, Enterprise Edition Version=5.0 Localization=English ServicePackNumber=0 BitVersion=40 [Version] DriverVer=10/01/2002,5.2.3790.0 I already have this informatin for English, French, German, Czech and Dutch. If you have any other language versions, please post them here.

I've updated the Test Version once again. As usual, the latest version is the only version that is being debugged, so please use this version before reporting any problems. There have been quite a few modifications since the previoius test version. These include: XPCREATE.INI default values will work as is on most configurations, with the exception of the CDBURNER. Downloader may optionally delete outdated files. Use of external programs COMPRESS and EXPAND has been changed to MAKECAB and EXTRAC32. Boot Image is extracted from Windows source, resulting in a locallized version. COMPRESS.EXE, EXPAND.EXE, MAKECAB.EXE and QCHAIN.EXE are no longer distributed with XPCREATE. QCHAIN now required in it's downloaded form, as a hotfix installer. XPCREATE will extract the necessary files from the full download. File downloads are verified using the MD5 checksum. Service Pack download handling improved. Distributed in an "installer". In short, I have "id***-proofed" XPCREATE as much as possible ... The Web Site for this version is in the process of being updated. This version is only downloadable form the XPCREATEWeb Site. This version also includes an End User License Agreement that mainly covers my own butt, and grants non-commercial users an unlimited license. The license is not very long, please read it. Commercial use is limited to one week of testing on one computer. If you have other licensing needs, or indeed to use XPCREATE in a commercial environment, please contact me. XPCREATE is now distributed in an IExpress Installer (surprise, surprise ... ). You are prompted to accept the EULA, and then indicate the extraction directory for the pogram. The installer is nothing more than a self-extracting archive, and XPCREATE does not write in the registry, or write to any other directories than the sub-directories in which it resides. To completly remove XPCREATE from your system, you only need delete the installation directory used in setup. Virindi has graciously contributed both the effort and the web space to host the Hotfix Lists. If your language or version does not download any hotfixes, please post your PRODSPEC.INI file in a seperate thread for future inclussion. Any help with creating, testing and maintaining these hotfixes lists is appreciated. Please note that I will not be maintaining these lists myself. You may modify the XPCREATE.INI to use the URL of your choice for retrieving these files. The suggested use of this test version is to: Extract all files to the directory of your choice. Insert your Windows CD into the CD drive. Double click the XPCREATE.CMD file a first time time initialize all directories. Double click the XPCREATE.CMD file a second time to start the complete downloading and slipstreaming process. (This could take several hours, depending on your Internet connection.) Use this set of hotfixes and files as the base of your Windows Creations. Though the first run can be quite long - I would run it overnight - subsequent executions are quicker, and the Windows source will already be on the HDD, slipstreamed with the latest service pack. As I do not anticipate any error reporting, please post your success stories!

Right you be, Alanoll. XPCREATE doestn't treat these drivesr any different than any other file you may want to add to the CD. Welcome, Alex T., to MSFN!

@ColMaki: Cool! @Bilou: I think most of those issues are resolved in the next test release. Check it out, please. I had not tested with Windows 2000. In the future, please do not cut and paste XPCREATE.CMD code on the Internet. Merci. @GrndZero: That should be possible, but please read the (new) EULA first. I'm closing this thread, as the next test version has been released.

You've made the right decision, DerRickster, I'm sure you will never regret it. As for your question, yes you can. You may want to test the new version, which does all that automatically.

Look at the shortcuts timestamps: they are created when the profile is created, after setup, not before. Cannot delete them if they are not there, can you now? (Which is also the reason you had a "File not found" error.)They are created during ActiveSetup. ActiveSetup is a per user setup that exists for IE, OE, WMP, amongst others, and runs upon first logon per user.

Thanks for that, Apollyon. Not meaning to burst your bubble ... I do believe most everyone here is aware of that site! But it never hurts to check! On the XPCREATE Web Site, there is a list of hotfixes needed, and for most of them, a google with the KB number will take to the MS page on first hit. See ya 'round, Hillbilly! (You started it!)

You cannot create a user because you are not trying! Where is the "Create User" code? Something like NET USER Jacques Menteur I'm sure it is on the Unattended Guide ...

There is an option to clear on exit (or is it startup ... ), but I've never heard of disabling it. Might be this one, I'm not sure: [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main] "Save_Session_History_On_Exit"="no"

Good to hear, X'Mac. 56K? You must be desperate!

I would highly suspect that Remote Desktop Web Service would need to enable IIS to work.

For one, the SVCPACK.INF file has different headers for the Version Info (Major, Minor, Build) Signature="$Windows NT$" MajorVersion=5 MinorVersion=2 BuildNumber=3790

All sounds too wierd for me ... I still believe CMDLINES.TXT should be in, and ONLY in, $OEM$, which is at the root of the CD. (CD install.) (Duplicate, identical files is not a technically sound solution, especialy on a machine that has not yet been FUBARed) .\ should preceed any file names for files in that directory, though it does not always appear to be "needed" Also, don't be confused between \, .\, and ..\ \ = Root of current drive .\ = Current directory ..\ = Parent directory ("up one level")

That's a new one on me. XPCREATE itself only modifies SVCPACK.INF, DOSNET.SIF, and TXTSETUP.SIF if SATA drivers are added. None of those files should effect IIS ...

No problem, "such a dork" ! Welcome to MSFN!

Thanks, mmarable. Works for me!

The ISO file already has the boot image. Nero, or similar, can simply be used to burn the ISO to CD, as can CDBURN. The command would look something like: CDBURN.EXE D: XPCREATE.ISO -SPEED MAXCDBURN.EXE and XPCREATE.ISO should be in the same directory, from which you run them.

Ah, now I remember the 3ware drivers. I did not include them, in part for the fact that, as you mention, there are two .sys file for one piece of hardware, and also because the file names did not fit in with my "conventions". There are other drivers that also list two .sys file, but not many. I am at a great disadvantage with neither hardware nor time to test these different configurations. But like I said, XPCREATE does work for the majority. Next time I pass through the SATA integration code, I'll see what I can come up with, but that is not for the near future.

Long file names in SVCPACK.INF. I always used to disable 8.3, but that with XCOPY is a very nice and easy way to rename the files for ISO compatability. You are fine using either version at the moment: the end result has not changed.

@johann83: From the website, I quote: I know which one is missing ...http://greenmachine.msfnhosting.com/XPCREATE/begin.htm

@johann83: First look at your logs files do not show anything. I have made a few more changes, and will be posted an updated version of XPCTEST either today or tomorrow. I did just test this latest version, and did not have the symptoms you mention. I have also switched from file size to check sum for download file integration, so in this way we can be sure we are using the exact same failsafe list. So hang tight a bit, and then please test the next release, and see if the problem is still there. I'll get back to you ... @mmarable: Basically, when run from a "clean installation" (e.g. no XPCREATE.INI) XPCREATE will look for the XP source, and copy it into the XPCREATE directory. It will update/create XPCREATE.INI to reflect the new source location. Also, when a service pack is slipstreamed, it is slipstreamed into the source, not the working copy, and the service pack is put aside for safe keeping in the OLDFILES directory. In short, yes, the XP CD is only needed the first time.

Jjazz: Yes, I know, making those lists is no fun ... You should not need SVC-OPK, as putting DX9 in SVC-PRE will run it BEFORE any of the hotfixes. UXTHEME.DLL is in it's own cab file. I also think you can use the ENU version. In any event, if you compress it (MAKECAB UXTHEME.DLL UXTHEME.DL_), and put UXTHEME.DL_ in FILESCD\I386, where WINNT.SIF is, that should be enough to install it. I'm not so sure that looks like an XPCREATE SVCPACK.INF, at least not anymore!

In such cases I make a loop in the command script that will sleep X seconds a Y number of times, or until a specific file can be found, such as the shortcuts for the program being installed. I'm not sure how to make it process dependednt, but there is always a way ...