VOGONS


First post, by SueFoster

User metadata
Rank Newbie
Rank
Newbie

Wonder if you would be able to help. I have a very old database program which needed Windows XP 32 bit. Unfortunately it does not work on the 64 bit refurbished computer I have just purchased as a replacement for one that is faDosbox installed.

I can successfully mount y C Drive and the sub directory where my program resides but am having difficulty knowing how to insert those dosbox on exit e exe file so that my program initiates and also how to iinput the lines to ensure that dosbox exits when I close the rprgram rather that having to use the exit command. Any suggestion would be gratefully received.After running Dosbox, the dosbox emulator runs but the commnd line has returned to Z:\

I am entering the following command into the auto exec field on the dosbox options batch file. The folder is on my C Drive

MOUNT C C:\Recorder\Arev
This loads the C drive but does not run the software. I am not sure where to put the run command

Reply 1 of 20, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

Note before the mods clobber the topic.

Dosbox is not meant for using productivity software, or anything where data loss is going to be a considered factor.

It is for playing video games.

It does not fully emulate a period pc, it just does the parts games wanted.

The mods will surely clobber this thread as a result.

As for how to use the autoexec section of dosbox.conf...

You want the mount line, and the program invocation line, to be seperate lines.

[Autoexec]
mount c /somepath
C:
cd /somedeeperpath
someprogram.exe

All on different lines.

Reply 2 of 20, by SueFoster

User metadata
Rank Newbie
Rank
Newbie

Thanks for quick response. Although meant for gamers, I have been using it to successfully accessing data records which have been gathered over the last 40 years for entomological mapping purposes so perhaps the post will not be clobbered. My Windows XP died, by refurbished backup has been successfully utilised but is beginning to sound very tired. The latest backup computer runs on 64 bit which the original database proramme now 40 plus years old and irreplaceable cant use.

I hope your suggestion works, I will now try it.

Reply 3 of 20, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

No, really. I'm surprised the lock isn't on yet.

To understand why 'productivity software' is 'NOT SUPPORTED' [FULL STOP], one needs to remember or be aware that providing any kind of support places legal liability on the supporting organization in some jurisdictions.

Dosbox is explicitly provided without any waranty of any kind, and the creators of that software do not want anything to do with these kinds of implied liability.

They are sticklers about it because they have to be.

If you use dosbox this way, you do so on your own, with the full and express knowledge that this is so.

This is also why I answered in the general sense, and wont give specific support.

Reply 4 of 20, by feda

User metadata
Rank Member
Rank
Member
SueFoster wrote on 2025-10-29, 14:22:

Wonder if you would be able to help. I have a very old database program which needed Windows XP 32 bit.

Sounds like what you actually need is either VMware or Virtualbox.
Both are free, designed for productivity/enterprise applications such as yours and can run DOS and XP 32 bit.

Reply 5 of 20, by SueFoster

User metadata
Rank Newbie
Rank
Newbie

I am more than happy to work without any legal liability, the data is out own and the software programme was specifically designed for the collection of biological data for mapping purposes. It was developed on Advanced Revelation software which is no longer available so having to deal with legacy computers.

Reply 6 of 20, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

The main issue is that Dosbox only gives 'high level' / 'file level' data access, and some dos programs did silly low level stuff to work with files, especially database software.

This predisposes dosbox to corrupting these files when such programs try to do direct hardware accesses to hardware that is not emulated by dosbox, with 'unpredictable' results.

If you are well aware of this risk, and know your program is well behaved, then I would think it will work for you; just be aware that the dosbox devs will not be keen to look at some odd behavior induced by a non-game program.

For your use case, you want the dosbox C drive to get mounted, switch to the C drive, change the directory to where your database software lives, then run the program.

All of that can be done with the [autoexec] section of dosbox.conf.

https://www.dosbox.com/wiki/Dosbox.conf#.5Bautoexec.5D

Reply 7 of 20, by Matth79

User metadata
Rank Oldbie
Rank
Oldbie

If it needs XP 32 bit, I can't see how DOSBOX would help at all, I think regular DOSBOX can possibly run Windows 3.1, while DOSBOX-X can be persuaded to run Windows 95/98
----
Ah, I remembered NTVDM was needed for 16 bit Windows apps (like a 16 bit installer), TBH I never realised it had (limited) DOS capability

Last edited by Matth79 on 2025-10-30, 14:11. Edited 1 time in total.

Reply 8 of 20, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

