Hacker News Reader

My idea is basically a DOS runtime with hooks on interrupts and I/O that would allow for either migrating databases to modern formats, or converting I/O accesses for modern USB peripherals. Customization for every customer and AI not being much of a help are pluses for me... lack of money not so much.

View on HN

I have been porting sections of the business software I mentioned earlier from QuickBASIC on DOS (nice to have the source code!) to Tcl on Linux using ChatGPT to automate the conversion. It gets it right the first try, almost every time.

The BASIC code is very simple by modern standards, and Tcl overlaps BASIC neatly, making conversion easy.

Unfortunately it's just a short-term stopgap to add some features management suddenly can't live without, that weren't practical to implement in BASIC/DOS. They'll replace the whole stack with a commercial product and support contract when they find something they like.

For anything business-critical, I'd tend to want to rely as much original code as possible, running actual MS-DOS on emulated hardware that could be tailored to suit your I/O needs.

Lots of forkable code exists to get started with this, QEMU, 86Box, DOSBox, PCjs, MAME, …

And if you do want to go the route of implementing DOS and BIOS interrupts yourself, DOSBox does this.

Reply on news.ycombinator.com