GreenMachine

Depends what switches they need for silent installation. Figure that out, and then check the "What Goes Where" page on the Web Site: http://greenmachine.msfnhosting.com/XPCREATE/directories.htm

HomeNet ... Tried that in XP Pro or Windows 2000? EDIT:: Also requires Internet Connection Sharing ... Oh Brother ...

Perhaps a script using MOUNTVOL or DISKPART could solve your problems ... You would probably need to run this as a detached program, defined in WINNT.SIF, which does have certain limitations.

Thanks, MindMaster. Those are both good ideas, however ... I have passed the "adding features" deadline for the next version, and now am only interested in debugging what I have. I wll keep these comments in mind for a subsequent release.

Thanks for that. I've updated the next release to correct this problem. Until then ... use Volume Labels without spaces!

The problem is due to confussion between ESP and ESN as the identifier for Spanish. I have made the hotfix list available to both ESN and ESP, but note that this list is quite old, and does not include SP2.

You are not giving me much to go on ... Please read the following page: http://greenmachine.msfnhosting.com/XPCREATE/help.htm

Please see this page for information about XPCREATE.INI, and settings to disable downloading from the web: http://greenmachine.msfnhosting.com/XPCREATE/xpcreateini.htm Please see this page for information about where you can place files, such as the service pack: http://greenmachine.msfnhosting.com/XPCREATE/directories.htm

Sorry, no suggestions at this point. I also will not be able to look into this for a week at least. Do keep me posted if you discover something before I do!

That's correct. However, to eliminate confussion, note that it is not needed for the English versions. Please refer to the Web Site for the up-to-date current hotfix list.

XPCREATE currently should support Korean Windows, though I have not tested it. There is not, however, a hotfix list needed to allow for automatic downloading of the hotfixes. This must be done by someone with a Korean Version. Please visit the following page for information on how to create this Hotfix List: http://www.msfn.org/board/index.php?showtopic=20401

Thanks, Bilou_Gateux! I have also updated the Current Hotfixes List on the Web Site. Though I haven't checked, I would imagine that they are similar. Your list, however has links: Mine does not.

Thanks, MindMaster. I do believe that I have fixed all those issues. Some were fixed in the update I uploaded yesterday, and it did not look like you used that version. I may be mistaken ... 1a. I now copy this command file to the log before erasing the CD (done in the begining), and when burning the actual ISO (done, obviously, at the end) 1b. I cannot get that error to happen for me ... It also looks like there is an empty ISO file attempting to be burned. 2. Those should be gone now ... 3a. Should also be OK ... 3b. Those files do not go in the "right place", as I want them in the root of the current directory, for ease or coding. I know ... a bit lazy. Chalk it up to "historic" reasons. If I do a total rewrite, I will consider changing this. For now, too much work for a "cosmetic" change. That is also my reasoning for not creating the LOGFILES.CAB. In any event, LOGFILES.CAB only contains XPCREATE.LOG (which is always created) in a compressed form, to allow it to be attached to forum posts. It contains no more information than the pre-maturely aborted XPCREATE.LOG. Thanks for the report. I do believe that the current version (dated 19 SEP 2004 in the DOS Windows Title) fixes these issues, but I am testing at the same time as you. EDIT:: My tests on a previously written to CD work fine. Yours?

