TranceEnergy

You dont need a third-party tool to enable x-mouse behaviour in windows. Just mentioning this if you still want windows to behave that way.

Imagine Add/Remove Programs in Control panel? You start it, and you see 2 entries for visual basic runtime files for x86 f.ex Not just 1 entry. Sorry for bad writing. One other thing tho i have had much trouble with disk.sys since i bought new computer, always used xp pro x64 since it came out almost, and now have random disk.sys bsods. I was only wondering if there is some update that could cause instability on some part with disk.sys? It's driving me crazy. Not that i arent already. On Vista x64, no trouble, so it is the os. One more thing, .Net framework 1.1 on x64, xp at least. I know it will install and installer works great, tho small notice on install. Is not .net 1.1 needed because 2.0/3.0 does not contain it? Also if i do not install .net 1.1 on xp x64 and i run CCleaner, then it will find missing registry keys for .net 1.1 At least thats what i remember it reports, it could be that ccleaner just doesnt understand like variables for windows paths f.ex %systemroot%. (tho it does understand that, but x64 has some folders 32bit doesnt have, and there may be 'conflict' in ccleaner there on x64 versions).

I used to to this procedure several years ago, actually 8years, on windows 2000/xp. However, if you have a farely new computer there is a much faster way to increase overrall system/io performance. Use a good partition manager to set cluster size to 64KB, disable pagefile first tho and hibernation if u have it,enable large memory pages on 64bit 2gbram+, increase critical workerthreads to 16(both). Then defragement harddrive. C:\ should be somewhere between 40GB to 60GB, suitable to keep many to insane many programs. Games should be kept at a completely different harddrive, because then games dont have to read/write to same place as windows/os has to. Also prefetch should be disabled as it slows down system boot, unless you are going to manually optimize the layout.ini, just forget prefetch. Also good practise is to use portable software, making the y:\program files here mentioned in #1 bloat, as you will NOT need it, since all programs should preferrably be portable and on different harddrive for optimized performance. For even further i/o speed consider ramdisk software by superspeed software, or getting some expensive SSD sata drivers, which you place directly on sata-port on mainboard, making it a truly fast 0.1ms system access speed. If that aint enough yet, start looking at memory latency timings. Your ddr2 800mhz cl4.4.4.12t2 average good memory might do good in 3dmark benchmarks and the like, but ddr2 400 mhz at 3.3.3.9.t1 will make it look retarded when it comes to f.example boot times. If your system when optimized as you like it cant boot under 10 seconds, it aint optimized in my book. It's always a matter of how far you are going to go, but i think the whole repartitiong scheme is really outdated, unless your computer hardware is even MORE outdated, the performance gains from it are truly neglible, at BEST. Please note, changing cluster size on c:\ in Windows Vista with latest acronis tools doesnt actually work, it will make system boot totally crashnburn.

This may be totally off topic but i thought i'd mention it anywy. If i use the Visual basic installers as mention in post #1, i integrate x86 and x64, i still get double installers showing up at add-remove-programs,control panel, when i install f.ex Ati drivers for system chipset, etc. This Ati Installer has own VB setup files, and i think maybe one problem is there. Also I know that Ahead Nero 8 micro edition has these VB installer files, which i found funny (micro edition). So if i basically first install VB in itself, then these two programs, or one of them i dont remember you see atm, i will get double up for x86 version at least in add/remove programs. And i dont like that. I have downloaded the latest version of VB and dont understand where the problem really is. Maybe the ati/nero installers just force VB anyway. But it shouldnt force double up uninstlallers. Also i remember that size of VB in add/remove was different.

I guess sometimes writing what one have at mind or heart isn't that easy. =)

I honestly dont know, since last versions of nlite, or for some time, nlite had used truly patched sfc, not hacked lol. Anyway anyway, normal command just Start menu, Run, sfc /enable i think. Found a link here It's from 2002 tho, lol, but what he write still apply i guess at least on cmds.

