g-force

This is the link for the EN-version: http://www.microsoft.com/downloads/details...30-081805b2f90b As you see, SP2 or SP3 is required for install. I don`t know if this is even required for integration. Post your "Last Session.ini", as "johnhc" asked for.

I can`t see that in your "Last Session.ini" - you removed only languages. Did you run nLite more than one time against the same source?

Sorry, but I don`t see any screenshot? But now I got the point of the problem - sorry for misunderstanding.

Legal or not... You unpack the "MassStorage" of the DriverPack and integrate them with nLite. These drivers need to be integrated by "textmode" and need to contain a "txtsetup.oem", but these drivers from DP do not include the "txtsetup.oem" - so the drivers won`t work in textmode. You`ve got to use the "DriverBase" from DP.

Francesco, what`s the meaning of "became removable"? Since I use XP, nearly every hardware component is removable in the devicemanager. I´m logged on as administrator. If I´m logged on as restricted User, it`s maybe not possible. Maybe that`s the point - you`re logged on as administrator.

Link gives "Error 500 - Internal server error"

I can`t see any attachments...? > solved But let me say that "Owner" is a limitation of XP "Home", different to XP "Pro".

Are you installing XP from your running VISTA, or are you booting from your XPCD?

You don`t have to modify the ISO - just create it later. You create everything with nLite, like you did - except creating the ISO. After nLite has finished (without creating an ISO) you edit the "winnt.sif" in your XPCD-Folder. After that you start nLite again and only choose "Creating ISO", don`t load any old "Last Session". So nLite (in this 2. run) creates the ISO with your modifications. It won`t mess up the other settings.

Place the "runonceex.cmd directly in $OEM$. If you already worked with nLite, there`s a "comandlines.txt" in this folder, otherwise create one. Add a line in this file like "runonceex.cmd" - no path is needed because it`s in the same folder.

THX @ "geek" - helps my to get used to non-german boards on my way to be "more international".

I think another reboot isn`t the goal to achieve, cause it`s not needed at this time. Question is why your "runonceex.cmd" doesn`t run before desktop is loading the first time? Where is the "runonceex.cmd" and how is it executed? Edit: Didn`t see your edit - is the problem solved?

Did you see the functions included in nLite? 1. Programs-Path: http://german-nlite.org/wiki/index.php?tit...ation/Allgemein (3.) 2. Documents&Settings-Path: http://german-nlite.org/wiki/index.php?title=NLite:Optionen (1.5) Sorry for the german screeners, but i think you`ll get the point.

Some questions to be sure that we`re talking about the same things. 1. The screenshots are from VB or from your real PC? VB only emulates generic hardware, not your real hardware. 2. XP contains a poor compilation of drivers, you need all drivers for all your hardware, are you aware of that? 3. Even Ryan`s UpdatePack contains no drivers or driver-updates, are you aware of that?

Quick `n Dirty... There are a lot of Drivers missing, please install them.

What the ..... 1. You can`t integrate the .NET-Installers as a regular Hotfix. 2. In "RunOnceEx" you only set the Switches - but where are the Paths and Files???

That not true - i edited my Post No.3.

All Updates, or after SP3?

We should take a look at your "Last Session.ini", especially at the Addons and Hotfixes.

Did you ever get sound out of your VM?

You can use this: http://downloads.german-nlite.org/sonstige...1.installer.exe http://downloads.german-nlite.org/sonstige...c.installer.exe Regards, g-force (Admin @ german-nlite.org)

What about "Worst Poll ever"...

No need to open a new Thread for this, I add it here. A really good vLite-Guide especially for german speakink users you`ll find here: http://german-nlite.org/wiki/index.php?tit...te:VLite-Portal Regards, g-force

Accessible from here (Germany).

I think something gone wrong with the settings in nLite. It could be seen in "Last Session_u.ini" - but i beg you not to attach it here! A better way should be to change the settings on your current system, there`s no need to do a fresh install just because of that little bug. Open Regedit @ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon Before you change anything backup the entry (rightclick > export) !!! Take a look at "AutoAdminLogon" - i think it`s self-explaining.