Take Command / TCMD/LE / TCC/LE 11.0 build 44 uploaded

[rconn]

I've uploaded build 44 to the web and ftp sites.

Build 44:
---------

TCC - fixed a problem when invoking help from a stand-alone TCC console window.

TCC - fixed a problem with not displaying Windows loader popup errors.

Build 43:
---------
TCMD - fixed a problem when loading a custom console color palette from the registry that doesn't define all 16 colors.

Fixed a Windows IPC bug that caused 32-bit versions of TCC to potentially hang 64-bit versions of Take Command.

Build 42:
---------
TCMD - now detects custom console palettes when attaching an existing console window.

Build 41:
---------
ASSOC / FTYPE - fixed a harmless (Windows) non-error message when attempting to delete a nonexistent entry.

DIRHISTORY / HISTORY - fixed a problem with reading Unicode files.

Minor help updates.

Build 40:
---------
@CRC32, @MD5 - fixed a crash if you specified 'f' or 's' and didn't include
the required argument. (Note that both these functions are seriously obsolete; you should be using the SHA functions!)

SENDMAIL - fix for a third-party dll bug that broke multiple /H arguments.

TYPE / HEAD / TAIL - added a check for redirecting Unicode input through CON:.

Minor help file updates.

 

[dim]

On 2010-03-15 15:48, rconn wrote:

> I've uploaded build 44 to the web and ftp sites.
>
> Build 44:
> ---------
>
> TCC - fixed a problem when invoking help from a stand-alone TCC console window.
>
> TCC - fixed a problem with not displaying Windows loader popup errors.

Still not all loader popup errors are shown, it seems. If one of an
application's DLLs is missing, entry points are not found, and so on,
the popups work.

However, you do not get a popup, when you start a DOS executable under
x64 Windows. (This still happens to me regularly, because I dual boot
32 and 64 bit versions of Windows, and I have DOS and 16-bit Windows
apps lying around everywhere. :)

With cmd.exe, in such a case, you first get a message box "The program
or feature "<path_to_executable>" cannot start or run due to
incompatibility with 64-bit versions of Windows"; when you click OK, you
get a message at the prompt "The image file <path_to_executable> is
valid, but is for a machine type other than the current machine".

TCC only shows the latter message. Which arguments are you now using
for SetErrorMode(), just 0?

 

[rconn]

> Still not all loader popup errors are shown, it seems. If one of an
> application's DLLs is missing, entry points are not found, and so on,
> the popups work.
>
> However, you do not get a popup, when you start a DOS executable under
> x64 Windows. (This still happens to me regularly, because I dual boot
> 32 and 64 bit versions of Windows, and I have DOS and 16-bit Windows
> apps lying around everywhere. :)
>
> With cmd.exe, in such a case, you first get a message box "The program
> or feature "<path_to_executable>" cannot start or run due to
> incompatibility with 64-bit versions of Windows"; when you click OK,
> you
> get a message at the prompt "The image file <path_to_executable> is
> valid, but is for a machine type other than the current machine".
>
> TCC only shows the latter message. Which arguments are you now using
> for SetErrorMode(), just 0?

I'm not using SetErrorMode, I'm passing the flag to CreateProcess to tell it
to use the default error mode.

Rex Conn
JP Software

 

[rconn]

> With cmd.exe, in such a case, you first get a message box "The program
> or feature "<path_to_executable>" cannot start or run due to
> incompatibility with 64-bit versions of Windows"; when you click OK,
> you
> get a message at the prompt "The image file <path_to_executable> is
> valid, but is for a machine type other than the current machine".

But ... why would you *want* two message boxes??

 

[dim]

On 2010-03-17 02:33, rconn wrote:

> ---Quote---
>> With cmd.exe, in such a case, you first get a message box "The program
>> or feature "<path_to_executable>" cannot start or run due to
>> incompatibility with 64-bit versions of Windows"; when you click OK,
>> you
>> get a message at the prompt "The image file<path_to_executable> is
>> valid, but is for a machine type other than the current machine".
> ---End Quote---
> But ... why would you *want* two message boxes??

It is one message box, and one message box at the prompt. I just wanted
to point out the difference between cmd.exe's handling and tcc.exe's. I
remember that in some earlier version of tcc the handling was the same,
so somewhere between then and now, it has changed. :)