![]() |
|
|
|
#1
|
|||
|
|||
|
The latest patch should have fixed the problems you mentioned.
|
|
#2
|
|||
|
|||
|
I have been trying out idleminer for the past week with Windows XP and it has run flawlessly until the last update(1.33). Now whenever it attempts to automatically open another table it pops up a windows error message saying it needs to close. Seems to work fine in manual mode.
Anyways I cleared the log and ran it again so you could take a look: Closed named pipe SERVICECOM: Service is stopped Calling ValidateVersion with /com/com.php?action=validate_version&version=1.33 CLIENT: Version 1.33 validated SERVER: Created named pipe SERVER: Created named pipe for relay SERVICECOM: Detected Windows XP SERVICECOM: Attempting to install service with path C:\Program Files\IdleMiner\IdleMiner\IdleMinerService.exe SERVICECOM: Installed service successfully SERVICECOM: Service is running SERVICECOM: Sleeping and then retrying pipe connection in 200 microseconds SERVICECOM: Connected to named pipe 210 Calling ValidateVersion with /com/com.php?action=validate_version&version=1.33 SERVICECOM: Recieved ok response from service SERVER: Spawned IdleMiner CLIENT: Version 1.33 validated CLIENT: Constructing CLobbyManager 8f49b8 CLIENT: IdleMiner is running in unlocked mode CLIENT: Number tables: 12 CLIENT: Connected to named pipe 74c CLIENT: C:\Program Files\IdleMiner\IdleMiner CLIENT: Manager 46c8b8 CLIENT: Entered CLobbyManager main thread loop (8f49b8)... CLIENT: In main thread got pipe handle 74c CLIENT: Constructing CLobby d50048 CLIENT: Looking for Party Lobby... CLIENT: Found party lobby at 3502a8 Looking for login dialog... WARNING: Could not find login dialog Allocated TVITEM inside lobby Allocated buffer inside lobby Allocated LVITEM inside lobby CRYPT: File has wrong bit depth SERVER: Got client connection via error SERVER: Lost client connection |
|
#3
|
|||
|
|||
|
Try 1.34 does it work?
|
|
#4
|
|||
|
|||
|
Does 1.34 work better for you?
|
|
#5
|
|||
|
|||
|
[ QUOTE ]
Does 1.34 work better for you? [/ QUOTE ] I upgraded to 1.34 and it still shoots out the same error as the other guy described. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|