> On Sun, Jul 30, 2023 at 3:38 PM Bret Johnson 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
On Sun, Jul 30, 2023 at 3:38 PM Bret Johnson 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
On Sun, 30 Jul 2023, Jim Hall via Freedos-devel wrote:
*Aside: I thought QBASIC would only run on MS-DOS, but I checked the
screenshot the user sent me; it's really MS-DOS QBASIC, not QuickBASIC
or something else. And the series of screenshots they sent indicated
QBASIC was running on FreeDOS.
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
A user emailed me with what they thought was a bug, but to me it looks
like everything is okay. Ironically, I think it's QBASIC that has the
issue.
Here's the "bug" as described to me:
The user ran PC Tools on FreeDOS and navigated around. They exited PC
Tools into a directory (BAS_DAT) that
