From DAVIDK@ASYMETRIX.COM Wed Feb 8 10:22:14 1995
Date: Wed, 8 Feb 1995 08:50:00 PST
From: David Kester
Reply to: Asymetrix 'Toolbook' product discussions
To: Multiple recipients of list TOOLB-L
Subject: Re: RELIABILITY OF MM/TBK
In the last year and a half of doing Technical Support for TB and MTB I have
found that about 90% of the time GPFs in mtb30bas.dll, tb30bas.dll and
tbkbase.dll are caused by one of two things:
- A video driver that has a bug.
- A corrupted TBK file.
It's always best to approach these problems on a case-by-case basis so as
not to make assumptions. If you find that your getting GPFs regularly but
not in a reproducible manor(1) try switching the computer to use the VGA
driver for a day. It will look ugly (only 16 colors) but that video driver
is bug free. If you can go all day without a GPF then it's probably the
video driver you were using.
Always make sure that the video driver you are using is the latest version
of the driver for your card. Since all video drivers for Windows are
proprietary and written by the hardware manufacturer they vary widely in
reliability. The VGA driver I mentioned is the only truly standardized
driver for Windows.
I have usually run MTB 3.0 (Not 3.0a) and I don't get GPFs in mtb30bas.dll
without it being a reproducible problem. I use a stable video card and
driver. I save my work often and I use save as to a back up with CD-Rom
optimization turned on.
By following these steps I rarely crash. That is that I crash a lot more in
mail or because of a network problem.
(1) A reproducible example would be:
- I get a GPF every time I go to page 4 of my book.
Dave Kester
Asymetrix
Revised 2/8/95
brianp@u.washington.edu
(Brian Parkhurst)
T-301 HSB, SC-72, University of Washington, Seattle, WA
98195
206/616-7435