RW> Hi all! Was wondering if anyone had any luck with configuring
 RW> EzyCom with NetSerial?  I would like to actually use and buy a
 RW> license for NetSerial but whenever I go to start EzyCo Win2K3 SBS
 RW> says that the NTVDM has returned with a hard error and then aborts
 RW> back to a DOS prompt.  Any ideas?

Well... I have no access to a 2k3server, but I decided to download the
latest version of EzyCom and see what it would do under XP with netserial.
I guess that's the kinda thing I oughta do since I am on the beta team.

I have two comports set up on netserial... 2 and 4. Com2 runs FD2.33ml on
port 24 with ADF for telnet connectivity.  It works perfectly.

Com4 is reserved just for these testing purposes :)

Anyway... I installed ezycom and set the modem commands for Com4 and tried
to get it to go with ADF.  No luck whatsoever.  Checked and rechecked my
netserial settings fot that port and it was right, and so were the settings
in ADF.  I first tried running the bbs.bat from a dos prompt several times
(old DOS baby habit) and it was coming back
that there was a config error in ezycom.  I then decided to click on the
bbs.bat from explorer and got a windows error.  Not the same as yours, but
it pointed me in the right direction... it stated that the application was
unable to open Com4.  Before resigning it to a netserial error, I decided
to go with another fossil, fossil problems being KNOWN to be a nightmare in
the past with certain software/fossil combinations.

I put BNU in my Ezy directory and added "BNU.COM /L3=57600 /M+"
in my bbs.bat file, and BANG!  There it was.  Logged in from another
machine on my LAN and it worked lovely.

The relevant parts of the bbs.bat file (setting will have to be adjusted by
you depending on what ports you're using):

---------------------

:start
BNU /L3=57600 /M+
ezy -E25

:finish
BNU /U
echo Ezycom is down

---------------------

One note on this... this only works consistantly when the bbs.bat is run
from an explorer window and clicking on BBS.BAT  ...  Even though the
unload BNU command is there, if any DOS window is left open that previously
ran it, the error returns (cannot open comport)... I have sat here playing
with it and so long as only one instance is open for any task of ezy, or
previously run task, it works fine.

As far as your netserial... make sure that the comports are set with:

Connection type : Telnet
Request Remote Telnet Echo : UNCHECKED
Accept Local Telnet Echo : CHECKED
Request Binary Connection : CHECKED
Port Mode : Check "Virtual Modem"
Port : Whatever you're using
Accept Inbound Connection : CHECKED

Also note, even though it shouldn't be necessary, I do have the virtual
modem devices for netserial installed in my devices.

I don't know for sure if this will help any, but this is the experience I
had this morning with Ezy and NetSerial under XP.  If this doesn;t help,
please let me know and I'll check into other problems that may be that are
on my mind, but would rather wait to look into if this "isn't"
the problem.

BTW... this is the first time in all the years I ever even
"looked" at EzyCom :)  Doesn't look like a bad package, but I'll
never switch from what I use now.  Too deep into it.

Phil

--- FMail/Win32 1.60
Netwo (1:267/169)