#: 14607 S12/OS9/68000 (OSK)
    15-Mar-92  14:20:24
Sb: #14606-#MM/1 help
Fm: Steve Wegert 76703,4255
To: Kevin Darling 76703,4227 (X)

Kev,

Here's what two days of testing has shown me:

It now appears there are two distinct problems that have been hidding as one.

Problem #1:

The creeping CPU time.

Thanks for the info on windio. Everything was as you said it would be. A quick
session with dEd, and viola!  no more CPU creep. (Is this anything like the
Texas two step?)

Problem #2:

The 'one off' problem can now be be duplicated at will .... at least with my
hardware setup. It looks to be isolated to /t2 only. It has nothing to do with
the CPU creep issue as it has continued since I patched windio.

Does the sc68901 and sc68681 drivers handle  sequences differently?

To duplicate the 'one-off' problem, I must fire up STERM on /t2. (I'm using
sterm because the shell will try to act on the ).

A quick funtionality test of sterm sets the stage (hit  to redisplay
it's help menu.)

Now, I issue  (On the Wyse 50 and the TVI912 this is a 
 command. The cursor homes, then 'scans the page'.)

At the end of the 'scan' approximately 196 '&' characters are spit out on on
sterm's screen.

At this point, the 'one-off' problem is active as hitting  will display
a few more '&' at each press of the  key. Attemping to do anyting at the
keyboard will now demonstrate the problem. (try an  for the help screen
hitting  several times to move things along.

The 'one-off' problem doesn't seem to effect any windows or processes on
 /t3 or /t4. I'd like to see what happens on /t1. If the problem occurs there
as well, it would appear that it's possibly the 68901 driver causing the woe. I
need to hit Mark up for the remaining pieces of my MM/1.

Can /t2 be moded to use a different driver?

Any further thoughts or suggestions are appreicated.

Steve




There is 1 Reply.