Hi folks.
Given that there are now a few more people involved in the development
of Arachne (as well as Michael, of course), I thought I should post here
a _reminder_ of bugs that were reported at V1.66 _or_earlier_, but have
*still not been addressed*!!! I hope that at least some people will be
interested in eliminating these bugs, because they won't go away by
themselves ... :-(
As you can see, there's a "fair number" of bugs outstanding here, and
I haven't even mentioned those introduced with V1.67 (after all, I don't
expect immediate bug fixes - just that they be fixed in due course ...)
Best regards,
Joe.
1. XSWAP CRASH :
================
On Thu, 13 Jul 2000 17:54:56 +1000, da Silva, Joe wrote:
> This is cool - I've just seen my first "xSwap" crash (Arachne
V1.64 for
> DOS)!
> Hey ... at least this type of crash doesn't lock-up my machine!
;-)
> Error Message :
> Memory allocation error - Illegal xSwap operation at line 222 of
file
> URLOVRL.C!
> Trying to deallocate xSwap ... ok
> This crash occurs consistently for me when I try to look at the
URL :
> "http://www.freeonline.com.au/corporate/connect.html".
********** Glenn reported : **********
Here's the problem, (https)
<td width="30"><img height="20" width="222"
src="https://www.freeonline.com.au/preregister/images/capture12.gif"
align="right"></td>
The resutling "unknown protocol in URL" instead of an image is
what's
causing the at http://www.freeonline.com.au/corporate/connect.html
2. VIEWING LOCAL 'BMP' FILES :
==============================
When I use Desktop - All Files, then click on any BMP
files on the drive, Arachne says it doesn't know how to
handle them. This is strange, because I'm sure Arachne
has native support for both BMP and GIF (no such
problem clicking on GIF files, BTW).
3. CORRUPT HYPERLINKS :
=======================
a) Go to "http://www.newark.com/".
b) In the Search dialogue, search for the Manufacturer's
Part Number "2N3055".
c) Now, on the Search Results page, click on the
"09F5475" hyperlink.
This hyperlink fails, with the Address line showing :
" ... ID=250&VID=250&10005=09F5475",
instead of the *correct* address :
" ... ID=250&VID=250&10005=09F5475" .
You will notice that Arachne's Address line has an
extra "amp;" after each "&" (if you edit the Address
line to delete the extra characters, it then works).
Also, if you try IE(5), the hyperlink works as expected.
BTW, I chose just one example above - I think all
similar hyperlinks at this URL give the same problem.
4. DISK ACTIVITY AFTER LOADING URL :
====================================
On 2000/08/04, I wrote :
Yes Eino, there *is* a problem here ... I tried this
with V1.66 and got the same thing.
In fact, when I pressed "break", closed down Arachne
and restarted it, Arachne's pages (eg. Desktop) were
*very* slow and had *lots* of disk activity! Nothing
strange reported by "mem", yet I had to reboot before
Arachne worked normally again. Strange!!!
Regards,
Joe.
PS. Good job Michael - I just installed 1.66 and
many of those "silly" little problems (such as
garbage "quick start" file name) are now finally
fixed!
____
| From: [EMAIL PROTECTED]
| To: [EMAIL PROTECTED]
| Cc:
| Sent: 22 July, 2000 05:14 AM
| Subject: Loading a certain page..
|
|
|
| Trying to load this page:
| http://members.theglobe.com/saregist/
| from The Net has my DOS Arachne 1.64 "loading page
| from disk" for,
| I guess, eternity. I Ctrl-break at the point in which
| it's starts
| swapping? with my HD.
|
| Anyone else get the same result?
5. TRUNCATED DOMAIN NAMES :
===========================
There is a problem with long domain names, in that Arachne
truncates them to *just* 40 characters! As another user
reported (complained) to me ... :
My colleague here was trying this address:
http://www.supercatjaguarspares.freeserve.co.uk
...and getting very frustrated. I felt guilty, since he was trying
it on my behalf. Eventually, we noticed that the 'k' of '.uk' was going
AWOL and we never got to the site. He reported this to the list and
Michael's attitude seemed to be that it wasn't worth making Arachne
conform to the standard for URL lengths because addresses that long
wouldn't occur very often.
