[nos-bbs] Jnos & windows

[Barry Siegfried]

["Bob Tenty" <bobtenty at sympatico.ca> wrote]:

> I played around with the SwsvPkt driver but I get: No adapters found.
>
> I assume this virtual packet driver is scanning for ethernet cards but
> it doesn't find them.  Have 2 network cards in this machine.

That's a new one on me.  Admittedly, I have only used the driver in
machines which only have a single ethernet adapter so I don't know
how it would function under the circumstances you describe above.

> Is there no need to use the -i (HW IRQ) option?

I know that the SwsvPkt packet driver defaults to IRQ 7 for its own use.
Is it possible that IRQ 7 is already being used in the machine where you
are trying to use it?  If so, perhaps the -i option to redirect it to an
unclaimed IRQ might help.

But that notwithstanding, it never occurred to me what the packet driver
might do if it finds two different ethernet adapters which are "owned"
by Windows.  Which one does it choose?  What criteria does it use?  The
actual hardware appears to be immaterial since the packet driver appears
to be "virtual" and it somehow works *through* Windows.

Quite honestly, it's a bit of magic to me how this packet driver works
at all, since it must somehow tell its host O/S, "Please send me all
your traffic from this card and it's ok that I'm here listening to
everything that you're hearing".  That's essentially how it functions.
It hears *everything* that Windows hears which is why our NOS programs
need to be patched for them to play nice and not try to route packets
for Windows.

Oh yes, because of what I have described above there is one other caveat
which I forgot to mention.  After NOS is patched to play nice with
Windows, you cannot possibly have IP connectivity between SwsvPkt and
its host O/S.  They will NOT talk to each other.  But other than that,
it functions as a very nice additional "machine" on your LAN and will
talk everywhere else.  :)

> ----- Original Message -----
> From: "Barry Siegfried" <bgs at mfnos.net>
> To: <nos-bbs at lists.tapr.org>
> Sent: April 28, 2006 4:35 PM
> Subject: Re: [nos-bbs] Jnos & windows
>
> Basically, just download the Swsvpkt packet driver zipfile and unzip
> it into a directory by itself.  If you try and "install it" through
> the Control Panel (the way it says to do in the README.TXT file) it
> may or may not actually "install".  It's not really necessary to do
> that if you're only using NOS.  Basically, after you unzip the files
> you really only have to:
>
> 1) Copy SWSVPKT.EXE and SWSVPKT.DLL into %SystemRoot%\SYSTEM32 and
>    SWSVPKT.SYS into %SystemRoot%\SYSTEM32\DRIVERS.
>
> 2) Create a shortcut to %SystemRoot%\SYSTEM32\CMD.EXE and
>
>    a) On the Misc tab under Properties change the Idle Sensitivity
>       setting to MAXIMUM, and,
>
>    b) On the Program tab under Properties use this Cmd Line:
>       %SystemRoot%\SYSTEM32\CMD.EXE /k <mynos>.BAT
>
>    c) Select a Working Directory where it can find its own
>       AUTOEXEC.NT and CONFIG.NT files.  Copy them from the
>       stock "system" AUTOEXEC.NT and CONFIG.NT files in
>       %SystemRoot%\SYSTEM32 and edit them accordingly
>       (specifically, remove what you don't need to load at
>       the end of the AUTOEXEC.NT file).
>
> 3) Load the SwsvPkt driver at the end of the AUTOEXEC.NT file or
>    at the beginning of the <mynos>.BAT file:
>
>    LH %SystemRoot%\SYSTEM32\SWSVPKT
>
>    which executes the SWSVPKT.EXE file in %SystemRoot%\SYSTEM32.

73, de Barry, K2MF >>
           o
          <|>      Barry Siegfried
+---------/-\---------------------------+
| Internet | bgs at mfnos.net              |
| HomePage | http://www.mfnos.net/~bgs  |
+----------+----------------------------+
| Amprnet  | k2mf at nnj.k2mf.ampr.org     |
| PBBS     | k2mf at k2ge.#cnj.nj.usa.noam |
+----------+----------------------------+