MPalmz

Randomness did you ever get to the bottom of this? It has to do with running vLite on the 32-bit version of vista. There is a quick and easy fix for it. Just copying some file somewhere. If you do a search you should find it fairly easily, I myself am too lazy to do so. Sorry. Just wanting to check on an update of this guide to see if you're any closer to tayloring it to the updated images of Vista that already have SP1 integrated. The component removal portion is quite a bit different in some areas. Still, this works wonders for those of us with the patience, common sense, and intuition to make the gaps work.

My execution times have been roughly cut in half. Boot-up, about 40% faster. That's just my system.

Cool. Thanks so much for the support. I'm going to rebuild and try again tonight after work. I really appreciate the assistance.

vLited Vista working like a charm with no problems whatsoever, until now. I have a plug and play capture card (Canopus ADVC 110) that I'm trying to capture analog video with, and it's not working properly. Once connected to the Firewire port, the driver gets installed properly, but another portion of the automatic installation fails. The error states that "The required section was not found in the INF." Any clue what I could have removed to cause this? The unit itself did not come with any supplementary software or drivers. They are not needed normally, and as far as I know cannot be downloaded from anywhere. This is my first time posting a last session. Don't know anything about .inf files, but I found my last session.ini. Is this the same thing? Last_Session.ini

Oh crap. I better copy this guide then because it worked perfectly for me. People who have difficulties just need to use a little common sense and play it safe on a few of the "iffy" things. For example I kept in some things that the guide indicates can be removed like Crash Dump and Firewire. I'm also vLiting a very current release of Vista (my OEM disk had SP1 already integrated) so some of the options are different. You just use common sense, read up on things that are questionable for removal. My personal ISO was 1.06GB and despite leaving in several components I was able to chop out 2/3 of my original ISO. Not as slim as some other people's ISO's but my system is at least twice as fast now...at least! It was this guide that actually got me back into OS customization and I'm just thrilled with vLite now. Maybe warn us prior to replacing this guide in case there are others that frequent the thread for perfecting their custom OS. I'm actually using it tonight to fix both of my work PC's.

Indeed. The whole experience has enlightened me. I had a lengthy discussion with a tech about BIOS and some of the do's and don't's. I was lucky they were a really good vendor and took back the fried board no questions asked. Otherwise it was 2 weeks wait for Asus RMA. The board was a refurb. Reason for refurb: "wouldn't post." Which is why the exchange went so well I think. But yes I've learned that BIOS flashing needs to be a carefully executed affair. And...that vLite rules and had nothing to do with it. Sad part is I had to exchange my 4870x2 for a GTX280.

Could you please make some corrections if you think that there were some mistakes? My Vista Image is based in a part on this guid so before the installation I would like to know if I have to correct something, I don't want then my system to be unstable. Thanks Well, if you read the reply's on this thread, you'll notice that a lot of users are correcting almost every part of the "Guide" I know this comment is months old but I can't help but touch on it... what a prick. Randomness this guide is an absolute money idea. Sure it's needed a little refining along the way, but that's why it's in a thread and why we have community. I've been looking for a guide of this simplicity and clarity. Finally I'm using vLite with confidence and improving my Windows experience. Great job, and thanks for putting it together. And thanks for all the comments in thread to help clarify parts of it.

Doing a new vLite ISO to integrate my new hardware drivers for my new system. Just wondering...if I want to sync my iTunes with my iPhone will I need to keep "Windows Portable Devices"? Anyone able to sync music and photos from you PC to your iPod with this removed?

My vLited OS is trying to install drivers for "unknown device." Since I removed all drivers for my ISO and just install drivers from my chipset disk, it can't find the driver for it and asks for me to insert the manufacturer's disk. But even then Vista can't find drivers for the device. When I go into device manager the properties for the Unknown Device say that it's location is "on PCI standard ISA bridge." My guess is that it's really not that important, and to avoid windows trying to get drivers for it every time I restart I've just disabled it for now. Anyone know what this could be?

Hence me taking so long to reply. :-)

"My car had a flat tire so put the spare on. I drove for a few miles then the wheel fell off. The problem must be the engine so I'm getting it replaced." Does that make any sense to you? If you had profound engine vibration, maybe some solid fabricated engine mounts instead of standard rubber ones, combined with a poor install of the spare, then yes actually. I'm new to this, and had never seen that kind of behavior before. I thought that there could have been a small possibility that I had perhaps altered something with start-up in my vLite and my PC couldn't find something it needed. After some research I realize that that is preposterous, but again, I'm a noob. With all the issues I had with nLite nothing would have surprised me. Thank you for this reply. You got me looking into how to reset my CMOS jumper and I learned a ton about BIOS stuff. I guess Asus Update (an official BIOS update utility from Asus) has been notorious for causing these problems. At the official Asus forums everyone warns new guys to NEVER update from Windows using this utility. Must be causing Asus a lot of grief too. So after the CMOS reset was unsuccessful, I took the board to my point of purchase. They tested it and the chip was completely gone. It was fairly new so I exchanged it for an nForce 780i board. Apparently this chip-set is problematic too but EVGA has 10 times the customer service that Asus does. Anyway, bottom line is vLite had absolutely nothing to do with it, and I thank you for your help.

I'm a newb to all things technical when it comes to software and hardware, but I used the guide here in these forums to vLite my x64 edition of Vista Home Premium and have had it working flawlessly with no errors or weird behavior for a few days now. Couldn't be happier with the results, quicker loads, less resources etc. etc. I have used the OS extensively to try to root out any weirdness and have found nothing. Boots fine, runs everything fine. Awesome. Today I tried to update my P5E3 Deluxe motherboard BIOS to the latest official release (1303) using it's ASUS update BIOS updating program which updates the BIOS right in windows. I immediately got an erro saying that it couldn't find CPU information and had to quit. I THEN tried to reboot my PC to see if that would help and I would try to flash the board again. But now it just starts to boot up for like 3 or 4 seconds and then turns off, then 3 or 4 seconds later, it spontaneously turns on again and does that over and over until I just switch off the PSU. Could this be because of my OS? Or does that sound like a firmware issue with the mobo?