MPalmz

No worries. My run with Windows 7 is over. I've uninstalled it! It had nothing to do with errors or bugs, in fact I think vLite must have helped a little because my brother kept his installation untouched and his machine is a little buggy. But I've gone back to Vista simply because of compatibility. I need to start using my PC for some business affairs and I ran into a few compatibility problems with 7. I can't run the current stable version of Skype, for example. Once 7 is fully ready, like you I'm sure I'll buy it. I totally agree with you about nLite! My heavily vLited vista feels like an untouched XP, but it's running on much, much better hardware. I miss Windows XP, and with nLite it was an unstoppable arrangement. vLite isn't even close to what nLite was, but I believe that the good doc' Nuhi has done everything that could be done to help us amputate our Vista pains. The only thing that keeps me on Vista and vLite is the fact that I spent (wasted) $1xx on it! I better make use of it. Best of luck with 7 everyone!

Used the same .ini. I have zero problems. Windows Update, for me, works like a charm whether automatic or manual. Only issue I faced was not being able to see my network drive in the map. But keeping lanmanager would fix that. Either way I can map the drive with it's firmware. Going to keep using this as long as I can. I'm still trying to figure out what I like more.. a heavily vLited Vista or a slightly vLited 7. Vista for productivity, 7 for the interface. Tough call.

Fixed this. Re-enabled my services, and presto. New problem though. Cannot find my network drive anymore. My D-Link DNS-323 shows up in the network map, but not as an accessible volume the way it used to. Crrrrraaaaaap. Hope someone checks back here soon.

Just found out that Sony Japan released x64 drivers for some of their notebooks with no support for the drivers or the OS. I have everything working except my webcam and fn keys. This is money. Thanks.

without trying to look big headed, both myself and MagicAndre have posted in nlite/vlite a lot, and have used both many times we've both arrived to the same conclusion, that it's best to keep components that you need a part of, instead of scrambling for a solution when things don't work. we're simply passing on what we've learned the 'hard way' and i'd never target someone because of a language barrier , one of the thing i love about msfn is the great mix of languages / localities no need to fly off the handle and jump at our throats It's not the answers I'm concerned about it's the delivery. I agree with your advice, I just don't understand how experience means you have to give it the "hard way." Just seems mean. And it's just in my nature to defend people when it looks like there is condescension. Post #'s 3 and 4 explain my frustration regarding language. What I mean is that I believe there was a miss communication there and yet Magic begins to condescend almost right away. But whatever, Magic obviously knows a lot and I still want advice in the future, however it comes. Just trying to look out for my fellow MSFN people.

This guide should be bumped and stickied. I use it every time I customize. Which has been...a lot. Thanks again Randomness.

Thanks for the tip. I'm not experienced in this area. Hopefully this is just what I need. I'll report back!

Have tried the whole process over again but keeping the rebuild as an "Ultimate" image? Leave unattended, and manualinstall and keep it as ultimate and give it a try.

I need to integrate some drivers that are in an .exe file. And that file cannot be executed properly on my system. Here is the gist: My notebook runs x86 and I'd like to install a vLited x64, but Sony doesn't offer x64 support for the FZ series. However there are drivers that will function properly on my machine from another notebook in the Vaio line-up that comes with x64. I've tried installing those onto my machine (in order to do an export with Driver Max for integration with the vLited ISO) but alas the .exe file will not complete it's installation. It concludes with an error saying that the driver was not meant for my computer. So I want to pull the driver out manually some how and integrate it into my OS install disk with vLite. I'm sure this is possible but can anyone tell me how?

I've come to my first problem! After my PC goes to the screensaver I can't get back out! I move my mouse around, type a bunch of crap etc. and nothing happens. It's like it's trapped. I accepted an optional update from Windows update for my Samsung monitor, but I don't know if that was the problem because since installing the OS I haven't left my PC idle long enough to see it act like this. Anyone know what service or component is in charge of this issue? Hopefully it's correctable with a service tweak and I don't need a whole new install. last_session.ini is attached. Last_Session.ini

Sorry to double post, totally seperate topic. Just want to say anyone looking for virtual drives for their Windows 7 x64. I strongly recommend the latest version of PowerISO. I have experimented with a few including magic ISO's Magic Disk and everything I've seen causes problems. Furthermore, the unistallation of these programs appears to be impossible. I don't know if it's something I've taken out during vLite or if it's a lingering bug in the beta OS. Has anyone else found this? If you start with PowerISO you'll have no problems. It's trial software but so is your OS :-).

A couple things you'll need to keep for sure: - Error reporting - gives the wer.dll if removed - Windows firewall and dependencies - the firewall is very good so I would keep anyways - Secondary logon - lets you run as administrator on apps for non-admin users w/o logging off Great idea to have a fresh thread dedicated to x64 to be able to discuss and deal with it's unique issues. I will say that I deleted Error Reporting and Secondary Logon and have had no issues in consequence. But I don't think Secondary logon would be a big deal since I skipped user account creation in the unattended portion of vLite. And, incidently I installed Messenger Live today and during the install it said "Installing Error Reporting." I don't know if it was a singular function for Messenger of if it saw I was missing it and reinstalled it. I'm guessing the former.

Thanks for the compliment but I'm no expert. I believe that kazuni is though. He's posted extensively on this stuff in other forums. And incidently it was his .ini file that I copied in the first place. But here is mine. However it's not my original. It should show the services that I've removed, but I'm going to have to do service tweaks after install. Forgot to do them this time but the .ini file attached below will give you a configuration that will successfully install. My concern about not being able to input my own BETA key on install is that I don't know what it gets replaced with. Maybe it's a Vista trial key, like vLite will do for unattended Vista configurations. Problems can only arise if and when authentication happens. The OS will not appear to be genuine. Seems trivial to me since it's a beta product and the keys are free, but hey, there is still a legal license agreement. Last_Session.ini

