Hi,
I do first test with Windows 11 and xHb console application.
The problem seems to be the font to use in console.
When using raster font, german umlauts and frame characters are shown correct. But when using Lucida Console, all Characters above Ascii 128 are not shown correct.
Before Windows 11, this was no problem.

I am grateful for any advice.

Michael Hagl.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Dear Michael Hagl:

On Thursday, December 30, 2021 at 3:40:10 AM UTC-7, Michael Hagl wrote:
...

I do first test with Windows 11 and xHb console application.
The problem seems to be the font to use in console.
When using raster font, german umlauts and frame characters
are shown correct. But when using Lucida Console, all Characters
above Ascii 128 are not shown correct.

Did you check to see if the code page was successfully changed? Does this function call return success or failure. I do see that code pages are deprecated, and we are encouraged to go to UTF-8 or UTF-16... Which means you might have to set up the font
before executing your program.

Before Windows 11, this was no problem.

May or may not help: https://docs.microsoft.com/en-us/windows/win32/intl/code-pages

David A. Smith

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi David,

sorry for delay!

It seems to help to start the xHb-program.exe in batch file and do chcp 437 before the program is started.

The new windows terminal seems to have more problems to show the line of my xHb programm in a correct way.

I will do more tests.

I think, all users which are using console mode of xHb will have problems with windows 11.

Michael


dlzc schrieb am Montag, 3. Januar 2022 um 15:08:51 UTC+1:

Dear Michael Hagl:

On Thursday, December 30, 2021 at 3:40:10 AM UTC-7, Michael Hagl wrote:
...

I do first test with Windows 11 and xHb console application.
The problem seems to be the font to use in console.
When using raster font, german umlauts and frame characters
are shown correct. But when using Lucida Console, all Characters
above Ascii 128 are not shown correct.

Did you check to see if the code page was successfully changed? Does this function call return success or failure. I do see that code pages are deprecated, and we are encouraged to go to UTF-8 or UTF-16... Which means you might have to set up the font

before executing your program.

Before Windows 11, this was no problem.

May or may not help: https://docs.microsoft.com/en-us/windows/win32/intl/code-pages

David A. Smith

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thursday, December 30, 2021 at 12:40:10 PM UTC+2, in...@hagl.de wrote:

Hi,
I do first test with Windows 11 and xHb console application.
The problem seems to be the font to use in console.
When using raster font, german umlauts and frame characters are shown correct. But when using Lucida Console, all Characters above Ascii 128 are not shown correct.
Before Windows 11, this was no problem.

I am grateful for any advice.

Michael Hagl.

Eventually you might want to try out the procedures described below for configuring compatibility mode:
https://www.online-tech-tips.com/computer-tips/run-older-programs-in-compatibility-mode-in-windows-11-10/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Ella Stern schrieb am Dienstag, 4. Januar 2022 um 18:35:19 UTC+1:

On Thursday, December 30, 2021 at 12:40:10 PM UTC+2, in...@hagl.de wrote:

Hi,
I do first test with Windows 11 and xHb console application.
The problem seems to be the font to use in console.
When using raster font, german umlauts and frame characters are shown correct. But when using Lucida Console, all Characters above Ascii 128 are not shown correct.
Before Windows 11, this was no problem.

I am grateful for any advice.

Michael Hagl.

Eventually you might want to try out the procedures described below for configuring compatibility mode:
https://www.online-tech-tips.com/computer-tips/run-older-programs-in-compatibility-mode-in-windows-11-10/

Hi Ella,

I think it´s no problem of compatibility. The only problem seems to not using the raster font for DOS-Box.
On Win 10 I can use Lucida Console without any Problems, but on Win 11 there are no Umlauts even I set chcp 437 before starting program.
But sometimes the output on screen is correct although i use Lucida Console as font.
This seems to work in DOS-Box or starting the programm in batch file.
But when starting the program.exe direct with double click, then how to change codepage and font?

This is very misterious.

Michael

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tuesday, January 4, 2022 at 8:52:42 PM UTC+2, in...@hagl.de wrote:

