README9X.TXT Driver File Contents (HF000X9_070.ZIP)

ReadMe File for HF000X9 V0.7 Windows 95A/B/C/98/98SE/ME Driver package part

   Table of contents

   1. Overview
   2. Contents
   3. Installation
   4. Driver options
   5. FAQ
   6. Revision history
   7. Disclaimer
   8. Copyright notices

------------------------------------------------------------------------------

1. Overview

   HF000X9 is a driver package for the Diamond Multimedia HomeFree Wireless
   LAN line of cards and adapters for Windows 95, 98, ME and XP operating
   systems, supporting PCMCIA, ISAPNP and PCI cards and adapters.

------------------------------------------------------------------------------

2. Contents
 
   HF000X9 for Windows 95, 98 and ME consists of the following files

   BIGSKYLN.VXD  - The VxD Memory trace device
   WIN95A  .TXT  - The easy network installation guide for Windows 95A
   WIN95B  .TXT  - The easy network installation guide for Windows 95B
   WIN95C  .TXT  - The easy network installation guide for Windows 95C
   WIN98   .TXT  - The easy network installation guide for Windows 98
   WIN98SE .TXT  - The easy network installation guide for Windows 98SE
   WINME   .TXT  - The easy network installation guide for Windows ME     
   HF000X9 .CAT  - The Windows 98/SE, ME dummy catalog file
   HF000X9 .INF  - The INF file for Windows 9X/ME operating systems
   HOMEPING.EXE  - The HomeFree wireless lan utility (WLU)
   HOMEPING.TXT  - The WLU ReadMe
   README9X.TXT  - This file
   SKYHOOK .VXD  - The Windows 95 support
   SKYLINE .SYS  - The W9X driver for HomeFree WLAN cards and adapters

------------------------------------------------------------------------------