Thanks, MindMaster! Now you see why I have a limited test base! 1. I admit I rarely actually burn a CD/DVD ... I have reworked that part of the code a bit, and I think your problem may be solved. I will wait till I hear more, from the latest test version, before looking at it again. 2. Yes, "File not found" are harmless. Still, I thought I had caught them all. I need to know where exactly it is before I can eliminate it. 3. I am testing that now, and see that same message. I will correct it for the next test version, which I will post before this reply. 3. Those files are left because the XPCREATE run errored out. Log files and modified files that are added to the ISO (SVCPACK.INF, DOSNET.INF & TXTSETUP.SIF) are stored in NEWFILES for review. Temporary files (XPCT* are deleted) at the end. Apparently, you did not get that far. There was probably no LOGFILES.CAB, either. I am less worried about the actual installation at this point, particularly in your case. I am surprised that it gets to the burn code with no drive specified. That really should not be. Thanks for your help. I think I have fixed the issues you mention, so if you could download and test again ... I know that there was no LOGFILES.CAB created this time, but when there is, that is really the file I am most interested in. It dows not contain any personal information, other than the path to the files. That means if you run it on your desktop, and your desktop is in, for example, C:\Documents and Settings\%USERNAME%\Desktop, your username will be there. Additionally, every line that appears on the screen should be prefixed with a time stamp. If not, I made a boo-boo ... In this case, please cut and paste from the screen, and post that, so I can see where and what the boo-boo may be. Thanks again for your testing. Bilou! Don't bother with the GDI Detection Tool. It cannot be installed silently, and does nothing other than direct you to a web page that will tell you either you have products that MAY need an update, or that you are OK. It, in itself, does not update anything except the registry. I will email you a toll that will fool Windows into thinking that this "update" has been run. As for the language pack, I do belive it will work in SVC-X2M. I have also updated the list for Windows 2000, but only the downloadable version for ENU. Still, it does include the later JPEG update. Merci!

Not so sure: I think that you can pass with an invalid ProductKEY as well. There is a story on the Front Page. No, I guess I didn't want to see that stuff. Unfortunatly I know what they do ...

I still think that XPCREATE does a nicer job: they still run the update from SVCPACK, don't compress the files added to I386, and don't use the /O switch on the hotfix. That can get really slow when the number of fixes adds up. However, I do think there is something to be learned from what the /INTEGRATE option does. (Like the BRANCHES.INF) They should really talk to me before doing this stuff ...

That must be due to a premature reboot: thise files still should be in NEWFILES, as well as LOGFILES.CAB, and XPCREATE.LOG. The XPCREATE.LOG file will probably not show a completed run. I knew you would not like that, but I stand by that being the most acceptable solution, especially with the Manual Rename option (RENAMEF=NO)Hey: You edited your post before I could finish! (Put a tag in there, would you!) Anyway, I do believe that I included your suggestions. Let me know how your installation goes. EDIT: Mail me your HFLIST file, and I will upload it.

Time for work! (Just don't put your knee down: you might get roughed!)

So far it seems OK, but just wait till they release another Advanced Networking Package (a.k.a. 817778) type patch! Still, it will certainly be faster then integrating the files, and running the fixes from SVCPACK.INF. Let the RyanVM HotFix Pack fly!

@RyanVM: In that case, an .INF file is probably better suited. You could also use it to move/copy files. RaveRod did something along those lines long ago.

REG.EXE is really not bad, though not available in Windows 2000.

%DATE:~4,14% That should get the date without the "Sat". EDIT: You can only use variable with REG.EXE, not REGEDIT.EXE.

You cannot install that update silently, as it is not an "update" as such. It is simply a program that looks on the system to see if you have any offending software, tells you to go to Windows Update or Office Update if you have something that may need updating, and tells you all is OK if not. It is not an update, it a message box, so by definition cannot be silent. I use the registry setting to "fool" the system. EDIT: Something like "gdidettool.exe /q /c:""msiutil2.exe /? /?""" would not work, as it is not the msiutil2.exe file that is called, rather the .INF file inside the package. You would need to modify that file.

The variable %TIME% has the current time. I believe TCPIP.SYS is language independant, meaning one version for all languages, even though the installers are available in different languages.

Well, one zip file cannot contain all the info that this thread has, and the comments are as important, if not more, than the registry entries. There are many, many different and "conflicting" entries, so who is to decide whch is "correct": they both are "correct", albeit for different desires. I know that a 56Kb connections is not the tops, and I, myself, am sometimes on that, or worse. I speed it up other ways: use the Google search feature, turn off the images, use the cache. Still, I feel for those poor tortoises ... Still, a new thread loses all the comments that are relevant, and a search of the new thread only will not find much of what has been learned in the last year. There is also the option to print the whole topic, which will be lost. Not to mention the inability to cross thread quote topics. And keyword searches will end up here, not in the zip file that is only one persons opinion. Don't get me wrong: I am not, by any means, saying that the new thread should not be used. I'm sure not going to tell anyone anything about what or where to post, other than keep it civil, and keep it correct. But I ask the same of others, so please understand why I may post here. In short: Live and let live! And ... Viva la Difference!