leecher1337 / ntvdmx64

Run Microsoft Windows NTVDM (DOS) on 64bit Editions
780 stars 80 forks source link

Wont install because "launguage br is invalid" #178

Open Xanderplayz16 opened 2 years ago

Xanderplayz16 commented 2 years ago

uiou I am not installing WOW32 to it, so no windows 7 iso.

Xanderplayz16 commented 2 years ago

aaaa

leecher1337 commented 2 years ago

check logfiles in w\ directory before cleanup, there may be hints why build fails for you. w\minnt\base build.log build.wrn build*.err

Xanderplayz16 commented 2 years ago

Here is my log file because NMAKE is failing with the error message "Stop". Weird. buildchk.log

Xanderplayz16 commented 2 years ago

Found TONS of invalid include statements. Seems like required modules are missing.

Xanderplayz16 commented 2 years ago

Found the problem. Required modules are missing and NMAKE is failing with the error message "Stop".

leecher1337 commented 2 years ago

The missing include files are just warning and can be ignored. -1073741819 = 0xC0000005 = Access violation. Something crashes your nmake, as it seems. I never saw this before. If you are compiling on a machine where NTVDMx64 is already running and the loaders are installed, you can uninstall them to rule them out as a source for the crash, just to be sure.

Otherwise you may need to install a just-in-time-debugger to find out why nmake crashes on your machine.

Xanderplayz16 commented 2 years ago

I just looked up 0xC0000005 and found 2674EEE1-6C96-447C-8217-BD874FEB1B7C. Seems like there is something wrong with my PC. I’ll probably try to compile it on a VM.

leecher1337 commented 2 years ago

x64dbg is a good one (in this case, the x32dbg part is needed, as nmake is 32bit), some knowledge about debugging is required to find issues, though. Debugging problems via images of a debugger via github is a complicated task. When x32dbg is run as administrator, it can be set to be a JIT debugger that opens on crashing:

image

peter8777555 commented 2 years ago

ntvdmx64.zip : 04/27/2022 OS : Windows 7 X64 Chinese Edtion

autobuild-ccpu-chk.cmd It is OK and build 17 languages.

autobuild-haxm-chk.cmd I have the same problem. Language br is invaild , aborting

=====================================

ntvdmx64.zip : 06/21/2021 OS : Windows 7 X64 Chinese Edtion

autobuild-ccpu-chk.cmd It is OK and build 17 languages.

autobuild-haxm-chk.cmd It is OK and build 17 languages.

=====================================

By the way,

autobuild-ccpu-chk.cmd I have download de_windows_7_professional_with_sp1_x86_dvd_u_677093.iso

I have tw_windows_7_ultimate_with_sp1_x86_dvd_618764.iso Can i rename tw_windows_7_ultimate_with_sp1_x86_dvd_618764.iso to de_windows_7_professional_with_sp1_x86_dvd_u_677093.iso ?

leecher1337 commented 2 years ago

My guess is that the problem happens randomly, can you check? I tried bulding autobuild-haxm-chk.cmd on clean directory and it worked without issues. There is a known problem with the NTOSBE build system which sometimes crashes. Stephanos was never able to reproduce and fix it, neither was I.

Regarding your question about the ISO: Any X86 Win 7 ISO will work that contains the required files, so yes, you can try to rename it.

peter8777555 commented 2 years ago

My guess is that the problem happens randomly, can you check? I tried bulding autobuild-haxm-chk.cmd on clean directory and it worked without issues. There is a known problem with the NTOSBE build system which sometimes crashes. Stephanos was never able to reproduce and fix it, neither was I.

Regarding your question about the ISO: Any X86 Win 7 ISO will work that contains the required files, so yes, you can try to rename it.

Good news,i try again and everything is OK.

===================================== BEFORE (NG):

ntvdmx64.zip : 04/27/2022 NTOSBE-master.zip : 08/07/2018 OS : Windows 7 X64 Chinese Edtion de_windows_7_professional_with_sp1_x86_dvd_u_677093.iso

autobuild-ccpu-chk.cmd It is OK and build 17 languages.

autobuild-haxm-chk.cmd I have the same problem. Language br is invaild , aborting

AFTER (OK):

ntvdmx64.zip : 04/29/2022 NTOSBE-master.zip : 05/25/2020 OS : Windows 7 X64 Chinese Edtion I rename tw_windows_7_ultimate_with_sp1_x86_dvd_618764.iso to de_windows_7_professional_with_sp1_x86_dvd_u_677093.iso

autobuild-ccpu-chk.cmd It is OK and build 17 languages.

autobuild-haxm-chk.cmd It is OK and build 17 languages.

By the way,

It show TWO Error Dialogs,but it still can build 17 languages.

buildchk.err 2>NMAKE : fatal error U1077: 'exe2bin' : return code '0x1' 3>NMAKE : fatal error U1077: 'exe2bin' : return code '0x1'

Show Error Dialog


Unsupported 16-bit applications

The program or function "\??\C:\Windows\System32\exe2bin.exe" cannot be started or executed because it is incompatible with the 64-bit version of Windows. Check with your software vendor to see if a 64-bit compatible version of Windows is available.

leecher1337 commented 2 years ago

Hi,

exe2bin problem is due to the fact that NTOSBE has a 32bit version shipped with it, but in Windows\System32 directory, there is exe2bin from possibly previous NTVDMx64 installation. You can try the following, please report if it fixes your issue:

Replace the line

if [%TOOLS16%] equ [1]                     path %PATH%;%BETOOLS%\tools16 

in NTOSBE-master\ntenv.cmd with:

if [%TOOLS16%] equ [1]                     path %BETOOLS%\tools16;%PATH%

