Upon further review, my subject line is slightly incorrect.
It would appear that the ifp from ifp-line responds to most error conditions with a segfault, so this is apparently *not* a result of the wierd char. In fact, device reset before and after "ifp format" made it work, as I'd described. So the only issue on ifp-line is poor handling of error conditions. This has been fixed on ifp-line-libifp but at the cost of having the weird char blocking even "ifp format". -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
