Hcfyk

TUI-drawing code can be pretty compact when you're working in assembly and relying on the IBM video BIOS to do the heavy lifting.

For example:

• 
  INT 10h/AH=06h and INT 10h/AH=07h can be used either to scroll a rectangular region of the screen or to clear the screen to a specified foreground/background colour combination.


• 
  INT 10h/AH=09h can be used to tile a character like ═ horizontally, or to fill the screen with a character like ▒ before drawing on top of it, both in a single BIOS call.


• 
  INT 10h/AH=13h (available on the PC AT, New XT, EGA, and beyond) lets you write a string, with or without in-line colour attributes and with or without moving the cursor.

I'm sure that someone crunched down their drawing code using tricks like this drawing order:

1. Use INT 10h/AH=09h to fill the screen with ║ characters.


2. Alternate using INT 10h/AH=09hto draw the spans of ═ and the corners and intersection pieces.


3. Use INT 10h/AH=06h to clear out the remaining ║ characters to produce the content areas of the frames.

That has three advantages:

1. There's no BIOS routine that I'm aware of to draw a column of ║ but you can efficiently fill the screen with it, then overdraw or erase everywhere it isn't needed.


2. When you're working in assembly, you can save space by figuring out how to batch up similar int 10h calls so that each operation leaves as many registers as possible already set up for the invocation of the next operation.


3. If you alternate drawing the horizontal and corner pieces, you can take that a step further when dealing with instructions that don't move the cursor by drawing the ═ spans one character too long and one character too far to the left, then overdrawing them with the left-end corner pieces. (Thus, no need to mov a new target column value between drawing the horizontal border and drawing its left-end corner.)

From what I remember of the TUIs I saw in Phoenix and AMI BIOSes right up into the Pentium era, it'd only be a few bytes to draw all that framing and set the colours, then updating the screen would just be a case of one int 10h call to clear each framed region you want to update, then you draw in the new text.

The BIOS routines you need to expose to the OS anyway would be your abstraction and anything more would be unnecessary code bloat in that sort of situation.

Traditional BIOS setup interfaces had much simpler user interfaces than you're assuming. They were also written in assembly which allowed for much more compact code than you would think based on the size of applications today. They didn't have "full blown TUIs", most used a simple form interface. On the other hand operating systems like GEOS for the Commodore 64 showed how you could implement a full blown GUI in assembly and have it fit in 64K of RAM and still leave room for applications.

The original IBM PC didn't have a BIOS setup interface. It didn't need one: there was no real-time clock to set, no hard drive interface to configure, and no battery-backed CMOS RAM to store any sort configuration values. It wasn't until the IBM PC/AT that the IBM PC architecture gained these things, but even then there was no BIOS setup interface in the BIOS itself. Instead, if you wanted to changed the BIOS settings you needed to run a special program.

Eventually though, IBM PC clone manufacturers started putting the BIOS setup code in the BIOS. However rather than a full-blown text user-interface (TUI), with various widgets, they used a simple form-based interface. There was a bunch of static text, plus various fields where you could set things like the current time or various hard drive parameters. The arrows keys would select which field to edit, and the number keys and/or the plus (+) and minus (-) keys would change the value. Pressing a key like F10 would save the change configuration values and exit.

Over time BIOSes also got bigger and bigger. The IBM PC/AT reserved 128K space for motherboard ROMs, so BIOSes could easily grow to 128K as necessary. Eventually even that wasn't enough space and BIOSes started using bank switching to allow the BIOS to grow even bigger while still staying inside the 128K (or even 64K) footprint allowed.

However, most of this additional ROM space (now implemented using flash memory) didn't go towards more advanced setup interfaces; mostly it was used to support new features and functionality built into the motherboard. Things like Advanced Power Management, ACPI, USB keyboard and mouse support, more advanced disk interfaces with RAID support, and booting of Ethernet, CD-ROM and various kinds of USB devices all required more and more ROM space. While this meant more options were added to the BIOS setup screens, the basic interface remained the same.

(There was a period where BIOS vendors experimented with crude graphical setup interfaces with mouse support, but this didn't last long. They were basically the old form based interfaces with additional icons, so they weren't really much of an improvement.)

