On Tue 2018-02-20 22:32, Dallas Hinton (1:153/7715) wrote to andrew clarke:
Windows 10 64 bit. Timednt exe but everything else left exactly
as the way I use it with the old Timed (although I used to run it
on XP).
1) Full screen window -- the index of message areas looks like a
3/4 size window within the main window. It returns to full screen
when a message is opened or edited.
Yes, this is expected behaviour. The width of the arealist window is hardcoded for some reason. This could be seen in the OS/2 version of timEd 1.10, when the
Command Prompt window was set to be wider than the 80 column default (eg. with "mode 110,35").
I don't consider it a bug, but I'll look into having timEd use the entire window, because it does look odd.
2) Control-End does not jump to the last message in an area.
OK. I guessed there might still be some leftover key translation problems with the Windows version. I'll look into it.
3) Headers (to, from etc) are lost when scrolling down in a long
message.
4) Bottom line ("Area: xxx % Current: xx High: xx |clock" not
showing
5) On XP -- no difference noticed at all between timed.exe,
tim386.exe, and timednt.exe
I can't reproduce #3 or #4 in Windows 7.
A screenshot would be handy.
Given you say the problem doesn't exist in XP, I'm assuming the Windows 10 Command Prompt window is behaving differently. I must admit I haven't tested timEd 1.12 in Windows 10 yet. I'll have a look.
More to come, I suspect -- but I sure appreciate being able to use timed locally again!!
I was wondering what you meant until I remembered 64-bit Windows 10 won't run DOS programs any more.
At least not without DOSBox, or vDosPlus.
Regards
Andrew
--- timEd/NT 1.12+
* Origin: X (3:633/267.1)