🚀 go-pugleaf

Rainbow EchoMail Digest                     Jan 17, 1990

In this issue:
  Rainbow Comm Programs
  Accessing and clearing MP
  RE: C COMPILER ON RAINBOW
  ALTERNATIVE COMM PKGS FOR
  RE: C COMPILER FOR 'BOW
  PATCHING TURBO C (BAD???)


  Articles posted to either INFO-DEC-MICRO or comp.sys.dec.micro are
currently gatewayed automatically to the Rainbow Echo on Fidonet; thus,
you do not need to take any special action to respond to articles in
these digests.

  Please send reports of problems or suggestions for improvement of this
digest to GTHEALL@PENNDRLS.UPENN.EDU (ARPA Internet).
------------------------------------------------------------------------
Date:     01-16-90 (10:20)
To:       DAVE SPAULDING
Subject:  Rainbow Comm Programs
From:     GEORGE THEALL

DS>what he really wants is to be able to use a transfer protocol other
DS>than Kermit which is what he is using now.

   There are many Rainbow programs which support Xmodem (look at LCTerm,
Decmini, PibTerm, TurboComm II, etc...). BinkleyTerm does this and
Zmodem as well.

   These programs are all available from the INFO-DEC-MICRO file
archives. Look for them too on your local Rainbow-oriented bbs.

George
---
 ~ EZ 1.23b4 #263 ~ BARCELONA - Site of the 1992 Olympic Games

------------------------------
Date:     01-16-90 (14:21)
To:       GEORGE THEALL
Subject:  Accessing and clearing MP
From:     HARRY GRAY

I replied to you somewhere else. For the benefit of others:
1. The MPSC controls the COM port on the Rainbow. It is more complex
       than the UART on the IBM (and more difficult to use)
2. MSC 5.1 (except for the graphics library - at least) runs on the
       Rainbow under MSDOS 2.05 up. The install program runs on 3.10b
       with Code Blue as does Quick C in integrated mode, Code View in
       window mode, and the Microsoft editor, M. Code View runs in
       sequential mode without Code Blue. The IO ports seem to be
       changed by Code Blue.

       Josh
---
 . Via ProDoor 3.2.R Satalink Node 2
==============================================================================
Date: 01-14-90 (13:39)           Number: 920       SATALINK (tm) Your Ult
  To: GEORGE THEALL  Refer#: NONE
