Kelsenellenelvian

That is for "old-school" use of WPI and unattended setups. Fist off WPI (The whole folder "WPI") is place at the root of your disk. There is no need to waste time or space by copying all of the files over. See pic at bottom of post Second off your folder structure is way wrong for your $OEM$ folder. $OEM$\$1\Install In other words you have 1 folder named "$oem$" and in that another folder named "$1" and in that folder another one named "install"

@ sirmor = Its already there. Under the commands tab pick the following: jscript={createshortcut} a small wizard will popup giving you many, many options to make shortcuts.

No, I am sorry. It isn't really just nLite's EULA. nLite modifies many files even if all you are doing is slipstreaming drivers. This is severly against the MS EULA within windows itself. Now sad to say that any non-personal use of this can and probably would be extrememly frowned upon by MS. It isn't that fact really that you are a (Arguably so) non-profit agency. It is the fact that you are using nLite to deploy Windows on many many PC's. nLite and its creator Nuhi caould be held responsible if anything goes wrong without the clause of non commercial usage. The fact of what you removed opens many security holes in Windows and sensitive information could be released. As for wanting to save time there are many applications out there that combined can do most of what you want to achive. Driverspacks as you already know is fine to be used in your situation. Also removing AU and or the security center can be somewhat achived by disabling them during the installation process (Even the winnt.sif file can achieve this).

You need to do that anyways (Reformat all pc's) nLite is not for business or corporate use! Before you say anything else, YES a school is considered a business or corporation & you agreed to the EULA during installation of nLite...

inceni infix! NOT FREE, but VERY good!

Same this with strels link I get it going way off the screen. 1280x1024 res IE8 on Win7

Considering that they are not (nLite & vLite) for buisiness or corporation usage I would say no...

These should work fine for your mini. http://www.wpiw.net/sata_ide.rar

Here ya go!

????Sould be $OEM$

%CSIDL_COMMON_DESKTOPDIRECTORY% Needs to be added to the variables section for Vista and 7.

Microsoft recommends that you use the update switch because of the intergate switch failure issue with xp sp2b. Autostreamer uses this switch when it works. http://majorgeeks.com/AutoStreamer_d4444.html Sigh more research done. (Couldn't sleep.)

Further Googling Shows this:

I have heard of a version of XP that was released with a sp2b on it. That SP actually contained a couple of extra hotfixes alongside the normal SP. After a bit of googling I did find that that disk label IS an SP2b disk. While it should work fine for your slipstream I would be curious as to which files are in the I386\SVCPACK dir. Windows XP SP2b CD Labels Code: Windows XP Professional (SP2b) Upgrade = VX2PCCP_EN

Roguespears runtimes pack is know to cause this error...

Please DO NOT refer to any of us here as "Dude"! OK then how did you create your disk? Please provide any session and or bat files you used. Just how sure are you?

**Shudders** Most cases that come with power supplies pre-added in have very inferior PS units... Out of the 4 I have gotten I have had 4 blow out all within 6 months of usage.

With that kinda attitude and the obvious patience you have shown maybe you are better off just sticking with a standard Win7 installation...

What? All this time and I have had that on my drive? Nod never detected it either. I am very sorry to the OP. I never suspected that file as it came from a trusted source. Edit: Nod detects it now as I try to move or delete it. I am glad I haven't used it for ages.

The problem is with your au3 files. I used to use several au3 scripts and never had an issue with them, yours are closing out too early.

WPI by itself cannot bypass this. You will HAVE to add a sleep command to wait until the installer is finished or correct the tgup commands so that the parent command (i.e. a .bat file or auto-it file) waits for the installer to finish before closing. WPI waits for the installer (The original .bat or au3 file) not any sub-processes....

Daaaaaaaaaaaaaaaaaaaaamn Cluberti! Your just that good! Bravo!

HE DIDN'T NAME IT SO!!! MS is calling it that! Get off his effing back man. Come on you are better than this.

Yes you create your own Install folder. Choose other and a text box will automagically appear for you to add your own custom category in. After that each one that you define will be saved into the drop down box.

Not a snowballs chance in... Well you know. Win7 is a COMPLETLY different beast!