I'm having a problem with files becoming unreadable in Poser 6.  They show up ghosted in the folders, sometimes only minutes after I've loaded them into the scene and subsequently deleted them.  It's happening with .obj and .jpg files.  I just downloaded a new file and all the textures are ghosted.  I've tried to drag them on to the desktop and apply them manually in the material room but nothing works.  The files themselves are fine because they can be opened with other applications.  Does anyone have any idea what is happening?  For information's sake, I run a Mac with OX 10.6.4 and 4GB RAM.

Could you post a screen shot example of ghosted items?

Unfortunately, resolution is reduced so much we can't actually read the folder content.

Rename the additional Runtimes to Animals, V4 etc. Runtime in combination with something else makes Poser to hide those folders.

I renamed them R_Animals, etc., and added them to the libraries, but it didn't make the texture files show up.  What should I try next. 

I discovered the jpeg's will only open in Preview, not any other program.  I can open them in Preview, save them as png's then open them in my graphics program and resave as a new jpeg.  That way the material room will see them.  I discovered this late last night and haven't had time this morning to convert all of the textures into a new folder to replace the old ones in Poser to see if they are recognizable.  I'm not sure how to do this with the obj files that won't show up.

2 possibilities:

1. the Poser search is not set to Deep (Ctrl + k - library - File search)

2. the path in the cr2 is not correct as in some cr2 the runtime:texture: is missing for texture files (search for .jpg)

Assuming it's one of these, what do I need to do?  I have only rudimentery computer skills and don't immediately understand what you're suggesting I do.  Could you expand your explanation?  Thanks.

The first thing is easy as above explained. Open Poser, go to Edit => General Preferences  (Ctrl + K) => Library Tab and then check if the File search is set to Deep.

The 2nd thing is, if you have only little knowledge about computers, not so easy so I suggest you try the first thing.

The error I notice, the runtime folders are named something other than runtime.  For Poser to detect a runtime, you must create a folder first, name it whatever convention you like, and place the content runtime folder within.  Do not rename the runtime folder itself.  Poser will not recognize that format as a runtime.

Quote - Open Poser, go to Edit => General Preferences  (Ctrl + K) => Library Tab and then check if the File search is set to Deep.

P6 doesn't have that option (it was introduced in P7).

The main problem here is that you shouldn't be putting additional Runtimes in your P6 program directory (the problem with naming was covered earlier).

I suspect that MacOS may be setting the permissions on files differently in directories that it expects to contain programs rather than data.
The other possible problem premissions-wise would be that they're set in such a way that because they're owned by another user you're getting an indication that the user you're logged in as doesn't have full access to them.

Nruddock, I don't think that's the issue.  If you note my post above and view the OP's screencaps, the runtime folders are named incorrectly.  You can nest numerous runtime's within the primary Poser folder, as long as each runtime is contained within it's own individual folder.  We forget that there is a separate download folder within Poser that contains it's own runtime structure; we just overlook it because we don't want to overcrowd the primary with too much content.

What causes files to be greyed out must be mentioned in the documentation somewhere, so once we know what the possibilities are, we should be able to tell which one(s) applies to this situation.

I'm getting confused.  Originally I had "Runtime" in front of the name of each folder, ie "Runtime V4**". ** Jules53757 said having Runtime in the title would confuse Poser, so I renamed them with "R_" in front.  Now hborre says I have to have Runtime in the title so Poser can find them.  To be perfectly honest, they seem to work either way as far as switching from one to the other.  The problem seems to be with some of the older DAZ items like Noggins Macaw (the texture's ghosting that started this discussion) and the MFD extensions and V4 Hooded Cloak whose .obj files are no longer recognized.  When I first downloaded them, everything was working fine.  Someone in the DAZ forums suggested it might be a mismatch between Poser 6 and the 10.6.4 operating system.  I can "remake" the textures**,** but I'm not sure how the resurrect the .obj files.  Solving the root cause is not looking too promising so I need to be able to treat the symptoms in some way.  Any ideas on a way to "update" the .obj's and still retain their original flexibility? **
**

If you want to make a runtime for animals that shows up as "Animals" in Poser then name the directory that's the parent of the runtime folder "Animals". You still need to have a folder called "runtime" (which contains "textures", "geometries", "libraryies") below the "Animals" folder, otherwise you'll run into problems.

poser is expecting this

YourRuntimeNamehere / Runtime /

where YourRuntimeNameHere is whatever you want it to be, eg Dazfigures then the Runtime under that.