As long as there's no crack or cd key gen or anything like that, I'd assume it to be legal since it's nothing that MS themselves haven't offered to the public.

Anyways, I've been plagued with the reboot loop myself as well as Vlite saying that certain 32 bit updates don't apply to my system as well as vista itself telling me that several updates that the windows updates report returns don't apply to my system???

Well if they don't apply then why did windows update tell me I need them?!?

In particular, update 935509 says it doesn't apply both in Vlite and from within a non SP1 vista. Yet MS says it's a critical update for SP1 to install correctly. (which SP1 doesn't install from within windows if it's a version I've tweaked with Vlite)

I'm in the process now of integrating SP1 into an image of ultimate 32. I'll save it and burn it to disk for future use so I can have a full, unmolested iso with SP1 already integrated to work with for future builds.


It only brings me back to my original question though of how I'm supposed to be able to integrate all the dozens of hotfixes Iv'e downloaded into any future projects? Becuase it seems that once SP1 gets put into the image, it wreaks havoc on any chances of all the hotfixes sucessfully being integrated with vlite (or at least a lot of them say they can't be integrated when they're SHOULD be) and also, if I don't put any hotfixes in with vlite and try to install them one at a time manually after vista loads, at least 10 or so come back saying they don't apply to this operating system when they SHOULD.


Anyone else face this problem?

This post has been edited by FastRedPonyCar: Aug 12 2008, 08:59 AM

Actually any non-MS source for a Windows.iso is illegal and will get you banned for posting it here..

Sorry but its just that way and always has been.

It's like some one walking around the mall and giving out homemade copies of vista, even though they are not adding keys they would be paying MS 30% or more of their salary for a very long time...

hey nuhi great work

Some Requests

1.remove windows anytime upgrade which is under system32 and the start menu shortcuts to windows marketplace and windows website
2.remove all those cursors except the aero cursor
3.remove unneeded fonts
4.let the user change the minimum ram needed to continue setup or disable the check
5.add more services under components because there is some which are under tweaks which isnt under components

You dont have to put all these in the next version because im grateful that someone has made this possible

Thanks again on a great piece of software and keep up the good work

This post has been edited by Richard Arkless: Aug 18 2008, 06:56 PM

SP1 integration went well and installed fine. Running all the windows updates as we speak.

Question (and I'm sure the answer is no) but does the fact that I haven't activated windows yet have any impact on the success of the install of the patches and updates?

Regardless, I'm going to write down which updates fail then try and manually run the install package. If some still don't work, I'll return with a list of the failed patches to see if anyone else has the problem with them.

It'll be interesting to see which of them get successfully integrated in Vlite when I rebuild it again today.

Basically I'm trying to do this one step at a time. I know the oem disk works; I now know that the SP1 slipstream disk works. If the updates all work fine without tossing me into the reboot loop, I'll proceed with another vlite build with all the available patches and updates, verify the success of the install and then finally see whether or not it will let me start yanking components out at that point and still sucessfully install.

Even if Windows isnt yet activated, you can install updates fine.

yup. all the updates installed fine, no loop. I've rebuilt the iso with all the updates and SP1 and haven't modified the components yet. Will be installing shortly.

So? This is precisely what MS did, has done for ages, and will be doing for ages. They've only recently stopped offering the Vista x64 image downloads.

I seem to have lost option of running applications in "compatibility mode" for lower oses. The tab is missing from properties options of executables. Can someone tell me about the dependency which I might be missing out?

Found it!

"Error reporting" has to be selected!

This post has been edited by clavicle: Aug 15 2008, 08:22 PM

Hi all...

Vista x64/x86 Business SP1 (RTM) Vlited. Reboot after Windows Update, Loops in WinLogon at Step 3 to 3 100%

No problem with older versions.

please post your Last Session.ini

Too Late...

I build a new integration with Vlite 1.1.6 Final and no problem...


Thanks for your support but i wait the Vlite 1.2 final version

if you do not provide information nuhi can't fix it for the final

Yeah, sure but look like everyone is on vaccation

I have downloaded the latest version of vlite and I try to integrate SP1 and it says it failed and no changes were made. I have also upload my last preset. I have vista ultimate X86 version. I have plenty of free space

Your ini states you're using "vLite v1.1.6 beta 2". The most recent version is 1.2RC. Incidentally, you also appear to be trying to operatate onto an already vLited source.

Nuhi, after electing to remove UAC from components the next page shows the tweaks with User Account Control (UAC) Enabled but greyed out. I assume this is because it cannot be enabled because it's been removed. It would be nice if this screen indicated that. So instead of showing 'Enabled' it showed 'Removed'.

Just a thought.

This post has been edited by Dobby: Aug 17 2008, 05:43 AM

@ Dobby: It indicates it by greying it out. I think this is just enough.

Yes but that makes it looks like it's enabled and you cannot turn it off. As I said it's not a big deal but thought I'd mention it as some might get confused.

for you guys having trouble, try taking just the oem out of the box iso, slipstream SP1 and apply that then create the iso, burn it to disk. Don't touch anything else, not even the automated install. Just SP1 and that's it, no other hotfixes.

install vista and then run a windows update and write down all the patches that it finds that you need. What I did was use a vista updates downloader that scanned my PC and downloaded the individual kb packages.

Next:

Take the original disk and open Vlite back up and use the original disk's data as the foundation, NOT the one you have slipstreamed SP1 with.

Now once Vlite is open, skip the service pack option and ONLY integrate the patches that the OS said you needed after you just ran the windows update, I also ticked the 4 gig ram fix also.

Now, DONT remove anything. Apply, rebuild and burn that to disk.

Now, take THAT disk's data and use it as the foundation for your next build.

At this point, slipstream SP1 but again, do NOT remove any components. Apply and build the iso.

Now, for the final build, you should have a disk that has the post SP1 hotfixes integrated as well as SP1 slipstreamed and NOTHING else removed.

Take this disk and use Vlite to use it's contents to start removing components, automated install, etc...


If you do it like this, it SHOULD work and best of all, windows updates should work without giving the reboot loop.

I've built 4 install disks from scratch this way and can verify that for me, it's worked flawlessly every time. For whatever reason, if you integrate the post SP1 hotfixes, rebuilt, slipstream SP1, rebuild then strip down, rebuild, it works with no errors trying to install patches or anything like that.

@FastRedPonyCar - why do you integrate the updates first and then SP1?