Ella Stern schrieb am Dienstag, 4. Januar 2022 um 18:35:19 UTC+1:

On Thursday, December 30, 2021 at 12:40:10 PM UTC+2, in...@hagl.de wrote:

Hi,
I do first test with Windows 11 and xHb console application.
The problem seems to be the font to use in console.
When using raster font, german umlauts and frame characters are shown correct. But when using Lucida Console, all Characters above Ascii 128 are not shown correct.
Before Windows 11, this was no problem.

I am grateful for any advice.

Michael Hagl.

Eventually you might want to try out the procedures described below for configuring compatibility mode:
https://www.online-tech-tips.com/computer-tips/run-older-programs-in-compatibility-mode-in-windows-11-10/

Hi Ella,

I think it´s no problem of compatibility. The only problem seems to not using the raster font for DOS-Box.
On Win 10 I can use Lucida Console without any Problems, but on Win 11 there are no Umlauts even I set chcp 437 before starting program.
But sometimes the output on screen is correct although i use Lucida Console as font.
This seems to work in DOS-Box or starting the programm in batch file.
But when starting the program.exe direct with double click, then how to change codepage and font?

This is very misterious.

Michael

"Compatibility mode" is making certain assumptions regarding the code pages and font families (between others).
If I were you I'd try out the options offered in the "troubleshooting" check list (one at a time).
Also make sure that the computer's locale settings are configured for the German language (like your customers do have it).
I don't yet have a Windows 11 machine, I cannot test it further.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tuesday, January 4, 2022 at 10:36:52 PM UTC+2, Ella Stern wrote:

On Tuesday, January 4, 2022 at 8:52:42 PM UTC+2, in...@hagl.de wrote:

Ella Stern schrieb am Dienstag, 4. Januar 2022 um 18:35:19 UTC+1:

On Thursday, December 30, 2021 at 12:40:10 PM UTC+2, in...@hagl.de wrote:

Hi,
I do first test with Windows 11 and xHb console application.
The problem seems to be the font to use in console.
When using raster font, german umlauts and frame characters are shown correct. But when using Lucida Console, all Characters above Ascii 128 are not shown correct.
Before Windows 11, this was no problem.

I am grateful for any advice.

Michael Hagl.

Eventually you might want to try out the procedures described below for configuring compatibility mode:
https://www.online-tech-tips.com/computer-tips/run-older-programs-in-compatibility-mode-in-windows-11-10/

Hi Ella,

I think it´s no problem of compatibility. The only problem seems to not using the raster font for DOS-Box.
On Win 10 I can use Lucida Console without any Problems, but on Win 11 there are no Umlauts even I set chcp 437 before starting program.
But sometimes the output on screen is correct although i use Lucida Console as font.
This seems to work in DOS-Box or starting the programm in batch file.
But when starting the program.exe direct with double click, then how to change codepage and font?

This is very misterious.

Michael

"Compatibility mode" is making certain assumptions regarding the code pages and font families (between others).
If I were you I'd try out the options offered in the "troubleshooting" check list (one at a time).
Also make sure that the computer's locale settings are configured for the German language (like your customers do have it).
I don't yet have a Windows 11 machine, I cannot test it further.

The "non-unicode" language should be German: https://websiteforstudents.com/how-to-change-system-locale-in-windows-11/
and after restarting the machine delete the desktop shortcut icon of your proggy, and create a new one (the old is carrying the properties of the old locale etc).

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Ella Stern schrieb am Dienstag, 4. Januar 2022 um 22:03:53 UTC+1:

On Tuesday, January 4, 2022 at 10:36:52 PM UTC+2, Ella Stern wrote:

On Tuesday, January 4, 2022 at 8:52:42 PM UTC+2, in...@hagl.de wrote:

Ella Stern schrieb am Dienstag, 4. Januar 2022 um 18:35:19 UTC+1:

On Thursday, December 30, 2021 at 12:40:10 PM UTC+2, in...@hagl.de wrote:

