Well, there are a number of things that could be causing this little program to not function correctly.
The biggest problem is that Netscape's and Microsoft's "applet accelerators" seem to take some shortcuts they shouldn't be taking,
and the effect on the code is not unlike the effect on JPEGs when the compression is too high:
It just doesn't cut it.
So, ever since version 3 beta 4 of Netscape Navigator,
and version 4.0 of µsoft's IE, Java applets have not behaved at all like they do in
Sun's JDK; or
µsoft's Internet Explorer 3.0,
Sun's HotJava, or even
Netscape's browsers on UNIX.
Very soon an Amiga browser that supports Java will be available.
I do hope it functions properly....
It
had come to be my theory that Netscape's primary programmer had been promoted.
I felt that this would explain the sudden loss of functionality in what had been turning out to be a keen browser.
Later, I discovered that that was apparently precisely what happened.
Following is a list of things that Netscape Navigator
was able to do in previous versions, but not since:
-
Java applets in general, though only some are trashed in subtle, but effective ways
-
Display images via MIMEtypes.
Binary files without an "appropriate" filename extension (a convention of CP/M, carried over to MS-DOS, and otherwise not really used) are no longer checked for their MIMEtype, which means
-
a GIF (or any binary) named "sambone" becomes
.
-
a JPEG named "sambone.gif" becomes
.
-
a GIF named "sambone.jpeg" becomes
.
As you see, it still does it for erroneous extensions, but for no extensions, it fails to do it.
...unless the extensionless file is pulled from the cache.
Then it processes the image according to its MIMEtype.
Figure that one out.
:^)
Incidentally, IE can't do MIMEtypes correctly, either, even though Windows 95+ and NT 4.0+ have provisions to deal with them — typical µsoft, in my experience.
Please forgive my pontification. :^)