More on PUT corruption

Found out today that the problem I am having seems to
be because of something on my home system. I did not
have the problem at all at work, everything worked as
it was supposed to.

So, then I found that my JDK at home was an older 1.3
Release candidate, so I un-installed it and installed
the same JDK as on my work computer, which is 1.3.0_01.

So now the only difference I can tell between the 2
systems is that one is Windows 2000 (the one that works),
and the other one is WinNT 4.0 SP 6. I have found I even
get the corruption using Winie's JWPut command line
interface to upload a file now.

I have also noticed that I also have some graphics refresh
errors on my swing components, especially the menu bar,
even with the new JDK installed.

I see to actually be getting more errors using jwput
than my own program, even after upgrading the JDK and
rebooting. Funny, the connection at work is a full
100Mb, you'd think the faster transfer might be more
prone to such errors! Yet the slower, 128Kb connection
is the one giving me problems!

Since this only appears to happen to me when trying
to use the w3c client lib, is there some way I can tell
it to do more error checking or something? Until this is
resolved, I huess it's back to using native libcurls
to do my uploads, as it hasn't failed yet.

Bob Schader

Received on Tuesday, 27 February 2001 07:45:43 UTC