Conference pamsrc::decmessageq

2867.0. "Settimer error?" by SIOG::BATEMAN (We are all DECservers) Thu May 08 1997 05:01

Using the V3.2 SSB kit of the Windows Client Library (32-bit) and
the OCX custom control with VB 4 we're getting the following error
in the log file :-

SetPollingTimer: SetTimer() error: (too many clocks/timers)

What does this mean? Would this error occur if the PollingRate was
reset to 0?

Attached in the section from the log file.

Thanks,
Alan.

Wed May 07 17:25:02  | SetPollingTimer
Wed May 07 17:25:02  | AttachQ
Wed May 07 17:25:02  | InitMsgAreas: firing event InitMsgArea for DmqMsgCtrl 0x7b32f8
Wed May 07 17:25:02  | InitMsgAreas: firing event InitMsgArea for DmqMsgCtrl 0x7b36e8
Wed May 07 17:25:02  | DmqMsgPointer
Wed May 07 17:25:02  |   any: 0x4501e0
Wed May 07 17:25:02  | AttachQ: attach to temporary queue
Wed May 07 17:25:03  | AttachQ: pams_attach_q() successful
Wed May 07 17:25:03  |   queue: [4.557]
Wed May 07 17:25:03  |   DmqQueueCtrl: 0x7b2f00
Wed May 07 17:25:03  | SetPollingTimer
Wed May 07 17:25:03  | PutMsg
Wed May 07 17:25:03  | PutMsg: using MsgAreaString, str 0x7b3b58, len 10
Wed May 07 17:25:03  | >>>
Wed May 07 17:25:03  | RDECpc333
Wed May 07 17:25:03  | <<<
Wed May 07 17:25:03  | PutMsg: calling pams_put_msg()
Wed May 07 17:25:03  |   class: 2000
Wed May 07 17:25:03  |   type: 1
Wed May 07 17:25:03  |   target: [0.101]
Wed May 07 17:25:03  | PutMsg: pams_put_msg() successful
Wed May 07 17:25:03  | SetPollingTimer
Wed May 07 17:25:03  | SetPollingTimer: SetTimer() error: (too many clocks/timers)
Wed May 07 17:25:03  | DmqMsgPointer
Wed May 07 17:25:03  |   any: 0x4501e0
Wed May 07 17:27:19  | SetPollingTimer
Wed May 07 17:27:19  | AttachQ
Wed May 07 17:27:19  | InitMsgAreas: firing event InitMsgArea for DmqMsgCtrl 0x7b32f8
Wed May 07 17:27:19  | InitMsgAreas: firing event InitMsgArea for DmqMsgCtrl 0x7b36e8
Wed May 07 17:27:20  | DmqMsgPointer
Wed May 07 17:27:20  |   any: 0x4501e0
Wed May 07 17:27:20  | AttachQ: attach to temporary queue
Wed May 07 17:27:20  | AttachQ: pams_attach_q() successful
Wed May 07 17:27:20  |   queue: [4.558]
Wed May 07 17:27:20  |   DmqQueueCtrl: 0x7b2f00
Wed May 07 17:27:20  | SetPollingTimer
Wed May 07 17:27:20  | PutMsg
Wed May 07 17:27:20  | PutMsg: using MsgAreaString, str 0x7b3b58, len 10
Wed May 07 17:27:20  | >>>
Wed May 07 17:27:20  | RDECpc333
Wed May 07 17:27:20  | <<<
Wed May 07 17:27:20  | PutMsg: calling pams_put_msg()
Wed May 07 17:27:20  |   class: 2000
Wed May 07 17:27:20  |   type: 1
Wed May 07 17:27:20  |   target: [0.101]
Wed May 07 17:27:20  | PutMsg: pams_put_msg() successful
Wed May 07 17:27:20  | SetPollingTimer
Wed May 07 17:27:20  | SetPollingTimer: SetTimer() error: (too many clocks/timers)
Wed May 07 17:27:20  | DmqMsgPointer

Apparently the SetTimer function is failing when it tries to start the
polling timer. Setting the polling rate to 0 should make this go away because
the timer won't be used.

The question is why is it failing? Are you running this on Windows NT or
Windows 95?

    Pat

    
    W95. SetTimer should only fail if an invalid timer value is specified
    or there are no more timers available. There used to be a limit of 8 on
    WFW311 I think but I don't know in WIN32.

The Win32 environment should support an unlimited number of timers. Win16 only
provided 32 timers.

I'll take a look at the code to see if I can tell why it fails.

    Pat

    Someone installed VB4 on the PC with the problem and the problem
    disappeared - not sure why yet.