Not sure if R'Osity is the betst place for a query like this, but if you know a better one, please do mention it. :) Anyway, I closed Poser through the task manager while it was saving a render and now, when it starts up, I get an XML error window with the message "Parse Error: Not well-formed at line 14" and the loading is abruptly halted. Any ideas?

Sounds like you have to do a reinstall...

Thought as much. Will I have to reinstall everything else back into Runtime?

I just grabbed this off the Curious Labs site: Poser 5 is showing XML parse errors... XML parse errors can occur if you have a library (either created in Poser 5, or an old Poser 4 library) that has one of the following characters in the name: quote (") apostrophe (') ampersand (&) less than (<) greater than (>) (These may not cause a problem, but may be problem characters) back slash () slash (/) Hope this helps Tony

look for an *.xml file somewhere under the poser dir. with a current time stamp and rename it *.xml.bak (this will delete the file). When the file is not found Poser should just recreate the file (or restore the file from a backup, you do do backups?).

Be sure you've installed the latest Service Release, and you won't get that problem.

Be sure you've installed the latest Service Release, and you won't get that problem.

Okay, I'm gonna bring this thread back to life. :(

I have WinXP, P4, 1G of RAM, and haven't loaded any new items. I have SR3 for both the application and the figures (have for a month).

Today I went to open Poser5 (haven't opened for a couple of days) and boom I get the box:

XML Error - Parse error - not well-formed at line 8.

I searched the old messages and most just say, with the updated service release that this goes away, or it has something to do with invalid characters. Well, service release is correct, and I have no idea about characters, since I haven't loaded anything new.

Anyone else having this problem with SR3? Anyone have suggestions? If it is to reinstall, will I have to reinstall all the stuff that I've added?

Yes, I'm new, can ya tell? ;)

Here's a quote from the Curious Labs site: "Poser 5 is showing XML parse errors... XML parse errors can occur if you have a library (either created in Poser 5, or an old Poser 4 library) that has one of the following characters in the name: quote (") apostrophe (') ampersand (&) less than (<) greater than (>) (These may not cause a problem, but may be problem characters) back slash () slash (/) This issue is addressed in our Poser 5 SR1 updater. Download our Poser 5 SR1 updater from SR1 UPDATER"

Thanks :) I had read that over at CL, but since I already have SR3, have not loaded anything new to program, that doesn't quit fit what is happening.

And I still don't know HOW to check for thost characters. I'll keep trying, posted this to a separate thread incase some don't keep going back.

Appreciate the answer though. :)

Perhaps you didn't do something right when you installed SR3? This was a very temporary problem which was fixed with SR1. The updaters only work on the default installation. If you've moved any of the default libraries, the fix won't work. That's why I installed all my Poser 5 stuff into a separate Runtime folder, and kept the original Poser stuff in the default location. You can easily check for those characters. Just use a file manager, such as Windows Explorer and see if those characters are in any of the library names.

Hi Bobbie :)

Where....would I find the library names though? No, I haven't moved anything to anywhere.

I am very new to Poser, there is no other Poser program on my system. Whatever/wherever that Poser5 installed itself is where it did it from the beginning. When I went to do SR3, it said to put it in the same directory that the original Poser5 was in, so that is what I did.

I'm more than willing to to look for these character things, but don't know where.

Thanks :)

Bobbie,

Thank you for your help. :)

I was able to fix it finally! I think it was re-doing the SR3. Not sure, but whatever it was, it worked!

I do appreciate you trying to help me though!!

Great!!! Glad it's fixed.