Shame on me... months ago... I just remember that it was so frustrating that I never bothered to give it another try...

The best idea might be a really good search feature - I tried the search field a couple of times, and never got a useful result, to be honest. Is there a chance to get the posts indexed? If you are allowed to look for "Koyko Hair" in the content of posts, you got it!

Dont't try to treat the .rsr files with ResEdit - it's not working. Just drag the whole stuff (.rsr's included) onto Maconverter, and it should do its job... http://www.main-rheiner.de/homepage/soft.rabbit

Hi, one little note about the URL: I'd prefer if any postings of it would go http://www.main-rheiner.de/homepage/soft.rabbit My ISP is changing the internal path quite frequently, but the www version will always point/switch to the current one.

Hi, just got a chance to drop in here before my return... Kathleen, the PoserWorld CD gets all file names spoiled when used directly on Mac. I wrote some AppleScripts that will copy the content properly to your Mac disk. Unfortunately I can't remember the URL of my own stuff right now :-) Go to PoserWorld, visit the Links page, and there is a download link to the scripts. This might help, if not I'll look at it next week. Cheers, MartinC

The original PC version is "Mover", for the Mac use "Poser Maconverter" - both are on this site's FreeStuff in the Utilities section.

Sorry for abusing this old thread for a personal matter... Wander, I haven't got any reply from you for ages now, but I ran into some e-mail blues recently. If you did send anything, please try to drop me a note otherwise, eg by web-mail through this board. Cheers, MartinC

Nance, not sure, but it could still be a misunderstanding: The possible problems have nothing to do with "unzipping". Your trouble with agnes stuff is due to MacBinary. I mailed her, and if I got it right she is going to re-post repaired versions. The "renaming" problem could occur with ObjAction Mover - and PhilC is using .pcf very often. So this is something seba could try to re-check again.

This could be a mixture of two things: 1) All files by agnes are zipped Mac files which are (probably accidently) MacBinary encoded. This is an unlucky setting of the zip compressor which damages the files for both Mac and PC, because everything should be named "xxx.bin" in order to extract properly on the Mac as well. Dear Mac Poser creators: Please pay attention to this - turn OFF MacBinary if you zip stuff for the net. You can turn it off in your zip compressor, or you can use my tool to delete the resource forks to be safe. The best choice is probably to use the converter to export for the PC and then zip it - suits everyone on both platforms without restrictions. If you ever need to use MacBinary, preserve the .bin extensions, otherwise there will be garbage. Maconverter is repairing it on conversion, but this is no excuse for doing the mistake in the first place. Back to the original topic... 2) Maz once told me about a problem with the french Poser and .pcf - some Geometries .obj's seem to have capital letters. Unfortunately, Mover 1.01 is strictly case sensitive. Until it will be fixed, the only workaround on PC would be to rename the seedfile to lowercase in France for non-french .pcf, and to uppercase everywhere else for french .pcf files. Thankfully no problem on Mac, because Maconverter is not case sensitive. Hope that helps, MartinC

Jeff, I tried it myself and it works flawless. I inspected the .pcf manually and it looks perfectly fine - it even decodes with the earlier tool versions on Mac (which should NOT be used any longer, Maconverter 1.1.x only folks!). Maybe you can ask JVipond to get in touch with me as well, I would need more info about the way how the conversion fails in order to help. Cheers, MartinC

Maz told me once that he gets a constant stream of requests for the Mac version of ObjAction Mover - he even recommended to post Maconverter a second time under the different name... :-) To clear it up for new visitors: The full features of ObjAction Mover are built-in in Poser Maconverter, you don't need a further utility. There once was a separate tool called "PCF Decoder", but it is obsolete & withdrawn now, and it could even cause trouble with P4 stuff - please don't use it any longer. There is a modification called PCF 1.1 which is fully supported by Maconverter and which solves all decoding problems on the Mac automatically - and it also allows Poser creators to encode files that will work with Mover 1.01 (until it supports 1.1 as well).

I think the trouble is on their website. If you try "http://www.macnn.com/contributions/" you can't reach any of the other links as well. Maybe they are doing roadworks with their files and bring it back later.

Ikyoto, as I said before, I totally understand this and fully support the way how you handle it. I just wanted to take the opportunity and point out the problem - the past has shown many times that a lot of users (even with good intention) are not aware of this legal difference, and quickly ran into a lot of trouble. Cheers, MartinC

Of course I wasn't accusing you... I was just referring to your quoted "Go ahead and give it out for non-commercial use/don't sell/no altering/just give me credit/etc/etc" line. In my opinion this doesn't automatically include re-distribution (unless the /etc/etc parts clears it :-) I think whenever some stuff is not clearly marked as "in the public domain" or has a freeware clause which explicitly allows a certain thing, it'll be good not to assume anything but better ask for permission first.

I hope I'm not going to spoil the party, but in my point of view any re-posting of other people's stuff is a very nasty thing to do. There is a difference in "using" (eg use a texture/prop in Poser) and any sort of "distribution" (eg post it on one's site). A read-me telling that the stuff is free for usage, doesn't include the full rights to do with it whatever you want. Therefore I can only suggest that you try to get the permission before you do it - if the read-me already includes an explicit passage about it: fine. If not - PLEASE ask. It prevents you (and the creators) from a lot of potential trouble. MartinC