ReadMe File for HF000X V0.8 Windows 95/A/B/C, 98 /SE, ME Driver package part Table of contents 1. Overview 2. Contents 3. Installation 4. Driver options 5. FAQ 6. Known issues 7. Revision history 8. Disclaimer 9. Copyright notices ------------------------------------------------------------------------------ 1. Overview HF000X is a driver package for the Diamond Multimedia HomeFree Wireless LAN line of cards and adapters for Windows 95, 98, ME, 2k, 2k3, NT3.51, NT4, LH and XP operating systems, supporting PCMCIA, ISAPNP and PCI cards and adapters. ------------------------------------------------------------------------------ 2. Contents HF000X contains the following files for Windows 95, 98 and ME 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 HF000X .INF - The combined INF file for 9X and NT 5 based operating systems HF000X9 .CAT - The Windows 98/SE, ME dummy catalog file 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 terms and setup procedures. For an easy step-by-step network and driver installation, browse the 'GUIDES' folder in your distibution copy of 'HF000X', read and print the guide for your operating system and follow its instructions. Additional internet sharing utilites from the original manufacturers windows 9X installation software are not 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 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' is 'hardwired' into the INF file. To customize the entry use the driver / network advanced properties page or the 'HomePing' WLU to change the default or current value. All text entries should or must be in upper case. Windows 95 defaults to 'IPX/SPX' without 'NetBIOS', no shared resources or 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 'WIN95A.TXT', 'WIN95B.TXT' and 'WIN95C.TXT'. Windows 98/SE and ME default to 'TCP/IP', no shared resources or 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 'WIN98.TXT', 'WIN98SE.TXT' and 'WINME.TXT'. Windows XP Home and Pro default to 'TCP/IP', no shared resources or 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 'WINXP.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 Protocol OS Adapter Driver OS Adapter Driver ---------------------------------------------------------------------------- TCP/IP connecting W95A / HFPCMCIA (Diamond) to W2K / HFPCI (Generic) TCP/IP connecting W95A / HFPCMCIA (Generic) to W2K / HFPCI (Generic) TCP/IP connecting W95A / HFPCMCIA (Diamond) to W2K3 / HFPCI (Generic) TCP/IP connecting W95A / HFPCMCIA (Generic) to W2K3 / 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 W98 / HFPCI (Generic) TCP/IP connecting W95A / HFPCMCIA (Generic) to W98 / HFPCI (Diamond) TCP/IP connecting W95A / HFPCMCIA (Generic) to WLH / HFPCI (Generic) TCP/IP connecting W95A / HFPCMCIA (Generic) to WME / HFISAPNP (Generic) TCP/IP connecting W95A / HFPCMCIA (Generic) to WME / HFISAPNP (Diamond) TCP/IP connecting W95A / HFPCMCIA (Generic) to WME / HFPCI (Generic) TCP/IP connecting W95A / HFPCMCIA (Generic) to WME / HFPCI (Diamond) TCP/IP connecting W95A / HFPCMCIA (Generic) to WXP / HFPCI (Generic) TCP/IP connecting W95B / HFPCMCIA (Generic) to WME / HFPCI (Generic) TCP/IP connecting W95B / HFPCMCIA (Generic) to WME / HFPCI (Diamond) TCP/IP connecting W95B / HFPCMCIA (Generic) to WXP / HFPCI (Generic) TCP/IP connecting W95C / HFPCMCIA (Generic) to WME / HFPCI (Generic) TCP/IP connecting W95C / HFPCMCIA (Generic) to WME / HFPCI (Diamond) TCP/IP connecting W95C / HFPCMCIA (Generic) to WXP / HFPCI (Generic) TCP/IP connecting W98 / HFPCMCIA (Generic) to W2K / HFPCI (Generic) TCP/IP connecting W98 / HFPCMCIA (Diamond) to W2K / HFPCI (Generic) TCP/IP connecting W98 / HFPCMCIA (Generic) to W2K3 / HFPCI (Generic) TCP/IP connecting W98 / HFPCMCIA (Diamond) to W2K3 / HFPCI (Generic) TCP/IP connecting W98 / HFPCMCIA (Generic) to WLH / HFPCI (Generic) TCP/IP connecting W98 / HFPCMCIA (Generic) to WME / HFPCI (Generic) TCP/IP connecting W98 / HFPCMCIA (Generic) to WME / HFPCI (Diamond) TCP/IP connecting W98 / HFPCMCIA (Generic) to WXP / HFPCI (Generic) TCP/IP connecting W98SE / HFPCMCIA (Generic) to WXP / HFPCI (Generic) NetBEUI connecting W95A / HFPCMCIA (Generic) to W98 / HFPCMCIA (Generic) NetBEUI connecting W95A / HFPCMCIA (Generic) to W98 / HFPCMCIA (Diamond) NetBEUI connecting W95A / HFPCMCIA (Generic) to WME / HFPCI (Generic) NetBEUI connecting W95A / HFPCMCIA (Generic) to WME / HFPCI (Diamond) IPX/SPX connecting W95A / HFPCMCIA (Generic) to WXP / HFPCI (Generic) IPX/SPX connecting W95A / HFPCMCIA (Diamond) to WXP / HFPCI (Generic) Configurations untestet TCP/IP connecting WNT3.51 / HFPCMCIA (Generic) to any TCP/IP connecting WNT3.51 / HFISAPNP (Generic) to any TCP/IP connecting WNT3.51 / HFPCI (Generic) to any TCP/IP connecting WNT4 / HFPCMCIA (Generic) to any TCP/IP connecting WNT4 / HFISAPNP (Generic) to any TCP/IP connecting WNT4 / HFPCI (Generic) to any ------------------------------------------------------------------------------ 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. 'Default CoNetId' (network identification) is a unique identifier distinguishing accessable nodes of one wireless lan from foreign wlans. Default : 'MYNETWORK' Max. length : 32 letters and digits Case : Upper and lower case possible 'Driver Description' is automaticaly administered by the system, no user interface available. Default : 'Auto' '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' 'Maximum Link Speed' limits the actual transfer speed (bitrate) of possible connections; higher bitrats available, because of hardware capability of the IFR controller, but not tested. Default : 1 Mbps Values : 1, 2, 4 Mbps (12, 24, 48 MHz IFR controller clock) 'Network Address' allows to substitude the current network address. Default : 'Auto' Max. length : 12 hexadecimal letters and digits Case : Upper case only 'Tx Minimum Holdoff' defines timeout holdoff to prevent packet collisions. Default : 1000 Range : 0...10000 Step : 100 'Vendor Description' identifies the vendor of the network. Default : 'HOMEFREE' Max. length : 32 letters and digits Case : Upper and lower case possible ------------------------------------------------------------------------------ 5. FAQ Q. Can 'HF000X' replace the manufacturer's driver packages? A. 'HF0009' contains only necessary and compatible parts. It provides the functionality and support needed and usual for wireless lan products. Q. Windows 95 OSR1 reports missing files 'HOMEPING.DOC' and 'SVRAPI.DLL' during installation and several others during removal of the manu- facturer's driver package. A. The installation and removal procedures and sequences are cleaned up. Q. Windows ME crashes during installation of the manufacturer's 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. Known issues None. ------------------------------------------------------------------------------ 7. 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 03/04/2006, V0.8, Updated INF and ReadMe ------------------------------------------------------------------------------ 8. 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. ------------------------------------------------------------------------------ 9. 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, 2K, 2K3, NT3.51, NT4, LH and XP are Copyright (C) Microsoft Corp. NetGroup Analsyser is Copyright (C) Politecnico di Torino, Italy TDIMON is Copyright (C) Mark RussinovichDownload Driver Pack
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.