It wont happen is more like it. At some point, you can't just expect to remove and remove and think hey all functionality should still work. Not unless we start resource hack whole vista as a entity, making it something totally different. Windows update is MADE for the untouched windows version, not the vlited one. The only way, and only way, this could be doable, if someone were crazy enough to start hosting an alternative Windows updated mirror, which supported such uniquely hacked vlited/nlited windows versions where certain if not all features originally in windows are removed. I'm all for that, and it could be done, i honestly believe that, but i dont see it happening any time soon. The other option would be if all windows updates were pre-tweaked, pre-patched to be consistent with a vlited install. Which more or less would be the same as herein original suggestion. Now hopefully I have irritated and annoyed someone to be as crazy to actually start doing this, hosting a mirror which supports fully vlited vista, or nlite,preferrably both.

So if i remove .Net with Vlite with -extreme option (run that always anyway), i can still use Vlite with the runtime files pack?

I am having a discussion with my self here in another topic, but seemingly you can remove/optimize your Vista vlite Image a small bit, if you integrate Windows6.0-KB938371-v2-x?? (x86 or x64) BEFORE you SLIPSTREAM SP1. Im doing a final check now but as you know it takes some time to slipstream sp1. I'm very intrigued at this point!! its exciting =)

I dont understand where you are going, what you mean exactly, but it's kind of obvious that you would not be able to read languages alphabeths etc that you dont have installed. It would translate into a lot of ???????????? replacements. Do you mean to remove only other speech language but not text part?

I didnt see these.. Without doubt in my mind, probably the best tweak for windows, by far: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Executive] "AdditionalCriticalWorkerThreads"=dword:00000010 "AdditionalDelayedWorkerThreads"=dword:00000010 thats 16 for both in decimal.no more no less, it is also the maximum afaik. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters] "EnableSuperfetch"=dword:00000000 "EnablePrefetcher"=dword:00000000 NO THANK YOU! + "DisablePagingExecutive"=dword:00000001 "LargeSystemCache"=dword:00000001 Of course.

Well I dont get any audible ticks or weird noise at all without it. Google this and you will find people reporting that their systems work much better with the service disabled. So I thought, then why not remove it? So i did, obviously, and voila! Instant Profit! Harddisk copies very fast, was like 50mb+, and now is like 70/80mb+ when multitasking. I have dualcore+ 8gb ram, and reasonably fast system. However, i am a totally nut at tweaking system for maximum performance in terms of responsiveness,lowest latency possible, and while checking with DCP LAtency checker it reported a staggering low 8 us latency. I couldnt believe my eyes but hey, im no programmer. But i do know a thing or two about tweaking. In comparions i had 300 us+ after boot, no programs on xp x64 ( the latest xp x64sp2 updates has made it really unstable tho). Vista is actually faster then xp, by a good margin! After tweaks but still. Profit!

Sometimes NEW drivers REQUIRE *OLD* drivers. I was testing SATA AHCI mode for harddrives in vista, and when i installed the ATI drivers, it also looked up some promise controller drivers. And the only promise controller drivers i have are integrated in the vista originally. Solution to optimize vista with single drivers for stuff would be to capture and export drivers with perhaps tool like DriverMax, great tool, free registration. So first install system with all drivers original, nothing removed, then install all drivers as normal, then capture drivers with inf files and all and use them for a fresh install of vista with all original drivers removed. Either that or you could try extracting drivers from the Vista dvd, i know this works quite good in XP but havent tried it in vista yet.

The great thing is that it would be optional, so those who will not use it, dont have to. Everyone profits =)

I just did a fresh install of vista ultimate x64 in vmware, with integrated WinVista SP1 All Language Standalone for x64-based Systems (KB936330) without anything else, and with x64 + the WinVista SP1 All Language Standalone for x64-based Systems (KB936330) AFTER, then made iso, applied to rebuild only ultimate. I did check with windows update with the fix+sp1, and it doesnt say that i need to install the KB update anymore, even tho the hotfix in v2 version is both for pre sp1 and sp1. The Servicepack, offline version NOT windows update version (as in singlefile), does not include the V2 of the KB, so i dont know whats best? If the system is better served with the v2 of the hotfix FIRST, then slipstream SP1. I really would like to know what's best. edit: After thinking about this for about 10 seconds more, lol, i think this patch is also available for presp1 users, so if its ok for them to install it also without sp1, it doesnt exclude sp1 either. Much profit! Edit 2: I finally got the hotfixed integrated on the image AFTER SP1. It is 15282780 bytes larger, the entire folder then the folder with hotfix+sp1 (in that order.) I am kind of tired so dont know if i have made something twice, but i think this is correct. edit 3: i am trying to integrate it again to see if it vlite accepts it, and it does that, but filesize doesnt increase as much. I tried to manually install the patch in the vmware with hotfix+sp1, and it didnt accept it there. So i think its safely integrated, even if SP1 came after the v2 hotfix. edit 4: Someone reply to this already lol, Vlite apparently reads the vista image as vista With service pack 1, but it doesnt anyway, i mean it doesnt say "(service pack 1)" but the build number 6001. is correct. Im totally confused at this point... edit 5: My bad, confused it with original sp1 disc. Im going to try and compare it to that instead. I am leaning in the direction that it IS best to integrate the Windows6.0-KB938371-v2-x?? 1st then SP1, because if you integrate Windows6.0-KB938371-v2-x?? AFTER SP1, vlite will increase the size of the overrall image, which i have seen it do. I will report back when i know this for sure. I'm too deep into it now to let go... =) OBVIOUSLY the point here is to optimize Vista Install image as much as possible, not having redundancy in itself.

