NoClose is not called for CMD files

Flint · Post by *Flint » 2011-10-22, 20:08 UTC

There was an old report finally moved into "won't fix" area because, as Ghisler said, PIF file (which NOCLOSE.PIF was) were not suited for cmd.exe.

However, now TC8 has its own implementation of noclose.exe, so I think supporting CMD files should not be a problem anymore.

PS: I'm not sure, maybe it should have been created in the "Suggestions" section, but the current behaviour looks to me like bug rather than unimplemented feature.

karlchen · Post by *karlchen » 2011-10-23, 11:34 UTC

Issue reproduced using Total Commander 8.0ß6 32-bit and 64-bit.
Agree with Flint's point of view and request.

Karl

Post by *ghisler(Author) » 2011-10-24, 14:07 UTC

I agree, I will add support for .cmd files now.

karlchen · Post by *karlchen » 2011-10-28, 11:11 UTC

Hello, Christian.

NOCLOSE.EXE and NOCLOSE64.EXE are now called when launching .CMD script files.

Tested on:
+ Server 2008 R2
+ Total Commander 8.0ß7 32-bit
+ Total Commander 8.0ß7 64-bit

Thanks and cheers,
Karl

Flint · Post by *Flint » 2011-10-28, 11:37 UTC

Confirm fixed in 8.0β7.

Post by *ghisler(Author) » 2011-10-30, 14:44 UTC

Thanks!