Did these wind up in your inbox instead? I'm running NT4 also and
had problems consistently with email import until I replaced the
import and filter programs in my $home directory with the standard
DOS versions from yarn_092. I didn't have your exact message,
though, mine was more of a 'error running filter' message.
One problem I've run into using NT is decoding MINE binaries. The
only decoders I've got are DOS utilities, so I lose the long files.
Does anyone have a link to a Win32 version of Munpack or UUdeview?
>Boot under Win95 and "import" works as normal.
Don't have Win95, though my OS/2 started giving me problems when I
added a Zip drive I got for Christmas. OS/2 runs fine, but all OS/2
Yarn functions started running *really* slow. Where import would
take only a minute or so pre-Zip, it was taking a half hour to import
a 10 MB packet (lots of binaries.) Add to that the additional time
needed to expire a 50 MB newsbase and I had to find a new solution.
It's not the Zip drivers causing the problem, either, since I had
the same problems when I upgraded to FP31. Luckily I had run
Sysbench against my system a week or so pre-Zip, so I had a record
of system performance. There are slight differences in drive access
times, but they don't seem far enough off to seem significant. The
DOS import and expire functions weren't affected however, so the
above fix for NT was no problem. Yarn reading under OS/2 has slowed
considerably also, so I created a batch file to read news using the
DOS Yarn, leaving only the binaries with long file names to be
decoded using OS/2. Has anyone else noticed similar problems either
in Yarn or OS/2 under FP31?
-- ======= Remove the 5 digit spamkiller from address before replying ========== : LabRat 'at' pobox 'dot' com : Just because you're paranoid doesn't : : : mean they're not out to get you : =============================================================================