Ping : The Macisti....

So, those nice chaps at apple lend us products to test all the time,
I've been using a Mac Book Pro 13" for the last month or so, and very
nice it is too.

I've come to re-install it from the original Grey install DVD's that
shipped with it.

A quick Google says that I need to hold down "c" to get it to boot
from the DVD.

I've done this an now all it does is loops to this screen every time I
try and boot.

http://www.facebook.com/photo.php?pid=3178285&l=ab978c064d&id=715546495

Do I have a major malfunction (pp) or am I just missing something ?

 

You could try resetting the PRAM/NVRAM - hold down Command Option P R

 

Just stick the DVD into the drive once it's booted up, you should be
able to reinstall the OS that way, too.

 

Yeah, that's a 'kernel panic', aka. a *really* bad crash. Might be a
defective DVD, or it could be a hardware fault - RAM for a start.

 

Tried the install from Desktop. Same Result. Tried resetting NVRAM as
well - same result. Can't eject the DVD now to stop it happening. Damn
machine !

 

Hmmmm.....

Interval Since Last Panic Report: 108922 sec
Panics Since Last Report: 2
Anonymous UUID: 6D2AA9BE-302B-4752-BF59-
D03A1022E820

Wed Oct 14 13:58:31 2009
panic(cpu 0 caller 0x003EF4A2): "A driver releasing a(n) OSArray has
corrupted the registry\n"@/SourceCache/xnu/xnu-1228.10.33/libkern/c++/
OSObject.cpp:241
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x507e7bd8 : 0x12b4c3 (0x45d7fc 0x507e7c0c 0x133542 0x0)
0x507e7c28 : 0x3ef4a2 (0x4a0128 0x4a01f4 0x743fa04 0x507e7c40)
0x507e7c68 : 0x3ef412 (0x743fa00 0x0 0x1 0x0)
0x507e7c88 : 0x3ef4df (0x743fa00 0x0 0x7 0x0)
0x507e7ca8 : 0x56e7d9eb (0x743fa00 0x7476b80 0x507e7ce8 0x569ffc3e)
0x507e7ce8 : 0x56e7d809 (0x752ce00 0x7528500 0x507e7e2c 0x4d)
0x507e7e48 : 0x414fd8 (0x752ce00 0x7528500 0x1 0x3ef3e6)
0x507e7ea8 : 0x41687b (0x7528500 0x752ce00 0x73457c0 0x7489aa0)
0x507e7f28 : 0x4160df (0x7528500 0x73605c0 0x0 0xffffffff)
0x507e7f78 : 0x417773 (0x7528500 0x0 0x507e7fac 0x1)
0x507e7fc8 : 0x1a055c (0x6697c40 0x0 0x1a30b5 0x75066b0)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleHDA(1.6.6a32)@0x56e79000->0x56ee2fff
dependency: com.apple.driver.DspFuncLib(1.6.6a32)
@0x574e1000
dependency: com.apple.iokit.IOHDAFamily(1.6.6a32)
@0x51a1c000
dependency: com.apple.iokit.IOAudioFamily(1.6.5fc5)
@0x569fc000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9G3556

Kernel version:
Darwin Kernel Version 9.6.3: Tue Jan 20 18:26:40 PST 2009;
root:xnu-1228.10.33~1/RELEASE_I386
System model name: MacBookPro5,5 (Mac-F2268AC8)
Model: MacBookPro5,5, BootROM MBP55.00AC.B03, 2 processors, Intel Core
2 Duo, 2.53 GHz, 4 GB, SMC 1.47f2
Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D),
Broadcom BCM43xx 1.0 (5.10.91.19)
Bluetooth: Version 2.2.1f7, 2 service, 0 devices, 1 incoming serial
ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: FUJITSU MJA2250BH FFS G1, 232.89 GB
Serial ATA Device: HL-DT-ST DVDRW GS23N
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0x24400000
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403,
0x26500000
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.),
0x0237, 0x04600000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x04500000
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.),
0x8213, 0x06110000

 

Reboot and hold down the mouse button.

Have you got any USB devices attached?

 

<table mode=turned>

Get a PC.

</table>

 

Install Windows.

 

All my computers work as expected here - the Macs just 'work' [1]. The
Windaz box needs encouragement!

Strangely enough, I run XP in Parallels on my MacBook, and it's faster
and more stable than it is on the PC proper.


[1] With the exception of Emily's iBook, which she's not looked after
too well - jammed keys, broken screen, broken hinge, sellotape around
the power lead.... Yet it does kind of function.

 

I had a devil of a time getting osX installed on my g4 tower.
I ended up formatting the drive in the box with it mounted in firewire
target mode to another mac, copying the contents of the install media
across to a huge partition (a small one failed to work) with the boot
flag set to pretend to be a dvd. Then rebooting and running the
installer from that partition. Then again with target mode, cloning the
resultant installed image from the average sized partition it was
installed to, wiping the partition table and reconstructing a single
large partition. then cloning the installation image back into that
partition to result in a machine with a whole disk available to the OS
in a bootable state.

Any other way I tried either didn't boot, or chucked the grey screen of
death up.

From then on: 'it just works'.

 

Unless there's a hardware fault...

 

Heh.... battery gave up ..... To be continued......

(Charger at home!)

 

Blimey, it might have been an unsupported drive unit or something. I've
even managed to install 10.5 onto an unsupported G4 very easily here,
Target mode-install-reboot-install extras-jobsagoodun.

 

IIRC, Macs only began having any kind of reliability issues at all once
they started using 'standard' PC parts. Pre-PCI based Macs were pretty
much bullet proof - old Quadras were in serious use for many years, some
into this decade, which means they were 10 years in service.

Indeed, I still have a Mac SE (circa 1989) in my loft, which does still
work perfectly.

 

Andy Hewitt wrote:
<snip two wasted days of my life, especially since I'm told new macs
'don't do target mode'>

I'm not entirely sure it was worth the bother in the end, I'm still
scratching around for 2 512 mb pc100/133 dimms to get the thing up to
it's full capacity of 2gig ram. I was going to do some audio work on
it, but it may not have the grunt I need in the end.

 

Hmmm, now that's a thing I hadn't thought of - RAM!

Mac OS X does run a compatibility check on RAM modules during
installation. If you have some not-quite-up-to-spec modules, they'll
work perfectly in OS 9, but may not in OS X - indeed it won't install.

 

Connected to charger, tried dvd 2 with the diagnostics, starts to
boot, then resets. Obblox !

 

It needs to go to boot camp.


--
Beav

VN 750
Zed 1000
OMF# 19

 

What did she say?