Casteele M.

correct; that was the case, but I can no longer reliably reproduce the oproblem, thus just cllose this as "resolved". more info: I realized I also had MagicSplat Tcl+Tk 8.9..* installed (I saw it in my error/install logs while trying to get my exact window and Tcl+Tk versions.)

It might also help mentioning, I do not have any problems if I execute "tclsh" or "wish" from the "cmd prompt", then "source" my files. It only gives me problems when I try to execute a *.tclapp or a *.tkapp from the command line (using the command line assoc's set up by MagicSplat. I checked them as well, and see nothing unusual or wrong with them, either.

from the command line: ver Microsoft Windows [Version 10.0.26120.1542] tclsh % info patchlevel 8.6.15

from the command line: ver Microsoft Windows [Version 10.0.26120.1542] tclsh % info patchlevel 8.6.15 9.

from the command line: ver Microsoft Windows [Version 10.0.26120.1542] tclsh % info patchlevel 8.6.15 9.

Please understand, I am disabled, and struck in a nursing home, so it is very difficult for me to find and provide the requested details. What I have done in the past is write a simple Tcl script to open potential (.tcl, .tclapp, .tk, and .tkapp) problem files, read them in binary mode to check the first 2, 3 or 4 bytes for a BOM: -- UTF-8 :: 0xEF 0xBB 0xBF -- UTF-16 LE :: 0xFF 0xFE -- UTF-16 BE :: 0xFE 0xFF -- UTF-32 LE :: 0xFF 0xFE 0x00 0x00 -- UTF-32 BE :: 0x00 0x00 0xFE 0xFF Unfortunately, I...

My suggestion is to ensure all the distro files are plain old 7-nit ASCII files, using "\uXXXX" style escapes where unicode chars are absolutely needed. (I personally cannot think of any cases where any kind of 8-bit character encoding is absolutely needed in the core distro.) I caught this issue because my text editor (Edit Pad Pro 7) is somewhat Unicode capacle and aware, and the error popup (on Windows) is something like: "invalid command name: \" ...\" while executing ...", which happens to...

Also, note that the BOM is NOT in any of the files I created/my source code: my editor has a toolbar that allows my to add/strip any BOM at will, and I have made certain that none of my source files have no BOM. It seem that at least one file in the MagicSplat distro is the problem, as I have a standard (plaijn ASCII) header in all my files, and the tracing I could do, show the problem occurs long before my file is even sourced in Tcl/Tk. As best as I can figure out, the MagicSplat Tcl/Tkinitialization...