On Mon, 2025-05-12 at 16:42 +0200, tom ehlert via Freedos-devel wrote:
> Hallo Herr Eric Auer via Freedos-devel,
>
> am Montag, 12. Mai 2025 um 02:03 schrieben Sie:
>
>
> > Hi!
>
> > > i posted the error and a screen shot of it in the kernel issues
> > > thing
> > > https://github.com/FDOS/kern
Hi!
You will need a driver which knows your exact chipset for UMB,
unless you have a very verbose CMOS BIOS setup giving you some
fine-grained control over the configuration at boot already.
In your other mail, you show some MEM output which mentions
a driver LTEMM and FDXMS286, so I guess LTE
On Mon, 2025-05-12 at 02:03 +0200, Eric Auer via Freedos-devel wrote:
>
> Hi!
>
> > i posted the error and a screen shot of it in the kernel issues
> > thing
> > https://github.com/FDOS/kernel/issues/205
>
> Let me type this screenshot message over and comment on it:
>
> Immediately after loadi
FWIW:
doskey keeps track through its own internal buffers, and the MS-DOS
command.com calls out to doskey through a documented interface (falling
back onto int21/0Ah if that doesn't work). That way, aliases persist from
instance to instance because it's handled by a separate TSR app.
-uso.
Hallo Herr Eric Auer via Freedos-devel,
am Montag, 12. Mai 2025 um 02:03 schrieben Sie:
> Hi!
>> i posted the error and a screen shot of it in the kernel issues thing
>> https://github.com/FDOS/kernel/issues/205
> Let me type this screenshot message over and comment on it:
> Immediately after
On Mon, May 12, 2025, 6:58 AM Danilo Pecher via Freedos-devel
wrote:
>
> That's normal. If you start a new shell, the aliases are a clean
> sheet. Unlike Unix shells, FreeCOM doesn't have startup files (perhaps
> an idea for the future).
AUTOEXEC.BAT is the startup file for command.com (such as
That's normal. If you start a new shell, the aliases are a clean
sheet. Unlike Unix shells, FreeCOM doesn't have startup files (perhaps
an idea for the future).
On Mon, 12 May 2025 at 13:29, Wilhelm Spiegl via Freedos-devel
wrote:
>
> Hi,
> when running FDT2505 (and earlier) I noticed the followi
This is as expected. The aliases are not kept in the environment variables
but in separate memory.
If you start another FreeCOM sub-shell (such as a sub-shell executed from a
file manager or programming IDE) the environment is inherited, but the
aliases are not.
On Mon, May 12, 2025, 6:28 AM Wilh
Hi,
when running FDT2505 (and earlier) I noticed the following:
FDT has an environment with set xy=blabla etc. and it also uses aliases, e.g. alias reboot=fdapm warmboot.
Usually this works fine.
But when I run "command", and start a new instance with this, e.g. to see the version number of com
