Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

Code at 0x9F00 segment after boot (Miscellaneous)

posted by Zyzzle, 09.11.2020, 06:46

> > Also, are you running DOS from UEFI, without using any built-in legacy
> > BIOS? What is the procedure you are using for this?
>
> Hi, AFAIK DOS and also all non-UEFI aware Windows (Vista and older) depends
> on BIOS services and MBR loader so you need to have CSM enabled in your
> UEFI. The problem is that CSM is no longer required as part of standard and
> manufacturers will happily get rid off it :\

But, isn't it possible to boot through LILO and / or GRUB in Linux UEFI bootloader, and then load (emulate?) legacy MBR mode, and pass this code by in order to then boot native DOS? I hope it is so.

And, my laptop available memory in DOS is not the usual 655360 bytes, either. It is about 6kb reduced as well. Every laptop I've used, except ones based on the old Atom 32-bit processors have never showed the full 640kb of low memory available when booting DOS. A vintage 2016 Dell laptop reduced low memory by about ~70-75 kb, cause unknown, but it was almost not usable for DOS purposes because of that. And BIOS didn't have any "disable" options, either.

And board manufacturers are going to gladly eliminate CSM since it will save them a nickel or a dime per montherboard manufactured. It is a sad day for legacy compatibility. The only boards to support CSM in future will be high-end "retro" boards, which will be 10x as expensive as boards of today due to capitalistic greed and an intentionally created market. Sad, indeed.

I've saved a few legacy MBR boot BIOS boards myself for just this purpose of maintaining bare-hardware DOS compatibility. Emulation is for the dogs, I want to boot DOS baremetal.

 

Complete thread:

Back to the forum
Board view  Mix view
22749 Postings in 2119 Threads, 402 registered users (1 online)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum