--- In FS2_User@yahoogroups.com, Mark Henigan <driven_zen@...> wrote:
>
> Jim Read wrote:
> >
> <unrestrained snip>
> >
> > Mark,
> >
> > I will see what went wrong. FS/2 does do path length checking but
> > maybe not when summing. If so, I will fix it.
>
Hello Jim:
>
> That certainly sounds like a description of
> what I experienced because I have also found
> FS/2 to refuse to open a directory without
> crashing because there was an excessively
> long path within it.
>
> Also, I didn't actually answer your question.
> I hit the button to kill the wayward thread.
> The dialog stated that the process would
> continue. I did not press the abort button,
> /per se/.
>
> Best Regards,
>
> - Mark
>
> Mark Henigan

I could easily tell from the fs_except.log that it occurred in posting
a message to the message window. In some error conditions where it can
continue to perform a function, FS/2 posts the error message to the
bottom line message window. When it is appropriate, it also appends
the path, enclosed in "[ ]" to inform the user where the error
occurred. In this exception the path length was not checked,
overflowing the fixed length buffer, and the message handler was where
the exception occurred. Kind of an unusual condition.

In other cases, FS/2 reports excessive path/filename length by using a
pop up message box. Those are handled correctly.

The exception handler WAD and, upon clearing the thread exception
message window, normal operation should have resumed but the function
thread obviously is terminated.

I will include a fix for the next available update, whenever that is.
I don't plan to issue updates until warranted by number or severity.

Jim