datalife

I am very happy to testing this new release, with SP2+NEW-IE7+RWMU (ENG & IT) and SP3 build 3205 For next release i suggest the integration of famous thirdy part readyboost for windows xp Bye Bye p.s. ... now the next step is new vLite release...

... i run nLite 1.4RC2 from Vista HomePremium SP1 v.275 and all work fine... now testing into XP SP3 v.3205

nlite v.1.4.RC2 Thanks ... all work fine... and iso is more little respect to v1.3 final

Windows XP Service Pack 3 Beta Build: 2600.xpsp.070831-1912 (Service Pack 3, v.3205) is first "Public Beta Preview" for beta testers only https://login.live.com/login.srf?wa=wsignin...40&id=64416 and i am one of that! Read http://www.softwareheadlines.com/modules/p...icle.php/228355 Please: don't flame me more Thanks!

Testing stopped! SP3 3205 not accept my LEGAL! VOL KEY. This KEY work fine with SP2 and SP3 3180 with latest WGA! ... umh! I remenber: this is the same error of the latest SP2 beta build before first RC (accept only beta CONNECT key) I try to install RETAIL VOL and after SP3 3205, but if is off-topics, ending post. Thanks. p.s. Nuhi waiting your reply.

Visual Tweaks are redundant!

Testing now! with SP3 build 5.1.2600.3205 and IE7 build 7.0.5730.13 @ nuhi: officially Nlite 1.4 RC ic compatible and/or work with SP3 and new IE7? Thanks p.s. ... new vLite?

I don't know... speeking with Nuhi. Bye.

umh! misconfigration of your vLite dot ini ? Or real bug ? Install clean vLite to any separate directory and retest.

All N version's dont have "ALL MEDIA PLAYER FILES AND MODULES RELATED" but somes windows functionalities don't work. Bye.

For my personal opinion is not possible to compare RTM or SP1 build of Vista with RTM or SP1 vLited build of Vista All the vLited build of Vista (RTM or SP1) are more more fast respect normal RTM or SP1 of vista not vLited vLite and nLite are the best configuration tools software and they optimize always the performances of Windows For example: xpLite remove some windows components but not optimizing never! The same nLited are more realiable fast and optimized

CONFIRM but others issues have found... pardon modified my reply

... vLite 1.1b work with new SP1 but only breaks some "Control Panel - Features" not critical.

I dont know but for me the ammount of ram is not another brick in the wall... for one SPx-Upgrade...

Tested to Dell Insiron 9400 2GB ram DDR2 666Mhz + HDD 7200 rpm + readyboost with HISD 4GB For now noting special! Vista + KB938979 and KB938194 Hotfixes or Vista + Service Pack, 1 v165 are more equal. The performance and memory allocation are the same of Windows Web Server 2008 beta 3 (the service pack is the same v165) Boot time is 24/28 sec's (40/80 sec's to full load desk+wireless+cpuidle+admuncher+avast+spamihilator) Shutdown is 10/12 sec's Installation time 15 minut's (TOTAL time to load first desktop) Phisical memory available 2045 -271MB (nvidia shared memory) Cache 378 Free memory available 1233 p.s. peerguardian2 not load and not work!!! p.p.s. no others test possible delete and format vista32bitsp1 partition now Enjoy

Windows Vista 32bit Service Pack 1, v.165 Full build tag 6001.16549.070628-1825 Full ISO name x86fre_client_en-us-fb1cfre_en_dvd.iso DVD label fb1cfre_en_dvd Windows Internet Explorer 7.0.6001.16549 Windows Media Player 11.0.6001.6334 This Hotfixes is already integrated KB 936330_100 Service Pack KB 937287 Hotfix KB 938371_1 Update KB 937286_2 Service Pack New setup installation screen with more reboot add. New bootloader with F8 functions add. All "Language Pack" available from windowsupdate are not compatible and not install. Evaluation time end 365 days after install. The KB938979 and KB938194 Hotfixes are not need. vLite 1.0 Final and vLite 1.1 beta fail "Turn Windows Features on/off" (with and without unattended setup) My personal opinion is: Vista with KB938979/KB938194 are more fast and reliable, for now!

