Illustrator CC fails to boot on my mac.

I just downloaded Illustrator CC on my mac. It begins to launch, but fails to boot and quits. No screen prompts appear to tell me what happened. It just doesn't start.

Ensure that the following connector is connected properly
Quote
JPWR1 ATX 24 pin power connector
JPWR2,atx 12V power connector which is used to provide power to the cpu
JPWR3 12V power connector is used to provide power to stable the operation of graphic card
As well as the Front Panel Connectors: JFP1/JFP2 as in power led, power switch, reset switch, hd led etc

Similar Messages

Win7 x64 install fails at boot with alternating Mac and Cross-Circle Logo

Thanks for reading.
I have a new late 2009 i7 2.6Ghz Macbook (6.1 model) that I purchased in February this year. I'm having real problem trying to get a Windows 7 DVD to boot on it; whenever I try (either by using the bootcamp assistant to parition my drive then start the boot process, or by holding down the OPTION key, or even using the C key at boot) instead of the normal Windows 7 boot process, the disc spins, then I am left with an alternating Apple logo with a circle with a angled cross line through it, sometimes showing a folder with a ? mark.
I have tried resetting the PRAM, using other Windows 7 media, but I just can't seem to get a disk to boot. I have even tried wiping my Mac parition in case it was a corrupt partition by backing up to a timedesk then reinstalling, but again when I come to install Windows 7 I get the same problem.
I can boot the Mac OS install disks not problems.
Really appreciate if anybody has any guidance or resolutions?

Hi - no nothing plugged, except my external DVD drive.
I managed to install TechTool Pro's emergency EDRIVE from DVD, and have managed to reinstall Mac OS X without any problems, so unsure about a hardware problem. All TechTool tests come back ok, so no issues seem visible from that.
You might be thinking why I am using an external DVD; well this is because I've taken out the internal DVD using OWC Datadoubler http://eshop.macsales.com/item/Other%20World%20Computing/DDAMBS0GB/
I have a 512GB SSD in the normal hard drive space, and a 500Gb Hybrid disk where the DVD drive was. The drives are seen perfectly well in Max OSX; indeed when I did a reinstall I used the 2nd internal hard disk as the time machine and then restored from it.
Could it be a problem with partitions or some issue with the EFIboot from the Windows 7 DVD's? I've tried looking at rEFIit http://refit.sourceforge.net/ to see if that would help, but no luck.
The data doubler shows examples of this being used in my mac model for a specific Windows implementation (which is why I bought it) so don't think its that. Anybody have any ideas?

Macbook Pro Fails to Boot on Operating System

After Restarting My Macbook Pro 13" 2012 it repeatedly fails to boot up to Mac OSX but instead to OSX utilities. I tried to reinstall Mountain lion but it shows me that Macintosh HD is locked and when erasing it , it tells me couldn't umamount Disc. Any solution!!! Thank you

Found a solution. As expected, I needed to restore the firmware. However by just downloading the firmware update, OSX didn't want to write the firmware as it was already up-to-date. OSX has no way to know up-to-date but defective.
Found this thread:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/774089
which lead to
http://pubmem.wordpress.com/2011/04/09/flash-efi-firmware-update-manually-on-a-m acbook-51/
that explains how to FORCE a firmware to be written.
I had to download this free software
http://www.macupdate.com/app/mac/16357/unpkg
to unpack the EFI udpate downloaded at
http://support.apple.com/kb/ht1237
I would say that a good command line knowledge is needed to process the above steps.
Hopefully I was able to find a solution before admitting that the logic board was defective and pay the 600$ for its replacement, as instructed by the genius at the Apple store. They are not allowed to process firmware restoration, but they should at least suggest it before proposing an expensive logic board replacement.
Good luck.

OS9 bootable G4 mac fails to boot with NI-DAQ4.9

