Windows 95 Preview Program README.TXT (3 of 3)

PSS ID Number: Q129583 Article last modified on 08-22-1995

WINDOWS

The information in this article applies to:

- Microsoft Windows 95 Preview Program

SUMMARY

This article contains a copy of the information in the Windows 95 Preview Program README.TXT file.

NOTE: This file was split into three articles in the Microsoft Knowledge Base. This is the third article.

MORE INFORMATION

PRINTING

Network Printing

Printing over the network between a computer running this release (M8) to, or from, a computer running the previous release (M7) is not supported.

Installing printer drivers from servers with user level security

“Point and Print”, or trying to install printer drivers directly from servers, from servers with user level security is not functional in this release. However, this works fine from servers using share level security. This will be fixed in the next release.

Browsing for a Network Printer after installing M8

There are known problems with choosing the “Browse” button in the “Add Printer” wizard the first time after M8 is installed. The workaround is to not install a network printer the 1st time M8 is used, but to later start the “Add Printer” wizard from the printers folder. This will be corrected in the next release.

Using WordPerfect for Windows Printer Drivers

If you are using WordPerfect for Windows Printer drivers, and get an error message “Error initializing output device” when trying to print, you may work around this problem by doing the following. This will be corrected in the final release.

From the start button, choose “Settings”, and then select the Control Panel. Double click on the fonts folder.
Choose File/Install New Font.
Select your windowsdirectory in the directory selection labeled “folders” at the lower right side of the dialog box.
Now select the “Modern” font from the list & choose OK.
Restart your computer. After restarting, you should be able to print from WordPerfect for Windows using it’s own printer drivers without any problems.

NETWORKS

Client for NetWare: Opening files on NetWare 3.11 servers

Using certain applications, you may encounter problems opening files on NetWare 3.11 servers (3.11 only). Possible error messages could be: - file not found error on a file you know exists - sharing violation or lock violation error - unable to open file error - file in use error This may happen with applications that open a very large number of files in a consecutive fashion. This can also happen when opening a file in a directory for which you do not have file scan rights(ex. MS Mail shared post office). This only happens on NetWare 3.11 servers; please file a bug if you have problems opening files on other versions.

If you encounter this problem, there are two different ways to get around it. One is to obtain a patch (for 3.11 servers) from Novell which fixes this problem. It is available via ftp from ftp.novell.com; go to /pub/netware/nwos/nw311/osnlm and run 311ptd.exe. This exe will extract the file os2opnfx.nlm. Then, load this nlm on the 3.11 server. (“load os2opnfx.nlm”)

Alternatively, you can disable long file name support in the Client for NetWare. This means that you will not be able to use long file names on any NetWare servers from Windows 95. There are two ways to disable long file name support: (1)In your system.ini file, paste in the following two lines: [NWRedir] supportLFN=0 (2)Alternatively, run REGEDIT, navigate to HKEY_Local_Machine Create a new binary value whose name is supportLFN and whose value is 0.

ARCNET and Windows 95

You cannot use the IPX/SPX compatible protocol over an arcnet real mode (16 bit) NDIS2 driver. When connecting to Windows NT server or Windows for Workgroups using arcnet, make sure you have another protocol in common such as NetBEUI.

For NetWare connectivity using arcnet, you must install support for one of Novell’s real mode Network Clients. It is not possible to use the Client for Microsoft Networks if you use an arcnet ODI driver, or IPX monolithic.

Plug And Play Network Cards and 16-bit Real Mode Drivers

When you need to run the 16-bit real mode driver for your NIC (which is common if you use DLC or another real mode protocol), sometimes your PnP card may appear not to function. The reason for this is that on most computers, your PnP card remains inactive until Windows 95 turns on the card. 16-bit NIC drivers, load before Windows 95 has a chance to turn on PnP cards. Some 16-bit NIC drivers know nothing about PnP cards (most NE2000 PnP clones fall into this category), and this is where you would see a problem.

In order to use your PnP card with a 16-bit NIC driver: 1) Run the softset utility that comes with your PnP card, and set the card to non-PnP mode. 2) Remove the net card from the network control panel 3) Read the card using the Add New Hardware Control Panel applet.

