Remote Floppy Device Considerations

A remote floppy device enables a client running on a remote PC (not running on the Server) to use a local floppy device as a drive on the mvBase system.

Once a remote floppy device is configured to be an mvBase tape unit, tape commands operate in customary fashion for the local floppy drive. For example, when executing the T-STATUS command, a remote floppy is identified by the F# in the DRIVE column.
Any client that is running Windows can use a remote floppy device that is configured to be an mvBase tape unit. Drives resident on the system (e.g., A:, B:, etc.) may be added as remote floppy devices.
The Remote Floppy feature of the Tapes tab allows a client running on a remote PC to enable its own floppy drive to function as an mvBase tape unit.

NOTE	In the case of a Telnet client connected via mvTelnet, the floppy that is considered remote is the floppy where the mvBase Workstation is running.

When you use T-SELECT to select a remote floppy device, the client’s or Workstation’s PC floppy drive replaces drive A in the mvBase Server’s tape device table. The client may now use this floppy drive, rather than using the floppy drive located on the Server. Tape commands on the remote floppy function normally. When the user detaches from the remote floppy, the path to drive A is restored.

The remote floppy feature can create multiple aliases for a single floppy tape device. Consequently, while one user is T-ATTached to the floppy device, another user can T-ATTach to the same device using a different alias. However, the second user receives the DEVICE NOT READY message if attempting to access the floppy tape device. This same message displays if the device is in use by another program running on the host operating system.

NOTE	Once you define an mvBase tape unit of any type, mvBase considers that unit to be a tape device, hence you must use T-SELECT, T-ONLINE, T-REW and other tape-related commands in the customary sequence in order to perform normal tape device functions.