=========================================================================
 
INFO-ATARI16 Digest         Thu,  1 Feb 90       Volume 90 : Issue  138
 
Today's Topics:
                              EMULATORS
                         Lynx developer info
                        New Atari ST keyboard
                         Resettable RAM Disk
                          Shareware Policy.
                         SPECTRE GCR PROBLEM
ST Format, TOS 1.4 moans directed at Atari UK (was: HAPPY NEW YEAR, ALL!)
             Tick-tick-tick-CRASH! is not dead in TOS 1.4
                  Want pseudo-trap handler examples
----------------------------------------------------------------------
 
Date: 1 Feb 90 07:59:13 GMT
From:
 cs.utexas.edu!jarvis.csri.toronto.edu!neat.cs.toronto.edu!omicron.cs.fsu.edu!fs
 ucs.cs.fsu.edu!boyd@tut.cis.ohio-state.edu  (Mickey Boyd)
Subject: EMULATORS
Message-ID: <9002010521.AA10485@fsucs.cs.fsu.edu>
 
In article <1998@moscom.UUCP>, tmb@moscom.UUCP (Tom Bellucco) writes:
>Let's compare apples to apples here...it makes sense to want 3 seperarte
>items that perform their tasks perfectly than 1 item that performs 3 seperate
>tasks half-ass.
>
>Look at the list of software that wouldn't run on the Megas!  You bought a
>piece of software for an ancient IBM PC, it worked on a PS/2.  period.
>
>As for wives, the one you described is taken.  :-)
>
>--
> Tom Bellucco - moscom!tmb@cs.rochester.edu  or  ?...?!rochester!moscom!tmb
>                    -------------------------------------
>   "Whatever I said, I didn't mean it...unless, of course, you liked it!"
>   #include <std.disclaimer>
 
Ah, such a simple answer for such a complex question.  I would say that it
makes sense to emulate a mac on an ST, because it does an equal or BETTER
job of it than the mac itself about 99% of the time, for much less money.
If you want to do work with a PC, buy one and set it up next to your ST.
The biggest flaw with the PC emulators out now is that they don't really
out-perform the real PC's, and are only of use (but valid use) to:
 
          a:  people who only need PC compatability occasionally.
          b:  people who have very small desks, and no money for furniture
              (but plenty for hardware add-ons).
          c:  hacker-types that just want to do it for the fun of having
              two or three machines in one casing.
 
As always, these statements are all IMHO, and I intend to get a PC emulator
board because I fit in group c.
--
 
    -----------------------------------------------------------------------
    ---------------------------------+-------------------------------------
         Mickey Boyd                 |    "Nobody can be exactly like me.
                                     |      Even I have trouble doing it."
             FSU Comp Sci            |              - Tallulah Bankhead
    ---------------------------------+-------------------------------------
    -----------------------------------------------------------------------
 
------------------------------
 
Date: 31 Jan 90 18:36:58 GMT
From: portal!atari!kbad@apple.com  (Ken Badertscher)
Subject: Lynx developer info
Message-ID: <2012@atari.UUCP>
 
For information on becoming a Lynx developer, please contact
Larry Siegel at Atari U.S. Corp. (Chicago).  His address is:
 
Larry Siegel, VP Software
Atari U.S. Corp.
330 Eisenhower Lane
Lombard, IL 60148
 
Phone: (708) 629-6500
--
   |||   Ken Badertscher  (ames!atari!kbad)
   |||   Atari R&D System Software Engine
  / | \  #include <disclaimer>
 
------------------------------
 
Date: 30 Jan 90 05:00:22 GMT
From:
 cs.utexas.edu!samsung!brutus.cs.uiuc.edu!usc!elroy.jpl.nasa.gov!peregrine!ccicp
 g!cci632!rit!ultb!clf3678@tut.cis.ohio-state.edu  (C.L. Freemesser)
Subject: New Atari ST keyboard
Message-ID: <2048@ultb.isc.rit.edu>
 
In article <1129@carroll1.cc.edu> dnewton@carroll1.cc.edu (Dave Newton the Late)
 writes:
