Ducth postscript error preventing leopard install

I have a powerbook G4 17" with a brand new hard drive. I have attempted an install of Leopard. The installation progressed completely through the process and at the end of roughly an hour and 15 minutes I recieved an error that said roughly +dutch postscript installation error continue to re-install+.
Anyone have suggestions? I am stuck.
Thank you

where can i get migration assistant? will carbon copy not do? my situation is worse now. i don't know why i forgot to go with archive and install and chose upgrade. life is **** for my g4 now. the new situation is that if i choose archive and install or the clean install option, there is an error message at the end saying the install failed and that there is an error with the disc. I have also seen an error message saying the install failed due to not finding the oxford dictionary something. on top of that, i can't reboot into OS9 because leopord alters or deletes an important extension that the sonnettech processor needs. they sent me the new file and once i overcome these failed install issues i can add that new file. oh well. wonder how vista installs are going?

Similar Messages

XCode Error on Leopard Install

I'm getting this error on trying to install XCode 3.2.6 on Leopard:
XCode installer encountered an error that caused the installation to fail. contact the software manage
Any ideas?

Before installing, be sure to quit all of the following:
iTunes
Xcode
Interface Builder
Application Loader
...still no joy, run Activity Monitor, then find and quit 'iTunes Helper'.

Javascript error preventing software install

I'm a Pro Tools user and I'm getting a Javascript error when I attempt to install an update for an AVID/Digidesign virtual instrument plugin called Transfuser. I downloaded the software directly to my Mac Pro got the error so I ran software updater and it brought the machine right up to date including Java but I'm still getting this:
"There was an error while evaluating Javascript for the package"
So AVID support asked me if I updated Javascript but I can't find a proper download link for it. I did an internet search for this error and found that it's quite common but nothing that helps me directly. I understand that Java and Javascript are not the same thing but AVID support mentioned that updating Java on my Mac would probably update both....though this is not clear. How can I fix this issue? I've never encountered it before and could use some help. You can see the DUC support thread I've got going here: http://duc.digidesign.com/showthread.php?t=278422
I tried an experiment: Booting into my cloned drive and installing and it worked. But still no way to install from there onto another volume....and I can't use Time machine because I've had it turned off since I've been using Carbon Copy Cloner. Time Machine has known issues with Pro Tools.
Seems to me it has something to do with the HD??? Any help on the matter would be most welcome.

I don't see why you can't restore.
Ideal is to do a walk-thru and test what a restore is and does and such - when you have time and things are working.
When I restore, I format and then restore. Or you can erase.
with enough drives, there is almost no need unless there may be structural errors, or you want to move the system to a new larger or faster drive.
HELP menu in programs like Disk Utility plus it is quite easy
I am not audio or protools, more system maintenance type, and I have no idea why or what is different. But I do know that if I have a system that works, I would make a copy (clone) of it and keep it safe (and off line).
Having spare drives handy is a must, along with SuperDuper and Disk Warrior.
Clone with SuperDuper doesn't copy temp files, log and caches, which is great, those can be problematic and just take up space, and are best recreated fresh.
I would never say a drive is working 100% okay without also using Disk Warrior, maybe even TechTool Pro 5.
Just DO NOT rely on only Apple First Aid to tell you or keep a drive in tip top shape and working order - it doesn't and won't.
A newly formatted drive insures a number of things. You can also write zeros over the drive. A drive used by 10.6.3+ really should be formatted by Snow Leopard, especially system drives. Yes you can just install over Leopard and update, but it really isn't the same.
I buy a lot of drives, but I trust all 4 systems I have to WD VelociRaptors for the most part, built like SCSI drives use to with good low seeks and latency, and run cold but fast.
Also nice to have 4 systems so one can be used for testing or something or a job that takes a lot of time and leave me free.
I'd take your problem system, use SuperDuper (free for full clone, inexpensive $29 for "Smart Update" feature) and clone it to a newly initialized drive; plus run Disk Warrior 4.2 against it first. Then run from that.
I've had three WD drives out of 30 fail, all WD Caviar, two were "Black" series, one was repaired and works fine now thanks to WD's Windows utility. But I won't use Caviar drives except for storage and triple backups now.
I was worried that going back and forth with different versions of AVID apps might handle data files differently, like how Microsoft changes Excel/Word .docx files.
About CCC and other issues:
http://macperformanceguide.com
How to clone with CCC
http://macperformanceguide.com/Mac-HowToClone.html
Even for non-RAID (but definitely for use with RAID) nothing beats SoftRAID for reliable and easy to setup partitions.
http://macperformanceguide.com/Mac-DiglloydHardware.html
http://macperformanceguide.com/Storage-SoftRAID.html