From: CHRIS RYAN    Read: YES
Subj: RE: C COMPILER ON RAINBOW    Conf: (74) fRAINBOW
------------------------------------------------------------------------
re: "C" compiler for Rainbow, the patches published in Rainbow News for Turbo
C 1.5 work fine on Ver. 2.0 also. One caveat though, I've been using the
patched version on a 100B with DOS 3.10A & have had no problems except with
shelling to dos. The display is the same as I see on the PC-compatible at
work, & functionality is the same. The Code Blue switches necessary are /a/v/c
(all of 'em). The caveat is that when I upgraded DOS to 3.10B, I completely
lost the menu lines and menu boxes. And the display does look different.
The menu lines
& boxes still function, but you better know what they are asking you,
since you are working blind. (This happened on the patched & unpatched version
of Turbo C, and on Turbo Pascal Ver 5.0.)
Suitable Solutions were understating the case when they said that there were
some video anomolies with the Borland language products. Still, they do functi
and if you aren't interested in using Borland's "I.D.E." for display, it
works fine from the command line.
Also in passing, I heard Booth Hartley comment at one of our LUG meetings
that Microsoft C works without a patch. Don't know the version number, and
I am not sure, but I don't think he was referring to Quick C. (He is on CompuS
as Rainbow Graphics developer - he's done the GIF decoder for the RB.) Maybe
he can help further.


---
* Origin: Long_Island RB (Opus 1:102/138)

------------------------------
Date:     01-14-90 (13:55)
To:       DAVID STRICKLER
Subject:  ALTERNATIVE COMM PKGS FOR
From:     CHRIS RYAN

Also good is PIBTERM. I've been using it for about 2 years, and only just
recently switched over to BINKLEYTERM, and that was mainly to get Z-MODEM
capabilities. If your friend is familiar with the PROCOMM style of interface
(I'm not familiar with the one he has) then PIBTERM won't come as any great
shock. NB: I also started out with LCTERM, but switched almost as soon as
I found an alternative, since I could use it only under DOS2.11, which ment
that I couldn't access my harddisk
(set up under 3.10A). Pibterm (3.25) comes in IBM & Rainbow flavors,
they don't mix. If not avail locally, they are here on Long Island Rainbow
(102/138), with all of the necessary RB mods.
good luck.

---
* Origin: Long_Island RB (Opus 1:102/138)

------------------------------
Date:     01-15-90 (18:30)
To:       GEORGE THEALL
Subject:  RE: C COMPILER FOR 'BOW
From:     CHRIS RYAN

PER ARTICLE IN *RAINBOW NEWS* OF JUNE '88 (VOL5,#4-6), PG. 57, BY CHRIS WALTHE
ntc.$$$
1
e3e6b 90
e3e6c 90
e3e7c 90
e3e7d 90
e3fe3 90
e3fe4 90
e3feb 90
e3fec 90
w
q
^z
THIS IS CONTENTS OF DEBUG FILE USED TO PATCH TURBO C. ALTHOUGH CHRIS DIDN'T
SAY THEY WERE FOR VER. 2.0, THEY DO WORK. I'VE BEEN USING THEM FOR ABOUT
A YEAR. HOWEVER, THAT WAS WITH CODEBLUE (/A/V/S/C/L) AND
***DOS 3.10A***. SO FAR, I HAVE NOT BEEN ABLE TO WORK AROUND THE "VIDEO
ANOMOLIES" THAT SUITABLE SPEAKS OF WITH ***DOS 3.10B***. THESE APPEAR WITH
BOTH THE PATCHED & UNPATCHED VERSIONS OF TURBO C 2.0.
AN INTERESTING OBSERVATION: IN THE INTERESTS OF "WHAT THE HELL, WHY NOT",
I TRIED THE PATCH ON TURBO PASCAL 5.0, NO GOOD. WOULDN'T RUN. UNDER DOS 3.10B,
TURBO PASCAL 5.0 RUNS, & THE "VIDEO ANOMOLIES" THAT OCCUR ARE THE SAME THAT
OCCURED WITH BOTH PATCHED & UNPATCHED VERSIONS OF TURBO C 2.0. (HAVEN'T TRIED
PATCHED 5.0 WITH 3.10B YET.)
HOPE THIS HELPS.


---
* Origin: Long_Island RB (Opus 1:102/138)

------------------------------
Date:     01-17-90 (08:37)
To:       CHRIS RYAN
Subject:  PATCHING TURBO C (BAD???)
From:     GEORGE THEALL

CR>PER ARTICLE IN *RAINBOW NEWS* OF JUNE '88 (VOL5,#4-6), PG. 57, BY CHRIS
WALTHE
...
CR>THIS IS CONTENTS OF DEBUG FILE USED TO PATCH TURBO C. ALTHOUGH CHRIS DIDN'T
CR>SAY THEY WERE FOR VER. 2.0, THEY DO WORK. I'VE BEEN USING THEM FOR ABOUT
CR>A YEAR. HOWEVER, THAT WAS WITH CODEBLUE (/A/V/S/C/L) AND
CR>***DOS 3.10A***.

   These are for v1.5. I have ***SERIOUS*** doubts that these work
properly on v2.0. Have you traced TC's program execution before patching
to determine where incompatibilities existed or have you simply applied
the patches blindly and observed that they work (more or less)? I mean,
what reason do you have for patching those portions in TC.EXE?

   Several people have told me the IDE from TURBO C v2.0 does ***NOT***
need to be patched to run under Code Blue and DOS v3.10b. (How different
is v3.10a?) The standalone compiler (TCC.EXE) and macro preprocessor
(CPP.EXE) do, however, require patching since both by default take
control of int 18h.


George
---
 ~ EZ 1.23b4 #263 ~ This space for rent - call (215) 662-0558

------------------------------