GreenMachine

Perhaps, but with those Full Pint cans, what's a little water? And as Marie-Antionette said about their drought all those years ago: "Let them drink Fosters!" Hmmm ... Perhaps that is too loose of a translation! Anyways, you folk down under: Night when it should be day, Dead Winter in the middle of July, Football without helmets or quarterbacks, and baseball with a flat bat? Come on ...

The google box on the bottom of all pages works well, and in a familar way ..

Be careful: I can read dutch!

Yeah, like getting some more Foster brewing now that the drought's over !!!

Thanks, jjn1056. So much Plug and Play, I'd nearly forgot all the old hardware tricks.

Had to be something flakey somewhere: XPCREATE just couldn't randomly cause errors like that.

As we say in Yiddish ... Oiy Weh ... Hey there devil270975, good to see you around. Sorry, no answer for you, just wanted to say good to see you pop in again! Isn't there an option from that blue screen to delete the partition, and then you have to press "D" somewhere? I'd try myself ... but I have my data just where I want it now.

One of my favorites is Americans and British: seperated by a common language ...

175 Mb ISO? That's small ... I can only conclude that somehow the files are not being correctly copied off the CD. You could try ... - Running XPCREATE with DLAUTO=NO - After completion, verify the contents of the CDSOURCE directory against the CD itself. Once these are syncronized, including all "hidden" and system files, change DLAUTO=YES.

Something strange ... you're ISO file seems to be only about 400 Mb. That seems too small. My Windows XP home is about 469 Mb BEFORE adding any hotfixes or service packs. Also, the "failsafe" version should NOT have any files in the FILESCD directory, and you have many there. We'll need to remove the superflous files, and figure out where the other files went. Are you sure that you are using a "real" XP CD? You know, the one's with the Microsoft Hologram?

@Alanoll: I think that should fix you, too. I use MPC, too, sometimes, and I no linger see a box about which program to use for opening certain files. Like much of this stuff, it bugs the hell out of me so I have to have it my way, it is like pulling teeth to find the info somewhere, and then once I get it straightend out ... I flush my local buffers, and forget. Sometimes I write it down, and then forget where I wrote it ...

Hey, as many brain-cells as I've lost along the way, sometimes I'm lucky just to remember the way to the nearest bar! Enclosed is the list of Reg Edits I make concerning WMP. I hope I didn't miss anything, but these are extracted from my complete registry imports. All are called from SVCPACK (CMDLINES will be fine). The last section, Silly StubPaths, include ALL the StubPath entries that I edit, but I believe only one or two are pertinent to WMP. It will be more obvious when searching a non-modified registry, which I do not have. That should be enough. Please post back how it works, or if I can help you further. And if you have all you need, perhaps you can make a little "How To" page!!! Good luck! WMP.REG

Thanks, Dustinwmew, I'll look at it as soon as I can.

gosh posted on this subject long ago, and you may find more info on his web site.

@prathapml: Odd, I never have that screen, and it would bug me if I did! I do two things, and will share them with you from memeory, as I cannot get to my files at the moment. 1) I clear the StubPath entry for WMP. The StubPath entry is the code that runs once for each new user. 2) Remove a registry key for each supported type, e.g. GIF, JPG, AVI, that tells WMP NOT to run this type, or something. Sorry, my memory is very foggy on this one, but if you are intersted I'll dig it out later. The StubPath keys are look something like this: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{6BF52A52-394A-11d3-B153-00C04F79FAA6} (StubPath is a value for that key) In any event, my workaround is far from ugly, if you're still interested.

@Vel Straty: I guess I have not been paying enough attention. If you still have not got XPCREATE to work for you, that is terrible, especially after all the effort you have made, and the help you have been here. Please post you log file, and PM me with a description of what is happening (to save me some reading on this forum ... ), and I will try to look at it, though without my development computer and the Japanese version, this may be difficult. In any event, I do want to thank you for your tireless contributions! @Dustinwmew: I don't know what to tell you, except that I am quite sure your problem is something trivial, or silly. This is why I would prefer to see you test on another machine. Also, you mention $OEM$... this is not on the failsafe list ... Add your LOGFILES.CAB file, and I will see if anything jumps out at me. I seriously doubt that "playing" with the files by hand will solve your problems, and suspect that your current configuration is the troblemaker if you try ther basic, failsafe CD creation, and that does not work.

The Hotfix Lists should only list Microsoft sites for downloading, simply for "security" reasons. The one exception is DX9 OPK version, which is not available to the general public on Microsofts site. Furthermore, given the way in which file downloading is processed, adding any kind of logic, such as "Is the file available, Is the site up, Has the download timed out", etc., would require a complete re-write and re-think of the download code, and that is not in the current planning. Then again, the current planning only includes bug fixing and vacation till the end of the summer!

I hate to insist ... but dictating the hotfix lists for the average or non-technically inclined user is exactly what I am after. If such a User cannot download his own hotfixes, I sure don't want to try to debug his installation problems. WMP9 updates without installing WMP9, Java updates with SP1A, files renamed that adversly effects XPCREATE: those are headaches I will not have. Other threads here have shown how to create and use your own download list, without the need for a web server, so again, those with the ability can do it. Personally, I would think that just downloading and maintaining your own set of updates would be easier than updating a list: that is what I do ... Your two Canadian Cents are appreciated, as is all constructive criticism. Were this a commercial product, such options would probably be incorporated. But alas, only one user has admitted using this in a commercial environment (as noted in the EULA ... ). The Home Hobbiest, however, will still need to put on the thinking cap if more than the standard results are desired. Perhaps it comes down to this: making an id***-proof product will no doubtably attract idiots, and that I am not inclined to do for free. As for shrinking Windows, this is something I have never desired to try myself, but I believe both jdeboeck's scripts, and nLite have had success in the endeavor.

Do yourself a favor, and don't even bother trying to burn any XPCREATE CDs on that burner. Once they start failing, you will only waste your time and patience wondering whether the CD or data is at fault. On the other hand, there is no reason not to install from a local HDD source. As Bilou suggested, the key is in how you call WINNT.EXE, or WINNT32.EXE, and there is plenty af reading available on that.

Dutch translation: Create a shortcut to XPCREATE.CMD, and rename it "Drukken". Voila! Seriously, XPCREATE is NOT an interactive program, and the screen output and log files are for ME when debugging. I have specialized in multilingual programming for over 15 years, but XPCREATE in Dutch, German, Greek or Zulu will NOT happen ... unless someone wants to pay me a lot of money. On the other hand, if you are so inclined, you may translate the Web Site for me, and I will make room and links for it on the XPCREATE Web Site.

The log file reveals that there is no link for SP1, so naturally iOpus hangs there. The error is in the HFLIST file.

If you used XPCREATE from start to finish, you should not have these kind of errors, and adding files yourself will most likely not solve the problem. A few things to check: - Does the CD work in another computer? - Does the XPCREATE.ISO have the same problems in VMW/VPC? - Does running XPCREATE on a different PC display the same symptoms? - Are you using the failsafe Hotfix list from the Web Site, and nothing more?

Thanks, JBlond, and welcome to MSFN! Again, once I find time to update all the lists, I will! In the words of that other famous Bostonian: Ich bin ein Berliner! (JFK, 1961)

Looks like Bilou_Gateux has this HFLIST thing mastered! ... Now, to re-think those specs ... As for which updates are downloaded, I leave that to be dictated by Windows Update and the MBSA. Save's me from my own personal evaluation of what is "good" and "bad" ...