Sorry, I just realized you're on a SAM, so your file revisions will be different from me, I have a micro.
Other then that, I'm running out of ideas. If you have a boot cd that shows images, all you can do is start comparing files to see whats missing/changed.
Look, only one leg, count em, one! X1000/PA6T@1800MHz/2Gb/Radeon 4850
well i was messing around with my catweasel settings the other day but what the heck did I accidentally move/erase for this to happen ??
If you are absolutely 100% sure that you've done nothing else but fiddle with catweasel settings since your datatypes last worked...then we need someone to post that knows or has a catweasel.
Hmm. Could you please post here a list of the datatype descriptors that reside in your DEVS:Datatypes drawer?
According to your Snoopy output, a "BINARY" datatype descriptor seems to "overule" all other datatypes (including all image types) - but there seem to be no "binary.datatype" class in Classes:Datatypes. Maybe some strange install script put that descriptor in your DEVS:Datatypes drawer? (Catweasel?)
Ok, thanks - that were the datatype classes from "SYS:Classes/Datatytpes/#?". And now the list of datatype descriptors from "DEVS:Datatypes/#?", please.
According to your Snoopy output, a "BINARY" datatype descriptor seems to "overule" all other datatypes (including all image types) - but there seem to be no "binary.datatype" class in Classes:Datatypes.
That's normal - binary.datatype is a superclass for binary files, but it's not included with OS4. There are 3rd party ones available that can be dropped in.
If you really have files in sys:devs/datatypes that are copies of those in sys:classes/datatypes then you -do- need to replace them with the datatype descriptors from your CD.
So yes, I would start with deleting the contents of your directory: sys:devs/datatypes And replace it with the contents from the CD directory devs/datatypes.
If any additions or changes were made to OS4.1 update 2 regarding either sys:devs/datatypes OR sys:classes/datatypes, you would also have to update to any newer versions.
btw-I am still curious how this could have happened to you.
I did a quick test. I deleted all datatype descriptors from sys:dev/datatypes and replaced them with the datatypes themselves from sys:classes/datatypes. (rebooted)
iff loader on background pic for WB failed of course. Then I tried to load .jpg with multiview:
I did a quick test. I deleted all datatype descriptors from sys:dev/datatypes and replaced them with the datatypes themselves from sys:classes/datatypes. (rebooted)
iff loader on background pic for WB failed of course. Then I tried to load .jpg with multiview:
You can see that I got similar error message to the OP concerning binary.datatype.
#6
#6 you sir are NUMBER1 in my book problem solved now thanks to your help ..oh & sundown & cha05e90 as well
btw, have no blody idea how those folders got buggered up....must have accidentally copied them some how when I was trouble shooting my catweasel anyhow alls well that end well
When I said it was normal, I meant it was normal that datatypes.library would try to load binary.datatype. It would only do this if it could not find a matching subclass.
Normally if you are loading a JPEG, datatypes.library would check the file against all the descriptors (in DEVS:DataTypes), identify it as a JPEG. The JPEG descriptor would tell datatypes.library that jpeg.datatype handles the file. jpeg.datatype is subclassed from picture.datatype, so loads that to do rendering (and other things which relate to all pictures, not just JPEGs).
If datatypes.library fails to identify the file using the descriptors, it falls back to one of the three base classes - ascii.datatype, iff.datatype or binary.datatype.
Out of these three, only ascii.datatype is supplied with OS4, as it is the superclass for all text formats.
So, seeing binary.datatype in the log is normal, if it is a non-IFF binary file which could not be matched against any descriptor. This is consistent against the issue the OP was having with no descriptors present.
Thanks for that explanation regarding "fallback". Much appreciated. I was curious about that myself. I only thought to imitate the OP's experience and attempt a .jpg file load from Multiview.