andrew clarke wrote to Robert Bashe on Thursday August 07 2003 at 13:28:

RB>> When I enter an area and read a message, then try to return to the
RB>> area list (_not_ the message list _in_ the current area), only the
RB>> area I've been reading in is displayed.

[...]

ac> This sounds like a problem with your Startup_Mode command in
ac> timed.cfg.

I pretty well exclude configuration problems since I'm using precisely the
same configuration I used for some 6-7 years on the OS/2 machine with the
only differences being the squish.cfg instead of the fastecho configuration
and the fact that the paths are specified without drive letters as I
already mentioned.

ac> Or maybe there is a bug in the code somewhere.

Possibly. I'd have to look at the original 32-bit DOS extender version of
timED (which I didn't know existed until recently, and still have no source
for) for a comparison to say much.

ac> Or maybe neither.

Possibly the networking setup is producing this, although I use the same
kind of setup with GoldED without problems.

ac> Need more information.

;-)

ac> Can you post your timed.cfg?

I can, but I doubt if it will tell you anything since as I say it's the
same one I used for many years with only the above indicated change and the
fact that the batch file for the program is started over the network. It
may be that the paths without drive letters cause problems in only _some_
timED routines. That wouldn't surprise me too much, since such paths aren't
really standard, although they often work. See the bottom for the
configuration (I've removed the comments to shorten it).

ac> And also state which version of timEd 1.11 you're using (although I
ac> suspect it won't matter).

The archive is named tm111a4c.zip.

ac> Also, you might want to see if you can repeat the problem with timEd
ac> 1.10 (OS/2 or DOS).

There are no problems with the OS/2 version, since I used it for many
years, but naturally I can't use it in the network. The DOS version doesn't
see the long file names of my message base and so it's not a particularly
good candidate to check. If you know where I can get a copy of the 32-bit
DOS extender version I could check it, since I presume it will
"see" the long file names.

Otherwise I wouldn't worry too much about it... probably this is just some
glitch due to the networking.

Cheers, Bob

timed.cfg:


=== Cut ===

Address          2:2448/44
Address          2:2448/1

;========= added for version 1.10

V7NodeFlagBit 16 CM
DefaultOutput IBMPC
DefaultInput IBMPC

Name       "Robert Bashe"

Nodelist    \fido\Nodelist

Zonegate Ask

Kill_Original No

AKAmatching Yes

INTLforce No

Netmail_Tearline Yes

FreqAttributes ck

Origin    "Jabberwocky System - ISDN/Zyx at 49-2363-56073"

Editor \fido\share\q.exe

hello           "Tag %fto,\n\n"

rephello        "Tag %ffrom,\n\nAm %day.%mon %year schrieb %from eine
Mail an %to:"

followhello     "Weiter zu einer Mail vom %day.%mon %year um %time von
%from an %to:\n\n"

Signoff         "Gruesse, Bob\n"

EchoLog \fido\flags\echotoss.log

Include Timed1.col

ShowKludges No

Startup_Scan Yes

Personal_Skip_Received No

End_Of_Area_Menu Yes

Move_Notes Yes

WriteName \fido\bin\timed\temp\export.txt

Printer LPT3

Squishcfg \fido\bin\timed\squish.cfg

;Fastechocfg \fido\bin\fe\fastecho.cfg

ReadLocalAreas Yes

ReadNetAreas   Yes

AreaListSort TGN

Swap_on_Edit  Yes

Swap_on_Shell Yes

Confirm_Delete Yes

Confirm_Exit Yes

Jumpy_Edit Yes

CCVERBOSE YES

=== Cut ===

--- GoldED+/W32 1.1.5-0613