>
>   I know this has been discussed, but I was wondering if anyone has the
>canonical list of replacement keyboards for the ST.  I'd like to put the
>beast in a new box, get one of those cute curly cables for the keyboard,
>and get a real keyboard.
>   If anyone knows of a replacement, or anyone has done one, please tell
>me.  If there are sufficient replies and/or requests for info, I'll summarize.
>   Thanx in advance.
>
Well, there aren't any REAL replacement keyboards for the ST.  You can
buy those awful spring-things to stiffen up the keyboard, but they don't
work.
 
I've been kicking the idea around of building a new keyboard with REAL
key mechs (like the Mega and STacy have) for my 520.  It's only an idea,
but seems quite feasible.  Of course, I'd have to make my computer into
a detached-keyboard type (but I need the extra room for upgrades
anyways).  I'd also make some fundamental changes, like removing the
slant to the function keys (their shape is impractical and a waste of
space) and moving the joystick ports to the external keyboard itself,
thereby cutting down the number of wires going to the motherboard from
22 to about 8.
 
How do people feel about such a thing?  I'm surprised it has not been
done yet.  From what I hear, quite a few people would like something
better than this rubber crap we use now.
 
 
Chris Freemesser, Rochester Institute of Technology :BITNET:%clf3678@RITVAX
    |||        ____________                         :GEnie: C.FREEMESSER
    |||       /___    /          (and 8-bit too!)   :USENET: clf3678@rit.isc
   / | \   ______/   /                              :        .edu
Call the A.C.O.R.N BBS (716)436-3078, 300/1200 baud :<-or my BBS
 
------------------------------
 
Date: 1 Feb 90 07:55:43 GMT
From:
 cs.utexas.edu!jarvis.csri.toronto.edu!neat.cs.toronto.edu!omicron.cs.fsu.edu!fs
 ucs.cs.fsu.edu!boyd@tut.cis.ohio-state.edu  (Mickey Boyd)
Subject: Resettable RAM Disk
Message-ID: <9002010514.AA10434@fsucs.cs.fsu.edu>
 
In article <908@watserv1.waterloo.edu>, bmaraldo@watserv1.waterloo.edu
 (Commander Brett Maraldo) writes:
>
>       Can someone tell me where I can find a resettable ram disk?
>RDY.PRG from MWC will only allow a partition to 700k.  I would like
>to make a 1.5M partition.  It would be great if the M-Disk utility
>that was posted to binaries was resttable; it doesn't appear to be.
>
>Brett L Maraldo
 
Coderam, included on the Codehead Utility disk, is the best ramdisk program
I have used (of many).  It is reset-proof (really), and supports many different
sized partitions (from a menu at bootup, will go to a user-default in about
5 seconds).  This program, along with the others on the disk, are well worth
the price.  These guys churn out some of the freshest and most useful code
for the ST's.
 
--
 
    -----------------------------------------------------------------------
    ---------------------------------+-------------------------------------
         Mickey Boyd                 |    "Nobody can be exactly like me.
                                     |      Even I have trouble doing it."
             FSU Comp Sci            |              - Tallulah Bankhead
    ---------------------------------+-------------------------------------
    -----------------------------------------------------------------------
 
------------------------------
 
Date: 1 Feb 90 02:01:14 GMT
From:
 cs.utexas.edu!jarvis.csri.toronto.edu!utgpu!watserv1!watcgl!electro!ignac@tut.c
 is.ohio-state.edu  (Ignac Kolenko)
Subject: Shareware Policy.
Message-ID: <1295@electro.UUCP>
 
In article <1940@laura.UUCP> klute@heike.informatik.uni-dortmund.de (Rainer
 Klute) writes:
>If the shareware author does really want to see any money he
>has to find out how he can "encourage" the user to pay. This
>can be done be offering some additional benefit for paying. I
>tried this with my Arcgsh from version 2.1 upwards: From time
>to time a dialog box pops up and asks the user to pay for the
>program. He then can click any button and the program
>continues. This procedure has two advantages:
>
>1. Occasional use of Arcgsh: The user can take full advantage
>   of the program without paying. The "Please pay your
>   shareware donation" dialog boxes he can ignore. He is not
>   *forced* to pay. The boxes will not disturbe him too much
>   because he uses Arcgsh seldom.
>
>2. Regular use of Arcgsh: The frequent popping up of those
>   dialog boxes gets really annoying and the user wants to get
>   rid of them. And this is exactly what he gets if he pays his
>   shareware donation.
>
>Experience has shown that this procedure works very well.
 
 
 