When you move to a 32-bit protect mode NIC driver in the future, you may rerun softset to turn on PnP mode for your card.

Parallel Port Network Adapters

Any Network adapter that uses a Real Mode network driver and runs off your Parallel Port might have problems with this release of Windows 95. These problems will be fixed for final release. To use your parallel port adapter, disable the printer port within Device Manager. Run the System Control Panel Applet, select the Device Manager tab. Look for Ports, Printer Port. Find the printer port that corresponds to the port you are using for your adapter, and look at it’s properties. At the bottom of the page, uncheck any boxes (this disables the printer port). If you later want to print using this port, repeat these steps and check all these boxes.

Adapters that we know are affected include Xircom PE, PE2, and PE3 Pocket Ethernet Adapters. Your Xircom PE3 will continue to run properly with our Protect Mode 32-bit driver.

Novell/Eagle or National Semiconductor NE2000Plus

If you have an NE2000Plus netcard, you may have problems if you install the card as a Novell NE2000 Plus. You need to install the card as a “Novell NE2000 Compatible”, or as a “National Semiconductor NE2000Plus Infomover or compatible”. If your card does not work and your card is listed by Windows 95 as a “Novell NE2000 Plus”, remove the card through the Network control panel and read the card through the Add New Hardware control panel applet. This will detect the card as a “Novell NE2000 Compatible”, which will work properly.

Intel EtherExpress 16 NICs and PCI machines

You may experience system hangs or initialization problems if you are using an Intel EtherExpress 16 NIC in a PCI machine with some Diamond Speed Star PCI video cards. The following are excerpts from Intel’s Customer Support Database. These problems are not related to Windows 95, and happen on a variety of operating system platforms. In general, if you experience other problems with your EtherExpress 16 in a PCI machine, please attempt to replace the card before reporting the problem to Microsoft.

If you have one of these video cards, contact your vendor about getting a new video BIOS update.

Diamond Speed Star PCI video card with BIOS version 1.01
Diamond Viper PCI VGA Video Adapter
Diamond Stealth video card, BIOS v1.03

Windows for Workgroup shares

When you upgrade from Windows for Workgroups, it will not upgrade the folders/directories that you have shared. You will have to recreate them.

Drive connections to other servers will be migrated to Windows 95.

Running Windows 95 off a server

M8 allows you to run Windows over the network. The beta Windows 95 Resource Kit contains complete instructions in for installing Windows in this environment (see chapter 4, “Server Based Setup for Windows 95”).

There are a few limitations in this release:

The following configurations are supported: Booting from hard disk using: Client for Microsoft Networks Client for NetWare Networks Novell Workstation Shell 3.x (NETX) Novell Workstation Shell 4.x (VLM) Booting from a floppy disk using: Client for Microsoft Networks Client for NetWare Networks Booting from a remote boot server using: Client for NetWare Networks

To use one of the Microsoft clients, your network card must have an NDIS2 (16 bit) AND and NDIS3 (32 bit) driver.

Known bugs:

Shutdown does not get all the way to the final shutdown screen that says you can press CTRL+ALT+DEL to reboot. This makes it appear that the machine is hung. When shutting down these machines, wait for a few moments after disk activity has stopped, and then you may reboot or turn off the machine.

To boot from a remote boot server using the client for NetWare Networks, there are a few extra steps to follow:

Before running setup, edit the msbatch.inf on the server and add the following line to the [Network] section:

SaveSUBoot=1
Run setup as usual.
After running setup, go to the SUBOOT subdirectory of the home directory.
Edit the win.bat and switch the “nwrpltrm” and “set comspec” lines. (The “set comspec” line should be first)
Make a new boot image by going back to the home directory and running:

RPLIMAGE SUBOOT

(The RPLIMAGE can be found in the same directory as the NETSETUP program)
Copy the new NET$DOS.SYS file to your directory.

Near the end of setup, you will be prompted saying that setup cannot write to mapisvc.inf. This is just a harmless error. Just click Continue and let setup finish.

