See below ...
Regards,
Joe.
> -----Original Message-----
> From: Bernie [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, 14 November 2000 5:27
> To: 'arachne-development'
> Subject: Re: Outstanding bugs
>
> > I hope that at least some people will be
> > interested in eliminating these bugs, because they won't go away by
> > themselves ... :-(
>
> Are you sure? ;-)
>
[da Silva, Joe]
You're right, Bernie !!! ;-)
The "BMP file bug" _has_ fixed itself !!!
It turns out, the problem was PK(UN)ZIP V2.04g ...
The BMP files had been extracted from a ZIP file using
this version of PK(UN)ZIP, which resulted in spaces
within the 8.3 filenames! When I used Arachne to view
the directory, the BMP files "showed up", and I thought
the file names had an underscore (_), rather than a
space ... For some reason, when you then click on
the file's icon, Arachne just says it doesn't know how
to handle this file type - so this message mislead me
into thinking it really didn't know how to handle the
BMP file type ...
So the only bug here is the misleading error message
and the original problem, of using PK(UN)ZIP V2.04g ...
(I have now upgraded to PK(UN)ZIP V2.50 ... ;-)
----- snip -----
>
> > 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).
>
> file/.bmp isn't specified
> Add the following line to mime.cfg:
> file/.bmp BMP
>
> You should need to do this for GIFs as well... Hmm... I can't test much
> here at school - all I can do is run Arachnebasically and slow in NT :(
>
----- snip -----