Trying to install an upgrade but Error 7 is preventing the install from going thru. I am logged on as Administrator running windows 8.1 on my pc. Help

Trying to install an upgrade of iTunes on my pc but Error 7 (Windows 193) is preventing the install from going thru. I am logged on as Administrator running windows 8.1 on my pc. I have repaired and uninstalled a couple times These are my warnings
"Service 'Apple Mobile Device Service' ('Apples Mobile Device Service) failed to start. Verify that you have sufficient privilege to start system services." [Abort Retry Ignore ]. "ItunesHelper was not installed correctly "

If the above steps haven't helped try installing:
iTunes 12.1.0.71 for Windows (64-bit - for older video cards) - itunes64setup.exe (2015-01-28)
which is a 64-bit installer for a 32-bit core program, similar to previous 64-bit releases of iTunes, or roll back to:
iTunes 12.0.1.26 for Windows (32-bit) - iTunesSetup.exe (2014-10-16)
iTunes 12.0.1.26 for Windows (64-bit) - iTunes64Setup.exe (2014-10-16)
as appropriate.
tt2

Disk Full Error after Clean Leopard Install-MacPro

Reformatted drive into 2 partitions, Leopard Install, update to 10.5.7.
After Reboot disk full error-plenty of space available.

Well, we can't help without more information than that to go on...

Diagnostics error message after installing Leopard

Hi
I have just upgraded to Leopard from Panther and every time the computer starts up I get a message saying "Error - Could not load login file". Diagnostics tries to open and than crashes. I have tried opening Diagnostics directly and I get the same message. Any suggestions?
Also, some applications keep asking me if I want to allow incoming connections on the Firewall even though they are already checked. Something called pipedaemon has also appeared in the Firewall list and as I have no idea what this is I have blocked it. Is that okay?
Thanks
Ian

Retain a bootable backup/clone of your Panther boot volume? If so, boot into it and ensure it works normally; then, boot with the Leopard install disk, erase the corrupt installation, do an Erase & Install, and use the setup assistant to migrate from the good Panther volume. If not, all I can suggest is an Archive & Install installation.

Time Machine gives "error code -43" after leopard install

Hi folks,
This leopard install has been a mess. I have a one year old macbook on which I've done nothing unusual, and I ran the leopard install. Now I try to use leopard and I find that the one feature I bought it for, Time Machine, does not work. I clickon the icon either on the dock or in the application folder and I get "error code -43". I cannot launch Time Machine. Can anyone help? It is very frustrating to have to consider spending extra money for mac tech support when I haven't done anything out of the ordinary, I'm just installing their product on a recent laptop.
In addition, this leopard hogs 11 GB of hard drive space and has slowed my computer by at least 50%. Boy do I regret this upgrade, but I don't see any way to go back.

have the same problem on my imac g4 have not tried it on the macbook pro yet, tried backing up to a La Cie hard drive have another thread going with problems related to this which started when I first initiated time machine wonder if the 2 problems are related

Console Messages:Color profile errors after fresh install of Snow Leopard

