REBOOT & RUNONC~1.JS in the OEM folder...

[PVU]

I'm also using HFSLIP and I'm trying to see if there might be a conflict with switchless installers that are placed in my HFSVCPACK folder. A couple of these did not get installed (dotnet11sp1.exe of RyanVM and vbrun60sp6.exe), and that was unusual.

I think, dotnet11sp1.exe need a installed and ready worked Windows Installer Service... At install hotfix is this service not yet active!

I appreciate you even taking a crack at this one. I just put it out there to set-up the main question, but you might be dead on here. I'll have to ask about a possible order of install issue, but the installer service should have been a hotfix slipstream, and the installer service should have been up and running, with dotnet11sp1.exe installed latter (at T-13, I think). They just updated the code, so...

Again, thanks for even addressing this.

I have been textmode adding drivers with your CD creator, then running HFSLIP. This could be a problem with HFSLIP, and I'm not really questioning an "error" in the CD Creator, but I'm about to post my HFSLIP results and I just wanted to ask if you might think I should or could delete the REBOOT.EXE and or the RUNONC~1.JS.

I guess the question is this: If all I'm going to do with the CD Creator is textmode setup drivers, and not finish off the project with it, would it be OK to delete the REBOOT and JS? Are they critical?

If you integrated Soft with Creator, you need RUNONC~1.JS (RunOnceEx.js)
If you integrated a "Reboot" with Creator, you need Reboot.exe

1) Okay, I'm going to assume that basic drivers don't count. However, in this case, I did integrate complicated Intel video and Realtek audio drivers that included software installs. I don't know if this would create a conflict or not, but I'll assume that the CD Creater part of the install would require it. There could be a conflict due to HFSLIP's HFGUIRUNONCE folder.

I'll have to get on the installation source computer and do some digging. What I may have to do is just go conservative again and not worry about complicated drivers with software installs that may require something like <root>\$OEM$\$$\SYSTEM32 work.

2) Okay, I did not.

Thanks. Good luck on the Vista Creator. Say hello to Fernando for me.

BTW, this forum software keeps getting better. You gotta love the built-in text editor. All they need is spellcheck now (just kidding).

Be good.