Tomorrow

Not wanting to be pain in the butt or anything but on top of the forum it reads: Since this clearly seems individual part of WAIK and its defenetly not official MS link then i suggest you replace it with RC WAIK link to avoid any problems with admins: http://www.microsoft.com/downloads/details...35-d30ead27ef72

To the best of my knowledge no such update is coming.WAIK SP1 stays for SP2 images too

For hotfixes this might be ok but for Autounattended.xml you have to use WAIK for Vista SP1.

As i have said previously.Do not use the Unattended tab in vLite when vliting Windows 7.The unattended part will not work correctly and on worse case install will fail.Use WSIM(Windows System Image Manager) form WAIK(Windows Automated Installation Kit).WAIK for Windows 7 RC can be downloaded here: http://www.microsoft.com/downloads/details...35-d30ead27ef72 .

Ok i can confirm now that diskeeper is the culprit here.Heres the list of files Diskeeper defragmented on Windows 7 partition.I will ofcourse contact Diskeeper Support and let them know that such problem exists.Diskeeper version is Diskeeper 2009 Pro Premier 13.0.835.0 Servers are running RAM in exess of 12GB.It makes sense that Windows Server version goes x64 only.I dubt that much people will have 4GB when Windows 8 comes.I mean look.2GB was the norm a while ago but even today many still run barely 1GB.Not to mention netbooks where 4GB is really premium today(ASUS EEPC etch).Most still come with 1GB or 2GB conf. I have 2GB so i see no benefit from going x86 to x64 currently.I will go x64 once i build a new PC(4-8GB RAM) but not before.

MS has not said that it will be dropping 32bit support in Windows 8. And considering the still very big number of 32bit machines out there i seriously doubt they will stop supporting it in both Windows 8 & 9 .Windows 10 maybe... Simply put people who have less then 4GB of RAM in their pc are not gonna see any benefit from 64bit.And by todays standards that is most laptop users and nearly all cheap netbook users.

nope. final release of Vista SP2 RTM DVD image should be built on April 10, not any other date. Well mine seems legit anyway: 6002.18005.x86fre.lh_sp2rtm.090410-1830 DVD ISO with SP2 integrated

He doesn't owe us anything, including a reply. It's his life, and regardless of what anyone thinks, he's free to do with his life and his code what he pleases. Indeed he does not but it would be polite to do so.At the very least it would end the unnessesary topics popping up here time-to-time and put a stop to the speculation.So he does have few minutes to get behind PC and log in,but does not have a few minutes to post a quick annoucment?.Seems odd thats all... Atleast whats the status of the programs?.Dead,Halted or what?

I managed to integrate the following nicely: Internet Explorer 8.msu (English) Windows6.0-KB933713-x86 Dreamscene.cab Windows6.0-KB947506-v2-x86 Language Pack Fix.msu Only one that i could not integrate was: Internet Explorer 8 Estonian Language Pack.msu vLite complained that it does not recognize the hotfix. I know there is like 10 diff things you need that directly effect hotfix install, so thats why I had asked him that Yes well i used untouched SP2 image.Nothing was removed.I would not even consider trying to integrate hotfixes into vlited build.I always integrate everything first and remove things at the final stages to be on the safe side.Also this way image should be a bit smaller

I have stumbled into a showstopper bug possibly.Lately(well starting from Beta) ive had issue where Windows 7 builds become completely unbootable. Basicly i installed a build and used it for x amount of time.When i tryied booting it a few days later it showed only the Starting Windows text and no boot animation appeared.This has always been consistent with these.Same place-same symptoms.Nothing also helped. Startup Repair only gave vague idea what might be the case.System files integrity check produced code 0xa(not 0x0 wich means no erors) and once SR said A recent driver installation or upgrade may be preventing the system from booting.Other time it gave more vague Unspecified changes to system configuration might have caused this problem.The F8 advanced options were useless too.Safe mode always got stuck after loading the first line: C:\Windows\system32\system.Other options(as ntbtlog.txt,Last known good configuration etc seemed to not work at all).So now im(hopefully) close to figuring it out.I installed RC build.Only created one Restore point and then left it alone fow few days(that was monday).Today it booted fine.Ill wait for few more days to be sure. The only differences with other install(that became non-boot) are(things i did back in that install that could account for this problem): Installed Nvidia Display drivers(185.81).Installed Marvell Yukon NIC driver(Win7 includes older out-of-box) and installed ACPI ATK110 Utility(whatever it is) that Windows Update offered me. Additionally on my dualboot system(Vista Ultimate x86 SP2) Diskeeper was allowed to defragment the Windows 7 partition. In this install(that so far seems to be alive) i did not install any drivers and i completely disabled Diskeepers ability to defragment the Win7 partition.Lets see.Im suspecting either the ACPI utility or Diskeeper.If this install survives then im first gonna enable diskeeper and see if install boots after few days.if it does then im gonna install the ACPI utility and so on...