This is a dump of the Console Messages for my Macbook Pro immediately after a fresh install.
Are all the Color profile errormessages normal?
24/12/2010 16:06:02 com.apple.launchd[1] * launchd[1] has started up. *
24/12/2010 16:06:17 com.apple.launchd[1] (com.apple.bsd.dirhelper) Throttling respawn: Will start in 6 seconds
24/12/2010 16:06:18 com.apple.launchd[1] (com.apple.smb.sharepoints[24]) Exited with exit code: 71
24/12/2010 16:06:20 com.apple.launchd[1] (com.apple.bsd.dirhelper) Throttling respawn: Will start in 3 seconds
24/12/2010 16:06:35 com.apple.service_helper[90] launchctl: Error unloading: com.apple.backupd-auto
24/12/2010 16:06:35 com.apple.service_helper[90] launchctl: Error unloading: com.apple.backupd-wake
24/12/2010 16:06:35 com.apple.service_helper[90] launchctl: Error unloading: com.apple.backupd-attach
24/12/2010 16:06:37 com.apple.fontd[82] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
24/12/2010 16:06:38 com.apple.fontd[82] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
24/12/2010 16:08:52 com.apple.coreservicesd[49] ThrottleProcessIO: throttling disk i/o
24/12/2010 16:18:07 com.apple.service_helper[150] org.ntp.ntpd: Already loaded
24/12/2010 16:21:43 com.apple.coreservicesd[49] ThrottleProcessIO: throttling disk i/o
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorIllegalArgument: CGSGetDisplayBounds (display 0)
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Warning>: CGSLookupServerPort: _CGSSessionDeathWatchPort(gSessionPort) returns 268435459
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Error>: (ipc/send) invalid destination port: CGSGetNextEventRecord (Inline) connection 0x7b07, 16384 bytes
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Warning>: CGSShutdownServerConnections: Detaching application from window server
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Warning>: CGSDisplayServerShutdown: Detaching display subsystem from window server
24/12/2010 16:24:34 [0x0-0x8008].com.apple.IncompatibleAppDisplay[203] Fri Dec 24 16:24:34 Jeremy-Gordon-Flowerss-MacBook-Pro.local IncompatibleAppDisplay[203] <Warning>: 3891612: (connectAndCheck) Untrusted apps are not allowed to connect to or launch Window Server before login.
24/12/2010 16:24:36 com.apple.launchd.peruser.501[215] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
24/12/2010 16:24:36 migCacheCleanup[221] Flushing Cache Locations...
24/12/2010 16:24:36 com.apple.loginwindow[205] 2010-12-24 16:24:36.819 migCacheCleanup[221:903] Flushing Cache Locations...
24/12/2010 16:24:38 SoftwareUpdateCheck[229] Checking for updates
24/12/2010 16:24:40 com.apple.fontd[228] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
24/12/2010 16:24:42 com.apple.launchd.peruser.501[215] (com.apple.Kerberos.renew.plist[247]) Exited with exit code: 1
24/12/2010 16:24:43 com.apple.fontd[228] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
24/12/2010 16:26:53 SoftwareUpdateCheck[229] PackageKit: Missing bundle path, skipping: <bundle id="com.apple.NetworkUtility"></bundle>
24/12/2010 16:26:53 SoftwareUpdateCheck[229] PackageKit: Missing bundle path, skipping: <bundle id="com.apple.Terminal"></bundle>
24/12/2010 16:26:53 SoftwareUpdateCheck[229] PackageKit: Missing bundle path, skipping: <bundle id="com.apple.DiskUtility"></bundle>
24/12/2010 16:26:53 SoftwareUpdateCheck[229] PackageKit: Missing bundle path, skipping: <bundle id="com.apple.SystemProfiler"></bundle>
24/12/2010 16:26:53 SoftwareUpdateCheck[229] PackageKit: Missing bundle path, skipping: <bundle id="com.apple.RAIDUtility"></bundle>
24/12/2010 16:26:55 Software Update[269] PackageKit: Missing bundle path, skipping: <bundle id="com.apple.NetworkUtility"></bundle>
24/12/2010 16:26:55 Software Update[269] PackageKit: Missing bundle path, skipping: <bundle id="com.apple.Terminal"></bundle>
24/12/2010 16:26:55 Software Update[269] PackageKit: Missing bundle path, skipping: <bundle id="com.apple.DiskUtility"></bundle>
24/12/2010 16:26:55 Software Update[269] PackageKit: Missing bundle path, skipping: <bundle id="com.apple.SystemProfiler"></bundle>
24/12/2010 16:26:55 Software Update[269] PackageKit: Missing bundle path, skipping: <bundle id="com.apple.RAIDUtility"></bundle>
24/12/2010 16:28:14 SoftwareUpdateCheck[229] Downloading "iTunes"
24/12/2010 16:28:47 SoftwareUpdateCheck[229] Background check cancelled by user-initiated update.
24/12/2010 16:28:47 SoftwareUpdateCheck[229] Auto-download of "iTunes" SUCCESSFUL.
24/12/2010 16:28:47 com.apple.launchd.peruser.501[215] ([0x0-0xd00d].SoftwareUpdateCheck[229]) Exited with exit code: 102
24/12/2010 16:50:06 com.apple.WebKit.PluginAgent[344] Debugger() was called!
24/12/2010 16:50:06 com.apple.WindowServer[84] Fri Dec 24 16:50:06 Jeremy-Gordon-Flowerss-MacBook-Pro.local WindowServer[84] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
24/12/2010 16:50:39 com.apple.WebKit.PluginAgent[344] Debugger() was called!
24/12/2010 16:51:45 com.apple.WebKit.PluginAgent[344] Debugger() was called!
24/12/2010 16:52:17 com.apple.WebKit.PluginAgent[344] Debugger() was called!
24/12/2010 16:52:53 com.apple.WebKit.PluginAgent[344] Debugger() was called!
24/12/2010 16:53:25 com.apple.WebKit.PluginAgent[344] Debugger() was called!
24/12/2010 16:55:44 com.apple.WebKit.PluginAgent[344] Debugger() was called!
24/12/2010 16:56:39 com.apple.WebKit.PluginAgent[344] Debugger() was called!
24/12/2010 16:57:05 com.apple.WebKit.PluginAgent[344] Debugger() was called!
24/12/2010 17:00:45 com.apple.WebKit.PluginAgent[344] Debugger() was called!
Message was edited by: gr8fanboy - fixed os version was 10.6 at this point

