Update: from Product Development
Update: from Product Development
There was a 10.4 Java update last night as well, so I'd expect similar problems there.
Some inititial investigation seems to indicate the following:
The Java update seems to prohibit use of aliases to the OS JavaApplicationStub file. This technique is used by Workshop 4.0.2.4 and lower.
Workarounds:
1) Don't update Java.
2) If you've already updated Java, you can modify your Workshop to use the actual JavaApplicationStub, not an alias:
On your Mac, find the Workshop icon (Applications\Kodak\Prinergy\Workshop). Select Workshop icon, rightclick+"Show Package Contents"
Go to \Contents\MacOS
rename the "JavaApplicationStub" file to "JavaApplicationStub.original"
Right-click on the JavaApplicationStub.original file, and select "Show original". A new Finder window will open (pointing to /System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/MacOS/)
Select the JavaApplicationStub file. Select "File\Copy" to add to the clipboard.
press Back button in Finder to bring you back to the content of the Workshop package (Applications\Kodak\Prinergy\Workshop\Contents\Mac OS)
Select File\Paste to copy the real JavaApplicationStub file.
Close all Finder windows. Workshop should now start.
This issue is also fixed automatically in 4.0.2.5 and higher (co-incidentally... we happened to move away from the "alias to OS copy of JavaApplicationStub" in that update for other reasons).
James
