Hi!
CSMWrap is a cool little hack that brings back the good old PC BIOS on
those fancy-pants UEFI-only systems. It utilises the CSM
(Compatibility Support Module) and VESA VBIOS from SeaBIOS project to
emulate a legacy BIOS environment.
https://github.com/FlyGoat/csmwrap
I read the comments
On Thu, 29 May 2025, Aitor Santamaría via Freedos-devel wrote:
Even more, I have to admit that when I wrote KEYB long time ago I used the
same exit codes as MS-DOS KEYB (plus some extended codes that MS-DOS KEYB
did not have), but it was so long ago that I can't even remember where I
took the li
forget ai. yesterday I asked meta ai how far a snail can walk in her life, and i got a result of in about 15 km in her 5 till 7 years of life. in the same response meta ai told me that the snail can reach a distance of 50 till 250 m per hour. when i asked her if 250 m per hour is correct, ai correc
forget ai. yesterday I asked meta ai how far a snail can walk in her life, and i got a result of in about 15 km in her 5 till 7 years of life. in the same response meta ai told me that the snail can reach a distance of 50 till 250 m per hour. when i asked her if 250 m per hour is correct, ai correc
Even more, I have to admit that when I wrote KEYB long time ago I used the
same exit codes as MS-DOS KEYB (plus some extended codes that MS-DOS KEYB
did not have), but it was so long ago that I can't even remember where I
took the list from ( I am not sure that it wasn't taking MS-DOS KEYB and
maki
Thanks to both again.
Yeah, I supposed that there is no consistent exitcode list for all commands.
I seem to remember a table somewhere with exitcodes for SOME DOS commands
(but I lost track).
The Pascal sources mentioned are interesting attempts to do so. I assume
that no MS-DOS command was prog
Hmm,
The code tries to ignore any non disk-related errors, and returns 0x00
(ignore). Ignore should become fail if it's not allowed. And when it
detects a disk error it seems to set an internal flag to indicate a
critical error which is then tested for in the TestCriticalError[1]
function.
I gues
> Hi Eric,
>> new components should NEVER be tested in conjunction with multiple other
>> changes. NEVER.
> A good idea in theory, but upgrading a distro, including FreeDOS,
> usually gives you updates to dozens, hundreds or thousands of
> packages and this is how in practice MANY users "live"
I would like to know if FreeDOS would be comptaiblewith Broadcom/LSI/Avago
reflash utilities for SCSI SAShard disk cards.___
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
> Am 28.05.2025 um 16:50 schrieb tom ehlert via Freedos-devel
> :
>
> I'm afraid of a kernel 2037 2.0 disaster.
> [...]
> It only happened that 2037 crashed/halted/got stuck after a while. "Randomly".
Without knowing the details, we should try to avoid such a scenario under all
circumstances
> Date: Wed, 28 May 2025 10:06:41 +0100
> From: Liam Proven
> Subject: [Freedos-devel] CSMWrap
>
> CSMWrap is a cool little hack that brings back the good old PC BIOS on
> those fancy-pants UEFI-only systems. It utilises the CSM
> (Compatibility Support Module) and VESA VBIOS from SeaBIOS project
Hi Bernd,
>> Am 27.05.2025 um 16:17 schrieb tom ehlert via Freedos-devel
>> :
>>
>> I don't have any secret information.
>> I'm just worried that there might be a reason PerditionC hasn't released
>> *any* kernels over the last few years, while there has been so much
>> added/fixed.
>> And I
Hi,
> Thanks to all for the attention.
> Actually I seem to vaguely remember some such list in an undocumented DOS
> book or document, but was unable to find it, and hoped someone would.
you might mean the list of error codes for failing function calls,
where "out of disk space", "invalid handle
I want to inform that the FreeDOS T2505 contains a FreeCOM v0.86 with a faulty
.EXE header (wrong MIN paragraphs). So T2505 will not boot on VMware under menu
option 2 (default).
I fixed this on Gitlab for the FreeDOS 1.4 release via the master branch, but
forgot to merge this into the unstable
«
CSMWrap is a cool little hack that brings back the good old PC BIOS on
those fancy-pants UEFI-only systems. It utilises the CSM
(Compatibility Support Module) and VESA VBIOS from SeaBIOS project to
emulate a legacy BIOS environment.
»
https://github.com/FlyGoat/csmwrap
--
Liam Proven ~ Profil
15 matches
Mail list logo
