#ASL 2.0?
4 messages in this thread
Hi Brian,
I worked around the other problem, but I have seemed to stumble across another.
After installing the program I have developed with VB and ASL 2.0 I tried to
execute the program, I receive and INVALID FILE FORMAT message. When looking at
the original animation the size is approx 5 meg. After the distribution disks
install the file the animation is only 3 meg. Somehow when the file is
compressed and then split the limit is reached at 3 meg and will not handle all
5 meg. I had this problem with AVI files and the new version of the setup
wizard solved the problem. I'm not sure how to handle this third party product.
Any suggestions?
Thanks in advance…
-Paul
Paul,
Whatever 3rd party products you are using should have no bearing at all on the
setup wizard. When the wizard is working, your .VBX's and other stuff are just
files to be compressed. It does not differentiate between original VB files and
files from other vendors.
I would definitely go ask this question on the Visual Basic forum. (I think it
is GO MSBASIC to get there. Not sure) This definitely sounds like the setup
Wizard is messing things up.
-Brian
Brian,
What could be different with this particular animation file that would cause
this problem? I have used this same exact program with several different
animation files as a test, and all work but this one.
This particular animation file is not corrupt. It works within Animator Pro,
AAPlay and any other applications that can read .FLC & .FLI files.
Any other suggestions?
Thank You Much
-Paul
<<What could be different with this particular animation file that would cause
this problem? I have used this same exact program with several different
animation files as a test, and all work but this one.>>
I am not sure, but we could try to recreate the file and see if that helps.
Use the NUMPIC feature of AAPRO (or use the DTA.ZIP utility from here on the
forum) to turn the animation into a series of sequential TGA files, and then
recombine the TGA files into a new FLC with a different name. Try using this
new file and see if the problem persists.
-Brian