VMISFT-RFM2G. Drivers for Windows NT, 2000, 2003 Server and XP Operating Systems Installation Guide Document Number # Rev.

Transcription

1 GE Fanuc Automation VMISFT-RFM2G Drivers for Windows NT, 2000, 2003 Server and XP Operating Systems Installation Guide Document Number # Rev. B FANUC Parts

2 Table of Contents Chapter 1 - Drivers for Windows 2000, 2003 Server and Windows XP System Requirements Hardware Software Reference Documentation GE Fanuc Embedded Systems Technical Support Installation Installing the RFM Boards Modifying the SystemPages Registry Key Installing the RFM2g Device Driver Installing the Reflective Memory Device Driver Installing the RFM2g Utilities and Sample Files Driver Installation API Library and Command Monitor Installation Optional Command Line Utility Procedure Remove the API library and command line utilites: Standalone driver removal Components DLL Services Chapter 2 - Windows NT Driver The Windows NT Driver Supported Boards Installation Installing the RFM2g Boards Modifying the SystemPages Registry Key Installing the RFM2g Device Driver, Utilities and Sample Files Verifying RFM2g Driver Operation

3 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Uninstalling the RFM2g Device Driver, Utilities and Sample Files Components Building the Sample Application DLL Services Accessing Additional Information Distributed Files with the VMISFT/SW-RFM2G-ABC-940 device driver 58 Deprecated Windows API Functions Additional API Functions: VMISFT/SW-RFM2G-ABC-910 (Windows NT) and VMISFT/SW-RFM2G-ABC-940 (Windows 2000) Device Drivers 60 RFM2gEventName() RFM2gFlushEventQueue() RFM2gGetDebugFlagInfo() RFM2gGetEventQueueCount() RFM2gGetEventQueueLimit() RFM2gGetEventQueueMaxLimit() RFM2gNevents() RFM2gReceiveEventFromQueue() RFM2gRegName() RFM2gRegOffset() RFM2gRegSize() RFM2gSetEventQueueLimit() Appendix A - Troubleshooting Guide 74 Symptoms and Possible Causes Appendix B - Modification of the Driver for Specific Chipsets 78 Symptoms and Possible side effects Description: Installation FANUC Parts

4 CHAPTER 1 Drivers for Windows 2000, 2003 Server and Windows XP Contents System Requirements Reference Documentation GE Fanuc Embedded Systems Technical Support Installation Standalone driver removal Components DLL Services Introduction This chapter provides installation, installation verification and uninstall information for the VMISFT/SW-RFM2G-ABC-940 drivers that operate on the Windows 2000, 2003 Server and Windows XP platforms. 4

5 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces System Requirements Hardware Software To install and run the device driver, you must have the following: One of the following boards: VMIPCI-5565 VMIPMC-5565 or Windows NT 4.0 with service pack 6 or later for the VMISFT/SW-RFM2G-ABC-940 device driver Windows 2000 with service pack 4 or later for the VMISFT/SW-RFM2G-ABC-940 device driver Windows 2003 Server with service pack 1 for the VMISFT/SW-RFM2G-ABC-940 device driver Windows XP with service pack 2 for the VMISFT/SW-RFM2G-ABC-940 device driver 5 FANUC Parts

6 Reference Documentation 1 Reference Documentation The following is a list of reference documentation related to this driver: Common RFM2g Application Program Interface (API) and Command Line Interpreter for VMISFT/RFM2g Drivers. Document No Please call your GE Fanuc Embedded Systems sales representative for more information. Information on Reflective Memory and other GE Fanuc Embedded Systems Reflective Memory products is available via the World Wide Web at: reflective_mem/index.html Windows documentation is available from Microsoft Corp. via the World Wide Web. 6

7 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces GE Fanuc Embedded Systems Technical Support You may contact GE Fanuc Embedded Systems Customer Care at: TELEPHONE: GEFANUC (or ) (outside of U.S.) FAX: support.embeddedsystems@gefanuc.com Service is free with product purchase. With your correspondence, please provide the following: Product number and version, found by reading the version.h file Type of target hardware, processor and board Software version numbers of Windows 2000, 2003 Server or Windows XP Exact wording of any messages on your screen What you were doing when the error occurred What steps you have taken (if any) to resolve the problem In addition, when ing, please include the following: Your name Your company s name Your phone and fax numbers Your address 7 FANUC Parts

8 Installation 1 Installation Installing the RFM Boards The steps in this section will guide you through the installation of the VMISFT/SW-RFM2G-ABC-940 device drivers for the 2 GigaBaud Reflective Memory Interfaces on the Windows 2000, 2003 Server and Windows XP operating systems. The tasks required to install the device driver are: Installing the RFM2g Boards Modifying the SystemPages Registry Key Installing the RFM2g Device Driver, which includes: Installing the Reflective Memory 2 GigaBaud Device Driver Verifying Driver Installation (Optional) Installing the 2 GigaBaud Reflective Memory utilities and sample files Steps for accomplishing each of these tasks are described on the following sections. 1. Shut down and turn off your Windows 2000, 2003 Server or Windows XP system. 2. Using appropriate ESD protection, remove the case from your system. 3. Jumper a unique RFM node number into each RFM2g interface board to be installed. See your interface board s user s guide for jumper information. 4. Install each RFM2g interface board into a free PCI slot in the computer. The RFM2g board in the lowest-numbered PCI slot will be assigned the device name \\.\rfm2g1, the RFM card in the next-highest numbered slot will be assigned the name \\.\rfm2g2", etc. NOTE: The RFM2g device name has no correlation to the RFM2g node number for that device. For example, if an RFM board with the device name rfm2 is removed from a system containing several RFM boards and then later placed in PCI slot 5 in the system (i.e. an empty slot), the device name will change to rfm2g6. Modifying the SystemPages Registry Key By default, the Windows 2000, 2003 Server and Windows XP Operating System manages page tables by calculating the number of Page Table Entries (PTEs) to allocate. When Windows 2000, 2003 Server and Windows XP were initially developed, it was not assumed that devices would have more peripheral memory than system memory (such as Reflective Memory). As a result, the default value of the SystemPages registry key, which stores the PTEs, is usually set at a default value of zero (0). 8

