BROOKER@MCOIARC.BITNET (MEDICAL COLLEGE OF OHIO) (01/10/90)
>Hoping someone out there has or knows of a patch that will fix a >problem with Windows/386 and Novell 2.15a > >When using the MS-DOS Executive window, and trying to copy files >to/from the server (drive F:), the files always arrive as zero-length. > However, if I use the command interpreter and the COPY command, all >works fine. Is this a Windows/386 bug, or a bad interaction between >it and the NET3 shell? Oh, by the way, we use IBM DOS 3.30, PS2 Model >70, and 3Com EtherLink cards. > >Which brings up another problem. If the EtherLink card's shared >memory address is setup to other than C0000, my connection to the LAN >goes awry after leaving WIN386. Is Windows using that memory as >swapping space? Is there a way to control or restrict what portions >of memory WIN386 will use as swapping space? If I set the card to >C0000, it again is fine. I would like more flexibility and control >over the setup than this currently allows. > >Thanks in advance > Gary Dobbins, University of Arizona > bitnet: DOBBINS@ARIZRVAX Gary: After much trial and error on our ethernet network trying to get Windows 386 working, I have given up. We are using Compaq 386/20e's here and are finding that there just isn't enough continuous RAM, anywhere in memory to load the complete Windows 386 program. It seems that Windows 386 needs 2 contiguous blocks of 64K memory, inorder for it to load completely, (and it supposedly goes out & looks for these itself). There are a parameters you can use to tell it to skip over certain areas, however, they did not work for me. On my network, the problems occurred when I tried to utilize expanded memory in any of my windows, apparently, the Windows 386 program would load fine, however, it would not load it's exp. memory manager which feeds windows with expanded memory. Pc's would also periodically lock up, especially with several windows up. After talking to Microsoft tech support, they basically said, "to bad, Windows 386 was not made for network use" and that was the end of their discussion. Sounds like you are in the same boat. I would recomend reconfiguring your ethernet drivers for the smallest mode they will go into, usually this is a 32K buffer mode, and see if Windows will load. You definitly have a memory configuration problem if you loose your network connection after running Windows 386. Sounds like you are loading Windows, and it is overwriting the same area as your net drivers. There is a command to try to load windows, after certain memory address, and it goes in the WIN.INI file (I don't remember the command, call tech support). Also, if you do get Windows to run, or just want to use w/o the net., there is a great product you should look into, it is call Command Post for Windows 386. It allows you to add drop down menus, which you can use to launch appl'ns., etc., and the overhead is very small. It makes running appl'ns. a breeze under Windows 386, I recomend it very strongly. It only costs $50, and it sold by Wilson WindowWare, 3377 59Th SW, Seattle, WA 98116. I did see a blurb about Windows ver 3.0, which is supposed to be more friendly to networks, I am waiting for it to be released, later this month (supposedly). Good luck. Jeff Brooker Medical College of Ohio