(13 October 1995, Rev 34)

Tested Hardware

Equipment tested includes the following system hardware;-

• Apricot EPx P60 (M5)
• Apricot FT//e 486 DX2/66 (Panther 2)
• Apricot FT//ex 1000 (M5 Pentium 60 w/128Mb RAM)
• Apricot LS Pro 486 SX25 and 486 SLC33 (Bonsai)
• Apricot LS PRO DX4/100 and DX2/66 (Caracal)
• Apricot Qi 386 DX/25 (Qi 600 series)
• Apricot Qi 486 DX2/66 (Panther 1)
• Apricot Qi 900 486 DX2/50 (Scorpion)
• Apricot XEN-PC 486 DX2/66 (Acer A1 and P2)
• Apricot XEN-PC 575 (Jade)
• Apricot XEN-PC 590 (Jade)
• Apricot XEN-PCls 5120 (Jade)
• Apricot XEN-PCls 560 (Revenge)
• Apricot XEN-PCls 575 (Jade)
• Apricot XEN-PCls 590 (Jade)
• Apricot XEN-PCm 486 DX2/66 (Acer A1)
• Apricot XEN-PCm 560 (Revenge)
• Apricot XEN-PCm 560 (Ruby)
• Apricot XEN-LS II DX2/66 and DX4/100 (Samurai Rev F)
• IBM ThinkPad 755CE LapTop (used for compatibility testing)
• Toshiba T-2150CDT LapTop (used for compatibility and Shogun SMA testing)

Within the Apricot systems, additional hardware tested includes the following;-

• 3COM 3C503, 3C509, 3C523, 3C529, 3C579 and 3C595 Network cards,
• Adaptec 1510 and 1640 SCSI cards,
• Apricot PC-Online Internal 14400 Fax-Modem,
• BusLogic BT-646S SCSI card,
• Creative Labs SB16, SB16 SCSI and SB16 Vibra sound cards,
• Cumana parallel port CD-ROM drive,
• Lantech NE2000 clone network cards (EN2000 and E-Net 16/A),
• IBM Auto 16/4 Token-Ring ISA Adapter,
• Novell/Anthem NE1000 and NE2000 network cards,
• Sony SLCD, IDE and SCSI CD-ROM drives (single, dual and quad speed),
• US Robotics Courier V.Everything (V.34+) Fax-Modem,
• Memory configurations ranging from 4Mb to 128Mb

Note : Although Windows 95 will run in 4Mb of memory, it can be quite slow and exhibits a lot of swapfile activity. On a 4Mb system, under ‘System Properties’ ‘Performance’, Windows 95 will suggest that more RAM is installed; 8Mb is a recommended minimum. Also, full network functionality is not available unless you have at least 6Mb, otherwise you can only operate as a client - no server (file and print sharing) capability.

TSD testing also involved PCMCIA (PC Card) adapter compatibility testing in the LS Pro (Caracal), IBM ThinkPad 755CE, and Toshiba T-2150CDT systems, and included;-

• The Adaptec SlimSCSI adapter
• The Dacom Gold FaxModem card
• The Mitsubishi 14400 FaxModem
• The US Robotics WorldPort 2496 Fax Modem card
• The 3Com 3C589B Ethernet adapter
• The IBM Token Ring adapter
• The Apex Token Ring adapter
• The Apex Data High Speed PCMCIA Modem

Installation

Test installations were simple thanks to the much improved setup procedures within Windows 95. The Windows 95 CD-ROMs supplied by Microsoft to Apricot during the beta program contained upgrade product (that had to be installed over an existing DOS/Windows setup), and as a result, most systems were upgraded from existing working configurations rather than being installed from scratch, although a few systems were ‘clean installed’. No major problems were found either way.

Most of the Apricot hardware was auto-detected by Windows 95, but notable exceptions are the Cirrus Logic 5410 Graphics Controller (early XEN PC/XEN LS II and LS Pro), the Chips and Technologies 452 graphics Controller (XEN LS, Qi 486 and Panther 1 FT/e & FT/s), Apricot Business and Professional Audio (XEN-LS II and LS Pro) and i82592 and i82596 Network Adapters, however Apricot are writing an NDIS 3.1 driver for the i82596 adapter (XEN-LS II and LS Pro) and initial beta testing has not found any problems.