9 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces To load and start the 2 GigaBaud RFM2g driver (PMC5565.sys), the SystemPages registry key must be edited to increase the PTEs that the system allocates. NOTES: The larger the SystemPages value, the more system resources (i.e. memory) are utilized. You must be logged into an account with administrator privileges to save changes made to registry entries. CAUTION: It is recommended to back up and create an emergency repair disk for the computer before editing its registry entries. Incorrectly modifying the registry can make Windows 2000, 2003 Server or Windows XP nonfunctional on your computer. To modify the SystemPages registry key: 1. Log on to the system. 2. Select Start > Run to display the Run dialog box. 3. Type regedit and then click OK 9 FANUC Parts

10 Installation 1 The Registry Editor displays. 4. Navigate to the HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Session Manager > Memory Management registry key. 5. Highlight SystemPages and then select Edit > Modify. -or- Double-click on SystemPages. The Edit DWORD Value dialog box displays. 10

11 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces 6. Modify the Value data field. Recommended values are to 50000, with being a recommended initial value. Use the following formula to determine a SystemPages value: SystemPages Value Description Use for the first 32 Mbytes of main system memory 8192 Use for each additional 32 Mbytes of main system memory 8192 Use for each 32 Mbytes of Reflective Memory NOTES: The default Windows 2000, 2003 Server and Windows XP SystemPages value is usually zero (0). Write down the original SystemPages value that initially displays in the Edit DWORD Value dialog box in case you want to restore it later. 7. Click OK to dismiss the Edit DWORD Value dialog box. 8. Select Registry > Exit to dismiss the registry editor. 9. Reboot the computer. 11 FANUC Parts

12 Installation 1 Installing the RFM2g Device Driver NOTES: Before installing the driver, ensure that any previous version of the RFM2g device driver has been uninstalled and that all virus protection software has been turned off to prevent installation conflicts. Refer to "Standalone driver removal" on page 30 and perform a complete removal of the current device driver. This operation will not remove the currently installed API library or the command line driver. You must have administrator privileges to install this device driver. Installation of the software for the Reflective Memory 2 GigaBaud boards is comprised of three parts: 1. Installing the Reflective Memory 2 GigaBaudDevice Driver 2. Verifying Driver Installation (Optional) 3. Installing the Reflective Memory 2 GigaBaud utilities and sample files Steps for accomplishing each of these tasks are described on the following pages. Installing the Reflective Memory Device Driver Windows 2000, 2003 Server and Windows XP utilize the Plug and Play feature to automatically detect when a new hardware is installed. The distribution media includes a Windows 2000-, 2003 Server- or Windows XP-compatible configuration information (.inf) file, pmc5565.inf, which is used by Plug and Play to load the device driver. NOTE: Windows.inf files will only function with Windows 2000, 2003 Server or Windows XP. Plug and Play will detect the Reflective Memory 2 GigaBaud board you installed, and then prompt you for the location of the device driver. 1. Boot Windows 2000, 2003 Server or Windows XP. 2. Insert the VMISFT/SW-RFM2G-ABC-940 distribution media into the CD-ROM device. 3. Log on to the system with administrator privileges. 4. Plug and Play searches the system and, when the newly-installed RFM2g board is found, displays a Found New Hardware dialog box, followed by the Welcome to the Found New Hardware Wizard. 12

13 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces NOTE: RFM2g boards are defined by the PCI configuration ID system as a network controller board. Click Next >. 5. The Install Hardware Device Drivers dialog box displays. 13 FANUC Parts

14 Installation 1 Select Search for a suitable driver for my device (recommended) and then click Next >. 6. The Locate Driver Files dialog box displays. Check the CD-ROM drives check box. Click Next >. 7. The Driver Files Search Results dialog box displays with the message Windows found a driver for this device. To install the driver Windows found, click Next. Click Next >. 14

15 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces 8. At this point, Windows 2000 or Windows XP may display a Digital Signature Not Found dialog box containing the name of the RFM2g board for which you are installing the driver. Click Yes. 9. Windows 2000 or Windows XP displays a Copying Files dialog box, followed by the Completing the Found New Hardware Wizard dialog box that specifies the Reflective Memory 2 GigaBaud device driver for the particular RFM2g board that was installed. 15 Click Finish. FANUC Parts

16 Installation 1 Installing the RFM2g Utilities and Sample Files To install the 2 GigaBaud Reflective Memory Utility and sample files, perform the following: 1. Ensure that the device driver has been loaded. See "Components" on page 32 for more information. NOTE: The utility will not function without the device driver. 2. Insert the VMISFT/SW-RFM2G-ABC-940 distribution media into the CD-ROM device. 3. Double-click on the My Computer icon on your Windows 2000, 2003 Server or Windows XP desktop. 4. Double-click on your CD-ROM s icon. 5. Double-click on the RFM2g Utilities folder icon, and then double-click Setup.exe. 16

17 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Driver Installation If installing the driver for the first time, the Windows Plug-and-Play environment will present the following screen: Select "No, not this time" 17 FANUC Parts

18 Installation 1 Click "Next" Select "Continue Anyway" 18

19 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Typical progression bar. 19 The driver has loaded FANUC Parts

20 Installation 1 An optional step is to verify that the driver has loaded: 1. Start->Settings->ControlPanel->->Administrative Tools->Computer Management 2. Select Device Manager 3. Click on "Network adapters" 20

21 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces API Library and Command Monitor Installation Next is the installation of the RFM2g API library and command line utilities: 1. Run "Setup.exe" from the delivery CD-ROM 2. If Windows XP Service Pack 2 is installed the following menu will appear: 21 Click "Run" FANUC Parts

22 Installation 1 Click "Run" Typical progression message. 22

