> On Sun, Jul 30, 2023 at 3:38 PM Bret Johnson <bretj...@juno.com> wrote: > > > > Those extra "spaces" may not really be spaces at all -- they may > > actually be ASCII 0 or ASCII 255, which look like a regular space (ASCII > > 32) on the screen even though they aren't. I've ran into similar > > issues at various times that have caused me all kinds of grief. There > > are also some DOS Code Pages where other characters (besides 0, 32, and > > 255) also are blank (they look like a normal space when they aren't). [..]
On Sun, Jul 30, 2023 at 3:55 PM Jim Hall <jh...@freedos.org> wrote: > > Possibly. I'll add that the AMB directory I tested *already existed* > on the filesystem before I ran PC Tools. All I did in PC Tools was > navigate to my AMB directory, view the AMB.TXT file that was already > there, then exit back to DOS. That was all I needed to reproduce the > problem. I just booted FreeDOS in QEMU using the '-display curses' option, so QEMU runs in plain text mode in my terminal. That lets me copy/paste the prompt from Linux into another file. And it looks like spaces when I investigate the file: $ hexdump -b /tmp/f 0000000 103 072 134 124 105 115 120 134 101 115 102 040 040 040 040 040 0000010 076 012 0000012 The prompt really is AMB followed by 5 spaces (\040) C:\TEMP\AMB > _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