3. Installation

   You must be familiar with network setup procedures.

   For an easy step-by-step network and driver installation, browse the
   'GUIDES' folder in your distibution copy of 'HF000X9', read and print
   the guide for your operating system and follow its instructions.

   Additional internet sharing utilites from the original W9X distribution
   are not neccesary for Windows ME and XP, both including the 'Network
   Installation Assistent' to create a diskette, containing necessary files
   to grant support for bridge based internet access from client machines.

   You may use Windows 9X/ME network properties and settings to configure
   workgroups, shared drives etc.
   

   Example

    W9x TCP/IP configuration
   
     User        : GUEST           (Setup)
     Computername: COMP1           (Setup / network properties, ident.)
     Workgroup   : HOMEFREE        (Network properties, identification)
     Description : MYNETWORK       (Network properties, identification)
     IP-Address  : 192.168.000.001 (Protocol properties)
     Subnet mask : 255.255.255.000 (Protocol properties)
     DNS         : -               (Protocol properties)
     CoNetId     : MYNETWORK       (Network properties, adv. / HomePing)

    ME TCP/IP configuration

     User        : GUEST           (Setup)
     Computername: COMP2           (Setup / network properties, ident.)
     Workgroup   : HOMEFREE        (Network properties, identification)
     Description : MYNETWORK       (Network properties, identification)
     IP-Address  : 192.168.000.002 (Protocol properties)
     Subnet mask : 255.255.255.000 (Protocol properties)
     DNS         : -               (Protocol properties)
     CoNetId     : MYNETWORK       (Network properties, adv. / HomePing)

    XP TCP/IP configuration

     User        : GUEST           (Setup)
     Computername: COMP3           (Setup / network properties, ident.)
     Workgroup   : HOMEFREE        (Network properties, identification)
     Description : MYNETWORK       (Network properties, identification)
     IP-Address  : 192.168.000.003 (Protocol properties)
     Subnet mask : 255.255.255.000 (Protocol properties)
     DNS         : -               (Protocol properties)
     CoNetId     : MYNETWORK       (Driver / network properties, adv.)


     CoNetId 'MYNETWORK' for Windows 9X/ME is 'hardwired' into the INF file.
     To customize the entry use the driver / network advanced properties page
     or the 'HomePing' WLU to change the current value.

     All text entries should or must be in upper case.


   Windows 95 defaults to 'IPX/SPX' without 'NetBIOS', no shared resources and
   access rights during network installation. 'TCP/IP' protocol, shared drives
   and printers, access rights and path have to be supplied manualy. Additional
   information about network installation and configuration is supplied in the
   'easy step-by-step installation guide' files 'EASYW95A.TXT', 'EASY95B.TXT'
   and 'EASY95C.TXT'.

   Windows 98/SE and ME default to 'TCP/IP', no shared resources and access
   rights during network installation. Shared drives and printers, access
   rights and path have to be supplied manualy. Additional information about
   network installation and configuration is supplied in the 'easy step-by-step
   installation guide' files 'EASY98.TXT', 'EASY98SE.TXT' and 'EASYME.TXT'.

   Windows XP Home and Pro default to 'TCP/IP', no shared resources and access
   rights during network installation. Shared drives and printers, access rights
   and path have to be supplied manualy.  Additional information about network
   installation and configuration is supplied in the 'easy step-by-step install-
   ation guide' file 'EASYXP.TXT'.


   XP and XP with Service Pack 1 do not support 'NetBEUI', use
   'NWLink IPX/SPX/NetBIOS compatible protocol' for XP and
   'IPX/SPX compatible protocol' with activated
   'NetBIOS over IPX/SPX' to connect W9X/ME to XP instead.

   XP with Service Pack 2 supports 'NetBEUI'.

   Minimum 'TCP/IP' configuration is preferable to and more reliable than
   'NetBIOS' over 'IPX/SPX'.


   Configurations testet
 
    TCP/IP  connecting W95A / HFPCMCIA (Generic) to W98  / HFPCI    (Generic)  
    TCP/IP  connecting W95A / HFPCMCIA (Generic) to W98  / HFPCI    (Diamond)  
    TCP/IP  connecting W95A / HFPCMCIA (Generic) to WinME/ HFPCI    (Generic)  
    TCP/IP  connecting W95A / HFPCMCIA (Generic) to WinME/ HFPCI    (Diamond)  
    TCP/IP  connecting W95A / HFPCMCIA (Generic) to WinXP/ HFPCI    (Generic)

    TCP/IP  connecting W95B / HFPCMCIA (Generic) to WinME/ HFPCI    (Generic)  
    TCP/IP  connecting W95B / HFPCMCIA (Generic) to WinME/ HFPCI    (Diamond)  
    TCP/IP  connecting W95B / HFPCMCIA (Generic) to WinXP/ HFPCI    (Generic)

    TCP/IP  connecting W95C / HFPCMCIA (Generic) to WinME/ HFPCI    (Generic)  
    TCP/IP  connecting W95C / HFPCMCIA (Generic) to WinME/ HFPCI    (Diamond)  
    TCP/IP  connecting W95C / HFPCMCIA (Generic) to WinXP/ HFPCI    (Generic)

    TCP/IP  connecting W98  / HFPCMCIA (Generic) to WinME/ HFPCI    (Generic)  
    TCP/IP  connecting W98  / HFPCMCIA (Generic) to WinME/ HFPCI    (Diamond)  
    TCP/IP  connecting W98  / HFPCMCIA (Generic) to WinXP/ HFPCI    (Generic)

    TCP/IP  connecting W98SE/ HFPCMCIA (Generic) to WinXP/ HFPCI    (Generic)

    TCP/IP  connecting W95A / HFPCMCIA (Generic) to W98  / HFISAPNP (Generic)
    TCP/IP  connecting W95A / HFPCMCIA (Generic) to W98  / HFISAPNP (Diamond)
    TCP/IP  connecting W95A / HFPCMCIA (Generic) to WinME/ HFISAPNP (Generic)
    TCP/IP  connecting W95A / HFPCMCIA (Generic) to WinME/ HFISAPNP (Diamond)

    NetBEUI connecting W95A / HFPCMCIA (Generic) to W98  / HFPCMCIA (Generic)
    NetBEUI connecting W95A / HFPCMCIA (Generic) to W98  / HFPCMCIA (Diamond)
    NetBEUI connecting W95A / HFPCMCIA (Generic) to WinME/ HFPCI    (Generic)
    NetBEUI connecting W95A / HFPCMCIA (Generic) to WinME/ HFPCI    (Diamond)

    IPX/SPX connecting W95A / HFPCMCIA (Generic) to WinXP/ HFPCI    (Generic)
    IPX/SPX connecting W95A / HFPCMCIA (Diamond) to WinXP/ HFPCI    (Generic)

   Configurations untestet

    NT4/2K/2K3 (Generic)