23 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Welcome screen, click "Next>" 23 FANUC Parts

24 Installation 1 Click "Next" Click "Next" for the default installation Or select the alternate API library and click "Next" 24

25 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Or select the Custom installation of the API library and click "Next" Select custom API library components and click "Next" 25 FANUC Parts

26 Installation 1 Click "Next" for the default folder destination Typical progression messages 26

27 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Click "Next" Click "Finish" 27 FANUC Parts

28 Installation 1 Optional Command Line Utility Procedure The following is an optional procedure used to execute the command line utility. 1. Start->Rfm2g Utilities- API library->rfm2g_util 2. Type "1" 3. Type "config" Remove the API library and command line utilites: 1. Start->Settings->ControlPanel->Add/Remove Programs Click "Change/Remove" The utility will begin removing the files. 28

29 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces A new option is now available to remove the device driver after successful removal of the command line monitor and API library. The default is "No" If you want to remove the RFM2g driver click on "Yes" Typical progression message Click "Finish" The system will reboot. 29 FANUC Parts

30 Standalone driver removal 1 Standalone driver removal Click Yes 30

31 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Click "Finish" 31 FANUC Parts

32 Components 1 Components The VMISFT/SW-RFM2G-ABC-940 Driver contains the following components: 1. Installable Device Driver (PMC5565.sys, or PMC5565_XP.sys) The device driver may be installed into a running system without rebooting or otherwise interfering with any executing programs. However, the system must be rebooted before the driver may be used. An application program gains access to the underlying RFM2g hardware by opening a file created by the driver named similar to \\.\RFM2g1 (for the first RFM2g device in the system). When this file is opened, the application program may then use a driver I/O control request to map the RFM2g device s local memory into its virtual address space where ordinary array access techniques may be used. Alternatively, the application may issue other I/O control requests to access the Reflective Memory on an 8-bit byte, 16-bit word, or 32-bit longword basis. The driver provides up to four types of RFM2g interrupt events for use by the application program. An application may send an RFM2g interrupt event to any other individual RFM2g node or may broadcast the RFM2g interrupt event to all other RFM2g nodes. The application may also wait to receive the next RFM2g interrupt event transmitted by another RFM2g node. The driver may be safely used in a multiprocessor system. It is threadsafe, so multiple application threads may access it. 2. C-Language Driver Header Files (rfm2gdll_stdc.h, rfm2g_api.h) The application program interface to the services provided by the driver are defined in header files. This file is suitable for inclusion in either a standard C or C++ compilation. 3. DLL Runtime Library (rfm2gdll_stdc.dll) Services additional to those provided by the driver are implemented as a dynamic-link library or DLL. One DLL is provided, which is for standard C compilers (rfmdll_stdc.dll). The DLL provides a language-specific binding of the interface to the device driver. 4. Sample Applications (rfm2g_util.exe) The rfm2g_util.exe program, with source code, is provided to demonstrate the RFM2g device driver and DLL. Language specific bindings for ANSI-C are available in the executable file rfm2g_util.exe. Many common operations (such as displaying the RFM2g memory or sending an RFM2g interrupt event) are implemented. The programs accept input from the command line (for batch use) or the standard input file (for interactive use). 32

33 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Also included are sample applications on how to use the API. The samples are intended to work together to demonstrate basic data transfer and interrupt handshaking: rfm2g_sender.c, rfm2g_receiver.c, rfm2g_map.c. See the Common_API.pdf (document no ) for more information. 33 FANUC Parts

34 DLL Services 1 DLL Services Standard C language bindings for the rfmdll_stdc.dll DLL are provided. The DLL has its own header file which defines the features provided for standard C compilers. NOTE: The DLLs included with VMISFT/SW-RFM2G-ABC-940 driver support the Microsoft Visual C++ dllexport interface only. 34

35 1 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces 35 FANUC Parts

36 CHAPTER 2 Windows NT Driver Contents The Windows NT Driver Supported Boards Installation Uninstalling the RFM2g Device Driver, Utilities and Sample Files Components Building the Sample Application DLL Services Accessing Additional Information Deprecated Windows API Functions Introduction This chapter provides installation, installation verification and uninstall information for the VMISFT/SW-RFM2G-ABC-940 driver that operates on the Windows NT platform. NOTE: Windows NT drivers are not supported for versions of Windows NT earlier than

37 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces The Windows NT Driver Supported Boards The VMISFT/SW-RFM2G-ABC-940 device driver supports the following boards. Board VMIPCI-5565 VMIPMC-5565 Description PCI bus 2 GigaBaud Reflective Memory PMC bus 2 GigaBaud Reflective Memory 37 FANUC Parts

38 Installation 2 Installation NOTES: Before installing the driver, ensure that any previous version of the RFM2g device driver has been uninstalled and that all virus protection software has been turned off to prevent installation conflicts. You must have administrator privileges to install this device driver. Updates of the Windows NT driver can be downloaded from Installing the RFM2g Boards The steps in this section will guide you through the installation of the VMISFT/SW-RFM2G-ABC-940 Device Driver for the 2 GigaBaud Reflective Memory Interfaces on the Windows NT 4.0 operating system. The tasks required to install the device driver are: Installing the RFM2g Boards Modifying the SystemPages Registry Key Installing the RFM2g Device Driver, Utilities and Sample Files Verifying Driver Operation Steps for accomplishing each of these tasks are described in the following sections. 1. Shut down and turn off your Windows NT 4.0 system. 2. Using appropriate ESD protection, remove the case from your system. 3. Jumper a unique RFM2g node number into each RFM2g interface board to be installed. See your interface board s user guide for jumper information. 4. Install each RFM2g interface board into a free PCI slot in the computer. The RFM2g board in the lowest-numbered PCI slot will be assigned the device name \\.\rfm2g1, the RFM2g card in the next-highest numbered slot will be assigned the name \\.\rfm2g2, etc. 5. Boot the system. Modifying the SystemPages Registry Key By default, the Windows NT 4.0 Operating System manages page tables by calculating the number of Page Table Entries (PTEs) to allocate. When Windows NT was initially developed, it was not assumed that devices could have a device with more peripheral memory than system memory (such as Reflective Memory). As a result, the default value of the SystemPages registry key, which stores the PTEs, is usually set at a default value of zero (0). 38

