Last night while I was working with Poser I clicked something near the first drop down menu, not sure what as my mouse slipped. Then Poser shutdown.

When I tried to open Poser after that I kept getting an: XML error at line... not well formed error log is being created, type of message.

This meant that I couldn't open Poser up whatever I tried.

Eventually I found by looking at files created in last 24 hours that the offending file was my Library prefs. I ended up renaming an extra Runtime that I'd created and amending the Library prefs file to reflect this name/path change.

Pheeew it worked out fine in the end.

Does anyone know how I managed to get the error up in the first place, what on earth did I do wrong?

Thanks
Mit

this happens when poser crashes. what I did was make a copy of that xml library file and when I crash I just move it back. Poser will automatically rebuild it after most crashes, but I've noticed that it defaults back to when you first installed and you have to re-enter all the addtl runtime folders you added.

At least its a relatively straightforward process to sort out eh?

yes definitely... once I figured it out.:)

xml is mainly html with a few more rules..;) what that has to do with Poser is beyond me..'not well formed' means that the code isn't set up by XML rules, like missing end tags, etc.

I wish I'd said that.. The Staircase Wit

anahl nathrak uth vas betude doth yel dyenvey..;)

Posers stores its preferences etc. in xml files. When Poser 5 was first released, this problem did happen with some special Characters (like & )in libary path names.

It was fixed in SR 1 ore 2.

Stefan

quinlor, that would explain it. I re-installed poser just last week and hadn't gotten round to the srs.

The SR's will overwrite some of the xml files IF they are the native date/stamp ones. So, don't manually modify your xml's. Also, maybe just rerunning the patch will fix the problem depending on which xml was damaged.