Well, I did not say that the change was deliberate but it may have been caused by another modification. There is no magic here. Just explain me why TCC 16 works and TCC 19 doesn't? CHCP command returns 850 in both versions. And I am using the same OS, Win 7 Pro x64 French. I also tested TCC 19...

Hi Rex, NTFS description is not compatible with FAT32 which I still use for compatibility. I believe XnView and a few other applications and batches won't work either. What about my NAS (Synology)? I have many, many files with classic description, even if it should be easy to convert then, I am...

Thanks for all your suggestions. I admit I did not have enough time to test them but what troubles me is that TCC worked up to a point (for instance it was OK at v16) then proceeded to screw up from a given release, don't know which one. Similar situation appeared somewhere in v11 if I remember...

Mmmm... Let me some time to analyze your answers and make some tests! Thanks anyway! :smile: However I jumped from TCC 16 (with which I was -- almost -- happy) to TCC 19, without making any change to the system. So something has been changed meanwhile, don't know exactly at what version number...

Hi Rex, Coming back from 2010! There is still a problem with French accented characters (éèàôöùüû...) in file descriptions. The issue is similar with the one I explained here: https://jpsoft.com/forums/threads/describe-under-tcc-11-doesnt-work-with-diacritics.1731/ (this was for TCC 11). Here...

Re: and similar http download was still build 50 one hour ago, but ftp is already build 51. Seems to work also me also. Thanks Rex. :)

Re: and similar Hi, You're right, the localization was set on Automatic, i.e. comma for decimal separator in France. Strange enough, even things like %@eval[pi] shows weird results but without error message. Until this issue is fixed, I'll use setdos /g., in my batches only for calculations...

Hello, Unless I'm wrong, the following issue has not been reported yet. Did I mistyped something? D:\X>echo %@eval[sin(0)] Eval warning: '_set_string', Non-digit char found in parse Eval warning: Text = Eval warning: 0.000000000000000000000000000000, 0 D:\X>echo %@eval[cos(0)]...

Hi Rex, I'm terribly sorry but I didn't read to the forum since February and didn't answer to you last post. Anyway, the problem disappeared since build 46, so I'm happy! Best, Georges

Thanks for that! I was waiting for it since I bought TCC 11. Regards, Esteban <o><o><o> </o></o></o>

Hello Rex, As you didn't answer yet, should I understand you don't intend to correct that bug? On Feb. 15th, you wrote "those people are also not buying new versions of Take Command, so I don't base development decisions on them!", speaking about me I suppose. Just let me point out that I DID...

Cool boys! As I am a reasonable guy, of course I use NTFS for all my large capacity media. But Steve is right when he says that FAT format is still useful, even for people who just bought TCC 11 (at least me). For example I made some bootable tools under 4DOS for some old computers, which were...

OK, but what about the compatibility with old descriptions? I've got thousands of files described in ASCII since 4DOS v3.0 (which I still use for bootable tools), no way to transcribe them all! What's more, NTFS descriptions are fundamentally not compatible with FAT12/16/32 partitions...

Hello Rex, Thanks for answering. I am using Lucida Console, which is not unicode to my knowledge. Anyway, opening the descript.ion file in notepad shows the same question marks. I'm afraid there is something other... Esteban

Hello, All is said in the title! I am talking about Take Command 11.0 build 40 under Win XP French. When you enter diacritics (i.e. accentuated characters) from foreign languages (e.g. French éèêëàâùîïôöç...) using DESCRIBE, they are generally converted into question marks. For instance...