Even though BIOSes got bigger and bigger, they still would've been written mostly in assembly language. Aside from there still being a need to keep the code as small and as efficient as possible, most of this code was run in 16-bit real-mode. By the time BIOSes might have considered using C, 16-bit x86 C compilers were obsolete and no longer being developed. By today's standards they weren't very good code generators and a bit on the buggy side, and they weren't going to get any better.

Since BIOS vendors were just iteratively updating their BIOS implementations, writing everything in assembly wasn't that big a problem. They had a stable base of code, well tested and known to support all the weird quirks that 100% IBM PC compatibility required. Today if you were writing an entire traditional BIOS from scratch, you'd probably use C, but rewriting everything in C would have caused the BIOS vendors more trouble then it would've been worth.

Because of the adoption of UEFI, things are very different today. UEFI-based firmware for PC clones operate mostly in 32-bit (or 64-bit) mode. This has allowed to them to have much more fancy graphical setup interfaces written in C and/or C++ and compiled with modern compilers.

Was it easier than I'm imagining?

Yes, I believe it was.

Did these early programmers just use a library similar to ncurses but for BIOS programming? How were these text interfaces engineered?

To understand this, it's important to keep in mind two things.

1. The IBM PC of the time was a very simple architecture by today's standards.




2. You can do a lot of things in very little code, especially when you know that you don't have to worry about anything else (even operating system routines) running at the same time and you can know with 100% certainty the starting state of the system (as you are entering from a known point in the BIOS power-on self test).

IBM, and by extension every clone maker that wanted that coveted 100% IBM compatibility, put the graphics card's memory at a fixed address. For monochrome, the address range for text mode began at (physical) B0000H; for color, B8000H. In each range, two bytes were used per character to be displayed; the first byte (even address) held the character code, and the second (odd address) held the attributes for that one character. Characters were laid out such that the first memory position held the character displayed at row 1, column 1; the second memory position held that displayed at row 1, column 2; the 81st memory position that displayed at row 2, column 1; and so on.

Thus, with only a little bit of math and minimal knowledge of how to work with data at arbitrary memory locations, both of which would be absolute requirements to be anywhere near the BIOS code anyway, it's trivial to fill any rectangular portion of the screen with any combination of character and attribute you want.

Beyond that, you can just move text labels into video memory directly, not unreasonably by simply copying bytes (REP MOVSW would be your friend, and probably both be faster and require less code than calling through an interrupt, which will at a minimum require its own bookkeeping).

Having that, you need a way to keep track of what element the user is interacting with. A trivial state machine will do that, quite likely in very little code - especially if you're willing to be a little clever in how you implement it. To indicate which selection is active, you could just toggle the "high intensity" bit for the appropriate characters, which could be done with a few instructions at most (I'm not sure if you can actually do REP OR or REP AND but even if you can't, it'd be a real tight loop).

I imagine that the hardest part would be where the setup utility needs to accept more advanced user interaction than to simply "increase" or "decrease" a value (whatever exactly that means for the specific value), which already gets you quite far. But even that could be done in very little code and a little bit of RAM.

There would be no need for anything even remotely as complex as ncurses for any of this.

Oh, and many of the exact same techniques were used by non-BIOS programmers as well, simply because they gave far superior performance as well as better control over the output compared to pretty much any alternative approach, not least of which going through the BIOS or OS services via interrupts.

Assembler is the way ... You can do a lot of stuff in 4 KBytes just google 4K demoscene ... I once created a 3D space ship sim game under 4K (gfx included) with 3D polygonal SW rendering with textures.

Text mode (VGA mode 3) menus are really just few Bytes of code look at his:

• What is the best way to move an object on the screen?

Printing of text is really just copying data into VRAM so printing routine is just few BYTEs of code and as you can see even Keyboard interrupt handler is not that big.

If you compile similar code in higher level language then the executable is much much bigger because it must contain Engine of the language (handling heap/stack stuff and variables), also the linkage stuff especially if DLLs are used can be quite big in comparison to the usable code itself.

Also modern OSes does not allow direct HW access so even stuff that was easy on the BIOS or MS-DOS side is now much much more complicated and requires a lot of code just to handle APIs.

So the reality of nowadays computing is even if you create some "almost empty window" with some simple functionality that would fit to few KBytes of code the executable grows to ~1MByte or more simply due to interfacing to OS APIs and used Libs ...

My answer is anecdotal, not authoritative, but hopefully it illustrates answers to your questions.

In the early-1990s I worked for a SCSI host adapter startup. Part of being feature-complete in that market was to offer two ROM BIOS features: (a) an INT 13h boot loader (which allowed for the PC to boot off of a SCSI drive, as well as present other SCSI drives as though they were IDE) and (b) a ROM BIOS configuration program to configure the host adapter, format SCSI drives, set IRQ and port numbers, and so forth. (If you used Adaptec cards in the 1990s, this was the "Press Ctrl+A for Setup" option you would see at boot time.)

I was tasked with (b) for our card. Although our target market by that time was not 8086 IBM PCs, or even PC/ATs, compatibility was a high concern; no company wanted a lot of phone calls from unhappy users owning some off-brand machine you never heard of. So, although writing directly to the video RAM was tempting, we stuck with INT 10h for compatibility reasons.

Because we were too cheap to license an existing box-drawing library -- they flourished in the 1990s, and some were small enough for ROM work -- I rolled my own "mini-library" that we wound up using in some simple DOS apps as well. All it offered was box-drawing routines, color selection/highlighting, and a crude form-construction system to move a cursor between menu items (to traverse a tree of menus, a la Gopher) and select/deselect radio buttons and checkboxes. There was no need for free-form text input so the number of controls was quite limited.

Believe it or not, this was mostly written in C with inline assembly stubs for the INT 10h code and to talk with the host adapter (mostly INP/OUTP). The entire ROM BIOS configuration was less than 10K as I recall, well under the 16K onboard ROM I was allocated. (Some of the space was due to the text labels; I considered compressing all strings but abandoned that because we were out of time.)

