nuhi

You don't need a preset, just use vLite as you wish, that is the whole point. Read the text on the vLite pages carefully.

It integrates the whole folder because the whole folder is the normal driver package. However I am planning to make it selectable since some manufacturers put XP and Vista drivers at the same place. Best is to delete the inf file for which you are certain that is not needed, before the integration.

You do not burn the files as they are, first make the ISO from vLite. Select the ISO page in vLite - Tasks, read the info on the right. After the ISO is made run Nero and choose Recorder - Burn Image.

Glad to hear that it is on the full one as well. Maybe you disable some services in both situations? Anyway you can filter the Event Log yourself, double click the even you want and then on the right play with the Filter Current Custom View. It is just for the Custom view but still it can help during debugging.

If you used latest then your issue isn't vLite, many people have that issue on the full Windows as well, browse through the Logitech forum. Please let us know if you find your solution.

Updated hotfixes have v# in the name, like KB00000v2. About the second part why would you torture your ISO so much, take the clean ISO and integrate only the newest.

Install that OS virtually with internet support enabled in the virtual machine. Run Windows Update, and choose all the criticals it detects, decide yourself on the other ones. Each hotfix detected will have a Details link which you can follow to the MS site to download it aside, if that is too much fuss then let the WU downloads all that you select and then after the reboot pick the CAB files from the C:\Windows\SoftwareDistribution which look like the hotfixes you just installed and integrate those.

It's install.wim, not wam. There is a guide linked on the vlite.net, all the information is in there.

vLite v1.1 or v1.1.1? That registry load error was fixed in v1.1.1, happened only when ran from XP.

Hm weird indeed. I don't put such clueless messages into the error popups. Could be the extract/compress control that is not sending the proper error message. I tried the hotfix shown in your progress bar and it worked fine, unfortunately. If your nLite or CD files path has non-ACSII characters, like French special characters, then try moving the Hotfix, nLite and CD files each to their own folder named something simple like: c:\hotfixes c:\nlite c:\xp cd

There is no bug, if that is what you are asking.

Since nLite reads those zones automatically and integrating some hotfixes changes those files then try this: integrate what you integrate usually, then after it's done rerun nlite and configure the rest. It should be fine then. Gonna see about rereading the updated files on the fly so this double run isn't necessary.

Interesting, gonna try that these days. If you can't wait or there is no solution then you can install XP virtually, like in Virtual PC. Copy CD content in some folder inside the virtual machine, use nlite to slipstream inside it, drop the folder back to the real machine and continue with configuration.

Ok for starters you are mixing Autorun with CD Boot. Autorun is what pops up on double click when it's there. For Windows to still have it keep the Manual Install component. Then you can either run Setup.exe from the root or winnt32.exe from the i386 folder. CD Boot is more preferable and your burned ISO can do it. Just set it in the bios to first boot from the CDROM or observe which hotkey is for the boot menu and use that to initiate CD boot on machine reboot. You will see some message during bios post like Press F12 for Boot Menu. Then with CD in the drive and pressing F12 and choosing CDROM it will say Press Any Key to boot... Ask Homer where is the any key

Next time when making ISO be sure to copy the whole CD, including the root files, not just the i386 folder.

Ok, I will need your preset used (last session.ini from that CD), please attach it.

For drivers no problem, integrate as many as you want Windows will choose the proper driver when detecting your hardware. About programs see about WPI and Xplode (i think that's the name) and see if they allow some sort of preset selection during runtime.

Ok, good. That unknown device can be for example Firewire and you removed the support. Can also be Smart Card when removed, LPT ports maybe...essentially the point is if you are not missing any functionality don't worry about it.

Can you post that link? Did you install some Firewall, tried to disable it? Tried other browsers? Some say try disabling javascript temporary to see if it helps. Basically it shouldn't be your issue, they all point to the server issue http://urbangiraffe.com/2005/08/20/mysterious-406-error/

I heard about this issue regardless of nLite. Haven't heard about the solution so I'll just fire at will. If you didn't remove Logical Disk Manager (in Cpanel - Administrative Tools - Computer Management) you can play with it from the Windows when you run it, then right-click your partition and make it Active if it isn't but be careful when tampering around partitions.

It sounds like you were trimming SP2 somehow? SP3 is bigger because it has more components, they are being added into the future version of nLite. If you extract it then select i386\update.exe for integration...but don't think that you don't need other files, they are used during integration, as in sp2.

Ok. It's selectable because next time you might want to use only that page, or you don't use it at all and continue to modify the folder after nLite is done.

For DX find the addon which does that (try the Application addons subforum in nLite forum). All drivers are to be extracted and integrated per folder which are displayed on the Insert - Multiple folders option. And of course if it says Win9x skip that. If it is Intel Chipset driver then you can run it and go to your Windows temp folder to find the extracted folder. It will have something like Driver and Driver64 in it.

Thx for the info. If you know this before making the ISO you can use Components - Advanced - Keep box and enter the files there for the keeping. I will see about adding some option to save those, components are Smartcards and WMP.

That helps. nLite returns signed syssetup.dll after the install to avoid such issues but since you do manual install from winpe then it might have got skipped. Do you use /unattend:winnt.sif switch? Can you try it next time just to confirm. Let me know if you do, thx.