PokerTracker

Both after upgrading to 3.12 beta and subsequently to 3.13.0, I found that files weren't moved to the processed files directory after being processed. I was able to solve the problem by reselecting the required directory. Windows 7 OS.

Was the Processed Folder shown incorrectly after the update? The update really shouldn't change that..

No, the processed folder was shown correctly. I had to change it, then reselect it, before processed files were moved correctly.

That's very odd but I'm glad to hear you got it fixed. If anybody else reports similar behavior I'll let them know of your solution.

Unfortunately it doesn't seem to be fixed.Once again, processed files are not being transferred (to a NAS drive, mapped to Z: ). This means that PT reports a lot of duplicate hands whenever I start auto-processing.

Any ideas?

Can you confirm that it works to a local folder?
Do you need to provide credentials to connect to your network drive? Does it make any difference if you have already connected to it in Windows Explorer for example?

No credentials needed. In all cases, already connected to Z: with windows explorer. Haven't yet tried with a local drive. Today, having upgraded to 3.13.1 (but after deselecting/reselecting correct folder again) seems to be working OK. Will keep monitoring and will try with a local drive if problem recurs.

NB I used the NAS drive originally because my local drive was getting too full. However, I have since upgraded my main PC, so could store processed HHs locally, for a trial (though I prefer to keep 'em on the NAS drive longer term, for storage management reasons).

Thanks for the update.
I understand that - I did not intend to suggest that you shouldn't use the NAS, I agree that is a useful thing to be able to do, but it would be a different issue if it wasn't working to a local drive either and that would affect how we proceed. If the problem re-occurs please let us know.

Thanks WR.

Latest status: after restarting my computer, processed files aren't being transferred again. I have now switched to a local drive and will see whether that improves matters (won't know until I next restart, having switched destination directories, it's OK again for now).

I was previously using PT v3.12 under Windows XP and didn't observe this problem. It has occurred since I moved to a new computer running Windows 7 and upgraded to PT 3.13 (am now running PT 3.13.2).

Regards,

Mark

Sounds like a plan - please keep us posted.