You can add one third party BITS dependancy: ESET NOD32 v4 Antivirus.When BITS service is disabled or not present on 32bit systems program install will not complete.On 64bit system result might be BSOD. This actually holds true for Vista too but neverless...

I managed to integrate the following nicely: Internet Explorer 8.msu (English) Windows6.0-KB933713-x86 Dreamscene.cab Windows6.0-KB947506-v2-x86 Language Pack Fix.msu Only one that i could not integrate was: Internet Explorer 8 Estonian Language Pack.msu vLite complained that it does not recognize the hotfix.

Thx for the info

What a joke .First off you complain that you have ton of downloading and installing to do.When it errors out you uninstall all(instead of coming here and doing search or asking help).Then you complain that you dont have the resources or experience needed to run Virtual machine(considering this i wonder if you could properly use even vlite).In the end you complain that you had waisted 2+ hours on this.Let me ask.Did anyone commanded you to try this,did you pay any money while doing this?.No.So its was your own risk.

Have you considered that maybe he is waiting FOR donations before starting work?.Or do you expect him to live from air and love?. Nuhi is currently at work to make money(assuming ppl didnt donate any).Naturally he doesent have time for development.If and when he returns it will be glorious :thumbup hoping for the best...

Good topic! If i find something i will let u know.I think i spotted Help mentioned as one component nessesary.I still have to confirm this tho. Ofcourse i hope everyone knows by now to avoid the Unattended tab

i walked the same way and tested it already. it´s working like a charm! all this sp2 reverse integration or with other tools is bulls***. here are my proofed results: last_session.ini i can asure you that this is the real deal As far as i know MSDN full iso images vith sp2 integrated are not out yet.So u using some homemade version?

Pretty odd thing with my install.The same build(same things removed): When installed on HDD ie8 install fails When integrated offline with vlite and then installed the build ie8 was installed and worked flawlessly

As far as ive seen non-english ie8 integration is broken...

...or you can follow this guide... http://www.msfn.org/board/index.php?showtopic=111168

I'm always integrating WS 4 and I don't have this. Neither do i.Actually i integrate Windows Installer 4.5 not 4.0. Havent had the loop for months now.All working perfect here.Vista Ultimate x86 EDIT:sry.I said WI but you were talking WS

From my testing i have found both to be almost equal.Although Win7 is a little faster(around 5% in some cases compared to vlited vista).Win 7 default is defenetly faster than vista default(were talking around 20% - noticeable!!!)

In order to debug possible problems i build my vLited Vista editions the following way: Step1 - Clean Vista+SP1+My language pack integrated(Estonian).I unpack the ISO.And with vlite add only Hotfixes and configure services and tweaks from vlite.Then rebiuld and make temp iso 1. Step2 - I unpack temp iso 1,remove components and rebuild image +make temp iso 2. Step3 - I unpack the temp iso 2 and mount install.wim with gimagex to do some in-depht tweaking.Once ready i unmount wim and add drivers with vlite.I rebiuld and remake iso to be test iso 1. Step4 - I mount test iso 1 with VirtualPC(Virtualbox lately) and do some 45min run to see if install goes well and there are no significant problems.If theres not then i will burn this iso to DVD and use as my next build for 1-2 months.If there are significant problems(reboot loop etc) then i have previous temp iso 1 & 2 to fall back for debugging purposes.If im confident that i have found the culprit i make nessesary steps and remake it to test iso 2. I know it takes a lot of time but its the most foolproof way IMO

See SP2 Release Shedule here: http://www.techarp.com/showarticle.aspx?artno=604

Im unsure how this works(or doesent) in x64 version,but on x86 you can integrate both signed and unsigned drivers.You still get a promt to install the unsigned drivers during install(no workaround for it sorry).When it comes to x64 version yüu should be able to integrate both signed and unsigned.Difference is that you still get the promt for each unsigned driver and plus you have to disable driver signature enforcement via F8 @boot.In everyday use i suggest using Readydriver Plus to avoid pressing F8 each boot.Hope this helps...