On Thu, 24 Apr 2008 07:27:16 +0100, in
gmane.comp.lang.smalltalk.squeak.general you wrote:
>Rio may be what you are looking for.
>
>http://www.squeaksource.com/Rio
>
>docs: http://wiki.squeak.org/squeak/5929
>
>enjoy
>
>Keith

Thanks Keith. I've been playing with Rio; not quite got my head around
it yet but I'm going to play with it some more tomorrow. 

The printOn: methods in classes RioKernel and Cwd are causing DNUs
from class LimitedWriteStream, for want of methods #<< and #, which
I'm guessing you must have in your image, but which aren't being
included in the package. 

This occurs regardless of whether I load the latest versions off
SqueakSource, or whether I do it via the Universe Browser.

Right now I've just altered those printOn: methods in my image, to do
something a little more conventional (to my eyes), so no big deal.

I was a little alarmed to see all of the Rio tests produce errors,
(I'm running a fresh 3.10.7159 image and 3.10.6 Windows VM on XP,
straight from the FTP site today); it turned out just to be that the
MultiByteFileStream to "..\_test_\InflateStream.orig" (from the
RioGzipTest) wasn't being closed soon enough, so the _test_ folder
wasn't getting deleted during the tear down.

The specific error that each test gives is:
RioLocalDosFileSystem>>errorUnableToDeleteDir: 

I don't know enough to say whether that's likely to be a problem in
real life, or whether it's just a consequence of the way the tests are
run, but for what it's worth I found that adding "Smalltalk
garbageCollectMost" to the top of RioKernelTest>>tearDown took care of
it - all tests passed.

Cheers,
Nick