try this idea: Do a leopard install to an external disk then do a Disk Utility "restore" function to that clean partition. So you restore from the external to the internal partition. Should leave Bootcamp untouched.

Successful Leopard Install after GUID partition error on Intel iMac

Firstly the hardware:
- Intel iMac 20" (Early 2006) with 750GB HD
- 1 X Iomega MiniMax External HD (750GB)
- 2 X Iomega MiniMax External HD (250GB)
This is what I did:
1) Moved files between external drives (8 hours) and repartitioned all 3 with GUID option.
2) Installed Leopard on one of the external drives (1 hour) and firewire startup to check the machine runs ok on Leopard and confirm access to all other drives, apply all software updates.
3) Back to Tiger on my internal drive and Carbon Copy Cloner to the 750GB external drive (3 hours to copy 300GB). 6 hours to zero out the external drive before the clone. Test startup between the 2 clones.
4) Use Leopard DVD to startup and erase/partition internal drive with GUID option (very scary, but worked fine).
5) Install Leopard on the internal drive (1 hour).
6) Transfer files, settings etc. from the clone during the Leopard install (3 hours). Install all updates.
So far, so good. All applications worked fine including iLife, Photoshop CS3, Aperture, Office 2004 etc. I will keep the Tiger clone for a couple of weeks then delete. Let's hope the next upgrade is not so difficult.
Hope this helps.

Libraries have computers everywhere. I would recommend getting acquainted with your nearest one. If they don't have computers, hours, times, write your local politicians demanding better computers, and hours if there aren't enough. You could have subscribed to Apple Discussions at the library, and learned as much as you needed. The info is out there. http://www.everymac.com/ is another place, so is http://www.apple-history.com/ and many sites you'll find via http://www.macsurfer.com/
Tiger isn't so much outdated, as no longer sold by Apple. Plenty of people still use Tiger, and even Panther, and believe it or not, even Mac OS 9. See this board:
http://discussions.apple.com/category.jspa?categoryID=177
and
http://discussions.apple.com/category.jspa?categoryID=99
So it is not like there aren't people using it. It just becomes harder to find some things, but never would I say impossible.

Family Pack Leopard install fails G4 Dual 1.2Ghz

