ok it's the hard way i'm afraid... a few points to start:
1. You can re-enable Sophos - we use it and it's the best product on the market and works well with PT & postgres.
2. You've obviously had postgres and PT3 working? Is there something (an app?) new on your PC recently? - as i said before, this error is symptomatic of another process holding a lock on a file or registry key that postgres needs to get going.
3. Visit
http://www.sysinternals.com and download procmon - install.
4. Start procmon, then start postgres and wait for the error - procmon produces a huge log of processes, threads and handles that are running... with this we hope to isolate the processes holding the lock.
5. You can look at this yourself for a suspect process, or save the log to a file and email it to me - PM me for the email address.
6. We tried with the pg_dumpall to back off your databases, but i forgot it needs the postmaster service to be running to do this.
7. I still believe we have a good chance of doing this and saving your databases.
Susan