NEW G5 will no longer boot up...

Greetings...
I have a brand new G5/Tiger which has been running well for the last month. I ran disk utility (as I have done monthly in the past with my G4), then restarted the computer. The G5 seemed to power down, but not back up! the power light is on, but I cannot get the cd tray to open, NOTHING! the only connections are the monitor and keyboard. I tried a different monitor/keyboard- nothing. This is a production machine, so I'm very anxious to remedy this..
Thank you!

Hello mdken:
Since you have a new machine, I suggest you call Applecare. The technicians there are trained and will walk you through troubleshooting steps.
Barry

Similar Messages

After installing Leopard, my G4 will no longer boot in OS 9.22. (Classic still works, but I need it to boot in OS 9.) Any clues about what the Leopard installer might have done to my machine that rendered OS 9 boot unusable? What can I do to fix it?

After installing Leopard, my G4 will no longer boot in OS 9.22.
(Classic still works, but I need it to boot in OS 9.)
Any clues about what the Leopard installer might have done to my machine that rendered OS 9 boot unusable? (And what can I do to fix it?)
Details:
G4 Gigabit Ethernet
Boot ROM version: 4.2.8fl
Accelerator card added: 1.6 MHz
1.5 Gig Ram
I have erased the partition that had Leopard installed on it.
I zapped the pram.
In Open Firmware, I "reset-nvram", and then "reset-all"
I tried to reinstall G4 FW Update 4.2.8, but that must be done when booted from OS 9, and of course, that's the problem: it won't boot into 9.
I tried restarting from 9.2.1 DVD.
I tried restarting from an external firewire drive containing OS 9.2.2.
I tried moving a fresh OS 9.2.2 system folder into an empty partition on an internal hard drive. (Partition was created WITH OS 9 drivers installed.)
All attempts to boot into OS 9 give me the same results - grey screen - no spinning beach ball, no icons or logos - just a blank grey screen.
This machine still works fine in OS 10.3 and 10.4, and it worked fine for many years booting into OS 9, until I installed Leopard, and I haven't been able to boot into OS 9 since then, although I have done considerable research online and tried many things.
I have since learned that this machine does not support Leopard - 10.5. Fine, but how did it break 9.2.2?
Any help greatly appreciated.

Thanks for checking in, BDAQua.
Problem solved.
In the docs that came with my Powerlogix accelerator card, I found this sentence buried:
"If you reset the PRAM, the NVRAM code for OS9 compatibility is cleared, so you will have to boot from the Firmawre Update CD and perform this process again in order to boot in OS9."
The "process" it's referring to is the process of setting up the NVRAM for booting into OS9 from the CD.
Fortunately, I was able to find the disk, and it worked as expected. I can now, once again boot into OS9.
Conclusion: My (unadvised) attempt to load Leopard on this old machine apparently reset the PRAM on the accelerator card and cleared the NVRAM code for OS9 boot. Although I did attempt to reset the NVRAM via Open Firmware, it did not reset it on the accelerator card.
So, thank you BDAQua, for your "Ah yes" . . . that's all I needed to steer me in the right direction.
Gratefully,
tupester

881W Will no longer boot with Radio Card installed

Hello!
I have a Cisco 881W that will no longer boot/operate properly if the internal radio card is installed.
If the card is installed, all I get is the following...
System Bootstrap, Version 12.4(22r)YB5, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2009 by cisco Systems, Inc
Testing lower main memory - data equals address
Testing lower main memory - checkerboard
Testing lower main memory - inverse checkerboard
Clearing lower memory rommon use
read_sys_eeprom: not a smart eeprom
Search for cpu type (Field ID 0x09) failed.
Using default value...
Search for Controller ID (Field ID 0x40) failed.
C880 platform with 262144 Kbytes of main memory
Readonly ROMMON initialized
rommon 1 >
if I do a dev I get nothing. If I do a dir flash: I get "bad device name". My cookie shows FF in all positions.
BUT......
If I remove the entire WiFi Radio card (both boards), then It boots fine, cookie appears intact, devs appear, IOS loads, just without the WAP.
Any chance this is a matter of a file getting deleted or corrupted or is this certainly bad hardware? The router sans Wifi appears fully functional.
Thanks!