We're going to use the OS9 bootable G4 machine with NI-DAQ4.9 driver. However, after the installation of NI-DAQ4.9 the G4 machine failed to boot up(Pure OS9 boot. Not classical environment). The error message said that address error occurred when the NI-DAQ was loaded during the icon parade.
We installed the OS completely newly without any other softwares and installed the NI-DAQ4.9 driver. So it must be difficult to account for the problem by any conflict with other inappropriate softwares. Minimum set of system extension plus NI-DAQ also caused the same problem.
Now I doubt the problem caused by the conflict of new G4 with NI-DAQ4.9 because other hardwares work OK (Other G3 or older G4 machines).
If anybody ca
n post any idea or solution on this problem, we'll appreciate.
(*)We need to control PCI-DIO-96 board with our homemade C-program, so NI-DAQ 4.9 is required instead of NI-DAQ 6.
Machine: PowerMacintosh G4(Single1.25G4 Processor)-Latest OS9-bootable G4 machine
NI-DAQ:4.9.4

First, we will want to make sure that you have the latest NI-DAQ driver that still supports C program. That driver should be v4.9.4 and can be found from the link in the previous post (or here http://www.ni.com/support/daq/mac/macversn.htm).
After verifying this, I would try to restart the computer without your hardware installed to check if it is a hardware/NI-DAQ configuration issue or if you just had a bad install of the software. If it still does not work without the hardware than you can attempt to uninstall/reinstall NI-DAQ v4.9.4.
Finally, the problem may lie with in a conflict with the extensions on your MAC. If you are familiar with troubleshooing MACs, then you can disable all but the core extensions and see if you can get the computer up and running
that way. Below are a few KnowledgeBases that discuss some of these issues:
Computer Hangs While Trying to Install NI-DAQ or LabVIEW on Macintosh
My NI-DAQ Crashes Either at Boot (4.x) or When Loading (6.x) on the Blue and White Power Macintosh G...
Regards,
Michael
Applications Engineer
National Instruments

After update mac os x lion 10.7 to 10.7.4 the os fail to boot ??

i just installed mac os x lion 10.7 on virtual machine ( vmware workestation 8) for some reasons,, after that I start the software update to update 10.7.4
after updating the os fail to boot ( changing tha Apple logo to another logo )..
what can i do to fix this problem ??

mohammad207 wrote:
i just installed mac os x lion 10.7 on virtual machine ( vmware workestation 8) for some reasons,, after that I start the software update to update 10.7.4
after updating the os fail to boot ( changing tha Apple logo to another logo )..
what can i do to fix this problem ??
10.7 client or server?

Mac OS Yosemite 10.10.1 fails to boot

I am running OS 10.10.1 on Mac Pro Early 2009. This morning all running programs including Finder froze. All i could do was Quit or force-quit the running programs and shut down. Then the computer failed to boot. I was able to boot in Safe Mode. But any attempt for normal boot failed.
Since i have Boot Camp, I tried booting to the Disk Startup Manager (pressed Option key). I got the 3 options -- (1) Mac OS; (2) Windows; and (3) Recovery. But after I selected either Windows or Mac OS and the arrow moved to my selected option, nothing happened when i clicked the "arrow" button. I could click it many times but the screen remained frozen till I powered off the computer.
Strangely, when I held down the Command key by itself the computer started normally. But subsequent all attempts to boot normally failed again.
Any suggestions?
i will greatly appreciate any help. Thank you all in advance.

Boot into the recovery partition and select Disk Utility from the 4 option menu.
Run Disk Utility>First Aid, Verify and Repair.
If the disk cannot be repaired an new HDD will have to installed.
Ciao.

Tip - Mac Pro fails to boot up, no chime.

I have a Mac Pro (Intel, 2008). Within the last 6 months, a situation with the Mac Pro has occurred twice.
While asleep, or shut down, I press the Power button to start up the Mac Pro leading to the following events:
the graphics card fan runs at full speed.
the LED indicators on the RAM cards all light up red.
the HDD's begin to spin.
the startup chime does *not* sound.
the screen does *not* turn on.
the fan does *not* slow down.
several seconds after pressing the Power button to start up the Mac Pro, it shuts itself down.
it is not possible to reset the PRAM. (the startup sequence does not proceed far enough to allow this to happen.)
resetting the system via the reset button on the mother board does not affect the situation.
replacing the PRAM battery does not necessarily correct the situation.
removing every HDD, RAM card, PCI card and cable does not correct the situation.
this is what has worked for me.
assuming that the Mac Pro is not powered up:
unplug the power cable.
press the Power button for 5 seconds to drain any residual power from the system.
let the Mac Pro sit idle for 12 to 24 hours. (10 minutes simply doesn't do it!)
plug the power cable in.
press the Power button to boot up the Mac Pro.
removing the HDDs, RAM cards, PCI cards and cables may or may not affect your situation.
the first time my Mac Pro booted after this procedure, only 4GB of RAM was recognised by the system. I shut down the Mac, removed and re-inserted the RAM cards and booted the Mac up again. the Mac then recognised all of my RAM (20GB).
hopefully, we'll see a new generation of the Mac Pro this year with *both* firewire and thunderbolt.
cheers all.

Hi Greg! Yeah good tips. I'd like to add a few other tips that worked for a few of us. I have a 2009 nehalem MPro, 16 cores, 4 used internal bays, 5870 (added in 2011), replaced main boards, power supply, memory and CPU modules under extended warranty. Several ATTO pcie sas cards (r380,h380) bla blah.
History:
Ok, we we moved the whole suite to new premises some months back and the transportation was safe and well and due to premises issue, the setup above Nd the disk arrays etc sat I. The packing for two weeks...
Issue:
Mac Pro would not power on some times.. Else it would power on and then after or during startup would shutdown.
Cure:
Did most of the steps you described and
1) pulled all the disks from bays 1-4, pulled all the pci hba card including the ati 5870, pulled the two DVD player units and lastly, the CPUs and memory module unit.
2) cleaned all contacts with cans of clean compressed air of all the above
3) then proceeded to replace each component then powering up the Mac Pro and make sure the startup chime occurrs, then power the Mac Pro off.
4) I started with the memory module with a single DIMM in the memory, finally replacing them finally with all of them repeating step 3. I did find a bnd memory dimm doing this. Don't worry if the Simms are not inthe most efficient slots.. Fix this later.
5) replace the GPU card (in my case ati 5870) strap Nd shutdown
6) this time hold the power button in for at least 20 seconds and reset the SMC.. Wait for the squeal!,
7) then do one of the disks or the disk set that you start from..
8) restart. .. Wait for it to settle. Power off
9) plug in the mainscreen display and restart .. By now it all should be ok.
10) power off again. Power up again with key board and restart and then shutdown
11) add/insert each pcie Hba power up and. Reset the SMC AS IN STEP 6 and shutdown. Repeat for any other MAKE SURE THAT THE SPEED OF THE PCIE card matches the rating of the slot. so remaining hbas.
12) should be looking good by now.... So login and then shutdown
13) and remainder of the internal disks , power up and access file systems.
14) should u get the memory manager appear at startup and recommend to re-organise the memory Simms, then print the report or use your iPhone to record the display, shutdown and move the dimms s it requests.
15) lastly serially plug in other peripherals and see hat they can be accesses.
Summary: worth the effort NDS time. Macpro has been solid ever since.
Hth
Warwick

