Microsoft KB Archive/103705: Difference between revisions
From BetaArchive Wiki
(importing KB archive) |
m (Text replacement - ">" to ">") |
||
| Line 33: | Line 33: | ||
== SUMMARY == | == SUMMARY == | ||
Users sometimes pipe network commands to NUL to shield their workstations from network messages. But If SHARE.EXE is loaded and any LAN Manager LOAD command has been piped to NUL before you enter Windows enhanced mode (LOAD NETBEUI | Users sometimes pipe network commands to NUL to shield their workstations from network messages. But If SHARE.EXE is loaded and any LAN Manager LOAD command has been piped to NUL before you enter Windows enhanced mode (LOAD NETBEUI > NUL) then all subsequent piping to NUL from within Windows reports a sharing violation.<br /> | ||
<br /> | <br /> | ||
To avoid this, refrain from piping protocol LOAD commands to NUL. It should not pose a problem: LOAD commands return only two lines of information. | To avoid this, refrain from piping protocol LOAD commands to NUL. It should not pose a problem: LOAD commands return only two lines of information. | ||
Latest revision as of 17:43, 20 July 2020
Article ID: 103705
Article Last Modified on 10/31/2006
This article was previously published under Q103705
SUMMARY
Users sometimes pipe network commands to NUL to shield their workstations from network messages. But If SHARE.EXE is loaded and any LAN Manager LOAD command has been piped to NUL before you enter Windows enhanced mode (LOAD NETBEUI > NUL) then all subsequent piping to NUL from within Windows reports a sharing violation.
To avoid this, refrain from piping protocol LOAD commands to NUL. It should not pose a problem: LOAD commands return only two lines of information.
Additional query words: 2.20 2.2
Keywords: KB103705
