W.S. Lockwood III wrote in a message to David Calafrancesco:
 DC> Big question... why bother? What can that version do that NS2.02 for
 DC> OS2 can't do? If you need it to respond as a Ver 3 NS then add a -3 to
 DC> the command line switch. You need to first make sure that your
 DC> VDOSTCP.SYS is being loaded properly and also to get rid of any WIN
 DC> based TCP stacks inside the WINos2 as they will conflict with the IBMs
 DC> TCPIP stack. There are also fixes that are necessary that include a
 DC> new VDOSTCP.SYS for DOS that is supposed to work with NS3.  
 WSLI> I have applied fix pack 26, is that what I needed to do to
 WSLI> get VDOSTCP.SYS updated?  If not, what do I do?
Possibly need to run Retrieve software updates and update the IAK which is 
not part of the fixpack unless you run Warp Connect and even then it has a 
whole new mpts and TCPIP update fixpack for Warp Connect. 
 DC> Again... why? It all sounds too damn old fashioned for me... WinOS2 is
 DC> for Spreadsheets and accounting software, not web browsers, IMHO. 
 WSLI> Because I can't get the plugins to work.
Don't know about no plugins but they appear to work for people at work. I 
don't do multi-media here for the BBS but haven't heard of any problems short 
of the NS202 prior to April had some problems and there is a new plugpack. 
Have you ever installed the Beta NS2? 
Dave Calafrancesco, Team OS/2
dave@drakkar.mhv.net
... They got the library at Alexandria, they're not getting mine! 
--- 
---------------