From: "Milton Aupperle" <milton@outcastsoft.com>

Date: November 28, 2005 4:36:42 PM MST

To: Astro_IIDC@yahoogroups.com

Subject: Re: DMK camera fixes itself - is there some kind of timeout?

Anthony;

Milton, is that really the way that Astro_IIDC is written? I find that

a bit surprising. I use Linux for my firewire imaging and an

application called Coriander which lets me unplug and replug my

firewire camera as often as I like without crashing.

NO - ASTRO IIDC DID NOT CRASH - Where did you Get That From?

He unplugged the camera and expected it to automagically reconnect up

when he re-plugged it in. It cleanyl shut down and released all the

resources it had allocated.

If I unplug the camera then it cleanly shuts down any capture stream

and puts up a dialog box saying something like "No firewire camera

present. Please connect a camera to continue". It sits there patiently

until I plug a camera back in (either the same camera or a different

one) and then the dialog closes and the application resumes with the

new camera.

So does Astro IIDC. IT NEVER CRASHES even while the stream was running

and you yank the cord. It did warn him that the camera was having a

problem and also printed off warnign messages in the console.log.

As I said before - under OS 9 at the system level if you disconected

it it would reconnect up automagically - under OS X it doesn't happen

at all - it's left orphaned. You can force it too - but that has it's

own problems under OS X.

I assumed that all firewire applications would behave like this, as

the firewire protocol has more than enough flexibility to allow it.

That's a limitation of OS X's I/O Kit implementatio.

It's vey sad to hear that unplugging a firewire camera could cause any

sort of crash. That is reminiscent of a different operating system...

Why not try actually READING what was written. At no time did anyone

say "Astro IIDC  Crashed" because of this.

Milton Aupperle