[Prev][Next][Index][Thread]
Bug(???) found in Executor/Linux 1.99q7
I think, though I cannot be certain, that I have found a bug in Executor
1.99q7/Linux. (running on an Intel 486DX4/100 running FreeBSD 2.1)
Note - I'm not sure if this is a FreeBSD problem or a genuine Executor
problem, and I can't find out, because I don't have any Linux machines
here to test on. If possible would someone at ARDI (or another person
out there on the net) test this out for me please?
I'm running MSword 5.1a and am unable to access a file. Yes, it is a
properly formatted Word file, the filetype is proper (WDBN/MSWD) -- I
basically just created this file, saved it, and exited both Word and
Executor. When I came back later to work on it, I cannot open the file
(It does not appear at all in the "Open" dialog box). HOWEVER, if I use
the "quick open" menu in Word (in the File menu, where it shows the last
X documents you've worked with) the file appears there, and I am able to
load it that way.
This is definitely weird.
I'm using the file off directly off of the UNIX filesystem. It's not in
a HFV or anything.
The filename is:
FAQ- Running Executor under FreeBSD
which, I believe, is a right and proper Mac filename.
Attached, is a .tar.gz of the file in question (both data and resource
forks, of course).
I'd appreciate hearing back from you as to whether or not I've found a
real bug, or if I'm doing something screwy. Thanks!
Donald Burr [d_burr@ix.netcom.com], PO Box 91212, Santa Barbara CA 93190-1212
TEL (805)564-1871 / FAX 564-2315 / WWW http://www.geopages.com/WallStreet/2072
PGP Public Key available by request (send e-mail) or on Public Key Servers.
** Uphold your right to privacy - Use PGP. **
badfile.tar.gz