I think it's more 'XP still had NTVDM, it could run in that.'

Reply 9 of 20, by DaveDDS

User metadata
Rank Oldbie
Rank
Oldbie

I constantly run XP stuff in "VMware Player 7" - It was free, and does a good job on XP.
I've been playing a bit with PCem ... Haven't tried XP yet, but I did get W98 running well.

DosBox is great for running DOS stuff, and I've heard rumors that it can be made to run W3.1 and possibly W98,
but I wouldn't expect it to run XP.

But it can be useful - I get stuff on/off my virtual machines using my own DDLINK. a very simple network file transfer
that doesn't need installation/setup, and I can run on DOS through XP (anything that can run a 16-bit code) .. but getting
access to files on a modern host can be tricky, I run DDLINK in DosBox on the host side - DosBox can access Host files
(if you mount things right), and some versions support an NE2000 NIC, accessable through a normal DOS packet driver.

Dave ::: https://dunfield.themindfactory.com ::: "Daves Old Computers"->Personal

Reply 10 of 20, by konc

User metadata
Rank l33t
Rank
l33t

Just as an idea to consider if you decide eventually that you don't want to go the dosbox way, you can always get a compact refurbished PC that is WinXP compatible for very little money. Yes they don't sell them with XP anymore but maybe someone knowledgeable enough can select it and install XP on it.

Or as already mentioned install XP in a VM like VirtualBox. You won't get the "click one icon and program starts" experience I understand you're after, but some compromises are necessary.

Reply 11 of 20, by SueFoster

User metadata
Rank Newbie
Rank
Newbie

thanks for all the answers, my program was built on Advanced Revelations (about 25) years ago and no longer have access to the developer) as a specialist natural history database system. It worked well on Windows XP and I have had it running using DOSbox up to a Windows 10/11. My problem has been that we had a XP machine isolated from all access to the internet which died but I had already purchased a refurbished XP computer as a backup but hadnt had to use it. Now needing to use it, it seems to be playing up so I bought another XP refurbished machine but setting it up is proving difficult so wanted to try using dosbox on it as I was unsure if it was 32 or 64 bit. Compromise is not possible unfortunately as 80 year olds can't easily adapt to new systems.

Reply 12 of 20, by konc

User metadata
Rank l33t
Rank
l33t

Well you never mentioned in your first post that you already got to run program under dosbox successfully, and this changes the scope a lot: It's only a matter of configuring dosbox to run it. People were worried that the program might not run at all using dosbox.

wierd_w's answer earlier in this thread is what you need to follow. In [autoexec] section and after your mount command add a couple more lines to run the program. If you don't know what is the executable's name or how to find it, we'll need a list of the program's folder contents.

Reply 13 of 20, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

I was more worried about

'using int13 interface to do disk io is slow, does not let me abuse hardware caching in the disk controller, if present, and does not let me squeeze every last processor slice out of the hardware like assuming direct control over the disk controller's io port does! This is DATABASE software, and time is MONEY!'

As it collides with

'Dosbox is really meant for, tailored for, and expressly presented for, playing video games. The file level access it gives is very high level, and as long as everything obeys normal dos io service routine conventions, our high level access methods work. It's not meant for full hardware emulation, please dont run stuff like that in dosboxm it's outside the use scope.'

With all the resulting chaos.

If this database software stays inside the box, and uses nothing but normal io service calls, and does not try silly hardware quirks to do stuff, it should run fine from dosbox.

There is just a very big risk that such software will want to squeeze every operational timeslice for the very maximum perf possible, and dosbox is not made to take that treatment. Strange Things(tm) are likely to happen if you try.

If this program works under dosbox, and does not crash randomly, or eat its own files, then you probably want either the [autoexec] section of dosbox.conf (if this is the only thing you expect to run with dosbox), or, you can inline all the mounting and invocation stuff with your shortcut/launcher.

To do the latter:

(Windows)

Create a shortcut to dosbox.exe
right click the shortcut and choose properties.
on the 'target' line, you should see a full path to dosbox.exe inside quotes. Just outside the quotes, you can append command line arguments. The -c argument accepts a command string enclosed in quotes, and can be used multiple times.

It should look something like this, after you append the needed bits:

Target: "C:\Program files(x86)\DosBox\dosbox.exe" -c "mount C C:\dosboxroot" -c "C:" -c "cd MyDBsoft" -c "MyDBsoft.exe"

Then click 'apply', then OK.

