Windows for Workgroups or WC Hang on NETBIND Command (96334)
The information in this article applies to:
• Microsoft MS-DOS operating system 6.0
• Microsoft MS-DOS operating system 6.2
• Microsoft MS-DOS operating system 6.21
• Microsoft MS-DOS operating system 6.22
• Microsoft Windows for Workgroups 3.1
• Microsoft Workgroup Connections 1.0
This article was previously published under Q96334
If you use MS-DOS 6.2 Interactive Boot (F8 or CTRL+F8) to interactively
process your CONFIG.SYS and AUTOEXEC.BAT files, you may end up with very
little conventional memory if you are using Microsoft Windows for
Workgroups. For example, the MEM command indicates that MS-DOS and IO.SYS
are taking up more than 100 kilobytes (K).
If the Windows for Workgroups or Workgroup Connections network drivers
are loaded at the top of unallocated conventional memory, your system
may stop responding (hang). This problem can occur if you run a large
program before the NETBIND command.
If you are using the MS-DOS interactive boot option, this problem
can occur when you select N when given the option to process the
NET START command in the AUTOEXEC.BAT file. This leaves a lot of
memory that is waiting to be initialized allocated to PROTMAN.DOS.
To work around this problem, move the NET START command to the top of
your AUTOEXEC.BAT file.
If you are using the MS-DOS interactive startup option, respond
consistently to your network commands in both the CONFIG.SYS file and
the AUTOEXEC.BAT file. For example, if you respond Yes to the prompt
to load PROTMAN.DOS, you should respond Yes to the prompt for NET
| Modification Type:
|| Last Reviewed: