#Does this make sense?
3 messages in this thread
Originally I had to make a separate bootup configuration for ani pro 1.3
with nothing loaded into the UMBs, because Pharlap doesn't like the windows
memory manager. Other people confirmed that this was the same for them
too. Then one day I accidentally ran ani pro with the setup where windows
puts my 90kB disk caching driver in upper memory… and now it works. It
works every time I try it. I've been getting a lot of strange intermittent
behaviour. Does this one make sense to anyone out there?
I have experienced problems with Pro 1.3 giving me memory faults and page
protection faults. I have been talking with everyone I can at Autodesk
tech support. So far they haven't been too helpful other than admitting
that it is probably their problem. I may have a unique situation on my
system, I use Bernoulli removable cartridges exclusively. They have
drivers that are loaded into lower memory. There seems to be some conflict
with Pro 1.3 and either the mouse drivers or Bernoulli drivers. I have
updated the mouse drivers to the latest available from Microsoft (I use the
Trackman trak ball), and the latest available Iomega drivers but I still
experience program failures to the point where I can not execute the 1.3
version. I had previously used Animator and then Animator Pro 1.0 with no
problem whatsoever.
I'm very interested in getting to the bottom of this problem. If you find
any insight into this, could you please pass it along….I will do
likewise.
FWIW,
I use a ESDI hard disk and a bernoulli drive (with an Iomega controller), DOS
5, QEMM, and I get along fine with Ani Pro 1.3 (and 1.0 before that).
OADDOS before QEMM. I use Quarterdeck's HOOKROM utility too, but I think it
works without it.
Chuck Jameson
Silver Tongue Software