Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/104059

From BetaArchive Wiki
Knowledge Base

Article ID: 104059

Article Last Modified on 8/16/2005


  • Microsoft Schedule+ 1.0 Standard Edition
  • Microsoft Schedule+ 1.0a

This article was previously published under Q104059


In versions 1.0 and 1.0a of Microsoft Schedule+ for Windows, when you move your local schedule file (.CAL) to a floppy disk drive that does not contain a floppy disk and you subsequently insert a floppy disk to complete the move procedure, your local file is moved to an unspecified, seemingly random location (including one of the servers to which you are connected) instead of to the floppy disk.


To prevent this problem, be sure to insert a floppy disk into the drive before you choose the Move Local File command from the File menu in Schedule+ to move your local file to a floppy disk.


Microsoft has confirmed this to be a problem in Microsoft Windows versions 3.0 and 3.1. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


When you choose drive A as the destination drive for the move and no floppy disk is currently in that drive, you will receive the following message:

<filename> This file name is invalid.

When you insert a floppy disk and proceed with the move procedure, everything seems to work, until you try to find your local file. It may not be on the floppy disk after all; it may be on one of the servers you are currently connected to.

This behavior is not specific to Microsoft Schedule+. You will experience similar results with Windows Notepad. For example, if you are working with Notepad and attempt to save a Notepad file to a floppy disk drive using the Save As command from the File menu, the file may be saved in a random location if there is no floppy disk in the drive.

Additional query words: schedule plus 1.00 1.00a misplaced missing

Keywords: KB104059