iBook identity crises

9 posts / 0 new
Last post
Offline
Last seen: 12 years 8 months ago
Joined: Apr 15 2004 - 22:11
Posts: 142
iBook identity crises

When I ran Apple System Profiler on my iBook i noticed that it thinks it has a 68LC040?
NOT FOUND: 1

Odd...

Offline
Last seen: 12 years 8 months ago
Joined: Apr 15 2004 - 22:11
Posts: 142
Forgot the image...

IMAGE(http://www.applefritter.com/images/weird_processor-17982_640x480.jpg)

Offline
Last seen: 2 months 3 weeks ago
Joined: Aug 22 2005 - 10:32
Posts: 404
i think that is pretty cool i

i think that is pretty cool is that Mac Os 9 ? are you running wish i were?

Offline
Last seen: 15 years 3 months ago
Joined: Oct 9 2004 - 08:26
Posts: 92
wow a 600 mhz 040 i want one

wow a 600 mhz 040 i want one of those for my performa

Offline
Last seen: 2 months 3 weeks ago
Joined: Aug 22 2005 - 10:32
Posts: 404
no you wouldn't it'd go up in

no you wouldn't it'd go up in a poof of smoke

Offline
Last seen: 10 years 6 months ago
Joined: Sep 16 2004 - 02:44
Posts: 274
I remember in resedit in the

I remember in resedit in the pre-x era you could modify that info, if i remember correctly. Pretty cool though.

macg4's picture
Offline
Last seen: 11 years 11 months ago
Joined: Jan 17 2005 - 23:33
Posts: 311
coolness!

coolness!

Offline
Last seen: 15 years 3 months ago
Joined: Oct 9 2004 - 08:26
Posts: 92
Re: no you wouldn't it'd go up in

no you wouldn't it'd go up in a poof of smoke

i know i was being sarcastic

Offline
Last seen: 1 year 3 months ago
Joined: Dec 20 2003 - 10:38
Posts: 69
I got this on my old 604 too.

I got this on my old 604 too. I think it's because the emulated 68K chip in the PowerPC is based on either the 68020 or 68040.

Either that, or ASP has no clue what chip it is and is just resorting to the first string in some internal table. Since your version of ASP is probably >= 8.0, and the slowest chip supported was a 68LC040, that's probably what is the first element in the list.

Probably looks like {68LC040, 68040, PowerPC 601, PowerPC 603...} and your CPU isn't "known" to your version of ASP since it's outside of the list. That's my guess.

Log in or register to post comments