this is actually a very common technique among shareware authors.
before quickst went commercial, the last couple of demo shareware versions
that loaded from the auto folder would purposely put all kinds of
ordering information and "propaganda" on the screen and forcibly made the
user press a key before continuing. this way, people who didn't want to
upgrade to the shareware version (with no such messages or keypress waits)
could still use the program, but they would have to endure the "press any
key" condition EVERY time they would reboot. we got lots of shareware
contributions after that, with almost all letters asking (hoping!) that
the registered owner version not have such things. and of course, that
is the incentive of registering: you get a clean, properly working version
with enhancements and further bug fixes from when the shareware version came
out and the entitlement to receive future updates whenever they become
available.
 
of course, there are people who will actually take the time and disassemble
shareware programs and remove the offending code which pops up the
dialog boxes, or forces a keystroke before continuing, etc. for the
three hours they spent disassembling and debugging, even someone working
at mcdonalds at $5 an hour could have broken even (at least for quick st)
by sending in their contribution ... but that's their choice!!! :-) :-) :-)
 
 
 
--
=====Ignac A. Kolenko (The Ig)=====watmath!watcgl!electro!brasoft!ignac======
     co-author of QuickST, and the entire line of Quick Software!!!!
  Branch Always Software Box 2624, Station B, Kitchener, Ont. CANADA N2H 6N2
=============================================================================
 
------------------------------
 
Date: 1 Feb 90 07:54:09 GMT
From:
 cs.utexas.edu!jarvis.csri.toronto.edu!neat.cs.toronto.edu!omicron.cs.fsu.edu!fs
 ucs.cs.fsu.edu!boyd@tut.cis.ohio-state.edu  (Mickey Boyd)
Subject: SPECTRE GCR PROBLEM
Message-ID: <9002010510.AA10387@fsucs.cs.fsu.edu>
 
In article <25C771C5.3162@paris.ics.uci.edu>, wngai@ics.uci.edu (Wayne Ngai)
 writes:
>
>       I just bought Spectre GCR not too long ago and I have a color monitor.
>When I run mac software on it, the color is really bad.  Can anyone out there
>tell me how I can improve the problem?  I try following the suggestion on the
>manual and it doesn't seem to have any effect on the mac mode.  I've
>tried changing the colors on the atari control panel and  no effect.
>If you have any sugguestions or help, I would deeply appreciate it if
>you would send them through email to me.  Thank you so much!!!
>
>
>Wayne Ngai
>
>Wngai @Paris.ics.uci.edu
 
Well, mac emulation on the atari color monitor is not very satisfying.  You
may be able to make it a little better by setting the colors to emulate a
grey scale, but it is still pretty rough.  On the other hand, such emulation
with a mono monitor ($150 new, about $80 used) is superior to real mac monos.
 
--
 
    -----------------------------------------------------------------------
    ---------------------------------+-------------------------------------
         Mickey Boyd                 |    "Nobody can be exactly like me.
                                     |      Even I have trouble doing it."
             FSU Comp Sci            |              - Tallulah Bankhead
    ---------------------------------+-------------------------------------
    -----------------------------------------------------------------------
 
------------------------------
 
Date: 31 Jan 90 20:07:25 GMT
From: portal!atari!kbad@apple.com  (Ken Badertscher)
Subject: ST Format, TOS 1.4 moans directed at Atari UK (was: HAPPY NEW YEAR,
 ALL!)
Message-ID: <2013@atari.UUCP>
 
grahamt@syma.sussex.ac.uk (Graham Thomas) writes:
 
| ps. UK mags have been saying that disks formatted with the STE and TOS
| 1.6 are not readable by IBM PCs.  Any comments?
 
Sounds suspiciously like a case of bad floppy or old DOS.  The desktop
formatting code did not change AT ALL between Rainbow and STE TOS.
 
Compatibility problems can arise with old MS-DOS versions which use a
magical "media descriptor byte" rather than the proper parameter block
information from the boot sector of a floppy.  The "media descriptor
byte" is not supported by GEMDOS, nor is it supported by Microsoft any
more.  Incompatibilities also exist among certain PC drives - not only
with ST formatted disks, but with PC formatted disks as well.
 
