Mark Henigan wrote:
> Hello Jim:
>
> When I attempted to copy a large directory from
> one JFS partition to another JFS partition using
> Copy under FS/2, it ended with a thread exception:

Hi Mark,

When copying or deleting directories, FS/2 by default options sums all
files in the source directory for the purpose of presenting a progress
bar, one of the nicer features in FS/2 IMHO. The larger the directory
and also depending on the source media, the more time consuming this is.
Since some users still are running very old, slower computers, The
dialog that is shown during summation has an 'Abort' button on it. Using
the abort stops the summation and gets on with the copy - and cancels
the use of a progress bar. Once the copy operation starts, the same
abort button is used to abort the copy.

It appears from what you have said and presented from the logs, the
abort was used during this summation phase. This can either be an 'Esc'
or 'Enter' key or a mouse click on the abort button.

Did you knowingly use the abort button?

For you and everyone else that reports a problem, it is very helpful in
resolving any problem to have a very detailed explanation of what user
actions preceded the problem. The fs_debug.log does not get
auto-activated until a exception has occurred. In most cases it only
defines what FS2 did after the exception. In a repeatable scenario, it
is possible to activate various logs before the event but that usually
takes some coaching from myself. All the *.log files help in problem
diagnosis but the fs_dump.log and fs_except.log probably help the most.
The fs_dump.log is of the type that can't be quoted in an email or
forum. It contains a dump of the most useful program variables that
existed at the time of the exception and is normally generated with
every exception. So it's most helpful if all the logs can be sent to me.
You may edit them to include only the very recent events if you wish to.

Regards,
Jim