If you use autobuild, you may need to patch your local NTOSBE-master.zip archive accordingly as autobuild deletes NTOSBE after work and reextracts it from .zip If it works, I will add an NTOSBE-patch to NTVDMx64 so that it gets patched automatically.

peter8777555 commented 2 years ago

I will try path %BETOOLS%\tools16;%PATH% and feedback later.

I am sorry my poor English about NTOSBE question. I put NTOSBE-master.zip : 05/25/2020 in C:\NTVDMBLD Run autobuild-ccpu-chk.cmd Only and get build 17 languages. Run autobuild-haxm-chk.cmd Only and get build 17 languages.

By the way, If NTOSBE-master.zip does not exist,autobuild-ccpu-chk.cmd/autobuild-haxm-chk.cmd will auto download from internet, Do i need put NTOSBE-master.zip : 05/25/2020 in C:\NTVDMBLD ?

leecher1337 commented 2 years ago

For testing purpose, you would need to repack NTOSBE-master.zip with given changes and put it in build directory. If it is not there, autobuild will download it, but then it is unpatched, so you would not be able to test my proposal above. I'm pretty confident that it fixes the issues, but better try it on an affected system like yours first to verify.

As NTOSBE won't change anymore in future, as it got DMCAd from github und therefore only the archive.org mirror is used for download, it's normally pretty safe to keep it in your build directory in order to avoid additional download times on building.

peter8777555 commented 2 years ago

You mean,autobuild auto download NTOSBE-master.zip and i do NOT delete it.

leecher1337 commented 2 years ago

Correct, you can normally keep it,

peter8777555 commented 2 years ago

I will try path %BETOOLS%\tools16;%PATH% and feedback later.

It fixes my issue.

autobuild-ccpu-chk.cmd It is OK and no any error.

autobuild-haxm-chk.cmd It is OK and no any error.

dominicraf commented 2 years ago

I have also started experiencing a problem with 'language usa is invalid' (as I try to build for English only), here is the image building from command prompt in windows terminal: Screenshot 2022-05-23 141152 I made the suggested fix above to NTOSBE-master.zip\ntenv.cmd but it has not helped.

leecher1337 commented 2 years ago

check logfiles in w\ directory before cleanup, there may be hints why build fails for you. w\minnt\base build.log build.wrn build*.err

dominicraf commented 2 years ago

the only log file with info is w\minnt\base\buildfre.log, it has:

BUILD: Compile and Link for X86
BUILD: Computing Include file dependencies:
BUILD: Examining c:\ntvdmbld\w\minnt\base directory tree for files to compile.
BUILD: Compile and Link for X86
BUILD: Computing Include file dependencies:
BUILD: Examining c:\ntvdmbld\w\minnt\base directory tree for files to compile.
BUILD: Compile and Link for X86
BUILD: Computing Include file dependencies:
BUILD: Examining c:\ntvdmbld\w\minnt\base directory tree for files to compile.
BUILD: Compile and Link for X86
BUILD: Computing Include file dependencies:
BUILD: published found in dirs, is not a subdirectory of c:\ntvdmbld\w\minnt\base
BUILD: Examining c:\ntvdmbld\w\minnt\base directory tree for files to compile.
BUILD: dpm found in mvdm\dirs, is not a subdirectory of c:\ntvdmbld\w\minnt\base\mvdm
BUILD: c:\ntvdmbld\w\minnt\base\mvdm\dpmi32\sources. unexpected in directory with DIRS file
BUILD: Ignoring c:\ntvdmbld\w\minnt\base\mvdm\dpmi32\sources.
BUILD: c:\ntvdmbld\w\minnt\base\mvdm\softpc.new\base\video\daytona: Ignoring invalid directory prefix in X86_SOURCES= entry: ..\i386\ggdcdraw.asm
Building generated files in c:\ntvdmbld\w\minnt\base\mvdm\inc ********************
'NMAKE.EXE -c BUILDMSG=Stop. NTTEST= UMTEST= NOLINK=1 PASS0ONLY=1 BUILD_PHASE= X86=1'
1>BUILDMSG: Processing c:\ntvdmbld\w\minnt\base\mvdm\inc
1>

BUILD: NMAKE.EXE failed - rc = -1073741819

Does that help?

dominicraf commented 2 years ago

If I just run autobuild-ccpu-fre.cmd without specifying a langauge I have the same issue although the failing message at the end is (as OP reported) 'Language br is invalid, aborting'.

leecher1337 commented 2 years ago

Normally, you should have a buildchk.err containing build process errors. But you can attach your full buildchk.log here, maybe it contains some useful information.

dominicraf commented 2 years ago

Thanks for your help!

I uninstalled NTVDMx64, installed Windows 11 update (KB5014019) and rebooted. Then I was able to rebuild NTVDMx64 without apparent error.

The subsequent install produced a strange message (see below) but it then proceeded to completion and after (another) reboot NTVDMx64 works fine:

---------------------------------------------
Installing, please wait...
---------------------------------------------
Please check for completion-message from installer in taskbar.
[*] Preparing correct loader
        1 file(s) copied.
        1 file(s) copied.
[*] Trying to download necessary debug symbols
Detected 0 byte symbol file: C:\WINDOWS\Symbols\appinfo.pdb\0C369099E1D5BA2EEE8F
1DBEF6FDBE5A1\appinfo.pdb, removing
SymFindFileInPath(C:\WINDOWS\system32\appinfo.dll, 1, 0) failed: 2
kllkradio commented 8 months ago

I had a similar problem with the latest version autobuild and the latest updated version of Windows 11 (22H2). Once I acquired a version of nt5src.7z with the proper .cab files within it, I was able to get the most recent version of autobuild to complete its routine once I uninstalled NTVDMx64, rebooted my computer, and disabled the real-time virus protection. I am running running Windows 11 22H2 with all of the most recent updates.