• Subject: Re: System 34
  • From: dhandy@xxxxxxxxxxx (Douglas Handy)
  • Date: Sat, 08 Jan 2000 15:10:17 -0500

Al/Nina,

>>when the 32 came out, dfu and seu seemed like space age tools compared
>>to kde and kse.
>
>I wrote interactive programs on the System/3 Model 6.  Set and Key 
>statements in RPG II, but alas, yes KSE.

My brother didn't like how S/32 DFU would roll the fields as you
entered stuff, so he wrote (in assembler) his own generic replacement
for DFU so he could maintain files in "full screen".  If you can call
a 6 x 40 character display "full screen". :(

I think he had too much time on his hands back then.  He probably had
the only S/32 which had sign-on security, a menu driver, and full
screen interactive (not SET/KEY) programs.  All written in assembler.

I'm still amazed when I think how SCP ran in just a 2K transient space
on the S/32!  All the S/32's I ever used had just 16K of memory,
though they ranged from about 5MB to a whopping 13MB of DASD.

And two of them even had the line printer instead of dot matrix.  If I
mismember correctly, one of the clients with a dot matrix had a 40cps
uni-directional model instead of bi-directional.  Even compiles took
forever to print.  You tried *real* hard to not go through extra
edit/compile cycles!

Those were the days...

Doug
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].