A similar invocation works with linux, using an .application file launcher. The same -c "some foo todo" syntax works.

Reply 14 of 20, by llm

User metadata
Rank Member
Rank
Member

My problem has been that we had a XP machine isolated from all access to the internet which died but I had already purchased a refurbished XP computer as a backup but hadnt had to use it. Now needing to use it, it seems to be playing up so I bought another XP refurbished machine but setting it up is proving difficult so wanted to try using dosbox on it as I was unsure if it was 32 or 64 bit. Compromise is not possible unfortunately as 80 year olds can't easily adapt to new systems.

you can have a full running XP 32 bit Windows on VMWare/VirtualBox even with file drag&drop on a new x64 Win11 system (but you need a XP license and all update packs etc.)
it will run faster compared to dosbox and more safe (due to the overall and not game oriented development of VMWare)

i would try to use at least Win7 x86 or Win8.1 x86 - maybe your program isnt graphical and runs also on these more recent OSes inside a virtual machine

but its still fine if dosbox works for you

Reply 15 of 20, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie
llm wrote on 2025-11-04, 15:38:
you can have a full running XP 32 bit Windows on VMWare/VirtualBox even with file drag&drop on a new x64 Win11 system (but you n […]
Show full quote

My problem has been that we had a XP machine isolated from all access to the internet which died but I had already purchased a refurbished XP computer as a backup but hadnt had to use it. Now needing to use it, it seems to be playing up so I bought another XP refurbished machine but setting it up is proving difficult so wanted to try using dosbox on it as I was unsure if it was 32 or 64 bit. Compromise is not possible unfortunately as 80 year olds can't easily adapt to new systems.

you can have a full running XP 32 bit Windows on VMWare/VirtualBox even with file drag&drop on a new x64 Win11 system (but you need a XP license and all update packs etc.)
it will run faster compared to dosbox and more safe (due to the overall and not game oriented development of VMWare)

i would try to use at least Win7 x86 or Win8.1 x86 - maybe your program isnt graphical and runs also on these more recent OSes inside a virtual machine

but its still fine if dosbox works for you

NTVDM (NT Virtual Dos Machine) was removed after XP, and windows needs that to run dos programs. It was also an integral part of running 16bit win3x applications on windows, using the WoW (Windows on Windows) wrapper.

As a result, win7 and newer cannot do those things, which is why we need things like dosbox to run vintage games.

Reply 16 of 20, by DaveDDS

User metadata
Rank Oldbie
Rank
Oldbie
wierd_w wrote on 2025-11-04, 15:46:

... NTVDM (NT Virtual Dos Machine) was removed after XP ...
As a result, win7 and newer cannot do those things ...

Not entirely true...

NTVDM was removed in 64-bit editions of Winblows.

I run native DOS applications in Windows7 all the time on one of my smaller Laptops.

The main thing is - That machine has only 3gb of RAM - and since everything I use in Windows is 32-bit, there was no advantage to using the 64-bit edition (and a big disadvantage in not being able to run my DOS tools directly) - so I installed 32-bit Win7. And DOS stull runs just as well as it did under XP.

Other that being able to run 16-bit code, it looks/feels exactly like my other Windows7 systems.

(and 32-bit Win7 works just as well in VMware)

Dave ::: https://dunfield.themindfactory.com ::: "Daves Old Computers"->Personal

Reply 17 of 20, by llm

User metadata
Rank Member
Rank
Member

@DaveDDS

does your Win7 32bit also works for graphical dos applications? mine seems to faile -> some message with missing nvdm extension
Windows 8.1 32bit failed for me running graphical DOS programs

Reply 18 of 20, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

Microsoft's vdm has known deficiencies in regard to Sound and VESA video trapping.

These are *why* vdmsound was created.

Reply 19 of 20, by DosFreak

User metadata
Rank l33t++
Rank
l33t++
llm wrote on Yesterday, 16:06:

@DaveDDS

does your Win7 32bit also works for graphical dos applications? mine seems to faile -> some message with missing nvdm extension
Windows 8.1 32bit failed for me running graphical DOS programs

You need to use video drivers using the XPDM driver model in Windows 7 for full screen NTVDM.
Windows 8.1 only supports WDDM video drivers. So you'd need to use something like solvbe or dgvoodoo (not 2) but they aren't worth bothering with for that purpose since development never continued and they don't work that well for that purpose.

How To Ask Questions The Smart Way
Make your games work offline