Q. NETWARE AND WINDOWS 95
Q.1 Booting Windows 95 from NetWare on a disk-less workstation
Joe D. and his team have succeeded in getting Windows 95 to boot-up on hard disk-less workstations connected to NetWare. A document summarizing their efforts is at:
ftp://netlab2.usu.edu/misc/win95boo.txt
For Netscapers:
[Thx Joe D.]
The following is excerpted from a recent post by Joe D.:
Win95 is DIFFERENT. With few exceptions you will need to reinstall all Windows programs from scratch. One exception seems to be Quattro Pro for Windows, where it is finally self contained enough to be run with a single pointer ("shortcut" in Win95-speak).
I *strongly* recommend printing and reading the Win95 Resource Kit.
You may also glean hints from reading win95boo.txt (mentioned in Q.1)
Without doing lots of homework it is foolish to convert a production server to use Win95.
To run VLMs you need autoexec.bat, and to do decent memory management and other normal tasks then config.sys is used too.
My people have created a Win95 production delivery system on a production NW 3.12 server, and we've doubled the number of application directories (one for Win 3.1, one for Win 4.0). Each is booted differently at this time. We can use VLMs provided we don't use Ethernet boot ROMs, but if those ROMs are used then we must fall back to NETX.EXE. The problem is in Win95.
We use QEMM/386 for memory management, but some machines don't work properly unless DOS memory management is used; beware. Long name support is NOT present unless one uses Microsoft's NW client, and I have no desire to do that. Long name support will cost your server quite a bit of memory and performance, to cache directories and to pay the penalty of each directory cache block holding only half as many files as without the extra OS2 namespace.
The load stream across the wire for Win95 runs to about 7.5MB here, so be prepared for additional network traffic.
Printing works at both GUI and DOS box levels (to queue, via Capture in login script, respectively), but it is not yet gotcha-free.
[Thx Joe D.]
Update: -------
>What did [Joe D.] do to get Win95 working WELL on diskless workstations? How much RAM on the workstations, any swap files on the server, what applications are you running with it??
Clients are going to 32MB, up from 16MB, and of that 9MB is allocated as a C: RAM drive. I need 9MB to handle certain situations, but I need a RAM drive to service local storage requirements (read-only file server). Windows swap file is on C: as well so basically all of memory is available to Windows.
Just about everything works under Win95. MS Office, WordPerfect for Windows and DOS (DOS 6.0b must run full screen), Borland C++ 4.5, Autocad, Quattro for Windows, MS C compilers, engineering programs, etc. Quattro Pro 5 for DOS does NOT, however, and does not run out of a DOS box on any version of Windows.
I do not run MS Access data base, so I am free of those horrid locking problems.
Clients are going to Pentium 90's, up from 486-33's. But the 486 machines do run Win95 ok, within their memory constraints. 16MB is just too small to run Excel and something else, limiting cut and paste operations. 32MB is about right for this year, until the Win95 versions of packages chew up more, as expected.
All Ethernet. The traffic gets a bit hectic but the NE-2000 clone boards in clients work fine, and a pair of NE-3200's in the NW 3.12 server take the load and still manage to get plenty of sleep. Two runs of coax in this particular student lab.
Printing is not quite perfect for Win95, yet. WordPerfect objects to the spelling of a print queue on the first go, but accepts it on the second try. Within Windows we print to NW queues, and CAPTURE still operates fine in the DOS boxen (Capture is run in the login script). VLM shells on machines, even though some test Pentium machines had sufficient trouble with their memory that we had to retreat to NETX and DOS mem management for them.
We have discovered that a number of packages can be invoked ok from Win95 by creating the proper shortcuts. Some can be reinstalled to get .dlls etc. into Win95, and then the guts removed to save disk space; editing the Registry is needed to point to the directory used for regular Win 3.1 operation. Yes, we decided to run both Win 3.1 and Win95 for several months until customers voice a firm choice. In any case, not every package needs a Win95 installation but the vast majority will require significant work.
Overall, Win95 seems to be about as stable and usable as Win 3.1. Finding anything on the green screen is nearly impossible until one clutters the desktop with shortcut icons, and then it's like Win 3.1 but with pretty pictures rather than square icons. Your tastes may vary.
We decided to trash long name [LFN] support. That helps the file server a lot. LFN support works only with MS shell components at present, and in the end we found it to be nearly worthless. Yes, next year or two it will be the rage to create filenames miles long with spaces, but all programmers will have white hair from parsing such things.
You can give all this a test drive at the end of the week. Be sure to thoroughly backup your system manager's DOS workstation because Win95 will eat its hard disk. Installing Win95 onto a file server for shared access requires installation to be executed on a workstation, as folks will discover.
Be sure to turn off all peer to peer work over IPX. That item has a very nasty problem of making a Win95 station masquerade as a NW file server, and users seeing it can be trapped in a black hole. See my comments in the trade press on this snafu.
[Thx Joe D.]
Q.3 The NetWare Requestor for Windows 95
The Windows 95 requester for Netware is available for free download. See section S.43 for more up to date information.
The drill is to install Win95 on a workstation, and then use NETSETUP to install the shared image on a file server; the program runs only under Win95. I again refer folks to classical doc win95boo.txt for further hints; dir misc on netlab2.usu.edu.
ftp://netlab2.usu.edu/misc/win95boo.txt Netscapers: ftp://netlab2.usu.edu/sys/anonftp/misc/win95boo.txt
[Thx Joe D.]
The diskette version DOES NOT come with a network installer, you will need the CD-ROM version for this.
[Thanks to Fred Salerno for this info]
Q.5 Long filename install workarounds
MS Office 95 is being very difficult about being installed on a NetWare 3.12 server without long (OS2) filename support. Hint: try executing SETUP.EXE /F where undoc'd /F means without long filename support. I'll get there eventually, I hope, but right now MS is winning the struggle.
MS docs: "make sure the long file name feature of Windows 95 is turned on by setting the following entry in the Windows 95 system.ini file:
[nwredir] SupportLFN=2"
[Thx Joe D.]
Q.6 Crippled MS NetWare Requestor stack
"When you do talk with MS, discover the well known fact that their stack does not support Bootp. It has a crippled rendition of DHCP.
Good luck, Joe D."
[Thx Joe D.]
Q.7 NetWare 4.x NDS and Windows 95
I need Microsoft's MAPLE product. I can not get my Windows 95 machine to utilize NDS. I can't run NWADMIN, therefore, I'm dead in the water.
The latest Client32 and IntranetWare Client can be downloaded from:
Microsoft's Win95 Page:
32bit.com Win95 Software Archive!
Dylan Greene's Win95 Page!
Dylan Greene's Windows95 Page!
A Ross Keele - Univ. of Sask
Process' Win95 Page!
PC World's Here's How/Win95
Stroud's Consumate Winsock Apps Win95 Page
WWW VMS Win95 Page
Windows Rag
Windows NT and Windows 95
The One-Stop Windows 95 Site
Windows 95 Resources
[Thx F.P.M.]
Q.9 Telling Windows 95 to back-off!
>It seems that for WIN95 to see the real mode NIC driver, the IRQ has to be less than IRQ 9.
Go into Win95, SYSTEM icon and tell it certain hardware resources are excluded from consideration. IRQs and Ports are on this list. IRQ 2/9 is grabbed by Win95 unless you slap its hands. Once that matter is understood by the green screen beast all is well. I happen to run Ethernet boards on IRQ 2/9, VLM redirector with boot roms, and do so happily after the above treatment.
[Thx Joe D.]
Q.10 Let's be clear...this is a _NOVELL_ list
Let's be clear about what I[/NOVELL] can contribute to the discussion [of Win 95 server installs, etc.], and where you plus your Win95 Resource Kit plus Microsoft's Tech Support have to take over.
I specifically dealt with a READ-ONLY file server, with clients having NO HARD DISK but with a RAM drive C:. In the examples in my doc the user directory was named \win95\user. The examples discuss what's particular to a user in that area, and you should pay attention to what's are MS "registry" files. You can create as many users as you wish, each with individual accounts located anywhere you wish, and they contain material similar to what I showed (but you can trim away great hunks after you have things settled down). May I repeat, learn what's in the registry files, because they hold the user and machine-specific information.
I did not discuss Windows 3.x, nor NT 3.x since folks know how to handle the former and I don't want to spend more of my time on the latter (yes, I have both). I did not discuss having a local hard disk and storing Win95 on a server, though my notes basically cover that arrangement by implication. I did not discuss booting multiple operating systems, though personally I boot amongst DOS 6, Win95, OS/2 and NT on my desktop.
I apologize for the notes being less than crystal clear and in strict order and free of omissions. I have updated material with clarifications and amplifications based on a second pass at installation, and I hope that the combination will be sufficient to launch folks along the twisty narrow safe pathway through this minefield.
With the benefit of hindsight I can say that one needs to rethink arrangements when installing Win95. It is not an application invoked and exited at will, sigh. Many (most?) Windows applications will need to be reinstalled, but cleverness on your part can permit one final installation to service both Win 3 and 4 (as we do at my place). DOS applications will still run, but you will find creating "shortcuts" (icons with .PIF files) the convenient way of dealing with many. First thing: create a DOS icon as a shortcut to command "command.com." And, Plug&Play is your biggest enemy to installation, so keep at it time after time after time until you succeed.
I have discarded Microsoft's networking material and in my lab we run ordinary VLMs. They work fine, thankyouverymuch, to the NW 3.12 file server. Novell has said at Brainshare[95] this spring, and the trade press has speculated, that NDS logins will be available real soon now (tm). Yesterday's press release said basically the same thing. There are good reasons to believe these statements.
I put the discussion on this list only because of the NetWare server and client shell aspects. Beyond that the problems should go straight to Microsoft or one of the Windows NEWS groups/listservers, not to this listserver.
[Thx Joe D.]
Q.11 The best version of the Windows 95 Help File is...
ftp://ftp.inmagic.com/pub0/k/kenbo/ or ftp://tecfa.unige.ch/pub/software/win95/updates/helpfile/
There's also a great Win95 Registry FAQ which can be downloaded from:
http://www6.zdnet.com/cgi-bin/texis/swlib/hotfiles/info.html?fcode=000BD3
[Thx S.R.#2]
Q.12 Integrating the Netware Client 4 DOS/Windows (VLMs) with Windows 95
Soon Novell will release a public beta of their Win95 32-bit client requestor, but until then here is what you can try...
This [info] contains the instructions to integrate the NetWare Client for DOS\MS Windows (VLMs) v1.2x with Windows 95. This solution is temporary. Novell will release a 32-bit client for Windows 95 later this year (1995). When the 32-bit client is released, it will be the recommended client for Windows 95.
This [info] provides step-by-step instructions to integrate the VLMs with Windows 95. It is assumed that you are running the 1.20 VLMs or later. The 1.20 VLMs are the VLMs that ship with NetWare 4.10. If you do not have the 1.20 VLMs, they can be downloaded from CompuServe. The updated VLMs are in VLMUP3.EXE in the NovFiles Forum. The entire client kit can be downloaded from NovFiles. There are 6 files that make up the client kit. The files are named VLMKTx.EXE (the x ranges from 1 to 6). This client kit already has the updates from VLMUP3.EXE applied.
Detailed step-by-step instructions are provided on the following pages. Here is a brief overview of the installation/configuration process for installing the VLMs on a new Windows 95 machine, and upgrading an existing Windows machine on which the VLMs were already installed.
Overview of installing the VLMs on a new Windows 95 workstation. (Follow all steps in the detailed instructions beginning with step 1.)
1. Remove all network components from Network Control Panel in Windows 95 2. Reboot machine in MS DOS mode. 3. Install NetWare Client for DOS/MS Windows. 4. Reboot machine and add the Novell NetWare (Workstation Shell 4.0 and above [VLM] client in the Network Control Panel in Windows 95.
Overview of the configuration steps for configuring Windows 95 to run with the VLMs after upgrading an existing Windows workstation that was configured for the VLMs. (Follow all steps in the detailed instructions beginning with step 8).
1. Perform the upgrade to Windows 95 with the VLM client loaded. 2. After completing the Windows 95 upgrade, open the Network Control Panel. If the client listed is Novell NetWare (Workstation Shell 4.0 and above [VLM]) you are finished. 3. If the above client is not installed, remove all network components and select Novell NetWare (Workstation Shell 4.0 and above [VLM]).
Q.12.2 Some FAQs on integrating NetWare Client kit (VLMs) with Windows 95
Q. When will Novell's 32-bit client solution for Windows 95 be released? A. Novell's 32-bit client solution for Windows 95 will be called NetWare Client32 for Windows 95. It will be released 60-90 days after Windows 95 ships.
Q. How do I login to a NetWare server from a Windows 95 workstation? A. When using the VLMs, if you want a login script to be executed you must login from a DOS prompt. To do this, execute login.exe from the autoexec.bat or winstart.bat after the VLMs have loaded. The NetWare Client32 for Windows 95 will ship with a Graphical login that will enable users to login from the Windows GUI interface.
Q. Are Network Neighborhood and Windows Explorer functional with the VLMs? A. Yes. You can use Network Neighborhood and Windows Explorer to navigate through bindery servers. There is no NDS support within Network Neighborhood or Windows Explorer. The NetWare Client32 for Windows 95 will be fully integrated with Network Neighborhood and Windows Explorer. NWUser will provide you with a GUI interface into NDS servers.
Q. Can I use NWUser on a Windows 95 workstation? A. Yes. You can use NWUser to map drives, capture ports, etc. However, the permanent connection features do not work with Windows 95. You should use login scripts to establish your workstations default network environment (mappings, captures).
Q. How do I capture from Windows 95? A. You can execute capture.exe from a login script or in a DOS box. NWUSER can also be used to capture a port. Add Printer Wizard can be used to attach to bindery based print queues or NDS queues in the bindery context.
Q.12.3 Detailed Step-by-Step Installation/Configuration Instructions
1. Launch Windows 95 and open My Computer
2. Open Control Panel.
3. Open Network.
4. If there are any network components in the Network Configuration property sheet, remove them. This is accomplished by highlighting a component and clicking Remove. If there are no network components installed, skip to step 5.
Windows 95 will make the required modifications and display a dialog: Enter No.
5. The workstation now must be rebooted in MS-DOS mode so the VLM client install can be run.. Click on Start, Shut Down. Click Restart the computer in MS-DOS mode? and click Yes.
6. At the DOS prompt insert the NetWare Client for DOS/MS Windows diskette #1, change to A: and enter Install. Enter the required information in the NetWare Client Installation screen.
7. When the NetWare Client for DOS/MS Windows installation is complete, reboot the machine. The following series of error messages may be displayed when Windows 95 loads.
Cannot find a device file that may be needed to run Windows or a Windows application.
The Windows registry or system.ini file refers to this device file, but the device file no longer exists.
If you deleted this file on purpose try uninstalling the associated application using its uninstall or setup program.
If you still want to use the application associated with this device file try reinstalling that application to replace the missing file.
C:\windows\system\vmm32\vnetbios.vxd. Press a key to continue.
If these errors occur, press any key to continue. The next step is to configure Windows 95 to run with the VLMs. Once Windows 95 is configured to run with the VLMs, the errors will no longer occur.
8. Once Windows 95 has loaded, open My Computer, Control Panel, Network once again.
9. The Network Control Panel should not have any network components installed. If there are network components installed, remove them.
10. Click Add
11. Click Client
12. Click on Novell. You will see two options under Network Clients.
13. Click Novell NetWare (Workstation Shell 4.0 and above [VLM]), then click OK.
14. Click on the Identification tab. You must type in names for your computer and the workgroup it will appear in. You must also type in a short description of your computer.
15. Click OK.
While Windows 95 is being configured you may receive dialog boxes asking for you to insert a disk. If you are displayed a screen such as this click OK.
These files were installed when you installed the NetWare client for DOS/MS Windows. If the dialog states "The file filename' on Novell Netware 4.x Windows driver disk could not be found.", enter the path c:\windows\system directory in the "Copy files from:" box and click OK. If the dialog states "The file filename' on Novell Netware DOS driver disk could not be found.", enter the path c:\nwclient in the "Copy files from:" box and click OK.
A dialog will be displayed when the configuration process is complete: Click No. There is one more step that needs to be performed.
16. Open a DOS box, and modify the c:\nwclient\startnet.bat or autoexec.bat to include the following commands:
F:login (servername\username is optional)
When you reboot the workstation you will be prompted to login while Windows 95 is initializing.
In some cases, Windows 95 will insert lines in the autoexec.bat to load the Novell ODI drivers even though the client is already being loaded from another batch file such as the startnet.bat. Check your autoexec.bat and verify that the ODI drivers are not being loaded twice.
17. Reboot the machine. Click Start, Shut Down. Then click Restart the computer and click Yes.
18. The machine will reboot. You will be prompted to login from a DOS/text screen while Windows 95 is initializing.
For more information on NetWare Windows 95 client issues with, check the following URL:
http://support.novell.com/products
Select the link to intraNetWare Client 2.12 for Windows 95
Q.13 Windows 95 + SAPs .NE. NetWare file server !!!
Do not let Microsoft products advertize themselves via IPX SAPs because in the case of print/file sharing they appear to be real NetWare file servers (but are not). At my place it is a formal crime against the network to do so, and we retaliate formally. There's nothing behind that facade of "I'm a server, come to my place", and further it says it's one hop closer to the wire than anyone else. Thus clients starting up get that Win95 monster and the consequent black hole.
If they must share, then use NetBEUI (not routable) or RFC-NetBIOS (routable).
[Thx Joe D.]
Q.14 Is there any way to check the version of Client32 for Win95?
Type MODULES at the DOS prompt and see what version of CLIENT32.NLM is loaded.
[Thanks Peter Burtt]
Last updated: 28 April 1998 - JEL