2.3.1 -
NCSA Mosaic for MS Windows, 2.0.0 Final version, cannot save
forms output to a file.
(yangw@dolphin.upenn.edu 10/19/95)
(rcg8@phppo1.em.cdc.gov 10/20/95)
The problem occurs only with forms output, not with ordinary HTML pages.
(The same problem occurs with MS Windows Netscape, but not with Mac
Netscape or XWindows UNIX Netscape.)
To see the problem, try the following
LOOKUP example.
Bob Peterson (mosaic-w@ncsa.uiuc.edu) was notified on 10/20/95.
He replied on 11/20/95 that he cannot reproduce the problem.
Forwarded his response to yangw@dolphin.upenn.edu and rcg8@phppo1.em.cdc.gov,
with a request that they correspond directly.
Robert Gersoff (rcg8@phppo1.em.cdc.gov) confirmed that the problem still
existed with MS Windows Mosaic version 2.0.0b3 build 128.
This bug is fixed in Mosaic 2.1.1 (at least for Windows 95).
Upgrade to the latest version of Mosaic.
2.3.2 -
NCSA Mosaic for MS Windows, 2.0.0 Final Beta version, gives the following
error:
"An error has occurred with this server. Exit val: 134."
The bug occurs with a simple
LOOKUP example.
(rcg8@phppo1.em.cdc.gov MS Windows Mosaic 2.0.0B3 and 2.0.0B4 7/20/95)
(dwmerrill@lbl.gov MS Windows Mosaic 2.0.0B4 and 2.0.0 Final Beta 7/20/95)
(CPU@marsh.vinu.edu 7/25/95)
(pat.jakobi@utmb.edu 7/25/95)
(Brian C. Martinson *@co.hennepin.mn.us 8/4/95)
(aleson@ix.netcom.com 8/9/95)
(johnm@uwsi.com 8/10/95)
(upl.com@upl.com 8/16/95)
(mroimc_12778.mro.usace.army.mil 8/16/95)
(rmorgan@mednet.med.miami.edu 8/18/95)
(mcoletti@omni.voicenet.com 8/19/95)
(msimle@ci.madison.wi.us 8/28/95)
(childres@sun1.its.state.ms.us 9/6/95)
(yangw@dolphin.upenn.edu 9/15/95)
(wernettd@smtplink.dis.anl.gov 9/15/95)
(PALERMO@mdh-chs.health.state.mn.us 9/18/95)
(jennifer_phillips@thoth.sra.com 10/27/95)
(gjs8@pge.com 11/1/95)
This bug does not occur with X Windows Mosaic 2.4.
This bug occurs with all three LOOKUP servers (cedr, bigsur, census).
It occurs also with STF1A (all places in Rhode Island).
This bug does not occur with X Windows Mosaic 2.4.
This bug does not occur with Mosaic 2.1.1 for Windows95.
Upgrade to the latest version of Mosaic.
The Mosaic developers at mosaic-w@ncsa.uiuc.edu were notified on 7/20/95,
again on 8/4/95, again on 8/10/95, and again on 8/28/95.
As of 8/10/95 they were investigating the problem.
On 9/13/95 Technical Support Representative Bob Petersen
(mosaic-win@ncsa.uiuc.edu) reported that the problem
would be fixed in version 2.0 final.
On 9/28/95 Judd Weeks (jweeks@ncsa.uiuc.edu) reported that the
bug is fixed
on build 128 and later of version 2.0.0 Final.
On 10/14/95 Technical Support Representative
Bob Peterson (mosaic-win@ncsa.uiuc.edu)
reported that
all known problems with LOOKUP are fixed
in version 2.0 Final.
Will Mosaic users please confirm?
Upgrade to the latest version of Mosaic.
2.3.3 -
NCSA Mosaic 2.0a5 for MS Windows does not work with LOOKUP.
(chris.stuber@census.gov 5/7/95)
(dwmerrill@lbl.gov 5/22/95)
Trying to select counties of California in STF3A, response is:
'HTAccess: Error accessing "http://parep2.lbl.gov/mpub/cdrom/img/warning.gif":
"HTTP: Error response from server"'; then 'CGI Server ERROR:
"Found a selection w/invalid value. (field #1 of SEL='California' is bad.)"'
Mosaic 2.0.a5 did not handle SELECT tags properly. It stripped
out some necessary information, apparently ignoring the VALUE tag
contained within each selection. A similar problem occurs
with older versions of MacWeb.
This bug is fixed in MS Windows Mosaic version 2.0.0b4.
(csamos@ncsa.uiuc.edu 5/22/95).
Upgrade to the latest version of Mosaic.
2.3.4 - Mosaic/2.1 (Windows x86) gives an error:
Found a selection w/ invalid value. (field #1 of
SEL='Pierce County' is bad.)
(jim@bigone.ca.boeing.com 3/14/96)
The bug was reported to mosaic-win@ncsa.uiuc.edu on 3/14/96.
This bug does not occur with Mosaic 2.1.1, at least for Windows95 (4/2/96).
Upgrade to the latest version of Mosaic.
2.3.5 -
With X11 ULTRIX Mosaic, when requesting multiple lines of data,
frequently some lines of output get lost.
For example, one might have requested data from
five counties, and get the data for three. If one then requests
the data for the missing counties, one gets them, which suggests
that it isn't a data retrieval problem, but a program
bug. Also, sending the same request does not always generate
the same result, or even the same number of lines. If one needs only
a few lines of data, this is not much of a
problem to check by hand, but when one sends a request that is
several hundred lines long, and has half of them lost,
comparing the result with the request becomes more tedious.
Perhaps Lookup should compare the number of lines in the request and in
its answer, and act accordingly.
dsussman@mit.edu on 2/5/96 with NCSA_Mosaic/2.6 (X11;ULTRIX 4.2 RISC)
Can anyone else confirm the existence of this bug?
This bug was reported on 2/5/96 to softdev@ncsa.uiuc.edu.
Upgrade to the latest version of Mosaic.
back to browser bugs affecting Lookup