GreenMachine

My take ... if you need to add .cat (signature) files, as when slipstreaming hotfixes, use SVCPACK.INF. If not, use CMDLINES.TXT. If nothing else works, use GuiRunOnce. Different strokes for different folks ...

Bingo ...

I vaguely remember something about that ... did you try WITHOUT the 4.7 update? Or using WMS 5.0? If not, please do try, and report your findings. Log file looks fine. Good luck ...

When in doubt ... attach your log file to the post ... try the above suggestions and let us know.

@SurfD: On a PIII 1 Ghz, 396 Mb RAM, standard IDE disks I do a complete XPCREATE with ALL latest hotfixes AND service packs I need 55 minutes. On an Athlon 2200 with 256 Mb RAM on a SATA disk, I need 30 minutes. Compresssing and decompressing do require time, but experience tells me that your HDD is the weak link in this chain. No way you should need more than an hour, unless you are doing 2 at the same time ... @daywalker03: You, on the other hand, are a bit fast ... did you remember to copy the files?

Welcome to XPCREATE and MSFN, Drpepperman. Go to Start - Run and type SYSOCMGR. If this is the same error you are seeing REMOVE Hotfix 817778 !!!!

Welcome to MSFN, mniceguy81. Just as XtremeMaC sugessts, if there is an XPCREATE problem, attach the log file to your post. However, I am not sure that is your case. In fact, I am not sure that you have tried and experienced a problem. Have you? The only additional requirements you shold have are to place your SATA and Intel Chiupset drivers in the $OEM$ ... directory, indicate the correct path in OEMPnPDriversPath in WINNT.SIF, and you will be OK.

You're biggest loss is probably in disk access time. Firstly, my CDSOURCE is on HDD already, though unless you have less a 15X burner, file copy should not take more than 5-10 minutes MAX. Secondly, I use a SATA disk with a ton of free space, and that make an enourmous difference. Other than that I run on an Athlon 2200, which is far from the latest and greatest. If nothing else, free up some disk space and defragment you HDD ...

For the long answer .... LOOK HERE

Welcome to MSFN, SurfD! As I recall, SVC-PRE should be fine ...

Welcome to MSFN, x243. There is a tool, XPCREATE, that will slipstream the hotfixes and updates, and has been used by many with various degrees of success for Windows 2000. In my tests, I get the big fat 0 you are looking for. You can get there from one of the links below ...

@retailmessiah: I justed tested (again) the MSJAVWU.EXE update in SVC-HF2, and it worked fine on Virtual PC. I am not sure what you mean about taking enough switches ...

You got me on this on, Jazz. From the looks of the log, I would not expect an error. Please try again with the slightly modified, attached XPCREATE.CMD, and post your XPCREATE.LOG file once again. Waiting on you ...

You are correct, shareef59, the drivers should be in the $OEM$\$1\DRIVERS\ subdirectory, contrary to the web site documentation. The only "verification" you can get in VPC, is to look at the bottom status line during text mode setup, and see if the drivers show just before copying files. It is, however, easy to miss, and can hardly be considered a valid test, as such. You still need to test live, but you can run setup on your existing box, see if you can choose a partition on the SATA controller, and abort the installatoin before any changes are made to your hard disk.

Thanks for that, shareef59. one of these days I will get around to updating that web site ...

Welcome, ljdyjakon, to MSFN and XPCREATE. I have not tried 64 bit XP, though I suspect that driver integration should be similar. Please email or post a copy of your drivers, and I will see what I can do. I generally insist on drivers that have been tested using a floppy and the F6 method, but I guess in your case that will not be possible. If, however, you have the possibility to add a floppy to your system, even if only for testing, I would suggest that you do so. Waiting on you ...

Welcome to XPCREATE, Jazz! Hate to surprise you ... but my first suspicion is always user error ... Find the file XPCREATE.LOG that was used when creating thee CD (or try again, and save that file). It should be in the NEWFILES subdirectory. Attach (not post) with your next post, and I will take a look when I get a chance.

Let's see ... Were the SATA drivers you were using signed or not? The driver that XPCREATE integrates is only used during text mode setup, and driver signing is not an issue, as XP is not yet able to validate signatures at this point of the setup. I'm not 100% sure on the details ... but I do install my signed 3112 drivers without the Ignore thingy. The XPCREATE.CAB file only contains the info that will be added to the TXTSETUP.INF file. The actual files themselves are not used. The only similarity it has with XP drivers files, is that they both use the CAB archive format. One test would be to try the driver integration without XPCREATE, and see if that makes a difference. Another posibility when existing fies are reported as not found is UPPERCASE/lowercase issues. I do uppercase all the XPCREATE created files, but not the files in FILESCD. Just a thought ... Other than that I don't have any more ideas. Feel free to post as you discover more ...

Welcome to MSFN, cooldownguy86. I think I understand the question ... You would need to change this on a case by case basis, as each installation is unique. There are also some applications that do not allow this option. I do not have the specific switches for Norton AV. Try the Switches Forum.

Welcome to MSFN, zehninguem. I assume this is a typo: $OEM# (should be $OEM$) If not, that would be a problem. XPCREATE really does nothing special for any of the drivers, so I have to suspect that the problem lies elsewhere. The "DriverSigningPolicy=Ignore" must be because you were using unsigned drivers. There should be signed versions for that controller. Sorry I cannot be of more help, but I bet you will find in the end that the problem was silly; a typo, or a wrongly placed file, or something similar. Good luck!

What's wrong with this picture? Sorry, couldn't help myself! Personally, I encourage any and all. Keep up the good work!

Building the ISO can be a tricky issue. With XPCREATE all the XP system files (e.g. all those copied from the CD) are uppercased. I believe all, with the exception of some HTML doc in the DOCS directory, are named with the 8.3 file name convention. All files XPCREATE adds to the CD are named 8.3 UPPER. The CDIMAGE switches used require this. If files are listed as missing, yet are in fact present, I would look for these types of errors.

I don't know how many different ways there are ... XPCREATE does it in two steps: First SP extraction START "Slipstreaming SP" %STARTSWITCH% "SPACKS\%%~nI.EXE" -X:TEMP\SPACKS -USecond, integration: START "Slipstreaming SP" %STARTSWITCH% "TEMP\SPACKS\I386\UPDATE\UPDATE.EXE" -S:CDROOT -UI do it in two steps instead of one, to determine the extracted-to directory name, and delete afterwards.

No prob. I only got 'em because I remembered. Now that I think of it, I wonder how those memory cells escaped reset ...

Welcome to MSFN, Jamie. For the Identity settings, look HERE. For the passport thingy, you can't do better than follow baliktad's advice HERE