On Mon, 20 Mar 2000, Michael Nielsen wrote:
> I'm bought OS 3.5, which apparently is supposed to OEM Miami ??
>
> But anway it comes with the demo version, and I was trying to install it, but
> for some reason it will not communicate
> with my A2065 (period), neither with SANA II drivers nor the new MNI drivers,
> the mni drivers hang when I
> try to online the card, though they can obtain the ethernet addresse from the
> card, but the SANA II drivers
> simply states that they cannot open a2065.device Period.
There are a couple of things to watch out for when switching between MNI
and SANA-II drivers:
1) The unit numbers usually need to be different.
2) The default directory for the driver doesn't get switched when you
switch between SANA-II and MNI, and if you enter the driver name manually
you have to be careful about case.
3) Sometimes an "avail flush" is needed when switching from SANA-II to
MNI, with all kinds of nasty effects if you don't. Also be sure never to
put network card drivers in the Expansion drawer.
> Does anyone have similar problems??? Under 3.1, and Amitcp, the A2065
> functions perfectly, though a little
> slower than I would like.
Did you try AmiTCP with 3.5?
Note also that a bad entry for a2065.device in NSDPatch.cfg could cause
problems under 3.5.
Fred Wright
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