Hi,
I do first test with Windows 11 and xHb console application.
The problem seems to be the font to use in console.
When using raster font, german umlauts and frame characters are shown correct. But when using Lucida Console, all Characters above Ascii 128 are not shown correct.
Before Windows 11, this was no problem.

I am grateful for any advice.

Michael Hagl.

Eventually you might want to try out the procedures described below for configuring compatibility mode:
https://www.online-tech-tips.com/computer-tips/run-older-programs-in-compatibility-mode-in-windows-11-10/

Hi Ella,

I think it´s no problem of compatibility. The only problem seems to not using the raster font for DOS-Box.
On Win 10 I can use Lucida Console without any Problems, but on Win 11 there are no Umlauts even I set chcp 437 before starting program.
But sometimes the output on screen is correct although i use Lucida Console as font.
This seems to work in DOS-Box or starting the programm in batch file. But when starting the program.exe direct with double click, then how to change codepage and font?

This is very misterious.

Michael

"Compatibility mode" is making certain assumptions regarding the code pages and font families (between others).
If I were you I'd try out the options offered in the "troubleshooting" check list (one at a time).
Also make sure that the computer's locale settings are configured for the German language (like your customers do have it).
I don't yet have a Windows 11 machine, I cannot test it further.

The "non-unicode" language should be German: https://websiteforstudents.com/how-to-change-system-locale-in-windows-11/ and after restarting the machine delete the desktop shortcut icon of your proggy, and create a new one (the old is carrying the properties of the old locale etc).

Thank you Ella,

I will try it the next days.
At the moment I only do some tests with win11 because in the foreseeable future a customer with Windows 11 will come along.

Michael.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Il giorno mercoledì 5 gennaio 2022 alle 09:06:43 UTC+1 in...@hagl.de ha scritto:

Ella Stern schrieb am Dienstag, 4. Januar 2022 um 22:03:53 UTC+1:

On Tuesday, January 4, 2022 at 10:36:52 PM UTC+2, Ella Stern wrote:

On Tuesday, January 4, 2022 at 8:52:42 PM UTC+2, in...@hagl.de wrote:

Ella Stern schrieb am Dienstag, 4. Januar 2022 um 18:35:19 UTC+1:

On Thursday, December 30, 2021 at 12:40:10 PM UTC+2, in...@hagl.de wrote:

Hi,
I do first test with Windows 11 and xHb console application.
The problem seems to be the font to use in console.
When using raster font, german umlauts and frame characters are shown correct. But when using Lucida Console, all Characters above Ascii 128 are not shown correct.
Before Windows 11, this was no problem.

I am grateful for any advice.

Michael Hagl.

Eventually you might want to try out the procedures described below for configuring compatibility mode:
https://www.online-tech-tips.com/computer-tips/run-older-programs-in-compatibility-mode-in-windows-11-10/

Hi Ella,

I think it´s no problem of compatibility. The only problem seems to not using the raster font for DOS-Box.
On Win 10 I can use Lucida Console without any Problems, but on Win 11 there are no Umlauts even I set chcp 437 before starting program.
But sometimes the output on screen is correct although i use Lucida Console as font.
This seems to work in DOS-Box or starting the programm in batch file. But when starting the program.exe direct with double click, then how to change codepage and font?

This is very misterious.

Michael

"Compatibility mode" is making certain assumptions regarding the code pages and font families (between others).
If I were you I'd try out the options offered in the "troubleshooting" check list (one at a time).
Also make sure that the computer's locale settings are configured for the German language (like your customers do have it).
I don't yet have a Windows 11 machine, I cannot test it further.

The "non-unicode" language should be German: https://websiteforstudents.com/how-to-change-system-locale-in-windows-11/ and after restarting the machine delete the desktop shortcut icon of your proggy, and create a new one (the old is carrying the properties of the old locale etc).

Thank you Ella,

I will try it the next days.
At the moment I only do some tests with win11 because in the foreseeable future a customer with Windows 11 will come along.

Michael.

Hello Michael,

by default Windows 11 use PowerShell to run console applications.
I solved problems related to screen and fonts by force Windows to use the old Command Prompt (Windows Console Host).

Best regards,
Roberto

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)