Am I being paranoid, or has there really been a proclivity on the part
of the press (UK and elsewhere) to slam the STE???  I've heard more
negative rumours and outright lies about the STE than any other recent
Atari development.  I wonder why this is?
 
--
   |||   Ken Badertscher  (ames!atari!kbad)
   |||   Atari R&D System Software Engine
  / | \  #include <disclaimer>
 
------------------------------
 
Date: 31 Jan 90 15:38:28 GMT
From: mcsun!ukc!icdoc!syma!grahamt@uunet.uu.net  (Graham Thomas)
Subject: Tick-tick-tick-CRASH! is not dead in TOS 1.4
Message-ID: <2087@syma.sussex.ac.uk>
 
From article <22199@mimsy.umd.edu>, by bane@mimsy.umd.edu (John R. Bane):
> The dreaded keyboard-repeat-and-lock crash bug is apparently not gone in TOS
> 1.4.  For those of you who haven't seen it before, what happens is after
> several minutes of fairly steady typing in an editor (I use Word Writer),
> the keyboard suddenly starts slowly retyping the last seven or so keys you
> typed, over and over again.  After about 10 repeats, your program crashes.
>
This is similar to various bugs which many people have encountered with
First Word Plus.  (No coincidence, probably.  I understand that both
Word Writer and First Word Plus were written by the same outfit - GST in
the UK.)
 
We used to get the 'repeat then crash' a lot with Wordplus v2.  With UK
version v3.14 we now mostly get a simple freeze - the program just seems
to stop accepting keyboard & mouse input, and the only way out is to
reboot.  GST say it's something inside TOS (or GEMDOS or whatever layer
it might be), so I was rather hoping the problem might go away with TOS
1.4.
 
Does anyone have any information on what the problem might be?  It's
frustrating, because there doesn't seem to be any way of replicating the
problem.  People can go for months without it striking, and then have it
happen twice in a day.  (Sunspots??? :-) )
 
For what it's worth, it hasn't happened to me so often since I installed
Turbo ST (the software blitter, not the acceleration board Turbo 16),
but it has happened a couple of times.  It has happened to a wide range
of people where I work, from techies to novices, from hunt 'n peckers to
touch typists.
 
Does anyone know of other programs where similar things happen?  I
recall some messages a while ago about WordPerfect hanging, but ours has
been OK.
 
I'm waiting for the bug to strike while I'm running Wordplus from within
NeoDesk, so I can try sending a few wind_update() calls.  Would this do
any good?
 
Thanks,
 
Graham
 
--
Graham Thomas, SPRU, Mantell Building, U of Sussex, Brighton, BN1 9RF, UK
 JANET: grahamt@uk.ac.sussex.syma  EARN/BITNET: grahamt@syma.sussex.ac.uk
 ARPA:  grahamt%syma.sussex.ac.uk@nsfnet-relay.ac.uk
 UUCP:  grahamt@syma.uucp          Phone: +44 273 686758
 
------------------------------
 
Date: 31 Jan 90 15:34:41 GMT
From: motcsd!motsj1!mcdchg!chinet!saj@apple.com  (Stephen Jacobs)
Subject: Want pseudo-trap handler examples
Message-ID: <1990Jan31.153441.7404@chinet.chi.il.us>
 
I could really use examples of handlers for the software trap vectors.  Let's
just say that the documentation I have available isn't entirely clear or
consistent.  Specifically, if anyone would care to post fragments in C or
assembler that did the following 2 functions, I probably wouldn't be the
only person grateful to see them:
 
1) Attempts to read from a floppy disk.  If there is no disk in the drive,
   writes a message to the screen and waits for a keypress, then retries the
   original read (etc until satisfied).  The built-in 'drive not responding'
   alert is never activated.
2) Accepts input into a string with Cconrs  (do I have the name right?  I
   never remember such things, and my manuals are elsewhere).  If control
   C is pressed it intercepts the terminate vector and does something
   sensible (like clearing the input string and starting over).
 
Thanks.
                                     Steve J.
 
------------------------------
 
End of INFO-ATARI16 Digest V90 Issue #138
*****************************************