IBook G4 fails to boot with internal HD installed, works when removed

The short version: My iBook started failing to boot via any method (gray screen) and the boot menu (Option during startup) would freeze. Replaced HD, things were better. Six months into new HD, nearly the same symptoms appear again. Removed HD, now running off different HD via FireWire.
The long version–
Back in late 2008-12, my iBook started failing to boot up. Usually it would refuse to boot from any source. Booting the internal disk (10.4.11) would get to a gray screen without any logo and stay there. Holding down Option, the boot menu would come up, but it would usually freeze before it displayed any volumes. Booting from CD (AHT, or OS install disc) would fail in nearly the same way as booting from the internal drive. Target Disk Mode would start, but once the other machine tried to access the drive, the FireWire logo would stop moving and the drive would never show up on the other computer. Very rarely, the machine would get a bit further through one of the boot mechanisms, but it usually froze while booting or just after login.
This machine has gone through three logic boards in the past, so I suspected that was the problem again. I took it to a local Genius Bar and the Genius explained that it was probably the hard drive. He said that sometimes, depending on the way the drive fails, it can "take out" other parts of the system due to drawing too much current, etc.
I was a bit skeptical, but it was going to be much cheaper to replace the HD myself than it would be to send it in for a MLB replacement. So I ordered a new HD (80G) and a USB-to-ATA/SATA adapter. I hoped that I would be able to use the adapter to savlage a bit more data off the drive (it originally failed right before a backup!).
After extracting the HD (40G), I connected it to the USB adapter and was able to access the drive just fine. I used another machine to run another backup from the recently removed HD (40G) to one of my FireWire backup drives and proceeded to put the iBook back together with the new HD (80G).
Once it was all back together, the new HD worked fine. I was able to restore the recent backup from my FireWire drive to the internal, and it worked fine. The only oddity I noticed was that the new drive was apparently trying to sleep several times a minute. I used smartctl (installed via MacPorts) to adjust the power management setting on the drive, and that seemed to help. I also started running smartd (also via MacPorts) to better monitor the new drive.
Recently, a bit more than six months after the new HD was installed, the new HD started showing errors in the system.log. I never found any errors in the logs after the previous HD failed (even though I could look through the logs just fine with the drive attached through the ATA-USB adapter).
Jul 2 18:04:40 Blinky kernel\[0]: disk0s3: I/O error.
Jul 2 18:33:43 Blinky smartd\[217]: Device: disk0, ATA error count increased from 0 to 30\n
Jul 3 02:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 30 to 31\n
Jul 3 03:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 31 to 32\n
Jul 6 23:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 32 to 33\n
Jul 7 00:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 33 to 34\n
Jul 7 12:42:24 Blinky smartd\[217]: Device: disk0, ATA error count increased from 34 to 36\n
Jul 7 13:17:59 Blinky kernel\[0]: disk0s3: I/O error.
+same error message a bit faster than one every 3 seconds+
Jul 7 13:23:00 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 13:33:44 Blinky smartd\[217]: Device: disk0, ATA error count increased from 36 to 615\n
Jul 7 21:17:05 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:15 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:18 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:21 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:23 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:29 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:18:17 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:19:21 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:19:23 Blinky kernel\[0]: disk0s3: I/O error.
I did not notice the errors until the afternoon of the 7th when the problem became evident. The events around 13:00 happened when I was trying to run a backup. The first backup failed in an odd way (when I came back to check on it later that evening, SuperDuper! seemed to have quit running). So I restarted the backup and started looking around in the logs. That is when I noticed the kernel I/O error messages. When I asked smartctl to query the drive, it showed that many errors had been occurring and it displayed the drive's log of the last five or so errors (alas, I did not save this output). Meanwhile the re-run of SuperDuper! was having problems again. It seemed to have hung (no SDAgent or SDCopy processes were running, but the main UI was still there). Since the backup was not getting anywhere, I decided to shutdown for a while and try again later.
When I did try again later, I was back in the situation of six months ago. It would not boot at all (no internal, no FireWire, no CD/DVD, boot menu hangs, Target Disk Mode hangs). So, I opened up the system, removed the HD and put it back together without an internal HD. The machine is now able to boot and run from FireWire. Again, the (6 month old, 80G) HD "works fine" via the USB adapter. If SMART were available through the USB adapter, I could check to see if the drive is continuing to have problems. I used SuperDuper! to copy the HD to a volume on my FireWire drive which is how I an now running the system.
Has anyone had any similar problems? Any idea why my iBook seems to be killing/rejecting hard drives? (I say killing because, while the drive is connected internally, it certainly seems to be dying. I say rejecting because once the drive is out of the system, both the drive and the system seem to "recover".) I have read messages there where others report success having their iBook MLB resoldered ("reball"). Has anyone experienced substantially similar issues that were solved with a resolder repair?
Thanks!

