In the meantime, I've done what I mentioned - generating a squish.cfg just
before launching the above - and this works. Just using a simple batch file
for the job, started from the timed directory:

cd \fido\bin\fe
fesetup3 -x$
copy squish.cfg \fido\bin\timed
cd \fido\bin\timed
chcp 1252
timedunx.exe
del \fido\bin\timed\squish.cfg

However, there's an interesting problem I'm getting - doubtless one that
only I experience and nobody else has ever heard of or can explain, as is
usual in such things, but still I'll mention it: When I enter an area and
read a message, then try to return to the area list (_not_ the message list
_in_ the current area), only the area I've been reading in is displayed.
When the program starts, all the areas are scanned and displayed properly
and I can enter any one of them. But I can't get back to this... only to a
display of the single area I was reading in. Oh, and the right arrow key to
go to the next area with unread mail also doesn't work... just sends me
back to the same area again.

I have to note, however, that timedunx is physically on my OS/2 fido
computer, as is everything else connected with fido, and that I start the
program via my local network on my Win2000 machine. All the paths in the
timed configuration, and all those in the message base, are stated without
drive letters, e.g. \fido\echomail\moderator_ger. I have to do this to make
things independent of where the programs are started, since the drive
letters are different depending on whether the drive is local or network.

All this is just information to play with when and if you're interested, as
a solution is not critical for me. But I admit I'm intrigued by this and
wonder what is happening. It can't be just a problem with the paths without
drive letters, since then the startup scan wouldn't work.

Cheers, Bob

--- GoldED+/W32 1.1.5-0613