Commander X800

So i could make this in Visual Studio 2008 then?

Am i asking in the wrong place, is this not possible?

In an effort to make things a little less bolted and more efficient, I have set a fair amount of services that belong to applications that do not start with windows to run in maul mode, so that they are not just take resources when they are not needed. The problem i am having is that after i close the respective host application(s) when i am done with it, the corresponding services do not close out as well. Instead they just linger in the processes pool. My goal is to find a way to tell a given service to terminate after its parent application closes without me manually having to terminating the process in the task manager. Edit: to fix title.

Thanks for the Installwatch suggestion, to bad windows does not come with sort of thing by default.... Not sure if it catches every thing but seems fairly robust thus far.

I am looking for a program solution that will monitor my systems registry and folders as a application installs its files, drivers, and registry entries. The reason; i am currently testing out various configurations of Creative Lab based drivers and other DDS, DTS, CMSS-3D based modules on both windows vista SP1 X64, and windows 7 beta X64, and would like to avoid having to formatting/installing the OS's multiple times as i work on modifying the driver sets to suit my needs. I would like to build a file and registry entree listing based on the default drivers and added modules so i can 100% clear the computer of all items that are copied over during the driver install even after i uninstall said applications.

Hehe the infinite Wow6423node reflector loop can be fixed by removing the second wow6423node key eg: HKLM\SOFTWARE\Wow6423Node\Wow6423Node short term resolve: your 32 bit registry scanner/cleaner won't take for ever to complete a full pass(if it ever does...) Long term issues: unknown, as that key only comes up after SP1 and doesn't seem to affect any thing negatively after removal.

I didn't post this question because i was after reducing the registry in size necessarily, rather mainly to understand why it was so large(when comparing it to the norm)from the context i was viewing it in(all be it the wrong way... but that has been resolved now). In response too the last two post, i agree that most registry cleaning apps have the potential to be more harmful than proactive in most cases. This weighs heavily on the end users as well though. This is due in part but not limited to the fact that they(they being common registry cleaners) are designed in such a way that they are mostly an automated process with very little users verification required to validate the remove/modify action of a given key, value, or data entree. They also lack information as to why the key is considered to have an issue. Meaning it is as simple as: click once, click twice, click thrice, and congratulations... your system is now hosed. This allows non knowledgeable individuals who doesn't care to know "how it works, just that it does" to easily be wowed one way or the other by hype that would have them believe that there system is slow or at risk to charismatically more often than not corrupt their systems registry information because "its really as easy as 123" to fix all of your computing issues even if they don't exist. Where as like you said there is little gain from removing a few orphaned keys in the way of noticeable system speed/free space recovery. Meaning at the expense of allowing an application to decide for you whether all the keys it selects are bad or not without giving you much variable input on the matter is an indicator of there knowledge level... This falls back on the end user though, if they don't care to become smart enough to know whats going on its there fault then. That is why it is important to learn how theses sort of things work(registries for example), after all nothing ever gets fixed/improved unless your or someone else brakes it first. Additionally proactive maintained doesn't hurt ether. Just so long as its done correctly. For example I've upgraded my X-FI sound drivers recently and Ive manually cleared out the old registry keys/values linking to obsolete system and driver files before doing so, that otherwise would have prevented me from upgrading without software conflict.

My platform is x64 as well. Thanks for the relevant information about where the files are located, and how to distinguish there real size values. My values are similar, but more importantly not ridiculous in size as i now know now how to correctly identify them.

I'm well aware of that issue, as it would be true with any other Windows OS. I'm only looking for a common variable, and not an absolute value. I Think that if used responsibly, the better tools out there can be used as aids in finding possible problematic keys. Only then would you manually go in and verify if the integrity of the entree is whole or not. I've taken a look at this software, and let it do its thing.... its saying my registry is 66,322,432 bites, and 61,321,216 bites post compression [8% decrease] *Additionally I've noticed that this software was lasted updated in 2005, i don't know if this has any barring on its compatibility with current versions of vista, or for that matter if it takes in account x64 reg entries(still learning about how registry reflectors and such affect software like that). Yeah i would say so.... but that is the file size of the exported registry hierarchy, right after first boot. I hope its not loaded into the system memory pool like that, and its just that way when in a .reg file.

As the tittle suggests what is the size normally?

Hmm, i see where i may have caused confusion... I mean to say that i have not integrated any hotfixes into my Vista source directory prior to slip streaming the service pack, i think this is why my test build failed to install the for mentioned updates.

nobody?

Hello I'm having a bit of an issue with my Vista project. At the moment i am only trying to build a straight forward ISO of Vista x64 Ultimate SP1 for personal use... However after only slipstream the SP with the source directory by using the latest version of vLite and install the OS on a VM Ware machine(for testing). I run into an issue with Windows update, Three updates fail to install: Cumulative security update for internet explorer 7 in windows vista for x64-based systems (KB950759) Security Update for windows vista for x64-based systems (KB941693) Update for windows vista for x64-based systems (KB93871) I've read that some updates need to be integrated prior to slip streaming the SP. Is this true? If so, witch ones and will it resolve this issue completely for all other post SP1 updates? If you need additional information about any thing please just specify, and ill be glad to post it. Thank you.

I'll be honest, I've looked around but haven't come up with any thing. This could be because i haven't had much experience with using Camcorders video editing applications . Regardless, like any thing else software related i know there has to be a better application than that of the default ones that come with Sony camcorders. So to be more straightforward about it; what is or if not the best lite weight and easy to use application for: uploading/editing and burning footage taken with a camcorder? The default format of the video is MPG -Thanks in advance

Forgive my ignorance, but who is Yzöwl? I've been away from MSFN.org fro about 1.5 years