GreenMachine

I've been terribly busy with some other things, and I am afraid to release it when I will not have time to support it. That said, I am quite confident it will be out before Santa!

No, there is no PDF file. Just the Web Site, linked in my signature. You really do need to work on the grammer/syntax: I get dizzy very easy ...

Good point: perhaps the CD does not have a boot sector. I think I need a little re-think here ...

Thought you'd get it!

Try this ... baptize.zip

A trick that often works in cases like this is to create a directory that has the same name as the txt file would have, and the text file cannot be created. In this case that would be: MKDIR UsageTrack.txt

Hmmm ... Did you try just adding swflash.cab to SVC-SWF? It worked for me as recently as yesterday ... XPCREATE then gets the version number from the .INF file, decompresses the XP inf file, updates the version number, and recompresses it. It also replaces the compressed .OCX file with the with the version from SWFLASH.CAB, also compressed. In fact, it basically does the steps you listed, just as it has for almost a year! That has been tested on thousands of XPCREATIONS! Get it here: http://download.macromedia.com/pub/shockwa...ash/swflash.cab

If XPCREATE does not find the WIndows CD on it's own, when the CD is in the CD drive, something is amiss from the get-go. Try it, as I suggested, installing XPCREATE in an empty directory, place the CD in the CD drive, and double click on XPCREATE.CMD. If it does not find the Windows Source, post the LOGFILES.CAB file. A hardware problem is not out of the question. If you have access to another PC, try the same there. If we cannot get this to work, I am not interested in a "work-around", such as pointing XPCREATE.INI to the CD Source: something is not working as it should, and ANY subsequent results cannot be "confirmed".

I am very surprised that XPCREATE does not find the source ... Are you using one of those pretty Microsoft CDs with the hologram on it? That MUST work before we look any further ...

It should be just slightly larger than your original Windows CD. I do believe that there is a problem with the Boot Image file, especially since the BOOTIMGFILE entry in the XPCREATE.INI file is no longer present. That is why I would suggest a re-do in a clean directory, and letting XPCREATE make the modifications to XPCREATE.INI. Also: what is in the BOOT directory?

Strange ... First, the log file does not seem complete: it should have a few more lines at the end. Second, for some reason, the BOOTFILE value is not in XPCREATE.INI. Is there an XPCTBOOT.BIN file in the BOOT directory? Third, it DOES look like the burn completed successfully: does the new CD have all the files, but is just noot booting? The simplest test would be to simply re-run XPCREATE, but this time in a new, empty directory, without modifying XPCREATE.INI by hand. Another interesting question is what is in the .ISO file that has been created. Does this ISO work with VPC/VMWare? Let me know ...

Remind me to hire that guy ... Thanks, Bilou!

**** ... I guess that is why I had the -D in there. And to think that I even typed CDIMAGE /? before posting ... Just another thing I learned long ago, and promptly forgot. Thanks, JD, for the reminder!

I have MiXeD CaSe file names under $OEM$ and no problems ... I use this command: CDIMAGE -LCDLABEL -YD -N -H -X -OCI -M -D -BXPCTBOOT.BIN CDROOT CDISO.ISO I do not think CDIMAGE itself converts to UPPERCASE, though I could be wrong (it does not for me ... )

If you get that message, there is no reason to bother trying the CD. I do believe that the answer is in the log file ... Please read here: http://greenmachine.msfnhosting.com/XPCREATE/help.htm The good news is that I doubt it is serious! Welcome to MSFN, sorenavery!

For the moment there is no support for DX9 (coming soon to a theater near you ... ). You could just use the DirectX OPK. It is referenced in the Unattended Guide (http://unattended.msfn.org). Put the OPK in SVC-PRE.

I guess that makes sense ... I'm not sure if I have tested on a "live" P4/Celeron, but I thought so ... In amy event, I see no harm adding that to my list, do I think I will! I do know about the WMC. You can use the package that I posted about in one of the other forums, and add it to SVC-POS, or SVC-CF2 (as it will soon be called). Thanks, TwoFiver!

You're welcome, too!

I finally ran HFNetChk: I know it reports errors, and I do not know where the invalid checksums come from, but I do believe everything is OK, especially as MBSA comes up clean. @urgan: I have not tried that update, but as you can see, I have no JScript issues. I'll add it to my To Do list to look into it. THanks for pointing it out.

Welcome to MSFN, Sadomi! That update, as well as any others that have the same icon, should go in SVC-HF1, though I have not yet tested it. Updates with the more typical setup icon generally go in SVC-HF2. Good luck!

Thanks for that tip, Body! I'll be looking in to this one ... soon!

Welcome to MSFN, sael! Glad it worked for you! I've never had that JScript issue. I get WIN2K installed just fine, with everything but the GDI+ tool, and for that there is a workaround that has been posted that I have yet to try. For now, I just update the registry accordingly. So ... what other "os image updater" tools did you try?

Actually, XPCREATE does not integrate DotNet, but it does install it, as well as the service pack, during WIndows Setup.

You're welcome!

Well, I guess I could have mentioned that simply adding the swflash.cab file to SVC-SWF would take care of Macromedia Flash ... THe rest of the issues are not XPCREATE related. Welcome to MSFN, Body! I'm not angry ... yet!