Cylithera opened this issue on Sep 17, 2003 ยท 36 posts
Cylithera posted Wed, 17 September 2003 at 2:10 PM
I don't know what's wrong with this thing. It's a cool looking program, if it would actually work. It runs fine, and when I just open Poser, it can switch banks. But after spending a little time in Poser, making a picture, or whatever, and I try to switch the banks, it has sort of error. That you have to run CorrectReference, or something. I did that, and it's still doing it. -_- It's like some other program is using the Poser stuff. But I don't have anything else open! Someone help, please. I hope that makes sense, because, it doesn't really make sense to me. ;) Windows XP Home and Poser 4.
steveshanks posted Wed, 17 September 2003 at 3:34 PM
Sorry just boomarking coz i get this too...same OS but Pro pack..Steve
nickedshield posted Wed, 17 September 2003 at 5:26 PM
me to. Ver 1.4 also has a bug I'm waiting to hear what the fix is
I must remember to remember what it was I had to remember.
SamTherapy posted Wed, 17 September 2003 at 6:06 PM
When PBooost locks the files, they won't be unlocked again until you shut down and restart Poser. It usually means a texture path reference is incorrect. You can correct it within PBooost by using the Deep File Editor, or externally, by using Correct Reference. I generally run every new model/prop/whatever through Deep File Editor before I start Poser, just so the references are correct before I start. I used to get the file locking problem a lot, but now it happens hardly ever. As for the bugs in PBooost 1.4, yes there are some. Hogwarden is working on them and using me as a guinea pig to sort 'em out. They're weird and so far I'm the only one who seems to have encountered them.
Coppula eam se non posit acceptera jocularum.
Cylithera posted Wed, 17 September 2003 at 6:14 PM
Sounds good. But I have run CorrectReference on a bunch of stuff, but it's still doing it alot. -- It sucks to have to shut down poser and restart it, too. Arr. --
RealitysPoison posted Wed, 17 September 2003 at 6:23 PM
There seem to be a few bugs in the new version. I messaged the author about them, and he said he is aware and is working on a fix. Hopefully he will be done soon. (And the file locking caused by references in Poser isn't the only reason it is doing this. I have had it happen without poser even running, so don't kill yourself with correct reference. If you ran all your files and they came out correct, it is probably part of the bug.)
Cylithera posted Wed, 17 September 2003 at 6:33 PM
Well, darnit all. Okay. ;) Thanks for your help, you guys. :D
nickedshield posted Wed, 17 September 2003 at 6:40 PM
SamTherapy, Have you encountered problems with the browser not wanting to undock and then not diplaying the scroll bars? That's as far as I took it before reporting the bug.
I must remember to remember what it was I had to remember.
3ddave44 posted Wed, 17 September 2003 at 8:12 PM
I'm also on XP (where the locking is more of a problem) and I spent a good amount of time going through all the texture references in the MAT files in my pose library and the hr2 and cr2 files that load textures. I went through them all in the Deep File Editor and corrected everything. (In some cases, where the set had many many pose MATs, I corrected one in the Deep File Editor and then in a text editor globally replaced the incorrect reference with the new, correct one. That saved a lot of time). The whole process was time consuming (over a month of nights to do...) but it had to be done. Now I don't get the locked error window and I do do as SamTherapy and check the texture references in the DFE right after installing anything new. THEN, Pbooost is a DREAM. And I've not encountered any bugs with 1.4 - though I also don't use the new things like thumbnail display...
Spit posted Wed, 17 September 2003 at 8:27 PM
When the message comes up about correcting references I want to scream. My references ARE correct. I'm also on XP. But what I've noticed is that when you save things from poser, poser itself does not put the whole reference in the file. And sometimes if you reload a saved pz3 especially, things go wonky. And XP itself creates locks. Especially if you toodle around in Explorer in thumbnail view. If ever you've gotten the message, closed Poser, and tried to switch banks again and STILL get the message, it's XP. And the only way I've found to reliably get rid of the locks is to reboot. When everything works it works great! But there's never a guarantee if you're on XP so I hold my breath now when I use Poser and come to a situation where I need to switch banks.
3ddave44 posted Wed, 17 September 2003 at 8:38 PM
Spit - That's funny, I know what you mean about holding your breath before doing that final click. I have been on that cliff. : ) Now let me relate something else. Last night, I loaded the Sassy Hair from DAZ. I loaded a model and applied the hair, upon trying to 'switch' to the Hair MAT folder, I got the LOCK. So I went to the Hair MAT folder in the Deep File Editor (from now on DFE), and there was one wrong reference. I corrected it, rechecked the others and tried again. I got the same problem. Loaded a model, loaded the hair, tried to switch and BOOM. So I checked OTHER files in the folder and tried again. Same thing and gave up for the night. Well sleep rounded me out and in the morning almost instantly upon wakening (sad, huh? [g]), it occured to me that the hair file itself (the hr2 file) must be loading a texture that is wrongly referenced. Opened the DFE and loaded the hair and Son of a... the file had a wrong references - I corrected it and now, smooth sailing. The point of that whole story is that I learned to remember that when I think I've corrected everything (meaning mostly pose MAT files) there's a possibility that the base file itself may load textures that could be referenced incorrectly. Dave
3ddave44 posted Wed, 17 September 2003 at 8:42 PM
Addendum to previous post: ...and from the moment you've used (or loaded) something that is wrongly referenced, you'll get the error upon the next "switch" - even if the references in the folder you're switching to are correct. Dave
Spit posted Wed, 17 September 2003 at 9:22 PM
Yeah..so true. Poser locks the folder when it hunts for something. If it finds it, it unlocks it. If not, it doesn't and you're stuck. I install everything to a Poser Install folder and run Correct Reference on the entire folder before I move the stuff into Poser. So basically for me locks happen when I'm searching through my Poser stuff with Explorer or organizing it. Or sometimes saved pz3's do it. Not sure exactly why. When I remember I reboot before opening Poser. Luckily XP reboots pretty quickly.
RealitysPoison posted Wed, 17 September 2003 at 9:40 PM
:D I keep a seperate bank for "new" items, so I can run correct reference on just those banks. (Saves time, as it took me 23 hours to run my whole runtime. lol). I also run all Pz3's through CR. Works like a charm on them. In amongst the errors for the new version, I lost all my defaul banks. (Don't ask me how THAT happened...scratching head). But even with PBoost somehow locking itself up, I still use it. I'm sure he will get a bug fix soon. :D
elizabyte posted Wed, 17 September 2003 at 10:43 PM
I used to have a lot of problems using PBooost in XP (I still have problems with version 1.4; I went back to 1.3 and will await fixes). What I do now, though, is exactly what has already been suggested. I install everything to a temp directory, run CorrectReference on it, and then move it. Sometimes I also run CorrectReference on the new folders once they're in the Poser directory, as well, if there was a "missing" file that should be installed there but wasn't in the temp directory. I also run CorrectReference on .pz3 files before I open them. It works perfectly and saves lots of hassles. The problem is XP and the way it locks files, unfortunately, and the bug in Poser that causes Poser to keep a file open when it can't find a reference. XP ticks me off in lots of ways with that stupid "file locked" message (I get it in many forms, because of my personal workflow). In all seriousness, I really find PBooost to be a huge help. I'm thankful that I went back to version 1.3 as quickly as I did, though. I've heard a couple of stories about people losing whole banks due to the bugs in version 1.4. :( bonni
"When a man gives his opinion, he's a man. When a woman gives her opinion, she's a bitch." - Bette Davis
nickedshield posted Wed, 17 September 2003 at 11:10 PM
Has anyone had correct ref give a series of access violation errors? I had a slew of them ranging from dll's to memory.
I must remember to remember what it was I had to remember.
Cylithera posted Wed, 17 September 2003 at 11:53 PM
Oh, geez. -- I definitely -don't- want to lose -any- banks. -- That would incredibly suck. I guess I'll have to go back to my flooded, scrolling menus until these things can be fixed. ;)
elizabyte posted Thu, 18 September 2003 at 2:52 AM
"Has anyone had correct ref give a series of access violation errors?" YES!!! This is why I uninstalled version 1.4 and went back to 1.3 so quickly. I got a complete cascade of the errors, it was actually kinda scary. Geeez. I keep wondering about the beta testers for this release. Did NONE of them have WindowsXP? And yes, I know someone who lost her entire Props bank. She's furious, to say the least. I don't want to be rude because I really like Hogwarden's stuff, generally speaking, and he's a very personable person in my experience. I just can't figure out how this release managed to escape the notice of the beta AND store testing. bonni
"When a man gives his opinion, he's a man. When a woman gives her opinion, she's a bitch." - Bette Davis
Spit posted Thu, 18 September 2003 at 3:06 AM
Did she actually lose the files? Or is it something 'repairable' with Explorer? I haven't gotten any cascading errors (yet anyway). It probably has to do with what versions of specific system files we have.
TrekkieGrrrl posted Thu, 18 September 2003 at 3:15 AM
I had some weird errors too. I didn't exactely LOOSE the banks but I had to manually rename them to get them back in a working condition. Can't remember which ones they were, but it had me in cold sweat for a moment there L I've also had a neverending cascade of error messages popping up a few times. ctrl-alt-del to kill Pbooost removed them. They have happened when I was trying to move more than one item at a time between banks. I spent the whole afternoon/evening/night 2 days ago running Correct Reference, yet first loaded file yesterday gave me a folder lock. BUT It WAS a pz3, stored outside of where CR fixed things, so that's prolly the reason. All in all I couldn't live without Pbooost, but it has some issues. Some of them probably WinXP related. Yes, I'm using WinXP Home too. On NTFS drives.
FREEBIES! | My Gallery | My Store | My FB | Tumblr |
You just can't put the words "Poserites" and "happy" in the same sentence - didn't you know that? LaurieA
Using Poser since 2002. Currently at Version 11.1 - Win 10.
Gorodin posted Thu, 18 September 2003 at 4:13 AM
Anyone else trying to run PBoost on a multi-monitor/multi- viseo-card system? I got an abnormal program termination error on my dual monitor system. The problem is related to OpenGL and card drivers (not PBoost's fault). Using only a single monitor fixed the problem. Theoretically, using identical cards (mine are not) should work. Has anyone had success with this?
Phantast posted Thu, 18 September 2003 at 5:12 AM
Oh dear ... I have tons of wrong texture file references which I don't normally care about because I don't use textures within Poser. Maybe PBoost is not for me ...
RealitysPoison posted Thu, 18 September 2003 at 10:22 AM
"Has anyone had correct ref give a series of access violation errors?" YUP! And it is reparable with explorer. What you end up with is generally two banks with the same name and you can't switch. (Happened to me twice) It had the "loaded" bank using the same as another, but you couldn't rename it in PBoost. I used explorer to rename the bank that was name "whatever" character. Then I could switch. But it did it to evey bank in which the default wasn't loaded, so it was a pain. (That is why I no longer have default banks in some way...)
thorntoa posted Thu, 18 September 2003 at 11:21 AM
I'm running XP Pro, Dual Monitors and using a single twin head ATI card. Not exactly what you are referring to Gorodin -- but similar. I've had no OpenGL problems at all.
Allan Thornton
Gorodin posted Thu, 18 September 2003 at 11:39 AM
Thorntoa, Thanks. I know that a single twin head card will definitely work. As far as the System is concerned, that counts as a single card. Cheers, =G=
nickedshield posted Thu, 18 September 2003 at 11:43 AM
So far I haven't seen two banks. Lucky? Don't know. It would be nice to have a 'file only' moving program to clear the pose folder. The more bells and whistles the more room for glitches. Sometimes simpler is better. Just my humble opinion. PS As it has been stated above, when it works, it works great.
I must remember to remember what it was I had to remember.
Larry F posted Fri, 19 September 2003 at 7:49 PM
Just found this thread, admittedly haven't read all the way through, please excuse if already covered. I just upgraded from Win98SE to XP Home (yeah, I know, kind of slow to do so, but better late than never)! I'm very happy with this so far, but now I've discovered I have to close Poser to switch banks in PB1.3. Keep getting that "...fat32 ... recommend change to NTFS..." dialogue. Other than reformatting to NTFS, what can circumvent this problem; would upgrading to PB1.4 fix it? Thanks. Larry F PS: I'll go read the rest of the posts now.
3ddave44 posted Sat, 20 September 2003 at 8:38 AM
Larry -
Perhaps you will find out in the previous posts but what's happening is the pz2, cr2, hr2, pp2 (pose, character, hair and prop) files in your folders have texture map references whose paths are incorrect. Without Pbooost, this doesn't matter. Poser will load called for textures as long as it finds them anywhere on the machine and regardless of the path used in the file. With PBooost, the references have to be correct. The MAT pose file (or any of the others I listed) cannot call for "C:posermapmytexture.jpg" if the file is actually in "runtime:textures:ken:mytexture.jpg". So what has to be done (and it's a JOB) is that all your files which call textures have to be adjusted with the Deep File Editor (comes with PB) or CorrectReference, a separate program also from Hogsoft. That's the bare bones explanation. Once the references are correct, you'll be able to switch banks without the program finding the conflict and locking. This, by the way, is apparently a problem with how Poser proprieterizes the windows file/folder system.
WHEW! : )
TrekkieGrrrl posted Sat, 20 September 2003 at 12:30 PM
3ddave44 - that is exactely what Correct Reference is for :o) No hassle at all, only a lot of time needed while the computer does the work. Start it and go to bed. Then it'll be almost done when you get up in the morning (no kidding!!!) But no messing around with Deep File Editor at all :o) Anyway you're right, the references MUST be correct for Pbooost to work. If not, then it WILL lock the folders.
FREEBIES! | My Gallery | My Store | My FB | Tumblr |
You just can't put the words "Poserites" and "happy" in the same sentence - didn't you know that? LaurieA
Using Poser since 2002. Currently at Version 11.1 - Win 10.
elizabyte posted Sat, 20 September 2003 at 12:46 PM
Anyway you're right, the references MUST be correct for Pbooost to work. If not, then it WILL lock the folders. < This isn't the fault of PBooost, though. It's the fault of Poser, which doesn't properly "close" a file when it finds a missing or incorrect reference. Just wanted to be clear. I really like PBoost, I'm just going to wait until the bugs are fixed in version 1.4, that's all. I'm still using version 1.3. ;-) bonni
"When a man gives his opinion, he's a man. When a woman gives her opinion, she's a bitch." - Bette Davis
TrekkieGrrrl posted Sat, 20 September 2003 at 2:10 PM
Yes you're right, bonni. Thanks for clarifying :o) I'm using Pbooost 1.4 and though I just had one of those "exceptions-cascades" tonight, I still love the thumbnails too much to ever go back to a previous version G Without Pbooost, my Poser would be useless, I have FAR too many folders - and too much stuff to ever be able to use it, was it not for Hogwardens brilliant invention :o)
FREEBIES! | My Gallery | My Store | My FB | Tumblr |
You just can't put the words "Poserites" and "happy" in the same sentence - didn't you know that? LaurieA
Using Poser since 2002. Currently at Version 11.1 - Win 10.
Larry F posted Sat, 20 September 2003 at 2:27 PM
3dave44, elizabyte (love that nick!), ernyoka1 Thanks to all for more clarification. I HAVE been reading through the posts about this and I have Correct Reference, which I always wondered about but, since I had VERY FEW problems with PB 1.3 heretofore, never used it. Now I can see that I will have to dive into this, as I hope I do not have to be closing Poser everytime I want to switch banks. I'll probably be back to ask more questions, LOL! Of course, with the thumbs that are available in 1.4, that might not be such a bad thing. And it's true, hogwarden created a very great thing with this program. Hands down the most useful thing for Poser I ever bought. Larry F
3ddave44 posted Sat, 20 September 2003 at 9:05 PM
ernyoka1, et. al.,
In regards to using Correct Reference over Deep File Editor. I have found when using DFE, that sometimes textures from different texture sets have the same name, and that the DFE will use whichever it finds first and it may not be the correct one. It'll satisfy the need for a correct reference but it may not be the actual texture the pose file wants. And so I have assumed (perhaps incorrectly) that the same thing would happen with the program Correct Reference except that I wouldn't have the control or option to not have it save the file with the wrong texture... Like I said, I don't know if that's so but it wasn't worth the risk to me to have to ultimately search through files that may have actually been Incorrectly Referenced (pun sort of intended).
I have found this to happen mostly with reflection maps. For instance, I have a few called "gold.jpg" and I've had the DFE want to "correct" whatever file I'm working with with a gold.jpg that I know is from some other texture set. Also this has happened with hair files. I've had "black.jpg" files for clothes want to become the "black.jpg" for hair mats.
So you see my concern with Correct Reference? And these corrections may have happened unbeknownst to you. So after all that, does anyone know if this situation is the case with Correct Reference the program? Dave
TrekkieGrrrl posted Sun, 21 September 2003 at 2:24 AM
I've encountered your problem, 3ddave44, but only when Poser itself was looking for a file. Never had CR make a wrong reference. At least not that I have ever discovered. Your point is valid though, I don't know if/how CR checks for the RIGHT "black.jpg" in a reference. Another great incentive for merchants ect. to give your textures UNIQUE names. (not that I am perfect at that either)
FREEBIES! | My Gallery | My Store | My FB | Tumblr |
You just can't put the words "Poserites" and "happy" in the same sentence - didn't you know that? LaurieA
Using Poser since 2002. Currently at Version 11.1 - Win 10.
aodor posted Thu, 23 October 2003 at 6:32 PM
Same problems as all of you. How is PBooost uninstalled in order to work with poser the old way, until the fix for 1.4/XP is available?????
Khai-J-Bach posted Thu, 23 October 2003 at 7:36 PM
okies... here's what worked for me.. I don't login as the Admin but a power user... I was getting all the folder locked errors when I tried to change banks.. even after running correct reference.. this puzzled me and I looked deeper. I found that while I was a power user, I did'nt have full rights to any folder! only Admin has that.. so I gave myself full rights to my poser folder... and the errors stopped. until the next widget install, but a quick correct reference fixed it.. may not work for you but give it a try.... I think it's the prob but I'm not sure.. I'd like to hear if anyone else tries it and it works for them...