Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: D Finnigan <dog_cow@macgui.com>
Newsgroups: comp.sys.apple2
Subject: Re: A2osX Crashes and Feature Request
Date: Tue, 7 Apr 2020 14:45:34 -0000 (UTC)
Organization: Mac GUI
Lines: 16
Message-ID: <dog_cow-1586270733@macgui.com>
References: <dog_cow-1585236859@macgui.com> <10bcc57c-e58c-49d6-bd92-d496f4dcdbb3@googlegroups.com> <afdc48bc-f712-455b-a573-835a06eba066@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 7 Apr 2020 14:45:34 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="8e94ec95806b3a13682f71e01b9b34e5"; logging-data="19398"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19iPFCYK3wrDc2dPf1DJaj2"
User-Agent: Mac GUI Usenet
Cancel-Lock: sha1:WAbvW7wbzRebuiugWY+eb0T7r1Y=
In-Reply-To: <afdc48bc-f712-455b-a573-835a06eba066@googlegroups.com>
Xref: csiph.com comp.sys.apple2:44583

Patrick Kloepfer wrote:
> This is not a bug.  If you look at any other software for the ethernet
> cards (and for that matter printer cards, serial cards/modems, etc.) you
> have to tell the system which slot a card is in.  Specifically, look at
> all
> the software that works with the Uthernet II, you either must put the card
> in a particular slot (2 or 5 or something) or you have to patch the
> software to tell it where the card is.  In the case of A2osX, it scans the
> slots to attempt to find a card (this is true for any driver you load with
> INSDRV), so if you install support for terminals with INSDRV SSC.DRV then
> that will do the same slot scanning and would trip over your TM II.  This
> is the reason KCONFIG allows you specifically tell A2osX to never scan a
> particular slot (to solve the problem you saw).

So crashing into the Monitor is not a bug?