Jeronimo

Glad to see the first beta has arrived. I am definetely gonna check it inn the next couple of days. Can we expect a changelog in the future as I would like to see what things have been sovled. With nLite those were also very clear and helpful (opposed to some programs only mentioning many bugs fixed). Next time I will visit the website first, before posting a complaint

Here for your pleasure or at least I hope. For me it is therapy, writing off the frustration I had on my s***ty Sunday. I wanted to resize my drives for installation of Vista. I started the bootdisks of PQ Magic and it found some errors. I chose quicly, too quickly, to fix them. Which left me with my crippled D-partition. I use C for Windows, D for Data storage (had most important things backed up) and E for testing of Vista and now vLite. So I thougt, crap well lets start all over. Since I wanted a vLite'd Windows on C and I have no DVD writer (I only got the Windows Vista on DVD from a friend), I started of by partitioning followed with trying to install from DVD to E. Here the drama begins No Vista says, I will make E your new C, you wil like-a-it very much. Nono says Jeronim0, it should be E. Oh well lets just install it to my original C drive. But first make a vLite Vista and install from ISO. Nonono Vista says, I already have Vista on C, so this will be your D drive. Hows that Nononono Jeronim0 says, lets start over. Remove all partitions. Install from DVD to C. Yes I can live with that says Vista. Good says Jeronim0, lets install Vista ISO to E then. Nice says Vista, who made me this slim? I will install on 8GB E without a breeze. Finally we are getting somewhereshrugs Jeronim0, ok fatso Vista-C you are the weakest link goodbye. You won't get rid of me that easily Vista-C howels: you can not go and remove my Windows and Program Files that easily, I will takeown you and cacls the hell out of ya Jeronim0 shouts and Vista-C finally gives in. Now we install this vLite Vista on C and we are almost there, Jeronim0 smiles. What about me vLite Vista-E whines. You do not fit our format Jeronim0 says. Finally I can get some sleep, at least till the next release of vLite that is. Then nuhi and all Vista's A through Z will haunt me in my sleep again. p.s. on a serious note nuhi: The size required for Temp-directory should be raised (In any case you should need somewhere around 4 to 5 GB or not?). I was able to run vLite with far less disk space available, but it ran out during the process and could not complete the operation.

I was forced to perform a clean install after I (Partition Magic 8) crippled my partition. Had to do it several times over as I need to install from an image due to not having a DVD writer. After several installations and 1 run of vLite, I now have it as my primary OS and it works almost flawlessly. 1 setup problem: Timezone is not properly selected by default. 1 vLite issue(?): Search in contents does not work (as according to nuhi could be the case) and I hate the annoying pop-up for activatation of indexing. 1 general Vista problem: I have 1 view (details with name, size, type, date, attributes) which I always want to use, but no matter if I set "Remember each folder's view setting" or not, it keeps using its own kind of more or less random view. I create a directory Downloads and it sets a default view with tags and rating columns. I copy an empty folder with the proper columns and everything is ok. I never had to deal with this in XP, but if it the only issue, then I might just live with it ;-)

remove(d)

I may be picky, but why are not all/more files from WMP10 taken. I checked the version of l3codec.acm and it differs. So the old version is still used. I also notice mymusic.inf, Revert.wmz, skins.inf have changed and are not copied. These might not be important, but what about all the other files, files not named wmp.*, but now named wmp10.*? Maybe I overlooked some files, but I wonder, if this integration covers WMP completely. Even so it seems a lot of people benefit from it, so in any case you did a great job

I do not know who i was, but thanks for the tip on msiexec for Windows XP SP1 and SP2 beeing different. I created a package for SP2 in SP1 and I did not get it to work. When creating it from SP2 it did work.

If I reason it: Tempmode install to a new Temporary location and will never have to overwrite any files. WinRAR Help says it all. Just select Self-extracting modules from the helpindex and then the GUI RAR... All options explained

Overwrite=1 was it not? Check WinRAR hep it says it all.

OK, in fact I like 7zip - it gives extremely good compression (therefore huge space savings) in most cases. But I still feel somewhat shackled with it. RAR sfx'es are much more well-featured. 7-zip doesn't give SFX icon choosing, authenticity verification, the winrar shell extension, recovery record, and lots more. Then again 7zip is free and WinRAR is not. Still for these purposes you could use WinRAR on a trial basis.

I do not think the start and msiexec commands are needed. I did not try to run this at Windows installation, but in Windows for the cmd-file it is enough to state: netfx.msi /qn /norestart langpack.msi /qn Probably because administrative installations allready run automatically.

Ok and now with a languagepack: langpac1.cab langpack.msi I can run these too with /a and copy the files into the other folders, but I do not know if I still have to run langpack.msi (I think so). Can you add additional commands to WinRAR, I have used it in the past, but lost track a bit.

SP1 needs the cabinet file from the installation routine: netfx1.cab

Hmmm. Process goes well, but when executing it fails with some CLID's. I checked it with Dutch versions (1.1+sp1+langpack) as well as all English versions (1.1+sp1). Same result for both.

Integrate SP1 into 1.1 (do not know exact names): "dotnet 1.1".exe /c /t:C:\Temp.NET "dotnet 1.1 sp1".exe /Xp:C:\Temp.NET\sp1.msp msiexec /p sp1.msp /a netfx.msi (From c:\Temp.NET) Now you only need netfx1.cab and netfx.msi You can compress these with iexpress. Command to be executed: msiexec /qb /i netfx1.msi

So disabling Performance Logs and Alerts service is the easy way and disabling all counters is the other hard way.

Maybe even decrease performance. Who knows, the counters do not run just for nothing I assume. I am still looking for information on it. Doing something without really knowing if it is a performanceimpovement.

@dirtyepic So I can just disable ALL the counters with this program, without any problems?

And how many performance did you gain with that tweak Oh well I also do it just for fun, but if it does not work, do not make a fuss about it. Why spend so much time on a tweak that gives you near to zero gain? Oh, wait don't answer that: that is the real tweaker

From what I see in my registry, wouldn't this be the same: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PartMgr] "EnableCounterForIoctl"=- The way I see it CurrentControlSet=Control001. Changing CurrentControlSet would be sufficient.