Exchange clients (MSN, Exchange mail, Route 66, FAX, etc) do not work on machines that boot over the net in this beta.

If you encounter problems during first boot of an EISA machine, try renaming EISA.VXD on the server to some other name (like EISA.BAK).

Always run SETUP from the root of the directory that NETSETUP creates. Do not run the SETUP program in the SUWIN directory.

TCP/IP & System Pauses

If you are using TCP/IP for WAN connections but it is bound to both LAN and PPP adapter but no DHCP server is present on the LAN, your system may pause for a couple of seconds every once in a while. To avoid this, unbind TCP/IP from your LAN adapter by bringing up properties of LAN adapter in the Net control panel and unchecking TCP/IP in the bindings property sheet.

FTP Software’s Win95 NFS client

FTP Software, Inc. has prepared a Windows 95 specific .INF for installing their fully integrated 32-bit NFS client for Win95, which can work simultaneously with other Windows 95 32-bit networking components.

This file can be obtained directly from FTP Software (see below). To install FTP NFS support:

Get the FTP NFS Windows 95 client software from FTP software.
Copy the file NETFTP.INF to the directory of your Windows 95 installation.
From the start menu, choose Settings, Control Panel, Network.
Press the Add button in the Network control panel, and add the FTP Software NFS Client for Windows 95.

To request a beta test application form for FTP Software’s 32-bit Win95 NFS Client, send an Electronic Mail message to: nfs95beta@ftp.com

Third Party Networks

Windows 95 detects certain real-mode networks at installation time and installs over them, leaving them running. You must be running your real-mode network when you run setup. Windows 95 does not support installation of a real-mode network after setup, unless you have a Windows 95 specific .INF file from your network vendor. Windows 95 does not include network component files for networks other than Microsoft networks. You must already have the files for the network.

PC-NFS

Windows 95 supports Versions 5.0 or greater of Sun PC-NFS. If Sun PC-NFS is installed using an NDIS 2 network adapter card or an ODI driver, then Sun PC-NFS can be installed as an additional 16-bit network client along side 32-bit protected mode clients. If you are using a Sun PC-NFS Lan Driver, Windows 95 can support PC-NFS as the primary network only. Additional 32-bit network providers are not possible in this case.

Banyan VINES

If Banyan drivers report that the VINES version is not the latest, edit the VINES.INI in the Windows directory so it contains the following lines: [NEWREV] dontcopy=1 vines.version=5.5x (x) USA ; where x=your version windows.version=3.95

DEC PATHWORKS

DEC PATHWORKS support involves running the Microsoft client over the DECNet protocol. To support this, Windows 95 requires some additional files and templates from DEC. These files are shipped as the PATHWORKS for WFW 3.11 patch disk. If you are running PATHWORKS and have not run the PATHWORKS for WFW 3.11 patch disk, you must first do so before installing Windows 95.

If you use DLLNDIS.EXE, you must use a version dated 10/06/93 or later to work with Windows 95.

Artisoft Lantastic

The Lantastic server cannot be run when Windows 95 is setting up.

There are known problems running MSCDEX and Lantastic. If you experience hanging problems or protection faults, remove MSCDEX.

Artisoft Lantastic, Beame and Whiteside BW-NFS 3.0

You cannot run any of these two networks along with a second network. With other supported third-party networks, you can run any Windows 95 32-bit networking components at the same time.

Printing to network printer

Setting up for a printer that is shared via a 3rd party server may fail. The workaround is to redirect lpt1: through a MS-DOS window (command prompt) to the 3rd party share, then use printer setup for lpt1. For example, if a network printer is connected to “lpt1:” type: “net use lpt1: \servername” at a DOS command prompt (this command depends on the network you are using; please consult the product documentation to find out how to redirect a LPT port). Then use printer setup in the Control Panel. Alternatively, you can try selecting the printer from the printer folder, choose “Map Printer Port” from the “File” menu, and select the redirection for the dialog that is displayed.

Issues and Installation of MSDLC with Windows 95

