#Animator unstable
6 messages in this thread
Folks,
this program does not seem stable. Ever since installing it,
I've had frequent FLIPPER errors in MSVIDEO.DLL and just now
in ANIMATOR.EXE. I wasn't able to save and exit a file I had
been working on and couldn't even exit the program – I got
a message saying that there was part of an image on the
clip board and did I want to exit. I clicked OK but nothing
happened. I also could not select and copy a portion of an image.
I got an OLE Exception:Facility:4, Error 0x01d0.
I hope there is a patch upgrade coming soon, because as it is,
I cannot rely on this tool for any serious work.
What's going on?
Ray
>I got an OLE Exception:Facility:4, Error 0x01d0.
I got this same error when attempting to save a FLC or FLI file in the
Windows-95 platform. I put up a message about it but haven't received
any reply.
Jim H.
yes..why is there no reply. There are serious problems with this
release. When you pay several hundred dollars for software it
should work. I've called the Animator customer support line
and they all but admit it was released before its time. So far
no answer has been given to my problems. I call (or write here)
and no one gets back with an answer.
Autodesk…are you there?
Jim,
The message I cut and pasted into a response to Ray Laurencelle includes
something that might interest you. It's from a programmer. Since you
mentioned you were running WIN95, it appears that some conflict occurs.
"I looked up the error code for 0 x 40c7, and it wasn't very
useful. It just indicates a non-specific error in Video for Windows.
I looked and it doesn't appear that our code is generating that
error, but is probably simply passing it back from Video for Windows.
"Is he running on Win95 or NT? Does he have video for windows
accelerators? I have seen video for windows accelerators that
are not using the most recent version of Video for Windows, which
can cause problems. I would suggest looking for a more recent driver
set for the video card."
Nik,
I haven't used AS much yet as I've been busy with some other things, but so far
my experience is that I can load and save AVI files in AS. The only thing that
doesn't seem to work is attempting to save an FLC or FLI file.
Instead of the dialog box about reducing the colors, I just get that OLE error
(not the same HEX number). This is all under Windows-95.
I installed Windows 3.1 on the same machine and installed AS under Windows 3.1
and I have no problem loading or saving. That is, the problem goes away.
I've tried seting up AS under WIndows NT version 3.51 and it just freezes up.
Other than that, I haven't done any other extensive testing on it.
Jim H.
Hi Ray,
One of the programmers has commented on the OLE error you got, but does not
offer a specific remedy:
""OLE exception: facility: 4, error: 0 x 40c7"."
From one of the programmers – does this help?:
"I looked up the error code for 0 x 40c7, and it wasn't very
useful. It just indicates a non-specific error in Video for Windows.
I looked and it doesn't appear that our code is generating that
error, but is probably simply passing it back from Video for Windows.
"Is he running on Win95 or NT? Does he have video for windows
accelerators? I have seen video for windows accelerators that
are not using the most recent version of Video for Windows, which
can cause problems. I would suggest looking for a more recent driver
set for the video card."
You also stated, "I've had frequent FLIPPER errors in MSVIDEO.DLL and just now
in ANIMATOR.EXE." I've seen other Flipper errors, but from what I understand
Flipper is code from the Animator.exe, and not MSVIDEO, which is from
Microsoft. QA has asked that we gather as much information about the
circumstances that generate the error so that they can duplicate the problem
and thus write it up as a bug.
Can you let us know what steps you take to reproduce the error? Is it
consistent? What are your System Resources at the time of the error (Program
Manager, About, Program Manager…)? Any info, including your Windows video
driver revision and dates (I think they'd be interested in the size/date of
your Windows\system\*.drv files that pertain to your video display) and whether
or not you've installed any programs after AAStudio that maybe have overwritten
certain AAS files.
I'm sorry we don't have an answer for you at this time. You might also try
booting up with just HIMEM.SYS (so you can run Windows) and nothing else, to
see if the error goes away or changes.
Thanks again.
Nik