Due to various complaints of technical issues and bugs that all have the
same common element of Broadcom virtualization technology ("VMware"), and
with changes to the hypervisor that have rendered the virtualized
environment somewhat hostile to the DOS ecosystem, I recommend we just
flat-out state
Hallo Herr Bernd Böckmann via Freedos-devel,
am Donnerstag, 20. Februar 2025 um 00:11 schrieben Sie:
> Hello Jeremy,
> On 20.02.2025 00:03, perditi...@gmail.com wrote:
>> Thanks for looking into it. I will have a look at Watcom build and > see
>> why it's not patching header.
> Have a look
Yes, this is intended. The FreeDOS package version is updated to 0.86a, while
the binaries are still 0.86, as these are patched 0.86 executables, not newly
built ones. Also, there is no official new FreeCOM release yet, so I cannot
randomly increase the version number.
Bernd
> Am 21.02.2025 um
Le ven., 21 févr. 2025 09:42:59 -0500 Bernd Böckmann via Freedos-devel
wrote
>
> > Am 21.02.2025 um 11:24 schrieb Bernd Böckmann bernd-free...@boeckmann.io>:
> >
> > I will update the FreeDOS package to include a patched v0.86 command.com.
>
> Done via https://gitlab.com/FreeD
> Am 21.02.2025 um 11:24 schrieb Bernd Böckmann :
>
> I will update the FreeDOS package to include a patched v0.86 command.com.
Done via https://gitlab.com/FreeDOS/base/freecom/-/commit/eb332c2c
Bernd
___
Freedos-devel mailing list
Freedos-devel@li
Hallo Herr Eric Auer via Freedos-devel,
am Freitag, 21. Februar 2025 um 13:20 schrieben Sie:
> Hi Tom,
>>> As you already say, XMS SWAP in FreeCOM already makes DOS
>>> memory footprint very small while apps run,
>> Which is true - because XMS_SWAP
>>> little need to load it high into preciou
Hi Tom,
As you already say, XMS SWAP in FreeCOM already makes DOS
memory footprint very small while apps run,
Which is true - because XMS_SWAP
little need to load it high into precious UMB, where it
would require quite a bit of memory while no app runs!
Which is nonsense - because XMS
Hello Paul,
I appreciate your effort trying to fix it. Thanks for sharing your results
here. I will update the FreeDOS package to include a patched v0.86 command.com.
Regarding the IFDEFS, these are flawed by themselves, as they test for the
compiler used to build ptchsize, and not for the comp
Le ven., 21 févr. 2025 04:30:54 -0500 tom ehlert via Freedos-devel a
écrit
> > So my proposition is to load DOS low, if XMS_SWAP is available.
>
> My suggestion is to learn your "101 DOS memory allocation" and "202 DOS
> advanced memory juggling" before
> coming up with propo
Once the following patch is applied: (repeating for perditionc)
> C:\Users\Paul\freecom\freecom4>type
> 0001-patch-for-all-compilers-avoiding-out-of-memory-error.patch
> From 9b4e0fa43cb1c649ccd3f5ed23cef46278148c65 Mon Sep 17 00:00:00 2001
> From: Paul Dufresne dufres...@zoho.com>
> Date:
Hallo Herr Paul Dufresne via Freedos-devel,
am Donnerstag, 20. Februar 2025 um 11:34 schrieben Sie:
> I realize I tended to wrongly think that HIGH was in EMS or XMS regions (over
> 1 Mb).
> But now I kind of realize that HIGH is really above 640 kb, while still lower
> than 1 MB (default addre
Le Wed, 19 Feb 2025 18:11:19 -0500 Bernd Böckmann via Freedos-devel a
écrit
> Hello Jeremy,
>
> On 20.02.2025 00:03, perditi...@gmail.com wrote:
>
> > Thanks for looking into it. I will have a look at Watcom build and
> > see why it's not patching header.
>
> Have a look
Hi Eric,
> Hi Paul!
Paul as a newbie is excused for his ignorance, Eric as a 'senior' is not.
> As you already say, XMS SWAP in FreeCOM already makes DOS
> memory footprint very small while apps run,
Which is true - because XMS_SWAP
> so there is
> little need to load it high into precious UMB
13 matches
Mail list logo