I was able to test my “failing” ATA drives in a G4 Mac mini (I had to take the mini apart because its drive had finally failed). I was able to successfully boot the Mac mini with either of my iBook drives installed. Once booted, +Disk Utility+ said that each one's SMART Status was Verified. I used smartctl to pull the full SMART info while I had them installed in the Mac mini.
Since the drives were still “good”, I think this emphasizes that the problem is with the ATA interface on my iBook's logic board. Maybe it is broken, or maybe it just needs to be resoldered. For now I am happy just booting off an external Firewire drive.
BTW, I ended up installing the 6 month old 80G drive in the mini. It has been working OK for 10 days now. As long as it continues to operate normally in the mini, it will serve as evidence that my iBook's HD ATA controller is borked. I just hope the ATA controller is more capable of accepting its fallibility than was HAL.
There is a minor problem with the 80G in the mini in that I am unable to use hdapm to change the aggressive head unloading that the drive suffers. I was able to adjust it with hdapm while it was in my iBook. I am able to adjust it with hdparm under Linux on the mini. Luckily the change I made while booted in Linux "sticks" after rebooting back into Mac OS X (I hear it will be lost if the drive is completely powered off though).

[SOLVED] Arch Linux Duke (2007) Fails to Boot

Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch. It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
If you have read this far, you are a trooper. Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
:: Loading udev events [Pass]
:: Mount root Read-only
:: Checking file systems
This is where it stops.
The next thing I see is:
/dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
E2fsck –b 8193 <device>
I then get a sort of character based splash screen that says
**********FILE SYSTEM CHECK FAILED ****************************
* Please repair manually and reboot. Note that the root file system
* is currently mounted read-only. To remount it read-write, type:
* mount –n –o remount,rw /. When you exit the maintenance
* shell, the system will reboot automatically
Give root password for maintenance
At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
/dev/sda6 on / type ext3 (rw)
This is exactly the root partition that the start up complains about. It is clearly there. I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
# mknod “/dev/root2” b 3 6
(“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
image = /boot/vmlinuz26
root = /dev/sda6
label = ArchLinux-Duke
initrd = /boot/kernel26.img
read-only
I am stumped. Thanks in advance for any and all pointers you may be able to offer.
Last edited by mac57 (2014-06-02 17:42:21)

Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next. This is my guess anyway.
I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

Imac fails to boot - at all

Hi,
I restored my imac using original disks and then updated the osx to current over the web. all fine so far. then restored the system (full disk image) from time machine to recover my data. restore said it worked ok but when the machine restarted it failed to boot and i just get a list of script top left of screen saying launch faild, debugger called etc. Then gray screen and grey box in middle of screen saying you need to restart the computer. This i have done numerous times but it just does the same thing again and again. More worrying is that the machine will not boot from original disks either. Any ideas before I take it to the apple store?
Thanks, Pedro

If the disk image or time machine backup was from a older version of OS X then what was currently installed restoring that image/TM backup may have corrupted the newer version of OS X.
I suggest you start over by wiping the drive completely, then Restore your Mac from that TM/Image backup and Then Upgrade to Mavericks.
You have the steps slightly backwards. The latest thing you should do is upgrade the OS to the newest version.

OS X completely fails to boot

Hi there.
I've really screwed up my MacBook Pro. Post installing Quicktime 7.1.1 as part of a software update, I found that I wished, albeit temporarily, to revert to 7.02. Obviously, I wasn't going to be allowed to install that, so I figured I'd just use Pacifist to force an install, as I've done in the past for other software that refused to install for whatever reason (never Apple software though...could be the problem).
So, did that. Attempt to open Quicktime. Bounce, bounce, icon disappears. Hmm. Attempt to open System Preferences. Bounce, bounce, nothing. Oh dear.
I then downloaded the .dmg for QT 7.1.1, but it just refused to mount, so I then shut down the computer and restarted. OS X now completely refuses to boot, it gets as far as very slowly filling the blue bar at the OS loading screen, but then does nothing.
I've so far attempted to boot into safe mode by holding Shift as I boot up, but that just results in the MacBook reminaing on the spinning icon and the grey Apple logo till I release the key (after a good few minutes), and then it just tries and fails to boot OS X again normally.
I've also put my OS X install/recovery disc in the drive and booted from that, repairing the disk (it found no problems...awesome) and disk permissions (I'll admit I never thought that that would do anything anyway). Both failed to help, obviously.
Any ideas what I could do? I'll be gutted if I have to wipe my HDD and reinstall OSX; I'm guttered there's no rollback/restore feature on Macs, something I always found useful in these situations back when I used Windows.
Any replies are greatly appreciated.
Joe

You can re-install without losing most of your settings and without losing documents / files (unless something goes severely wrong).
Archive and Install will allow you to re-install while saving all your documents and files.
You can read about this technique here:
http://docs.info.apple.com/article.html?artnum=107120
Once you have re-installed, you can then upgrade your OS to 10.4.6 and QuickTime to 7.1.1
You really are not going to want to run a version of QuickTime prior to 7.1.1 on your system. Read the following documents for more information:
http://docs.info.apple.com/article.html?artnum=303176
http://docs.info.apple.com/article.html?artnum=303787
The Archive and install is probably your best option at this point.
Hope this helps.

Illustrator CS4 Fails to Display Font List In Yosomite

Illustrator CS4 Fails Display Font List In Yosomite, but displays Individual Font Family Names, I scroll down to about where I think it should be then check each font family till I find Correct one. As I am cutting back on work load in preparation for retirement, I have deleted my Font Manager rather than upgrading it to Yosomite and reverted to "Font Book".

Just discovered what appears to be the fix on another website. It was a fix for CF5 but it appears to work just fine for CS4 as we;
Open the Mac OS X System Preferences and head to ‘Accessibility.’ Once you are in there, select ‘Display’ from the left-hand list and then check the checkbox that says “Reduce transparency.”

Boot camp often fails to boot - fix?

