GreenMachine

Sorry, I don't. I've also been googling +trojan +wget +"web server" +tutorial, in varying combinations. Checked with the AV sites, etc ... Now I'm in the process of reading every thread in this forum. Boring ... Thanks for the suggestion!

Thanks, Virindi. I'm begining to wonder if that post has been deleted. I think it was near a post you did that mentioned the UPX compressed version. The one I saw was very very small: I thnk only a few Kbyte. Somehow that file lead me to a site, and there was also a small FTP/Web server, which make me think of the Worm/Trojan aspect. This WGET version also launched the downloaded file, as an option. It also seemed to do little else, other than download: that is what I am looking for the HotFix downloader. WGET has many options, most of which I would not need. I do think it was Jjazz that had posted it. (Where are you, Jjazz? Vacation time in France?) Thanks again for the reply, but I really do want to find that version. I guess I'll just keep bumping these posts till I get it!

This post probably doesn't belong here, as it is not "Unattended" as such, and I already posted it in the XPCREATE forum. But I'm not getting what I'm looing for, and I think everyone there has already seen it so, with out further ado ... I'm looing for a version of WGET that is very small, simple, and limited in functionality. From what I can gather, it is a version compliled for a worm or trojan. It was only a few Kbyte in size. My previous post is HERE. I had a copy of it once, but I cannot find it. If anyone can help me out, I would be most appreciative. Thanks!

I believe you need to remove the "LegacyDisable" reg key. Search for it with RegEdit.

Thanks much, swampy. The version I seem to remember (and I'm loosing my mind trying to find) was wicked small. I think it had very limited functionality, but it would do just what I need. I'm sure someone posted it on the XPCREATE forum, and I'm going nuts trying to find it. I guess it's bedtime in this northern, western hemisphere: maybe my memory/eyes/search will work better tomorrow. Thanks again for posting, and the link.

HELP! Somebody on this forum (I first thought Bilou_Gateux, then Jjazz) suggested I use WGET to download the hotfixes, and posted a link to a VERY, VERY small version of WGET. This version was one used by virus/trojans, that would silently download a file, and then silently launch the program. The file size was, as I said, very, very small: under 10 Kb. The same person also posted a link to an equally small MD5 CheckSum routine, again under 5 Kb. The WGET routine also showed up in McAfee as a trojan/virus. I've been searching for a few hours now, and I cannot find the post, the copy of the files I thought I had, or a link to these miniscule versions. If anyone has a link to the post or the files, or would be so kind as to zip and attach the files, they will "make my day". Anyone?

The idea is V.V. nice, the implementation is not as great. XPCREATE is cleaner and more efficient. To see what I mean, try both methods on a single hotfix.

CDSOURCE has been slipstreamed with the Service Pack Two. (Note WIN51IP.SP2 in the Left Side Orphans)

I knew I got get a laugh outta ya! Because it's you ... I'll think about it.

Thanks, all, for the input. The English list HAS been updated for SP2, and this thread wins the prize for being the first to notice. For SP1 fixes, you are on your own. Which route to take (SP1 or SP2) is purely a matter of opinion. I will continue to focus on the latest Microsoft recommended updates as my baseline. I do tend to agree with what Virindi has said.

I hope you found the threads that mention this current ... shortcoming ... of XPCREATE. It'll be fixed upon next update. For now the easiest solution is to let XPCREATE just do it's thing without touching XPCREATE.INI the first run, then there should be less that needs tinkering with.

@pinion: There are many different ways. The Undattended forum has many, as does the XPlode forum. Not really an XPCREATE specific thing.

@dvokt: 1) Don't know. Certainly not before any post SP2 fixes come out. 2) Yes. 3) You could just edit the files in CDROOT, and create another ISO from there, using your favorite ISO creator. XPCREATE doent have an opion for that: it would need to re-run the whole shebang. 4) Change to YES any time: does not effect future XPCREATIONS, and they are deleted first thing of a new run.

@ReSiVe: Thanks! Done. @mmarable: You didn't read the question ... @Wraith. Oh, never mind ...EDIT:: Top post updated.

Listen to Alanoll. Also, your IP HAS been logged.

Sure it is possible: the program hasn't changed. Just add the files you want, and set DLAUTO=NO.

It really is OK as is. Try DVDBURN from Microsoft. Good to know, arter all those years of the girls telling me otherwise!

The ISO IS bootable. Just burn it.

Finally, I'm in the process of making some bug fixes. Specifically, the following: Setting XPSOURCE in XPCREATE.INI causes Boot image extraction / "Cannot find Boot Image" error. Source Language not correctly determined. FILESCD directory cannot be used accross different XPCREATE directories. (FILESCD hardcoded.) "This folder may safely be deleted.txt" in file IE6 causes errors in non-English versions. User cannot add RAIDDRIVER.OEM files manually. Raid drivers with multiple .SYS files not handled. No SVCPACK directory created if there is nothing to add to it. If you can remember other errors that I said I would be looking into for the next version, AND CAN POINT ME TO THE THREAD IN WHICH I SAID IT, please post a link to that post in this thread. I am NOT interested in other "bugs", or feature/functionality requests, so please. please, please don't post any of that. Just bugs that have already been pointed out, and that I said I would be fixing. EDIT:: This post updated as developement progresses.

