I have the Steam release of X-Wing and am attempting to use DOSBox-X with it instead of the included DOSBox 0.74 release for among other things, MT-32 support. The problem is that for some reason only the X axis of my joystick/controller works ingame.

I've tried every 'joysticktype', turning 'timed' on and off and all sorts of messing around with the axis bindings but I just can't seem to get the game to recognize the Y axis. The weirdest part is that if I check the mapper tool or the joystick testing utilities from this thread the Y axis appears to be recognized just fine. It also works without issue ingame with DOSBox classic.

Edit: I learned about the existence of DOSBox Staging from this thread and was able to get the game running with MT-32 music and working joystick support, so that solves my problem. It's still weird that DOSBox-X has this issue though.

I recently downloaded and installed the May 2023 release of DOSBox-X (Windows SDL1) and have a question about the PC speaker settings.

I am wondering why it defaults to the rate of 65536 in the conf file that is generated when I performed a fresh install of DOSBox-X? In the wiki it says the default value is recommended to be 44100, and I cannot find any commentary on why the 65536 rate is now offered? Is it going to make any difference at all if I set it back to 44100 or leave the new default value in place?

almeath wrote on 2023-09-03, 17:40:

I recently downloaded and installed the May 2023 release of DOSBox-X (Windows SDL1) and have a question about the PC speaker settings.

I am wondering why it defaults to the rate of 65536 in the conf file that is generated when I performed a fresh install of DOSBox-X? In the wiki it says the default value is recommended to be 44100, and I cannot find any commentary on why the 65536 rate is now offered? Is it going to make any difference at all if I set it back to 44100 or leave the new default value in place?

65536Hz provides some better rendition but there's no reason you couldn't set it back to 44.1KHz.

There is also a new September 2023 release.

TheGreatCodeholio wrote on 2023-09-04, 05:59:

There is also a new September 2023 release.

Thanks. I just downloaded it. I will try out the 65536 rate and see how I go. Generally, I go with the highest rate available because while not always authentic, I like having the best sound quality.

K.A.R.R. wrote on 2023-05-10, 20:51:

just tested dosbox-x-mingw-win64-20230509035144 […]
Show full quote

just tested dosbox-x-mingw-win64-20230509035144

its working again with cycles=max
cycles are more or less constant at around 250.000
and playback is smoothly

compared to old 20221226190454
cycles are higher around 230.000 - 260.000 compared to 140.000 - 145.000

thx for the fast fix 😀

just tested latest dosbox-x version and the bug from version 2023.05.01 is there again 🙁
it was fixed with svn version
but with latest dosbox-x and max cycles playback with libopenmpt is broken again
(cycles fluctuate again from 250k down to 80k causing audio slow downs)

Rincewind42 wrote on 2023-07-15, 04:21:

Hi K.A.R.R. […]
Show full quote

K.A.R.R. wrote on 2023-05-18, 17:54:

hi may be you can take a look at a small problem with gus and midi playback […]
Show full quote

hi
may be you can take a look at a small problem with gus and midi playback

with standard patches (from latest driver 4.11) midi playback
for e.g. with playmidi.exe
is fine.
but when i use ppl 1.61 (pro patches lite 1.61)
some instruments are incorrectly looped.

dosbox, x, staging and pcem all have this problem
(x, staging and pcem have even more looping problems than normal dosbox with ppl1.61)

BUT with a real gus and the pro patches lite there is no looping error
means the patches are not the problem.

seems there is a bug in midi playback when using the ppl 1.61 patches with dosbox.
would be great if this could be fixed

here some test midis and a recording of the problem
https://www.mediafire.com/file/kfrhzm8720anw2 … ditest.zip/file

Hi K.A.R.R.

I would love to fix this. I suspected this was an emulation problem...

Can you please raise a ticket in our issue tracker on GitHub for this with all relevant info? I don't have a GUS anymore, so every bit of info helps.

DOSBox Staging issue tracker
https://github.com/dosbox-staging/dosbox-staging/issues

Thanks!

done

hope it can be fixed 😀

Attached is code to implement a gamma level modifier for cases where the input color depth is 8 bpp. It was only tested against 32-bit color output and in VGA, but may work in other cases. It is for testing only and based on the assumption that the modified red/green/blue values are 6-bit values, even though they are stored in 8-bit variables. Also, the background code is expected to differ from -X and SVN, so manual application of the patch is likely required (dependent on SVN method of 6-bit RGB values). The patch is self-documenting.

