|
Under Windows 95
-------------
1. (IntranetWare) Exiting RealAudio could cause a crash.
2. (IntranetWare) 32bit SPX applications did not work.
3. (IntranetWare) The following Windows 95 applications failed under the gateway's winsock because of use of Microsoft proprietary IPX APIs in Microsoft's WSOCK32.DLL.
- Oracle SQLNET
- Lotus Notes 4.xx
- Arcserv backup client
- Nprinter
- HP Jetdirect
4. (IntranetWare) MSVC WSOCK sample failure. This happened if two WSOCK processes/threads were in place at the same time.
5. (IntranetWare) IPX/IP Gateway Task showing not ready
6. (IntranetWare) Can not login to Microsoft SQL server.
7. (IntranetWare) Can find Microsoft SQL database when not specifying database name and protocol in SQL configuration.
8. (BorderManager) Can't read from x: message when launching 16-bit app on PC-98 with Japanese version of Windows 95.
9. (BorderManager and IntranetWare) Some WinSock programs run before user has a chance to login. Therefore, if access control is enabled, gateway task fails to connect to server. The fix is as follows. If a preferred gateway server is specified and the user is not logged in, the Gateway client will hold up WinSock requests until the user logs in. The Gateway task's windows will show status "Waiting For Login". This change has only been made for 32-bit on Windows 95.
10. Can't read from x: message when launching 16-bit app on PC-98 with Japanese version of Windows 95.
Under Windows 3.1
-----------------
1. (IntranetWare) When Windows was exited with WinSock applications active, memory could be corrupted.
2. (BorderManager) Pass gateway parameter to GwExe on WinExec rather than having GwExe read it from novws.ini. This assures EXE is using same value as DLL. This will fix problem on Windows 3.1 with NDPS running over Gateway, NDPS invokes WSACleanup, WinSock closes novgwp16, DLL stays in memory because NDPS still active, user disables gateway, NDPS invokes WSAStartup, WinSock WinExecs novgwp16, novgwp16 reads novws.ini and sees gateway=0. When WSAStartup causes start up of novgwp16.exe, do not return to user until novgwp16.exe calls winsock with its window handle. When WSACleanup causes close down of novgwp16.exe, do not return to user until novgwp16.exe calls winsock to clear handle. This should handle race conditions caused by invocation of startup/cleanup within one app.
3. (BorderManager) NDPS not working with IP/IP Gateway.
General
----------
1. (IntranetWare) Possible problem will large file transfer, over 3-7 MB.
2. (IntranetWare) Informix client failure to connect.
3. (BorderManager) Display "Last Proxy: a.b.c.d" in Gateway task's window. a.b.c.d indicates direct connection to Proxy is being used. Nothing indicates that a browser configured for proxy is still going through gateway.
4. Problem with 16 bit application, regarding
a) Support user blocking hooks that don't PeekMessage
b) Support a select loop that checks for connect completion but does not PeekMessage
Enhancements
------------------
1. WINSOCK.DLL modified to support native TCP/IP.
2. Support for WSARecvEx in WINSOCK.DLL and WSOCK32.DLL added.
3. maxSockets can now be edited into NOVWS.INI for gateway and native operation.
4. This adds UDP support to the BorderManager IP Gateways. This should resolve any UDP problem with the IP Gateway. This includes: GroupWise 5.2, via TCP/IP
Internet Explorer 4.x, etc.
**** Please note, this patch will NOT work with the old (NIAS4.0/IntraWare 1.0) IPX/IP Gateway. ****
For symptom number 1: Configure RealAudio to use TCP. Don't exit.
For all other symptoms: Install FIPG0004.
|