------------------------------------------------------------------------------

4. Driver options

    Physical driver and network parameters can be modified, changing default
    values in the network properties advanced tab, optimizing performance
    or to customize settings.
    
     'CoNetId' (network identification) is a unique identfier distinguish-
      ing accessable nodes of one wireless lan from foreign wlans.

       Default     : MYNETWORK
       Max. length : 32 letters and digits
       Case        : Upper and lower case possible

     'Interrupt Number' is automaticaly administered by the system, no
      user interface available.

       Default     : 'Auto'

     'I/O Base Address' is automaticaly administered by the system, no
      user interface available.

       Default     : 'Auto'

     'MaximumLinkSpeed' limits the actual transfer speed (bitrate) of
      possible connections; higher bitrats possible due to hardware
      capability of the IFR controller, but not confirmed. 

       Default     : 1.0 Mbit
       Values      : 0.5 Mbit, 1.0 Mbit (,1.5 , 2.0, 2.5, 3.0, 3.5, 4.0 Mbit)

     'NetworkAddress' allows to substitude the current network address.

       Default     : 'Auto'
       Max. length : 12 hexadecimal letters and digits
       Case        : Upper case only

     'TxMinimumHoldoff' defines timeout hold off to prevent packet collisions. 

       Default      : 1000
       Range        : 0...10000
       Step         : 100

     'VendorDescription' identifies the vendor of the network.

      Default      : HOMEFREE
      Max. length  : 32 letters and digits
      Case         : Upper and lower case possible 

------------------------------------------------------------------------------

5. FAQ

   Q. Can 'HF000X9' replace the original windows driver package?
   A. 'HF000X9' contains only necessary and compatible parts. It provides the
      functionality and support needed and usual for wireless lan products.

   Q. Windows 95 reports missing files 'HOMEPING.DOC' and 'SVRAPI.DLL' during
      installation and several others during removal of the original driver
      package.
   A. The installation and removal procedures and sequences are cleaned up. 

   Q. Windows ME crashes during installation of original drivers.
   A. The original drivers missused 'SKYNDI.DLL' for extended installation
      options. The complete procedure is no longer used.

   Q. HomePing won't report any visible nodes.
   A. Add the protocol 'NetBEUI' to your bindings.
      HomePing must be running on every node to be reported.

   Q. Are common wireless lan utilities and sniffers compatible with the
      HomeFree wlan?
   A. HomeFree wireless lan emulates an IEEE 802.3 cable based lan. It's
      Windows 95/98 driver design restricts performance and interface,
      providing support for common and advanced protocol analysation on
      network protocol level only.
      (-> NetGroup 'Analayser', System Internals 'TDIMON')   
    
------------------------------------------------------------------------------

6. Revision history

   08/21/2004, V0.1, Crosscompare version for ALL_OS.INF assembled
   07/19/2005, V0.2, All OS version stripped down to W9X/ME only
   07/28/2005, V0.3, Optional parameters added
   08/03/2005, V0.4, HomePing WLU support added
   08/08/2005, V0.5, Reintegration into ALL_OS.INF
   12/01/2005, V0.6, Advanced network properties, WHQL conformity
   01/04/2006, V0.7, Minor changes and additions, network installation guides

------------------------------------------------------------------------------

7. Disclaimer

   This driver is provided in good faith and the hope that it is useful for
   users, however the author explicitly disclaims all liability for damages
   that are a result of the usage of this driver.

   The author is not affiliated with any company mentioned, nor is any support
   available from them.

------------------------------------------------------------------------------

8. Copyright notices

   BIGSKYLN.VXD, SKYHOOK.VXD and SKYLINE.SYS are Copyright (C) Alation Systems
    , Inc.
   HOMEPING.EXE is Copyright (C) Diamond Multimedia Systems, Inc.
   HomeFree (R) is Registered Trademark (TM) Diamond Multimedia Systems, Inc.
   Windows (R) 95, 98, ME, NT4, 2K, 2K3 and XP are Copyright (C) Microsoft Corp.
   NetGroup Analsyser is Copyright (C) Politecnico di Torino, Italy
   TDIMON is Copyright (C) Mark Russinovich
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web4, load: 1.52