... vLiting with 1.1b and testing now... Update: vLite 1.0 Final and vLite 1.1 beta fail "Turn Windows Features on/off" (with and without unattended setup)

Is official Microsoft.Windows.Vista.SP1.32Bit.Build.6001.16549.DVD Think of it more as a pre-beta build of SP1 than an actual beta build. Full Build tag is: 6001.16549.070628-1825 Retail/OEM key to activate. Enjoy

Is: official M$ SP1 beta testing, unofficial SP1, or only all available Hotfixes integrated?

Yeah! All problem solved. Thanks to Jamieo and Nuhi

No, I don't think so. My issue relates only to unattend.xml - Removal using the 'Turn Windows features on or off' UI works as expected. Yeah! All problem solved. Thanks to Jamieo and Nuhi

Broken autounattend.xml functionality (New) The 'servicing' section within autounattend.xml can no longer be used with a vLited image since 1.1b. Setup aborts just prior to the first reboot complaining that settings cannot be applied. I use this section to uninstall some games (see snippet below) but there are many other things that can be added, removed, or otherwise configured within this section... This is the same of my last report ? @Nuhi: somes serious issues in vLite 1.0 and 1.1 1° problem -> affected vLite 1.0 and 1.1 version's After remove Internet Explorer component with vLite (v1.0/1.1) all the function in tab "protection" of ie7 internet options stop to work. Is not possible to add custom site's list in security categories. The system return popup error with red x circle. If Internet Explorer componente is not removed with vLite all work fine. With IE component removed from vLite - > error show img-001 - img-002 - img-003 Without IE component removed from vLite -> all work fine img-000 2° problem -> affected only vLite 1.1 version -> MUI integration problem "seriuos problem" problen not exist in vLite 1.0 with same .ini configuration Test to retail and genuine "localized" italian distribution of Vista (homepremium and ultimate) source VISTA-IT-DVD 32/64bit Retail and Genuine "localized" italian distribution of vista has alredy built-in IT-MUI-LANGUAGE integrate. vLite recognize from "integration" tab Italiam MUI language alredy installed (if this is or not enabled) img-011 - From vLited 1.1 image installation of Vista is not possible remove or add more installed default modules or functionality of SO like (differential compression, XPS support, HTTP print support, games and more...) - Procedure stop and system return error popup with "red x circle" - Event viewer return red error and the word MUI is present in all description's. - The problem not exist with vLite 1.0 same .ini configuration - Tested with and without add other "new pathes" Vista image created with vLite 1.0 img-004 - img-005 - img-006 - img-007 - img-008 Vista image created with vLite 1.1 img-009 - img-010 Nuhi this is one very crucial problem please your attention! P.S. Complete eventviewer .evtx archive (to load in local event viewer) and .ini presets files (to local load in vLite or notepad) are attached to this post. Thanks _eventviewer_vLite11_error.7z _ini_presets.7z

@ Nuhi My opinios is: problem related to MUI integration e/o "new-pathces" integration. All "red error" in eventviewer are referred to any Vista "removed components" from vLite in my custom image! For me one possible fast solution is: separate mui integration in vLite from tab Integration and insert it to any separate tab called "MUI INTEGRATION" Other idea is split all into 3 separated tabs called "Drivers Integration" "Patches Integration" "MUI Integration" and ability users from tab "Tasks" to enable odr disable it for working vLite in different mode like vLite 1.0. For example one identical release with only this changes build v.1.1 reload or v1.1.1 or v1.2 beta This separation permit to inegrate patches/drivers or mui in indipendent modality and separate error. vLite 1.0 Final not have this problem and MUI and Pathces/Drivers integration not are present, but vLite reload integrate also all new "components removal" of vLite 1.1. beta. Thanks

@nuhi - I add more screenshots, .ini preset's and complete evtx file to load in your local event viewer! Bye.

Nuhi, is not this my question. Now post "screenshot images" of problem... re-read post... pardon yelling... my intention is only resolve and use... remember...