Jeronimo

Have not noticed any problems with WMI service need to check. I did have problems running diskperf, which might not be necessary after removal of the Reliability and Performance monitor (I think loadperf.dll is part of this).

I ran vLite for component removal with everything except IE and core and another time with only IE core left out. Tonight I will compare the file differences in files and see if copying the missing files to my current installation might solve the issue.

I also have this, only component that I can think of that could cause this (and which I selected additionally for removal) is Application Experience.

I tested it yesterday once more and it seems that Internet Explorer is the cause. I tried to check with Process Monitor to see if I could find what was the cause, but was unsuccesful. I compared a log of Process Monitor from my current system where it does not work, with the other installation where it did work.

Ok, either one of the following is the cause: IE, Windows Firewall, Performance Counters, Realiability and Performanc Monitor. I will try with only Performance Counters kept and see what it does.

OK, I'll see what I can test out. What I did not mention is that this occured both under my current installtion :-) as well as an additional test with the same preset under a new installation to verify the isue.

When I run vLite and choose all options except component removal, then I can run the DirectX web installer as available from here. However, when used with Vista ran by vLite with preset as attached. I get an errormessage at initialization stating to look at DXError.log an DirectX.log. DXError.log [05/03/07 22:42:37] module: DXWSetup(Apr 4 2007), file: dxwsetup.cpp, line: 65, function: CDXWSetup::CDXWSetup Failed API: CoCreateInstance() Error: (0x80040154) - Klasse is niet geregistreerd -------------------- [05/03/07 22:42:37] module: DXWSetup(Apr 4 2007), file: dxupdate.cpp, line: 431, function: CDXWSetup::DownloadDXUpdate Failed API: CoCreateInstance() Error: (0x80040154) - Klasse is niet geregistreerd -------------------- [05/03/07 22:42:37] module: DXWSetup(Apr 4 2007), file: psheets.cpp, line: 447, function: PreinstDlgProc CDXWSetup::DownloadDXUpdate() failed.DirectX.log 05/03/07 22:42:35: DXWSetup: ***** DXWSETUP ***** 05/03/07 22:42:35: DXWSetup: WinMain() 05/03/07 22:42:35: DXWSetup: IsIA64(): not IA64. 05/03/07 22:42:35: DXWSetup: Unable to get Version on target file C:\Windows\system32\directx\websetup\dsetup.dll 05/03/07 22:42:35: DXWSetup: Installed file C:\Windows\system32\directx\websetup\dsetup.dll 05/03/07 22:42:35: DXWSetup: Unable to get Version on target file C:\Windows\system32\directx\websetup\dsetup32.dll 05/03/07 22:42:35: DXWSetup: Installed file C:\Windows\system32\directx\websetup\dsetup32.dll 05/03/07 22:42:35: DXWSetup: GetDXVersion(): Unable to get RC string from registry. 05/03/07 22:42:35: DXWSetup: DirectX Version: 4.09.00.0904.00 05/03/07 22:42:35: DXWSetup: Setup Version: 4.09.00.0904.00 05/03/07 22:42:35: DXWSetup: A newer version of DirectX have been installed already. 05/03/07 22:42:35: dsetup32: IsWow64(): running on Wow64. 05/03/07 22:42:37: DXWSetup: CDXWSetup::CDXWSetup() 05/03/07 22:42:37: DXWSetup: CDXWSetup::CDXWSetup(): CoCreateInstance() failed, error = 0x80040154. 05/03/07 22:42:37: DXWSetup: CDXWSetup::DownloadDXUpdate() 05/03/07 22:42:37: DXWSetup: CDXWSetup::DownloadDXUpdate(): CoCreateInstance() failed, error = 0x80040154. 05/03/07 22:42:37: DXWSetup: PreinstDlgProc(): CDXWSetup::DownloadDXUpdate() failed. 05/03/07 22:42:37: DXWSetup: WM_APP_ENDDOWNLOAD 05/03/07 22:43:53: DXWSetup: CDXWSetup::~CDXWSetup() 05/03/07 22:43:54: DXWSetup: CreatePropertySheet() returns -9. 05/03/07 22:43:54: DXWSetup: Deleted file C:\Windows\system32\directx\websetup\dsetup.dll. 05/03/07 22:43:54: DXWSetup: Deleted file C:\Windows\system32\directx\websetup\dsetup32.dll.

Not sure if there would be any gain taken from it. Polling might not give anoticeable dealy (if you know how the principle works). Only if there is an actual task waiting, when polled, then there will be a delay. Would it matter if a device is attached and appropriate action is taken after 1 second instead of 30us? I do not think so and if it would really matter, then I will think that Microsoft would have set the polling time lower per default. Because if this would cause noticeable decrease in performance, they would not set it up like this.

Alternative for the above tweak of wiSHmaKeR Install: reg add HKCR\CLSID\{21EC2020-3AEA-1069-A2DD-08002B30309D}\Shell\Open\Command /ve /d "Explorer.exe ::{21EC2020-3AEA-1069-A2DD-08002B30309D}" /f reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\MyComputer\NameSpace\{21EC2020-3AEA-1069-A2DD-08002B30309D} /ve /d "Control Panel" /f Uninstall: reg delete HKCR\CLSID\{21EC2020-3AEA-1069-A2DD-08002B30309D}\Shell /f reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\MyComputer\NameSpace\{21EC2020-3AEA-1069-A2DD-08002B30309D} /f

