Title: | VAX on VMEbus: KAV30 |
Notice: | Could have been as fast as 68K but its a VAX! |
Moderator: | CSSVMS::KAV30_SUPP |
Created: | Thu Apr 18 1991 |
Last Modified: | Fri Aug 02 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 159 |
Total number of notes: | 645 |
Hello all I have a customer who has a query about KAV$TIMERS, and specifically about ast_addr and ast_param. He claims that under v1.0 KAV30 extension he didn't need to specify either of these and his program worked. However under v1.1 he says he needs to specify both, or his program wont work. So far as I can see the call for KAV$TIMERS hasn't changed at all. ast_addr only needs to be specified when timer functions,specifies KAV$M_LOAD_TMR_CNT.timer functions,specifies KAV$M_LOAD_TMR_CNT. ast_param is optional (I assume when ast_addr has been specified)and is only specified when timer functions,specifies KAV$M_LOAD_TMR_CNT. Is this right? Did anything change from v1.0 to v1.1 with the timer call? Thanks for your help Alec
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
100.1 | GOBANG::LEMMER | Mon Aug 16 1993 15:51 | 13 | ||
Hi, we are not aware of any change in KAV$TIMERS between 1.0 and 1.1... Nevertheless, the current (and supported) version is ELN4.4 with the integrated KAV30 toolkit extensions. There were changes to the KAV$TIMERS routine when V1.1 was 'merged' into ELN4.4 (see the documentation for details). The current documentation describes the ast_addr as *required* parameter, the ast_param may be omitted. Thomas |