Thanks to all who responded to my plea for help with the problem of not being
able to run class files generated under linux under Win95, while if the same
files were recompiled under Win95, they run fine.
However, most of your proposed solutions fall wide of the mark.
1) Classpath is irrelevant since the Classpath under Win95 is the same
regardless of whether the copied .class files or newly compiled .class files
are run.
2) Many wrote about the difficulties with copying files between the two
systems. This is not relevant either, since the files actually copied are jar
files containing the class files. This should be equivalent to zipping the
files.
3) Others have asked how the files were transferred. My results are the same
using binary-mode FTP or passing data by floppy disk.
4) Other points made about 8.3 file names or wrong-case filenames do not seem
to apply here
either, especially because the means of transmission was a jar file which
preserved case names.
Now here is a detail that may be more relevant:
There are 19 .java files in the package. The compilation under linux is making
them into 19 class files. When compiling under Win95, 27 class files are
created. Two of these are for non-public classes defined in other java files.
The other six files have names like xxxxx$1.class where xxxxx.java is one of my
project files (xxxxx.class is also created by the compilation). I don't know
what these extra files are for, but the NoClassDefFoundError message is telling
me that the class it cannot find is xxxxx$1. The extra files do not seem to be
required under the linux environment, but they appear necessary under the Win95
environment.