#IFFParse.library
10 messages in this thread
Please excuse my ignorance, but can anyone explain what the
iffparse.library is? I have some demo software that won't run without it and I
can't find it in any library on any boot disk I have. Is this a WB 2.x library
by any chance?
Barry
Barry,
Yes, iffparse.library is a standard part of the Amiga operating system, used
to allow application programs to be able to read/write IFF files in a standard
way. I believe that it was first included in the 2.0x version of the Workbench
distribution.
Hope this helps….
– BobR
iffparse.library is a library module written by Commodore. The intention was
to allow programs to easily scan into an IFF file and pick out the parts that
were wanted. Although it is indeed distributed with DOS 2.0, documentation
says it is compatible with the Workbench 1.3 environment.
Programs using iffparse.library that are intended to be 1.3-compatible are
likely distributed with a copy of iffparse.library. A copy of this library was
also supplied separately to developers.
If you have more interest in the purpose and use of this library, you might
wish to reference (from FF disk 705): NewIFF, which gives code modules and
examples on the use of this library.
–Jim
Jim,
Thanks for the information. I was trying to test DMCS 2.0 demo and the
verison I DL'd didn't have the libs. I DL'd a different version that had the
libraries needed.
I'm still having a problem though. Whenever I try to operate the MIDI
port, I get an error requestor saying that it can't find the "CAMD.library".
This is interesting because it is there, in the libs directory. I've even tried
assigning it with no luck. Do you have any ideas?
Barry
"Can't find the CAMD.library"? And it's there, in libs: ???
That's an odd one. Other than an invisible character within the name (most
unlikely: try LIST LIBS:CAMD.LIBRARY and if you get a listing, it can't be
that), I'm not sure what's happening.
Are you familar with SNOOPDOS (Fish 725, maybe there's a version in the
library area here) ?? Put that in, and it will report exactly what files (with
path name) the program is trying for.
If it finds the right file and still says "Can't find…", then apart from
it being an untruthful program, I would assume that it thinks the file is
corrupt.
–Jim
Or it isn't the right version.
-Karl Speaking from the Rubble.
True. The DOS function OpenLibrary doesn't distinguish between a library
that's not sufficiently recent, and one that's not there. Wish it did.
Of course, a programmer COULD request any version of the library and then
check it him/herself, so as to give a more meaningful error message. But when
Commodore gives you a standard facility, you just tend to use it rather than
take the long way around.
Good point, Karl.
–Jim
I only wish I could be as clear as you were. It is very, very good to
have you back around here.
-Karl Speaking from the Rubble.
Thanks for the information. When I put it in the libs directory it worked
fine. I still don't know why an assign wouldn't work.
Barry
Just a followup note on SNOOPDOS, by Eddy Carrol. You'll find a recent version
in Library 11 here, named SNOOPD.LHA. Subsequently, other authors have written
similar packages, such as DTRACE.LHA (DosTrace, also on Fish 969), and SNOOPY
on FF948.
That should let you snoop away to your heart's content.
–Jim