Thanks for the response.
I have copies of the receiver files in several of those places, so I'm starting to think that that isn't the problem. The client is stuck at block 76221, which was mined well before I got devcoin, and I have only ever used it to get an address. I downloaded devcoin-qt from one of the links on devtome and built it with qt creator. This has worked fine for other altcoin clients, so I'm not really sure what I've done wrong.
It picks a random lbock number at which to go get next set of receiver files, I think it would have been round 19 it would have already got before reaching block 76000, then sometime before block 8000 it would try to get round 20. Possibly block 76221 is the random block number at which it decided to do that.
Is the receivers list number 20 in the receiver subdirectory of the data directory?
Extra copies of receiver files lying around elsewhere it likely will not even be seeing, unless by change they happen to be in the directrory that was the program's "current working directory" when it was run. (In which case it should have copied them to the receiver directory of the data directory).
I guess with all the flavours of coins though there is always the weird times when people seem to end up deleting the blockchain and re-getting it from scratch. Hate to blindly try that without knowing the actual problem though.
Is there any clue in the debug.log file that is in the data directrory?
Does it write something to console maybe about files it got being identical or not?
Does it actually have connections? It is not some old version is it?
-MarkM-