I have no way of testing it on Win2K. But I know at least one other member uses Win2K and it works there. At least earlier versions did.
I have computers with almost all OS installed (inc. Debian Linux). I installed and ran StokerLog v4.0(RC) on a W2K OS computer, no problem. Might be .net 2.0 or patches.
Here is the updated version 4.0.
Ken, I put in the fix so that it remembers the changed log file without doing anything else. Let me know if it doesn't work for you.
There are also a few other bug fixes. For example, the alarm used to go on/off if the temp oscillated above and below the target. Now the alarm goes on and stays on.
FYI only
I have the new 4.0 RC installed on 3 computer , 2 xp-pro and a w2k. I still cannot change the log file, and I have tried at every stage of operation; first step after opening, before and after F5, before start logging after stop logging, immediate save after change. Note: I will allow me to change the name, but, after I do, I hit the tab to make sure it got it, then press done. If I got back, it has changed it back to StokerLog.txt. I thought maybe there a default value for the file name field and that by going back in, I was changing it, But that is not the case. If I press start logging after changing the name, it still starts logging to StokerLog.txt.
What we should do probably is start gathering the collective wisdom on what recipe would work for each cook. I would then be able to put pre-sets in there for each one.
I agree, what can I do to help? We probably need only a few fields. MeatCut, MeatWeight, CookerTemp, TargetTemp, ShelfTemp, ShelfDuration. (Shelf being the word I use to describe the point at which temps fails to increase at a normal rate)
Thanks again for all your selfless time and devotion to this. This tech support is a nightmare. I know, been there, done that, still doing it. I sometimes feel that every computer in the world has a mind of it's own. Some call it AI, I call AS.