Unable to download files ( Sea Monkey 1.0) - Mozilla

This is a discussion on Unable to download files ( Sea Monkey 1.0) - Mozilla ; When clicking on any link containing downloadable file the following dialog box appears: ------------------------------------------------------------------------- C:\path\LOCALS~1\Temp\Filename.ext could not be saved because the source file could not be read. Try again or contact sys admin. ------------------------------------------------------------------------ This is on fresh install of ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Unable to download files ( Sea Monkey 1.0)

  1. Unable to download files ( Sea Monkey 1.0)

    When clicking on any link containing downloadable file the following
    dialog box appears:

    -------------------------------------------------------------------------
    C:\path\LOCALS~1\Temp\Filename.ext could not be saved because the source
    file could not be read.
    Try again or contact sys admin.
    ------------------------------------------------------------------------

    This is on fresh install of Seamonkey 1.0 ( Mozilla/5.0 (Windows; U;
    Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0)



    What am I doing wrong?

  2. Re: Unable to download files ( Sea Monkey 1.0)

    T.Rex wrote:
    > When clicking on any link containing downloadable file the following
    > dialog box appears:
    >
    > -------------------------------------------------------------------------
    > C:\path\LOCALS~1\Temp\Filename.ext could not be saved because the source
    > file could not be read.
    > Try again or contact sys admin.
    > ------------------------------------------------------------------------
    >
    > This is on fresh install of Seamonkey 1.0 ( Mozilla/5.0 (Windows; U;
    > Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0)
    >
    >
    >
    > What am I doing wrong?

    I have seen this problem with prior versions of the suite after doing an
    uninstall followed by a install without rebooting between the uninstall
    and the install. Just installing again, without an uninstall corrected
    this type of problem for me. This problem occurred intermittently and I
    was never able to pin down an exact sequence that would make a
    reproducible test case.
    Jim

+ Reply to Thread