-=> /* Quoting Jorj Strumolo to Frank Sexton */ <=-
 FS> My only real suggestion would be to use all the native OS/2
 > stuff instead of your existing Windows stuff.  Why do you
 > want to keep using your Windows 3.1 stuff for the Internet?
 JS> Because I *know* that stuff, mayhap?  (Why do people
 JS> question motives instead of answering questions?)  And
 JS> I'm being methodical.
Didn't mean to question your motives.  I said what I did
because I wanted to give you my opinion that I thought
might help you.  I feel that the built-in native OS/2
Internet stuff was better then running Windows stuff under
OS/2.  Also, setting up the Win-OS/2 TCP/IP and internet
stuff I feel is much more difficult than setting up the
native OS/2 TCP/IP networking.  Either way this will be new
to you under OS/2. You can not use the actual DOS/Win
TCP/IP stack under OS/2 anyway.  Since no matter what you
do it'll be new to you I just thought you might prefer the
added performance of true 32-bit native OS/2 stuff that
comes with the operating system for free.
Anyhow, I certainly didn't mean to try to talk you into
anything you don't like.  I've just seen so many folks give
up on OS/2 because it didn't run their Windows stuff the
way they liked.   I was hoping to influence you so you
wouldn't get caught in the same trap.  That's all.
 JS> Try one thing, then move on.  And really, I need to
 JS> have the foundation stuff installed to *get* the
 JS> Internet connection in OS/2 before I even begin
 JS> considering what programs I'll pledge my heart to.
Understand.  Just felt that the OS/2 stuff would be easier.
Some folks try to load their Windows networking driver
stuff before they realize that some of it won't run under
OS/2. By that time the system can get plenty messed up from
botched installs.
 FS> OS/2's Internet support is about the best around,
 FS> IMHO.
 JS> No doubt it's grand, but I can't do everything at
 JS> once.
Agreed.
-Frank
(fsexton@xpert.net - http://www.concentric.net/~fsexton)
--- Blue Wave/OS2 v2.30
---------------