GreenMachine

This would: [HKLM\Software\Microsoft\Windows\CurrentVersion\Run] "ZNclient.exe"=- "UltEng.exe"=-

1) Create the diskette. From there you want either the files in the root directory, or a directory named something like WINXP. 2) I don't do Sun Java. If you have a silent installer, it could go in SVC-EXE. 3) MDAC_TYP could go in SVC-DAS, but I don't use it anymore, because it needs an update that I cannot do until reboot. My workaround is to just update the current (2.71) instead of install the new (2.8) 4) You are correct, it goes in SVC-POS, as stated on the Web Site ... 5) 4 out of 5 ain't too bad. And you really should not open yourself up with such questions!

Windows Registry Editor Version 5.00 ; This prevents a bad program from running ... [HKLM\Software\Microsoft\Windows\CurrentVersion\Run] "BadProgram"=- ; This deletes the whole **** key - probably not a good thing ... [-HKLM\Software\Microsoft\Windows\CurrentVersion\Run]

Bald yet? First, simplify things. For what you want to work, you need apply the settings to the HKCU at T-13. The settings to HKU are not important: they only effect the system when no one is logged on, e.g. boot up. The do NOT effect the default user. Not do you want to be applying the tweaks twice. No need: do it right the first time. So ... eliminate the calls to the .reg files from RunOnceEx, get rid of the *HKUD.reg file, and debug from there. That is the way it is meant to work. Good luck! http://greenmachine.msfnhosting.com/READING/cmdlines.htm

The mystery continues! I forget things all the time when I leave the house in the morning, why not them?

Strange, I thought SP2 brought them back. Look-see here: http://www.msfn.org/board/index.php?showto...indpost&p=92446

I'm really not a drivers expert: I'll leave RyanVM, the Driver Man, to that! As for integrating .CAB files, I don't see how that would work. Once option would be to pack the CAB file with IExpress, as well as a CMD script that extracted the files, and call the script from the IExpress command. Nobody wants to believe me ... There are many that start with the full kit and kaboudle, only to have it not work, and then go back to the "failsafe" package. An original XP CD, the hotfixes from the Current Hotfixes list, and a blank CD are all you need, and all you should use, in getting started. Once you know you can get one working, the frustration thing is much less pronounced. As for the attitude ... we try to keep it sane. I sometimes think they put me in my own corner so I would stop picking on the others! Welcone, CodeDead, to MSFN and XPCREATE. Hope your stay is enjoyable!

Yes, those would be the indeo codecs. I believe they are in SP1 and not SP1A. (You did not believe JVM was really the only difference, did you?) @bonedaddy: If you are going to lay it out like poetry, at least make it rhyme! I mean, what's up with all that white space? Seriously, I have trouble connecting sentences over paragraphs, but I'm like that. @nuhi: Looks like you got a winner here. I haven't tried it out, because I am too busy making my XP CD bigger, but you sure have woken the natives! If you need some advice on crowd control, let me know! (And mostly, keep up the good work.)

That is what I was starting to think as well. What's the point in lewtting you do all the work, if I can't keep up on my end? However, I think I see a RyanVM -> XPCREATE.CAB parser in the calling. I hate doing the same tasks twice. On a side note, I did try adding as many SATA drivers as I could. Works fine virtually, but as soon as I try in my box with a 3112 DataLink card ... BSOD. Conflict somewhere, and it sure seems hardware dependent.

Ahhh ... once again an ignored problem goes away! Glad you got it figured out. Been a while since I tried the SILENTINSTALL=NO thingy. Dates from the days when I had less faith in the XPCREATOR.

Correct again, RyanVM. It is a value in WINNT.SIF, like ProfilesDir. The full answer is probably in the REF.CHM file, but the key is certainly WINNT.SIF. There is also ProgramFilesDir and CommonProgramFilesDir (or something like that ... )

