| John, I don't have copies of either the V2.0 or V2.0A SPD for DEComni
API - Claudio Muggia has confirmed to me that they were produced in the
States.
However, I do have the following (if they can be of any help):
- DEComni API V2.2 SPD for OSF/1 (September 1994)
- DEComni API V2.1A SPD for OpenVMS VAX (July 1995)
- DEComni API V2.2 SPD (January 1995)
- DEComni API V3.0 SPD (July 1996)
Let me know if these are of any use.
Regards,
Dominic Turner
|
| John,
If you can find somebody who has a VMS Consolidated distributions
CD from Oct 92 to 93 then you'll find the SPD there with the omni kits.
I have a CD either here at home of in the office, unfortunately you'll
have to wait until Tuesday for this cos I can't get the CD on-line.
I'm wondering if this has anything to do with an MMS customer
who wanted to pay for DECnet VAX exts or OSAK to have a problem fixed,
there was a note in the DECnet OSI conference about this and I sort of
guessed it maybe an old DEComni problem.
If this has anything to do with DEC/MAP and DECnet extensions, then
stay well away from this. I got burnt at VW on this, and Bob Doyle and
Joe Billmaier never did get around to investigating the problems or
getting anyfixes made in Omni, DECnet or OSAK. Hence we lost this
customer. A few years later Volvo, Bosch, SEL, AEG etc.. found that
they had a number of similar problems in the area, it took me almost
2 years and a lot of IPMTs on all the products involved, i.e. OSAK
OSI and Omni, these fixes are only in DECnet OSI 6.3 ECO's and the
current Omni kits. To go back and fix these would be really
painful and very exspensive. It would be easier to go to the latest
and greatest and upgrade the customer andapplication etc... Of
course if he's using a DTQNA then it's no good, but a token bus
to Ethernet bridge might be a solution providing you can still
find one.
I'll mail you the SPD on Tuesday when I'm back in the office.
Chris
|