Yeah, but I think the experience gained on nLite helped him with vLite. Vista is a different OS and requires a different aproach, but still he knows what issues he can encounter and how to deal with those, although there is some new stuff as well. I think once a stable version has been reached with enough components and functions to start with, it will come out of beta stage and then new components will be removable, tweaks added, bugs solved along the way. Mind though this all is pure speculation (I can not look into the brain of nuhi, if I could I would be making nVista )

I am also still not convinced. I understand the concept of ReadyBoost and Superfetch and both can be of no use in certain environments. Someone who opens his E-mail and webbrowser and uses those 2 applications during a specific amount of time, will not benefit from Superfetch that much, nor will someone who will start up his pc and then 1 game. However it does not hut either, I have to see the facts before I will believe that Superfetch locks memory required by other applications. If your application requires a certain amount of memory, then Superfetch will release this. Off course this will take time, but I do not think it is swapped to disk or the game uses swap space instead (e.g. pagefile). ReadyBoost is a nice addition especially for systems with less environment, it is a level of caching between memory and pagefile, which can be very quick for small files. It is not a replacement for memory or pagefile, it is a compliment for both (quick access because it does not have to come from disk, but it will not be required to be kept in memory). THG has some nice benchmarks on both, although I have not seen any real life examples, which state that either service has a positive or negative impact. Fractions of seconds have been scientifically proven to be of great importance to how efficient people work. If people are to wait over a fifth of a second, their efficiency decreases. But if this is relevant, when you start an application? I think it would matter when you are busy within an application, but if it would matter when you just start. I still need to be convinced of the up- or downside, however the implementation of the functions and the few reviews I have seen (THG as stated above) leads me to believe it will not hurt enabling them.

@raymerjacque could you provide us with information, where you got this wisdom?

It has been exactly a month since release of 0.95 beta (0.9 beta was 1,5 month prior to that) so my guess would be possible in a week or 2. However there is no schedule/planning so no guarantees.

I came to learn that installing unattended only works from boot, not when installing/upgrading from within windows (by use of autorun/setup). Not sure if you are running into the same issue. I also believe the next beta of vLite might contain unattended options, maybe if you wait for this a bit and try it from that it will work (then you can compare differences in the unattended file).

@Bjorland. I asume e:\temp is where you keep your files and is not where you have mounted your Vista-image to with imagex. You need to include the image directory and Windows-directory as well, add the following to the pkgmgr command: /o:"DRIVE:\MOUNT-DIR;DRIVE:\MOUNT-DIR\Windows" Also the xml-way (/n:UPDATE.xml) seems to work better than the cabinet way (/e:...).

That is an Outlook 2007 update, not a Vista update nor Vista spefic.

Does this mean you will integrate WinFS in the next beta?! I am ready to be surprised and test a new version

No it is intended as a future option, but not yet part of vLite. See the sticky topic in the Vista forum, there is more information on updates and integration methods if you are interested.

You can add it from under Programs and components from the control panel, it is not installed by default. See enable/disbale Windows components and the is the Telnet Client.

Ok, seems I have had more luck this time. Only prep option does not seem to work... peimg /prep c:\vista.image /f Hulpprogramma voor het instellen van een installatiekopie voor een vóórinstallatie-omgeving voor Windows Copyright (C) Microsoft Corporation. Alle rechten voorbehouden. [==========================100,0%========================= ] Kan de bewerking met statuscode 0x80070005 niet uitvoeren. Maybe I am doing something wrong or maybe prep is not meant for "install.wim"?

I had this issue when installing XP after Vista as Vista criples the bootloader (at least for me it did). Default tools were not sufficient, I had to play around with Vista Boot Pro. Install the OS you would like on C and then take a careful look at this tool.

If you are an Administrator: takeown /f "System Volume Information" /R /A cacls "System Volume Information" /T /C /E /P Administrators:F Normal Users (run commands under an administrator accout/elevated prompt): takeown /f "System Volume Information" /R cacls "System Volume Information" /T /C /E /P Users:F (note that "Users" is dependant on your Vista language)

@nepsyde if you have a router to connect you to the internet you can try the following... Type the following on the commandline and reboot: netsh interface tcp set global autotuninglevel=restricted If MSN still can not connect after reboot, then a bit more rigoreous: netsh interface tcp set global autotuninglevel=disabled Again reboot and if MSN still can not connect, then this is a different issue and you can restore the setting with: netsh interface tcp set global autotuninglevel=normal

Removing makes no sence, since Vista will keep adding the folder again and again. Only thing I do is make it readable, so when I accidently click on it in Explorer I do not get an errormessage.

Again been busy quite a few hours, but neither pkgmgr nor peimg can integrate ALL updates properly with the given methods (winbeta, the above, another topic from FireGeier, spacesurfer). peimg did not allow integration of 50% of my updates and pkgmgr causes peimg /list to give an errormessage and stops after displaying the first update. This is becoming ridiculous. I hope vLite has some integration option soon, because I am getting sick and tired of it. For the record I am integrating into an original install.wim not ran by vLite.