avx wrote:

This build has issues with atleast System Shock 1. With last years build it did not start, with the 20160327 build it now starts but cannot find the sound config. (I have it set to general midi + GUS)

Thanks for reporting the issue with System Shock 1! I have fixed the problem finding the sound config as you described (I have tested Sound Blaster and General MIDI, both worked now) in the 20160407 build. This 20160407 build also incorporated the changes from the latest DOSBox SVN r3979, and download links for the Windows binaries remain the same as previous versions. If you find any other issue please report it too. Thanks for your support.

I have updated the DOSBox SVN-lfn source and Windows binary to build 2016.09.26, which fixes some issue and also incorporates the changes from the latest DOSBox SVN version r3995. It now further contains LPTx port passthrough feature for printing support (see README.TXT inside the binary packages for more details). The download links for the Windows binary remains the same (i.e. http://bit.ly/12jANWF for the Visual Studio build and http://bit.ly/1laDvGX for the MinGW build), and the latest diff and source files changed from the latest DOSBox SVN version have been uploaded in the attachments (EDIT: please download the latest diff and source files from my next post).

Updated for DOSBox SVN 4006. Also added the APM power down feature to shut down DOSBox SVN-lfn and (for Windows) DOS APIs that communicate with the Windows clipboard directly (e.g. 4DOS's clipboard feature via the CLIP: device name will work). The source code changes have been attached.

Wengier wrote:

Updated for DOSBox SVN 4006. Also added the APM power down feature to shut down DOSBox SVN-lfn and (for Windows) DOS APIs that communicate with the Windows clipboard directly (e.g. 4DOS's clipboard feature via the CLIP: device name will work). The source code changes have been attached.

This(170905) build seems has bug when I start RICH3 with super slow motion. (20161007 build is fine)

EDIT: Oops. This is actually an old bug happens after r4000. A bug report is filed. https://sourceforge.net/p/dosbox/bugs/467/

I have updated the DOSBox SVN-lfn to match the latest DOSBox SVN version 4052 in the latest build, which should include the fix linked from the above post, and also new commands FOR and PROMPT are added to the build. The download links for the latest builds remain the same.

Does the SVN-lfn build include support for printing? I have a set of old games that I use DosBox to play - and they generate statistics that I'd love to be able to print.

Lemur21 wrote on 2019-03-14, 21:11:

Does the SVN-lfn build include support for printing? I have a set of old games that I use DosBox to play - and they generate statistics that I'd love to be able to print.

Yes, it does allow you to print via the LPT passthrough feature. Not a full-featured printing support like my vDosPlus though.

I have updated the DOSBox SVN-lfn to match the latest DOSBox SVN version 4334 in the latest build. The Windows binary is available from:

http://individual.utoronto.ca/wengier/files/d … box-svn-lfn.zip

And the changed source code files are available from:

http://individual.utoronto.ca/wengier/files/srcchanges.zip

LFN support has already been fully integrated into DOSBox-X with some improvements, so it is recommended to use DOSBox-X with the setting ver=7.1 for improved LFN support. The all in-one Windows installer for DOSBox-X 0.83.6 is available from:

DOSBox-X-0.83.6-setup.exe

@Weinger could you post a diff for SVN?

@fr500 There are later improvements for this feature in DOSBox-X, most notable LFN support on overlay and FAT drives. So it will require some work to back port such improvements for SVN.

And even if so, such "improvements" should perhaps be disabled by default and only be activated if desired (say via dosbox.conf or via DOS command).
I mean, just Imagine what happens if the media starts to advertise this change.
People not familiar with DOS would do all crazy sorts of things with path names (using spaces etc).
This surely would cause lots of confusion with older tutorials or newer tutorials with older DOSBox releases (or real MS-DOS).
Teaching people to take care of DOS' 8.3 naming scheme took ages, already.

@j022 also with DOSBox-X the LFN support is disabled by default. The two ways to activate it in DOSBox-X are to either set your reported DOS version to 7.0+ which corresponds to Win95. Or set [DOS] LNF=TRUE (defaults to AUTO, which means to activate when dos ver >= 7.0).

I would imagine that a backported patch would take a similar approach

@fr500,

I'm aware of how extensive the LFN changes are, and at least for me, back-porting it would be a non-trivial amount of work.

Are you able to share why DOSBox-X with already-working LFN support is unsatisfactory for your needs versus "SVN + backported-LFN"?