|
|
#132
08-18-2006, 04:31 PM
|
|||
|
|||
Re: New Software- IdleMiner
Maybe can we choose to datamine between monster/regular or with/without dp protection?
----- http://mupoker.blogspot.com 
|
|
#133
08-18-2006, 04:34 PM
|
|||
|
|||
|
Re: Another Big Update
Newest update opens PT and importer but doesnt hit the start button. It also opens an importer that goes into my main database not my mined database. Not a big deal.
Is there any way to have an option to open the generic auto import(lightning bolt) window rather than the party window in PT? Are you guys really using the party importer to get your observed hands? This PT feature doesnt make or break the software for me. With or with out it this software is sweet.
|
|
#134
08-18-2006, 06:11 PM
|
|||
|
|||
|
Re: Another Big Update
Not sure what's happening, but I came home today and the software had stopped. Party was sitting open with the Login screen showing, but no tables open.
Here's a bit of my log file. CLIENT: Making another attempt to open table Table 108124 CLIENT: Popping partypoker up... WARNING: Could not open table Table 108124 in 30 seconds WARNING: Lobby window is no longer valid CLIENT: Destroying lobby object and creating new one. CLIENT: Constructing CLobby cc3100 Looking for Party Lobby... CLIENT: Got party path of C:\PartyGaming\PartyGaming.exe SERVICECOM: Service is running SERVICECOM: Connected to named pipe 422c SERVICECOM: Recieved ok response from service Lobby spawned Looking for Party Lobby... Found party lobby at 150034a Looking for login dialog... Looking for login dialog... FATAL: Could not find login dialog in 30 seconds and this is a required login SERVER: Lost client connection Closed named pipe SERVICECOM: Service is stopped
|
|
#135
08-18-2006, 06:56 PM
|
|||
|
|||
|
Re: Another Big Update
When I hit Start, IdleMiner doesn't do anything for a bit and then closes every time.
Here's the log: Calling ValidateVersion with /com/com.php?action=validate_version&version=1.21 CLIENT: Version 1.21 validated SERVER: Created named pipe SERVER: Created named pipe for relay SERVICECOM: Service is running SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Could not connect to named pipe in 5 seconds SERVER: Failed to spawn IdleMiner with error: 183
|
|
#136
08-18-2006, 06:58 PM
|
|||
|
|||
|
SYSTEM CRASHING
My system froze last night after running idleminer and pt - didn't discover it until this morning.
I restarted and started up the programs again this evening . The first pt download after 20 minutes worked fine. I came back to the computer an hour later to find it had restarted on me. The error report from Microsoft states this was an "Error caused by a device driver" - a "Windows stop error". Anyone else run into this? Thanks.
|
|
#137
08-18-2006, 07:09 PM
|
|||
|
|||
|
Re: SYSTEM CRASHING
I can't get idleminer to open up any tables at all for me. It just sits there doing nothing. Here's my log:
Calling ValidateVersion with /com/com.php?action=validate_version&version=1.21 CLIENT: Version 1.21 validated SERVER: Created named pipe SERVER: Created named pipe for relay SERVICECOM: Service is running SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Connected to named pipe 23c Calling ValidateVersion with /com/com.php?action=validate_version&version=1.21 SERVICECOM: Recieved ok response from service SERVER: Spawned IdleMiner CLIENT: Version 1.21 validated CLIENT: Constructing CLobbyManager 9e3868 CLIENT: Number tables: 8 CLIENT: Connected to named pipe 74c CLIENT: C:\Program Files\IdleMiner\IdleMiner CLIENT: Manager 4594f0 CLIENT: Entered CLobbyManager main thread loop (9e3868)... CLIENT: In main thread got pipe handle 74c CLIENT: Constructing CLobby e30048 Looking for Party Lobby... CLIENT: Got party path of C:\Program Files\PartyGaming\PartyGaming.exe SERVICECOM: Service is running SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Connected to named pipe 610 SERVICECOM: Recieved ok response from service Lobby spawned Looking for Party Lobby... Looking for Party Lobby... SERVER: Got client connection via error Looking for Party Lobby... Looking for Party Lobby... Looking for Party Lobby... Looking for Party Lobby... Looking for Party Lobby... Looking for Party Lobby... Looking for Party Lobby... Found party lobby at 9078e Looking for login dialog... Clicked login button, sleeping 1/4 second... Allocated TVITEM inside lobby Allocated buffer inside lobby Allocated LVITEM inside lobby CLIENT: Attempting to open 0 more tables for limit descriptor 0:0:1:6.00:4 CLIENT: Attempting to open 0 more tables for limit descriptor 0:0:1:4.00:2 CLIENT: Attempting to open 0 more tables for limit descriptor 0:0:1:50.00:2 CLIENT: Attempting to open 0 more tables for limit descriptor 0:0:1:10.00:2 CLIENT: Attempting to open 0 more tables for limit descriptor 0:0:1:1.00:2 CLIENT: Attempting to open 0 more tables for limit descriptor 0:0:1:0.50:2 CLIENT: Attempting to open 0 more tables for limit descriptor 0:0:0:2.00:2 CLIENT: Attempting to open 0 more tables for limit descriptor 0:0:0:60.00:2 CLIENT: Got exit message SERVER: Lost client connection
|
|
#138
08-18-2006, 08:18 PM
|
|||
|
|||
|
Re: SYSTEM CRASHING
After about 2 hrs of running the app it starts to constantly open and close just one table. For some reason 2 to 4 seconds after the table is open the program shuts it down. Then 5 seconds later the same table gets opened again. This goes on until I restart the program.
This has happened to me 4 times today but did not happen at all before the latest upgrade.
|
|
#139
08-18-2006, 08:28 PM
|
|||
|
|||
|
Re: SYSTEM CRASHING
[ QUOTE ]
After about 2 hrs of running the app it starts to constantly open and close just one table. For some reason 2 to 4 seconds after the table is open the program shuts it down. Then 5 seconds later the same table gets opened again. This goes on until I restart the program. This has happened to me 4 times today but did not happen at all before the latest upgrade. [/ QUOTE ] I have the same problem after the upgrade, except it was doing it with 4 of the 12 tables i had open. 8 tables would stay open, but the other 4 kept opening and closing every 5 seconds.
|
 |
|
|
Linear Mode