Which was good, because the INT 13h ROM code (the (a) above) went too big (and it was written in assembly) and had no space for the host adapter microcode (the object code that had to be loaded on the card's microcontroller).

The solution was to use a 32K ROM bank-switched by the host adapter. This meant a portion of the INT 13h code had to be mirrored on my 16K "side" of the ROM so when the switch occurred the CPU continued executing the now-gone ROM code. If the user pressed Ctrl+A the code would jump to my entry point; if the ROM was loading the microcode during its boot routine, it copied the microcode to a block of RAM and bank-switched back to its "side" of the ROM and continued.

Tons of tricks and shortcuts were made to cram a lot of functionality into the ROM BIOS code. C is often pish-poshed as too heavyweight compared to assembly, but it solved a lot of problems for us and cut development time. (Also note my code ran entirely off the stack; a lot of languages simply cannot do that.) It was only two of us writing all of this and we were under time pressure. I don't know we could have fit all of this in a single 16K ROM, but I bet we could've whittled it down further and (perhaps) avoided the need to bank-switch for the microcode.

And remember: While my ROM configuration code was ephemeral (exiting required a reboot), the ROM boot loader hooked INT 13h and remained in memory. This was a trick unto itself; it had zero RAM at its disposal once the system was booted and could only use a limited amount of the stack during interrupts.

It's a miracle all this worked, and yet it did.

As noted, assembly can be pretty dense.

You can pack even more code into a small space using a TIL (Threaded Interpreted Language). FORTH is a well known TIL, but it is easy to roll your own. It is easy to have part of your ROM be pure assembly, and part of it be a TIL. What a TIL does is to trade off speed for space: TILs are more compact than native assembly, but slower. So what a programmer can do is to use the TIL in the parts of the program where speed doesn't matter (such as the UI), and stick to native code where speed does matter (floppy disk interface, for example).

I am not saying that any BIOS used a TIL, but it's a well known technique for squeezing more program into a space, one that would come readily to mind if space started to become a problem.

A TIL isn't the only way to trade off speed for space. You can also implement a specialized bytecode interpreter, and write parts of the program in that. For example, the Apple II computers had an interpreted byte-code interpreter called SWEET16, used to do 16-bit arithmetic on the 8-bit processor.

Early x86 PCs had no boot configuration program, nor was one needed

Quoting Wikipedia:

The BIOS of the original IBM PC and XT had no interactive user interface. Error codes or messages were displayed on the screen, or coded series of sounds were generated to signal errors when the power-on self-test (POST) had not proceeded to the point of successfully initializing a video display adapter. Options on the IBM PC and XT were set by switches and jumpers on the main board and on expansion cards. Starting around the mid-1990s, it became typical for the BIOS ROM to include a "BIOS configuration utility" (BCU[10]) or "BIOS setup utility", accessed at system power-up by a particular key sequence.

• As noted in the quote above, many settings were made by adjusting DIP switches and jumpers inside the computer.




• The boot device was chosen by a fixed scheme. After the power-on self-test and initializing I/O, the BIOS tried to read the boot sector from the A: floppy drive. If that failed, it moved on to the B: floppy, and then the C: hard drive. If the drive itself or its disk were not present, it moved to the next in the sequence. You could always override the hard drive by using a floppy in A:, a security risk that modern BIOSes now allow you to prevent. If there was no viable boot device, it either dropped into ROM BASIC (see below) or gave a retry message.




• More sophisticated configuration was done by files on the boot volume. This was the whole point of the CONFIG.SYS and AUTOEXEC.BAT files in DOS. Want to reconfigure your system? Just edit the configuration files on the boot volume. No special ROM utility needed.




• The drivers and configuration files for expansion cards were on the boot device anyway, not stored in ROM. Software on the boot volume could also override the default behavior of calls to ROM BIOS.




• BIOS literally means basic input/output system. Input was limited to keyboards (and the original ROMs could not even handle 101-key keyboards). Output was text and basic teletype control characters to the screen. ROM BIOS did not even support ANSI escape codes -- that was the whole point of the ANSI.SYS file on the DOS boot volume!



• 
  

  Sure, there was ROM BASIC, but...

  
  
  
  
  

  • only on IBM brand machines. They licensed BASIC from Microsoft to put into ROM. Part of the agreement was that Microsoft could not sell clone makers the contents of the IBM ROMs. Therefore, clones never had BASIC in ROM.

  
  

  • it was only activated if no boot drives (floppies, hard disks) could be found.

  
  

  • it was a command-line interpreter, not a fancy menu-driven configuration utility.

  
  

  • ROM BASIC could only access files on cassette tape. There were other versions of BASIC that could access files on floppies or the hard drive, but these were DOS programs, not something in the ROM.

  
  

  • ROM BASIC could only run BASIC programs, not .COM or .EXE files. So there is no way to transfer control of the system to something else.

  
  

  • the cassette port hardware was eliminated in the XT, and BASIC was taken out of the ROM starting with the AT.

  
  
  
  



• Sure, there were fancy menu-based programs, but... these were DOS programs loaded from disk, not programs built into ROM.




• There was no memory to store the settings anyway. EEPROM, battery-backed RAM, and FLASH memory were far more expensive than storing the configuration on the boot device. FLASH chips weren't even available until 1988.

Was it theoretically possible? Yes, and all of the other answers seem to focus on that aspect. However, this is Retrocomputing and should be about what historically happened.

The graphics area is small 320x200 with 4 colors on CGA screen or 640x350 2 colors. So a simple chess game can be done in a small area.

For text UIs there's ASCII graphic characters to make boxes and such https://en.wikipedia.org/wiki/Code_page_437

which are still being used today. The color range is also limited to 16 colors.

So basically given a limited palette but "richer" primitives (in the form of ASCII lines from CP437), you don't need as much to do rendering.

Secondly there's less overall memory space so you have an address of 2 bytes to represent something in the 64K space. There's no memory management to deal with because the entire memory space is yours (except for a few reserved areas)

A lot of work can also be done through interrupts specifically Int 10 https://en.wikipedia.org/wiki/BIOS_interrupt_call which gives you a lot of video controls as well.