HP NetServer AA 4000 HP NetServer AA 6200 Solution Release 3.0 Messages - Page 158

Chapter 9 MtcFLOP and MtcFLOR Messages IOPn.MtcFLOP status: The Floppy Provider attempted to attach a floppy device to the floppy driver's device object, but failed. As a result, that floppy device will be inaccessible. Severity Error Description One of the following problems has occurred: • The floppy device was not properly defined using the HP NetServer AA Configuration Utility. • The floppy driver could not find any floppy devices. • The floppy driver is not running. Action • Using the HP NetServer AA Configuration Utility, check the configuration information that you supplied for each floppy device. • Make any necessary corrections. • Remember that when you make a change using the HP NetServer AA Configuration Utility, you must make the same change on both IOPs. (The IOPs must contain identical configuration files.) Because any changes will not take effect until the IOP reboots, schedule an appropriate time to reboot the IOPs. • On the IOP where the floppy devices physically reside, use Start Setting Control Panel Devices and make sure that the "Floppy" is listed and shown as running. • Check the Event Viewer for a Windows NT message stating that the floppy driver failed to initialize. If this message was logged, Windows NT did not initialize the floppy driver. Refer to Windows NT documentation for information. IOPn.MtcFLOP status: The Floppy Provider attempted to create a floppy device, but failed. As a result, that floppy device will be inaccessible. Severity Error Description The floppy device failed initialization. This error usually occurs because the device is not configured properly. Action • Using the HP NetServer AA Configuration Utility, check the configuration information that you supplied for each floppy device. • Make any necessary corrections. Remember that when you make a change using the HP NetServer AA Configuration Utility, you must make the same change on both IOPs. (The IOPs must contain identical configuration files.) • Because any changes will not take effect until the IOP reboots, schedule an appropriate time to reboot the IOPs. 148