#Hardware compatability
2 messages in this thread
Chuck, I recently installed 4.06 on my 4000 and everything was fine for a
while. Then while the Flyer was doing it's thing before playing back a project
it would stop and give me an error message something like, "unexpected problem
meditation error #18. Make note of the circumstances that created this and
notify NEWTEK tek support." Not exactly what it said but close enough.
Let me tell you the hardware I have on my computer. Toaster 4000, Flyer, GVP
4008 SCSI card, and a multisync monitor. After disconnecting the GVP and
putting my 1084 back on the computer and restarting the Flyer I still had the
error message. I then thought that maybe something in my startup seq. might be
the culprit because I had just installed the GVP software for the 4008. (I
wanted to use my SYQUEST 270 for transfering files between my Amiga and my PC.)
Well I really don't understand the startup seq. so I just renamed it and copied
the startup seq. from the Commodore workbench disk. This worked! No more
problems with the error message. But this seq. is very basic and lacking some
assigns. I can just add things back in until I create the problem again. Can
you tell me what may have happened. Also with the old startup seq. the Flyer
would not start up on the first try. All screens would be going crazy like
there was no sync. But after a reboot the Flyer would then start up, but with
the error message showing itself. Maybe you could shed some light on how I
could use these components together. Thanks!
I haven't had a briefing yet on the error 18, but the Flyer Error list (in the
Library) defines it as a list error.
I would stick with the unmodified Startup-Sequence. Build your assigns, etc,
into the file User-Startup. Adding them one at a time until the failure occurs
would be the best (though time-consuming) way to isolate the failure.
We have no 4008 GVP cards to work with here, but I would expect few differences
between that and the other GVP devices with SCSI built in.
If you would not mind filling out a bug report (use bugfeat.lha, from the
Library), that might help us identify the problem better.
Chuck