39 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces To load and start the 2GigaBaud RFM2g driver (PMC5565.sys), the SystemPages registry key must be edited to increase the PTEs that the system allocates. NOTES: The larger the SystemPages value, the more system resources (i.e. memory) are utilized. You must be logged into an account with administrator privileges to save changes made to registry entries. CAUTION: It is recommended to back up and create an emergency repair disk for the computer before editing its registry entries. Incorrectly modifying the registry can make Windows NT nonfunctional on your computer. To modify the SystemPages registry key: 1. Log on to the system. 2. Select Start > Run to display the Run dialog box. 3. Type regedit and then click OK. 39 FANUC Parts

40 Installation 2 The Registry Editor displays. 4. Navigate to the HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Session Manager > Memory Management registry key. 5. Highlight SystemPages and then select Edit > Modify. -or- Double-click on SystemPages. The Edit DWORD Value dialog box displays. 40

41 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces 6. Modify the Value data field. Recommended values are to 50000, with being a recommended initial value. Use the following formula to determine a SystemPages value: SystemPages Value Description Use for the first 32 Mbytes of main system memory 8192 Use for each additional 32 Mbytes of main system memory 8192 Use for each 32 Mbytes of Reflective Memory NOTES: The default Windows NT SystemPages value is usually zero (0). Write down the original SystemPages value that initially displays in the Edit DWORD Value dialog box in case you want to restore it later. 7. Click OK to close the Edit DWORD Value dialog box. 8. Select Registry > Exit to close the registry editor. 9. Reboot the computer. Installing the RFM2g Device Driver, Utilities and Sample Files To install the RFM2g Device Driver, Reflective Memory Utilities and sample files, perform the following: 1. Close all programs and turn off virus protection software to prevent installation conflicts. 2. Insert the VMISFT/SW-RFM2G-ABC-940 distribution media into the CD-ROM device. 3. Double-click on the My Computer icon on your Windows NT 4.0 desktop. 4. Double-click on 3 1/2 Floppy (A:) icon if the delivery media is a floppy disk. - or - Double-click on your CD-ROM s icon. 41 FANUC Parts

42 Installation 2 5. Double-click on the RFM2g Utilities folder icon, and then double-click Setup.exe. 6. The InstallShield Wizard dialog box displays, followed by the GE Fanuc Embedded Systems Reflective Memory RFM2g Driver & Utilities Setup wizard. Click "Run" Click "Run" 42

43 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Typical progression message. Welcome screen, click "Next>" 43 FANUC Parts

44 Installation 2 Click "Next" 44

45 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Click "Next" for the default installation Or select the alternate API library and click "Next" Or select the Custom installation of the API library and click "Next" 45 FANUC Parts

46 Installation 2 Select custom API library components and click "Next" Click "Next" for the default folder destination 46

47 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Typical progression messages Click "Next" 47 FANUC Parts

48 Installation 2 Click "Finish" 48

49 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Verifying RFM2g Driver Operation Once the driver and its utilities have been installed and the SystemPage registry key modified to increase its PTEs, you can verify that the driver is operating properly by doing the following: 1. Select Start > Programs > RFM2g Utilities > RFM2g Command Line Interpreter. An MS-DOS window displays containing information on the driver s status. The following is an example window: 2. If a dialog box displays containing the message Cannot open RFM2g file (\\.\rfm2g1)!, specify a larger PTE value for the SystemPages registry key. See "Modifying the SystemPages Registry Key" on page 38 for more information. NOTE: The larger the SystemPages value, the more system resources (i.e. memory) are utilized. 3. If your RFM card is still not functioning properly after specifying a larger PTE value, see "Troubleshooting Guide" on page 74 for additional information. If the problem persists, contact GE Fanuc Embedded Systems for further assistance. See "GE Fanuc Embedded Systems Technical Support" on page 7 for contact information. 49 FANUC Parts

50 Uninstalling the RFM2g Device Driver, Utilities and Sample Files 2 Uninstalling the RFM2g Device Driver, Utilities and Sample Files To uninstall the VMISFT/SW-RFM2G-ABC-940 driver, utilities and sample files: 1. Select Start > Settings > Control Panel, and then double-click the Add/Remove Programs icon. The Add/Remove Programs Properties dialog box displays. 2. Highlight RFM2g Utilities and then click Add/Remove. 50

51 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces 3. An InstallShield Wizard displays. Click Remove, and then click Next >. 4. A Confirm Uninstall message box displays. Click OK. 5. The Maintenance Complete dialog box displays on completion, confirming that the InstallShield Wizard has finished removing the utilities and sample files. 51 FANUC Parts

52 Uninstalling the RFM2g Device Driver, Utilities and Sample Files 2 Click Finish. 52

53 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Components The VMISFT/SW-RFM2G-ABC-940 Driver contains the following components: 1. Installable Device Driver (PMC5565.sys for NT, 2000) or (pmc5565_xp.sys for XP or 2003 Server) The device driver may be installed into a running system without rebooting or otherwise interfering with any executing programs. However, the system must be rebooted before the driver may be used. An application program gains access to the underlying RFM2g hardware by opening a file created by the driver named similar to \\.\RFM2g1 (for the first RFM2g device in the system). When this file is opened, the application program may then use a driver I/O control request to map the RFM2g device s local memory into its virtual address space where ordinary array access techniques may be used. Alternatively, the application may issue other I/O control requests to access the Reflective Memory on an 8-bit byte, 16-bit word, or 32-bit longword basis. The driver provides up to three types of RFM2g interrupt events for use by the application program. An application may send an RFM2g interrupt event to any other individual RFM2g node or may broadcast the RFM2g interrupt event to all other RFM2g nodes. The application may also wait to receive the next RFM2g interrupt event transmitted by another RFM2g node. The driver may be safely used in a multiprocessor system. It is threadsafe, so multiple application threads may access it. 2. C-Language Driver Header Files (rfm2gdll_stdc.h, rfm2g_api.h) The application program interface to the services provided by the driver are defined in header files. This file is suitable for inclusion in either a standard C or C++ compilation. 3. DLL Runtime Library (rfm2gdll_stdc.dll) Services additional to those provided by the driver are implemented as a dynamic-link library or DLL. One DLL is provided, which is for standard C compilers (rfmdll_stdc.dll). The DLL provides a language-specific binding of the interface to the device driver. 4. Sample Applications (rfm2g_util.exe) The rfm2g_util.exe program, with source code, is provided to demonstrate the RFM2g device driver and DLL. Language specific bindings for ANSI-C are available in the executable file rfm2g_util.exe. Many common operations (such as displaying the RFM2g memory or sending an RFM2g interrupt event) are implemented. The programs accept input from the command line (for batch use) or the standard input file (for interactive use). 53 FANUC Parts

54 Components 2 Also included are sample applications on how to use the API. The samples are intended to work together to demonstrate basic data transfer and interrupt handshaking: rfm2g_sender.c, rfm2g_receiver.c, rfm2g_map.c. See the Common_API.pdf for more information. 54

55 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Building the Sample Application The Sample Application comes with a Visual C Project File (rfm2g_util.dsw). This file is set up to correctly build the sample applications under the Intel platforms. However, you will need to use the Build > Set Active Configuration command within Visual C++ to select the Intel configuration you wish to build. The Intel configurations are Debug and Release. 1. Start Visual Studio with the project workspace RFM2G_UTIL.dsw. 2. To build the Sender example, set the active project to Sender_Win32 Release by selecting Build Set Active Configuration from the Visual Studio menu. 55 FANUC Parts

56 Building the Sample Application 2 3. Press the F7 function key to build the Sender example. 4. The Sender.exe file will be in the \Sender\Release directory. The additional sample applications are built in the same manner. For information on how to use the sample applications, consult Chapter 3 of the Common RFM2g Application Program Interface (API) and Command Line Interpreter for VMISFT/RFM2G Drivers. Document number

57 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces DLL Services Standard C language bindings for the rfmdll_stdc.dll DLL are provided. The DLL has its own header file which defines the features provided for standard C compilers. NOTE: The DLLs included with VMISFT/SW-RFM2G-ABC-940 driver support the Microsoft Visual C++ dllexport interface only. For information on the RFM2g API functions, see Chapter 1 of the Common RFM2g Application Program Interface (API) and Command Line Interpreter for VMISFT/RFM2G Drivers. 57 FANUC Parts

58 Accessing Additional Information 2 Accessing Additional Information The following is a complete list of files distributed with the VMISFT/SW-RFM2G-ABC-940 device driver software. Table 2-1 Distributed Files with the VMISFT/SW-RFM2G-ABC-940 device driver Location File Description <SystemDrive>\system32\driver pmc5565.sys The Reflective Memory device driver for NT 4.0 or 2000 <SystemDrive>\system32\driver pmc5565.sys_xp.sys The Reflective Memory device driver for XP or 2003 Server <SystemDrive>\system32 rfm2gdll_stdc.dll A DLL library containing a standard driver interface <SystemDrive>\GE Fanuc Embedded Systems\Rfm2g Utilities\Doc issues.txt Driver installations and operation issues <SystemDrive>\GE Fanuc Embedded Systems\Rfm2g Utilities\inc <SystemDrive>\GE Fanuc Embedded Systems\Rfm2g Utilities\Lib <SystemDrive>\GE Fanuc Embedded Systems\Rfm2g Utilities\Src memmgtkey.txt Readme.txt Version common_api.pdf pmc5565_nt.h rfm2gdll_stdc.h rfm2g_api.h rfm2g_defs.h rfm2g_errno.h rfm2g_osspec.h rfm2g_types.h version.h rfm2gdll_stdc.lib rfm2g_map.c rfm2g_receiver.c rfm2g_sender.c rfm2g_util.c RFM2G_UTIL.dsp RFM2G_UTIL.dsw Information on changing the value of the SystemPages registry entry Installation process Version of package Documentation of the RFM2g API Include files for building applications Include files for building applications Include files for building applications Include files for building applications Include files for building applications Include files for building applications Include files for building applications Include files for building applications Standard C library for linking applications Sample code for using the memory mapping feature Example code to receive data Example code to send data The command line monitor source Visual Studio 6.0 Project space for the command line monitor Visual Studio 6.0 Workspace for building the examples 58

59 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Table 2-1 Distributed Files with the VMISFT/SW-RFM2G-ABC-940 device driver (Continued) <SystemDrive>\GE Fanuc Embedded Systems\Rfm2g Uttilities\Src\MemoryMap <SystemDrive>\GE Fanuc Embedded Systems\Rfm2g Utilities\Src\Receiver <SystemDrive>\GE Fanuc Embedded Systems\Rfm2g Utilities\Src\Sender rfm2g_utilosspec.c MemoryMap.dsp Receiver.dsp Sender.dsp Template for additional functions in the command line monitor Visual Studio 6.0 Project space for the Memory Map example Visual Studio 6.0 Project space for the Receiver example Visual Studio 6.0 Project space for the Sender example The following is a list of reference documentation related to this driver: Common RFM2g Application Program Interface (API) and Command Line Interpreter for GE Fanuc Embedded SystemsGE Fanuc Embedded Systems SFT/RFM2g Driver. Document number FANUC Parts

60 Deprecated Windows API Functions 2 Deprecated Windows API Functions The following functions are deprecated and only available for use with the previous built applications VMISFT/SW-RFM2G-ABC-910 and VMISFT/SW-RFM2G-ABC-930 device drivers: Table 2-2 Additional API Functions: VMISFT/SW-RFM2G-ABC-910 (Windows NT) and VMISFT/SW-RFM2G-ABC-940 (Windows 2000) Device Drivers C-Language API Routine RFM2gEventName() RFM2gFlushEventQueue() RFM2gGetDebugFlagInfo() RFM2gGetDmaThreshold() RFM2gGetEventQueueCount() RFM2gGetEventQueueLimit() RFM2gGetEventQueueMaxLimit() RFM2gNevents() RFM2gNewDebugFlags() RFM2gNewDmaThreshld() RFM2gReceiveEventFromQueue() RFM2gRegName() RFM2gRegOffset() RFM2gRegSize() RFM2gSetEventQueueLimit() Description Returns the name of the RFM2g interrupt event. Flushes pending interrupt events. Returns the name of all RFM2g device driver debug message class control flags. Obsolete. See RFM2gGetDMAThreshold() in Common Driver doc. Returns the number or total number of pending events for each event type. Returns the limit on the number of pending events for each event type. Returns the maximum size setting for each event queue for an application. Returns and/or resets the value of RFM2g interrupt event counters. Obsolete. See RFM2SetDebug Flags(). Obsolete. See RFM2SetDMAThreshold() in Common Driver doc. Blocks received RFM2g interrupts events until the next interrupt event has been received. Returns the name of a specified RFM2g register by giving its offset. Returns the RFM2g hardware offset register. Use RFM2gFirst(). Returns the width of a named RFM2g hardware register. Returns the current limit on the number of pending events in the queue for each event type. 60

61 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces RFM2gEventName() Do not use the following for new applications. RFM2gEventName() is intended for backward compatibility only. The RFM2gEventName() function returns the address of an ASCII string which is the name of the RFM2g interrupt event whose binary value is given. The returned name does not contain the leading text RFM2G_EVENTID_. Syntax char Parameters *RFM2gEventName(RFM2GHANDLE rh, USHORT id); rh id Handle to open RFM device (I). Interrupt event of the currently opened RFM2g device (O). Return Values Success RFM2G_SUCCESS Refer to the driver definition of RFM2G_STATUS for all other possible return values. Example RFM2GHANDLE rh; USHORT id = RFM_EVENTID_2;... printf( The name for event id %u is %s.\n, id, RFM2gEventName( rh, id ) ); 61 FANUC Parts

62 Deprecated Windows API Functions 2 RFM2gFlushEventQueue() The RFM2gFlushEventQueue() function clears an application s event queue. The RFM2g device driver keeps a queue of pending events for each event type. An application can use RFM2gFlushEventQueue() to clear the event queue for a given event type, or clear all queues by passing RFM_EVENTID_NEVENTS for the event parameter. The function will return the number of events removed from the queue, or an error code it the call could not be completed. Syntax Parameters ULONG RFM2gFlushEventQueue(RFM2GHANDLE rh, RFMEVENTID event); rh event Handle to open RFM device (I). Which interrupt event queue to flush (I). See RFM2GETEVENTTYPE in the rmn_ioctl.h header file for valid values. Return Values Success RFM2G_SUCCESS Refer to the driver definition of RFM2G_STATUS for all other possible return values. Example RFM2GHANDLE rh; ULONG count;... count = RFM2gFlushEventQueue(rh, RFM_EVENTID_1); printf("%u events were flushed from event queue 1.\n", count); 62

63 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces RFM2gGetDebugFlagInfo() NOTE: Application programs should not use this function unless directed to do so by GE Fanuc Embedded Systems support personnel. The RFM2gGetDebugFlagInfo() function returns the name of the driver debug message class associated with a particular bit in the driver s debug flags variable. The RFM2g device driver can generate debug messages to assist GE Fanuc Embedded Systems support personnel in debugging. The actual debug message classes can vary between releases of the RFM2g driver. Syntax Parameters BOOL RFM2gGetDebugFlagInfo( RFM2GHANDLE rh, UCHAR index, RFM2GDEBUGFLAGNAME ); rdfn rh Handle to currently opened RFM2g device (I). index rdfn Return Values Success RFM2G_SUCCESS Refer to the driver definition of RFM2G_STATUS for all other possible return values. 63 FANUC Parts

64 Deprecated Windows API Functions 2 RFM2gGetEventQueueCount() The RFM2g device driver keeps a count of the number of each event type s pending events for an application. The RFM2gGetEventQueueCount() function determines the number of pending events for each event type, or the total number of pending events by passing RFM2G_EVENTID_NEVENTS for the event parameter. The number of the events in the queue are returned if the call is successful; otherwise, an error code is returned. Syntax ULONG RFM2gGetEventQueueCount(RFM2GHANDLE rh, RFMEVENTID event); Parameters rh event Handle to open RFM device (I). Event statistics returned to caller (O). See the rfm2g_struct.h header file for the definition of RFM2GQINFO. Return Values Success RFM2G_SUCCESS Refer to the driver definition of RFM2G_STATUS for all other possible return values. Example RFM2GHANDLE rh;... printf( "There are %u events pending for event 1.\n", RFM2gGetEventQueueCount( rh, RFM_EVENTID_1 ) ); 64

65 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces RFM2gGetEventQueueLimit() The RFM2g device driver has a limit for the number of pending events of each event type for an application. The RFM2gGetEventQueueLimit() function determines the limit on the number of pending events for each event type. The function will return the number of events in the queue, or an error code if the call could not be completed. Syntax ULONG RFM2gGetEventQueueLimit( RFM2GHANDLE rh, RFMEVENTID event ); Parameters rh event Handle to open RFM device (I). Event statistics returned to caller (O). See the rfm2g_struct.h header file for the definition of RFM2GQINFO. Return Values Success RFM2G_SUCCESS Refer to the driver definition of RFM2G_STATUS for all other possible return values. Example RFM2GHANDLE rh;... printf( "There can be a maximum of %u events pending for event 1.\n", RFM2gGetEventQueueLimit( rh, RFM_EVENTID_1 ) ); 65 FANUC Parts

66 Deprecated Windows API Functions 2 RFM2gGetEventQueueMaxLimit() The RFM2g device driver has a maximum size setting for each event queue for an application. The RFM2gGetEventQueueMaxLimit() function determines the maximum size of an event queue. Syntax ULONG RFM2gGetEventQueueMaxLimit( RFM2GHANDLE rh ); Parameters rh Handle to open RFM device (I). Return Values Success RFM2G_SUCCESS Refer to the driver definition of RFM2G_STATUS for all other possible return values. Example RFM2GHANDLE rh;... printf( "The maximum size any event queue can be set to is %u.\n", RFM2gGetEventQueueMaxLimit( rh ) ); 66

67 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces RFM2gNevents() The RFM2gNevents() function returns the value of RFM2g interrupt event counters and can reset them. The RFM2g device driver counts each RFM2g interrupt event which it receives. An application program can use the RFM2gNevents() function to return the current event counts. In addition, the application can reset the counters using this function. Each counter is a 32-bit unsigned value. The counter wraps to zero (0) after it reaches its maximum value (2 32-1). Syntax Parameters BOOL RFM2gNevents( RFM2GHANDLE rh, RFM2gGETNEVENTS rge, ULONG clearthem ); rh rge clearthem Handle to open RFM2g device (I). The event counters to reset (I). Clears the interrupt event counters defined in rge (O). Return Values Success RFM2G_SUCCESS Refer to the driver definition of RFM2G_STATUS for all other possible return values. Example RFM2GHANDLE rh; RFM2gGetNevents_T rge; ULONG clearthem;... clearthem = 0; if( RFM2gNevents( rh, &rge, clearthem ) == TRUE ){ printf( There have been %lu RFM_EVENTID_1 events.\n, rge.rge_nevents[ RFM_EVENTID_1 ] ); } 67 FANUC Parts

68 Deprecated Windows API Functions 2 RFM2gReceiveEventFromQueue() The RFM2gReceiveEventFromQueue() function determines if an RFM2g interrupt event has been received. The application program blocks until the next RFM2g interrupt event of the requested type has been received, at which time the function returns. The queued version utilizes pending events in the event queue to fulfill requests. RFM2gReceiveEventFromQueue() uses a timeout parameter to wait (in milliseconds) for an event to arrive before returning. Specifying a timeout of 0 causes the function to return without waiting, while using the RFM2G_INFINITE parameter causes the function to never timeout. NOTE: The RFM2G_INFINITE parameter is not currently implemented. RFM2gReceiveEventFromQueue() returns the source node in the *fromnode parameter. It also return a result code with one of the following values: RM_SUCCESS - Function returned with an event RFM_TIMED_OUT - Function timed out RFM_IOCTL_ERROR - Internal library error Syntax ULONG RFM2gReceiveFromQueue( RFM2GHANDLE rh, RFMEVENTID event, UCHAR *fromnode, ULONG timeout ); STDRMNCALL rmnwaitforinterrupt( RMNHANDLE rh, RMNEVENTINFO *EventInfo ); Parameters rh *fromnode timeout Handle to open RFM2g device (I). The source node which is being requested (IO). Indicates which interrupt to wait on, and returns info about the received interrupt (IO). See the driver definition for RFM2GEVENTINFO for more information. Return Values Success RFM2G_SUCCESS Refer to the driver definition of RFM2G_STATUS for all other possible return values. 68

69 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces Example RFM2GHANDLE rh; UCHAR sourcenode; ULONG result;... result = RFM2gReceiveFromQueue( rh, RFM_EVENTID_1, &sourcenode, RFM_INFINITE ); if( result!= RFM_SUCCESS ) { printf( "We did not get an event back\n" ); } else { printf( "We received an event from node %d\n", sourcenode ); } 69 FANUC Parts

70 Deprecated Windows API Functions 2 RFM2gRegName() The RFM2gRegName() function returns the name of a specified RFM2g register by giving its offset. The hardware registers of the RFM2g interface are mapped into the memory space for the RFM2g board and are accessed as if they were ordinary memory locations. Since the entire RFM2g board space is mapped into the application program s memory space, the program can access the RFM2g board registers using simple memory references. The header file pci55xx_nt.h contains preprocessor definitions that supply symbolic names for the RFM2g device registers. An application program can use these definitions to access the RFM2g registers directly, however, the RFM2g hardware registers may change depending upon the RFM2g device model. Portable programs may wish to have the DLL provide the offset of the RFM2g register. Syntax Parameters char *RFM2gRegName( RFM2GHANDLE rh, unsigned offset ); rh offset Handle to open RFM2g device (I). Offset in Reflective Memory from which to read (I). Return Values Success RFM2G_SUCCESS Refer to the driver definition of RFM2G_STATUS for all other possible return values. Example RFM2GHANDLE rh; unsigned offset = 1;... printf( The name of the register at offset %u is %s.\n, offset, RFM2gRegName( rh, offset ) ); 70

71 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces RFM2gRegOffset() The RFM2gRegOffset() function returns the RFM2g offset which may be used to access the named RFM2g hardware register. NOTE: The specified register name is not case sensitive and must be the complete register name as given in the device driver s header file. Syntax Parameters unsigned RFM2gRegOffset( RFM2GHANDLE rh, char *regname ); rh *regname Handle to open RFM2g device (I). The hardware register for which the offset is requested (I). Return Values Success RFM2G_SUCCESS Refer to the driver definition of RFM2G_STATUS for all other possible return values. Example RFM2GHANDLE rh; char *regname = RFM2g_bid ;... printf( The %s register is at offset %u.\n, regname, RFM2gRegOffset( rh, regname ) ); 71 FANUC Parts

