Newsgroups: bit.listserv.novell
Date:         Wed, 18 Nov 1992 12:06:50 -400
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Daniel Tran <DTRAN@EMELNITZ.UCLA.EDU>
Subject:      Re: Windows 3.0 + Netware 3.11

In article <NOVELL%92111100112886@SUVM.SYR.EDU> you write:
>Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
>Path:
 ucla-mic!unixg.ubc.ca!van-bc!zaphod.mps.ohio-state.edu!darwin.sura.net!paladin.
 american.edu!auvm!TWNMOE10.BITNET!GOVE036
>Message-ID: <NOVELL%92111100112886@SUVM.SYR.EDU>
>Newsgroups: bit.listserv.novell
>Date:         Wed, 11 Nov 1992 12:28:16 EST
>Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
>Sender:       NOVELERR@SUVM.SYR.EDU
>From:         Anne Liang <GOVE036@TWNMOE10.BITNET>
>Subject:      Windows 3.0 + Netware 3.11
>Lines: 52
>Hi, Novellers
>
>We are running Netware 3.11 and Windows 3.0 for chinese. Well, it runs
>OK on other machine except one with NE2000 NIC and ET3000 color monitor
>adapter. Here is the scenario:( After running IPX and NET5)
> 1. While not logged in,
>    (1) run WIN/R (real mode), it's OK.
>    (2) run WIN/S (standard mode), when exit, it shows
>       "Cannot run Windows in standard mode, check to ensure you are not
>        running other protected-mode software, or run in real mode."
>        I don't have to reboot the machine.
>    (3) run WIN/3 (Enhanced mode), when exit, it shows
>        "Network Error on Server DGBAS01: Error Sending on Network.
>         Abort, Retry?"
>         After answering "A"(Abort), there is another message:
>         "You are not connected to any file servers. The shell will try
>          to connect to a file server whenever the current default drive
>          is changed to an invalid drive."
>         Again I don't have to reboot the machine.
> 2. While logged in, I did not try (1) and (2) mentioned above. With (3)
>    after answering "A"(Abort) the message is simply "***Program Aborted***"
>    When I try to run WIN again, it shows "Shell Error: No filer server
>    attachments.", but it still run Windows in Enhanced mode.
>
>My configuration information is provided below, please give advices.
>Config.sys:   device=c:\win\himem.sys
>              device=c:\win\emm386.exe ram=e000-efff noems
>              ( I tried X=mmmm-nnnn but failed)
>              device=c:\win\smartdrv.exe /double_buffer
>              dos=high,umb
>              files=50
>              buffers=20
>              stacks=9,256
>
>Autoexec.bat: @echo off
>              prompt $p$g
>              set cc=et16
>              set shell=c:\command.com
>              set temp=c:\win\temp
>              lh c:\mouse\mouse
>              lh c:\dos50\doskey
>              lh c:\net\ipx
>              lh c:\net\net5
>              f:
>              login
>Hardware:  ROM BIOS: Phoenix dated 01/15/88
>           80386 AT machine, 80837 Math coprocessor, 8MB RAM, VGA adapter
>           100 MB HD, Adaptec SCSI controller, NE2000   , I/O address 300h
>           , IRQ 3, Vedio Address A000h
>
>If you need more information, please let me know. Thanks in advance.
>Anne Liang

Hi. I can see that you many questionable variables.
     1.  Are you using smartdrv.exe from Windows 3.1 ??  If so, where is
smartdrv.exe in your autoexec.bat.  Smartdrv.exe /double_buffer statement in
your config.sys alone does not provide disk caching.

     2.  You are using Windows 3.0 with Windows 3.1's smartdrv.exe ???
     3.  net5.com . is this netx.com renamed or did you run setver on a
previous version of net3.com or net4.com.
     4.  You are using IRQ 3 for your ne2000.  Do you have com2 port in your
machine??.  If so, this is a no no.  Use another IRQ (do not use IRQ 2,
Windows 3.0 does not behave well with IRQ2).
     5.  You load high all of your drivers in the autoexec.bat.  Are you
sure all of them are loaded high (I don't think so).  Use mem /c to check.
     6.  What mouse driver version are you using??.  If you're using
Microsoft mouse driver, put a /Y at the end.  I would use mouse.sys rather
than mouse.com.
     7.  The device=emm386.exe ram=e000-efff noems line in your config.sys
does not make sense.  The ram parameter provides both ems and UMB but the
noems parameter tell emm386.exe to provide ems.  The parameter you would use
is either RAM or NOEMS but not both at the same time.  Try this
     device=emm386.exe noems or
     device=emm386.exe x=b000-b8000 ram

     Your best choice is probably upgrade to Windows 3.1 and see what
happen.
Good Luck
Daniel - dtran@emelnitz.ucla.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU