10.4 to 10.5 update killed FCS?

I installed 10.5.5 on my Mac Book Pro and FCS worked mostly. But I assumed I would have to remove and reinstall. It was only there because of migration moving it over. Anyway I can install FCS but EVERY app sudden quits on launch. I've done the software update to get it current and NaDa. I have used a utility to totally remove FCS, receipts packages etc and done a clean install, asked for name and serial# etc, still NoGo. And just because someone is going to ask this is not a bootleg version. Any and all suggestions would be Very welcome. At this point my only one is re-formating the drive and going back to 10.4.11 where everything was happy.
Mac Book Pro, 2 gigs RAM, 320gig HD 10.5.5 QuickTime 7.6 (472)
thanks
SK

OK so I get the big prize. Though not sure anyone else could have. ProKit was the key. After typing that my slow brain began to remember something. When I installed FCS 1 I had this problem on THIS machine. I was actually working at Apple at the time and nobody could figure out what was wrong and then I noticed (thank you Pro Environment widget) that ProKit was not installed. It had been I had been running 4.5 when I upgraded. Somehow in the upgrade it got removed. Simply copying it from my back up fixed everything. Not sure what causes this problem but that was the problem here also. There was a ProKit (Leopard) but no ProKit. Again copying it from backup solved the problem. I just need to put a big sticky somewhere for the next time!

Similar Messages

Latest Acrobat X Update Killed Com1

The latest Acrobat X update killed my Com1 port. Yes, I still use Com1 to communicate with my ham radio. So if any Adobe guy is reading the discussions in this form, please fix this bug. BTW, why do I have to call tech support, why can't I send you guys an e-mail.
. . . JohnB

To correct the port problem of Adobe PDF Printer after the application of A10.0.1 patch kindly follow the below steps (they require Admin privileges):
1.      Go to Devices and Printers.
2.      Right Click on the Adobe PDF printer and click on Remove Device (Win 7). This will delete the Adobe PDF printer.
3.      Go to Programs and Features (Win 7)
4.      Select Adobe Acrobat X Pro or Standard and click on Change
5.      Select Repair and follow instructions to complete repair
6.      After the repair is done you will have correct settings of Adobe PDF printer and also Adobe Acrobat version 10.0.1.

MacOS X 10.4.9 Update Killed My Mac!

Today I tried to install the 10.4.9 update.
Something went wrong when installing the update and I got an error message saying that the installation was unsuccessful.
After restart my mac got stuck on the grey screen with the Apple logo and a wheel spinning forever.
Fortunately I fixed the issue: http://net3x.blogspot.com/2007/03/macos-x-1049-update-killed-my-mac.html

Most likely, you could have avoided this problem if
you had followed Apple’s instructions for properly
installing software updates:
Troubleshooting installation and software
updates
Note that Apple doesn’t mention anywhere the need to
repair permissions either before or after installing
a system update, not even for troubleshooting system
update issues. It’s the disk itself (i.e. the
filesystem) that should be verified/repaired
before installing anything. Note also that no
applications should be running while installing the
update and that you may experience unexpected results
if you have third-party system software modifications
(not normal applications) installed.
I have to call complete and utter BS on this. I have been a mac user for more than 3 years. I have updated the day of almost every major update since 10.3.1 and 10.4.9 is by far the most problem prone thing I have ever seen apple put out. I have never once had a single issue where my mac would not boot after the install of an update. Now I have updated both my MacBook and Intel Mac Mini and both were dead in the water after the install. A different software suite is on both systems, and there is no "intrusive" 3rd party software that should cause any trouble. Thanks to the instructions above I was able to get back on-line and running 10.4.9, but something really needs to be done about these issues.

Kernel updates kill my luks encrypted system

All right, this is weird. I have a 64bit system with encrypted root, home and swap partitions. To setup I followed the wiki here:
https://wiki.archlinux.org/index.php/LUKS
My swap is encrypted like described here:
https://wiki.archlinux.org/index.php/LU … sk_support
Since the updates to kernel 3.1 each new kernel update kills my system. Pacman says while upgrading
[2011-11-08 08:21] >>> Updating module dependencies. Please wait ...
[2011-11-08 08:21] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-11-08 08:21] ==> Building image from preset: 'default'
[2011-11-08 08:21] -> -k /boot/vmlinuz-linux_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img_64
[2011-11-08 08:21] ==> Starting build: 3.1.0-3-ARCH
[2011-11-08 08:21] -> Parsing hook: [base]
[2011-11-08 08:21] -> Parsing hook: [udev]
[2011-11-08 08:21] -> Parsing hook: [autodetect]
[2011-11-08 08:21] -> Parsing hook: [pata]
[2011-11-08 08:21] -> Parsing hook: [scsi]
[2011-11-08 08:21] -> Parsing hook: [sata]
[2011-11-08 08:21] -> Parsing hook: [usbinput]
[2011-11-08 08:21] -> Parsing hook: [keymap]
[2011-11-08 08:21] -> Parsing hook: [usb]
[2011-11-08 08:21] -> Parsing hook: [encrypt]
[2011-11-08 08:21] -> Parsing hook: [openswap]
[2011-11-08 08:21] -> Parsing hook: [resume]
[2011-11-08 08:21] -> Parsing hook: [filesystems]
[2011-11-08 08:21] ==> Creating gzip initcpio image: /boot/initramfs-linux.img_64
[2011-11-08 08:21] ==> Image generation successful
[2011-11-08 08:21] ==> Building image from preset: 'fallback'
[2011-11-08 08:21] -> -k /boot/vmlinuz-linux_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img_64 -S autodetect
[2011-11-08 08:21] ==> Starting build: 3.1.0-3-ARCH
[2011-11-08 08:21] -> Parsing hook: [base]
[2011-11-08 08:21] -> Parsing hook: [udev]
[2011-11-08 08:21] -> Parsing hook: [pata]
[2011-11-08 08:21] -> Parsing hook: [scsi]
[2011-11-08 08:21] -> Parsing hook: [sata]
[2011-11-08 08:21] -> Parsing hook: [usbinput]
[2011-11-08 08:21] -> Parsing hook: [keymap]
[2011-11-08 08:21] -> Parsing hook: [usb]
[2011-11-08 08:21] -> Parsing hook: [encrypt]
[2011-11-08 08:21] -> Parsing hook: [openswap]
[2011-11-08 08:21] -> Parsing hook: [resume]
[2011-11-08 08:21] -> Parsing hook: [filesystems]
[2011-11-08 08:21] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img_64
[2011-11-08 08:21] ==> Image generation successful
So the generation of the initramfs seems to be ok.
But when I reboot this box, I get:
running hook [openswap]
device /dev/sda4 doesn't exist or access denied
running hook [resume]
waiting 10 seconds for device /dev/mapper/swapDevice
waiting 10 seconds for device /dev/mapper/root
root device /dev/mapper/root doesn't exist. Attempting to create it.
ERROR: unable to determine major/minor number of root device /dev/mapper/root
/dev/sda4 is my swap partition. Then I get dropped to a recovery shell which I can't use because my (usb) keyboard is not working.
Now the funny part. I start the box from a install cd and chroot into the existing installation. I do a
mkinitcpio -p linux
The initramfs is regenerated and it works again! What the hell is pacman doing other than regenerate the initramfs with my presets?
Harvey
Last edited by Harey (2011-11-12 16:10:48)

New kernel 3.1.1 did it again. My system hangs in initramfs after the reboot. Same as before: a simple rebuild without any changes fixed the boot process. This time I was able to backup the 'bad' initramfs before chrooting in and rebuilding.
it is very funny to see the content of the 'bad' initramfs image - it is nearly empty!
==> Image: /boot/initramfs-linux.img_64.bak
==> Kernel: unknown
==> Compressed with: gzip
-> Compression ratio: .452
-> Estimated decompression time: 0.036s
==> Included binaries:
/sbin/dmsetup
/sbin/cryptsetup
/sbin/udevadm
/sbin/blkid
/sbin/modprobe
/bin/busybox
==> Hook run order:
udev
keymap
encrypt
openswap
resume
The rebuilt image looks like this:
==> Image: /boot/initramfs-linux.img_64
==> Kernel: 3.1.1-1-ARCH
==> Compressed with: gzip
-> Compression ratio: .593
-> Estimated decompression time: 0.047s
==> Included modules:
aes_generic fcrypt hid-roccat-kone rmd160
aesni-intel ff-memless hid-roccat-koneplus rmd256
aes-x86_64 gcm hid-roccat-kovaplus rmd320
af_alg gf128mul hid-roccat-pyra salsa20_generic
ahci ghash-clmulni-intel hid-samsung salsa20-x86_64
algif_hash ghash-generic hid-sjoy scsi_mod
algif_skcipher hid hid-sony sd_mod
ansi_cprng hid-a4tech hid-speedlink seed
anubis hid-apple hid-sunplus seqiv
arc4 hid-axff hid-tmff serpent
async_memcpy hid-belkin hid-topseed sha1_generic
async_pq hid-cherry hid-twinhan sha256_generic
async_raid6_recov hid-chicony hid-uclogic sha512_generic
async_tx hid-cypress hid-wacom snd
async_xor hid-dr hid-waltop snd-rawmidi
ata_piix hid-elecom hid-wiimote snd-seq-device
authenc hid-emsff hid-zpff soundcore
authencesn hid-ezkey hid-zydacron sr_mod
blowfish hid-gaff hifn_795x syscopyarea
camellia hid-gyration hmac sysfillrect
cast5 hid-holtekff jbd2 sysimgblt
cast6 hid-kensington khazad tcrypt
cbc hid-keytouch lcd tea
ccm hid-kye libahci tgr192
cdrom hid-lcpower libata twofish_common
crc16 hid-logitech lrw twofish_generic
crc32c hid-magicmouse lzo twofish-x86_64
crc32c-intel hid-microsoft mbcache uhci-hcd
cryptd hid-monterey md4 usbcore
crypto_null hid-multitouch md5 usbhid
ctr hid-ntrig michael_mic usb-storage
cts hid-ortek padlock-aes vmac
deflate hid-petalynx padlock-sha wp512
des_generic hid-picolcd pata_acpi xcbc
dm-crypt hid-pl pata_jmicron xor
dm-mod hid-prodikeys pcbc xts
ecb hid-quanta pcrypt zlib
ehci-hcd hid-roccat raid6_pq zlib_deflate
ext4 hid-roccat-arvo raid6test
fb_sys_fops hid-roccat-common rmd128
==> Included binaries:
/bin/busybox
/sbin/udevadm
/sbin/dmsetup
/sbin/blkid
/sbin/cryptsetup
/sbin/modprobe
==> Hook run order:
udev
keymap
encrypt
openswap
resume
For some reason the initramfs built by pacman is missing all modules. To say it again, nothing changed, simple rebuilt by mkinitcpio -p linux!
This seems to be a bad bug...
Harvey
Last edited by Harey (2011-11-12 16:07:09)

I have an iPhone 4S with Sprint, I had to replace my last phone after the newest update killed my wifi button. Now my new phone won't get 3G at all. I have tried turning my phone off/on, resetting my networks, and turning airplane mode off and on.

I have an iPhone 4S with sprint. I had to replace my phone after the new update killed my wifi button and wouldn't let me turn my phone off. Since I've had my new phone, I haven't been getting 3G. I have tried resetting my networks, Turing airplane mode off/on and restarting my phone. Nothing seems to work. Any info on what I should do next would be great.

If you have set this phone up, then there would not necessarily be a solution here until you have been verify with the provider that everything is provisioned correctly on their end. Since the 3G comes from your cellular provider, if the settings are correct on the phone, then you should work with the carrier next.

Flash updates kills sound

I have a Mac 10.6.8 which on the last Adobe Flash update killed my sound.
I know nothing of computers - it is a glorified typewriter to me, so please advise how to remedy this in simple terms.
Technical terms are the death for me!

Hi,
Could you please let us know some more details?
Please go to the following page and let us know the Flash Player version and browser you use: http://helpx.adobe.com/flash-player/kb/find-version-flash-player.html#main_Find_the_Flash_ Player_version_installed_on_your_machine
Do you mean to say you don't hear any sound at all?
Thanks,
Sunil

Student price for update to FCS 2?

I bought FCS 1 at full price 3 years ago— and at my university I used FCS 2 on a project, that I now can't work on at home because FCS 1 can't read the files. Anyhoo, I'm looking to update to FCS 2 and the price is steep, considering FCS 3 is surely around the corner.
Can I get a student discount on my update to FCS 2?!

As I understand your post, you have a full retail version of FCS 1, but want to upgrade and get a discount because you're a student. If that's the case, you'd be much better off purchasing the retail upgrade at $499.00 so you'll maintain your upgrade path in the future. If you purchase the academic version, you won't be able to upgrade later.
-DH
ps: Welcome to the forum!

Isit true to say that iPod Updater kills your iPod?

Hello all,
First, sorry for my poor English. I am not a professional nor a technician and I could be wrong, so please correct me. There are many problems reported mainly from the PC users that their iPod can't be recognized nor mounted after the installation of the latest iPod updater. Most of them claimed that the iPod updater kills their beloved iPods. Before we jump to a conclusion, we must understand what is iPod, and how does the iPod update work.
I believe that iPod equals a basic computer and need a OS in order to communicate with the PC. Installation the Updater will format the Hard disk of the iPod and then install the simple OS, so if we open the iPod updater file, it will show a window with two buttons i.e. Restore and Update, an Update is to copy the latest OS over the old version, but the Restore will format the hard disk before it install the OS over it. And importantly, during this process, the iPod needs sufficient of power to complete the upgrade, however, the problem comes just after the format, and the PC's USB (only 2 will work not 1.1) does not supply the stable power,even some cases that iPod does not get charge in the half way of installatin (a proper installation, you will see a running bar showing on the iPod screen just after the format), so you can imagine a hard disk got format but only got an uncompleted OS, of course, the iPod would not get recognized and mounted, and do not manage to communicate with the computer. At this stage the iPod will show a Sad iPod icon, a folder with exclamaiton points or a battery charging icon.
So, what would you do when it reach at this stage, a Reset would not work, and you would not able to do the Restore as the iPod is totally unrecognized by the computer.
Therefore, is there anyway to solve this problem, in my opinion and from my past experience, the answer is "yes", the simple way is to put your iPod in Disk Mode, when it plug to the computer, it will show as an external Hard Disk, you must fix it by doing a format (RESTORE would not work at this stage as it still can't recognized and mounted), in Mac we can use "Disk Utility" but the XP would not allow you to do the format in FAT32. After the formatting, replug the iPod with the computer, then it can be mounted and allow you to do the RESTORE.
In addition, I find an interesting point is, if your iPod formatted with a Mac, you will have better chance to be mounted with a PC, even your iPod does not complete the process of the installation of the iPod updater, and a PC formatted iPod will be likely to be fixed by a Mac as well.
How should we do before the update of the lastest software, for the XP user please do the following:-
1. Go to the system restore and create a check point in order to revert back to the previous version of the iPod updater, or do the back up using the 3rd party software such as Ghost or Go Back.
2. To have a test and make sure the PC's USB works properly. You can use the iPod or a PDA, and just make sure it got charged.
3. Have your iPod a full charge before the installation of the iPod updater
So, who is the main killer for the iPod?
For further infomation please read the following link - which wrote by a groups of great people - thank your guys
http://discussions.info.apple.com/webx?128@@.68ae8668

Yes, it will erase all your data with your iPod. Please do not format until you have the back up of your iPod. Very likely that your iPod was formatted by a Mac, which can't be read by your PC. Download a software called Xplay
http://www.mediafour.com/products/xplay/

Please help: 10.4.3 update KILLED iCal

After updating to 10.4.3 all my iCal data was gone. I restored it using Backup and when I launched iCal it all appeared as normal—and then a few seconds later, poof, it all disappeared again right before my eyes. I tried making a new entry and at first it didn't seem to work, then all my iCal data reappeared for a few seconds, only to disappear again a few seconds later, leaving iCal "virgin" as if no entry had ever been made. If I quit and reopen iCal, I can again briefly see the calendars before they disappear.
The current iCal version is 2.0.3. I have tried erasing preferences and starting over again to no avail, as well as logging in with the shift key down. I have also repaired the disk and the permissions with no improvement.
Any suggestions anyone? Is it possible to reinstall just iCal? I really really don't want to have to do a complete system reinstall because of this stupid bug.

I don't believe the 10.4.3 Update killed iCal and if a bug, it must be selective since I didn't experience the same and I haven't seen the same reported here in large numbers.
What is your hard drive capacity and available free space?

Acrobat X Update "killed" Acrobat 9

Our prepress department uses Acrobat 9 Pro with the Pitstop plug-in to process files. A co-worker working in Windows noticed that he had an update available -- for Acrobat X -- so he went ahead and let it update. (I'll note here that we are in the habit of having multiple versions available, so he assumed he could still use the Acrobat 9 workhorse as needed.)
He's not happy with X's user interface (and his Pitstop plug-in lives in version 9), so he tried opening files back in version 9. Now suddenly he finds that he cannot run Acrobat 9 at all. Even if he selects it directly. PDFs now open exclusively in version X.
Is there an "uninstaller" for Acrobat X, and if he runs it, will it break anything else? Will he have to reinstall Acrobat 9 and Pitstop?

I zip back and forth between versions, so it can be done with a bit of patience and luck. What you have to give up the idea of is that double-click-to-open is any use to you any more. You need to use File > Open or similar.
Try
1. Reboot
2. Use task manager to make sure no Acrobat.exe is running
3. Try starting Acrobat 9.
4. Still starts X? Kill it, repeat step 2, and navigate to the acrobat.exe file for v9 and run that.
5. Still starts X? Right click, properties, check version. Maybe someone/something actually overwrote the app.
But always remember once you have it working that it is "unsupported" and what that really means. (It is NOT a statement that it never works.)

Did Quicktime 7.5.5 update kill my iChat video client?

Yesterday I upgraded my Quicktime to the latest and greatest via Software Update.... and now the video portion of my iChat client appears to be broken. It was working great before the update, but now it will freeze video, audio might continue and then when I end the chat it will crash.
I read some posts on the site about setting the preferences to 500 bps for video in iChat and 1.5 Mbs on the Quicktime Streaming preferences. This worked initially, but now I'm back to crashing.
Has anyone else had this problem? If so, how did you fix it?
Thanks,
Rich

I have tried the solution posted here, as well as one that I found in another board on this forum (Reinstalling Quicktime from the stand alone installer).
My situation: The video froze, the audio would work for 15 seconds or so afterwards, then ichat would hang and eventually have to be force killed.
I tried:
repairing permissions
reinstalling quicktime
getting the person I was ichatting with to update quicktime (this just caused it to crash on their end as well as my end)
The console output from the crash is:
15/09/08 7:04:13 PM [0x0-0xaa0aa].com.apple.iChat[1719] Tue Sep 16 02:04:13 mabel QTH264_SHMServer6b73d36fdd9[1723] <Error>: kCGErrorRangeCheck : On-demand launch of the Window Server is allowed for root user only.
15/09/08 7:04:13 PM [0x0-0xaa0aa].com.apple.iChat[1719] Tue Sep 16 02:04:13 mabel QTH264_SHMServer6b73d36fdd9[1723] <Error>: kCGErrorRangeCheck : Set a breakpoint at CGErrorBreakpoint() to catch errors as they are returned
some googling of these functions brought up people talking about Quicktime APIs, so I can only assume this is still a quicktime issue. If anyone has actually solved this I'd love to know, thanks.

9.2 Update killed my audio input monitoring during play!

I can monitor my audio input while I'm stopped, but as soon as I loop and play (not in record mode) it automatically kills monitoring of the signal. YET, I can still record if I need.
This didn't happen until I updated to 9.2.
Has anyone else had this problem?
Thanks!

I got other problems after updating Logic, they occured twice. One was not having 'open recent session' and the other was not having 'incompatible' plugins menu item in Logic AUs. Perhaps this is similar to my problem and the solution was to trash Logic preserences and rebooting. Try it, you don't loose anything that way. I'm not at my mac now but the preferences can be in MacHD/library/Preferences (start with com.apple.logic) or in your user Library/preferences. There are 2 files and I'm not sure which one but if you trash both (without deleting the files, only trash) you can try if it brings the requested feature back. One of the files will reset your settings but if you restore it after the test you will have them back (of course with the 'bug' itself. Later today I will pot you the exact one to throw.
Message was edited by: samplaire

OS 10.4.9 Combined Update Killing Internet Connection

Hey All,
So here is my situation - last night I ran TechTools as my ibook has been acting somewhat erratically as of late (shutting down completely without warning when the battery gets to about 1/4 strength). Techtools found errors and I asked for them to repair it...and it wiped my drive clean.
So, I erased and restored using the provided discs. Once this was done, I was able to connect to my wireless network no problem. I ran the software update which of course found a number of downloads. After completing most of them, my internet connection was suddenly lost. I noticed that this happened while the 10.4.9 Combined update was being installed, and it was marked as not being completed.
Network Diagnostics shows that I was able to connect to my Airport, but could no longer reach my ISP. I tried to connect via ethernet directly to my cable modem, and could still not connect.
I decided to erase and reinstall again, and the same thing happened. My internet connection was fine until the OS 10.4.9 combined update started to download. This is killing me...help?

Thanks for the advice - I do have a strong suspicion that the logic board needs to be replaced based on the other behavior that brought me to use TechTools which caused this whole mess to begin with, however AHT showed that everything passed. I do find it quite strange that it works fine until it starts to download the 10.4.9 combined update though.
I will download the combined update and burn it to a disc and try to run it on the machine tonight and see if that makes any difference. Has anyone else experienced anything like this?

10.4.7 Update killed my firewire ports

Hello -
All was going quite well this morning, but then I upgrade my machine to 10.4.7 which killed my firewire port.
All I get in System Profiler is:
"FireWire Bus:"
No bus info is displayed. It was working this morning before I did the update.
I already zapped my pram, reinstalled the firmware required to run my GigiDesigns card, rebuilt permissions, cleaned out every cache possible with "Main Menu".
Any thoughts? tips? Tricks?
Thanks - Dustin
G4 Quicksilver, 1.8 GHz Giga Designs Mac OS X (10.4.7)

What is the status of the computer's built-in Firewire ports? If they are OK, then your PCI card may not be compatible with 10.4.7. If that's the case check with the manufacturer's website support.
When you installed the update did you use the Combo Updater or the Delta Updater (via Software Update?) If you did not use the Combo Updater, then download it and re-install the update. Before doing so do the following:
Boot from your Tiger DVD. After the installer loads select your language and click on the Continue button. Then select Disk Utility from the Utilities menu. After DU loads select your OS X volume from the list on the left, click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now shutdown the computer for a couple of minutes and then restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (3.0.3 for Tiger) and/or TechTool Pro (4.1.1 for Tiger) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

10.5.3 update killed my 24" E248WFP monitor

Well, not exactly killed, just rendered my external monitor unusable. If I try to connect it via the mini-DVI connector my macbook screen just keeps flickering like it's trying to detect a monitor but can't anymore. With 10.5 and 10.5.1 I had no issues with this monitor. As soon as 10.5.2 went on, I began having to reset my PRAM and do a cold boot with the monitor connected in order for it to display properly. Now after the 10.5.3 update the monitor no longer is detected no matter what I do leaving a rather large paperweight stuck in the middle of my desk. I reformatted and reinstalled back to 10.5 and the monitor works perfectly again. I updated to 10.5.1 and it too worked. And as soon as I went back to 10.5.2 it began experiencing the same problems.
I contacted applecare phone support but after an hour they concluded they could not help me "but that they would continue working on the issue". Hmm...I'm a little skeptical about that one.

For now and until Apple fixes the bug, the only solution I have found is to turn the proxy off in the Network settings. If you need to use a proxy server for work/school, you are best off with using Firefox. Firefox has a number of add-ons that allow you to turn the proxy on and off (for instance Switchproxy, which is very useful and allows you to turn the proxy on only selectively). (https://addons.mozilla.org/en-US/firefox/search?q=proxy&cat=all)

10.4 to 10.5 update killed FCS?

Similar Messages

Maybe you are looking for