Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!luth!d88-mbe
From: d88-mbe@sm.luth.se (Michael Bergman)
Newsgroups: comp.sys.amiga.tech
Subject: Re: JRComm (Was Re: AMIGA too slow for speeds higher than 9600 Baud? HELP!)
Message-ID: <892@tau.sm.luth.se>
Date: 2 May 90 14:41:52 GMT
References: <02373.AA02373@spirit.kref.sub.org> <625@titan.tsd.arlut.utexas.edu> <22897@uflorida.cis.ufl.EDU> <1332@faatcrl.UUCP> <334@ncc1701.sub.org>
Organization: University of Lulea, Sweden
Lines: 32

space@ncc1701.sub.org (Lars Soltau) writes:

>why does the stupid thing only run on a 80*25 window/screen? Hm? I have a
>704*282 pixels big Workbench screen and I bloody well expect any professional
>software to not stuff me into any NTSC frame.

>(minor flame off)

>Sorry for the harsh words, but I've been pissed about this a lot of times with
>quite a lot of different programs. It can't be that difficult to make use of
>big screens, can it now? Come on, US programmers, show that you're
>professional. Lots of you have proven it is possible.

Well, I for one am convinced that JRComm 1.0 will be great. It's fast and has
*lots* of options and modes.

However, just like Lars, I'm getting very tired of all these NTSC frames that
US programs use all the time. I know it's easy to check if the machine is PAL
or NTSC. I don't want to have an unused stripe at the bottom of my screen...
So come on guys: when you write a program, make the screen 255 high if it's
a PAL machine and leave the 200-line screens for the inferior NTCS mode.

Mike




-- 
      Michael Bergman         Internet: d88-mbe@sm.luth.se
  //  Dept. of Comp. Eng.     BITNET:   d88-mbe%sm.luth.se@kth.se
\X/   U of Lulea, SWEDEN      ARPA:     d88-mbe%sm.luth.se@ucbvax.berkeley.edu
			      UUCP:  {uunet,mcvax}!sunic.se!sm.luth.se!d88-mbe