bokeron2008

Any answer ? Please ?

I posted this as an independent thread, but it seems I should have posted it here in the first place, so here I go... it's about 'dependencies' in the 1.2 final. Why is IPSec needed for Windows Update ? Why is Remote Management needed for Event Log ? I've been testing A LOT of differently vlited ISOs and I've never noticed any problem with the Windows Update service or the Event Log service, though I do remove IPSec and Remote Management. Could someone be so kind to explain me why are those elements 'linked' in the new vlite 1.2 final ? I'd like to know what (if something) might go wrong ... before it goes

A simple question, but I've been looking for answers in the forum and it seems I'm not able to fin them. Why is IPSec needed for Windows Update ? Why is Remote Management needed for Event Log ? I've been testing A LOT of differently vlited ISOs and I've never noticed any problem with the Windows Update service or the Event Log service, though I do remove IPSec and Remote Management. Could someone be so kind to explain me why are those elements 'linked' in the new vlite 1.2 final ? I'd like to know if something can go wrong if ... before it goes Thanks in advance to all.

But what if my iso comes with sp1 AND KB938371 (I suppose is the old version) PRE INTEGRATED, can I integrate, again in this iso, KB938371 ?

Hm, I've been wondering about that, too. Right now I'm doing all this tests using an MSDN version of vista that comes with the KB938371 pre-integrated. And vista, after install, asks me to install the - I suppose - new version of this KB. But... can I integrate the new KB938371 on my ISO, even if I use the MSDN version with preintegrated sp1+ KB938371 ?

Disabling Superfetch frees A LOT of memory. I suppose it is something to be expected, but is there a way to know what is superfectch doing or waht is it caching ?

No, it's just a single Intel core-quad, and the perfmon tests were run on a virtual pc running on top of it, as I've experienced the same issues on the 'real' machine and I was trying to solve the problem before re-installing.

I've done new tests using perfmon. Checked private & virtual bytes, working set, subprocesses, etc, for 20 minutes after boot up. 1st test : Clean install, no updates apart from those that come pre-integrated, sp1 included. 2nd test : The same install, after installing updates available thru Microsoft Update, letting the virtual machine idle for 20 minutes, and rebooting again. Result : There are some processes that use more memory or a few more processes. But there are some more processes that use less memory or less processes. When considering the "total" results from each indicator (private & virtual bytes, working set and subprocesses), ALL of them are lower on the 2nd test... wich contradicts the almost double cache size increase and almost zero available memory reported by Task Manager on the 2nd test. What can this mean ? What more can I check ?

Ok. I've been testing some things again, and the main problem seems to be that, even when the number of processes remain stable, the cache increase or even double, depending on the number of updates installed. I can not find wich process is responsible, as they seem to use about the same memory after the updates. In Process Explorer, the available memory remains quite the same, but Vista Task Manager shows less available memory, or even NO available memory. Any comment on your own experience about Vista cache , or about this different readings given by PE / Task Manager ?

That's what I'm trying to find right now, but PE output is difficult to understand for me. What I can say right now is that, even when the procesess stay at 32, "used memory" increase again when I install a few updates more, and "non cached" memory decrease too. I'll try to collect more data, but in the meanwhile, if someone has any experience like mine, or contrary to mine, I'd like to know. So far I have only two answers, one say is normal, one say it's not... P.S. I have a question related to Process Explorer / Task Manager. In Task Manager, the available memory is 0 of 1023 mb. 864 cached. But, in Process Explorer, it shows 778mb of 1023, 850 cached. Why this diference, 0 vs 778mb of free memory? (In this test, the cached memory before updates was 480 in PE. Went up to 850 after installing 21 updates. Free memory went from 450 in task manager to 0 - but remained at 760 approx in Process Explorer. Number of processes remained at 33 after updates. All of this, again, after two reboots and 20 minutes idle)

Last example from a recent test. I have only installed 1 update, KB938371. Available memory went down from 450mb to 389mb. And, as I said before, this is after two reboots and 20 minutes idle after the first one, and another 20 minutes idle after the second. So, please, can't anyone comment on the issue ? Is this the normal behaviour ? What can I do if not ?

I mean way after the update. Like rebooting, leaving the virtual PC idle for 20 minutes, rebooting again, and leaving it idle again for 10-15 minutes.

That's what I'm not sure. In everyone experience, is this normal ? I was of the impression that "updates" or security updates at least, modified files or "behaviours", but not to the point of causing a 150 mb increase in memory usage because of it. At least, when I was using XP, it was not the case. A few K's at most, because of new processes running, or files that got increased in size... but not this.

