FireFTP problem - OS2

This is a discussion on FireFTP problem - OS2 ; For some reason, FireFTP seems to always capitalize the extension on files it uploads despite being told to "leave case alone" in the site set up. Is there a way to prevent that? It breaks completely Unix hosts. The FTP-PM ...

+ Reply to Thread
Results 1 to 19 of 19

Thread: FireFTP problem

  1. FireFTP problem


    For some reason, FireFTP seems to always capitalize the extension on files
    it uploads despite being told to "leave case alone" in the site set up. Is
    there a way to prevent that? It breaks completely Unix hosts.

    The FTP-PM does not have that problem, so I don't think it's a host bug.

    Thanks,

    Pierre
    --
    Pierre Jelenc
    The Gigometer www.gigometer.com
    Home Office Records www.homeofficerecords.com

  2. Re: FireFTP problem

    On Fri, 19 Oct 2007 19:28:57 UTC, rcpj@panix.com (Pierre Jelenc) wrote:

    > For some reason, FireFTP seems to always capitalize the extension on files
    > it uploads despite being told to "leave case alone" in the site set up. Is
    > there a way to prevent that? It breaks completely Unix hosts.
    >
    > The FTP-PM does not have that problem, so I don't think it's a host bug.


    When I looked at the settings for my site, I found that upload was set
    to "always lowercase" while download was "leave alone". After i changed
    the upload setting, I did some tests and got the expected results: case
    was preserved on uploads.

    Double/triple check your settings & if that doesn't resolve the issue,
    locate fireFTPsites.dat in your profile. Therein, you'll find these
    settings: [...] downloadcasemode:"0", uploadcasemode:"0" [...]
    Make sure both at set as shown (i.e. to zero).

    BTW... I'm using v0.97.1 (the latest) with PmWFx 2.0.0.6.


    --
    == == almost usable email address: rws AT e-vertise.com == ==
    __________________________________________________ _________________
    |
    | Remote Workplace Server v0.80
    Rich Walsh | interact with the WPS from any program
    Ft Myers, FL | http://e-vertise.com/rws/rws080.zip
    __________________________________________________ _________________

  3. Re: FireFTP problem

    On Sat, 20 Oct 2007 02:47:26 UTC, "Rich Walsh" wrote:
    > On Fri, 19 Oct 2007 19:28:57 UTC, rcpj@panix.com (Pierre Jelenc) wrote:
    >
    > > For some reason, FireFTP seems to always capitalize the extension on files
    > > it uploads despite being told to "leave case alone" in the site set up. Is
    > > there a way to prevent that? It breaks completely Unix hosts.
    > >

    > After I changed the upload setting, I did some tests and got the expected
    > results: case was preserved on uploads.


    Let me take that back :-( Later on I reopened FireFTP, uploaded a web page,
    and found it had capitalized the '.HTML'. No amount of screwing around would
    fix it, so I gave in & returned the upload setting to "always lowercase".

    FWIW... this bug was reported to FireFTP's author on 2007-01-23.
    (https://www.mozdev.org/bugs/show_bug.cgi?id=16266). I just added another
    comment to remind him that the problem persists.


    --
    == == almost usable email address: rws AT e-vertise.com == ==
    __________________________________________________ _________________
    |
    | Remote Workplace Server v0.80
    Rich Walsh | interact with the WPS from any program
    Ft Myers, FL | http://e-vertise.com/rws/rws080.zip
    __________________________________________________ _________________

  4. Re: FireFTP problem

    Rich Walsh writes:
    >
    > FWIW... this bug was reported to FireFTP's author on 2007-01-23.
    > (https://www.mozdev.org/bugs/show_bug.cgi?id=16266). I just added another
    > comment to remind him that the problem persists.


    Thanks. I had tried to look through the bug reports but I never got a
    complete list, there was something timing out.

    Pierre
    --
    Pierre Jelenc
    The Gigometer www.gigometer.com
    Home Office Records www.homeofficerecords.com

  5. Re: FireFTP problem

    On Sat, 20 Oct 2007 22:35:05 UTC, rcpj@panix.com (Pierre Jelenc) wrote:
    > Rich Walsh writes:


    > > FWIW... this bug was reported to FireFTP's author on 2007-01-23.
    > > (https://www.mozdev.org/bugs/show_bug.cgi?id=16266). I just added
    > > another comment to remind him that the problem persists.

    >
    > Thanks. I had tried to look through the bug reports but I never got a
    > complete list, there was something timing out.


    Peter W. just released new versions of the mozapps. In his notes,
    he mentions this:

    > Three small OS/2 specific changes were done:
    > [snip]
    > - File extensions of downloaded files are no longer uppercased


    I installed his new FF, created a new profile, then reinstalled
    FireFTP. I did a series of tests (rather than just one like last
    time), and it __seems__ like the problem may be solved.

    You can get his versions from: http://pmw-warpzilla.sf.net/


    --
    == == almost usable email address: rws AT e-vertise.com == ==
    __________________________________________________ _________________
    |
    | Remote Workplace Server v0.80
    Rich Walsh | interact with the WPS from any program
    Ft Myers, FL | http://e-vertise.com/rws/rws080.zip
    __________________________________________________ _________________

  6. Re: FireFTP problem

    On Fri, 19 Oct 2007 19:28:57 UTC, rcpj@panix.com (Pierre Jelenc) wrote:

    >
    > For some reason, FireFTP seems to always capitalize the extension on files
    > it uploads despite being told to "leave case alone" in the site set up. Is
    > there a way to prevent that? It breaks completely Unix hosts.
    >
    > The FTP-PM does not have that problem, so I don't think it's a host bug.
    >
    > Thanks,
    >
    > Pierre


    I think I was the first to report the bug to the author. The reply
    indicated that it was an OS/2 issue. I don't believe that. All of my
    other FTP clients work correctly.

    --
    Chuck McKinnis
    mckinnis@sandia.net
    http://7cities.net/~mckinnis/

  7. Re: FireFTP problem

    In , "Chuck McKinnis" writes:
    >On Fri, 19 Oct 2007 19:28:57 UTC, rcpj@panix.com (Pierre Jelenc) wrote:
    >
    >>
    >> For some reason, FireFTP seems to always capitalize the extension on files
    >> it uploads despite being told to "leave case alone" in the site set up. Is
    >> there a way to prevent that? It breaks completely Unix hosts.
    >>
    >> The FTP-PM does not have that problem, so I don't think it's a host bug.
    >>
    >> Thanks,
    >>
    >> Pierre

    >
    >I think I was the first to report the bug to the author. The reply
    >indicated that it was an OS/2 issue. I don't believe that. All of my
    >other FTP clients work correctly.


    I received the same response. Interestingly, it
    works correctly on some hosts, but not on others. When
    uploading whole directories, case is always preserved,
    but on single files, it is upper cased.

    Baden


    >--
    >Chuck McKinnis
    >mckinnis@sandia.net
    >http://7cities.net/~mckinnis/




    -----------------------------------------------------------
    Let Ignorance and Intolerance Rule!

    Baden Kudrenecky
    baden@baden.nu
    http://baden.nu/
    -----------------------------------------------------------



  8. Re: FireFTP problem

    On Tue, 23 Oct 2007 07:16:56 UTC, Baden Kudrenecky wrote:

    > >I think I was the first to report the bug to the author. The reply
    > >indicated that it was an OS/2 issue. I don't believe that. All of my
    > >other FTP clients work correctly.

    >
    > I received the same response. Interestingly, it
    > works correctly on some hosts, but not on others. When
    > uploading whole directories, case is always preserved,
    > but on single files, it is upper cased.


    You guys should really forward stuff like that to the Warpzilla
    newsgroup! Or even open bugs about it at Bugzilla. While I am not really
    good at fixing bugs at least it would get my attention. If I don't hear
    anything I just assume that everybody is happy!
    Luckily this seems to have been fixed as a side-effect of another fix as
    Rich noticed.
    --
    Greetings, | My From: address is valid as is the version without "spam"
    Peter. | I try to find real messages among the spam once a week

  9. Re: FireFTP problem

    On 10/23/07 02:30 pm, Peter Weilbacher wrote:

    > While I am not really good at fixing bugs at least it would get my attention.


    Peter, you are too modest!

  10. Re: FireFTP problem

    Hi Peter:

    Well, the new Mozilla 1.5 will not even start on my
    3.0 system. I initially didn't have the new libc DLLs
    installed, but after they were, 1.5 attempted to start,
    but never came to the desktop, even though it was on
    the tasklist.

    Referring to bugs, Java has never been as stable on
    Mozilla, as it was on Netscape 4.61. I am unsure
    whether this is due to the Java 1.3.1 or browser code,
    but Java 1.1.8 on Netscape was bomb-proof in
    comparison. 1.3.1 is pretty flaky.

    thanks a lot,
    lin Baden


    In , "Peter Weilbacher" writes:
    >On Tue, 23 Oct 2007 07:16:56 UTC, Baden Kudrenecky wrote:
    >
    >> >I think I was the first to report the bug to the author. The reply
    >> >indicated that it was an OS/2 issue. I don't believe that. All of my
    >> >other FTP clients work correctly.

    >>
    >> I received the same response. Interestingly, it
    >> works correctly on some hosts, but not on others. When
    >> uploading whole directories, case is always preserved,
    >> but on single files, it is upper cased.

    >
    >You guys should really forward stuff like that to the Warpzilla
    >newsgroup! Or even open bugs about it at Bugzilla. While I am not really
    >good at fixing bugs at least it would get my attention. If I don't hear
    >anything I just assume that everybody is happy!
    >Luckily this seems to have been fixed as a side-effect of another fix as
    >Rich noticed.
    >--
    >Greetings, | My From: address is valid as is the version without "spam"
    > Peter. | I try to find real messages among the spam once a week




    -----------------------------------------------------------
    Let Ignorance and Intolerance Rule!

    Baden Kudrenecky
    baden@baden.nu
    http://baden.nu/
    -----------------------------------------------------------



  11. Re: FireFTP problem

    On Wed, 24 Oct 2007 19:18:25 UTC, Baden Kudrenecky wrote:

    > Hi Peter:
    >
    > Well, the new Mozilla 1.5 will not even start on my
    > 3.0 system. I initially didn't have the new libc DLLs
    > installed, but after they were, 1.5 attempted to start,
    > but never came to the desktop, even though it was on
    > the tasklist.


    I was really talking about reporting bugs in recent products (not
    browsers that have been obsolete for 5 years)!

    > Referring to bugs, Java has never been as stable on
    > Mozilla, as it was on Netscape 4.61. I am unsure
    > whether this is due to the Java 1.3.1 or browser code,
    > but Java 1.1.8 on Netscape was bomb-proof in
    > comparison. 1.3.1 is pretty flaky.


    That may be a bug but so vague that there isn't anything that a
    developer can do about it. I find Innotek's 1.4.2.09 plugin fairly
    stable (more so than GCs 1.4.1, which I use for programs on my desktop).
    --
    Greetings, | My From: address is valid as is the version without "spam"
    Peter. | I try to find real messages among the spam once a week


  12. Re: FireFTP problem

    On 10/24/07 12:18 pm, Baden Kudrenecky wrote:

    > Well, the new Mozilla 1.5 will not even start on my
    > 3.0 system. I initially didn't have the new libc DLLs
    > installed, but after they were, 1.5 attempted to start,
    > but never came to the desktop, even though it was on
    > the tasklist.


    I'm hoping you mean Seamonkey 1.1.5, not Mozilla 1.5. I'd start by
    trying it with a new profile.

    > Referring to bugs, Java has never been as stable on
    > Mozilla, as it was on Netscape 4.61. I am unsure
    > whether this is due to the Java 1.3.1


    As suggested by Peter, the Innotek Java 1.4.2 plugin is probably your
    best bet.

  13. Re: FireFTP problem

    In <5BUTi.13668$lD6.11367@newssvr27.news.prodigy.net>, Steve Wendt writes:
    >On 10/24/07 12:18 pm, Baden Kudrenecky wrote:
    >
    >> Well, the new Mozilla 1.5 will not even start on my
    >> 3.0 system. I initially didn't have the new libc DLLs
    >> installed, but after they were, 1.5 attempted to start,
    >> but never came to the desktop, even though it was on
    >> the tasklist.

    >
    >I'm hoping you mean Seamonkey 1.1.5, not Mozilla 1.5. I'd start by


    Exactly. {:-)

    >trying it with a new profile.


    Everything was brand new, and it didn't even get to
    the profile window. I may have to wait until I re-boot
    for different DLLs to load.

    >> Referring to bugs, Java has never been as stable on
    >> Mozilla, as it was on Netscape 4.61. I am unsure
    >> whether this is due to the Java 1.3.1

    >
    >As suggested by Peter, the Innotek Java 1.4.2 plugin is probably your
    >best bet.


    I am not aware of any Java 1.4 that works on 3.0.

    thanks,
    Baden


    -----------------------------------------------------------
    Let Ignorance and Intolerance Rule!

    Baden Kudrenecky
    baden@baden.nu
    http://baden.nu/
    -----------------------------------------------------------



  14. Re: FireFTP problem

    On 10/24/07 11:59 pm, Baden Kudrenecky wrote:

    >>> Well, the new Mozilla 1.5 will not even start on my
    >>> 3.0 system.

    >> I'm hoping you mean Seamonkey 1.1.5, not Mozilla 1.5.

    >
    > Exactly. {:-)


    Hmm... now that the high-memory support is there, it may only run on
    Warp 4.5 now.

    > Everything was brand new, and it didn't even get to
    > the profile window. I may have to wait until I re-boot
    > for different DLLs to load.


    Unless you have SYS2070 errors in popuplog.os2, that's probably not the
    problem.

    > I am not aware of any Java 1.4 that works on 3.0.


    I thought someone had gotten it working, but I don't pay too much
    attention to those posts...

  15. Re: FireFTP problem

    On 10/25/07 08:54 pm, Steve Wendt wrote:
    > On 10/24/07 11:59 pm, Baden Kudrenecky wrote:
    >
    >>>> Well, the new Mozilla 1.5 will not even start on my
    >>>> 3.0 system.
    >>> I'm hoping you mean Seamonkey 1.1.5, not Mozilla 1.5.

    >>
    >> Exactly. {:-)

    >
    > Hmm... now that the high-memory support is there, it may only run on
    > Warp 4.5 now.
    >
    >> Everything was brand new, and it didn't even get to
    >> the profile window. I may have to wait until I re-boot
    >> for different DLLs to load.

    >
    > Unless you have SYS2070 errors in popuplog.os2, that's probably not the
    > problem.
    >
    >> I am not aware of any Java 1.4 that works on 3.0.

    >
    > I thought someone had gotten it working, but I don't pay too much
    > attention to those posts...


    Perhaps using this package
    http://hobbes.nmsu.edu/pub/os2/win32os2/warp_3_fix.zip?
    Dave


  16. Re: FireFTP problem

    In , Dave Yeo writes:
    >On 10/25/07 08:54 pm, Steve Wendt wrote:
    >> On 10/24/07 11:59 pm, Baden Kudrenecky wrote:


    >Perhaps using this package
    >http://hobbes.nmsu.edu/pub/os2/win32os2/warp_3_fix.zip?
    >Dave


    Thanks very much! I will have to give it a try!

    lin Baden

    -----------------------------------------------------------
    Let Ignorance and Intolerance Rule!

    Baden Kudrenecky
    baden@baden.nu
    http://baden.nu/
    -----------------------------------------------------------



  17. Re: FireFTP problem

    Hi Peter:

    On a whim, I decided to download the 'official' new
    1.1.5 Seamonkey, and it ran fine, where the one you
    compiled will not start at all on 3.0 FP_40.

    thanks,
    lin Baden


    In , "Peter Weilbacher" writes:
    >On Wed, 24 Oct 2007 19:18:25 UTC, Baden Kudrenecky wrote:
    >
    >> Hi Peter:
    >>
    >> Well, the new Mozilla 1.5 will not even start on my
    >> 3.0 system. I initially didn't have the new libc DLLs
    >> installed, but after they were, 1.5 attempted to start,
    >> but never came to the desktop, even though it was on
    >> the tasklist.

    >
    >I was really talking about reporting bugs in recent products (not
    >browsers that have been obsolete for 5 years)!
    >
    >> Referring to bugs, Java has never been as stable on
    >> Mozilla, as it was on Netscape 4.61. I am unsure
    >> whether this is due to the Java 1.3.1 or browser code,
    >> but Java 1.1.8 on Netscape was bomb-proof in
    >> comparison. 1.3.1 is pretty flaky.

    >
    >That may be a bug but so vague that there isn't anything that a
    >developer can do about it. I find Innotek's 1.4.2.09 plugin fairly
    >stable (more so than GCs 1.4.1, which I use for programs on my desktop).
    >--
    >Greetings, | My From: address is valid as is the version without "spam"
    > Peter. | I try to find real messages among the spam once a week
    >




    -----------------------------------------------------------
    Let Ignorance and Intolerance Rule!

    Baden Kudrenecky
    baden@baden.nu
    http://baden.nu/
    -----------------------------------------------------------



  18. Re: FireFTP problem

    Sir:

    Baden Kudrenecky wrote:
    > Hi Peter:
    >
    > On a whim, I decided to download the 'official' new
    > 1.1.5 Seamonkey, and it ran fine, where the one you
    > compiled will not start at all on 3.0 FP_40.
    >


    I'd sooner believe that you don't have the prerequisites in Warp version
    3 to run a build that uses "high memory".
    --
    Bill
    Thanks a Million!

  19. Re: FireFTP problem

    On Mon, 29 Oct 2007 09:06:14 UTC, Baden Kudrenecky wrote:

    > On a whim, I decided to download the 'official' new
    > 1.1.5 Seamonkey, and it ran fine, where the one you
    > compiled will not start at all on 3.0 FP_40.


    I'm not surprised to hear that. As Bill says, the high-memory feature is
    unlikely to work on Warp3. And I have heard of additional problems with
    the current v0.6.x C library on such an old system. So either stick with
    Warp3 and run official binaries linked against libc05*.dll (the 1.1.x
    line will be the last of those, SeaMonkey 2.0 will always be linked
    against libc06*.dll or newer) or update to Warp4 or eCS.
    --
    Greetings, | My From: address is valid as is the version without "spam"
    Peter. | I try to find real messages among the spam once a week


+ Reply to Thread