All, I purchased the Leopard family pack and have successfully installed it on an Intel Macbook Pro and a G5 2.3Ghz DP machine - flawless, no problems during installation or after.
However, any attempt to install on a G4 Dual 1.2Ghz + 2Gb of RAM + just bought a Seagate 500Gb Barracuda internal drive (well within the designated technical requirements), I've tried the following.
1. Booting the G4 off the Leopard install DVD, I get the following error: Failed Install message = "The Installer could not validate the contents of the Essentials Package...".
I can never get beyond this point. After receiving this error, the internal disk isn't even recognized on the bus - I have to pull the disk out, put it in an external case to reformat it. I've even tried a low level format and also had Seagate replace the disk thinking it was defective.
2. I then thought it may be an issue with putting the Seagate disk in cable select mode versus master / slave configuration. The Seagate is the only hard drive in the machine. I have tried both cable select and master/slave configuration - both freeze after install, etc. without fail.
3. Tried installing Leopard on the G4 by connecting it to the G5 in target disk mode. It installed, but routinely just freezes (NEVER had this issue with Tiger on this machine).
I do see lots of people posting issues with the "The Installer could not validate the contents of the Essentials Package..." error.
For the record, after successful Leopard install using technique #1 and #3 - I am also unable to run the Migration assistant - it fails every time with a kernel panic. I'm not having any trouble with the Leopard install media on any of the other 2 machines, nor did I have issues running the migration assistant.
Any ideas are appreciated. thx,

themdg - you said you put back your 2-512 original RAM cards and tried to install Leopard and the install failed. But my original, factory-installed RAM was third-party RAM which prevented me from installing Leopard, giving the “essentials” error. Only when I purchased RAM from Apple, and used only that RAM to install, could I get it to work correctly.
Check your original RAM. If it is not the Apple brand, it may not work because of that, even if it was the factory-installed RAM.
After I installed Leopard with only the Apple RAM, I added back the third-party RAM and I’ve been running Leopard flawlessly since.
It seems the installation software, which meticulously checks the installer disk for flaws, should also check the RAM to see if the installation will be successful (i.e., check to see if it is going to produce the “essentials” error) and also check to see if you have enough valid RAM to install, before it begins installation, and to let the user know there will be a problem unless the RAM is changed to valid cards.
I “assumed” I had enough valid RAM when I first tried to install Leopard because I had a G5, but it had only 256 MB of non-Apple brand RAM (minimum of 512 is required). A direct check of that by the installer and letting me know it was a problem would have saved me a lot of trouble checking lots of other potential problems, like a bad installer disk, a third-party drive, etc., before I figured out it was insufficient and incompatible RAM for the installation.
I read the minimal requirements for installation of Leopard and probably someone will say I should have checked all those before I tried the installation, but I didn’t, as I’m sure many others have not, because we “assume” Apple had tested it and would prevent us from making any mistake like this.
Previously Apple made their software and hardware to “just work” by providing error messages before we made an error and we have come to rely on that. But they overlooked this problem on this update. It’s the first time I’ve had a problem with an update from Apple.
I’m still a loyal Apple user, but I’ll check requirements a little closer with future updates.

Postscript Errors with Toshiba eStudio 2500c

