TIP: Click on subject to list as thread! ANSI
echo: novell
to: ALL
from: Robert Voight
date: 1998-06-18 00:00:00
subject: RE:LOGIN from DOS7.0(win95).......

From: Robert Voight 
Subject: RE:LOGIN from DOS7.0(win95).......
Date: 1998/06/18
Message-ID: #1/1
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Organization: MCI2000
MIME-Version: 1.0
NNTP-Posting-Date: Thu, 18 Jun 1998 23:09:29 GMT
Newsgroups: fido.novell


Try using the 16 bit NW client disk set for win 3.x and set your context for a

direct BINDERY connection only!!!!    DOS 7.0 (WIN95) is Windows 95 just it
doesn't launch the GUI for windows.  The 32 bit NW clients all see DOS 7.0 as
real windows because it is!!!!  This causes all kinds of problems, varing
based on your configuration, from unable to connect to hung login files which
prevent some programs from running to total crash of the login directory.
most common is the Network bandwidth is totally absorbed by one workstation
while it tries to login and cause the Network to show constant collissions or
no other servers/clients on the bus.  We have allowed GAMES to be played
accross a 10/100 Mhz Ethernet 50 node network by using a DOS 7.0 boot disk and

NW client (16 bit) for WIN 3.x/dos made from the Netware CD to enable a
NETWORK Game of command and conquer RED ALERT on WIN95 machines in clean boot
dos mode.  Hope this works for you.....

Robert




sander wrote:

> Trying to connect a fat32/dos7.0 PC with netware 3.12.
> Running under dos NOT win95
> Doesn't work with current NWclient drivers, only work with dos 6.0 or 6.2.
>
> Sander

SOURCE: echoes via archive.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.