Mac G3 Beige desktop, OS 9.2.2, QT 6.0.3 (free version), 224 MB RAM,
VM off.
----------------

I recently downloaded a few MP3 files using a LimeWire (peer-to-peer)
client. A few refused to open under QT and I got a system error
message stating the files could not be opened.

A system restart and a rebuild of the desktop seemed to fix that
problem for the majority. I chalked this up to a quirk with Limewire
(the free download version).

However a couple of music files still refuse to open after 2 restarts
and rebuilds. Double-clicking the file icon accesses QT but the app
says it cannot find the file. Ditto trying to open it from within QT.

I ran Norton Disk Doctor (Norton Utils ver 6) and that didn't find
anything wrong with the files.

I then downloaded a copy of GrapAmp, a free MP3 player and that can
play these files without a hitch.

So I'm wondering what the problem is?

Suggestions?


DMK

D. Kirkpatrick <sunclad@sunclad.com> wrote:

> OS 9.2.2, QT 6.0.3
>
> I recently downloaded a few MP3 files [...]. A few refused to open
> under QT and I got a system error message stating the files could not
> be opened.

QuickTime used to be picky about types and creators (haven't checked 6.0.3,
though). Just the type code, to be precise. If it's different from what is
known to QuickTime Player, it can refuse to play it. Try setting it to "Mp3
". Still weird that it only happens to a few files. Maybe it's a
combination of that and a bad file header.

--
Tom

--

"If you're not confused, you're not paying attention"
-- Michael Rothschild, 1993

In article <BC13EC2A96684DC49@c22176.upc-c.chello.nl>,
th-usenet-j5mgqzzw@xs4all.nl.spamtrap.invalid (Tom) wrote:

> QuickTime used to be picky about types and creators (haven't checked 6.0.3,
> though). Just the type code, to be precise. If it's different from what is
> known to QuickTime Player, it can refuse to play it. Try setting it to "Mp3
> ". Still weird that it only happens to a few files. Maybe it's a
> combination of that and a bad file header.

---

Thanks.

I'll fiddle with it to see what happens.

DMK

In article <sunclad-4C304E.17274728122003@news.verizon.net>,
"D. Kirkpatrick" <sunclad@sunclad.com> wrote:

> Thanks.
>
> I'll fiddle with it to see what happens.
>
> DMK

----

Replying to self....

Used Norton to change the file type on a couple.

Oddly, some seemed to be labeled ".SMI" which seemed odd since these
were not disk images.

Changing to "MPEG" seemed to fix it.

Problem solved - for the most part.

DMK