Boot Camp often fails to boot at all, leaving the iMac dead at the bootloader screen. Have to force shutdown by holding down power button. Full hardware test declared the hardware 100% functional. Disk Utility and chkdsk sees nothing but fire. This is intermitent/random and it proved impossible to "force" it's occurance. It happen when it darn well please?
First occurance goes back to late July 2011, a few days after a major thunder storm that caused pulsing power blackouts (as in, very short bursts - like turning off the power then immediately flipping it back on - too quick to actually shut the computer down). Surely, this must be the source of the issue? Right? Alas it doesn't adds up. Power supply of this house is very stable and reliable. Power fluctuations are unhearded of. It's also connected to a surge protected outlet. The system itself, in Mac or Win, is flat out stable. It does not freeze out of the blue like what a damaged power supply would cause. It only ever freeze upon choosing a partition via the boot camp interface.
Further observation as compared to normal boot procedure: Upon selection of the Windows partition, the LED on the USB mouse turns off then back on again a short moment later. Windows loads up normally. When the crash occurs, the LED never turn back on. It's just dead right there and then.
What's going on and what can I do to fix this? It feels like some hardware initialisation fails for some reasons. It's ough to be around the USB systems itself but what do I know anyway?
P.S.: Please, don't mention the dreaded format and re-install. It's a 20 hours job. I'm not going there. ty
Message was edited by: Virgule - changed a "foul" word

Why not upgrade the surge protector to a UPS? good units are very affordable.
Put all your sensitive equipment like modem/router, computer, electronics running off UPS.
CyberPower SINE 1000VA/600W $137
http://www.amazon.com/CyberPower-CP1000PFCLCD-1000VA-600W-Compatible/dp/B00429N1 92/
Well, sometimes if you don't have backups, and refuse to do what you may need to....
There are troubleshoolting tips and faqs I'm sure on the 'net.
Starting with Windows 7 DVD for one
Even OS X won't survive with forced (hard) shutdowns.
If it only happens in Windows, and you were running OS X when the outage occurred...
USB devices and cables can be hard to ID but swapping cables and stuff helps.
As for Disk Utility, it does not look at drive sectors or files for issues.
If you really want to scan a hard drive, use the vendor's own Linux or Windows utiilty to recertify the sectors.
If you haven't done any deep cleaning of files, registry, even uninstall and reinstall components.
I just did a reinstall. Partially to be a test run for when I have to install Windows 8 next week, also to clear up a problem I had, possibly a rogue web site using a rootkit to hide files and icons and programs disappeared and icons became generic. So yes I don't take it lightly, but the new install runs much much better (over two years since last install).
AHT is not a 100% reliable at finding everything, only what it actually is designed or suppose to look for.
A semi-loose DIMM or faulty can be enough, and not likely AHT or Memtest will find it, but Windows does tend to spot a problem with RAM during installs.
CCleaner 3.x
Driver Sweeper 3.x
START: run %TEMP% - Select All and send to Recycle
Lion Recovery - show all hidden partitions and check health of all, hidden debug menu in Disk Utility can be enabled in command line
Some partitions (GPT, EFI, System, Volume Information Block) are only tested during format where each sector does get a thorough check for errors because they can't be mapped out later. When you do chkdsk etc you only test user partition areas and not the 'entire' drive, unless doing a full initialization. And GPT requires that the VIB and also the backup VIB both be error free - in the past the backup VIB if it failed was "optional" though, it is not now.
If you clone OS X then it is easy to move it to another drive and also to do full initialization and restore. If 3 days of your time isn't an option maybe time to invest in program(s) and methods that can backup and restore.
Trying to find the needle in haystack that you have limped along with I guess since July (since installing Lion? maybe ?) can take 3 days probably, unless you are lucky enough to replace a mouse or cable on first step and it all goes away (hit the lottery or get hit by lightning odds)

