- #Calmira free dos drivers#
- #Calmira free dos full#
- #Calmira free dos code#
- #Calmira free dos download#
It's terrible, but it allows me to hear anything.
#Calmira free dos drivers#
Because the Conexant audio device doesn't have drivers for any system older than XP nor does it have a Sound Blaster compatibility mode, I was forced to use a generic PC Speaker driver. To have an acceptably working system, I also needed audio. The VMWare one turned out to also work with my X200. There are two patching programs for the standard SVGA256.DRV - one supposedly for VirtualBox, another one for VMWare. To achieve the glorious 256 colors and 1024x768 (partially seen in the screenshot above), I've had to use a modified SVGA driver.
#Calmira free dos download#
You can download the VGA Option ROM here. The fix was to use some phoenix-proprietary tools, which I can't find now. As it turns out, the X200 ROM is the "new" ROM variant (which is kinda weird considering that I've unpacked a T420 ROM before without a problem). I've had a few dumps of lenovo BIOSes, but couldn't get anything out of them with tools like bios_extract or UEFITool. Option ROMs should reside inside the original proprietary BIOS images. The fix was to embed a proprietary VGA Option ROM inside the coreboot image, which was hard only because no one dumped it before. It turns out that libgfxinit isn't 100% VESA compliant and some older operating systems might crap out trying to init the display - all I could get was a black screen after typing `win` at the prompt. Even more problems.?Īfter deciding upon the 2.88MB barrier, I tried booting windows from a flash drive, just as a test to see if everything worked.
#Calmira free dos code#
After reading about how floppy systems are complicated on oswiki and fiddling with the code a bit more, I gave upon the idea about filling the whole ROM. It's either that SeaBIOS can't allocate a proper amount of memory for the disk and it stops half-way, or it's about how the floppy controller talks with the hardware. The logical explanation as to why is that so is rather complicated. I've tried changing the fifth case to 2 heads, 80 tracks and 72 sectors. By modifying the amount of sectors I should be able to load bigger floppy images. Struct floppyinfo_s FloppyInfo VARFSEG = ,Īs we can see, this struct is used to determine floppy size. I've mostly looked at the part used for handling the floppy itself. To use the whole area, I've tried modifying a few bits of SeaBIOS source code.
It turns out that SeaBIOS has partial support for booting from flash - it sets up a virtual floppy drive with your floppy of choice loaded from floppyimg/.lzma, but this gives us at best 2.88MB (standard ED floppy disk size, exactly 2x as large as a popular 1.44M), and I wanted more.
#Calmira free dos full#
(totally unncessary) SeaBIOS hackingīecause the standard coreboot payload with SeaBIOS only occupies only about 1MB out of the full 8 on the ROM, I thought about embedding a full OS on the remaining 7 megs. Besides my rage that was mostly a result of badly written libreboot and coreboot docs (things are hard to find, a ton of the info is outdated, etc), I came up with an idea for corebooting my own X200. Over a course of a weekend, I've prepared a SPI flasher based on flashrom and a Raspberry Pi and flashed a few ThinkPads. Recently, a friend of mine paid me a visit with a few of his ThinkPads.
0 kommentar(er)
