This is a quick start guide to using microcomputer emulators which implement a teletext adapter and support a live teletext packet source on Microsoft Windows. Currently this is only the Stardot fork of BeebEm for Windows. Emulation of the TTX2000S adapter will hopefully be available in Fuse in the near future.

Setting up a teletext packet server

The following instructions will get a single packet server running on port 19761, outputting the community run Teefax service. Other services can be created using vbit2, or an off-air packet stream from a digital TV capture card could be used, but that is outside the scope of this guide.

Some output should appear in the console along the lines of:
[Configure::Configure] Started
[Configure::Configure] Pages directory is ./teefax
...
[Service::run] Lines per field: 16

Windows will ask for permission to open the firewall.

To check for updates to Teefax run svn up in the teefax directory.

A batch file that regularly checks for updates can be made something like this:
@echo off
:loop
svn up
timeout /T 300 /NOBREAK >NUL
goto loop

The packet server is primarily intended for use on localhost. It will also work across a fast LAN, but struggles on slower wifi networks. Serving packets over the internet is not recommended.

BeebEm

For further information, refer to the Advanced Teletext System manual.

Currently only the ATS ROM is supported. The earlier Acorn TFS ROM will not work.

If Hardware->Teletext Data->IP:Custom destination is selected, BeebEm will use the IP address and port numbers specified in preferences.cfg. This enables connections over the network, on alternative ports, and ‘tuning’ the same packet source on more than one ‘channel’ preset.

Hardware->Teletext Data->Capture files reads from four static files as in previous versions of BeebEm.