@viceversa: I know you, and I know you indeed want discussion, not arguement. Otherwise, I probably would have stayed out of what can become such an opinionated thread! I appreciate your questions/answers. My case is a little different (surprised?). My set of reg tweaks is not that big. I have it divided into seperate files: HKCU, HKCR, HKLM. The HKCU ones are the only ones of interest here, and in my case these only contain Microsoft related settings. They do need to be re-evaluated with SP2, but there really isn't much, so it's no big deal. In fact, they are, for the most part, insignificant, and I honestly haven't bothered yet. They seem to work. As for the program specific stuff, I package most my installers in an IExpress package (surprised again?), that often does the install, and a little more. For example, there are very few programs that put the icons where I want them (AllUser profile, correct directory). If there are any registry settings needed, I add them to my installer package. If I update the installer, the reg settings are right there, and I will (hopefully) adjust them for the new version. All this keeps things modular, and easy to manage for the poor memory I've got (me, not my PC). Much easier to keep the little things straight, then the whole picture. Roaming profiles are a different thing, and I strongly believe that these are this is the only way to go in a corporate environment. Backup, controll, etc., is much easier to manage. These profiles are used on many different machines, with different hardware and software configurations. I have the profile, create a fictitious user, give it administrator rights, install the new program, and then save the profile back to the server and use as the new default. I may even manually edit the user profile's registry, mainly to remove old settings, but I like to avoid that. Now, if we are talking about the hobbiest here that has one PC, uses one profile, and is looking for something very user specific (user directories, drive letters, favorite collections, themes, etc.), that's a horse of a different color, and I do see how this idea can work for them. My one-track mind just considers even my own installations as a "generic" install, thus it's not for me. Keeps me from doing one thing here, one thing there. Again, for reasons of ease (to me). I really believe in keeping it all modualr, and a copied NTUSER.DAT doesn't fit in my scheme. Still, most important is to do what you (any you) is most comfortable with. (Rainy day here, must get me verbose!)

@VTshadow: Actually, XPCREATE gets SP2 to slipstream fine, just haven't really tested it. The legacy switch, -s, is still supported. (Great for those of us that get tired of looking fir all those letters in integrate!) I will fix the "no svcpack directory" error in the next release. @guysmiley: Glad you can take a joke: perhaps WiseOne would be more fitting! Again, thanks for the pointers.

Hmmm. No answer for you at the moment, but I'll keep you posted. Anyone else with a ... different ... language experiencing this kind of problem? If so, what language. Also, you'll need 2K/XP/2K3 (not sure about NT) as the delayed expansion is a critical part of the code (!VARIABLE! vs %VARIABLE%). WIN9X/ME wont cut it.

Darn it: too slow again. I never get to be first! Happy I am (even if he got a longer title than me!), and I'm sure it will make things MUCH easier for Benjamin. Been There, Done That! I also noticed we all made a step up on the Forum Home Page. Nah, viseversa, no Green jacket for me: makes it to hard for the others to spot me on the golf course! I'll stick to Yellow, like Lance Armstrong. Again. my respect and thanks to the poor fellahs that have to manage us all!

COPYSOURCE is responsible for ... copying the source to the HDD, and updates XPCREATE.INI accordingly. (See Web Site section XPCREATE.INI ) Don't know why it did not create the ISO the first time. Disk space? It looks like it DID work for the attached log: XPISO=c:\tmp\XPCREATE.ISO (user modified in XPCREATE.INI). The bad run may have more info in the log. It didn't burn a CD, as CDBURNER=F should be CDBURNER=F: (user modified in XPCREATE.INI), assuming F is your CD Burner. As for DotNetFX, the What Goes Where and Current Hotfixes section of the Web Site should get you straightened out on that. I'll be getting rid of those "File Not Found" errors ... soon. As they are not "critical", they will have to wait till I have time. As for the documentation, even out of date, I did get to throw a couple RTMs at ya! I wont be updating that until AFTER any program changes. Thanks for attaching LOGFILES.CAB. It makes it much easier to analyze, and find things that may be forgotten. The simplest way is still to just do a clean install, double click on XPCREATE.CMD once for the directory structures, a second time, whilst connected to the Internet, and let it rip. (Or crawl.) Still, I'd say all in all you done good, and your XPCREATION is more than likely fine. Welcome to MSFN, dvokt, and ... Happy XPCREATIONS! (Thanks for the compliment/thanks as well - never hurts!)

I've toyed with it before. Would have to vote "No Go". While they hardware specific data may NOT be in that NTUSER.DAT, software specific data sometimes is. For example, you install program X Version 101(at T-13, for example), which then sets up, via the HKCU section of the registry, to use %USERPROFILE%\My Documents\X-Files\RecievedData as the default file transfer data. You may, or may not, have included that in your profile. Then you update your Windows Distribution to use Program X Version 102, which has a new "feature", and uses directory %USERPROFILE%\My Documents\X-Files\Quarentine. ... Time to update your default profile. That is, if you know about the new registry settings it is supposed to add. Furthermore, some hardware devices have User Profile settings, particularly graphic adapters with "Profiles". That raises the issue of hardware compatabilty. While the settings most likely will not cause problems, they do cause registry bloat. Lastly, it requires you to "inspect" every modification to your Distribution more carefully, which is never fun. Having a controlled set of registry imports, and a command script for certain other modifications work's fine for me. I also find it easier to maintain, understand, and refer to when I have questions or doubts. To check what is in the default user, you have to load the hive, and look that way. If you know what you are looking for ... That said, on domain servers, I do keep a default profile that I copy for each new user. And these Roaming Profiles do attach themselves to different machines with different hardware and software configurations, and I've had next to zero problems with that. You wanted disscussion! There's the GreenMachine take!