Have you tried running fpdb on a separate drive (thumb/flash drives or external hdd)? Is windows managing the virtual memory or you? Check bios for any anomalies, try resetting to factory setting. Have you tried running the exe version of fpdb?

I am still using the fpdb-0.20.904anyCPU version on vista homep with minimal issues.

Another possible work around might be to start fpdb from the command line, with this option:
that is a lower case ell, the letter before m. Using that option should cause only critical errors to be logged. I don't understand what's going on here--I'm just suggesting things that might keep you playing.

One thing might be to roll back to the previous version that didn't do that.

Can i use it on PS and FTP?

Not sure of your definition of managing memory. I haven't done anything, so I assume Vista is managing the memory. I have 2gigs real memory, and running a flash drive with another Kingston 2gigs that is totally dedicated or allocated to "ReadyBoost".

Wait a minute... I am running a program "SmartRam" by Advanced System care. It manages the real memory and frees up memory once I close a program... but.... it doesn't "clean" the memory unless the cpu is either idle or (my setting) using less than 5%, and that isn't until it is like that for 5 mins... I wouldn't think that should have an effect, but I mention it just in case...

I am still running (basically) the factory default in bios. The only thing I have changed from the factory settings is in the "power" where I've set up the "wakeup" to start the computer at 5am each morning.

I have not recently tried the "exe" version.. but I did have problems two other versions when I tried running it. Besides, I prefer the source because I do mod some settings, like to get rid of "%" in the stats, have only the green line in the graph, and a few other minor preferences. Can't do that with exe version...

If I try running it (fpdb) on my external drive, do I have to move the appdata info, or just leave that where it defaults to now. Should I just run the "backup copy" I have on my external drive and see how that works?

Dog

Yes!

And it is much appreciated. I'm going to try running it, as suggested above, on the external drive. If I still have the problems, I'll add the "-l" (that's my verdona lower case L" with the "critical" after it. Will report on the results of both... if necessary... where's that damn Love Potion #9 when you need it...

Dog


p.s. Take it easy on me guys, I'm just an old man whose only computer education with what I self-taught over the last 30 years. I'm still proud of just creating and using simple batch files to update mods after a PS update.

First, when I changed the command line to include "-l critical" the program would not open.

I fixed the desktop icon to open the backup copy on my G: external drive. While it is far from proof, I played one hour and it didn't lockup ... yet. Time for dinner, will play some tonight and further test. I need at least a couple of days, with at least two hours play a session. If I don't lockup, then we're good to go.

Thanks to all of you, and MO7 who made the winning suggestion... so far

Dog

hmm. looks like those errors are occuring in the logging module, dog .. not sure what that means.

Are you out of space on any of your drives?

(Fingers crossed) Over a two-hour session tonight with no lockup, using my backup copy on the external drive. I left the appdata log files on the C drive. Also left Python and all other files on the C drive, just running fpdb.pyw from the external... Makes no sense why running it from there makes a difference, but who cares.

If it ain't broke....

Dog

Nope. Both are 250gigs (no laughing, it's 5 years old) Using 90gig on the C drive and about 100 on the backup, plenty of room for all my wife's digital pictures.. and as I stated above, they are defragged regularly and I run Eusing Registry cleaner once a week so there are no dangling or bad shortcuts or file names. Been using it for years. I've got clean, virus free, defragged, registry clean etc etc drives

Dog

"There is no joy in Mudville. Might Casey has struck out..."

Three hours into a session today the drive lockup in an apparent loop. I closed the fpdb down. Restarted immediately and it seemed fine. The irony was that one hand failed and caused the apparent error. When I restarted, it imported it just fine... go figure. Thanks for the efforts guys.

M07.. you have to return your winning prize, actually I never sent it out.

Dog

Hi Dog,

This error 9 in logging could well be due to the logging buffer space being overloaded.

If so, the underlying issue is because windows has a small and fixed size for the stdout and stderr. Consequently, the python runtime on windows inherits the same restriction. Any overload of these buffers can give a code 9 error, AFAIK.

There was an FPDB change to reduce the amount of logging output, (eliminating the message when a hand was written successfully), don't know off hand if that was included in -906 or not. A later version of fpdb may or may not help in your case.

I just need to be patient, and I agree with you. I'll wait for the next major release and see if that issue is resolved.

My other issue is the one that shouldn't, but does, drive me crazy. It make no sense that the hud display (hero set at one day to track my day) changes time different than the stats and graphs. I've heard all the tech description of how it defaults to GMT/UTC. If that is the case, there should be a simple way for me to adjust it "-8" for my PT (Pacific Time) so that everything is in sync..

Dog

That would explain it. Ekidikeo found a (possibly longstanding) issue with all of the right click entries in the main menu.

What is the size of that buffer gimick?

does this work for mac?

thanks awesome btw

HH importing, the tracker, graphing works for mac. The HUD does not work on the mac. The last person to try getting the HUD going on the mac could not figure out how to locate the table client windows.

http://****************/apps/mediawik...tall_in_MacOSX

One future feature that would be nice, would be a "last activity" column in the stats report. For me, I keep strict notes on Stars. Often I know players drop out of sight. (go broke or move to another site).

It would make it easier to clean old defunct players if we knew they hadn't played for a long period of time.

Dog

Dunno exactly, but the problem is documented in py2exe's boot_common.py.

Note that this is NOT a py2exe problem, it is just that someone on that project took the time to document it.

Pure speculation on my part, but it might be that this behaviour is a by-product of running as a pyw, since there is no console to handle the outputs.

Anyway, here is an extract from boot_common.py (there is a fuller explaination in the source file):

I installed ubuntu 10.10 RC next to 10.04 and HUD is not working there it seems.

oh lol i hadn't set up ftp to save hh-s.

all works.

i have coded some improvements with the graphing

1) chose if you want showdown or non showdown graphed
2) graph in BB or $

here is a screen shot.

are you interested in putting this in?

Nice - very interested. I'll PM my email address.

Sorrow

would really like an option to only display X amount of characters from player name.

in the HUD, you mean? that is pretty doable.

yup, would be great to shorten to them to like 4 characters