LaserSoft Imaging

hi.

I have the SF-210 auto-feeder attached to my Coolscan 4000 ED.

If in SF Ai Studio, I click the "Eject slide" button while there is no slide loaded in the scanner, then SF hangs indefinitely requiring a Force-Quit.

SF also hangs when I click the "Eject slide" button if a slide is loaded in the scanner but there is no slide in the IN tray of the auto-feeder. The pre-loaded slide gets ejected but SF than hangs as it waits for the next non-existent slide to load.

Is it possible to cancel the "Eject slide" operation with command-. or Escape?

cheers,
Gregory
Mac OS X 10.6 (10A421a)
Mac Pro, Quad-Core Intel Xeon, 2.8 GHz x 2, 8GB RAM

Related to the above problem:

In Batch mode while using the SF-210 auto-feeder, when the scanner has scanned the last slide in the feeder and there are no more slides to load, SF hangs. There is no way to avoid this unless you know exactly how many slides will be scanned and set the correct value in the Maximum Slides dialog when Feeder is chosen in the General pane.

Unfortunately, Force-Quitting means that all settings are lost, so it becomes a habit for one to Quit SF after configuring all settings to save them before relaunching and actually initiating the batch scan.

BUT, all that said, having to Force-Quit from time to time when I forget to be careful about which button I press is a small price to pay for being able to use SilverFast Ai and my (discontinued) Nikon Coolscan 4000ED on a Mac Pro running Snow Leopard and with full support for my scanner's infrared channel

Now to actually get to it and scan every slide/neg in the house before technology gets too far ahead of me.

btw, a big THANK YOU for the HDRi format. I can now choose to save every scan at maximum hardware resolution with Infrared for processing whenever I need without worrying that the film might degrade. (mmm... I can save roughly 5000 full-res HDRi images on my new 1TB drives; probably enough.)

cheers,
Gregory

I left SF running in Batch Mode last night, and this morning when I woke, it had completed the Batch and correctly displayed the "Batch Completed" dialog. Cool!

I'll have to see if it repeats this desired behaviour with future Batch scans.

More later...