Hmmm ... can you post your exception! Thx!

Alternatively you can
- delete your philosopherstone data directory (AFTER backing up wallet.dat)
- start the 1.2.0.0 client ... it will immediately stop again with the usual message ...
- create a new philosopherstone.conf file (don't for get the nodes!)
- delete the dat files (except the empty wallet.dat file) and the files in the database directory (NOT the directory itself)
- copy in the files from the zip file
- start philosopherstoned again ... let it catch up with the chain
- stop philosopherstoned
- delete the empty wallet.dat
- copy in your wallet.dat
- start philosopherstoned
YOU SHOULD BE FINE!

    one4many

yeah, thats to much trouble. i want my money back Moray

Hmmm .... It is actually none of my business and I couldn't care less about your LTC's ...
BUT ... If he sent you the coins using the correct chain, it is your responsibility to maintain an up-to-date client and not his. He did nothing wrong.
On the other hand, if he is/was on the wrong chain ... then he should send the LTC's back to you.

Just my 0.000005 (worthless) PHS's 

I have a windows version,  one4many,.. as I posted above, are we on the same chain?

And if so, which files do these guys need

What block your client think its at?

-tb-

Hmmm... I'm all synced with most things confirmed, but: "Current number of blocks: 6290"

Im currently stuck here as well, with one4many's node list... 1.2

will wait and c

It seems that too many clients have not yet updated to version 1.2 ... they propagate the "old chain" which seems to have stopped at 6290.  
May be the OP/DEV could bring out another software update which ignores those guys in the network, then at least it would be a proper split everyone would notice ... Just speculating here, not sure if this is possible at all.

So there are three chains??

Mine synced and block at 6290.  Some reporting syncing with block in the 8000.  WTF!

Going to sync one more time with only the config file.


-tb-

I believe I am synced now. Using ONLY the NEW nodes posted:

addnode=24.6.21.198
addnode=46.150.89.173
addnode=64.120.17.149
addnode=70.29.193.48
addnode=125.79.142.201

I waited for it to "sync" (at like 6290), then restarted with the -rescan option, and it fully synced. I don't think it would without the -rescan.