SETTING WINDOWS UP FOR NETWARE 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 Here is a Guide to get windows working with a Novell network getting it to run off a novell network is a different story!. The following is what worked for me with NO help from the "Windows Installation Guide" (Makes a good door stop!), It might not work for everybody but it should be a good start. You Must use IPX ver 3.01 Rev B or better, and NETx Ver 3.01 Rev x. If you are using any Lan card that requires to use Irq 2 then you will have to change this and Windows gets upset with this On an IBM token ring card put switch 8 up (Off) to fix this problem. The fix from novell to solve this problem seem's to cause more problems later on! Make sure you have a ordinary config.sys and have NO EMS or XMS driver resident in memory, Load IPX and NETx (Do-Not Use LANSPACE,EMSNETx or XMSNETx). If you didn't load ipx and the shell then remember to pick the network type in the installation screen of windows as windows will not see the network so it will not automatically load the drivers. Install Windows as per the windows manual, Next you will need to change the SYSTEM.INI file in the windows directory. Use any ASCII type editor, first look under the heading:- [boot.description] network.drv=Novell Netware 2.10 or above, or Novell Netware 386 ensure that the above line is contained in this area. Next look under the heading:- [386Enh] emmexclude=d800-dbff - this is the address used by a IBM Token ring card {Actual D8000-DBFF0} You must enter your cards own Address ebios=*ebios display=*vddvga keyboard=*vkd mouse=*vmd network=*vnetbios, vnetware.386, vipx.386 device=*vpicd - Novells bug fix vpicda seems to stuff up when using xms. Once you have saved the above then you can re start windows and use the lan at the same time. Memory and Windows. Windows dose some very weird thing with memory, you will find that very few non-windows applications will work because of the base memory left free, usually about 430kb. If you try and use programs like lanspace,386max or any other program that loads the shell high then windows will crack the sads and crash, I won't go into the exact nitty gritty of how all this memory cram is resolved but here is a solution that I worked out using Quarterdecks QEMM386.SYS device driver and EMSNET4.EXE. {QEMM Ver 5.11} Here is a example Config.sys:- DEVICE=C:\QEMM386.SYS RAM ARAM=D800-DBFF FILES=30 BUFFERS=20 DEVICE=C:\LOADHI.SYS /R:5 DXMA0MOD.SYS DEVICE=C:\LOADHI.SYS /R:1 DXMC0MOD.SYS 400010000001 SHELL=C:\COMMAND.COM /p /e:1024 DEVICE=C:\WINDOWS\MOUSE.SYS /Y LASTDRIVE=K: The first line is the actual qemm device driver, the RAM command is to Allow use of ram 640k-1024 for XMS, etc, the ARAM part is important to stop the use of memory at the same point as your lan adaptor card(s). Loadhi.sys is used to load any device drivers into hi ram (XMS) although Some mouse drivers will not work 100% if loaded into Hi-ram so try and see. Once windows has installed itself it uses smartdrive.sys and himem.sys, delete the lines containing them as qemm386 acts the same as himem.sys anyway and smartdrive gets upset on some machines when using qemm386. You will have to edit SYSTEM.INI file in the windows directory for some more changes, Under the heading :- [386Enh] emmexclude=d800-dbff {see page #1} emmexclude=a000-dfff IgnoreInstalledEmm=True Add the second and third lines to the file then save it. The second line emmexclude=a000-dfff (actual A0000-DFFFFh) Instructs windows not to use memory in the 640-896K range as we use it later. The third line IgnoreInstalledEmm=True instructs windows not to install its own EMS emulator and to use qemm386 instead. Memory and Windows [Cont] After re-setting the machine and the drivers have been loaded then here's one way of loading the lan software using quaterdecks loadhi.com :- loadhi /b ipx emsnet4 If you are using a 3270 or 5250 emulator that uses ipx/spx then you can also load TBMI high by using loadhi /b tbmi . **TBMI.COM and TASKID.COM are required if you intend to use a 3270 or 5250 emulation that requires ipx/spx under windows, Novell also requires that you remove the vipx.386 line from Network=*vnetbios, vnetware.386 line in the system.ini file I found that it can cause errors when loading windows and that leaving it in seems not to affect anything. Login in to the lan then execute windows. I have no doubt that there are much better ways of doing this but this way dose work. *NOTE:- The above has been tested on 386's with Chip & Technologies and VLSI Chip sets and on several 486 machines with 4MB or greater and had no problems, But I had troubles with a 386 with a OPTI chipset using windows and QEMM. To fix this change config.sys to read:- Device=c:\himem.sys (windows own EMS) Device=c:\QEMM386.SYS RAM ARAM=D800-DBFF MEM=2560 NOXMS This will enable windows own XMS manager, you can still use loadhi for both drivers and IPX etc. Hope this Information Is Of Some help, If anyone Knows any better ways of doing the above please let me and everyone else know. Regards. Steve Ruston, Melbourne, Australia.