Imac g4 only boot up to mac osx login screen ,then just sit there , did the fsck .

THIS IMAC G4 FAILS TO COMPLETE THE STARTUP PROCESS.
CAN GET IN SINGLE USER MODE AND RUN FSCK ETC.
EVERY THING LOOK NORMAL.
LOOK S LIKE A NORMAL BOOT APPLE LOGO   AND PROGRESS MARKER.
THEN THE MOUSE POINTER TOP LEFT CORNER AND BLUE BACK ROUND SCREEN.
WITH BOX IN THE MIDDLE OF THE SCREEN WITH "MAC OSX"
STOPS RIGHT THERE ,
NO OTHER MESSAGES   .
THE MOUSE CURSOR MOVES .
LEFT IT FOR HOURS .
THANKS IN ADVANCE EVERY ONE.

@a brody thanks for CAPS tip , new to apple etc "when i started in 73 did not have low case" guess its stuck with me all caps.
yes we have some applications on the disk and data, like final cut pro,   it worked perfect until 3 days ago.
@Limnos Safe Mode , did try and held it (shiftkey) down from beep thru the boot logo box MAC OS X,
no safe mode appeared. did try this a number of times. took some time to start up.
I am familiar with UNIX system but not with MAC OSX 10.4
Also renamed the .globalpreferences.plist to .globalpreferences.dead in directory /library/preferences/
made no change ,still booted to blue screen cursor in corner with white box center screen MAC OS X in large letters .
The mouse can move the pointer around ,click it on the white box the colored busy circle appears.
It just sits there for hours.

IMac Model No: A1312 running OS X fails to boot.

I work in a school. We have a number of Mac devices. One being an iMac Model No: A1312 running OS X. Today this machine failed to boot – instead it started up but after about a minute of a screen with the Apple and the spinney cog wheel it dumped to a dark grey screen with an active cursor and responsive keys on the keyboard (the beep was heard when pressing the spacebar for example) but no log on box or other screen activity.
I have tried all sorts of diagnostics – hard drives comes up as ok. Reload of OS X – twice but always the same result.
Any suggestions as to what’s wrong please fellow Forum members?

Thanks for your lone response @rkaufmann87 I'd have thought more responses were offered - perhaps an indication that this is a rare issue.
There are no peripheral devices connected - the KB and mouse are wireless and clearly communicating with the device well. I've tried the suggested resolutions without the LAN cable connected and as stated in my OP with the LAN connected (from two different locations) can access the support pages etc. and indeed the machine has spent in excess of 4 hours powered up and twice reinstalling the OS X. All seems to go well but then after the restart up comes the standard start screen with the Apple Icon and the spinning cog wheel then after a minute or so it dumps out to a darker screen with just the mouse cursor visible. The mouse moves the cursor and pressing various keys on the KB brings beep responses.
As a School Network Manager, working with a very tight school budget, I'd rather get the machine sorted with Forum help and my in house effort if at all possible. The last iMac job I put out to a recommended Apple repair Workshop was for a replacement screen to a still under warranty new 21 inch iMac and that cost about half the value of the machine to get done - ouch!

Illustrator CC fails to boot on my mac.

Similar Messages

Maybe you are looking for