I don't know, but there is no error on install if you use the text from post #91 as your session. I added the protection from your .ini, did my own teaking and removed a couple more services. I also skipped user creation in the unattended portion. However it then made me bypass the manual input of the beta product key, which I didn't like. But everything is smooth and stable...so far.

I understood your problem perfectly well. What I was trying to say was that no amount of Ram or Video Ram seems to do the trick. It's just glitchy. At work we run decent systems too with Vista x64 and we have the same lag and fps issues. Incidently, I don't have near the problems on my notebook which has lower-end hardware but an x86 OS. At work we used the same fix as you to clear things up a bit. Glad you found something.

Settepotet, I managed to successfully install the KB961367 fix without problems. Details in the other thread. http://www.msfn.org/board/index.php?showtopic=123539

I have removed the Media Center, and install of this update fails here. Anyone else with input on this specific subject? OK so I was concerned about this too but I just installed the KB961367 fix from the MS website and it installed! I'm using Kazuni's .ini outlined in post #91, with Media Center removed. I was not expecting a successful install of this fix but you can compare your .ini file to that one. I even removed some services, but made sure to protect the files outlined in this thread. EDIT: I should also mention that I installed the fix immediately after installing the OS and before actually setting up WMP and playing anything with it. I just tested it...no corruption issues. But it would be nice to have the fix, rather than have to make certain WMP12 doesn't get it's hands anywhere near your media. But hey, this is supposed to be a one month trial of the OS right? So who can't do without WMP12 for a month? :-) Even with a successful install, I wish I could remove more. In time I'm sure things will develop.

Is knowing how to do this common knowledge amoung vLite users? I don't think you can integrate the fix into the install ISO using vLite, but it doesn't sound like that's what you mean.

TWO THINGS: First: I've noticed on pretty much all of the .ini files shared by people who've successfully installed vLited 7, that no services were deleted. Only disabled in the tweaks. Can we not remove any services for this OS? Second: The fix that MS released to fix the MP3 corruption problems in Windows 7 makes changes to Media Center. Does the fix still install even with Media Center removed?

Vista is notorious for having difficulty playing HD content. I've read more than one article on it, but alas am too lazy to source you. From what I can remember they didn't provide sound solutions either so your not missing out. I vLited my copy of Vista within a week of having my new system so I can't say weather or not vLiting would help with that. My guess is it would. But consider this...this is my system: Q6600 @ 3.0GHz 8GB Patriot Extreme Performance 1066 RAM EVGA GTX280 Superclocked plus I'm running a vLited version of Vista with almost 2 thirds of the original ISO size lopped off and I still get some fps issues. I also found them to be more prevalent in VLC so I've switched to Media Player Classic, and sometimes will even use the Zoom Player that comes with the Combined Community Codec Pack. Furthermore, I almost never multitask when watching a movie on my PC. I would bet closing all other apps would, in itself, do wonders. Best of luck.

Randomness I thought you first guide was good. This is brilliant. Nice work. Now any critics of your old guide can eat it. Very helpful for the newbs to the realm of vLite'ing too. Which seems to be more and more people all the time.

Why are there so many jack-asses in this community? Catching a guy on technicalities when there is an obvious language barrier is just not cool. He simply wants to slim his OS as much as possible. Probably because of hardware constraints. I'm not the smartest guy in the world, but I could tell by his first post that he was an nLite user, and many people used nLited versions of XP with IE and WMP completely removed and had no issues. Always seemed risky to me but some may assume that later versions of Windows could also handle that kind of slimming. Not until two posts before me did he finally get a truly helpful answer. But alas, the info is generally correct. Since vLite came out, I have only heard of people running into issues when removing IE and WMP. IE to me seems obvious because of it's so similar to Windows Explorer. I tend to keep some of those core Windows Apps that seem to have almost universal integration with other windows components. Case and point: IE and WMP.

My copy of Vista came with SP1 already integrated, so I didn't have to bother slip streaming in vLite. What a huge relief. I'm not entirely sure how Microsoft's licensing works, but if it's legal, it would be worthwhile finding an ISO with SP1 and using your purchased license key from MS to activate it. I could be treading in deep water by recommending that though, so you'll want to double-check that your not in breech of license agreement by going that route. I know that the product keys work for either as the IT guy at my office snatched the optical disks we purchased with Vista Home Premium RTM before quitting, and then we had some issues and had to reinstall our OS. It was a jam situation so I brought my personal copy from home (SP1) and used the original, authentic product keys we purchased with our software. It all worked with no issues. According to my computer science teacher that is perfectly legal as it's the license you purchase, not the actual disk. But I could be DEAD wrong here. :-) At any rate, I can tell you that working with an already integrated copy of Vista with SP1 is a nice short-cut. Palmz

While I haven't seen any other benchmarks, I have read that SP1 failed to provide the performance increases promised over RTM. It DID of course solve a miriad of stability issues. However, in my experience there has been a correlation between stability and performance (speed). Not always I suppose though. Really high-end systems I would think would be somewhat insulated from performance depletion due to instability. But what do I know?

Found this interesting article comparing XP SP3, Vista, and Windows 7 build 6956. http://blogs.zdnet.com/hardware/?p=3187 The Windows 7 OS finally has better performance even than XP. I'm curious if any of you have compared the performance of a recent Windows 7 build to your vLited version of Vista. I wonder how the two would compare. I'll definitely be doing my own testing when the public BETA is released in a couple of weeks. Of course the ultimate is a vLited Windows 7...or 7Lited maybe.