Sonic

Last year I have this problem with usb mouse & keyboard and other standard peripheals ... To fix that I have deleted INFCACHE.1 and all *.pnf from C:\windows\inf , sometimes it works, but sometimes it doesn't work .. Try it , these files is just mecanism to speedup detection ... Have you used nLite and/or BTS drivers packs ?

I havn't really understand your problem but "NTLDR error" is about boot problem. To restore completety the boot of a windows xp system use same version cd of your current system (e.g. use sp2 cd if you have sp2 system) and try that method: 1) Boot from Windows XP CD and choose "repair" to boot to recovery console 2) Switch to C:\ and delete "NTDETECT.COM"; "NTLDR"; "boot.ini" 3) copy D:\i386\ntdetect.com copy D:\i386\ntldr 4) fixboot c: fixmbr bootcfg /rebuild edit: Use the method above if you have the NTLDR problem with just your system hard disc plugged.

hmm ... weird "bug" , it's not a surprise from Microsoft too

To start it : "C:\pathTo\FileZilla\FileZilla server.exe" /compat /start To stop it : "C:\pathTo\FileZilla\FileZilla server.exe" /compat /stop

yes you can just use the 60 patchs listed. I don't know/use Windows Updates Downloader 2.24, but I think it's okay.

From Post 1 of the topic: MS WINDOWS XP PRO SP2 - (60) means 60 updates available with IE7 & WMP11 & Windows Live Messenger installed. You can clear all your KB patches files and redownload the updated patches if you havn't updated your list more than 2 or 3 months because it's hard to find which are replaced/updated.

Official list on the board http://www.msfn.org/board/index.php?showtopic=86450 If you want to use the very official list you can use Catalog link from Windows Update but it's not easy to work with it, prefer the list from the_guy, it's perfect. I use that list at work without any problems.

Try to copy your script in Startup folder of Default User. I havn't tested but it can work. To self-destroy script use "delf /f %0" at the end of your script.

imagex is just to "capture" / clone a disk/partition. The setup of vista start with winpe which redeploy the real setup directly to the hard disk using imagex. You can mount and edit original install.wim (image of original install of vista) to add your customizations, and after unmount with saving changes to install.wim. But it's hard to maintain the source ... IMHO, use just autounattend.xml and $oem$ folder and remake dvd with oscdimg.exe

.NET 3.0 integrate full .NET 2.0 (you can see in the installer of 3.0), and you will see .NET 2.0 installed if you just install the 1.1 and 3.0. No need to install 2.0 before 3.0 ... Just use /q from original donwloaded setup from microsoft, same for language pack. Personnaly I don't integrate 3.0 because it's too "featured" for classic usage ... and take more long time to install ...

btw, Windows License Key isn't needed ... Your winnt.sif looks correct. Try to remake your CD without customization. After add just theme, and retry. IMHO, the problem is due to kernel boot files tuning. There are many kernel boot files to edit to achieve boot screen completely ...

It's caused by nLite. Check nlite.inf (uncab nlite.in_) if I remember all tweaks by nlite is in this file ... Delete lines about autologon ... btw, you can find more info in nLite forum ...

Hi all, There is new version of Kaspersky AntiVirus : 6.0.1.411. edits: At the begining I have created this topic to announce kav doesn't reboot but I have retested ... and it reboot same as other versions, I don't why I have some success at the beginning of my tests edit: Read new .mst mod. on http://www.msfn.org/board/index.php?showto...id=596118

It's same way as .net framework. If updates exist for 1.1, the full 2.0 will not fix the security of the 1.1 and 1.1 is needed too ... IMHO, for MSXML we must keep all differents version, no just the MSXML6.0 ... Reading http://www.microsoft.com/technet/security/...n/ms06-061.mspx I have understand the KB924191 is for XML version 3.0 , 4.0 and 6.0.

No native solution ... Perhaps with a third-party program which always scan drives and rename it ... but for me, I think there isn't really solution. Goodluck.

I set NetworkLocation to Work or Home, but when I come on desktop, the first window I have is to set my network location ... Event with <NetworkLocation>Work</NetworkLocation> tag set in oobeSystem passe. Anyone has successfully set network location ?

Sure, but one time I have an error when it's at root and now I keep it in sources ... I will re-organize my distribution folder at the end of unattend world of vista

Wrong, where have you seen that ?

3.0 fully replace the 2.0 because 3.0 is 2.0+new features. You can view the original 2.0 install in 3.0 package. I don't integrate 3.0 yet, I wait more feedbacks. edited.

For me, I put unattend.xml and $oem$ in sources folders. - sources \ $oem$ \ $1 \ FileWillBeAtRoot.txt - sources \ autounattend.xml (with UseConfigurationSet tag) That works well here.

Corrupted file I think ... try "imagex /info file.wim" with install.wim and boot.wim (winpe part ...)

Excuse me but you have set DNS server to 192.168.0.1 or you have just specified the gateway ? If DNS is set already to 192.168.0.1 and doesn't work , try to set DNS of your ISP.

Use "sysprep" deployement and after make a ghost image of sysprep' system ...

You win a new account level : banned

install.wim vLited, testing in progress ! Good job again nuhi !