Zip and mail me your drivers. I will try to add them to the list of drivers XPCREATE can integrate. Then you should be able to add them into an XPCREATE CD as the other SATA.RAID drivers - there is a page about this: http://greenmachine.msfnhosting.com/XPCREATE/raid.htm. The link from RyanVM will tell you how to do this yourself. Or, as already stated, use RyanVM's SATA Pack. Still ... I would like a copy of your drivers ...

I think Alanoll has the most experience here. Also, that thread you were talking about seems to have been bumped up. Tests, tests and more tests. Don't forget to post your results, for the next guy.

I was wondering when I would here something ... and probably not the last! 'Welcome, swampy! Operator Error: Get's 'em every time ...

I'm a little busy, but why all that new fangled stuff? Can't be much more than 5 lines of batch code ... I'll let you know when I get around to the Green Version, you keep me posted for the MSI!

First look suggests copy 3 files to system32, add the CLSID registry entries, and REGSVR32 the big file. I doubt that there is much more to it.

That would be interesting. I would guess right click, Install, or call RUNDLL and pass it some parameters. You could pack that into IExpress, and it calls the inf, and gets the files from the cab. Got a link?

Wonder why they didn't put V4? I use the MSI version, wrapped in IEXPRESS. Not sure that counts as a non-MSI version, but it installs fine from SVCPACK.INF. After XPCREATE does its thing, you should see it in the NEWFILES directory. It uses the same switches as type II hotfixes.

Use the StubPath in Active Setup. It is designed for exactly that purpose: one time per user setup. Here is a link to how it is set up for a virus. You should do similar, execpt avoid the auto-propogation. I admit, I did not read the article, but a glance suggested it has enough info, If not ... google. http://www.megasecurity.org/Trojaninfo/sub....2_startup.html

Can someone elaborate? I had trouble slipstreaming SP2 into a VLK XP, so I just downloaded the complete XP/SP2 ISO. Is it true that you cannot slipstream SP2 into a VLK XP? I did not use the /integrate switch: I used the standard procedure which (appeared to have) worked, until install time. If true, what is the solution? Preslipped SP2 VLK edition? Ryan, you know ... ?

CMDLINES.TXT? http://greenmachine.msfnhosting.com/READING/cmdlines.htm

Let's see ... slipstream a hotfix into an update, to slipstream into a distribution. I think I'll think about that AFTER SP2. Maybe ...

I completly understand that your company wants all CDs the same, but naming them all D: is an error, and you would be best off explaining that to those responsible. Due to the way Windows assigns drive letters, you are just asking for trouble, as you are starting to discover ... I always use K: (and possibly L: and M: and N:) for my CD drive(s). Eliminates many, many problems ... Still, since you seem desperate, I attached the script I use for changing my CD drive letter from <whatever:> to K:. I belive the MOUNTVOL program called can be used similarly for HDDs, Since D: will (possibly) already be in use, you will need to do it in steps (D -> X, E -> D, X -> E). As for your FORMAT script, that is straight batch coding: ask a question, process the result, and take action depending on the evaluation. Perhaps google for DOS, BATCH, FORMAT, etc. There is nothing special about such a script, but I am not going to write it for you, and the answers about scripting are out there ... sorry. SETCD.CMD SETCD.CMD

I do believe those three ( all "old" ) just cannot be confirmed by MBSA. They are OK: no worries.

@GrimSage: If you see a "File not found" error on the screen, I would like a past of the screen text, as well as the log files. Though this should not be a "hard" error, I would like to see why it does not find something that it expects to be there. I looks like you are using MBSA to determine the installation results. You are fine: it cannot verify three hotfixes, and there is a WMP update that is "greater" than the minimum required. I also use MSJVM, and there is no reason it should not install, except that possibly your DELL XP source is "funky" ... You could try the Baliktad combination of Distribution and Update. It is listed in one of the other threads near the top of the forum. @it_ybd: The reason MDAC 2.8 is not there, is that it also requires a hotfix, and I was unable to install 2.8 and update it in the same go. I suppose you could install it, and do the update from GuiRunOnce. I suppose ...