#turboc — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #turboc, aggregated by home.social.
-
Reject Modernity, Return to 80s, Learn C.
https://fed.brid.gy/r/https://hackaday.com/2026/07/10/reject-modernity-return-to-80s-learn-c/
-
Reject Modernity, Return to 80s, Learn C.
https://fed.brid.gy/r/https://hackaday.com/2026/07/10/reject-modernity-return-to-80s-learn-c/
-
Reject Modernity, Return to 80s, Learn C.
https://fed.brid.gy/r/https://hackaday.com/2026/07/10/reject-modernity-return-to-80s-learn-c/
-
New video: Let's Code MS DOS 0x38: Huge Pointers in Turbo C
YouTube: https://youtu.be/pf3s-6EVDoo
MakerTube: https://makertube.net/w/hPL2jfBzdmkWeRpfBnqz4a -
New video: Let's Code MS DOS 0x38: Huge Pointers in Turbo C
YouTube: https://youtu.be/pf3s-6EVDoo
MakerTube: https://makertube.net/w/hPL2jfBzdmkWeRpfBnqz4a -
New video: Let's Code MS DOS 0x38: Huge Pointers in Turbo C
YouTube: https://youtu.be/pf3s-6EVDoo
MakerTube: https://makertube.net/w/hPL2jfBzdmkWeRpfBnqz4a -
New video: Let's Code MS DOS 0x38: Huge Pointers in Turbo C
YouTube: https://youtu.be/pf3s-6EVDoo
MakerTube: https://makertube.net/w/hPL2jfBzdmkWeRpfBnqz4a -
New video: Let's Code MS DOS 0x38: Huge Pointers in Turbo C
YouTube: https://youtu.be/pf3s-6EVDoo
MakerTube: https://makertube.net/w/hPL2jfBzdmkWeRpfBnqz4a -
Let's Code MS DOS 0x38: Huge Pointers in Turbo C
-
Let's Code MS DOS 0x38: Huge Pointers in Turbo C
-
Let's Code MS DOS 0x38: Huge Pointers in Turbo C
-
Let's Code MS DOS 0x38: Huge Pointers in Turbo C
-
Let's Code MS DOS 0x38: Huge Pointers in Turbo C
-
New video for Patrons: Let's Code MS DOS 0x38: Huge Pointers in Turbo C
In MS DOS you can only access up to one Megabyte of memory easily, on an original PC or XT. This memory in turn is segmented, so accessing more than 64K at a time becomes a bit more tricky. This is why languages like Turbo C and Pascal introduced near and far pointers to the programmer. However there are also huge pointers, which we will investigate in this episode.
-
New video for Patrons: Let's Code MS DOS 0x38: Huge Pointers in Turbo C
In MS DOS you can only access up to one Megabyte of memory easily, on an original PC or XT. This memory in turn is segmented, so accessing more than 64K at a time becomes a bit more tricky. This is why languages like Turbo C and Pascal introduced near and far pointers to the programmer. However there are also huge pointers, which we will investigate in this episode.
-
New video for Patrons: Let's Code MS DOS 0x38: Huge Pointers in Turbo C
In MS DOS you can only access up to one Megabyte of memory easily, on an original PC or XT. This memory in turn is segmented, so accessing more than 64K at a time becomes a bit more tricky. This is why languages like Turbo C and Pascal introduced near and far pointers to the programmer. However there are also huge pointers, which we will investigate in this episode.
-
New video for Patrons: Let's Code MS DOS 0x38: Huge Pointers in Turbo C
In MS DOS you can only access up to one Megabyte of memory easily, on an original PC or XT. This memory in turn is segmented, so accessing more than 64K at a time becomes a bit more tricky. This is why languages like Turbo C and Pascal introduced near and far pointers to the programmer. However there are also huge pointers, which we will investigate in this episode.
-
New video for Patrons: Let's Code MS DOS 0x38: Huge Pointers in Turbo C
In MS DOS you can only access up to one Megabyte of memory easily, on an original PC or XT. This memory in turn is segmented, so accessing more than 64K at a time becomes a bit more tricky. This is why languages like Turbo C and Pascal introduced near and far pointers to the programmer. However there are also huge pointers, which we will investigate in this episode.
-
TIL there's a dosbox fork (dosbox-x) with a bunch of fancy features, including more realistic emulation of hercules monographics displays, which lets me more accurately re-experience my middle school XT clone computing experience.
-
TIL there's a dosbox fork (dosbox-x) with a bunch of fancy features, including more realistic emulation of hercules monographics displays, which lets me more accurately re-experience my middle school XT clone computing experience.
-
TIL there's a dosbox fork (dosbox-x) with a bunch of fancy features, including more realistic emulation of hercules monographics displays, which lets me more accurately re-experience my middle school XT clone computing experience.
-
TIL there's a dosbox fork (dosbox-x) with a bunch of fancy features, including more realistic emulation of hercules monographics displays, which lets me more accurately re-experience my middle school XT clone computing experience.
-
TIL there's a dosbox fork (dosbox-x) with a bunch of fancy features, including more realistic emulation of hercules monographics displays, which lets me more accurately re-experience my middle school XT clone computing experience.
-
I should have looked at the linker options more closely and turned on "Warn duplicate symbols" from the start...
-
I should have looked at the linker options more closely and turned on "Warn duplicate symbols" from the start...
-
I should have looked at the linker options more closely and turned on "Warn duplicate symbols" from the start...
-
I should have looked at the linker options more closely and turned on "Warn duplicate symbols" from the start...
-
I should have looked at the linker options more closely and turned on "Warn duplicate symbols" from the start...
-
Huh. For some reason Turbo C's time() is getting stuck in an infinite loop. Don't call it to seed the random number generator or determine the phase of moon and off we go...
Hmm. Can't get the time() hang to repro in a trivial test program. I wonder what's going on here.
Aha. time() called getdate() which conflicted with a function in Hack (that called getlt() that called time()). Not sure why that resulted in a hang instead of a crash due to stack overflow...
-
Huh. For some reason Turbo C's time() is getting stuck in an infinite loop. Don't call it to seed the random number generator or determine the phase of moon and off we go...
Hmm. Can't get the time() hang to repro in a trivial test program. I wonder what's going on here.
Aha. time() called getdate() which conflicted with a function in Hack (that called getlt() that called time()). Not sure why that resulted in a hang instead of a crash due to stack overflow...
-
Huh. For some reason Turbo C's time() is getting stuck in an infinite loop. Don't call it to seed the random number generator or determine the phase of moon and off we go...
Hmm. Can't get the time() hang to repro in a trivial test program. I wonder what's going on here.
Aha. time() called getdate() which conflicted with a function in Hack (that called getlt() that called time()). Not sure why that resulted in a hang instead of a crash due to stack overflow...
-
Huh. For some reason Turbo C's time() is getting stuck in an infinite loop. Don't call it to seed the random number generator or determine the phase of moon and off we go...
Hmm. Can't get the time() hang to repro in a trivial test program. I wonder what's going on here.
Aha. time() called getdate() which conflicted with a function in Hack (that called getlt() that called time()). Not sure why that resulted in a hang instead of a crash due to stack overflow...
-
Huh. For some reason Turbo C's time() is getting stuck in an infinite loop. Don't call it to seed the random number generator or determine the phase of moon and off we go...
Hmm. Can't get the time() hang to repro in a trivial test program. I wonder what's going on here.
Aha. time() called getdate() which conflicted with a function in Hack (that called getlt() that called time()). Not sure why that resulted in a hang instead of a crash due to stack overflow...
-
Well this sure brings back memories.
It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.
Disk Images
https://archive.org/details/borland-turbo-c-v2.0User and Reference Manual:
https://archive.org/details/bitsavers_borlandturer2.01988_23162264
https://archive.org/details/bitsavers_borlandturuideVer2.01988_19310204If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.
-
Well this sure brings back memories.
It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.
Disk Images
https://archive.org/details/borland-turbo-c-v2.0User and Reference Manual:
https://archive.org/details/bitsavers_borlandturer2.01988_23162264
https://archive.org/details/bitsavers_borlandturuideVer2.01988_19310204If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.
-
Well this sure brings back memories.
It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.
Disk Images
https://archive.org/details/borland-turbo-c-v2.0User and Reference Manual:
https://archive.org/details/bitsavers_borlandturer2.01988_23162264
https://archive.org/details/bitsavers_borlandturuideVer2.01988_19310204If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.
-
Well this sure brings back memories.
It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.
Disk Images
https://archive.org/details/borland-turbo-c-v2.0User and Reference Manual:
https://archive.org/details/bitsavers_borlandturer2.01988_23162264
https://archive.org/details/bitsavers_borlandturuideVer2.01988_19310204If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.
-
Well this sure brings back memories.
It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.
Disk Images
https://archive.org/details/borland-turbo-c-v2.0User and Reference Manual:
https://archive.org/details/bitsavers_borlandturer2.01988_23162264
https://archive.org/details/bitsavers_borlandturuideVer2.01988_19310204If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.
-
New video for Patrons:
Let's Code MS DOS 0x31: ANSI C Data Types
The C programming language has only few builtin data types. But for a beginner those can be a bit confusing. So we will have a look at what data types are offered, and what kind of new datatypes you can build with C.
-
New video for Patrons:
Let's Code MS DOS 0x31: ANSI C Data Types
The C programming language has only few builtin data types. But for a beginner those can be a bit confusing. So we will have a look at what data types are offered, and what kind of new datatypes you can build with C.
-
New video for Patrons:
Let's Code MS DOS 0x31: ANSI C Data Types
The C programming language has only few builtin data types. But for a beginner those can be a bit confusing. So we will have a look at what data types are offered, and what kind of new datatypes you can build with C.
-
New video for Patrons:
Let's Code MS DOS 0x31: ANSI C Data Types
The C programming language has only few builtin data types. But for a beginner those can be a bit confusing. So we will have a look at what data types are offered, and what kind of new datatypes you can build with C.
-
New video for Patrons:
Let's Code MS DOS 0x31: ANSI C Data Types
The C programming language has only few builtin data types. But for a beginner those can be a bit confusing. So we will have a look at what data types are offered, and what kind of new datatypes you can build with C.
-
Let's Code MS DOS 0x31: ANSI C Data Types
-
Let's Code MS DOS 0x31: ANSI C Data Types