POser just stops loading and flashes this "parse error on line 26" . Is there a way to solve without reinstalling?

Install the latest service relase, if you haven't done it yet.

This is (probably) a problem occurring in one of the .xml files that Poser reads on start-up. When you quit Poser, it writes several .xml files (in the UI directory, IIRC), which control it's next start-up, depending on what state Poser is in when you quit. The last time it happened to me was when I downloaded and installed a prop from the net. The installation created a new entry in one of the libraries, with a "$" sign (I think) at the start of the entry name. All was fine until I loaded Poser, tried the new prop (or what ever it was) then exited Poser with the library still selected. Poser wrote out my file configuration to (one of) the start-up .xml files. Unfortunately, "$" is a .xml "reserved" symbol. So when Poser tried to parse that file: "parse error". (BTW - the message that is flashed up should also contain the name of the file that the parse error occurred in.) My solution was to edit the .xml file and completely remove the offending line (Poser then reverts to default for that line). I also renamed the offending folder to remove the "$" signs. After that I had no more problems. If you don't know which .xml file is the problem, it might be worth using explorer to do a date-search on /runtime for any *.xml files modified within the last 1 or 2 days, which should narrow things down. Hope this helps, Cheers, Diolma

Don't go through all that trouble. Just install the latest Service Release, and all is well.

Thanks, guys! Since my edition of POser 5 has always been running smooth, I was afraid to change something in stalling the SR... I edited the xml file, and all is fine now!!! Thanks again!!!

You really should reconsider your decision concerning the Service Releases. It is obvious your Poser 5 is not up-to-date. That Parse error was fixed in the first Service Pack. There have been many fixes done since then, including disabling the copy-protection which apparently caused some problems.