Date   : Mon, 14 Jan 1991 20:43:59 GMT
From   : agate!bionet!uwm.edu!spool2.mu.edu!samsung!cs.utexas.edu!ut-emx!austex!roadhog@ucbvax.Berkeley.EDU (Lindsay Haisley)
Subject: Using BYE as a relocatable RSX

I recently upgraded by BBS from Z33 to Z34 with NZCOM.  I read with 
interest Chris McEwen's article in TCJ #42 on using BYE with NZCOM, however
I found the job to be not as formidable as advirtised.  NZCOM is easy to
configure and BYE is a bear, but once tamed and properly configured, it
coexists with NZCOM with no apparent problems.  I did not encounter any 
of the bugs which Chris reported.  I suspect that his maxdrive and maxuser
quirk was an artifact of QBBS.  HBBS, which is written in assembler had the
same problem - maxdrive was set one drive lower than it should have been.
The bug was easily killed.  
 
I would like to know if anyone has tried rewriting BYE to run as a
relocatable RSX under Z34.  Z34, NZCOM and JetLDR allow dynamic reloction
of files by two different mechanisms.  A "type 4" COM file contains a PRL
style relocation bitmap and an elegant relocation header (thanks, Bridger!)
which places the working image of the file in high memory just below the
CCP.  JetLDR has the capability as well of placing an RSX at the memory
location of your choice using a CFG file interface.  The RSX is in a .REL
format and JetLDR is capable of handling all the hooks via multiple common
declarations in the RXS relocatable module.
 
I'm probably going to jump into this one and try it myself at some point,
however if anyone has done this before I'd like to take advantage of 
his or her (hopefully successful) experience.


"Everything works if you let it!"
 ---  Travis J. Redfish
 +++++++++++++++++++++++++++
uucp: cs.utexas.edu!ut-emx!austex!roadhog
 BBS: (512) 259-1261 (Z-Node 77 - aka - Kaypro Club of Austin)