Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
stacker:support:knownissues [2018/09/09 18:31] rjlittlefield [Settings are retained across uninstall / reinstall] |
stacker:support:knownissues [2020/06/23 17:17] rjlittlefield [Macintosh OS X, accessing external drives may be awkward] |
||
|---|---|---|---|
| Line 22: | Line 22: | ||
| * [[#windows_manually_edited_program_files_persist_across_re-installation|Windows, manually edited program files persist across re-installation]] | * [[#windows_manually_edited_program_files_persist_across_re-installation|Windows, manually edited program files persist across re-installation]] | ||
| * [[#macintosh_os_x_could_not_establish_communications_with_stackshot_controller|Macintosh OS X, "Could not establish communications with StackShot controller"]] | * [[#macintosh_os_x_could_not_establish_communications_with_stackshot_controller|Macintosh OS X, "Could not establish communications with StackShot controller"]] | ||
| + | * [[#macintosh_os_x_zerene_stacker_will_work_on_only_one_stack_at_a_time|Macintosh OS X, Zerene Stacker will work on only one stack at a time]] | ||
| * [[#macintosh_os_x_mountain_lion_reports_installation_bundle_is_damaged_move_to_trash|Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash"]] | * [[#macintosh_os_x_mountain_lion_reports_installation_bundle_is_damaged_move_to_trash|Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash"]] | ||
| * [[#macintosh_os_x_how_to_recover_from_excessive_memory_allocation|Macintosh OS X, how to recover from excessive memory allocation.]] | * [[#macintosh_os_x_how_to_recover_from_excessive_memory_allocation|Macintosh OS X, how to recover from excessive memory allocation.]] | ||
| Line 150: | Line 151: | ||
| java.io.FileNotFoundException: C:\Users\Me\Pictures\unnamedZSproj20111103154858382\previewimages\-Unaligned-117.jpg (Access is denied) | java.io.FileNotFoundException: C:\Users\Me\Pictures\unnamedZSproj20111103154858382\previewimages\-Unaligned-117.jpg (Access is denied) | ||
| at java.io.RandomAccessFile.open(Native Method) | at java.io.RandomAccessFile.open(Native Method) | ||
| - | | + | |
| There are several possible workarounds for the problem: | There are several possible workarounds for the problem: | ||
| - Turn off or pause the backup or indexing facility while ZS is running. | - Turn off or pause the backup or indexing facility while ZS is running. | ||
| Line 237: | Line 238: | ||
| Interestingly, in most cases just going through the above steps to collect the required information also makes the problem disappear. That probably has to do with the reboot and order of operations. | Interestingly, in most cases just going through the above steps to collect the required information also makes the problem disappear. That probably has to do with the reboot and order of operations. | ||
| + | |||
| + | ===== Macintosh OS X, Zerene Stacker will work on only one stack at a time ===== | ||
| + | |||
| + | Solution: open a Terminal window and launch additional copies of Zerene Stacker using the command | ||
| + | <code> | ||
| + | open -n /Applications/ZereneStacker.app | ||
| + | </code> | ||
| + | |||
| + | If you put the ZereneStacker icon (the ZereneStacker.app application bundle) someplace besides in /Applications, then just edit the command line accordingly. | ||
| + | |||
| + | The explanation here is that by design, Zerene Stacker is programmed using the "single document" model. This means that each instance of Zerene Stacker can only work with one stack at a time. The normal process of launching Zerene Stacker by clicking its icon will not launch a second instance. Instead, clicking the icon just makes the current instance foreground, apparently in the expectation that all programs are multi-document. Unfortunately there seems to be no way to just tell MacOS that Zerene Stacker is single document and it should launch another instance when the launch icon is clicked. The "-n" argument on the open command says to create a new instance regardless of whether there's already one running. | ||
| + | |||
| ===== Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash" ===== | ===== Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash" ===== | ||
| Line 264: | Line 277: | ||
| ===== Macintosh OS X, accessing external drives may be awkward ===== | ===== Macintosh OS X, accessing external drives may be awkward ===== | ||
| - | **Note:** In all recent versions, you can drag-and-drop directly onto the input files list. There is no need to File > Add Files to open a filechooser as described below. Just open a separate Finder window, select your image files there, then use drag-and-drop to enter them directly into Zerene Stacker's "Input Files" panel, at the place where it says "(Drop files or folders here to begin)". | + | On Macs, Zerene Stacker normally attempts to open a Finder window to use as a helper service for navigating and selecting files. On a few Macs, for unknown reasons, the Finder window refuses to open. In that case, Zerene Stacker automatically switches to a different method, using a facility named "JFileChooser" that is part of the Java Runtime Environment that Zerene Stacker runs on top of. (The use of JFileChooser can also be selected explicitly, by removing the checkmark at Options > Preferences > Look & Feel > "Use system native File Choosers if possible".) |
| - | + | ||
| - | Further explanation and other approaches follow. | + | |
| - | + | ||
| - | The JFileChooser that can be selected for use by Zerene Stacker does not display alternate volumes like the native Mac filechooser does. External drives can still be accessed, but the procedure is somewhat awkward. | + | |
| - | + | ||
| - | On OS X 10.5 (Leopard) and later, the easiest approach is to open a filechooser dialog box in Zerene Stacker, using File > Add Files. Then separately, use Finder to open the external drive or network share, go to the appropriate directory, and select the files of interest. Drag and drop those files onto the Add Files dialog of Zerene Stacker, then click the Add button in the Zerene Stacker dialog. This method also has the advantage of showing you a thumbnail preview of the files to be added. | + | |
| - | Alternatively (and required for OS X 10.4), you can go to the bar at the top of the window, the one where the current directory is shown. Click once on that bar and it will expand into a pull-down list of enclosing directories. At the bottom of the list will be an entry like "Macintosh HD", representing the main file system of the computer. Click that. Scroll to the bottom of the list and double-click on Volumes. That should give you a list of all your currently mounted media. Double-click on any external drive to open that, then navigate as usual. | + | Unfortunately the JFileChooser interface looks much different from Finder, and it requires more mouseclicks to access drives other than the default. |
| - | The latter approach is required on OS X 10.4 because drag-and-drop into the Zerene Stacker filechooser does not work on that system. | + | To access alternate drives using JFileChooser, proceed as follows: |
| + | - Open a JFileChooser window, for example by File > Add File(s) or File > Save Output Image(s). | ||
| + | - Go to the bar at the top of the window, the one where the current folder is shown. Click on that bar and it will expand into a pull-down list of enclosing folders. | ||
| + | - At the top or bottom of the list will be an entry like "/" or "Macintosh HD", representing the main file system of the computer. Click that to open it. | ||
| + | - Scroll to the bottom of the list and double-click on Volumes. That should open to give you a list of all your currently mounted media. | ||
| + | - Double-click on any external drive to open that, then navigate as usual. | ||
| ===== Macintosh OS X, launch fails due to Courier font problems ===== | ===== Macintosh OS X, launch fails due to Courier font problems ===== | ||