| 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 |
KAV software version 1.1 needs to use ELN-V4.3... is there a new
version of this software which runs with ELN-V4.4 ??
A customer has upgrade his system to ELN-V4.4 and now he can't
re-instal his KAV software (v1.1) because of this compatibility
problem.
Thanks for any quick answer.
Jean-Pierre
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 102.1 | KAV software is bundled with VAXELN V4.4 | ZYDECO::BODA | Realtime Products Support | Fri Sep 10 1993 23:07 | 15 |
Hi Jean-Pierre, All of the KAV30 functions have now been integrated with VAXELN v4.4 so there is no KAV kit to install. Check out section 2.2.1 of the VAXELN V4.4 release notes for a discussion on compiling and linking KAV30-based applications. Also there is a new KAV30 Programming Guide that comes with VAXELN V4.4. Hope this helps. Regards, Alan | |||||
| 102.2 | V4.4 now has a "KAV30" target processor | EICMFG::BURKE | Jim Burke, @UFC | Mon Oct 11 1993 11:58 | 9 |
When migrating from V4.3 to V4.4, don't forget to change the
"target processor" parameter in Ebuild. It is no longer "rtVax-300"
but "KAV30".
I was bitten by this and I got strange (unhelpful) error messages
on any KAV$... calls.
Jim
| |||||
| 102.3 | HERR::crosbie | Graham Crosbie @PCS DTN 873-4193 | Mon Oct 11 1993 16:12 | 17 | |
Hi Jim,
> When migrating from V4.3 to V4.4, don't forget to change the
>"target processor" parameter in Ebuild. It is no longer "rtVax-300"
>but "KAV30".
>I was bitten by this and I got strange (unhelpful) error messages
>on any KAV$... calls.
The KAV$ calls are not dispatched in the same manner as regular VAXELN
kernel services, references to the KAV$ routines are resolved at link time, i.e they are fixed to the start address of the appropriate routine in the kernel
module for the KAV$ routines, only the KAV30 kernel (3KVKER.EXE) has this
module linked into it, so if you attempt to call a KAV$ routine when your
system is running the rtVAX 300 kernel you can see some very wierd behaviour.
Don't worry too much about being bitten by this, its happened to me and I
implemented the change... :-)
Graham
| |||||