Clipboard access

Here you can discuss the development of patches.

Clipboard access

Postby qv90 » 2006-9-22 @ 13:24

Version 0.1

Using DosBox on Windows systems, it is hard to transfer data between the DOS application and the host system.

I implemented a new DOS device called "CLPBOARD" which any DOS application can open and read or write. The data is then directly read (or written) to the windows clipboard.

Please be aware, that this patch is written for/in MS Visual-C++.

If you want to test the device with the "COPY" shell command, please download and apply bugfix and

You can download patch at

Live long and prosper
Last edited by qv90 on 2007-6-26 @ 12:12, edited 1 time in total.
User avatar
Posts: 65
Joined: 2006-7-01 @ 10:22

Re: Clipboard access from DosBox 0.65

Postby Dominus » 2006-9-22 @ 16:07

This sounds great. Got to try if that is compileable with mingw. I also wonder if that would work when you run Windows 3.1 in Dosbox :)

Is the patch against 0.65 release or "current" CVS?

Also if there are two patches to download and apply you are not linking to the second one but two times to the same one.
Edit2: Ah, I found it, you submitted your patches to the bug section of Dosbox and not the patches. But I'm sure a developer can move it to the right section (and maybe a mod can move the topics here to the patch section :))
User avatar
DOSBox Moderator
Posts: 7757
Joined: 2002-10-03 @ 09:54
Location: Ludwigsburg

Re: Clipboard access from DosBox

Postby qv90 » 2007-6-12 @ 08:57

I moved all my patches to one place. Please refer to
Live long and prosper!
User avatar
Posts: 65
Joined: 2006-7-01 @ 10:22

Re: Clipboard access

Postby ar101 » 2012-7-10 @ 03:42

This clipboard patch sounds good. I wanted to be able to write an application in VBDOS that would run under DOSBox, and have it transfer data with a Windows application. I was thinking about putting a trap door in the DOSBox source code, and using it to transfer control to a Windows application. Seems like DOSBox intercepts internal commands in "dos_programs.cpp", in lines like:


It seems like it is there that it intercepts the command "IMGMOUNT.COM" from the command line and then transfers control to the function "IMGMOUNT_ProgramStart ()". So seems like I could drop in an extra command there, which could transfer control to a Windows app. Not sure what kind of side effects it would have, but seems like that would work.

It would be cool to be able to create a data type called 'DOSBox', where .Net applications could instantiate a DosBox object:

Dim myDOSBox As DOSBox
myDosBox = new DosBox ("config.bat")

The constructor would just start DOSBox with the config file. Then the trap door would suspend DOSBox and relinquish control to the calling application. Then the calling could transfer control back to the DOSBox program again, and back and forth.

Then, sub-routines could be written in VBDOS
Posts: 3
Joined: 2012-7-10 @ 03:24

Return to DOSBox Patches

Who is online

Users browsing this forum: No registered users and 1 guest