qx89l4

4 ms·

1.
by qx89l4 7y ago
Awesome project, congrats!
2.
by qx89l4 7y ago
I "discovered" DOS 25 years ago, not sure what's your point?
3.
by qx89l4 7y ago
Hadn't heard of them, thanks for the links!
4.
by qx89l4 7y ago
Good point, OpenWatcom is obviously miles ahead of Turbo C, but it's also much more complex. I tinkered with it for a while, and ended up using the latter for its simplicity. DOSBox can be easily installed on any system, you can save t
5.
by qx89l4 7y ago
Targeting 8086-level of instructions was actually my first idea. It wasn't possible with gcc/clang, but Turbo C is freeware these days, so... ;) In case you're interested, see https://github.com/luke8086/
6.
by qx89l4 7y ago
I'm not sure if defaulting to 32-bit instructions would still allow calling BIOS, but good point! In this case the design goal was to show the easiest way to jump into C and start building the actual application, so I just tried to avo
7.
by qx89l4 7y ago
I feel your pain, so sorry that you still need to support the .code16gcc hack! My first approach was actually to avoid GCC/clang altogether, and use Turbo C instead. It came with its own set of problems, but the output was much more pr
8.
Show HN: A simple way to write standalone C programs for i386(github.com)
147 points by qx89l4 7y ago|34 comments
9.
by qx89l4 7y ago
> Also seems he has just self-published a book (as of July 27): > Do you would like more details on the inner workings? This program is fully commented in my new book Programming Boot Sector Games and you'll also find a 8086&#x2F