AB084@DK0RRZK0.BITNET (01/05/88)
To be very clear: I meant this "Does Joe Average Need Multitasking?" thing. ME
AB084@DK0RRZK0.BITNET (01/05/88)
I should have thanked everybody who wrote to me in response to my letter
about operating systems. I did so in some cases. But there are people
I am seemingly unable to write to. And I noticed that I have accidentally
deleted some letters, so I cannot answer them any more.
Therefore I have to choose this way to say
THANK YOU|
Michael Eibl
BTW: I found most of the letters worth being sent to the net.
Especially as compared to some af the somewhat childish arguments that
I read there...andre@mimsy.UUCP (Andre Tits) (06/02/89)
Thanks to all who sent me info on this (most of my ` thank you' email bounced back). My friend did reach the right person this time.
blee@plains.UUCP (Blaine Lee) (02/05/90)
Thanks for those who responded to my problem with my mouse...Yes it was a peskey virus. Vkiller did the work for me. My thanks to the author should be in the mail soon... For my other problems Nobody else has these problems??? I would realy like have these programs running on my machine, has anyone hacked a solution??? Tuzzle \ Domino 2 } No joystick access Squix / And Uniterm 2.0e is still easy for me to crash... all I have to do is move through a few menus or dialog boxes and things get all messed up. am I alone on this??? talk to me! Blaine Lee blee @ plains.nodak.edu Hey Dude, Lets Parity!!! blee @ next210.nodak.edu -*Voice Mail!
cr1@beach.cis.ufl.edu (Christopher Roth) (02/06/90)
Hello Blaine, I use Uniterm 2.0e quite a bit, and I haven't had any bugs you described. Well, there is one thing I get...I use Uniterm with Revolver, and I use it on Vax VMS system. I'll be in the editor, emulating vt200, when all of a sudden the screen will go bright and I will crash out to the desktop. Weird, huh? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= * Christoper Roth * "Machines have no * InterNet : cr1@beach.cis.ufl.edu * Conscience..." =-=-=-=-=-=-=-=-=-=-=-=-=-Post No Bills-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
scott@bbxsda.UUCP (Scott Amspoker) (03/26/91)
About a month ago I posted a request for some info needed to port
some MIDI software I wrote from a PC to an Atari ST. I got a few
responses directing me to various texts. Well, once I got the
information into a "usuable" form the port went very smoothly.
I'd just like to say "thanks" for help, folks.
For anyone who is interested here are a few tidbits I discovered about
the ST that are of concern to those implementing MIDI software:
The ABACUS book, as incoherent as it is, turned out to be invaluable.
The ROM listing in the back answered all remaining questions about the
hardware.
The LASER C manual explained the hardware interface better than
the hardware book in many ways.
TIMER A is available for programmable interrupt intervals. It
can be set for a wide range of intervals (the shortest being
a couple of microseconds).
The MIDI ports share the same exception vector as the keyboard.
A bios call may be used to set the address of "your" midi interrupt
handler. The main bios interrupt service routine gives the
midi handler first crack and then moves on to the keyboard handler.
This let's you *efficiently* take over the midi interrupt without
having to mess with the keyboard.
The VT52 simulator should handle most text-based applications without
any hassle.
The midi recieve port buffers only one character at a time. In order
to prevent overrun you must disable other non-critical interrupt processes
on the system. The vertical retrace interrupt (60hz) uses a memory
flag to tell it not to do certain processing. Turn off that extra
processing. Also, the TIMER C interrupt (200hz) will call the GEM
event counter (this is an indirect call through memory $400).
Change that location to point to your own stub routine. This will
deny GEM whatever use it is making of that interrupt but a serious
realtime application must have *complete* control. Only after
making these changes could I no longer overrun the midi port no
matter how hard I tried.
--
Scott Amspoker | Touch the peripheral convex of every
Basis International, Albuquerque, NM | kind, then various kinds of blaming
(505) 345-5232 | sound can be sent forth.
unmvax.cs.unm.edu!bbx!bbxsda!scott | - Instructions for a little box that
| blurts out obscenities.heiden@kboeng.enet.dec.com (Matthias Heiden) (04/15/91)
Thanks to all who replied to my question re. HP II printer problems.
I ended up soldering a pnp transistor into the strobe line as suggested
by John Logajan @ Network Systems (logajan@ns.network.com).
This solution has worked so fare fine (and is cheap). Matthias
--
--
digital equipment GmbH heiden@kbomfg.enet.dec.com
advanced system process development
Sudetenstrasse 5
W - 8950 Kaufbeuren (Germany) work: +49 8341 913392
--