you're using dosbox for a day job. a bad idea to begin with.

QEMU, VirtualBox, VritualPC... ANYTHING else would be supported for your task, not DOSBox. DOSBox is for games. We only care about games.

The 2nd issue has been fixed in Dosbox svn. Whenever hal does a new megabuild that fix should be in.
Lei is rught though...

First, thank you for noting that issue 2 is resolved. That leaves me with one less problem for the long haul.

Now, I do understand that you feel that DOSbox is not a buisness class software, however across the Internet, many folks have pointed towards DOSbox being the ideal alternative for people who are having problems getting a DOS application running under Windows 7 64bit, especially when you note that I'm also connecting to a Windows 2008 Server.

Explanation: An issue exists where Server 2008 does not trust DOS machines at all. One can go through, and make some serious reductions in the security of their network, and make DOS work, but that is also hit or miss with the individual PCs from my personal experience thus far. DOSbox provides the connectivity layer to the network through it's interaction with the host, negating the need for network drivers, or security loopholes in the overall system.

leileilol was kind enough to provide some suggestions for alternatives above, however each of them runs the same concerns as above. I've spent a good 20-30 hours working this one issue, and DOSbox has been the cleanest and best approach... and actually, it's the first one that actually gets me to the network consistently on multiple machines... forgetting about the fact that the others require greater risk to the network.

So, you like it for fixing games, and hey, I love to play games too, but if I could use an Xbox to fix this problem, or perhaps a bunch of Lego bricks, a yo-yo, tinkertoys, or even pink fuzzy bunny slippers... I would. (OK, let's pretend I didn't say anything about the slippers!)

BRCConsultations wrote:

Now, I do understand that you feel that DOSbox is not a buisness class software, however across the Internet, many folks have pointed towards DOSbox being the ideal alternative for people who are having problems getting a DOS application running under Windows 7 64bit, especially when you note that I'm also connecting to a Windows 2008 Server.

About 60 years ago lobotomies were also widely recommended for a number of problems.

On previous occasions, it has been noted that DOSBox is in some ways sufficiently inaccurate (such as in floating point math) that even though you may not notice anything wrong while running a game, it could feasibly make an error in some mission-critical application with drastic consequences. Thus, it is not recommended for business software.

Anyway, I'm not familiar with virtual printing in DOSBox, but if it came down to inserting a single line feed at the top of the output, I would use it to print to a PDF (using PDFill or one of many other free PDF generators) and then write a Python script of some sort to manipulate the PDF afterwards.

Using Dosbox is discouraged, AFAIK, because as Jorpho wrote, dosbox is not 100% correct in some stuff and the developers want to make that very clear to businesses. No guaranty at all for mission critical stuff. I CAN understand that you want to use it though, it's easy to setup and copy that setup to other machines and and and... 😀
This is the part where I like to point business users that still want to use it despite warnings, that you can donate some money to the devs as you are saving much money through the help of dosbox 😉