GreenMachine

Personally, I vote for the "fluke": error with neither reason nor rhyme. This time, the DOS window was relevant: there should never be any lines not starting with a Time Stamp. "File Not Found", though not a "hard" error that will cause problems, is a logical error. Fixed.

@iwod: Add DELTEMP=YES to XPCREATE.INI, and that should take care of your problems. You may want to add DELROOT=YES as well, and this will delete CDROOT after creating XPCREATE.ISO as well.

Yes, CDIMAGE takes only one directory and [possibly] one boot image as input. Note that using this command line may require all files needed during text based setup (blue screen) to be in UPPERCASE. Otherwise, try the command line from the http://unattended.msfn.org site. Can't tell you about NERO, but I think if setup correctly, that can work as well.

I don't really see how that error is related to SWFLASH.CAB, or even XPCREATE. Why does someone have that file locked? Note that anti-virus programs can cause undesired results when trying to keep up with XPCREATE file creation. Eliminate the white space in DOISO = NO in your XPCREATE.INI file, and you should be OK.

Yes, I can think of at least three off the top of my head ... Just Copyrighted ... And why I listened, though I did have the "CleanUp" Option in a Previous Incarnation. You guessed it! Look at the last 5 lines of code ... This one liner should do ... change the parts in Bold if desired. Welcome home!

Sounds like a Happy Ending!

XPCREATE.INI will simply set any values found inside. There are a few "hidden" options ... Alanoll can certainly tell you more about using the REMOVE scripts that I. I'm sure there is a way to make it work, I just have no time for debugiing the XPCREATE/jdeboeck combination. Simply a question of time ... Be careful modifying XPCREATE code ... No only is it copyrighted, but any modifications YOU make, will need to be made again if (and when) a new version comes out. On the other hand, there is no reason not to incorporate a CALL to XPCREATE from your own script, which then can call jdeboeck's scripts. Good luck!

Looks like you have the right one. I suspect that the problem is/was something else. We'll look at the logs ...

Cool! They both look like good tools, but are not at all the same. Thanks!

I've been looking for something to do this for a while, with no luck. I can't get this to work either: this switch generates the "help" screen (where it is not listed), and does not check that box. Anyone have it working?

Good idea: File sizes have been added. Did those missing fixes ever show up?

Seems the file did get corrupted. Odd... Fixed now.

SWFLASH.CAB should be 483,750 Bytes. It is linked to all over the Internet, and in any web page that uses Flash. The version number is listed in the .INF file inside the .CAB.

Ciao, cyberchicken, and welcome to XPCREATE! Now ... for your bashing! Two of your three requests are already incorporated in XPCREATE: DOISO = YES|NO DOCD = YES|NO Set these variable in XPCREATE.INI. I have added options to delete files at the end of the process, as you suggested, and this will be in the next release (your new ... last release took 6 weeks, and that just happened...) Concerning XPCREATE.LOG, that is meant for error reporting back to me, and I have it just where I like it. On the other hand, not being new to coding myself, I must disagree. XPCREATE.CMD is clean and minimally redundent. Most importantly, it is legible and beautiful. Every variable and sub routine have a "raison d'etre", perhaps not in your context, but certainly in mine. As for maintainability, I would say error free code is maintainable code. There hasn't been a "real" bug found in weeks. The whole XPCREATE process lends itself to Command Script. I have had no trouble with loops or calls. And while I am not against the learning process, my objective here is not to bring prehistoric batch coding to the "Script Kiddies". I've put a lot of time into getting the code just right. I have no interest or desire to debug others modifications to code that is not broken. It involves too much time, and honestly, "What's in it for me?" On a happier note, I'm glad you got it to work for you! PS Just saw your second post. Please read HERE. Ciao!

Hmmmmmm.....

Deja vu ...

I'd check your memory chips, or overheating ... So, what's the SATA status?

All's well that ends well! Case closed!

I use MAKESCUT from ScriptLogic.

Geeez, now I remember why I never updated this thing ... If that file is indeed present, and named HALACPI.DLL (UPPERCASE), and XPCREATE made the ISO, I vote for CD-RW error. Especially since HALACPI.DLL does not seem to be an updated file. Alors?

I don't get it ... that was the old version. Before I pull out too many hairs, do you have another PC you could try it on? Just doesn't make sense to crap out in the middle of a file copy. Anybody else have success/failure with the new version? At this point, I am suspecting the POS box ... please let me know if that is not it. Also, if you could edit your last posts and remove the attachments, MSFN would probably be gratefull! Thanks

I hate when that happens ... Please use the LATEST XPCREATE, but replace XPCREATE.CMD with the attached (older) version, and report back. This should still work for the newer SATA/RAID list. Waiting on you ... (Attachment removed)

ZEROADS, eh? Never heard of it ... I am not sure I understand your question/problem. If you are asking about RAID configuration of the controller, I believe this should be done with some sort of DOS based utiltity. If the problem is in XPCREATE finding your SATA/RAID drivers, be sure that they are placed in the FILESCD\$OEM$\$1\DRIVERS directory, or sub-directory.

XPCREATE can be used either way: either before, or after, the rest of your unattended installation is created. I prefer to use it as the last step, where it will merge and add all the files, and burn the CD in one go. My reasoning is that by keeping all the files seperate until CD/ISO creation, it is considerably easier to maintain and keep updated.

Hey, I care! However, your topic title was so efficient, there was no need to read the thread. Damned good, I'd say! What isn't working? I would be interested in seeing your XPCREATE.LOG files, and getting an exact listing of updates/hotfixes you used.