this worked for me...
try using procmon to detect the culprit...
googled & goofed around some more - found a thread somewhere about permissions and
using procmon to diagnose...
used procmon from sysinternals to get the clue... filtered on the postgres PID around the time
of the permissions failure...
log kept saying something to do with a program called spampal & a transparent proxy service layer provider it had...
it was a spam filter program i have had for yonks - spampal - with a transparent proxy service layer provider
uninstall postgres, delete all postgres folders (including the one(s) in Documents and Settings)
net user postgres /delete
uninstall spampal & the proxy
reinstall pokertracker with postgres - - voila!!
susan
