Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!suned1!efb
From: efb@suned1.Nswses.Navy.MIL (Everett F Batey)
Newsgroups: comp.os.msdos.desqview
Subject: Re: Communication programs
Message-ID: <10458@suned1.Nswses.Navy.MIL>
Date: 5 Jun 91 04:00:54 GMT
References: <1991May19.113245.19970@cs.umu.se> <13127@pt.cs.cmu.edu> <1880@csource.oz.au>
Reply-To: efb@suned1.Nswses.Navy.MIL (Everett F Batey II)
Organization: NSWSES, Code 4A05, Port Hueneme, CA 93043 - Opinions: Mine Alone
Lines: 18

In article <1880@csource.oz.au> david@csource.oz.au (david nugent) writes:
>> In article <1991May19.113245.19970@cs.umu.se> dvldbg@cs.umu.se (Daniel Brahneborg) writes:
>> Not unless you want your system to crash the next time a character comes
>This shouldn't be the case.  DV revectors the IRQ and manages the hardware

What I want to know is what happens if you try to share ( and how do you share
IRQs .. hear it is done under DOS ) does DV know to handle the say WAFFLE which
is FOSSIL-wise and suppose ka9q tcp/ip using COMM3 or COMM4 for ka9q's radio
modem, which ka9q seems not to be FOSSIL smart.

Has anyone an idea if I can throw enough RAM ( without unix ) to handle this
bizarre a configuration.

Any tips will be appreciated.  /Ev/
-- 
 +  efb@suned1.nswses.Navy.MIL  efb@gcpacix.uucp  efb@gcpacix.cotdazr.org +
 +  efb@nosc.mil   WA6CRE    Gold Coast Sun Users   Vta-SB-SLO DECUS  gnu +
 +  Opinions, MINE, NOT Uncle Sam_s | b-news postmaster xntp dns  WAFFLE  +