For all the crap that we install? I'd think it would be pretty easy to read the runtime, just lik eposer does, and then list the items installed. you could then have a windows like browser for moving, or deleting items. the problem with just yanking things, is all the places they put associtated files, like textures, poses n such. There REALLY should be some kinda management program available by now.. didn't anyone notice this problem in poser 1-4??

P3DO comes close - the problems with an uninstaller would be: more than one .??2 file may refer to the same OBJ or texture (all the Poser 4 Male Characters and Female Characters call the same geometry as Posette and Dork, you probably have multiple M/V1 chars. calling their respective geometries, lots of free V&M textures call the default lash and brow trans). there's no ready way of reading which character or outfit a pose file is for, so if you zapped the CR2 and support files the MATs would be left behind. people move stuff around, which would kill a history based uninstaller.

I've been thinking about this for a while also. I'm on a PC but a program that worked like MAC Suitcase, or Adobe Type Manager would work. Suck the contents of a zip file or a .sit file and the 'uninstaller' would have the files that it needed for that 'product' to be uninstalled. Seems like there should be something like this. Poser 5 with multiple runtimes helps the problem some for runtimes. Often I install a zip file not remembering what it actuall IS, then want to uninstall it cause it's something I didn't want and have to manually go through each and every file to get it out of my runtime. very time consuming. Even an independant program that you could run and show a list of what has been installed or 'products' listed so they could be turned 'on' and 'off' so runtimes could be cleaned up easily would be cool. At one time my Runtime for Poser 5 was 13 gig. Kinda large but I didn't have all the references to 'uninstall' all the crap that I didn't want or would no longer use. With large hard drives and Poser5's multiple runtimes I don't actually have trouble with how big my runtime IS, or poser use, but I don't use everything in my runtime and have no easy quick way to clean up and clear out the runtimes I have. I think a programmer could make a killing with a product that worked well for this. The one single application that I'm really desperate for. Hope someone reads this thread and takes it to heart, I'd love it.

Well, as I said P3DO is close - click on a CR2, PP2 or PZ2 and it will list the OBJ and texture files referred to, but it won't let you do anything to them (yet).

If daz and everyone else (commercial) used the standard wise installer/uninstaller, then it would be pretty easy. For the little guys, just having some database entry that would delete the newly installed items would help.

I hate it when people use uninstallers and clutter up my menu with their stuff. I can uninstall it myself. If they decide to do this I would hope they give us the option of not having the uninstaller. Marque

I like a standalone that did this. I agree with Marque about a bunch of uninstaller entries on the start menu and Add-Remove progs. Such a program would probably have to create database of your textures, geometries, libraries and so forth to know what is linked to what. Also it would likely be faster than searching through all the folders. It could also list rogue files like Geometries that have no parent prop, hair or figure. I better start writing it. Wait... I don't know how to code. Dammit.

Don't have an uninstaller. Such a thing would be so huge and mess up the registry and make it big enough to cause problems, particularly with Poser Addicts. If you have something you can just find it by searching and delete it (do a search by date to help cut down alternates). Registries have a limit on size and go slower the bigger it gets. Please do not make an uninstaller. I would rather waist a little space then have my comptuer crash completely because of registry overflow.

Maybe I misread the above, but the P-UN library uninstaller from the freestuff or konan's Innendo Software might be what you are looking for. It gets rid of library files and their associated files. I've found it very helpful. :)

Under NO CIRCUMSTANCES, ever, would I use any kind of uninstall for anything Poser. There is almost not a single file in a folder where it is 'supposed' to be since I put everything where I want it to be. An uninstaller is a very bad idea. Go pick out the files you want to remove and delete them yourself. An application on the other hand should have an unistaller deicated to it. There is no way ordinary non-prgrammers can work out all the angles in the registry. :] Fish

well this is how i'd see it working. run the 'uninstaller' app. point to a zip, sit, or installer.exe file. it scans and puts the refences in a database. and installs the files based on where they go. now you go and move the files. you run the uninstaller and select the 'product' you want to uninstall, hit the scan button, and scans the runtime and compares the 2 sets of files, asks if you want to uninstall. oh well, I like the idea, I need it, I'm not going manually through 20,000 files in my runtime picking and pulling. right now I just whipe the whole friggin thing and start over from scratch, which is a pain in the rear.

I conqure this two ways: When I install something from here or DAZ I usually do so to my My Documents folder. Then I go ahead and rename all of the directories(I can...) to something simple and similar. The other is tow develop more than one runtime i.e. one for M2, V3, Fantasy, Props, etc.

Its easy enough to uninstall if everything is in one directory, but when code is put in the win and win 32 and winsys and win this and winthat directory, its impossible to figure outwhat dll or what sys needs to go. I've watched my win sys directory swell to epic proportions over the years and I just buy more HD to warehouse that crap. Yes, I'm on an upgrade system that started out as dos 5 then to dos 6 then 6.22 then win 3.1 then 3.11 then sys32 on 3.11, then 95 then 98 then ME then ME dual boot with win2kpro. Its still running strong, but boy do I have to tote around a large bag because folks either don't write unistall programs or deliberately leave behind files that are designed to catch folks on reinstalling demos. What a mess. Has anyone ever heard of a LOD? Letter of Destruction? I'd rather send a LOD and have my drive cleaned up than have files left behind without permission to "police" me from rerunning something.

I wonder if all those folks who leave stuff behind would kindly send me money to pay for the new HD to hold all their crap?

Didn't Konan make one? Called P-Un found on the bottom of the page in his downloads section ;)

We've been testing the program for a while :) It may be out soon :)

Since I got P5, I had the chance to start a new file system, learning from the mistakes I made with P4. ;-) The multiple-runtime folder support is great, and I use it to keep my installs lean and easy to un-install - here's how: Only install things to your default runtime that are basic figures, hair, props, clothing etc. that you will be using over and over. (just the main cloPacks - not all clothing unless you will use something repeatedly over a long time). For each new project create a special runtime and install anything you need specifically for that project. As you work on that project ONLY use items in your Main runtime or the ONE for this project - this may mean that you sometimes install an item in more than one of your temp runtimes, but it will avoid large problems later. When the project is done, archive the custom runtime along with the final pz3 on a CD or zip it all up, and delete the original folder. You will always have your basic stuff in the main runtime (which you should back-up from time to time), and you can re-install a complete runtime from CD or ZIP if you ever want to edit or modify a project.