Spotlight › Browser
HTML on an IBM PC XT
A web browser for the IBM PC XT. It fetches pages over an Ethernet card or a parallel cable and lays them out on the PC itself: text, tables, pictures, colours and frames, the way a 1990s home page expected.
- Pictures a page
- Up to 64
- Largest picture
- 192KB
- Minimum CPU
- 8088
01 / Browser scope
Browser scope
The browser parses headings, paragraphs, lists, links, tables and basic forms on the PC. It performs cell measurement, column sizing and wrapping locally. Networking is provided by loadable drivers, separate from the browser package.
Direct requests use HTTP. The period protocol reference is HTTP/1.0, RFC 1945. This renderer supports a subset of HTML, not a contemporary browser engine.
Version 1.8 aims at the home pages of 1996 to 1999, as Internet Explorer 3 drew them. Most pictures on those pages sit inside a table, which 1.7 left out: on eleven front pages of the time, 1.7 showed about 12 of their 230 pictures, and the first step of 1.8 brought that to about 170. It also draws page, text, link and table-cell colours on VGA and EGA, matched to the 16 colours those cards show. Headings and body text are set in Times, and the largest headings are drawn twice the height. Frames sit side by side, up to 16 to a page. A picture aligned left has the text flow beside it. Pictures up to 192KB open, and a GIF is drawn as it arrives.
A new Options menu turns pictures, animations, colours, fonts and tables on or off, and saves the choice. A download is offered under the file's real name, cut to the eight-plus-three letters a DOS file name allows. Browser 1.8 is the work of pentagram666.
02 / Browser captures
Browser captures
03 / Network paths
Network paths
ETHER.DRV drives NE1000/NE2000-compatible ISA adapters and supplies ARP, IPv4, UDP, TCP and DHCP. Static addressing is available. NET.DRV supplies the alternative parallel-port path through a DOS host; the recorded payload rate was 3,741 bytes/s.
Both drivers expose the same connection API to the browser and Telnet. When both are attached, the Ethernet path is preferred.
04 / Rendering cost
Rendering cost
The recorded XT full-window text redraw takes 1.2-2.6 seconds depending on the adapter. The renderer avoids repeated glyph drawing, scrolls existing pixels, and repaints only exposed rows. Repeated cursor-key events are coalesced into one final scroll position.
QEMU screenshots establish output and interaction; they do not establish XT redraw latency.
05 / HTTPS through a host proxy
HTTPS through a host proxy
The guest has no TLS implementation. tools/os88proxy.py terminates HTTPS on another host and forwards an HTTP response. Its optional markup reduction can reduce transfer and layout cost.
Proxy traffic between the PC and host is unencrypted. Authentication state remains on the proxy host. The browser itself has no password input; use this arrangement on a trusted network.
06 / Rendering limits
Rendering limits
No JavaScript or style sheets. A page built by a script may come out empty. Unsupported markup falls back to text where possible. Basic form fields have fixed capacity; use the location bar for long URLs.
Colours show on VGA and EGA only. Hercules and CGA show every page black on white, and a page dragged from a colour screen onto a monochrome one on a two-screen PC is drawn again in black and white. Up to 64 pictures load on a page.
The rendering cost above was measured before pictures and colours arrived. Browser 1.8 has not yet been timed on a 4.77 MHz PC: the emulator that counts the original PC's cycles has no network card, so it cannot fetch a page.
07 / Run the browser
Run the browser
Attach ETHER.DRV in Control Panel and use a compatible ISA adapter, or configure the parallel bridge. The existing QEMU recipe below selects NE2000 ISA hardware. Plain HTTP requires no proxy; HTTPS destinations do.
-netdev user,id=n0 \
-device ne2k_isa,netdev=n0,iobase=0x300,irq=3python3 tools/os88proxy.py