Greetings,
We had some problems printing to the Toshiba eStudio 2500c in our office after upgrading to Snow Leopard. I have read the threads about that and I do have their "latest" (3/09) drivers installed and the permissions set correctly. Adding the printer works, added as LPD by IP address and it finds the correct driver. Print jobs are sent successfully to the printer with no errors returned to the user.
Some things print just fine. Recent successes were printing a PDF and an Excel file. However, some things like printing from FileMaker or Firefox cause the printer to spit out a Postscript Error page instead of the document I tried to print. Here's what the page looks like:
ERROR : limitcheck
OFFENDING COMMAND : -- nostringval --
STACK :
/TSBPrivate
setpagedevice
(DSSC PRINT USERLOGIN=Dave)
/TSBPrivate
{pop dscInfo /For known {« /TSBPrivate 100 string dup a (
DSSC PRINT USERLOGIN=)putinterval dup 21 dscInfo /For get put interval »
setpagedevice }if dscInfo /Tit1e known {«/ITSBPrivate 100 string dup a
(DSSC JOB NAME=)putinterval dup 14 dscInfo /Title get put interval »
setpagedevice /if « /TSBPrivate (DSSC PRINT PRINTMODE=NORMAL)»
setpagedevice }
where
/dscInfo
-mark-
The best information I could gather still indicates that Toshiba has not released drivers for this model line that support Snow Leopard. However, a friend of mine had a fix for this (I think) and I can't remember what it was, nor can I reach him. So I'm wondering if anyone here has any suggestions or fixes for this problem.
Using the Generic Postscript Driver does work, but it's too limiting because we can't choose what tray to print from, etc. Thanks!
-Dave

Hello,
I have basically the same issue as you do, although my setup is different. We have a Toshiba eStudio 452, and I am running OS 10.5.8.
I also found the most recent drivers and installed them onto my iMac. The problem occurs also from my PowerBook G4, using these same drivers (10.5.7).
As Kreetoo said below, it's true that using the generic postscript drivers work but many printer features are gone.
A workaround that I've found is to select "Open PDF in Preview" in the print dialog, which then opens Preview up. Then, using this PDF, you go to File > Print, and print again, and it works. I don't know what changes when you do this, but somehow it doesn't print the error message kreetoo quoted below if you do this.
It's very tedious, however, to preview everything you want to print, but it's the only way around it that I've found.
http://data.versiontracker.com/drivers/manualExtract/Toshiba/ga1190-user-english -v101_ext/extract/ReadMe.txt details a solution for MS Office users on Windows computers, but I couldn't find a Mac-equivalent setting in Mac OS X 10.5 or 10.6.
This fault is possibly Toshiba's rather than Apple's although both should get together and get it fixed ASAP.

Error message when installing Flash Player : List of actions not found

I get an error message when trying to install Flash Player.
I use Windows 64 bit with Internet Explorer 64x.
I'm able to download, the installation starts but it stops before completing.
I get this error message (loosely transalated) :
Installation encountered errors
List of actions not found
How can I fix this ?
Thank you
Annie

I solved my problem by installing the Flash Player from home.
The network security at work prevented me from completing installation.
Thanks for your help.
Annie
2012/9/26 Pat Willener <[email protected]>
Re: Error message when installing Flash Player : List of actions not
found created by Pat Willener <http://forums.adobe.com/people/pwillener>in
Installing Flash Player - View the full discussion<http://forums.adobe.com/message/4728064#4728064

Creating a backup before Leopard install

Is it possible to back up my entire 80gb imac startup drive to one of my firewire drives with assurance that I can go back to that system if my Leopard install goes haywire? My first attempt to install Leopard failed with some un-useful error message and I was concerned that I might have gotten too far to go back. It seems to have rebooted fine back to 10.4.10, but my other startup drive is 10.2.8 and I'd hate to have to startup from that

Make a bootable clone backup on the FW drive. I use LaCie Silverkeeper 1.1.4.
Most important! Test the bootable clone. Restart your computer with the Option key pressed and your external drive should appear as one of the bootable options. Select its icon and click on it. Only after you boot up and see that the clone is indeed a clone, do you really know that you are safe from any kind of installation problem.
I would also strongly suggest removing the external drive connectio from your computer before installing Leopard to be absolutely sure nothing can happen to it.

Installing Mountain Lion from Snow Leopard, Install failed and HD write-locked

I recently downloaded the mountain lion installer from the App Store and I ran the installer. Stupid person as I am, I did not have any backups for my file and I naively assumed that an apple OS installer would be without flaws. Boy, was I wrong. I need every bytes of my data (or close to every bytes) but the installer failed.
Mid installation, the installer stopped and said that the installation failed and that I need to repair my disk. So I restarted the computer and I ran disk utilities (my start up disk was the OS installer and the installer allows me to run several programs, including terminal, disk utilities, and by the way, when I held option while starting up to see which start up disks I have, I only had the OS installer as the start up disk. Also, the installer allows me to run a program called "Startup Disk" when I click on the apple logo on the top left corner, but it doesn't allow me to startup my computer using Macintosh HD) and noticed that when I highlighted Macintosh HD, my "Repair Disk" button was grayed out. So first things first, I ran the "Verify Disk" button but after a minute or so, Disk Utilities said that verification failed and that Macintosh HD needs to be repaired. But the "repair disk" button is grayed out! So I went to the Mountain Lion installer again and ran it. Of course, it failed again so I restarted the computer.
So I tried to first back up all files in Macintosh HD to an external hard drive using Disk Utilities, and I used features such as "New Image" and "Restore" but they both ended up in "Input/Output error". I tried many methods with Disk Utilities but they resulted in errors.
After some research, I noticed that some people's computers worked after they reset their PRAM. So that's what I did. I held command+option+P+R when computer started up and I reset the PRAM. When the start up disk (which is the OS installer, not the normal operating system) loaded, I was greeted with choose languages option and then I was back in the Mountain Lion installer state. I again ran the installer again, hoping something would be different, but then it was different. But not in a good way. When I was told to choose where I would like to install Mountain Lion, I noticed that Macintosh HD was grayed out. Last time, I was at least able to run the installer but this time, Macintosh HD was grayed out. The installer said that my Macintosh HD was locked. After some research, I learned that apparently, the Mountain Lion installer write-locks Macintosh HD mid installation.
So now I am stuck and I am thinking of two things (plus some questions)
1. I am wondering if there is a way to unlock Macintosh HD. But even if I can unlock Macintosh HD, there is no guarantee that the installer will successfully install Mountain Lion, am I right?
a. so how can I un-write-lock Macintosh HD?
2. More realistically, I am thinking of borrowing someone else's macintosh computer and use it as the backup center. I have a firewire cable and a terrabyte external hard drive. So what I'm thinking is that I'll hook my computer in target mode to my friend's computer and I will also plug in my external hard drive to my friend's computer and then I can download and run Carbon Copy Cloner from my friend's computer to copy all data from my Macintosh HD to my external hard drive. And then I will erase my Macintosh HD, freshly install Mountain Lion onto it and then copy all data back from my external hard drive. But I am not sure about few things.
a. it looks like my Macintosh HD is write-locked. Can I still use Carbon Copy Cloner to copy all data from Macintosh HD (in target mode) to my external hard drive?
b. will my computer allow me to erase (or format) Macintosh HD?
c. will my erased/formatted Macintosh HD able to install + be installed Mountain Lion OS?
If you are here, then you have read my long long problem. Thank you very much and I would really really really appreciate your answers and opinions. Thanks

I'm not sure where you read that about the disk being "write-locked." That doesn't make much sense, given that the major task an installer like this must achieve is writing a whole bunch of files to the hard drive. I think your source was mistaken.
As to what happened, it sounds like your hard drive was badly corrupt to start with, or possibly was on the edge of failing and is now in the process of dying entirely. If you don't have backups of your data, that does not bode well for you, unfortunately. If you can manage to use target mode to copy your data, do that.
Once you're sure you've got all your data, you need to start up from your Snow Leopard install disk and repair the hard drive. (Since it sounds like the Mountain Lion installer didn't work, I wouldn't trust the recovery partition that Mountain Lion installs.) Or, even better, just erase the hard drive entirely and reinstall Snow Leopard. Then, once you're back up and running, with all your data back on the system and with Snow Leopard updated to the most recent version, try installing Mountain Lion again. If any of that fails again, the problem is likely to be a dying hard drive, and you'll need to replace it.

My Leopard install DVD is getting caught in a loop

I'm having a problem with my Leopard install DVD. I'm running Leopard 10.5.7, and I wanted to use Disk Utility, so I inserted the intall DVD, double clicked the icon, and pressed enter to restart using the disk.
What happened next was the computer restarted, gave me the chime, went to a gray screen with no apple logo or spinning gear, then restarted and looped this same sequence repeatedly. I've checked the surface of the install DVD and it seems undamaged, so my only conclusion is that something software related is happening. Anyone else run into this?
The install DVD is version 10.5.1.

Okay, so I used Disk Utility on the internal drive to verify and then repair permissions (long list). Then I attempted to verify the disk and got a message saying Disk First Aid Failed and the following info in the history: Verifying volume “Macintosh HD”
Performing live verification.
Checking Journaled HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
Invalid volume file count
(It should be 956726 instead of 956732)
Invalid volume directory count
(It should be 233009 instead of 233003)
The volume Macintosh HD needs to be repaired.
Error: Filesystem verify or repair failed.
After that, I put the install disk in and restarted holding the shift key. Got the gray screen for a long time (DVD seemed to be doing something), and then the computer restarted. This time I held down the option key, got the Startup Manager and selected the install disk. And away we went with the gray screen loop again. I let it try to restart from the install disk 6 times before holding down the eject button and ejecting the install disk which allowed the 'puter to boot from from the internal drive.
And that's where I stand.

Ducth postscript error preventing leopard install

Similar Messages

Maybe you are looking for