I'm using an MSDN ISO of Vista x86, Spanish. I try every build using Virtual PC, giving the virtual computer an amount of 1gb of RAM. I have a problem, don't know if it's related to Vista itself or to Vlite. When lookin at the task manager info, a clean install of Vista Ultimate uses around 24-25% of RAM, about 260 mb. It also indicates a cached memory of around 450-500 mb and 450 free. 28-29 processes and about 370 subprocesses. When I install ANY update, the memory usage goes up by quite a margin. Free (not cached) memory drops to something like 360-280 mb (or even, a couple of times, 2-7 mb) . Number of processes go from 28 to 32-34, and even kernel memory goes up by 5-10 mb. I've tried every combination I've could think of when "vliting", I've tried installing different updates, one each time, and some of them affect the system more than others, but the end result is the same. I don't know what's going on, or if this is happening to anyone else. Could you please help me ?

I understand from your message that you kept ReadyBoost ?

Curiously for me, I must keep ReadyBoost and Windows Time for the update to install. I don't delete any QOS related service, but I do delete the Mail program.

You and me, bokeron. Just you and me. We will conquer the world, alone. Thanks, once again, for helping me solve this problem. It's the second time since I registered to this forum that you've been the only one able to help me. This forum is soooooooo useful that I guess I'l stay here forever. Well, your problem, bokeron, is : YOU CANNOT ADD FOLDERS STARTING WITH _. So no _Extra, _Drivers, _Tools ... nothing that starts with a _ If you do, you're f***ed up. Glad to be here and be of any service to you, I mean. Me. Man, I feel like I'm sucking my own dick.

OK, I've burn an vLited Vista x64. I've installed it. I've installed Virtual PC and vLite. Every ISO I create ends up showing the same boot error as before. I suppose all of this should be caused by a corrupted Vista source... but in this case, they have to be TWO corrupted sources, x86 & x64, at the same time. Both x86 and x64 are giving me this error. And I remember you... using Nero to create the ISO works OK I'm out of ideas. P.S. Beside this, the vLited x64 still asked my to create user, set time, language... but I used vLite to make this automatic. So this part of vLite doesn't work either.... though everything was working OK before. Am I cursed or what?

Everything was working OK. I've been using vLite to build some test ISO and install them on Virtual PC. No problem at all. I've made... hundreds. But now, suddenly, I don't know what's changed. Every ISO I build gives me a boot/bcd error when I try to boot the image, be it x86 or x64 Vista. Is the same message some people reported when building a Server 2008 image. I've even tried burning a DVD and tried to install in a real machine, and the exact same problem occurs again. I've tried reinstalling vLite, but the problem persists. If I create the image using Nero, with the boot.bin provided by vLite... the ISO is OK. I'm running a Vistax64 Ultimate, vlited. Help. Please. !! Edit 1: Funny, I'm playing with Matroshkas now (the nesting dolls, not the file type) with vLite running inside an vLited Vista x86 Virtual PC install. Created the x64 image. Failed again, but now the message is related to boot/winload.exe. It is related to VirtualPC not being able to execute x64 version... so this shouldn't be a problem. Edit 2: Now I tried to create an x86 image with vlite-in-vlited-VirtualPC . Fail. Error is again boot/bcd. Does it mean this it's not related to an OS problem ?

Thanks hmmm bokeron, for your answer. You've been really helpful. I'm glad I sucribed to this forum just to ask that question. And thanks to all the rest of the people who took any interest in this. You all have my respect.

Hm, well... bokeron... I have an answer for me, I mean, you. It is related to Application Experience. Should have known that one. Database or list for looking up programs and see if vista likes them or not. KB947562 updates it or modify it, so if you remove it, vista can't find it... If you don't have any use for Application Experience, it might be safe to delete it and simply don't update it. If you wan't to play safe, don't delete it.

Ok, I've tried a full install. No problem. KB947562 installed without problems. On the other hand, I've been seraching about this update and there seems to be quite a few reports of problem due to this update. But the fact that for me it only caused problems when altering the vista sp1 ISO with vLite, it means somenthing I removed is needed for KB947562. But what ? Any comments or solutions to this question ?

It doesn't seem to have anything to do with the options I choose in vLite. Or at least that's the way it seems by now... every combination so far have always ended the same. I don't integrate anything at all, though the MSDN ISO has some packs already integrated. I just remove items. When I choose to update thru 'windows update' after a fresh install, check some of the packs and amongst them KB947562, it goes into a loop (installing 3/3 100% - reboot - installing 3/3 100% - reboot ... ) If I don't choose that pack, then everything works fine (or at least does not reboot). If after that I choose to install this pack alone, it shows an error, code 80070643... related to Microsoft Office ¿¿?? I still have to try a full install to see how it goes. I'm using vlite 1.2 , vista ultimate x64 sp1 spanish (MSDN).The x86 version has the exact same problem. Is this a known problem ? Is there a solution ?