The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,860 other subscribers

Archive for the ‘MS-DOS’ Category

Rudimentary DaynaPORT packet driver to use WiFi from DOS using BlueSCSI: GitHub – cml37/daynaport-dos-packet-driver

Posted by jpluimers on 2025/10/08

Despite beta or early alpha quality [Wayback/Archive] GitHub – cml37/daynaport-dos-packet-driver by by [Wayback/Archive] RetroTech Chris – YouTube is very cool.

Main source: [Wayback/Archive] daynaport-dos-packet-driver/src/dayna.c at main · cml37/daynaport-dos-packet-driver · GitHub

Related:

Read the rest of this entry »

Posted in C, Development, Hardware Development, Hardware Interfacing, MS-DOS, Network-and-equipment, SCSI, Software Development, TSR Terminate and Stay Resitent, Turbo C | Leave a Comment »

Running DOS Programs on an Apple Silicon based Mac

Posted by jpluimers on 2025/08/11

I’m vintage, so I have some old machinery but also want to be able to run old software on newer hardware.

TL;DR: Since Apple Silicon (which is based on ARM) uses Intel Emulation for regular Mac binary programs, VMware Fusion# on Mac M* series cannot run Intel based operating systems, after some research there basically were these options:

  • use VMware Fusion and run inside a Windows on ARM VM by using
    • a dos emulator like DOSBox or DOSBox-X, since modern 64-bit Windows lacks the NTVDM:

      Since virtual 8086 mode is not available on non-x86-based processors (more specifically, MIPSDEC Alpha, and PowerPC) NTVDM is instead implemented as a full emulator in these versions of NT, using code licensed from Insignia’s SoftPC. Up to Windows NT 3.51, only 80286 emulation is available. With Windows NT 4.0486 emulation was added.

      NTVDM is not included with 64-bit versions of Windows or ARM32 based versions such as Windows RT or Windows 10 IoT Core. The last version of Windows to include the component is Windows 10, as Windows 11 dropped support for 32-bit processors.

    • an NTVDM replacement like NTVDMx64 or winevdm (sometimes calles otvdm)
  • use a specific emulator like DOSBox-X directly on MacOS
  • use a more generic emulator like QEMU based UTM

I have a VMware background on bare metal, Windows and MacOS, so I prefer it over Parallels

Links: Read the rest of this entry »

Posted in DOSBox, DOSBox emulator, Emulators, MS-DOS, Power User, Virtualization | Leave a Comment »

From Turbo Pascal to Delphi to C# to TypeScript, an interview with PL legend Anders Hejlsberg – YouTube

Posted by jpluimers on 2025/04/09

Nice historic perspective: [Wayback/Archive] From Turbo Pascal to Delphi to C# to TypeScript, an interview with PL legend Anders Hejlsberg – YouTube

Via [Wayback/Archive] Zack Urlocker on Twitter: “Great interview with @ahejlsberg on the evolution of programming languages, the rise of TypeScript and more. Anders is one of the best programmers I ever worked with. …”

--jeroen

Posted in .NET, Borland Pascal, C#, Delphi, Development, History, JavaScript/ECMAScript, MS-DOS, Pascal, Scripting, Software Development, Turbo Pascal, TypeScript, Windows Development | Leave a Comment »

Wow: inside DOS Doom version 2, you can run another Doom (even arbitrary other code)

Posted by jpluimers on 2024/09/17

Repository:

A Video that way better explains how the hacks work to make this happen is at [Wayback] You can run Doom inside (DOS) Doom, for real. – YouTube

I have found a code execution exploit in the original DOS Doom 2 and ported a Chocolate Doom to it. And then Chocolate Heretic.

Attention: This does only work on the original DOS Doom2 version, no GZDoom or other source ports. This is a good thing as you don’t want code execution exploit on modern systems. People would abuse it to spread malicious code.

DOS version is available on Steam and you can use DosBox emulator to run it.

Copy kgdid.wad to the directory where you have doom2.exe and then in DosBox start it with command “doom2 -file kgdid.wad“.

(Copy other files too if you want to try them. Game injection has to be renamed to doomsav4.dsg)

Related:

–jeroen

Posted in Assembly Language, Development, DOOM, Games, MS-DOS, Power User, Software Development, x86 | Leave a Comment »

GitHub – bbbradsmith/flompy: DOS floppy disk dumper

Posted by jpluimers on 2022/04/26

Need one day when archiving old floppies: [WayBack] GitHub – bbbradsmith/flompy: DOS floppy disk dumper

Via: [WayBack] Brad Smith on Twitter: “So I wrote a floppy disk dumper program for DOS. I dunno if this is really a very useful thing, but it’s open-source at least! 💾⚡🖥 “

Full thread at [WayBack] Thread by @bbbradsmith: “Hrm… why doesn’t the floppy controller status register have its non-DMA bit set, even though I’ve used a specify command to set it… and […]”:

Read the rest of this entry »

Posted in Development, History, MS-DOS, Power User, Software Development | Leave a Comment »

Much Turbo Pascal history (via What is a Delphi DCU file? – Stack Overflow)

Posted by jpluimers on 2021/05/19

Editing [WayBack] What is a Delphi DCU file? – Stack Overflow for more historic correctness and adding links prompted me to archive some older material and search for some more, basically because while historically very relevant, link rot makes a lot of that stuff harder and harder to find.