Windows 95 will work with Windows 3.x drivers, so the audio features on the LS Pro and XEN-LS II can be used, but without full support from Windows 95 (i.e. no toolbar mixer/volume controls. Likewise, Windows 3.x video drivers can be used (for CL5410 & C&T452 for example), but testing has identified certain limitations; see later in this document for details.

Plug and Play

Full plug and play compatibility is only accomplished on the current Apricot range with current BIOS revisions. Earlier versions of BIOS on the LS Pro (Caracal) and XEN PC series (Jade/Ruby) need to be upgraded for full plug and play support; a task that is easily accomplished with flash-programmable BIOS updates. Apricot are committed to ensuring full hardware compatibility for current and new systems with Windows 95, and all current and new systems will include a plug-and-play BIOS for ease of installation and configuration under Windows 95. Current Jade/Ruby BIOS is version 4.05, and current Caracal BIOS is 3.06.

Networking

Most network testing under Windows 95 involved using in-built 32-bit drivers, protocols and services. Some systems were however tested using ODI network drivers, and some systems were also configured using NetWare VLM client software (v1.20A) to enable full NDS compatibility. No problems were identified with any of these configurations. 32bit NDS aware NetWare clients are expected from both Microsoft and Novell within about 60 days of shipment of Windows 95. Systems running real-mode ODI and VLM drivers have also been run with Novell’s NMS and Lanalyzer for Windows products without error.

Conclusions

General conclusions within Apricot TSD are that Windows 95 is much easier to use than Windows 3.x, and eliminates the out of resource errors that occur under Windows 3.x on a heavily configured system. A lot of the tasks being run under Windows 95 within TSD would not be possible under Windows 3.x on an equivalent hardware configuration. The desktop and taskbar make Windows 95 easy to use and the various desktop configuration options make it easy to configure the system for personal preferences.

Specific Windows 95 Issues Identified During Testing

1. CL5410 Video (LS Pro and XEN-LS II)
Upon installation, Windows 95 will identify (incorrectly) the 5410 video adapter as a Cirrus Logic device (technically correct, but the Windows 95 Cirrus Logic driver assumes a 5422 controller or above with VESA BIOS). The 5410 however has no VESA BIOS.Once installed, Windows 95 will report an error when initialising the video and will then start in standard VGA mode. Once the system has booted, select desktop properties, settings, change display type, change adapter type, then select have disk. When prompted, insert the 5410 Windows 3.x drivers disk and then select a suitable driver option. Note that it is impossible to use a driver with more than 16 colours, but higher resolutions at 16 colours are possible (i.e. 800*600 or 1024*768). Windows 95 will display a message about being unable to read hardware settings from the driver. Acknowledge this message, then apply the changes and restart Windows 95. (See note 3 below - Use of Windows 3.x Video Drivers under Windows 95 for additional information).

2. C&T452 Video (Qi486, Panther 1 FT/s & FT/e and XEN-LS)
Upon installation, Windows 95 will not be able to identify the C&T452 controller, and so standard VGA should be selected. Once installed, and the system has booted, select desktop properties, settings, change display type, change adapter type, then select have disk. When prompted, insert the Apricot Hi-Res (C&T 452 Windows 3.x) drivers disk and then select a suitable driver option. Note that it is impossible to use a driver with more than 16 colours, but higher resolutions at 16 colours are possible (i.e. 800*600 or 1024*768). Windows 95 will display a message about being unable to read hardware settings from the driver. Acknowledge this message, then apply the changes and restart Windows 95. (See note 3 below - Use of Windows 3.x Video Drivers under Windows 95 for additional information).

3. Use of Windows 3.x Video Drivers under Windows 95
If using a Windows 3.x video driver under Windows 95, there are two limitations to be aware of.

1. When using a windowed command prompt (DOS box), Windows 95 will crash the DOS application if a display toolbar is selected. To ensure that this doesn’t happen, highlight the relevant icon (you could use the Find Files or Folders command to look for all .PIF files on the system), select properties, then select screen, and un-check the display toolbar box. Apply the change and save. The error actually seen is that Windows will display an Winoldap error box, and the details indicate a problem with the Windows 3.x video driver loaded (a general protection fault). Note that this limitation can cause problems when processing NetWare login scripts, and so it is recommended that for systems using Windows 3.x video drivers, the processing of login scripts is disabled, and the relevant resources connected to from within Windows 95.
   
   
2. It is not possible to select more than 16 colours on most systems using a Windows 3.x driver, even if the driver offers a higher colour choice. Selecting a 256 colour (or higher) Windows 3.x driver will result in Windows 95 reverting back to standard VGA.

4. Windows 95 with Apricot Business and Professional Audio
The Apricot Business and Professional Audio systems (as found on the LS Pro (Bonsai) and XEN-LS II) is not recognised by Windows 95, and there are currently no plans to develop Windows 95 drivers for these devices. It is however possible to install the Windows 3.x drivers that currently exist for these devices. Go into control panel, select the add new hardware icon, click next, select no to let Windows 95 search for new hardware, select sound video and game controllers, and then select have disk. Insert the Apricot Network and Audio Drivers Disk and install the appropriate driver from the list.With Windows 95 and the Business Audio drivers (on LS Pro [Bonsai]), some sounds will play incorrectly (loud static) when the system is busy, especially on early systems with CL5410 video hardware using the Windows 3.x video drivers.Also, when configured with the Business and Professional Audio drivers, or for that matter any Windows 3.x audio drivers, Windows 95 will not display any mixer tools in the toolbar, and the Windows 95 mixer application will not work with the Windows 3.x drivers. The only way to get mixer functionality is to use the Windows 3.x mixer applications supplied with the relevant drivers.

5. Windows 95 and the Sony CDU-55E Dual Speed IDE CD-ROM Drive
The Sony CDU-55E Dual Speed IDE CD-ROM drive is supported under Windows 95, but the revision of the CD-ROM drive must be BF or later (check the label on the top of the CD-ROM), otherwise read errors will be experienced when reading data from the drive (BD has been proven by R&D to cause problems, and BE was not tested by R&D, whereas BF is what Apricot are currently shipping).

6. Installing Windows 95 onto LS PRO (Caracal)
At present, Windows 95 will not correctly auto-detect the AMD PCNet adapter on the LS PRO (Caracal) systems when initially auto-detecting the hardware during setup/installation (it assumes that the adapter is an ‘AMD AM2100/1500t and compatibles’ device). The best way to overcome this problem is as follows;-

Firstly, ensure that you have a local copy of all the setup files, and that you have the latest Caracal BIOS (currently v3.06). When the Analyzing your computer screen appears during setup, do NOT tick the Network Adapter box (you can tick the Sound, MIDI, or Video Capture Card box to have the audio auto-detected). This will prevent the AMD PCNet adapter from being detected during the initial setup hardware detection stage. If you selected Custom at the Setup Options screen, when setup pauses at the Network Configuration screen, do not change any of the options. When the system resets after copying all the files on, it will go through a stage where it will auto-detect plug-and-play devices. At this stage, the network adapter will be correctly detected, and all devices will be correctly installed. All that remains after that is to go into the Network icon in Control Panel and set the various network options as desired (protocols, services and so on).

Note that the correctly identified device should be displayed as AMD PCNET Family Ethernet VL-Bus Adapter.

7. Installing Windows 95 onto XEN PCLS
At present, Windows 95 will not correctly auto-detect the AMD PCNet adapter on the XEN PCLS systems when initially auto-detecting the hardware during setup/installation (it assumes that the adapter is an ‘AMD AM2100/1500t and compatibles’ device). The best way to overcome this problem is as follows;-

Firstly, ensure that you have a local copy of all the setup files (on CD-ROM or hard-disk). When the Analyzing your computer screen appears during setup, do NOT tick the Network Adapter box (you can tick the CD-ROM Drive and Sound, MIDI, or Video Capture Card boxes to have the CD-ROM drive and audio hardware auto-detected). This will prevent the AMD PCNet adapter from being detected during the initial setup hardware detection stage. If you selected Custom at the Setup Options screen, when setup pauses at the Network Configuration screen, do not change any of the options. When the system resets after copying all the files on, it will go through a stage where it will auto-detect plug-and-play devices. At this stage, the network adapter will be correctly detected, and all devices will be correctly installed. All that remains after that is to go into the Network icon in Control Panel and set the various network options as desired (protocols, services and so on).

Note that the correctly identified device should be displayed as AMD PCNET Family Ethernet Adapter/ISA+.

8. Windows 95 and the Apricot PC-Online 14400 Internal Fax-Modem
If Windows 95 is installed onto a system with an Apricot PC-Online 14400 Internal Fax-Modem, or one is installed into a system running Windows 95, the auto-detect wizard will assume that it is a standard modem. To get full fax functionality, change this to a Rockwell 14400 bps Data-Fax Modem.

9. Windows 95 and Apricot Security/LOC Technology
Earlier Apricot systems that have the Apricot Security/LOC Technology option can use the Apricot Security/LOC Technology access control software under Windows 95. It is recommended however that the Apricot Security/LOC Technology Environment Pack Release 11 is used to install the software, and if using the Windows LOCSAVER application, do NOT enable the Timeout option, as LOCSAVER.EXE is a Windows 3.x application and monitors for system activity in a different way to Windows 95, and so as a result LOCSAVER will lock the system after the timeout period regardless of whether the system is idle or not. This is a limitation of the LOCSAVER software and is unlikely to be resolved.

Note that the Apricot Security/LOC Technology drive encryption option is NOT supported under Windows 95.

10. Windows 95 and Network Broadcast Messages
Windows 95 will by default not load any software to enable the display of network broadcast messages on systems using Microsoft network clients (Microsoft networks or Novell NetWare networks). To enable the display of broadcast messages, you need to run the Windows 95 program WINPOPUP.EXE.

11. Windows 95 Printing to NetWare Printers
There appears to be no way within Windows 95 to enable or disable broadcast messages for NetWare print queues. This limitation can be overcome by the use of the NetWare CAPTURE command (in a NetWare login script or DOS batch file when the user logs onto the relevant server).

12. Windows 95 and Long File Name Support under NetWare
It is possible to use Windows 95 long filenames on NetWare 3.x and 4.x servers, and this is accomplished by loading the OS/2 name space support module (OS2.NAM) on the NetWare server, and then adding the OS2 name space to the relevant volume(s). Note that this has an impact on the RAM needed on the NetWare server as adding an extra name space to a volume increases the memory needed to cache the volume!

During testing within TSD, one issue with this was identified however, in that even if the relevant steps are followed, a NetWare 3.11 server will not provide long file name support to a Windows 95 client (3.12 and 4.x work OK). Also, long name support is only available when using the Microsoft 32 bit client for NetWare (so on a NetWare 4.x server there will be no NDS support); using a real-mode client such as the VLM client shell will prevent long file name support on a NetWare server, even if the relevant server steps have been taken.

13. Windows 95 on Systems with LAN and Dial-Up Networking
A couple of problems have been seen when using systems that have both direct LAN connectivity and dial-up networking enabled.

1. If the Microsoft TCP/IP protocol is configured on both the LAN adapter and the Dial-Up Adapter, TCP/IP will only work on the last adapter defined/set-up (the other adapter will be disabled for TCP/IP). The only way around this is to either change the system configuration such that only one adapter (Dial-Up or LAN) has TCP/IP configured, or (in the case of mobile systems with PCMCIA) to physically remove the LAN adapter when using Dial-Up networking!
   
2. If the Microsoft NetWare Client is enabled on both a LAN adapter and the Dial-Up Adapter, Windows 95 will appear to hang when restoring permanent connections across the Dial-Up Adapter if the machine is also connected to the same LAN as the one that the dial-up host is connected to. If the machine is left, it will continue and connect correctly after a delay (of up to a couple of minutes).