MS-DLC does not currently ship with Windows 95. It is available to customers via MSDL Microsoft Download Service, CompuServe and other distribution methods as it was for WFW3.11.

Setup Issues: To install the Real Mode MS-DLC stack, you need to have a copy of MSDLC.EXE and NETDLC.INF. These are the only files necessary and both can be found on CompuServe, or contact your beta support team or your local subsidiary as appropriate. On Compuserve the file is named DLC16.ZIP.

To install: a. After installing Windows 95, copy NETDLC.INF into the directory and copy MSDLC.EXE into the Windows directory. b. In the configuration tab of the net control panel click Add/Protocol/Microsoft/Microsoft DLC then click OK. c. Restart machine and MS-DLC should now be installed A minimum example of the AUTOEXEC.BAT with MS-DLC looks like this: c:initialize c:.exe c:start

The net initialize command must come before the MSDLC.EXE line, which must come before the net start command.

Upgrades: * If after upgrading a machine that had MS-DLC installed, you encounter problems, remove any NET INIT AND MSDLC.EXE commands from AUTOEXEC.BAT. Then repeat the install procedure above.

If you install MS-DLC after installation of Windows 95, check to make sure there is only one NET START command in AUTOEXEC.BAT before installing MS-DLC.

Install issue: The default parameter settings for MS-DLC under the advanced properties are configured for Token Ring connectivity. You may have to modify the ‘swap’ and ‘usedix’ parameters for use for ethernet networks. Consult the prior protocol.ini ms-dlc section for similar settings or consult the DXME0MOD.SYS line in CONFIG.SYS for the corresponding parameter settings.

If you receive the error message, “Protocol.ini. Keyword is not recognized” when msdlc.exe executes, edit the PROTOCOL.INI and remove the lanabase entry under the [msdlc] section.

IBM’s Lan Support Program: IBM’s real mode DLC protocol is called the IBM Lan Support Program. It uses drivers that load in CONFIG.SYS typically as follows: c:0MOD.SYS c:0MOD.SYS (A token ring setup)

Windows 95 must be configured with NetWare ODI to use the LAN Support Program

If used with NetWare, the CONFIG.SYS is the same as above, but the AUTOEXEC.BAT looks like the following: lsl lansup ipxodi netx (or vlm)

If you do not have this configuration in place, but are running DLC on token ring, we recommend using the MS 32 bit client components of Windows 95 and replacing ipxodi and netx(or vlm). Windows 95 will replace the two files with odihlp.exe. Example AUTOEXEC.BAT below:

lsl lansup odihlp.exe

If the IBM Lan Support Program is using the DXME0MOD.SYS driver in CONFIG.SYS, it is then configured for its NDIS implementation. See example below: Sample CONFIG.SYS: C:.DOS /I:C:
C:.DOS C:0MOD.SYS C:0MOD.SYS

In this configuration, it is best to remove the drivers from the CONFIG.SYS and configure Windows 95 to use the Microsoft DLC stack instead.

Novell NetWare Login Scripts

The Login Script Processor for the Microsoft Client for NetWare should correctly process all commands in your login scripts, except that you cannot load TSRs in these scripts. If you find that any line(s) in your login scripts are not being executed correctly, make sure to file a bug report, and include your login scripts in the report.

Microsoft TCP/IP Protocol

If Microsoft’s TCP/IP is the only protocol you have loaded on your system, the IP Address will not be added during Setup. If you have a DHCP server, just open the Net Control Panel Applet and then close it; this will update the IP Address. Otherwise, open the Net Control Panel Applet, bring up properties on TCP/IP and manually enter your IP Address.

On a clean install, to use DNS or LMHOSTS name resolution, make sure you have DNS enabled in the network control panel. Earlier Windows 95 versions (pre 337) stored DNS information in the SYSTEM.INI file. This version stores the info in the registry. When doing DNS lookups, the subsytem will check both the registry and SYSTEM.INI for DNS information. A side effect of this is that DNS lookups will be enabled even if the TCP/IP setup UI does not show any DNS hosts or DNS disabled. To fix this, delete the DNS section in your SYSTEM.INI after copying the relevant info to the TCP/IP setup UI.