The legendary full page colour advert published in the 12th 1983 issue of Byte Magazine on page 456 is at the bottom of this post (Many BYTE magaine issues have been archived at https://archive.org/details/byte-magazine).

The smaller version below is from WayBack: Sip from the Firehose : November 2008 marks the 25th anniversary of Turbo Pascal v1.0! (this article is not available on the Embarcadero or Idera site any more).

I also included more adverts in reverse chronological order at the end:

The last two via [WayBack] saundby.com: Software for the Ampro Little Board.

--jeroen

Read the rest of this entry »

Posted in Conference Topics, Conferences, CP/M, Delphi, Development, Event, History, MS-DOS, Pascal, Power User, Software Development, Turbo Pascal, UCSD Pascal, Z80 | Leave a Comment »

Running BBS Door Games on Windows 10 with GameSrv, DOSBox, plus telnet fun with WSL – Scott Hanselman

Posted by jpluimers on 2020/12/07

Reminder to self: see if I ever can resurrect my old BBS and FidoNet node that was based on at least:

  • FrontDoor (by Joaquim Homrighausen)
  • RemoteAccess (by Andrew Milner)
  • GoldED (by Odinn Sørensen)
  • A FOSSIL driver (forgot the name)
  • A Fidonet NodeList Compiler
  • a Message Tosser

Maybe a good place to start: [WayBack] Running BBS Door Games on Windows 10 with GameSrv, DOSBox, plus telnet fun with WSL – Scott Hanselman

I already wrote a few times about me being on Fidonet, and BITNET in the late 1980s:

A few email addresses I have been using in that era:

A tag-line from me in that era (I blanked out the phone number as it now belongs to someone else):

    o _   _  _   _   _             voice:  +31-2522-XXXXX (19:00-22:00 UTC)
   / (_' |  (_) (_' | |            snail:  P.S.O.
__/                                        attn. Jeroen W. Pluimers
                                           P.O. Box 266
jeroenp@rulfc1.LeidenUniv.nl               2170 AG Sassenheim
jeroen_pluimers@f521.n281.z2.fidonet.org   The Netherlands

Related:

–jeroen

Posted in BBS, dial-up modems, FidoNet, History, MS-DOS, Power User, Windows | Leave a Comment »

The Throttle homepage. Slow that machine down!

Posted by jpluimers on 2020/01/06

Cool tool if you have industrial machinery that uses DOS and needs a slowdown on modern hardware (because for instance your serial communications program is running way too fast): [WayBackThe Throttle homepage. Slow that machine down!

Via Matthijs ter Woord

Downloads:

  • Q) How does throttle work?
  • A) Throttle enables power management bits in the chipset to control CPU clock. Any chipset that conforms to the ACPI (advanced configuration and power interface) specification has a means to enable and control the throttle.
    The intended purpose of these bits is to provide a means of power savings, typically utilized in notebooks or other battery powered devices.
    When the CPU is in a throttled state, it uses less power. It just so happens that a throttled CPU creates a perfect environment to emulate the performance of an older generation CPU!
  • Q) I have a chipset that supports ACPI. Why isn’t it supported in throttle?
  • A) Probably because I don’t know about it. Because the ACPI specification can be implemented in different ways by different chipset manufacturers, it’s impossible to create one generic program that works with all ACPI compliant hardware. This creates the problem of constantly updating the internal database of known hardware. So far, the biggest problem has been finding the documentation for known ACPI compliant chipsets. Adding support for them is the easy part! You may also be using an older version of throttle. Contact me for the latest.
  • Q) Can I have more speed options than just the 8 (or 16) provided?
  • A) No. Throttle provides you with as many different CPU throttling options as the chipset allows. The ACPI spec only defines 8 different modes, each one 12.5% more throttled than the previous. VIA technologies has taken the spec 1 step further and allowed for throttling on 6.25% increments, thus doubling the amount of options available, which provides for more slowdown and a finer tunability.
    If you want to run oldskool games, get a VIA motherboard!There’s nothing I can do to change the available options, and no further options will be available unless the ACPI spec changes.

–jeroen

Posted in History, MS-DOS, Power User | Leave a Comment »

Mode – from the DOS era, still works in Windows

Posted by jpluimers on 2019/12/27

Blast from the past:

–jeroen

Posted in MS-DOS, Power User, Windows | Leave a Comment »

Saving windows command prompt history to a file – Charlie Arehart’s ColdFusion Troubleshooting Blog

Posted by jpluimers on 2018/11/14

Dumping the command prompt history

From [WayBackSaving windows command prompt history to a file – Charlie Arehart’s ColdFusion Troubleshooting Blog:

doskey /history

gives you the command history.

Redirecting with >, >> or piping with | allows you to save this to a file or filter the output.

Found via: [WayBackHow I can export the history of my commands in Windows(7) Command Prompt? – Stack Overflow

Shells that do support persistent history

Note that the command history is not persistent. If you want that, then there are two other shells that support persistent history:

Both of these found through [WayBackwindows – Is there a global, persistent CMD history? – Server Fault.

–jeroen

Posted in Microsoft Surface on Windows 7, MS-DOS, Power User, Windows, Windows 7, Windows 8, Windows 8.1 | Leave a Comment »