Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Jolly Roger <jollyroger@pobox.com>
Newsgroups: comp.sys.mac.system
Subject: Re: Unable to boot up an old 15" MBP (2008)'s Mac OS X v10.5.8/LEOPARD...
Date: 20 Feb 2017 02:10:23 GMT
Organization: People for the Ethical Treatment of Pirates
Lines: 40
Message-ID: <egv1gfFhraaU1@mid.individual.net>
References: <vN-dnSbtmeFXuDXFnZ2dnUU7-cfNnZ2d@earthlink.com> <180220171111393467%nospam@nospam.invalid> <T86dndyRq_THDjXFnZ2dnUU7-a2dnZ2d@earthlink.com> <68mdnSAn_tErfTTFnZ2dnUU7-RPNnZ2d@earthlink.com> <N6CdnclU74B2fzTFnZ2dnUU7-InNnZ2d@earthlink.com> <xfCdnQnv-boqdTTFnZ2dnUU7-WWdnZ2d@earthlink.com> <3p6dneGxDIAGcTTFnZ2dnUU7-b-dnZ2d@earthlink.com> <FJednRSqZ6Z3aTTFnZ2dnUU7-IudnZ2d@earthlink.com> <gJKdnYOT9sdnajTFnZ2dnUU7-e1QAAAA@earthlink.com> <b-WdnQN4gLaQkDfFnZ2dnUU7-SPNnZ2d@earthlink.com> <eguhflFerqdU1@mid.individual.net> <mbOdnWxIKe-4sTfFnZ2dnUU7-b9QAAAA@earthlink.com>
X-Trace: individual.net WLeHd2siVrzQ4W2ICFT7xAP3kPbveOsW6EhzhbAo1nM7nW0bK8
Cancel-Lock: sha1:p3BHGWBfoSngzOIv8iiljok7LJ0=
Mail-Copies-To: nobody
User-Agent: slrn/1.0.1 (Darwin)
Xref: csiph.com comp.sys.mac.system:100720

On 2017-02-19, Ant <ant@zimage.comANT> wrote:
> On 2/19/2017 1:36 PM, Jolly Roger wrote:
>>> Yay, I finally and sucessfully booted up the brand new Mac OS X
>>> v10.5.2 from the external USB HDD. Its required registration was
>>> annoying (no cancel and skip options)!
>>
>> For as long as I can remember the Command-Q (Quit) command has skipped
>> the optional registration.
>
> And not in GUI since I didn't see it. I will try the hotkeys next time 
> if I run into it.

Pretty sure there is a File > Quit menu in the registration GUI.

>>> Anyways, I also updated v10.5.2 to v10.5.8 and all of its updates
>>> until there were nothing left. Also, I can see and access MBP's
>>> internal USB HDD just fine. I wonder if I can fix the issue in it. Any
>>> ideas what to try? This would be a good practice for me if it is
>>> possible. ;)
>>
>> Boot in verbose mode and pay attention to the messages that are
>> displayed. The startup messages will often tell you what's wrong with a
>> system that is failing to start up properly. Look for *errors* and
>> *failures* in particular. Post the messages here (photos or transcribed)
>> for help figuring out what they mean if needed.
>
> I did that as mentioned in my original newsgroup thread post:
> "3. command+v (verbose) = saw the text mode with technical datas. Then, 
> it loaded the light blue screen for about a second and then back to text 
> black screen with a white block on the top left corner. Then back to 
> light blue screen to the black text screen with the top left white block 
> in a loop forever."

"Technical datas" isn't enough detail to help any further. Sorry.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR