CompuServe Thread

#ANIPLAY input devices

8 messages in this thread
#168965From: joeMay 8, 1995 8:54 PM
I need to figure out why ANIPLAY generates an error message when playing scripts files that says that we have the wrong input device selected. I think it needs an overide switch either on the call to ANIPLAY.EXE to avoid using an input device or the FLIC files in question need to get the input device overriden with a NULL device or something. We do not run ANIPLAY in the mode where you get the menu, it is just called to execute scripts and exit when the script is completed. Eventually I plan to use our customized FLIC player to run them, but for the immediate future we have to continue using ANIPLAY. Some help here would go a long way.
#169178From: Brian Rudolph [Adesk]May 9, 1995 1:30 PM
Joe, Try deleting your aa.cfg file. that is where the configuration information for input devices are stored. -brian
#169256From: joeMay 9, 1995 6:32 PM
I seem to remember that when we did this we got a missing AA.CFG message (or was that AA.MU)… Will try again, though, thanks!
#169419From: Brian Rudolph [Adesk]May 10, 1995 11:36 AM
<<I seem to remember that when we did this we got a missing AA.CFG message (or was that AA.MU)… Will try again, though, thanks!>> If that is the case, what you can do is delete the CFg file, start AAPRO (or AA) and configure for the corect input device. then copy that AA.CFG file along with the player to a different location, and then go back and reconfigure the AAPRO program for how you want. (The player and AAPRO program use the same AA.CFG file.) -Brian
#169534From: joeMay 10, 1995 10:51 PM
Brian, I appreciate the response. I tried this and failed miserably, since it appears that the VESA driver has to be reconfigured each time a new VGA card is used. Not exactly portable. I was able to address the issue by using the mouse driver for the hardware the FLCs were generated on (rather than the logitech or microsoft driver), and it worked fine for the several different serial mice we use, so I can consider the issue moot. Thanks for the support!
#169592From: Nik Grant [adesk]May 11, 1995 9:45 AM
"…it appears that the VESA driver has to be reconfigured each time a new VGA card is used." I'm not sure why this is so. Are you saying that your AA.CFG configuration file for, say, a Diamond VESA-compatible card will not work with an ATI VESA-compatible card?
#169619From: joeMay 11, 1995 12:34 PM
Right… Although I am not sure if those two are incompatible or not, the card that is in our Dell PC's requires a different VESA selection than the generic Cirrus Logic based cards elsewhere… Anyways, ANIPLAY is not the best tool for our job and I plan to change it ASAP, so my using the wrong mouse driver for the mouse fixed the short term problem and I will have a better fix for the long term… Thanks for the responses!
#169685From: Doug SlemmerMay 11, 1995 6:59 PM
Sounds like a personal problem Joe.