Hello Lars!

05 Jan 96 12:00, Lars Hellsten wrote to Darin McBride:

 DM>> Lars, Lars, Lars.  Porting your Renegade stuff over?  :-)

 LH> My PCBoard and later Telagard stuff (for now - what are the
 LH> chances of an OS/2 version of Renegade? ;) )

Which is why I'm running Max3 now.    I was really used to
Renegade, but I couldn't stand DSZ eating up 100% of my CPU on a 1200-baud
transfer... 

Now, 28.8kbps bi-directional transfers use maybe 10% of my CPU... :-)

 DM>> Don't bother - let OS/2 decide that the program isn't in use
 DM>> and swap it out on its own.  First, you don't have as much
 DM>> to do.  Second, the recall time is faster... :-)

 LH> Yeah, this didn't really occur to me at the time, and I wasn't
 LH> really thinking.  I'm just so used to DOS where if you leave

You're just used to using a non-reentrant interrupt handler, not an OS.  :-}

 LH> something in memory, it's going to stay there.  I didn't stop to
 LH> consider the fact that OS/2 should automatically swap out
 LH> something that's not being used if it needs more memory.  It's

Sometimes swapping things that ARE being used - swapping things in and out
furiously trying to keep up... :-)

 LH> just the thought of my program sitting in memory while it's doing
 LH> nothing that threw me off, I guess.

Oh, you should see some of MY stuff.. it sits there in memory doing
nothing, using gobs of memory at the same time.  I just stopped caring once
I got to 32-bit programming.  "I need 100MB of RAM?  No problem...
OS/2 will grab that for me..."  Using a 1500-byte struct in an array
of 300... who cares?  :-)

 LH> Now if only I could get this much response to my problem with
 LH> screen writes being slow.  (I think David Muir may have provided
 LH> an adequate solution for now, although it still is horribly slow
 LH> compared to DOS in which screen writes - even one character at a
 LH> time - are instant...)

I believe if you try to stick to multiple screen writes... basically build
the screen in a character array in memory, and write it out.  If I had a
book on the VIO API, I'd give ya more help.  Personally, I still stick to
C++'s I/O streams.  :-}  You're using Pascal, still, aren't you... :-)

Darin McBride

--- GoldED/2 2.42.G0614