basicwiz opened this issue on Feb 20, 2013 · 16 posts
basicwiz posted Wed, 20 February 2013 at 8:49 AM
I've just upgraded to a new machine with Windows 7 and of course, there are issues.
I took the second install option, which placed Poser Pro in the programs folder of my C: drive, but put the content in My Documents.
All seems well until I try to save a scene.
My scene files are stored on the E: drive. Poser is unable to write to this drive, and indeed, when I use the dropdown to try and go to another drive, everything is blank. I cannt see any other drives in the system.
I have no problem accessing the E: drive with other programs.
Is this a Windows 7 issue or a Poser Pro issue? Does anyone know how to fix it?
3anson posted Wed, 20 February 2013 at 8:52 AM
sounds like a UAC issue. disable it totally, but if the rig is online,make sure you have a good firewall and at least MS Essentials for anti- malware.
ArtByMel posted Wed, 20 February 2013 at 9:11 AM
I never install Poser in any of the program files. I have a directory on my C drive called "3D". ALL my 3D programs go into that directory. I have about 30 runtimes, all under PP2010, and I access those from PP2012 no problem. All my scene files are saved in my Documents folder under names according to the artwork.
I suspect your problem is installing into the Programs area. I would back it out and install in a separate directory, outside of the program files.
********************************************
basicwiz posted Wed, 20 February 2013 at 9:22 AM
Turning off UAC solved all my problems.
I thought I had it turned off already, but it just goes to prove ASS/U/ME is true.
Justmel... I really THOUGHT about doing it that way, but wondered if there would be install issues for things like python scripts. Does everything install with no problems in that sort of setup?
Janl posted Wed, 20 February 2013 at 9:36 AM
I always install Poser outside of the program files directories and have never had a problem with python scripts. In fact, the opposite has happened with me which is why I now never install to program files.
hborre posted Wed, 20 February 2013 at 9:50 AM Online Now!
Technically BW, that option is recommented for Vista, Win7, and Win8. That is the same option I have selected on a 64 bit Win 7 setup, however all my runtimes are located in the Documents folder. I do have a second hd installed on it; maybe I should drop a runtime in there and investigate whether PP2012 will see it. In you case, there could be admins restrictions on the second drive. But totally disabling the UAC may not be a wise thing.
ArtByMel posted Wed, 20 February 2013 at 9:59 AM
Everything installs just fine. I install the Python scripts directly into PP2012, and everything else is still installed in PP2010. You just add the runtimes and point to PP2010. Works like a dream.
********************************************
hornet3d posted Wed, 20 February 2013 at 2:29 PM
I have Poser 2012 saved to the programs folder on my C drive. The Poser runtime is in My Documents folder which exists on my D drive, in fact all the downloads and temp files are also on the D drive as the C drive is an SSD. All other runtimes are on the E drive, another physical drive, and any work in progress is on yet another physical drive, drive K.
I have UAC turned on and have done so since I purchased Poser 2012 on launch. I have never hit a problem with either opening scenes or saving scenes so it all appears to work. That said I do have other programs also installed on drive D, leaving the SSD just for the most used programs. All programs on drive D work without issue so I would expect Poser to do the same if installed there.
I use Poser 13 on Windows 11 - For Scene set up I use a Geekcom A5 - Ryzen 9 5900HX, with 64 gig ram and 3 TB storage, mini PC with final rendering done on normal sized desktop using an AMD Ryzen Threadipper 1950X CPU, Corsair Hydro H100i CPU cooler, 3XS EVGA GTX 1080i SC with 11g Ram, 4 X 16gig Corsair DDR4 Ram and a Corsair RM 100 PSU . The desktop is in a remote location with rendering done via Queue Manager which gives me a clearer desktop and quieter computer room.
WandW posted Wed, 20 February 2013 at 5:48 PM
You shouldn't need to turn off UAC, Doug. It's actually a valuable security feature. Check your permissions on your E Drive. If it is still happening with the latest SR, file a support ticket.
Just a thought; is your user account an Adminstrator?
----------------------------------------------------------------------------------------
The Wisdom of bagginsbill:
"Oh - the manual says that? I have never read the manual - this must be why."
basicwiz posted Wed, 20 February 2013 at 8:32 PM
Yes to all.
My account is an administrator.
My permissions on the drive are set to full access for all user accounts.
I am running SR 3.1
I've researched turning UAC off. Seems the folks out there are pretty evenly divided on it.
My problem is solved. I'm not going to worry about it any further. My sincere thanks to all who helped!
LaurieA posted Wed, 20 February 2013 at 9:28 PM
Quote - Turning off UAC solved all my problems.
I thought I had it turned off already, but it just goes to prove ASS/U/ME is true.
Justmel... I really THOUGHT about doing it that way, but wondered if there would be install issues for things like python scripts. Does everything install with no problems in that sort of setup?
You bet. It's how I've installed Poser on my computer since Poser 8 ;). Laurie
Morkonan posted Thu, 21 February 2013 at 10:18 PM
I just purchased and installed Poser 2012 Pro on Win7 Pro using the default installation. I have no issues, can run scripts, render, save and access multiple runtimes just fine. I don't have UAC turned off, either.
basicwiz posted Thu, 21 February 2013 at 11:40 PM
Interesting side light on the whole access issue...
I ran into all sorts of (very random) access issues with several programs, even with UAC turned off.
What I finally did was copy all of the data off my E: drive (where my Poser content lives), reformat the drive, then copy the files back. Guess what? ALL of the issues magically went away! It appears that drives formatted by XP don't play very well with Windows 7, (although I have no clue why this might be.)
I have since formatted both of my old drives and am having no further issues.
Go figger!
shvrdavid posted Fri, 22 February 2013 at 7:00 AM
Contray to popular belief, you can't turn UAC off. You can turn it down, but that is not a good idea.
Some things are easy to explain, other things are not........ <- Store -> <-Freebies->
Ajaxx posted Fri, 22 February 2013 at 8:22 AM
Attached Link: http://andrulisart.com
XP-A used NTFS-5 whereas Win7 is using NTFS-7. Files and folder permissions for later NTFS versions are stored in the drive index and not in each individual file, which would explain the issue. Good idea when upgrading the Win7 to back up files, reformat the drives, and reload the files as he did.
hornet3d posted Fri, 22 February 2013 at 2:39 PM
Quote - XP-A used NTFS-5 whereas Win7 is using NTFS-7. Files and folder permissions for later NTFS versions are stored in the drive index and not in each individual file, which would explain the issue. Good idea when upgrading the Win7 to back up files, reformat the drives, and reload the files as he did.
Thanks for that, I did not know that but it does explain what happened. It also explains why I have not seen the problem as my last two systems used new drives and Windows 7 from the start.
I use Poser 13 on Windows 11 - For Scene set up I use a Geekcom A5 - Ryzen 9 5900HX, with 64 gig ram and 3 TB storage, mini PC with final rendering done on normal sized desktop using an AMD Ryzen Threadipper 1950X CPU, Corsair Hydro H100i CPU cooler, 3XS EVGA GTX 1080i SC with 11g Ram, 4 X 16gig Corsair DDR4 Ram and a Corsair RM 100 PSU . The desktop is in a remote location with rendering done via Queue Manager which gives me a clearer desktop and quieter computer room.