Path: utzoo!attcan!uunet!super!udel!rochester!kodak!ektools!barrett
From: barrett@ektools.UUCP (Chris Barrett)
Newsgroups: comp.sys.amiga
Subject: Re: vt100 v2.9
Message-ID: <1642@ektools.UUCP>
Date: 16 Dec 88 15:01:02 GMT
References: <8812150227.AA09671@postgres.Berkeley.EDU> <14049@oberon.USC.EDU> <3102@sugar.uu.net>
Reply-To: barrett@ektools.UUCP (Chris Barrett)
Organization: Eastman Kodak, Dept. 47, Rochester NY
Lines: 63

In article <3102@sugar.uu.net> peter@sugar.uu.net (Peter da Silva) writes:
>
>No it's NOT. "serial.device" doesn't support more than one UNIT. Another
>manufacturer will have to call their driver "rs232.device" or "myserial.device"
>or something like that.
>
>Anything they do to make "serial.device" accept multiple unit numbers (map
>their memory in to some magic place, for example, or patch serial.device
>to their code) is going to be (as I mentioned) a horrible kludge.
>-- 

Why can't the serial device that gets opened be part of vt100.init or 
what ever terminal program .init file for example:

In vt100.init:

SERIAL_DEVICE		serial.device		# Amiga serial port

or

SERIAL_DEVICE		rs2321.device		# external serial port 1

in vt100 source file:

	OpenDevice (SERIAL_DEVICE, ....);

This way the user can customise the program relatively easily.  If he wants
to be able to switch ports, or run multiple vt100 sessions, the create a script
file that sets the user to a directory that contains a vt100.init for the port
that they specify for example:

Directory structure:

s:	
	vt100.init	vt100.1	<dir>	vt100.2 <dir>

vt100.1:

	vt100.init	

vt100.2:

	vt100.init


Script file: vt100.1

cd s:vt100.1
run vt100

Script file: vt100.2

cd s:vt100.2
run vt100

In the vt100.init file in the vt100.1 directory opens the external serial port
1, in the vt100.2 directory, it opens external serial port 2, a regular vt100
invocation will use the vt100.init in the s: directory.  Sound easy?

Chris

rochester!kodak!ektools!barrett
barrett@ektools