You should be able to RMA the device. Search the forum for a post on the limited lifetime warranty:). They explain it good there.
Sent from Cisco Technical Support iPhone App

Made a new partition on Macintosh HD, Boot Camp will no longer boot.

Specs:
MacBook Air 2013
8GB RAM
i7
512GB SSD
Hello all, looking for some assistance.
My HD is formatted to 400GB of OSX and 80GB of Boot Camp. I stupidly made the mistake of adding a new partition out of the large amount of free space I have on the OSX partition, to format the new partition for Windows. This made Boot Camp no longer boot. On the Disk select screen after holding Option on boot, my Boot Camp partition is not visible. I can see everything on the partition on OSX, however.
To try and fix this, I deleted the new partition and tried to reduce the hard drive back to the original two partitions. However, I cannot extend the OSX partition to fill in the new free space. So now I have a Boot Camp partition, my OSX partition, and 20GB of unused, free space that I cannot use or put back into the original partition.
I asked AppleCare live chat for any assistance, they suggested that I use "Erase free space" in Disk Utility to use the space again. However, the option is greyed out on both the drive and the Macintosh HD partition.
After a bit of googling I saw a suggestion of making a USB Recovery drive to get the space back through Disk Utility that way. This still did not work; the results were the same, unable to add the space back to the original partition, and "Erase free space" is still greyed out.
Using BootChamp (notice the H, this is an app that allows you to restart and boot directly into Boot Camp through OSX), I get a DOS screen saying "No bootable device – insert boot disk and press any key". I cannot get this screen any other way.
I have repaired and verified the disk and its permissions, to no avail.
I cannot think of anything else to do short of formatting the entire drive but this is obviously less than preferable. I additionally do not have a backup of the BootCamp partition (as it is not accessible), even though everything is visible on the partition through OSX.
So, in summary, I added a new partition to my HD and now Boot Camp will not boot. Any ideas?

"rEFIt is an alternative bootloader for your Mac that's a lot more forgiving. If you don't think investing in iPartition is worth it, I'd give this a shot:
In rEFIt, do not boot: go to the EFI shell, and type "gptsync". This will tell you that the partition table is out of sync, and will offer to sync it for you. Say "yes", naturally. Now reboot and all systems should be go!"
This worked.

Bootcamp will no longer boot after deleting partition #3 of my new Mac Mini. What happened? Was it the way I tried to reclaim the HDD space for Mac?

