So i had to re partition my Mac the other day and loaded Windows 7 on it ..... awesome Win 7 .... the colors etc .. works just like a Mac ... but .... trying to load V4 morphs into my PoserPro directory is hell ... what is up with that? it wont let me, says something about how it has to be in the same directory as the executable file (meaning poserpro?) ..... 

has anyone else had this issue? .... its annoying me and i need a fix asap.

can anyone help?

Either one of two, it's looking for Poser.exe, or it is letting you know that it needs to be where V4 base is located.  My guess would be the latter.

 so it doesnt accept Poserpro.exe?

 Old DAZ installer...

Just make a copy of poserpro.exe and rename it poser.exe..  I think even an empty text file renamed poser.exe will do.  --  Actually, now that I think of it, I must have such a text file in each and every one of my external runtimes, to cope with the installer's request.

Put a dummy Poser.exe in your PoserPro root folder. That's seems to fool the installer ;o). Just make an empty text file and name it Poser.exe. Apparently Daz didn't think everything through when they made their installers - like different versions of Poser ;o).

So, in essence - what you're experiencing isn't a Windows problem but a Daz problem...lol.

Laurie

 Well this is really dumb how i just fixed this .... i opened up wordpad and saved a document as poser.exe .... it worked .... the morphs installed ..... i didnt think poserpro would have this issue.

 Just like Laurie said, it is neither a Microsoft (Winblows) nor a Smith Micro (PoserPro) problem. It is a DAZ installer problem. :)

So that just poses the question, do you really need the whole 200 yards of Poser installed or can you just create a dummy runtime with the dummy poser.exe in it (to not take up disk space) ...?

As it's already been stated, you can just put a dummy poser.exe in any runtime you wish and the installer will work.

A lot of problems with a poser pro/win 7 combo can be solved by right clicking on Poser before opening and selecting "run as administrator" - I nearly pulled my hair out before someone showed me that lol - Poser wouldn't run scripts, or save any files to any of my runtimes, whether poser main or those on my desktop. Seems that win 7 security is more paranoid than secure lol!

 i just need poser in my windows directory for the injection programs to refer to when making injs .... i dont actually use Poser on the windows side at all ... 

You don't need a dummy Poser.exe file.  The real problem with the installers is the names they gave to the two options,  Poser option should have been titled 'either 'Auto Install' or more accurately 'Poser.exe Search'.  DAZ Studio option should have been simply 'Manual' since that is what that option does, it just allows you to manually input the folder you wish to install to.

Mr. Ballmer will be happy to accept your apology along with a pre-paid order for Windows 8

The Daz installers are like getting into 'age-restricted entertainment venues' back in the day - just show the guy a card, doesn't matter what's on it, he just wants to see a card.
 

 haha fat chance .... i'm a Mac user, i love Apple ....

 O.O; Reminds me of when i had to reinstall my DAZ (OS 9 installers) products on a non-OS 9 computer. Sure DAZ has replaced a lot of the old 9 installers with X installers that you can re-download, but not all of them.  So i guess it pays to keep an old 9 computer lurking in the shadows.

.Artemis., the DAZ installer looks for Poser.exe to determine where -or if- it will install V4.  No, they did not have the foresight to make the installer look for either Poser.exe or PoserPro.exe, so if you have Poser Pro or Poser Pro 2010, you'll encounter this quirk.  As Laurie suggested, simply create a .txt file (mine says "DAZ was silly, so I had to make this fake Poser executable."), and save it as Poser.exe wherever you want to install V4.  The installer will create any folders it needs within the hierarchy.

Quote -  Well this is really dumb how i just fixed this .... i opened up wordpad and saved a document as poser.exe .... it worked .... the morphs installed ..... i didnt think poserpro would have this issue.

thanks guys!!! ....

Of course SM could have simply used poser.exe for all versions. It's easy enough to pull the version from the executable if they need to distinguish. They can name the shortcuts whatever they wany and if users need to check for some reason,  they can look at the file properties.  Easier IMO than Daz having to rejigger their installers for different versions. 

It isn't a Windows problem or a Poser problem;  it's a DAZ installer problem.

  It would be easy for DAZ  to modify the installers with a wildcard such as Poser.exe*;  it would be easier still if they simply refrained from micromanaging, demanding that the installation be made in the primary runtime.

DAZ installers already read Poser version numbers in order to determine which versions of MAT poses get installed.

That argument being made, all we really need to do is place a dummy Poser.exe where we want to install, and the problem's solved.  It's not a big deal.  We go on with life.

I would be easier if people would read my post and learn to use the installers.  Further more the installers are nothing more than self extracting zip files.  They make no distinction of the Poser version or whether you choose Studio to determine what to install.  The content in the file is the content that is installed.

"It would be easy for DAZ to modify the installers with a wildcard such as Poser.exe"* 

which would pick up poseray.exe probably among others, though that may only be a technical point.

"  it would be easier still if they simply refrained from micromanaging, demanding that the installation be made in the primary runtime."

Agree 100%

" Further more the installers are nothing more than self extracting zip files."

Not the case AFAIK. Neither WinRAR nor WinZip will open them. They (the latest ones) are Bitrock installer files. You can use a special utility to extract some of the older versions, but there is no runtime structure inside them - all the files are dumped in one place.

All right! technically they aren't 'self extracting zip file's.  But that is essentially how they work.