public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: norseman <norseman@firstlight.net>
To: "linux-msdos@vger.kernel.org" <linux-msdos@vger.kernel.org>
Subject: Two cents worth of IPX/SPX
Date: Fri, 26 Dec 2003 09:34:30 +0000	[thread overview]
Message-ID: <3FEC00A6.12B46172@firstlight.net> (raw)

I've been reading the IPX/SPX incoming "conversations".

Something to keep as a background thought:
	I've been running packet passing in "real" MSDOS for over
a decade with virtually no problems. Any that do occur have been
tracked to other end - so far.
	Also - all attempts to run non-packet passing interfaces
in "real" MSDOS have lead to numerous and continuous problems.
	MSDOS is interrupt driven. Thus - less interrupts in the
chain the less chance MSDOS has to trip over itself.

I know this does not help directly in solving anything but it does 
lend support to why Stas Sergeev makes the comment:
.
.
... (using IPX via the packet driver is
now faster than via native IPX support), ...
.
.
to Reinhard Karcher.


Kind-of a case where Linux and MSDOS prefer packet passing, and
working with, rather than against, gets better results.


So much for my 2 cents worth.


Steve Turner
norseman@firstlight.net

                 reply	other threads:[~2003-12-26  9:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FEC00A6.12B46172@firstlight.net \
    --to=norseman@firstlight.net \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox