Hi Jim,
> On Oct 1, 2023, at 7:05 PM, Jim Hall via Freedos-user
> wrote:
>
> Eric wrote:
>> You can also find updates for JEMM and HIMEMX on Japheth's GitHub "Baron von
>> Riedesel", even his HIMEMSX to use more than 4 GB RAM :-)
>
> Mercury Thirteen wrote:
> [..]
>> Looks like I fell
I think the monthly online get-together is today.
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Hi ecm,
> On Aug 28, 2023, at 3:50 PM, C. Masloch via Freedos-user
> wrote:
>
> On at 2023-08-26 11:30 -0500 , Jim Hall via Freedos-user wrote:
>> Great news, thanks! I've been following the feature request discussion
>> on the tracker, so it's great to see the new version with the cool new
>>
Hi Eric,
> On Jul 18, 2023, at 3:31 PM, Eric Auer via Freedos-user
> wrote:
>
>
> Hi!
>
> Today I have gotten more than 60 notifications about packet updates,
> NONE of which mentioned why the affected package got updated.
First, sorry about all the notification messages.
Earlier today,
> On Jul 16, 2023, at 10:21 AM, Jay F. Shachter via Freedos-user
> wrote:
> [..]
> If the answer to the first question is Yes, then I can continue this
> narrative, otherwise the remainder of this posting is moot. I copied
> FD13FULL.img to a USB stick, stuck it into the above-described
>
Hi,
> On Jul 20, 2023, at 5:47 PM, Karen Lewellen via Freedos-user
> wrote:
>
> Hi folks,
> did the obvious and visited the readme for the download section of freedos.
> While there is indeed a floppy only install, I understand one should over
> ride the 286 assumption with a switch to
Hi Eric,
First…
The Standard Install Media (CD, USB, LiveCD, etc) require a 386 or better.
There are several reasons I have mentioned before why those require a 386. But
for those who may have missed or forgotten why those require a 386, these are
the primary reasons. USB did not exist on
> On Aug 6, 2023, at 5:48 PM, Mateusz Viste via Freedos-user
> wrote:
>
> On 8/6/23 23:34, Ralf Quint via Freedos-user wrote:
>> DOS is using *text *mode, you just can't select a*graphics *mode and expect
>> to get text output in that mode.
>
> BIOS text output functions still work in most
First…
There seems to be a general misunderstanding that DOS only supports 80x25
columns. While it is possible that an extremely lazy programmer would hard code
for that resolution, most did not. Even back in the early days the display
could be in 40x25, 80x43, 80x50 and numerous other text
> On Aug 6, 2023, at 5:25 PM, EdzUp via Freedos-user
> wrote:
>
> I was testing in virtualbox.
Like PC speaker emulation…. I don’t think provides any support for higher
resolution text modes.
___
Freedos-user mailing list
Hi,
>
> To fake shifts, one can just modify the flags at 40:17 and 18.
> It will not update the keyboard LEDs, but that is acceptable.
> The BIOS itself uses 40:96 and 97 to track its own status.
>
It has been a very long time. But, if I recall correctly, I’m fairly sure you
can
Well,
If I were making something to support typing those extra/alternate characters,
the driver would probably behave like this…
Normal typing and continuous key press would behave as normal. This includes
key repeating at the set typographic rate.
I would implement some of the techniques
Hi Ralf,
> On Feb 9, 2024, at 2:16 PM, Ralf Quint via Freedos-user
> wrote:
>
> Are you guys trying to have DOS behave like macOS?
>
> Beside that any trickery with the keyboard controller would only work on an
> AT keyboard, where the controller chip is actually on the motherboard of the
During the DOS years, I used XTree a lot for moving things and general file
management.
During the early DOS years, I used Professional Write. Eventually, I moved on
to the Lotus Suite.
But as with the platforms that came before, I spent most of my time in DOS
writing code. Mainly that
Hi,
> On Dec 27, 2023, at 1:04 PM, andrew fabbro via Freedos-user
> wrote:
>
> Greetings!
>
> I'm a bit perplexed trying to get networking working for FreeDOS 1.3 on QEMU.
> My physical host is an M1 Mac (Apple Silicon).
>
> FreeDOS installs and boots fine, but I get this message:
>
>
Hi,
> On Jan 30, 2024, at 7:00 AM, Jürgen Wondzinski via Freedos-user
> wrote:
>
> Hi all,
>
> I'm currently facing some users which seem to have a bad BIOS battery and
> therefor aren't using the current date.
> Those users aren't even noticing that wrong date on their printed invoices of
> On Jan 30, 2024, at 8:01 AM, Jürgen Wondzinski via Freedos-user
> wrote:
>
> Hi Jerome,
>
> Perfect! Thanks for the pointer to that VSTR utility!
>
> wOOdy
Your welcome
:-)
>
> Von: Jerome Shidel via Freedos-user <mailto:freedos-user@lists.source
Hi,
> On May 9, 2024, at 3:53 PM, Eric Auer via Freedos-user
> wrote:
>
>
> Hi!
>> Initially I tried Bochs, but found Bochs either cannot go full screen
>> using SDL2, or I just haven't found the magical incantation...
>
> A quick google says "try alt-enter" (to go full screen). In 2011,
Hi
> On May 9, 2024, at 6:31 PM, Eric Auer via Freedos-user
> wrote:
>
>
> Hi!
>
> Turns out I only had some 2020 Bochs and no boot "disk"
> for it, so I could not easily test any hotkeys :-o But:
>
>>> What if the DOS distro installer can be improved, so it no
>>> longer matters which
Personally, I have zero interest in any on the versions of DOS that Microsoft
has open sourced.
Versions 1.25, 2.0 and 4.0. Really? Those aren’t even the good versions of
MS-DOS. I think if they were serious, they would release 3.3, 5.0 and 6.22. It
feels like they are only placating to the
Hi,
Since you said, the source code is about 640MB and is on an old XP machine….
Why not just boot the FreeDOS Live CD, enable LFN support by installing the
driver to the Live Environment and running it.
Then install the compiler to the Live Environment.
Then just compile the source directly
Hi,
> On Apr 6, 2024, at 8:40 PM, Norby Droid via Freedos-user
> wrote:
>
> One issue I find alot when tryin to install FreeDos is that it would go most
> of the way through the install then without any reason and no explanation as
> to why, it just stops and says there is a problem so
Hi,On Apr 7, 2024, at 6:46 PM, dnashmcp--- via Freedos-user wrote:I have a Thinkpad X301 (I think a perfect fit for FreeDOS). I was able to install to C: from the FD-13LIVE CD and it loads a driver for the CDROM as ELTORITO, but when I boot after installation it fails on the first attempt to
Hi Paul,
Just a side note about installing using the FullUSB.
One of my DOS test machines is an Acer One netbook with a 1Ghz Atom processor
and an ancient 30Gb SSD. This machine has no CD/DVD drive. It does boot from
the FullUSB when written to a flash drive. It takes about 5 minutes from
> On Jun 4, 2024, at 7:33 PM, Brandon Taylor via Freedos-user
> wrote:
>
> I've tried several times lately to run fdnpkg update, but the command hangs
> repeatedly at Loading
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/latest/base...
> ` and no progress is
25 matches
Mail list logo