leecher1337 / ntvdmx64

Run Microsoft Windows NTVDM (DOS) on 64bit Editions
805 stars 81 forks source link

AutoBuild problem #123

Open peter8777555 opened 3 years ago

peter8777555 commented 3 years ago

I build the ntvdmx64 step by step before. And no any problems by manual.

This is my first time to use auto build. 1. autobuild-ccpu-chk.cmd : It works and make 17 releases. The bld-minnt.cmd change chcp 950 to chcp 437.(The patch.cmd is OK.) The CMD text is VERY SMALL,i can not read text.

0_SmallText_CHCP437

2. autobuild-haxm-chk.cmd A. The bld-minnt.cmd change chcp 950 to chcp 437.(The patch.cmd is OK.) The CMD text is VERY SMALL,i can not read text. B. It does not work, I got error message and ABORT. By the way, My old PC for 12 years.Is this the problems ? I know my OLD PC no support HAXM.

0_Error1

0_Error2

Copying DOS files TS-Aware-Patcher 1.0

Cannot open file C:\NTVDMBLD\w\minnt\base....\Binaries\x86chk\ntvdm.exe: ¿t▓╬ºΣñú¿∞½ⁿ⌐w¬║└╔«╫íC Language br is invalid, aborting ??????? . . . ??? 1 ???? Cleaning up... Autobuild completed, check releases-directory ??????? . . .

peter8777555 commented 3 years ago

The autobuild-ccpu-chk.cmd and autobuild-haxm-chk.cmd can work.

Small question :

The CMD text is VERY SMALL,i can not read text.

leecher1337 commented 3 years ago

We found out in https://github.com/leecher1337/ntvdmx64/issues/76 that chcp 437 seems to be necessary on your system to build properly. Maybe putting chcp 437 directly into the autobuild script helps with your problem so that console doesn't cahnge codepage while working but already directly at start, can you check this?

peter8777555 commented 3 years ago

The autobuild-ccpu-chk.cmd and autobuild-haxm-chk.cmd can work.

I try 2 options.

Option 1 :

Change CHCP 437 firstly change font size to 8 x 12 Run auto build

All Non-English text will show ???????

a1

a2

Option 2 :

C:\NTVDMBLD\w\ntvdmpatch\bld-minnt.cmd @echo off call basepath.cmd pushd %BASEPATH% set BUILD_ALLOW_ALL_WARNINGS=1 set CCPU=1 chcp 437 build -e popd

C:\NTVDMBLD\w\ntvdmpatch\bld-minnt-haxm.cmd @echo off call basepath.cmd pushd %BASEPATH% set BUILD_ALLOW_ALL_WARNINGS=1 set HAXM=1 chcp 437 build -e popd

I remove "chcp 437" and work well. This is the best option.

a3

peter8777555 commented 3 years ago

By the way, My old PC for 12 years and no support HAXM. (Intel Core2Quad Q8400 2.66GHz 1333FSB 45NM LGA775 VT 2009Q2)

But i have powerful Nvidia GeForce GTX960 VGA ,it supports hardware acceleration(CUDA), Is it possible to support hardware acceleration(CUDA) ?

leecher1337 commented 3 years ago

So the build doesn't fail or produce bad results when not using chcp 437? That's weird, because you had this problem in the past:

So,the multi-language build for me is not good.
I must use USA(437) build and works.
if i use CHT(950) build and cry.

https://github.com/leecher1337/ntvdmx64/issues/76#issuecomment-591367752

cl16 seems to fail on non-CP437 (far east) systems, as we found out: https://github.com/leecher1337/ntvdmx64/issues/76#issuecomment-592219929

This commit was made due to the compilation problems: https://github.com/leecher1337/ntvdmx64/commit/4512fa5edc7773c7811bef6a8627e22d47d9b166

It makes no sense for me why it failed for you in the past and now it doesn't fail. As you reported the problem in the past, do you have an explanation?

Are you sure that it builds without a single error? Note that the mkrelease-script runs through no matter if complilation fails or succeeds, so errors neet to be checked in buildchk.err in w\minnt\base I don't want to break the build process.

But i have powerful Nvidia GeForce GTX960 VGA ,it supports hardware acceleration(CUDA), Is it possible to support hardware acceleration(CUDA) ?

No, GPU != CPU

peter8777555 commented 3 years ago

So the build doesn't fail or produce bad results when not using chcp 437?

CHCP 437 or CHCP 950 always has the same as small error. I ignore the error window,this is not problem. It still can build and make 17 releases.

a1

I test 2 conditions for autobuild-ccpu-chk.cmd :

Keep CHCP 437 : Build : Passed and make 17 releases. Log : No buildchk.err Run NTVDMX64 : Test some DOS programs are OK.

Remove CHCP 437 : (use default 950 code page) Build : Passed and make 17 releases. Log : buildchk.err (1>NMAKE : fatal error U1077: 'cl16' : return code '0x2') Run NTVDMX64 : Test some DOS programs are OK.

Yes,you are right. If i remove CHCP 437,i got buildchk.err (1>NMAKE : fatal error U1077: 'cl16' : return code '0x2')

Both of them,Run NTVDMX64 : Test some DOS programs are OK. Should i keep CHCP 437 or remove CHCP 437 ?

peter8777555 commented 3 years ago

By the way, I run a DOS program and NTVDM.exe has high CPU usage.

Test.zip