| From: | David Oakes |
| Date: | 11 Jul 2001 at 12:58:55 |
| Subject: | Re: [D5] Error msg:Packet request type unknown |
Bruner, Todd said to 'dopus5@lss.com.au':
BT> Recently I have received the following error message when I
BT> double click on a file which is of ASCII file type:
BT> Packet request type unknown
BT>: System/utilities/mulitview fatal error code 20
Personally, I much prefer having smartread display ascii/text files.
I know it is a personal preference, but it does work much more often
than multiview. Multiview is at best a very buggy program. I have
Uniview set up for those situations where one of the display programs
within Opus5 won't or can't work so that I don't have to use
Multiview.
Multiview can be so particular at times, plus it relies on having a
good, compatible, datatype installed. Within the Opus file types
setting for ASCII, double click on doubleclick and check what yours is
set to use. I'll assume that it is set correctly to call Multiview.
(To switch it to smartread change it to "Command smartread" and
unselect any flags that you might have set)
Now check your ascii.datatype for its version. AFAIK, it should be
v45.1 (I think that is from OS3.9 BB1). There is a chance that you
have something corrupted or missing from your Classes:Datatypes
or Devs:Datatypes directories.
BT> I am using DOPUS in the workbench replacement mode for years. No
BT> problems! I can double click on a jpg file type file and
BT> multiview starts and I see a picture. If I double click on an
BT> Amiga.guide file type file, multiview will start but I see an
BT> ASCII presentation of the amiga.guide file type document. I can
BT> start Multiview and with multiview open the same ASCII file and
BT> it reads it fine.
Does your filetypes setting for AmigaGuide files look like this?
SYS:Utilities/Multiview PUBSCREEN {Qs} {f} with the flag run
asynchronously.
If not, it probably should.
BT> I think this has something to do with file types rather than
BT> application programs (DOPUS or Multiview) I am not certain I know
BT> how to trouble shoot this, as I do not know what has changed to
BT> cause it to happen. Is it file type related? Is there some
BT> protocol of bits being messaged in packets.
I'm pretty sure that this has to do with either file types within
Opus5 or datatypes on your system.
BT> Could this be related to hardware changes I made?
BT> 2. MK III cyberstorm bd became intermittent and final failed.
BT> 3. Installed a new MK III and replaced the IDE HD with a SCSI
BT> very large HD. Moved all the files over to the new drive. They
BT> all look like they are there
It is possible that a datatype or two became corrupted during these
events.
A cynic is a man who, when he smells flowers, looks around for a
coffin. * H. L. Mencken
-*- ASTG 1.9