When upgrading a Windows For Workgroups PC with the Microsoft TCP/IP protocol, Windows 95 detects the TCP/IP stack and installs the Windows 95 version, but it will not preserve your WFW settings. To restore the settings, open the TCP/IP property sheet from the Network Control panel.

Dial-Up Networking

Connecting to the Internet with Dial-Up Networking? Then be sure to download latest Inet.zip from your CompuServe forum, or contact your beta support team or your local subsidiary as appropriate. It contains all the latest instructions for smooth connections to Internet/PPP servers.

We have some reports of interoperability problems when connecting with PPP accounts Internet Service Providers. These problems can be overcome if you turn off IP header compression. To do so, open the Dial-Up adapter property sheet (from Network Control Panel) to the Advanced TAB, and set the “Use IP Header Compression” value to no.

User Profiles Over the Network

If you are using user profiles over a Windows NT or Novell NetWare network, and you choose to include Start Menu/Programs, Network Neighborhood, and/or Desktop Icons in your profile, then you must have Long File Name support on the server in order for these parts of the user profile to follow you around the network.

Arcada Backup Exec network backup agent

In order to use the Arcada Backup Exec network backup agent included in Windows 95, you must have Arcada Backup Exec version 5.X.

Cheyenne ARCserve network backup agent

In order to use the Cheyenne ARCserve network backup agent included in Windows 95, you must have Cheyenne ARCserve version 5.01F. You may also use earlier versions of 5.01 if you obtain updated NLM’s from Cheyenne Software.

Troubleshooting Networks

Netcard Driver Problems Change the driver type of the card in control panel networks from enhanced mode(32bit and 16bit) NDIS to real mode 16bit NDIS driver. If this fixes the problem please file a bug report indicating the model of the netcard and it’s settings(irq, io, ram, eisa, pci, etc…) Also include what driver is showing up in netsetup exactly.

Browsing problems If you suspect browsing problems make sure that MS File and Print Sharing is installed in control panel, networks. This is not installed by default, only on a upgrade that has it already installed.

WINDOWS 95 PEN SERVICES

Release notes for Windows 95 Pen Services

Installation of the Pen Services has been removed from the base Windows 95 setup procedure. The setup procedure below assumes you have already installed Windows 95. If your pen hardware does not appear in the list below, please contact the manufacturer for the appropriate Windows 95 pen driver before proceeding.

To install this beta of Windows 95 Pen Services:

From the Start menu select Settings, then Control Panel, then Add/Remove Programs.
From the Add/Remove Programs Properties sheet, select the Windows Setup tab, and click the Have Disk button. Browse until you can select the PENWIN.INF file and click OK. The PENWIN.INF should be found in the directory on your installation CD.
In the Have Disk dialog optional components list box, check the box next to “Pen Services for Windows 95” and then click Install.
When the Add/Remove Programs Properties sheet is redisplayed, click OK. When you are prompted to restart your computer, click Yes.
After Windows 95 restarts, the Pen Driver Configuration dialog will appear. The five digitizers supported by the sample pen driver you have just installed are displayed:
- Wacom Technologies Digitizer Model SD-510C
- Wacom Technologies Digitizer Model HD-648A
- Wacom Technologies Digitizer Model UD-0608-R
- Grid 2260
- Compaq Concerto Select the digitizer you are using from the list and, if necessary, select a COM port and whether or not your stylus is pressure-sensitive. Then click OK.
When you are prompted to exit and restart your computer, use the Start menu to restart Windows 95 instead of turning off the machine or using Ctl-Alt-Del. This will allow Windows 95 to finish loading properly. Do not try to use the pen in this intermediate stage since the pen driver will not yet be configured.

Some video driver and video resolution combinations have not been tested for compatibility with the Pen Services inking scheme. Please report any inking problems found.

KBCategory: kbreadme kbsetup KBSubcategory: wpp95 win95 Additional reference words: 95

Microsoft KB Archive/129583

Contents