rrk@byuvax.bitnet (04/25/88)
I have a DSAB and callable editor added to the OAET.MAR file to be used
as the default editor in ALLIN1. But I am having trouble sending mail between
network nodes. The problem is related to the NBS identifier number I assigned
to the text format (non-ascii and non-DEC) associated with the DSAB. Symptoms
are as follows:
I assign a value also assigned to another type in the file, and ALLIN1 crashes
and burns trying to read a received message.
I assign a value out of the range of types assigned by DEC, and the allin1
mail fetcher hangs trying to bring the message into allin1.
I assign a value in the range of types assigned by DEC but currently not
in use on the nodes, and allin1 correctly sends and receives the message.
But I can't find a value in the range that works that isn't being used by
some nodes.
DEC says there is a bug in Allin1 2.1 and 2.2 which causes the last entries
in the tables in OAET to have problems, so we tried putting dummy entries
after it, but that didn't work. My question is, why does DEC bother to
use NBS codes, if they crash and burn on anything but their own codes?
Am I doing something wrong? Any help would be appreciated. Thanks.
AMMON::RAYhenrik@blblbl.UUCP (Larry DeLuca) (05/07/88)
If you call DEC and order the Foreign DSAB you should be able to mail things without problems. Be careful, though, as it does replace OAET.BLI and OAGBL.BLI, so you'll want to DIFF your customized versions first and not use the automatic install. Other than that, the Foreign DSAB provides a means of mailing non-ASCII data as attachments to mail messages. It is supposed to be coming standard with ALL-IN-1 V2.3, but I'll believe it when I see it. larry...
rrk@byuvax.bitnet (05/09/88)
I have my own DSAB that works much better for this application than the
foreign DSAB. As a matter of fact the only problem I am having is the NBS
identifier. I can even use the same NBS identifier that the foreign DSAB
uses on nodes that don't have the foreign DSAB. The problem is that we
have the foreign DSAB and ALLIN1 gets confused when two DSABs are assigned
to the same number. There are also open slots that I have been able to
successfully use which are left open for products not shipped as
a standard part of ALLIN1 such as DECTEXT (an old DEC WordProcessor) and
DECPAGE (DEC's desk top publishing), unfortunately some sites have these
products, so the mail fails to correctly type the messages on these systems.
The NBS number must be the same everywhere. If I use a number
out of the range of those used by DEC, ALLIN1's fetcher fails.
If I use a number within the range used by DEC, it fails on sites with the
products for whom the slots were left open. We cannot live without our
own DSAB. It implements a text type and editor as known text format and
editing styles.
AMMON::RAY