Bug in 5.0.9344 Saving to Mapped drive

Discussion in 'Windows Virtual Machine' started by Ken1, Apr 3, 2010.

  1. Ken1

    Ken1 Member

    Messages:
    37
    What I am trying to do works prior to upgrading to 5.0.9344 and doesn't work after the upgrade. It is a simple thing.

    It is effectively a show-stopper for upgrading to 5.0.9344 for me (for the second time) and I am for the second time downgrading.

    OS X 10.6.3 (and 10.6.2)
    MBP May 2009
    WinXP Pro


    Situation:

    I. I have my Windows files on a Mac folder which has been mapped in Windows to be the W drive
    i.e. \\.psf\Win is mapped as W:\

    2. I open a file in Framemaker 6 from a folder on the W drive which if fine.

    3. I try to save the same file (just a periodic save) and I get the error pop-up

    "The W:\Movie Log.fm.F70 that FrameMaker wrote may be damaged."

    This is consistent and happens every time I attempt to save. It also occurs when I try to save the file to any of the psf shared folders.

    "the W:\My Documents\Publications\Reading Lists\Movie Log.fm.10C that FrameMaker wrote may be damaged."

    And what is with the "10C" or "F70" file suffixes???

    4. If I try to save by following the network links to the drive, rather than the mapped drive, I get the same error:

    i.e. "The \\.psf\Win\Movie Log.fm.617 that FrameMaker wrote may be damaged."

    5. I can save fine to a virtual drive within Windows. e.g. C or D.

    I have not encountered this error with any other application.

    What gives?

    No, it is NOT a problem with FrameMaker, it is something that was introduced in 9344.
     
  2. I-che

    I-che Pro

    Messages:
    492

Share This Page