If you're crashing with the dump provided before, the problem is very likely a bug in Tiger with the API that returns the volume list - it used to generate exceptions just like the one you sent when used with "null" named FAT32 volumes.
You can look in the console, of course, but if SD! is crashing there's not going to be any SD log to look at.
__________________
--Dave Nanian
|