Hi guys.
Thanks for the response, replying to the various points together.
> 0standard input
> basically you are telling the STdiN device 0, that is no longer standard
input.
Yes, which is why in my original message I said:
>> Using 1 or 81h gives the same result.
ie I tried two ways
> 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
> mov ah, 044h
> mov al, 01h
> mov bx, 0
> ;mov dx, 081h
> mov dx, 0h
> int 021h
> mov ah, 04ch
> int 021h
Looking at this again, I think I see what your problem might be. You have
commented out the "mov dx, 081h" which makes me think you are trying to do
something with a hard drive (which
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
No problem, beergarden at "deergarden", german, Hirschgarten was fine.--Diese Nachricht wurde von meinem Android Mobiltelefon mit mail.com Mail gesendet.Am 30.07.23, 20:16 schrieb Jim Hall via Freedos-devel :
> On Sun, Jul 30, 2023 at 11:03 AM Gregory Pietsch via Freedos-devel
> wrote:
> On Sun, Jul 30, 2023 at 11:03 AM Gregory Pietsch via Freedos-devel
> wrote:
> >
> > Wasn't a virtual get-together supposed to happen about now? -- Gregory
On Sun, Jul 30, 2023 at 11:06 AM Rugxulo via Freedos-devel
wrote:
>
> Maybe Jim is still under the weather?
>
I'm so sorry I missed the
Hi Rugxulo,
[3] Windows 3.0 started to catch on. That meant HIMEM.SYS and XMS as
standard; LIM-spec EMS started to fade. Apps like 1-2-3 r3 used DOS
extenders routinely. Memory management really got important but
everyone was buying 386SXs so you could sell them QEMM even if they
didn't want
Hi,
On Fri, Jul 28, 2023 at 11:51 AM Liam Proven via Freedos-devel
wrote:
>
> For me, when I worked with, supplied and supported DOS in the late
> 1980s and early 1990s, the chronology went like this:
>
> [2] DOS 4 came along. It was a memory hog, but it had big-disk support
> (over 32MB) and
Hi,
On Sun, Jul 30, 2023 at 11:03 AM Gregory Pietsch via Freedos-devel
wrote:
>
> Wasn't a virtual get-together supposed to happen about now? -- Gregory
Maybe Jim is still under the weather?
___
Freedos-devel mailing list
Wasn't a virtual get-together supposed to happen about now? -- Gregory___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Hi Paul,
I can reproduce this on T2307. It is running fine on a test image with
self-build kernel (Git master, IA16-GCC) and alternative command shell
(SvarCOM). The problem also does not occur under T2307 with SvarCOM as a shell.
But I am not yet sure if it is the kernel or FreeCOM to blame.
14 matches
Mail list logo