The patch is modified from the previous version based on a recollection of a post by ripsaw about rgb palette changes. In this case, if dosbox is running, then changing the gamma level will not affect the gamma level on screen until the next palette update in the game.

Hello everyone! New to the forum and discovering all this amazing world of vintage PC emulation, I was quite surprised to see how much the scene moved forward, with even 3dfx emulation on PCEM, Dosbox-X, 86Box etc...

Talking about dosbox-x, i am trying to run Unreal Gold but no dice. Opened this bug report : https://github.com/joncampbell123/dosbox-x/issues/4516

But maybe it is something know (or bad config) and I am making everyone lose time 😀

K.A.R.R. wrote on 2023-09-04, 17:48:

just tested latest dosbox-x version and the bug from version 2023.05.01 is there again :-( it was fixed with svn version but wit […]
Show full quote

K.A.R.R. wrote on 2023-05-10, 20:51:

just tested dosbox-x-mingw-win64-20230509035144 […]
Show full quote

just tested dosbox-x-mingw-win64-20230509035144

its working again with cycles=max
cycles are more or less constant at around 250.000
and playback is smoothly

compared to old 20221226190454
cycles are higher around 230.000 - 260.000 compared to 140.000 - 145.000

thx for the fast fix 😀

just tested latest dosbox-x version and the bug from version 2023.05.01 is there again 🙁
it was fixed with svn version
but with latest dosbox-x and max cycles playback with libopenmpt is broken again
(cycles fluctuate again from 250k down to 80k causing audio slow downs)

the bug is still present in latest dosbox-x
tested with dosbox-x-vsbuild-win64-20231007055223
i guess that this could also cause problems with some games running with auto or max cycles setting

so i recommend using a fixed cycle setting (not max or auto) with dosbox-x
how many cycles you can use depends on host cpu

Hey All, Not sure if this is the correct forum, but I tried dosbox to move out of an old environment. This kinda worked, but much of the functionality was lost. I saw something here on this forum in regards to dosbox-x. This 90% works for my needs

Task? Move an old program called OAii which is essentially a Access 2.1

The application itself is works well in doxbox-x (thanks), but the printing function errors out with "infoe.prt" could not be found. Welp, its most definitely in the U directory as defined. Any thoughts on whats wrong? Here is my config - i Mount 2 drives, F (where the data is) and U (the working directory Userfolder). The current functionality in the "XP" environment is the user selects the data file (working) and selects print (not working) which initiates a "save to file" to the users U drive.

# This is the configuration file for DOSBox-X 2023.10.06. (Please use the latest version of DOSBox-X)
# Lines starting with a # are comment lines and are ignored by DOSBox-X.
# They are used to (briefly) document the effect of each option.
# To write out ALL options, use command 'config -all' with -wc or -writeconf options.

[sdl]

fullscreen = false
fulldouble = false
fullresolution = desktop
windowresolution = original
windowposition =
display = 0
output = ttf
videodriver =
transparency = 0
maximize = false
autolock = false
autolock_feedback = beep
middle_unlock = manual
clip_mouse_button = right
clip_key_modifier = shift
clip_paste_bios = default
clip_paste_speed = 30
sensitivity = 100
usesystemcursor = false
mouse_emulation = locked
mouse_wheel_key = -1
waitonerror = true
priority = higher,normal
mapperfile = mapper-dosbox-x.map
usescancodes = auto
overscan = 0
titlebar = OAii
showbasic = false
showdetails = false
showmenu = false

[log]

logfile =
debuggerrun = debugger

[dosbox]

#
language =
title =
fastbioslogo = true
startbanner = false
bannercolortheme = default
dpi aware = auto
quit warning = auto
working directory option = default
working directory default =
show advanced options = false
resolve config path = true
hostkey = mapper
mapper send key = ctrlaltdel
ime = auto
synchronize time = false
machine = svga_s3
captures = capture
autosave =
saveslot = 1
savefile =
saveremark = true
forceloadstate = false
a20 = mask
memsize = 16
nocachedir = false
freesizecap = cap
convertdrivefat = true

[render]

frameskip = 0
aspect = false
aspect_ratio = 0:0
char9 = true
euro = -1
doublescan = true
scaler = normal2x
glshader = none
pixelshader = none
autofit = true
monochrome_pal = green

[pc98]

pc-98 BIOS copyright string = false
pc-98 fm board = auto
pc-98 enable 256-color = true
pc-98 enable 16-color = true
pc-98 enable grcg = true
pc-98 enable egc = true
pc-98 bus mouse = true
pc-98 force ibm keyboard layout = auto
pc-98 try font rom = true
pc-98 anex86 font =

[dosv]

dosv = off
getsysfont = true
fontxsbcs =
fontxsbcs16 =
fontxsbcs24 =
fontxdbcs =
fontxdbcs14 =
fontxdbcs24 =
showdbcsnodosv = auto
yen = false
fepcontrol = both
vtext1 = svga
vtext2 = xga
use20pixelfont = false
j3100 = off
j3100type = default
j3100colorscroll = false

[video]

vmemsize = -1
vmemsizekb = 0
high intensity blinking = true
memory io optimization 1 = true
scanline render on demand = auto

[vsync]

vsyncmode = off
vsyncrate = 75

[cpu]

core = auto
fpu = true
rdtsc rate = 0
segment limits = true
cputype = auto
cycles = auto
cycleup = 10
cycledown = 20
turbo = false
apmbios = true
integration device = false
isapnpbios = true

aux = true
allow output port reset = true
controllertype = auto
auxdevice = intellimouse

[ttf]

font =
fontbold =
fontital =
fontboit =
colors =
outputswitch = auto
winperc = 60
ptsize = 0
lins = 0
cols = 0
righttoleft = false
wp =
bold = true
italic = true
underline = true
strikeout = false
printfont = true
autodbcs = true
blinkc = true
gbk = false
chinasea = false
dosvfunc = false

[voodoo]

voodoo_card = auto
voodoo_maxmem = true
glide = false
lfb = full_noaux
splash = true

[mixer]

nosound = false
sample accurate = false
swapstereo = false
rate = 48000
blocksize = 1024
prebuffer = 25

[midi]

mpu401 = intelligent
mpubase = 0
mididevice = default
midiconfig =
samplerate = 48000
mpuirq = -1
mt32.romdir =
mt32.model = auto
fluid.driver = default
fluid.soundfont =

[sblaster]

sbtype = sb16
sbbase = 220
irq = 7
listen to recording source = false
recording source = silence
dma = 1
hdma = 5
enable speaker = false
sbmixer = true
oplmode = auto
oplemu = default
oplrate = 48000
oplport =
retrowave_bus = serial
retrowave_port =
hardwarebase = 220
goldplay = true
blaster environment variable = true

[gus]

gus = false
gusrate = 48000
gusmemsize = -1
gus master volume = 0.00
gusbase = 240
gusirq = 5
gusdma = 3
gustype = classic
ultradir = C:\ULTRASND

[innova]

innova = false
samplerate = 22050
sidbase = 280
quality = 0

[imfc]

[speaker]

pcspeaker = true
pcrate = 65536
tandy = auto
tandyrate = 48000
disney = false
ps1audio = off
ps1audiorate = 22050

[joystick]

joysticktype = auto
timed = true
autofire = false
swap34 = false
buttonwrap = false

[serial]

serial1 = dummy
serial2 = dummy
serial3 = disabled
serial4 = disabled
serial5 = disabled
serial6 = disabled
serial7 = disabled
serial8 = disabled
serial9 = disabled
phonebookfile = phonebook-dosbox-x.txt

[parallel]

# parallel2: see parallel1
# parallel3: see parallel1
# parallel4: see parallel1
# parallel5: see parallel1
# parallel6: see parallel1
# parallel7: see parallel1
# parallel8: see parallel1
# parallel9: see parallel1
# dongle: Enable dongle
parallel1 = printer
parallel2 = disabled
parallel3 = disabled
parallel4 = disabled
parallel5 = disabled
parallel6 = disabled
parallel7 = disabled
parallel8 = disabled
parallel9 = disabled
dongle = false

[printer]
# printer: Enable printer emulation.
# dpi: Resolution of printer (default 360).
# width: Width of paper in 1/10 inch (default 85 = 8.5'').
# height: Height of paper in 1/10 inch (default 110 = 11.0'').
# printoutput: Output method for finished pages:
# png : Creates PNG images (default)
# ps : Creates PostScript
# bmp : Creates BMP images (very huge files, not recommended)
# printer : Send to an actual printer in Windows (specify a printer, or Print dialog will appear)
# multipage: Adds all pages to one PostScript file or printer job until CTRL-F2 is pressed.
# device: Specify the Windows printer device to use. You can see the list of devices from the Help
# menu ('List printer devices') or the Status Window. Then make your choice and put either
# the printer device number (e.g. 2) or your printer name (e.g. Microsoft Print to PDF).
# Leaving it empty will show the Windows Print dialog (or '-' for showing once).
# docpath: The path (directory) where the output files are stored.
# fontpath: The path (directory) where the printer fonts (courier.ttf, ocra.ttf, roman.ttf, sansserif.ttf, script.ttf) are located.
# openwith: Start the specified program to open the output file.
# openerror: Start the specified program to open the output file if an error had occurred.
# printdbcs: Allows DOSBox-X to print Chinese/Japanese/Korean DBCS (double-byte) characters when these code pages are active.
# If set to auto (default), this is enabled only for the TrueType font (TTF) output with the DBCS support enabled.
# Only applicable when using a DBCS code page (932: Japanese, 936: Simplified Chinese; 949: Korean; 950: Traditional Chinese)
# Possible values: true, false, 1, 0, auto.
# shellhide: If set, the command window will be hidden for openwith/openerror options on the Windows platform.
# timeout: (in milliseconds) if nonzero: the time the page will be ejected automatically after when no more data arrives at the printer.
printer = true
dpi = 360
width = 85
height = 110
printoutput = printer
multipage = false
device = -
docpath = .
fontpath = FONTS
openwith =
openerror =
printdbcs = auto
shellhide = false
timeout = 0

[dos]

xms = true
xms handles = 0
shell configuration as commands = false
hma = true
hard drive data rate limit = 0
floppy drive data rate limit = 0
ansi.sys = true
log console = false
share = true
file access tries = 3
network redirector = true
minimum mcb free = 0
ems = true
umb = true
quick reboot = false
ver = 5.0
lfn = auto
fat32setversion = ask
shellhigh = auto
automount = true
automountall = false
mountwarning = true
autofixwarning = false
startcmd = false
starttranspath = true
startwait = true
startquiet = false
vmware = true
int33 = true
mouse report rate = 0
keyboardlayout = auto
customcodepage =
dbcs = true
dos clipboard device enable = false
dos clipboard device name = CLIP$
dos clipboard api = true
dos idle api = true

[ipx]

ipx = false

[ne2000]

ne2000 = false
nicbase = 300
nicirq = 3
macaddr = random
backend = auto

[ethernet, pcap]

realnic = list
timeout = default

[ethernet, slirp]

ipv4_network = 10.0.2.0
ipv4_netmask = 255.255.255.0
ipv4_host = 10.0.2.2
ipv4_nameserver = 10.0.2.3
ipv4_dhcp_start = 10.0.2.15

[ide, primary]

enable = true
pnp = true

[ide, secondary]
enable = true
pnp = true

[ide, tertiary]
enable = false
pnp = true

[ide, quaternary]
enable = false
pnp = true

[ide, quinternary]
enable = false
pnp = true

[ide, sexternary]
enable = false
pnp = true

[ide, septernary]
enable = false
pnp = true

[ide, octernary]
enable = false
pnp = true

[fdc, primary]

enable = false
pnp = true
mode = ps2

[4dos]
rem = This section is the 4DOS.INI file, if you use 4DOS as the command shell

[config]

rem = This section is DOS's CONFIG.SYS file, not all CONFIG.SYS options supported
break = off
numlock =
shell =
dos = high, umb
fcbs = 100
files = 200
country =
lastdrive = U
set path = Z:\;Z:\SYSTEM;Z:\BIN;Z:\DOS;Z:\4DOS;Z:\DEBUG;Z:\TEXTUTIL
set prompt = $P$G
set temp =
install =
installhigh =
device =
devicehigh =

[autoexec]
# Lines in this section will be run at startup.
# You can put your MOUNT lines here.
mount u U:\OAII
mount f F:\
U:
spi.exe p=F:\Database\oaii
Exit

@Armoredgoat

Try this and see if it works for you.

https://dosbox-x.com/wiki/Guide%3ASetting-up- … _a_real_printer

I hope this is not the wrong section to ask, but is there a way to get DOSBox-X to horizontally blend pixels in the CGA color composite mode? It looks like this when I run Flight Simulator 2.1x (and 1.0x):

However, I want it to look like this:

hi guys, someone can tell me because on dosbox-x reshade shader (opengl or directx9) done strange effects, i have dosbox 4:3 on 16:9display but effects like bloom or curvature crt spread on all the display, like isn't a real 4:3 resolution, aren't real borders. reshade work fine on other builds like dosbox pure or ECE or dosboxcrt by matthias....i have tried both x32 x64 mingw and vstudio build nothing....dosbox-x have much functionality but without reshade i can't use it 😒
if i use built in shader effect , i can't set parameters like reshade

I've got a PCL and PS capable printer, that should be able to print if configured as a generic PCL or PS one (i.e.: Laserjet 2100). I thought that I could configure it using something like "file=\\x.x.x.x\print", but sadly that printer has no SMB support.

Is there any means to dump directly data to his network port 9100?

my dosbox-x has issues with Archimedian dynasty 3dfx
i am trying to use dgvoodoo2 in it but i get screen problems

I decided to test out the DOSBox-X version on my 2018 Macbook pro (Intel) and I ran into what looks like a packaging problem. It crashed immediately and the report below suggests it tries to load an ARM library on the x86_64 build.

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process: dosbox-x [15121]
Identifier: com.dosbox-x
Version: 2023.10.06 (2023.10.06)
Code Type: X86-64 (Native)

OS Version: macOS 14.3.1 (23D60)
Report Version: 12

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace DYLD, Code 1 Library missing
Library not loaded: @executable_path/arm64/libslirp.0.dylib
Referenced from: <1CCA865A-7A92-3A3A-BC45-173011993719> /Users/Shared/*/dosbox-x.app/Contents/MacOS/dosbox-x
Reason: tried: '/Users/Shared/Games/DOS/dosbox-x-macosx-x86_64-20231006231157/dosbox-x/dosbox-x.app/Contents/MacOS/arm64/libslirp.0.dylib' (no such file), '/usr/local/lib/libslirp.0.dylib' (no such file), '/usr/lib/libslirp.0.dylib' (no such file, not in dyld cache)
(terminated at launch; ignore backtrace)

This bug is fixed in the latest nightlies, in case anyone runs into the same thing.

Hopefully, this is the right place to ask this, this time. Anyway:

Curious as how to use the OPEN COM statement found in many older BASIC dialects I wrote this quick piece of code based on an example:

1 OPEN "COM1:9600,N,8,1,BIN" FOR OUTPUT AS #1
2  PRINT #1, "Hi!"
3 CLOSE #1

In my DOSBox-X config file I have this line:

1serial1       = file file:output1.txt timeout:1000 openwith:notepad

DOSBox-X appears to give no errors and my code runs without errors, however no output1.txt file appears to have been created. Could someone more familiar with the specifics of redirecting serial port communication in DOBox-X point me in the right direction?

Solved:
https://www.vbforums.com/showthread.php?90286 … SBox-X-question

Excuse me, if I'm asking in the wrong thread for advise.

I'm trying DOSBox-X for Linux (unfortunately there are only snap or flatpak packages for the distros I've tried and yeah, I hate this kind of software installations) and I can't mount any directory structure as "DOS drive letter" from "Autoexec.bat" configuration.

I try to use "mount c /media/{USER}/{linux mounted storage}/{directory}" and this produces empty "C: DOS drive", but this works for original DOSBox for Linux.

What is wrong here?

analog_programmer wrote on 2024-07-09, 08:16:

Excuse me, if I'm asking in the wrong thread for advise. […]
Show full quote

Excuse me, if I'm asking in the wrong thread for advise.

I'm trying DOSBox-X for Linux (unfortunately there are only snap or flatpak packages for the distros I've tried and yeah, I hate this kind of software installations) and I can't mount any directory structure as "DOS drive letter" from "Autoexec.bat" configuration.

I try to use "mount c /media/{USER}/{linux mounted storage}/{directory}" and this produces empty "C: DOS drive", but this works for original DOSBox for Linux.

What is wrong here?

That is correct. You mounted another drive. C: is empty as all Dosbox-X files are on your Z: drive.

If your directory is not empty and you don't see them on C: then that is another problem though. Never tried it on Linux so can't help with that. I set nocachedir to true in the conf file btw as sometimes copied over files only showed up after a Dosbox-X restart.