Today, for the 1st time using P6, I got a "Parse error" message box.

Situation:
I created a dynamic cloth simulation. I selected and rendered the "best" frame.
I didn't really like the look of it, so for the 1st time ever, I changed the background colour - to black.

Saved the PZ3 file. Closed Poser. (No I didn't at that time save the render).

Later, I re-opened the file. Didn't like the pure black BG colour, so decided to change it. Hit the "BG colour" button and that's when the error popped up. I don't remember it in detail, but it was something to the effect of:

"Parse error
 Junk after line 2"

(I can't remember if it specifically mentioned xml in the message - I don't think so, but it may have).

Nothing crashed, Poser continued to work (after I'd dismissed the error dialogue), and I rendered with my new BG colour.

Curious, I checked the prefs directory to see what had changed. One that immediately caught my eye was the Poser UI prefs.  (The others that had changed were irrelevant - I'd not added/changed/removed anything in the libraries etc.)

So I looked at the UI prefs. I couldn't see anything wrong with it - but maybe someone here can:-)

The 1st few lines are:

           

Anything wrong with that?
Why did I get the error?

I'm not worried, just curious...

Cheers,
Diolma

I got that error too, after installing V4 and a bunch of V4 items. Happened when I browsed one of the new library folders - can't remember which folder. 
After closing and restarting P6 the error went away.

The XML looks clean to me.

Why the error? Beats me.

The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter

My gallery   My freestuff

Attached Link: http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2675576

The problem is with LibraryPrefs.xml

What's causing it hasn't been determined yet, but it must be something recent, as a several people started getting the same thing in tha last few days.

But I haven't installed anything lately, haven't updated P6, haven't opened any new libraries....

Poser opens OK (so it shouldn't be the library prefs - that tends to stop Poser before it starts - at least it did in P5, maybe its different in P6). I didn't get the error til I clicked on the "background" colour change. As far as I can recall, I also didn't change anything else and didn't change the preference at all except to errrmmm - ah. maybe.

Just re-opened Poser and now realise that one thing I did do was delete the properties window (I wanted a bigger preview area). So, of course that got saved when I exited P6...

Wonder if that's got anything to do with it?..

Cheers,
Diolma

It happend again today, in totally different circumstances.

I started Poser, Loaded V3, de-IK'd her, zeroised her then started to go to the file menu to export her as a .obj mannequin (for use in Hexagon as a clothes horse). Up popped the error again.

There had been a little "disc-rattle" just before this happened., which normally doesn't occur when I run Poser (at least, not unless I load something..)

Then I checked something.....

Now normally I only connect when I am going on-line (like now). But then I realised that when I got the problem yesterday I was using P6 to create an example in one of the threads here, so I was on-line.

I must have forgotten to disconnect last night, so his morning when I started up Poser I was still on-line. And that's where I think the problem is coming from.
When Poser makes it's connection-check and/or tries to connect to CP, it's getting a bad file in response from somewhere (my guess would be CP)..

Simple answer - don't run Poser if you're on-line...
Cheers,
Diolma

You can still run Poser while you're online...
You'll just have to uncheck "Check for updates" in your general preferences.

Another solution is setting your firewall to stop Poser connection to the internet :-)

Yesterday's the past, tomorrow's the future, but today is a gift. That's why it's called the present.

Quote - When Poser makes it's connection-check and/or tries to connect to CP, it's getting a bad file in response from somewhere (my guess would be CP)..

Simple answer - don't run Poser if you're on-line...

The check for updates (to an EF URL) is what's causing the XML problem.
You can just turn this off is the Preferences dialog.

Many thanks.

Actually I did that yesterday having read the thread in the Poser forum (which was aftere I posted here).

But thanks for your help anyway!

Cheers,
Diolma

(PS - I always - well, usually,  run any software that doesn't actually need the net while I'm offline, and try not to use such software when I'm on-line. It saves problems. But that just my preference, not a recommendation.)