My corporation decided to skip Windows '95 and move to Windows NT
Workstation instead as our next PC operating system. However,  I am facing a
problem with new PCs because most vendors are shipping their units with Win
'95 preinstalled. We are not ready for a Windows NT Workstation upgrade yet
(or maybe we are but not aware of?) because of our current environment.
 
We've done some tests with PCs with Win '95 preinstalled and with one PC
upgraded to Win '95 that was already running our applications. We are having
trouble trying to use NS services to access the HP3000s and I think that the
same problem will arise with this setup under Windows NT workstation.
 
So far, we've used WRQ Reflection Network Series TCP/IP and NS/VT services
for DOS to access our HP3000s. I was informed that if we upgrade a current
PC with this configuration to Win '95, it will retain the 16-Bit drivers
from WRQ, and therefore NS-VT services will work. The major drawback is that
the Win '95 32-bit scheduler (one of Win '95's major enhancements) will be
substituted by the old Win 3.1 16-bit scheduler (with all other known
limitations), leaving Win '95 with just a "prettier" (mmm!, maybe just
different) interface.  We tried it on a PC and it worked, so this seems to
be true.
 
We also have licenses for RNS for Windows, but we can not use them because
the Windows drivers only work under Windows for Workgroups, and we do not
intend to use WFWG at all (do not ask, we found out after upgrading the
licenses!).
 
So my question is, is there a workaround to provide NS/VT services using
Windows '95 or Windows NT Workstation without  losing major capabilities of
the operating system upgrade?  Maybe Walker Richer and Quinn has the answer,
but based on past experiences, my best bet is that someone on this list have
addressed this situation already.
 
Rodolfo Lopez
[log in to unmask]