ICE
TCP/IP Products => TCP-PLUS => Topic started by: johnh on January 16, 2004, 10:02:12 am
-
I am running ICE TCP on a Win XP station. About every other day or so when I try to open Dejawint, it stops responding and I have to go into Task Manager and then End Task. Then I get a system error window that pops up saying "The request to end the selected 16 bit task has timed out. The Win 16 Subsystem may be unstable. Press OK to terminate the Win 16 Subsystem or Cancel to leave it running." This is a real pain because when this happens, the only way to fix it is to reboot my pc to restart the win16 subsystem. This was happening a while back and I reinstalled my system (XP). There has to be a better way to resolve this issue than constant rebooting / rebuilding. Any help would be greatly appreciated.
-
I am running ICE TCP on a Win XP station. About every other day or so when I try to open Dejawint, it stops responding and I have to go into Task Manager and then End Task. Then I get a system error window that pops up saying "The request to end the selected 16 bit task has timed out. The Win 16 Subsystem may be unstable. Press OK to terminate the Win 16 Subsystem or Cancel to leave it running." This is a real pain because when this happens, the only way to fix it is to reboot my pc to restart the win16 subsystem. This was happening a while back and I reinstalled my system (XP). There has to be a better way to resolve this issue than constant rebooting / rebuilding. Any help would be greatly appreciated.
Windows 16 bit emulation has become less exact over the last few revs of Windows. The solution is to update to a 32 bit version of ICE.TCP. The workgroup sized version is called ICE.TCP.PLUS and is very similar to the version you are using. For large site installls we recommend ICE.TCP.PRO.
If you check out compatibility chart, you will see that we don't support 16 bit versions on any Windows OS later than 98 second edition.
http://www.jriver.com/products/compatibility.html