Here's my dilemma. I have a new Mac Mini - a week old. I installed Windows 7 on it using Mac's Bootcamp assistant. I then set up and configured my Windows 7 world and everything worked fine. No issues logging in between Lion or Win7 via the restart/option key procedure. Well, yesterday I split my Mac HD partition one more time to create a third partition (was created as an "extra", e.g. possible future partition for another operating system). After creating it, I then decided that I didn't really need it. So I deleted it in Disk Utility and attempted to drag the Mac HD partition line downward so as to "fill in the gap" and reclaim the lost hardrive space. It seemed as if I could reclaim about 1 gig or so, but I figured...oh well.
Well, the Mac HD partition seems to work just fine, but now I've noticed that I can't get into the Bootcamp partition anymore. It wont boot. If I try to verify the partition [doesn't even give me "repair" as an option), then it fails and gives me the following error message: "verify volume failed. invalid request." When I go to the Startup Disk option in my System Preferences section, it displays the bootcamp partition as a folder and not as a drive anymore.
I'm assuming that I messed up some permissions or lost some vital links during my attempted resizing/reclaiming of harddrive space. How do I fix this without having to reload either all of my Mac info or all or my Win7 info? I'd hate to consider the last two days of my life loading this crap up a complete loss.
Thanks in advance!

Thanks for checking in, BDAQua.
Problem solved.
In the docs that came with my Powerlogix accelerator card, I found this sentence buried:
"If you reset the PRAM, the NVRAM code for OS9 compatibility is cleared, so you will have to boot from the Firmawre Update CD and perform this process again in order to boot in OS9."
The "process" it's referring to is the process of setting up the NVRAM for booting into OS9 from the CD.
Fortunately, I was able to find the disk, and it worked as expected. I can now, once again boot into OS9.
Conclusion: My (unadvised) attempt to load Leopard on this old machine apparently reset the PRAM on the accelerator card and cleared the NVRAM code for OS9 boot. Although I did attempt to reset the NVRAM via Open Firmware, it did not reset it on the accelerator card.
So, thank you BDAQua, for your "Ah yes" . . . that's all I needed to steer me in the right direction.
Gratefully,
tupester

My iMac will no longer boot after half installing Maverick (only the essentials package was opened). How can I reboot it back to 10.8.5?

I was able to get a copy of OS X 10.9, but it wasn't the one straight from the App Store (which is free and I wish I knew before I got this other copy, but oh well). There is nothing wrong with the copy, it just simply doesn't initiate the install when you double click on it.
I installed one of the packages (essentials) off file, but not all the rest of them. For some reason the other packages weren't opening because it wasn't accepting my password, so I restarted the computer to see if that would make anything better.
It didn't. It now boots to the grey apple screen and stays stuck loading. I assume because only some of the install disk was installed, it doesn't really know what to do. But how do I fix this? How do I unistall the essentials package so that it goes back to normal?
I tried booting it whilst holding down "Command+Option+P+R" and it takes me to a limbo area where you can access disk utility. Within disk utility I can see that everything is still there.
What is the process to get it back to normal (I previously had 10.8.5).
Please help!

Thanks for checking in, BDAQua.
Problem solved.
In the docs that came with my Powerlogix accelerator card, I found this sentence buried:
"If you reset the PRAM, the NVRAM code for OS9 compatibility is cleared, so you will have to boot from the Firmawre Update CD and perform this process again in order to boot in OS9."
The "process" it's referring to is the process of setting up the NVRAM for booting into OS9 from the CD.
Fortunately, I was able to find the disk, and it worked as expected. I can now, once again boot into OS9.
Conclusion: My (unadvised) attempt to load Leopard on this old machine apparently reset the PRAM on the accelerator card and cleared the NVRAM code for OS9 boot. Although I did attempt to reset the NVRAM via Open Firmware, it did not reset it on the accelerator card.
So, thank you BDAQua, for your "Ah yes" . . . that's all I needed to steer me in the right direction.
Gratefully,
tupester

HT201255 MacBookPro Early 2011 updated to Yosemite will no longer boot.

Hi All,
I had a Mac issue a few months ago where it started to work very slow, lagging, the turning ball kept appearing.
I backed up what I needed therefore, I care less about the data.
Since then, at some point I wanted to encrypt it but I believe I might have done something to it with an interruption. In any case it kept working and that bar started appearing bellow the apple logo.
Shortly after -> completely unbootable.
My troubleshoot so far:
1. Reboot -> nothing
2. Single user mode -> ran the shown commands and said the Drive is OK -> rebooted -> nothing.
3. Ran in verbose mode, saw several errors:
BUG in process suhel[perd[136 (and 139)]: over released legcay external boost assertions (1 total, 1 external, 0 legacy -external)
also saw in the work up of verbose _> error 107 rebuilding /system/library/Caches/com.apple.kext.caches/startup/kernelcache
Also a Warning: couldnt block sleep duringncache update
and Warning: proceeding without DlskArb
Previous shutdown cause -128
DSMOS has arrived
What else did I do:
Tried the AHT -> ran normal test and extensive test -> Both reported that there "are no troubles"
I tried Cmd+R and just R -> a few times I saw the spinning globe asked me for WiFi pw -> no success. Reboots and cant enter any GUI
Tried Safe Mode or Recovery where you have basic functions and DiskUtil -> I cannot even enter.
I have reset the NVRAM etc but no go
I made a Yosemite and Snow Leopard (My original OS) bootable USB Drives and tried booting from them -> it goes to a grey screen and nothing else from the Snow Leo
The Yosemite -> did not even want to boot up. It didnt found it once and then new USB found but not booted.
I believe I havent tried anything else but I am still unable to access my computer.
I do not have the original disks (Cant find them)
Oh, I tried with a Windows installation disk, just to see what might happen -> black screen.
Please, desperately need help. I have a VMWare OSX at the moment and several flash drives I can experiment with.

Previous shutdown cause -128
A negative shutdown code may indicate a hardware problem. The precise meaning of the codes is not publicly documented.
If you haven't already done so, you can try resetting the System Management Controller. Otherwise, or if the reset has no effect, see below.
Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. You may have to leave the machine there for several days.
Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional—ask if you need guidance.
If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
Keeping your confidential data secure during hardware repair
Apple also recommends that you deauthorize a device in the iTunes Store before having it serviced.
*An SSD doesn't need to be zeroed.

Macbook pro will no longer boot from main sata bay after Yosemite

Hi!
I am really stuck as to why my macbook pro will no boot from the main Sata bay.
I have the macbook pro late 2011 - a few months ago I installed a samsung 840 evo, and moved the 500gb hdd into the optical bay and all has been working perfectly until last night.
I installed yosemite two days ago and it worked perfectly to begin with... then when I re opened my laptop everything was frozen. I restarted it and it wouldnt get past the grey screen. Then I managed to get it to the internet recovery stage....however it would not recognise the SSD, so I had to install Lion on the HDD.
After I logged on it gave me the message saying that the disc is not readable and on disk utility I can only see the "samsung ssd" but no details about it.
I thought that the SSD may have gone, but when i removed it and plugged it in via USB I was able to boot from it with no issues.
Does anyone know if this has anything to do with the new OS? or whether it is the Sata cable?
Thanks for any help!!!

Hi, I have been having the exact same problem with a late 2011 MBP 15 inch. I replaced the hard drive with a samsung SSD 1.5 years ago, along with a samsung SSD in the optical drive. It worked great until the Yosemite upgrade. The MBP seemed to work reasonably well for a few days after the upgrade, but then it started stalling on various programs (spinning beach ball on Mail, Safari, etc). Start-ups were also longer and had a loading bar each time, which was new since the upgrade. I left the MBP to sleep last night and when opening it, it crashed and tried to restart. On restart it loads to the login screen, then after I enter the password it partially loads (based on the loading bar), then shuts off. I removed the SSD and plugged it in with a USG, but that didn't change anything. Here is a picture after using CMD-V before it shuts off.

Re-imaged brand new iMac and no longer boots

Hiya,
I did this in the past and naively did it again! We use a fairly up to date image that we restore machines with, however on this occasion a new iMac came in and I re-imaged it. Sad to say, the machine boots up with a slightly turned no entry sign. I seen this in the past and think it has something to do with the image not recognising the new chipset...
However, I tride the Recovery technique to download and install a fresh copy onto the mac-hd. It seems to work with no error issues and gets as far as rebooting but then the no entry sign appears again!
Does anyone have any ideas as I doubt we will get a new iMac in any time soon to take an image of it?
Thanks

New machines usually come with a computer-specific build, rendering installing images made with earlier versions unworkable. However, since wiping and restoring via the recovery mode failed, contact Apple's Express Lane and let them sort things out.
P.S. Zap the PRAM and Reset the SMC, then try recovery again.

New partition & windows no longer boots

Hey all, up until now i have had 3 partitions on my drive - Snow leopard, General media and Windows 7. I decided to add a linux partition and made a new partition using disk utility. I boot up to the choose disk screen to install ubuntu to find that windows is no longer an option for boot up, so i deleted the new partition and it still won't boot into windows anymore.
How can i restore the booting function? Doing it with a linux partition too would be preferable but it isn't necessary.
Thanks,
Brad

Hi Brad and welcome to Discussions,
Hi John,
A later done partitioning to add additional partitions to a harddisk alters the position of the BootCamp partition in the partition table so that the Windows Bootloader can not 'find' the Windows partition.
With Windows XP it helped to simply edit the Boot.Ini file and point it to the WIndows partition.
With Vista and Windows 7 there no longer is a boot.ini but EasyBCD http://neosmart.net/dl.php?id=1 can do the same.
One thing to remember though is, that even Vista and Windows 7 'suffer' from the limitation of four partitions on one harddisk immenent to the Master Boot Record (MBR) since Apples EFI/GPT/MBR emulation can not handle Extended Partitions and Logical Partitions inside an Extended Partition.
Regards
Stefan

15" Macbook Pro (2007) will no longer boot in any manner. (Please, help.)

Evening, everyone.
I could beat my head against the wall for all the frustration my MBP is giving me! I really hope some kind soul will be able to help me. I will try to be methodical in explaining the whole story of what I have done and what appears to be wrong, so that maybe you fine detectives can pluck out the relevant information and piece a solution together:
I was multi-tasking about two days ago (perhaps too much) and I had installed the most recent OS X (Leopard) Auto-update. I had also downloaded and installed the program "Little Snitch," and both the update and Snitch were asking that I restart. So, I did--sure enough, it went to the spacey-purpley Leopard screen and appeared to have successfully updated. It shut off and began to boot up as usual. However, it appeared to be stuck at the Apple and rotating dial screen, with the bluish-greyish background. All of a sudden, the screen went black and the computer shut itself off completely.
I tried to turn it back on, with the exact same sequence of events. I ran it in Cmd-V mode (is it called.... verbose?) and it mentioned Little Snitch amidst the rest of the report (which is what makes me concerned that it might be the source of the issue). At the end of the repost, it said something about "shutting off the CPU" and "killing all processes." Then, again, it shut itself off completely. I tried Cmd boot up (to select the boot disk, as I have a Bootcamp partition with Windows XP that has never caused me trouble before) and selected the OS X volume. Again, no change.
Finally, I hunted down a friend who had just purchased a new Mac to borrow his OS X install disc. I upgraded to Tiger, so I don't know if that might be why his boot disk did not work for everything I needed it for. I don't have Y disc with me, because I'm from California and I left it somewhere in my office. But, I was able to boot from his disk--although it reported that I "could not install OS X Tiger on this machine"--and use the Disk Utility. I tried to use the verify and repair functions, but they both came back with "sibling errors."
I may have made a crucial error here: I then tinkered with the Open Firmware Password Settings. I tried a few of the things I already had over again, and then went to bed.
Well, that was all last night. I came back from work today, determined to try using target disk mode and my friend's mac in order to solve the problem. I followed all the procedures necessary, plugged in the cable, booted up my kaputnik target computer holding down the "t" key, but my computer was totally unresponsive to the command. Now, NONE of the start up commands will work. I cannot boot from the OS X disc, I cannot run the cmd-v thing, I cannot "Cmd" select a drive at startup... I don't know if this has to do with my setting of a firmware password, because it was not doing any of this stuff yesterday.
I'm freaking out. I'm a student, it's finals time, and I have 3/4 of my thesis on that machine. Please, help me work this one out. Even if it's just a way to get to the hard drive in target disk mode to get those files I need without really fixing the problem. I'll be happy to provide any other information that might be helpful in finding a solution.

Restart with the Option key held down and the Mac OS X install disk inserted, provide the firmware password, click on the DVD, press the button with the straight arrow, access the firmware settings, disable the password, and use FireWire Target Disk mode. If you can't do that or it doesn't work, contact Apple.
(38384)

After OS Upgrade, Computer will No Longer Boot from Disc, Enter T-Disc Mode

I purchased the Leopard update about a week ago and proceeded to install it (upgrade option) on my MacBook Pro previously running Tiger. After this update, I no longer seem to be able to boot from a disc(c on startup), enter target disc mode(t on startup), enter single user mode(command s on startup), basically anything that requires hitting a key on boot. In short, the operating system seems to override any of those commands and just loads regardless of what I press.
How can I fix this?? I fear that if my mac suddenly dies, I won't be able to fix it with archive and install via the CD, since I can't boot from it. I also won't be able to recover my files with target disc mode or anything.
For more in-depth details:
-My hard drive does have an open firmware password- it was recommended as part of the undercover anti-theft program that I use. Although I can tell putting the password on was a mistake, since I've read that single user mode is no longer accessible with this password active. I don't think this is affecting my inability to boot from disc or target disc mode though, as I was always able to do this with Tiger, even with the firmware password active.
-I have tried booting from other discs, like my old tiger OS disc that came with the laptop- that fails too.
-My Leopard installation was not clean. Like many others, I used the upgrade option and it appeared to work ok- until restart, where I was faced with the blue screen. Since I was unable to boot to single user mode and try removing potential APE files, I let the computer sit for an hour on the blue screen until it finally loaded. Upon getting in, I found that I did not even have APE's installed. I proceeded to reinstall the operating system via an Archive & Install. Upon boot after this reinstall, I still received a blue screen that lasted a long time, and the OS loaded very slow. It did this for a few additional boots afterwards, and has appeared to smooth itself out now, a week later. The OS now loads fine and works alright (from what I can see), but I still can not boot from disc or anything else.
If anyone at all knows a solution for this, it would be much appreciated. I wanted to suspect something like the disc drive going bad, but being that things like the target-disc mode aren't working either- I'm hesitant to believe its just the disc drive. Being that it also happened just as I upgraded to Leopard and faced issues, I have more of a hunch that its something to do with Leopard.
I apologize if this has been answered before, but I've looked all over the site, google, everywhere I could think of and came up with no answer.
Thanks ~Brian

Hi, I have been having the exact same problem with a late 2011 MBP 15 inch. I replaced the hard drive with a samsung SSD 1.5 years ago, along with a samsung SSD in the optical drive. It worked great until the Yosemite upgrade. The MBP seemed to work reasonably well for a few days after the upgrade, but then it started stalling on various programs (spinning beach ball on Mail, Safari, etc). Start-ups were also longer and had a loading bar each time, which was new since the upgrade. I left the MBP to sleep last night and when opening it, it crashed and tried to restart. On restart it loads to the login screen, then after I enter the password it partially loads (based on the loading bar), then shuts off. I removed the SSD and plugged it in with a USG, but that didn't change anything. Here is a picture after using CMD-V before it shuts off.

New windows will no longer open

Within the last week neither chat windows on some sites or any new windows other than firefox home page ( and related tabs will open) Any help would be much appreciated.

Start Firefox in <u>[[Safe Mode|Safe Mode]]</u> to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.
*Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
*Do NOT click the Reset button on the Safe Mode start window
*https://support.mozilla.org/kb/Safe+Mode
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
It is possible that your security software (firewall, anti-virus) blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.
Remove all rules for Firefox and the plugin-container from the permissions list in the firewall and let your firewall ask again for permission to get full, unrestricted, access to internet for Firefox and the plugin-container process and the updater process.
See:
*https://support.mozilla.org/kb/Server+not+found
*https://support.mozilla.org/kb/Firewalls
*https://support.mozilla.org/kb/fix-problems-connecting-websites-after-updating
Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) as a test.
*http://www.bleepingcomputer.com/tutorials/how-to-start-windows-in-safe-mode/

How do i retrieve file vault protected files from an external hard disk that used to be my mbp's hard drive? the hard disk got corrupted and will no longer boot. I put it in an enclosure and attempted to copy my files but failed because of FV encryption.

This external hard disk used to serve as the main drive of my mbp. It got corrupted and the OSX would no longer load. I upgraded to a 500gb hd and used the old hd as an external drive. I tried to copy my files but i could not access them because of the filevault encryption. 110gb of hd space appears as used which means that my files are still in the drive. Is there a way to retrieve these files? thanks

According to your post, you're using Leopard, so FileVault only encrypts your user folder (unlike Lion). On the mounted external drive, in your user folder, you should see a file called username.sparsebundle, with username being your user name. Double-click that file to open it and it should prompt you for a password. Type in your password and the file will mount as a volume in Finder. You should be able to copy all of your files over.

During an update my Mac turned off and will no longer boot into the user interface.

The situation is that I don't have an os disk with me - traveling abroad - and would like to be able to create one using my PC.
- First is this possible?
- Second, will I lose my personal data upon system reinstall!
As far as the boot sequence goes is the apple logo and the spinning wheel...
Just thought of this, is there a "last good bootup" option available as an option or some other way to recover without reinstalling?
The situation was that I have a bad battery and the chord was accidentally unplugged... Pretty bummed at this point... :(
Thank you in advance!

So far I have tried to use the option, and a few other keys on startup, but no-go...
I found a snow leopard install .dmg file download on the apple site, since my MacBook is from 2005, but only have a PC to create the disk image from - if that will even work at all...
Will keep updating as I move forward... Any help is appreciated!

NEW G5 will no longer boot up...

Similar Messages

Maybe you are looking for