72 Deprecated Windows API Functions 2 RFM2gRegSize() The RFM2gRegSize() function returns the width of a named RFM2g hardware register. NOTE: See the description of the RFM2gRegOffset() function for additional details about RFM2g hardware register names. Syntax Parameters unsigned RFM2gRegSize( RFM2GHANDLE rh, char *regname ); rh *regname Handle to open RFM2g device (I). The hardware register for which the width is requested. Return Values Success RFM2G_SUCCESS Refer to the driver definition of RFM2G_STATUS for all other possible return values. Example RFM2GHANDLE rh; char *regname = RFM2g_bid ;... printf( The %s register is %u bytes wide.\n, regname, RFM2gRegSize( rh, regname ) ); 72

73 2 VMISFT/SW-RFM2G-ABC-940 Driver for the 2 GigaBaud Reflective Memory Interfaces RFM2gSetEventQueueLimit() The RFM2g device driver has a limit for the number of pending events of each event type for an application. The RFM2gSetEventQueueLimit() function determines the limit on the number of pending events for each event type. The function will return the current limit of events in the queue, or an error code if the call could not be completed. NOTE: This function is not currently implemented, and will return RFM2G_NOT_IMPLEMENTED if called. Syntax BOOL RFM2gSetEventQueueLimit( RFM2GHANDLE rh, RFMEVENTID event, ULONG limit ); Parameters rh event limit Handle to open RFM2g device (I). Which interrupt event queue to flush (I). See the driver definition for RFM2GETEVENTTYPE for valid values. The size of the event queue (I). Return Values Success RFM2G_SUCCESS Refer to the driver definition of RFM2G_STATUS for all other possible return values. Example RFM2GHANDLE rh; ULONG count;... count = RFM2gSetEventQueueLimit( rh, RFM_EVENTID_1, 46 ); 73 FANUC Parts

74 APPENDIX A Troubleshooting Guide Contents Symptoms and Possible Causes This appendix contains troubleshooting information for the VMISFT/SW-RFM2G-ABC-940 driver. 74

75 A VMISFT/SW-RFM2G-ABC-910 Driver for the 2 GigaBaud Reflective Memory Interfaces Symptoms and Possible Causes Symptom A a dialog box displays with the message Cannot open RFM file (\\.\rfm2g1)! when a program, such as the RFM2g Command Line Interpreter (rfm2gc_stdc), attempts to open the \\.\rfm2g device. Possible Cause The call to the rfm2gopen function in the RFM2GDLL_STDC Dynamic Link Library (DLL) failed because: The RFM card is not correctly jumpered and/or inserted into an appropriate PCI or PMC slot. Power down the system and confirm that the RFM card is correctly jumpered and/or properly inserted. See the product manual that came with the RFM card for more information. A previous version of the driver is installed on the system. 1. Verify no previous versions exist on the system using the Start > Settings > Control Panel > Add/Remove Programs command. If a copy is found, remove it. 2. (Optional but recommended) Search the system for files named PMC5565.SYS and RFM2gDLL_STDC.DLL and remove any copies that are found. 3. Reboot the system. 4. Install the new version of the driver. See "Installation" on page 8 for more information. The system may be running out of page table entries (PTEs), which are used to map the memory on the RFM card into the virtual address space of the Windows NT or Windows 2000 kernel. If there are not enough PTEs available, the RFM card cannot be opened. The number of available PTEs can be increased by changing the SystemPages registry value. See "Modifying the SystemPages Registry Key" on page 8 for more information. If your RFM card is still not functioning properly after completing the above steps, contact GE Fanuc Embedded Systems for further assistance. See "GE Fanuc Embedded Systems Technical Support" on page 7 for more information. 75 FANUC Parts

76 Symptoms and Possible Causes A Symptom The Windows NT 4.0 Event Viewer logs an event with the following information: Event ID: 7026 Source: Service Control Manager Type: Error Category: None Description: The following boot-start or system-start driver(s) failed to load: PMC5565 Possible Cause The RFM device driver did not properly detect and initialize the RFM card. This can occur for several reasons. Follow the procedures for the previous symptom. 76

77 A VMISFT/SW-RFM2G-ABC-910 Driver for the 2 GigaBaud Reflective Memory Interfaces 77 FANUC Parts

78 APPENDIX B Modification of the Driver for Specific Chipsets Contents Symptoms and Possible side effects

79 B VMISFT/SW-RFM2G-ABC-910 Driver for the 2 GigaBaud Reflective Memory Interfaces Symptoms and Possible side effects Installation Some system motherboards have exhibited PCI bus behavior that may cause the PCI bus to perform abnormally. The PCI/PMC 5565 is designed to meet the PCI 2.x compatible specification. An annomally as been noticed in motherboards where the PCI-5565 board is inserted into a PCI-X slot. When the PCI board is inserted into a PCI-X compatible slot, the PCI-X slot must modify the commnication protocol to operate in PCI 2.x mode. The problem has been seen when a reflective memory application is performing a massive amount of PIO operations. This folder contains custom, restricted registry entries. Do not install any of these files in the system registry unless instructed to do so by GE Fanuc Embedded Systems. Improper use of these files will result in system malfunction. This file must be renamed from the *.rege to *.reg suffix in order for the registry editor to interpret them properly. Description: File Name: rfm2g_marbr24.rege This modification is for system motherboards that are using: A) Serverworks "Grand Champion HE" or also known as GC-HE chipset This chipset is currently in the Dell 6600 series servers B) Intel 7505 This chipset is currently in the Dell 650 series servers C) Intel 7500 On the Gigabyte GA-8IPXDR and the Supermicro X5DAL motherboard. Other motherboards containing the Intel RG82861 Host Controller and FW82801CA I/O Controller Hub may require this registry entry. The custom registry files are delivered into the directory: <SystemDrive>\GEFANUC_ES\Rfm2g_Utilities\Restricted_Registry_Entries 1. Rename the file from rfm2g_marbr24.rege to rfm2g_marbr24.reg 2. Double click on the rfm2g_marbr24.reg file 3. The following pop up message will appear: 79 FANUC Parts

80 Symptoms and Possible side effects B Answer "Yes" 4. The following pop up message will appear; 5. You must reboot the system before the registry entries will be detected by the device driver. 80