Diagnostic for starting a 64-bit application in 32-bit TCC

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Status
Not open for further replies.
Feb 4, 2011
3
0
#1
If you try and start a 64-bit executable under Windows command.com, it tells you:

Code:
c:\testlab4>pfddfc.exe
This version of C:\testlab4\PFDDFC.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher.
If you do the same under TCC, it merely says:

Code:
[c:\testlab4]pfddfc.exe
4DOS/NT:  "C:\TESTLAB4\PFDDFC.EXE"
It would be helpful if TCC gave more complete diagnostics, like command.com, because it may not be immediately obvious that it is not running because of that issue.

Suppose you are only running TCC and you try and run the executable. All TCC does is echo the name of the executable. The average user goes "So? Yes, thats the exe, I know that, but why dont you execute it like I asked?" I had to switch to command.exe to find out why it wasnt running.
 

rconn

Administrator
Staff member
May 14, 2008
10,292
90
#2
Diagnostic for starting 64-bit application in 32-bit TCC

> If you do the same under TCC, it merely says:
>
> Code:
> ---------
> [c:\testlab4\pfddfc.exe
> 4DOS/NT: "C:\TESTLAB4\PFDDFC.EXE"
> ---------
> It would be helpful if TCC gave more complete diagnostics, like
> command.com, because it may not be immediately obvious that it is
> not running because of that issue.
I don't know what you're running there, but it isn't TCC/LE -- there isn't
any "4DOS/NT" string in TCC/LE (or TCC), and hasn't been for many years.

And command.com hasn't existed in Windows since Windows ME (though there is
a fake command.com in XP that simply passes everything you enter to
CMD.EXE).

Rex Conn
JP Software
 
Feb 4, 2011
3
0
#3
Re: Diagnostic for starting 64-bit application in 32-bit TCC

I don't know what you're running there, but it isn't TCC/LE -- there isn't
any "4DOS/NT" string in TCC/LE (or TCC), and hasn't been for many years.

And command.com hasn't existed in Windows since Windows ME (though there is
a fake command.com in XP that simply passes everything you enter to
CMD.EXE).

Rex Conn
JP Software
*blush* *gulp* I was accidentally running an ancient version of 4NT.exe. I see that more recent TCC versions do say this:

[C:\testlab4\]pfddfc
TCC: (Sys) This version of C:\testlab4\pfddfc.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher.

My apologies, Rex, you are quite correct. I did not even spot this.
 
Status
Not open for further replies.