Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!aplcen!haven!grebyn!ckp
From: ckp@grebyn.com (Checkpoint Technologies)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Question about multiple serial boards
Message-ID: <14149@grebyn.com>
Date: 17 Jan 90 21:43:30 GMT
References: <7970@nigel.udel.EDU> <14137@grebyn.com> <130261@sun.Eng.Sun.COM> <14142@grebyn.com> <4949@sugar.hackercorp.com>
Reply-To: ckp@grebyn.UUCP (Checkpoint Technologies)
Distribution: na
Organization: Grebyn Timesharing, Vienna, VA, USA
Lines: 18

In article <4949@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes:
>Since you're working on a copy anyway (I hope) zapping it on disk or in RAM
>isn't that different. Exactly what does ZapPort do? Change "serial.device"
>to "checkp.device"? Try to find the unit # and change it?

	The big advantage in using NewPort is that it only makes a
500-some odd byte long loader.  This saves a lot in disk space,
especially with 300K long executables.  This is really important if the
app is on a floppy, but still very nice when using a hard disk.

	What we do is find strings of "serial.device" and change them to
"ckptss.device".  Finding and changing the unit number is not something
that can realistically be done, given the myriad numbers of ways
programs might generate it.

	More and more programs are being released with support for
multiple serial ports, especially communications programs.  I figure
many users won't need these zappers at all.