Jump to content
20 posts in this topic

Recommended Posts

  • 1 month later...
  • 10 months later...

 

Thanks for you advise Beerkex'd. I read your guide and added the smbios.plist to my extra folder and restarted. I still get the error in system profiler. About this Mac is fine (was before too). Are the 2 related? or am I fixing the wrong thing?

 

Thanks again for all your help, I have learned so much from you on this forum. if it wasn't for you, I'd still be fighting with 10.5.6 too :-)

Yes, they're related. But of course it could be something else that's causing the crash.

 

Is this on the PC in your sig?

 

It's very important that you have no SMBIOS injector kext in S/L/E (I listed most (all?) of them in my guide) and that AppleSMBIOS.kext is unmodified. And make sure you're not spoofing a Mac model that has too different hardware from your PC. Though it's not really possible to get a good match for a P4 with Intel 845 chipset. My P4 with i865 works well with MacPro1,1 info in smbios.plist though. Maybe that'll work for you too.

 

Visit my guide again, I have attached some goodies for you:

http://www.insanelymac.com/forum/index.php...t&p=1400949

 

I think there's another "generic" fix for the System Profiler crashing...but I'll be damned if I can remember what it is right now. I'll edit this post if/when I find out.

 

Run Console.app and look around in the logs for anything mentioning System Profiler, maybe there's a clue or two about what causes the crash.

 

Thanks for the compliments!

Yes, they're related. But of course it could be something else that's causing the crash.

 

Is this on the PC in your sig?

 

It's very important that you have no SMBIOS injector kext in S/L/E (I listed most (all?) of them in my guide) and that AppleSMBIOS.kext is unmodified. And make sure you're not spoofing a Mac model that has too different hardware from your PC. Though it's not really possible to get a good match for a P4 with Intel 845 chipset. My P4 with i865 works well with MacPro1,1 info in smbios.plist though. Maybe that'll work for you too.

 

Visit my guide again, I have attached some goodies for you:

http://www.insanelymac.com/forum/index.php...t&p=1400949

 

I think there's another "generic" fix for the System Profiler crashing...but I'll be damned if I can remember what it is right now. I'll edit this post if/when I find out.

 

Run Console.app and look around in the logs for anything mentioning System Profiler, maybe there's a clue or two about what causes the crash.

 

Thanks for the compliments!

 

Yes, It's the PC in my sig. When I use the unmodified APPLESMBIOS I get the "about this mac" finder crash.

 

Is there any way around this or should I just leave it with the Hacked SMBIOS and system profiler error?

 

The funny thing is.....It works on my iPC 10.5.6 drive. It shows it as a Mac Pro with a Core Solo. :)

Hmmm that's not supposed to happen :)

 

Console reveals nothing?

 

Have you seen this:

http://www.insanelymac.com/forum/index.php.../blockquote>

 

Have you previously used OSX86Tools to modify the 'about this mac' box?

 

I don't see anything relevant in console......

 

I did not use OSX86 tools to modify "about this mac"

 

I don't think it can be a bios setting because system profiler works correctly under 10.5.6

 

what do you think? :wacko:

I think you should just use iPC 10.5.6 and update that to 10.5.8!

 

If you really want to get to the bottom of it, start comparing files between the two installations.

 

'Core Solo' is normal, that's a bit of the Voodoo Kernel voodoo. No Macs have Pentium 4 CPUs so the Voodoo kernel 'fakes' a CPU type that is actually used in Macs. This fixes a compatibility issue with apps that probe for a certain CPU type.

I've tried to update the iPC 10.5.6 probably a dozen times. No matter what I do it becomes unbootable.

The only thing that worked for me to run 10.5.8 was to do an iDeneb install with some custom kext injection.

 

I've also tried to compare files but there are a lot and I'm not sure exactly which files are relevant to this issue.

×
×
  • Create New...