🚀 go-pugleaf

We are currently using a TSR which redirects COM4 to go to a NetSentinel
security key running on a Novell server (tried under 3.11, 3.12, and 4.1).
When using NETX, all works well.  The application, which is writting in a
very restrictive language writes to com4, our TSR picks up the data and
retransmits it to the security key.  When we go to VLM's, this no longer works.
What appears to happen is that the VLM gets in the way of the writes to
COM4, preventing them from getting to the TSR.

When I contacted Novell tech support several months ago, they basically said
that there is a bug in DOS which has COM* being treated specially, and with
VLM's they are reproducing the behavior (although NETX worked fine).  They
also claim that, since it is "technically" a bug in DOS, they aren't going
to alter the VLM behavior to support what we are trying to do.  Unfortunately,
we have customers who's network administrators are requiring them to use
VLM's on their PC's.  I need a solution to my problem, and was wondering if
anyone could point me in the right direction (since Novell doesn't seem to
care).

What the application can basically do is open/close/read/write/etc. to a file
or device, but cannot talk directly to registers or hardware, or call any
of the NetSentinel routines directly.

Any assistance is much appreciated.

	-- Dave
-- 
    "I am an invisible man.  No, I am not a spook like those who haunted Edgar
Allan Poe; nor am I one of your Hollywood-movie ectoplasms.  I am a man of
substance, of flesh and bone, fiber and liquids -- and I might even be said to
possess a mind.  I am invisible, understand, simply because people refuse to
see me.  Like the bodiless heads you see sometimes in circus sideshows, it is
as though I have been surrounded by mirrors of hard, distorting glass.  When
they approach me they see only my surroundings, themselves, or figments of
their imagination -- indeed, everything and anything except me."

				    -- Ralph Ellison (from the Invisible Man)