Hi Andrew -- on Feb 21 2018 at 12:38, you wrote:

If so, please provide me with any feedback!

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.

2) Control-End does not jump to the last message in an area.

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

More to come, I suspect -- but I sure appreciate being able to use timed locally again!!



Cheers... Dallas



Cheers... Dallas

--- timEd/NT 1.12+
* Origin: The BandMaster, Vancouver, CANADA (1:153/7715)

Hi Dallas -- on Feb 20 2018 at 22:32, you wrote:

If so, please provide me with any feedback!

Windows 10 64 bit.

F1 (help) does nothing!!


Cheers... Dallas

--- timEd/NT 1.12+
* Origin: The BandMaster, Vancouver, CANADA (1:153/715)

Hi Dallas,

On 2018-02-20 22:32:00, you wrote to andrew clarke:

If so, please provide me with any feedback!

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.

2) Control-End does not jump to the last message in an area.

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

More to come, I suspect -- but I sure appreciate being able to use timed locally again!!

Cheers... Dallas

Cheers... Dallas

6) Double signatures.


;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

On 2018 Feb 21 08:40:42, you wrote to Dallas Hinton:

6) Double signatures.

that's because he edited the message... not sure if he's using the internal editor or an external one... it can make a difference because either one can be
set to add a signature...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Disassembler: An unattended 5 year old child.
---
* Origin: (1:3634/12.73)

Hi Wilfred -- on Feb 21 2018 at 08:40, you wrote:

6) Double signatures.

Thanks - that was MY fault - I copied and pasted badly!


Cheers... Dallas

--- timEd/NT 1.12+
* Origin: The BandMaster, Vancouver, CANADA (1:153/715)

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)

On Tue 2018-02-20 23:24, Dallas Hinton (1:153/715) wrote to andrew clarke:

F1 (help) does nothing!!

Odd. It works in Windows 7.

https://imgur.com/a/nsLeb

Does F4 (duplicate line) work?

Or F10 (save menu).

--- timEd/NT 1.12+
* Origin: X (3:633/267.1)

Hi andrew -- on Feb 22 2018 at 10:45, you wrote:

I don't consider it a bug, but I'll look into having timEd use the
entire window, because it does look odd.

Thanks!

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.

In your spare time! :-)

A screenshot would be handy.

Coming.... got an email, or dropbox, or ..... dhinton@shaw.ca

At least not without DOSBox, or vDosPlus.

I used to use VMWare with an XP, but now I just vnc to my XP box! :-)

BTW, I'm using the old q-edit (TSE32) as an editor....

Cheers... Dallas

--- timEd/NT 1.12+
* Origin: The BandMaster, Vancouver, CANADA (1:153/715)

Hi andrew -- on Feb 22 2018 at 11:01, you wrote:

F1 (help) does nothing!!

Odd. It works in Windows 7.

That's the call from TimEd for help

Does F4 (duplicate line) work?

Or F10 (save menu).

Yes, but that's within my TSE32 editor. I've not tried TimEd's native editor.



Cheers... Dallas

--- timEd/NT 1.12+
* Origin: The BandMaster, Vancouver, CANADA (1:153/715)

On Wed 2018-02-21 23:33, Dallas Hinton (1:153/715) wrote to andrew clarke:

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.

In your spare time! :-)

This is fixed in timEd 1.30, which I've just released.

1.12 was very short-lived :-)

A screenshot would be handy.

Coming.... got an email, or dropbox, or ..... dhinton@shaw.ca

mail@ozzmosis.com

But first see the notes about using timEd 1.30 in Windows 10.

BTW, I'm using the old q-edit (TSE32) as an editor....

Ah, I've not used it.

I'm just using the internal editor.

--- timEd/NT 1.30+
* Origin: X (3:633/267.1)

On Wed 2018-02-21 23:31, Dallas Hinton (1:153/715) wrote to andrew clarke:

F1 (help) does nothing!!

Odd. It works in Windows 7.

That's the call from TimEd for help

Yes, F1 works here outside the editor.

Does F4 (duplicate line) work?
Or F10 (save menu).

Yes, but that's within my TSE32 editor. I've not tried TimEd's
native editor.

OK, I assumed you meant the internal editor.

--- timEd/NT 1.30+
* Origin: X (3:633/267.1)

Hi andrew -- on Feb 22 2018 at 20:00, you wrote:

But first see the notes about using timEd 1.30 in Windows 10.

That's working just fine!!

BTW, I'm using the old q-edit (TSE32) as an editor....

Ah, I've not used it.

I'm just using the internal editor.

I've been using TSE since it's inception in DOS - I don't think I could learn a
different editor now!!



Cheers... Dallas

--- timEd/386 1.10.y2k+
* Origin: The BandMaster, Vancouver, CANADA (1:153/7715)

Hi andrew -- on Feb 22 2018 at 20:03, you wrote:

Yes, F1 works here outside the editor.

Not in W 10, it would seem.



Cheers... Dallas

--- timEd/386 1.10.y2k+
* Origin: The BandMaster, Vancouver, CANADA (1:153/7715)