There's no problem running several Vm PC's with several VM's inside them again. With enough hardware, mainly memory and hdd space, you can run more or less infinite vm's. If you are, totally crazy. If so, make **** sure you DON'T TAKE THE BLUE PILL!

Speaking of time, Vlite and Nlite and the Windows Package manager ( at least in vlite) uses only 1 core here at my dual core cpu. Would be great if both/all cores could be utilized for increased speed.

I have no trouble using the .cabs from fox's pack on vista ultimate x64. Are you trying to integrate hotfixes as same language as in os or other language?Also latest fox pack is 2.0+. Just so thats clear.

Does anyone know a way to remove the sp1 left over files that comes with when you slipstream sp1? And i dont mean the vsp1cln.exe way, i want to slipstream sp1 then make it permanent, removing the left over files, that is remove the uninstall sp1 option. So i dont have to do it after installing vista. Or maybe just hope this will be in next version of vlite? OR maybe it is, lol, but i havent seen it tho.

It seems like the new updates for vista sp1 gives the tcp ip stack workaround some troubles, ie system won't boot or tcp/ip stack locks up, no internet connection. I havent tried this since the RC of vista, x64. So, does it work with the latest updates? And if yes, someone could possibly create a hotfix package to slipstream with vlite, and everyone profits? I can't decide what i want more atm, the option to unlock the admin account in vista with vlite, or this..Think the admin unlock would be sweater as i can 'live' with the limit per se.

If you are integrating SP1 into vista, remember to also integrate the required hotfixes.

If you are afraid of this accidental , "Oh No I pushed the power button, girlfriend/boyfriend/friend/whatever id*** that pushed it when u was gaming/watching movies/actually getting some work done, " why dont you look inside bios for the wait-4-seconds-before-powering-off- option. ?!

Well not to put oil,gas and nitrogen on the fire, but gaming seems a lot smoother with this limit removed then enabled so to speak. Before: 125/140 (spikes 160) ping to US when gaming. After. 110-15 very stable at least, ping to US when gaming. I have a lot of ports open otherwise when i did these comparisons, and everything enabled in vista, nothing removed. I am aware that this limit shouldnt affect latency or such, but then again, if something says stop, this is the limit, usually there tends to be a a queue of something, rather quick. I am totally not neutral on this subject, as I for one, think limits are meant to be broken, destroyed, and move on with life.

Why on earth have you kept the multimedia class scheduler service if i dare ask? Remove it and remove the dependency from windows audio inside Vista, registry. Nuhi should clear the red of this one and instead add this 'tweak' to vlite so everyone can enjoy vista without it. It's absolutely NOT essential at all. edit: About the vista and server 2008, and server 2008 seems snappier i can totally understand. It's the same thing, i guess (since i havent tried server 2008), with xp and server 2003. Once upon a time i benchmarked server 2003 and windows xp, both 64bit versions, with performance test 5.0 i think it was,. Guess what? Server 2003 was 50% faster on 2d graphics. Even with exact same setup, classic theme, all display stuff removed/deactivated. edit: if u are ever going to play any game, which wasnt made for vista, you will need the Application Experience service.

2 Questions: 1 : Some years ago i participated in the bugtracker forum for nlite. Is it still active? I can't remember links.. 2: Where's the feature suggestion thread?