kreidas123 opened this issue on Jun 20, 2010 · 56 posts
Dave-So posted Sun, 20 June 2010 at 3:04 PM
i know you're having problems , but you're making a mountain out of a molehill, as do the majority of new Poser and DAZ Studio users, and also a lot of people that think they know what they're doing but actually don't have a clue.
Pay attention to where you install things.
When you installed Poser8 it told you exactly where it was going to install itself. YOU had a choice in changing the directory path. If you allow it to default, it goes to your C drive. The words on the install directory path are stated .. C:Program FilesSmith MicroPoser8 ... each and every time....unless YOU change it.
Installing product files is a piece of cake. Where new folks go wrong is when they're trying to get creative and install to different than where the stuff wants to be installed. Do default until you know what you are doing.
The DAZ installers are quite easy to use, contrary to the statements made. You can change their install directory to wherever you waNT .. however ...THE daz FIGURES , FOR THE MOST PART, NEED TO GO INTO THE pOSER root RUNTIME DIRECTORY, which is where Poser is installed and the poser.exe file resides. In case you do not know what an EXE file is:
EXE is the common filename extension denoting an executable file (a program) in the DOS, OpenVMS, Microsoft Windows, Symbian, and OS/2 operating systems. So Poser.exe is the file that runs to load Poser so you can use it. The DAZ installer needs to see that program so it knows that it can install the product to the CORRECT place.
ITS QUITE SIMPLE. point the install routine there and you're done. The DAZ installer will also search for Poser and allow you to approve of where it will install to. Place all of them in there until you learn the file structure of the program. In your case, it seems you need to learn the file structure of using a computer and how to manipulate your OS so you can find stuff as well.
The Poser program itself, is doing exactly what it is meant to do upon installation. It can't get any easier or simpler than it is.
If it sounds like I'm being harsh, don't take it too personally. Do things simply. Read the help files. Read the boxes that pop up when you try to install things. I'm just trying to help you and the rest that seem to ewant to take the same path ... kind of like the cart before the horse. Learn the basics first. If you don;t know, read...then ask when you're totally stumped. don't blame the program or the installers as they work for most people all of the time. I never have problems with them in Poser.
I download all of my purchases to a directory outside of Poser. I have D:Downloads then I have sub durectoruies for each store that I shop or by creator. I then unzip zipped products directly into those directories then copy the resulting runtime directly over the Poser runtime. This allows correct placement of all directoried and files into Poser.
The DAZ installers, once they find your Poser install, will always install there automatically. It remembers the path to use. Its a no-brainer.
NOW ... to screw with your mind, as that is what you seem to like to do, as well as others, is the fact you can have runtimes outside of the actual Poser directory. Again, this is a no-brainer. The DAZ installers need to see the Poser.exe file as discussed previously. You can make a dummy on by opening Windows NOTEPAD and typing a letter, ehatever, then saving the file calling it poser.exe. You then place that file or save it upon creation, into the external runtime you are creating. Then when you run the DAZ installer , you can point it to that external runtime and it will install the stuff to the correct directory/file structure needed for Poser. AGAIN: REMEMBER THAT CETTAIN DAZ PRODY}UCTS REQUIRE THEY BE LOADED INTO THE KMAIN POSER RUNTIME TO WORK> the readme usually tells you that, although if there is one weakness to the DAZ installer, you can't see it until its installed, so what to do? be safe and install it direct to the main poser runtime or try and find out if it can be installed outside of it. Another trick is to install to a dummy runtime so you can read the readme...then you know where it needs to go and you can install again to the correct place.
by now your eyes are glazed over so I will stop. Use the KISS principal Keep It Simple Stupid, and you will do just fine
Humankind has not
woven the web of life. We are but one thread within it.
Whatever we do to the web, we do to ourselves. All things are bound
together.
All things connect......Chief Seattle,
1854