DOSBoxWiki - User contributions [en]

Performance

2016-01-24T19:28:37Z

Tertz2:

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

It's rough speed level of emulated CPU for different host CPUs. For core=dynamic (cycles=max), while core=normal may to be 5 times slower. Different applications, even their parts, may have different this dependency. An application's and the emulator's settings affect too, - for example, sound's settings.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium Pro 200 MHz||286 6 MHz
|-
||Pentium II 350 MHz||386SX 25 MHz
|-
||Pentium III 1.0 GHz||486 66 MHz
|-
||Pentium 4 3.0 GHz||Pentium 133 MHz
|-
||Core 2 Duo 3.3 GHz||Pentium II 300 MHz
|-
||Core i5 4xxx 4.0 GHz||Pentium III 500 GHz
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14] and other.

 
Rough dependency between cycles and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||315
|-
||286 12.5 MHz||2750
|-
||386 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|-
||Pentium II 300||200000
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14]

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

== Other benchmarks ==
* [http://web.archive.org/web/20160124191939/http://ftp.sac.sk/sac/utildiag/snoop344.zip Snooper 3.44] ([http://web.archive.org/web/20090213132356/http://mastodonpc.tripod.com/bench/snooper.html chart])

Performance

2015-12-08T21:50:24Z

Tertz2: /* Emulated CPU equivalency */

Performance

2015-11-25T16:30:02Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

It's rough speed level of emulated CPU for different host CPUs. For core=dynamic (cycles=max), while core=normal may to be 10 times slower. Different applications, even their parts, may have different this dependency. An application's and the emulator's settings affect too, - for example, sound's settings.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium Pro 200 MHz||286 6 MHz
|-
||Pentium II 350 MHz||386SX 25 MHz
|-
||Pentium III 1.0 GHz||486 66 MHz
|-
||Pentium 4 3.0 GHz||Pentium 133 MHz
|-
||Core 2 Duo 3.3 GHz||Pentium II 300 MHz
|-
||Core i5 4xxx 4.0 GHz||Pentium III 500 GHz
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14] and other.

 
Rough dependency between cycles and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||315
|-
||286 12.5 MHz||2750
|-
||386 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|-
||Pentium II 300||200000
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14]

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-11-22T13:00:20Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

It's rough speed level of emulated CPU for different host CPUs. For core=dynamic (cycles=max), while core=normal may to be 10 times slower. Different applications, even their parts, may have different this dependency. An application's and the emulator's settings affect too, - for example, sound's settings.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium Pro 200 MHz||286 6 MHz
|-
||Pentium II 350 MHz||386SX 25 MHz
|-
||Pentium III 1.0 GHz||486 66 MHz
|-
||Pentium 4 3.0 GHz||Pentium 133 MHz
|-
||Core 2 Duo 3.3 GHz||Pentium II 300 MHz
|-
||Core i5 4xxx 4.0 GHz||Pentium III 1 GHz
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14] and other.

 
Rough dependency between cycles and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||315
|-
||286 12.5 MHz||2750
|-
||386 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|-
||Pentium II 300||200000
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14]

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-11-03T22:17:09Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower. Different applications, even their parts, may have different this dependency. An application's and the emulator's settings affect too, - for example, for a sound.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 350 MHz||386SX 25 MHz
|-
||Pentium III 1.0 GHz||486 66 MHz
|-
||Pentium 4 3.0 GHz||Pentium 133 MHz
|-
||Core 2 Duo 3.3 GHz||Pentium II 300 MHz
|-
||Core i5 4xxx 4.0 GHz||Pentium III 1 GHz
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14] and other.

 
Rough dependency between cycles and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||315
|-
||286 12.5 MHz||2750
|-
||386 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|-
||Pentium II 300||200000
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14]

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-10-24T22:12:06Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower. Different applications, even their parts, may have different this dependency. An application's and the emulator's settings affect too, - for example, for a sound.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 350 MHz||386SX 25 MHz
|-
||Pentium III 1.0 GHz||486 66 MHz
|-
||Pentium 4 3.0 GHz||Pentium 133 MHz
|-
||Core 2 Duo 3.3 GHz||Pentium II 300 MHz
|-
||Core i5 4xxx 4.0 GHz||Pentium III 1 GHz
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14] and other.

 
Rough dependency between cycles and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||310
|-
||286 12.5 MHz||2750
|-
||386 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|-
||Pentium II 300||200000
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14]

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-10-24T21:47:45Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower. Different applications, even their parts, may have different this dependency. The emulator's settings affect too.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 350 MHz||386SX 25 MHz
|-
||Pentium III 1.0 GHz||486 66 MHz
|-
||Pentium 4 3.0 GHz||Pentium 133 MHz
|-
||Core 2 Duo 3.3 GHz||Pentium II 300 MHz
|-
||Core i5 4xxx 4.0 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14] and other.

 
Rough dependency between cycles (core=normal) and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||310
|-
||286 12.5 MHz||2750
|-
||386 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14]

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-10-22T22:23:04Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower. Different applications, even their parts, may have different this dependency. The emulator's settings affect too.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 350 MHz||386SX 25 MHz
|-
||Pentium III 1.0 GHz||486 66 MHz
|-
||Pentium 4 3.0 GHz||Pentium 166 MHz
|-
||Core 2 Duo 3.3 GHz||Pentium II 300 MHz
|-
||Core i5 4xxx 4.0 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14] and other.

 
Rough dependency between cycles (core=normal) and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||310
|-
||286 12.5 MHz||2750
|-
||386 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|}
''Note'': Based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14]

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-10-18T17:34:17Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 400 MHz||386
|-
||Pentium III 1.0 GHz||486 66 MHz
|-
||Athlon XP 1.8 GHz||Pentium
|-
||Pentium 4 3.0 GHz||Pentium 166 MHz
|-
||Athlon 64 1.8 GHz||Pentium II
|-
||Core 2 Duo 8xxx 3.3 GHz||Pentium II 450 MHz
|-
||Core i5 4xxx 4.0 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
''Note'': Based (generally) on [http://web.archive.org/web/20070127180145/http://www.gamers.org/pub/idgames/idstuff/quake/quake106.zip Quake 1.06] fps.

 
Rough dependency between cycles (core=normal) and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||310
|-
||286 12.5 MHz||2750
|-
||386 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|}
''Note'': Cycles are based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test Benchmark 1.14] by R. Agababyan

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

KEYB

2015-09-13T19:40:36Z

Tertz2:

=Introduction=

Keyb is used to change the layout of the keyboard used for different countries.

=Syntax=

Configures a keyboard for a specific language.

<blockquote><tt>
KEYB [keyboard layout code/id]
</tt></blockquote>

For example the following will set your keyboard layout to a Swedish keyboard:

<blockquote><tt>
KEYB sv
</tt></blockquote>

or for not default character set:

<blockquote><tt>
KEYB sv 437
</tt></blockquote>

The keyboard layout can also be set in [[dosbox.conf]] (see [[Configuration:DOS]]), so it can also be set with the internal CONFIG command:
<blockquote><tt>
CONFIG -set dos keyboardlayout [keyboard layout code/id]
</tt></blockquote>

=Layout codes=

<pre> Keyboard Character Keyboard Country or
layout set identification language
------------------------------------------------------------------
be 850, 437 120 Belgium
br 850, 437 Brazil
cf 850, 863 058 Canadian-French
cz 852, 850 Czechoslovakia (Czech)
sl 852, 850 Czechoslovakia (Slovak)

dk 850, 865 159 Denmark
su 850, 437 153 Finland
fr 850, 437 120, 189 France
gr 850, 437 129 Germany
hu 852, 850 Hungary

it 850, 437 141, 142 Italy
la 850, 437 171 Latin America
nl 850, 437 143 Netherlands
no 850, 865 155 Norway
pl 852, 850 Poland

po 850, 860 163 Portugal
ru 866 Russian
sp 850, 437 172 Spain
sv 850, 437 153 Sweden
sf 850, 437 150 Switzerland (French)
sg 850, 437 000 Switzerland (German)

uk 850, 437 166, 168 United Kingdom
us 850, 437 103 United States
dv103 850, 437 104 United States (Dvorak)
yu 852, 850 Yugoslavia (Serbo-Croatian)
</pre>

See also [http://support.microsoft.com/en-en/kb/117850 MS-DOS 6.22 Country.txt]

4.77 MHz

2015-09-11T10:39:09Z

Tertz2: /* Other tools */

The IBM PC XT ran at 4.77 MHz. This describes how to run DOSBox at XT-like speeds for programs that do not perform their own timing. Keep in mind that DOSBox cannot run at exactly 4.77 MHz. At least, not exactly the way an IBM PC XT did. You can, however, get pretty darn close by testing with some benchmark tools.

As you will see in the testing below, various types of computer instructions run at widely various speeds on the different types of computer chips out there. The most striking example is perhaps math instructions that involve real numbers such as: 1.1 x 2.2 = 2.42. This is called floating-point math. Floating-point instructions were extremely slow on the 8086 CPU unless you installed the optional 8087 co-processor. It wasn't until the Pentium age that floating-point hardware was built into all PC CPU's. Anyway, the point is that DOSBox has only one speed control, and it slows down all computer instructions by the same percentage (more or less). It is therefore not possible to tell DOSBox to slow integer math by X%, floating-point math by Y%, and non-math by Z%, etc. Near-perfect 4.77 MHz speed will not be possible until someone builds an XT emulator specifically for this purpose. This is not likely to happen because close enough will always be, quite frankly, good enough.

== Searching for 4.77 MHz (XT) ==

[ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/mips.zip MIPS 1.10] is accurate and easy tool in the quest for 4.77 MHz.

From MIPS.DOC:
<code>
FUNCTIONS: Measures Million(s) of Instructions Per Second

(1) General Instructions - random
(2) Integer Instructions - ADD SUB MUL DIV
(3) Memory to Memory - MOV RAM to RAM
(4) Register to Register - MOV REG to REG
(5) Register to Memory - MOV REG to RAM
(6) Performance Rating - average
</code>

Running MIPS produces a screen similar to this:
<code>
+---------------------------------------------------+
| MIPS v1.10 CPU Benchmark and Performance Test |
+-----------------------------------------------------------+
| | Million Instructions Per Second | 10:10:00 |
+-----------------------------------------------------------+
| BENCHMARK: | IBM/XT IBM/AT COMPAQ | |
| | 4.7Mhz 8Mhz 386 | MIPS |
|----------------------|----------------------------|-------|
| General Instructions | 25.83 7.51 3.79 | 4.29 |
| Integer Instructions | 16.92 2.64 1.16 | 2.85 |
| Memory to Memory | 7.79 2.40 1.34 | 1.85 |
| Register to Register | 18.07 2.35 0.98 | 3.25 |
| Register to Memory | 20.72 6.22 3.43 | 6.39 |
| | | |
| Performance Rating | 18.24 4.40 2.16 | 3.72 |
+-----------------------------------------------------------+
</code>

'''''Note:''' If you run MIPS at too high a speed, the numbers will get large enough to screw up the formatting and make the results mostly unreadable.''

=== Steps to Find 4.77 MHz ===

#Download MIPS and place it in an easy-to-find folder. (I created a DOSTOOLS folder inside my DOSBOX folder.)
#Make these changes to your [[dosbox.conf]] file:
#:[[dosbox.conf#.5Bsdl.5D|[sdl]]]
#:fullscreen=false
#:[[dosbox.conf#.5Bcpu.5D|[cpu]]]
#:cycles=300
#:cycleup=1
#:cycledown=1
#:[[dosbox.conf#.5Bautoexec.5D|[autoexec]]]
#:mount C "C:\Program Files\DOSBox\DOSTools\"
#:C:
#[[Basic Setup and Installation of DosBox|Launch]] DOSBox. Then run MIPS from the [[Command Line|command line]].
#Your goal is to get the Performance Rating in the IBM/XT column to equal 1.00. To do this, press [[Special Keys|Ctrl-F11]] (slow down) or [[Special Keys|Ctrl-F12]] (speed up) several times while watching the CPU Cycles in DOXBox’s [[:file:Dosbox2.jpg|title bar]] change from 300 to your next test value.
#Run MIPS again. Repeat steps 4 and 5 until you get a Performance Rating of 1.00
#Make a note of your final CPU Cycles value and set "cycles=xxx" to this value in your dosbox.conf whenever you need 4.77-MHz-like speed.

You should get something like:

''core=normal, cycles=245''
<code>
+---------------------------------------------------+
| MIPS v1.10 CPU Benchmark and Performance Test |
+-----------------------------------------------------------+
| | Million Instructions Per Second | 10:10:00 |
+-----------------------------------------------------------+
| BENCHMARK: | IBM/XT IBM/AT COMPAQ | |
| | 4.7Mhz 8Mhz 386 | MIPS |
|----------------------|----------------------------|-------|
| General Instructions | 0.85 0.25 0.12 | 0.14 |
| Integer Instructions | 1.48 0.23 0.10 | 0.24 |
| Memory to Memory | 1.02 0.31 0.18 | 0.24 |
| Register to Register | 1.35 0.18 0.07 | 0.24 |
| Register to Memory | 0.79 0.24 0.13 | 0.24 |
| | | |
| Performance Rating | 1.00 0.24 0.12 | 0.22 |
+-----------------------------------------------------------+
</code>

=== Notes ===

Some users may prefer a speed at which General Instructions equals 1.00 (instead of Performance Rating). This depends entirely upon what kinds of instructions you feel affect the program’s speed the most. 2D games should not be using any floating-point math so no worries there. But predicting whether a program is integer heavy, memory heavy, or whatever heavy, would be pure sorcery. [Anyone care to modify a debugger to analyze this? Didn’t think so.] Really, just choose what feels best to you (actually, I can hardly tell the difference between cycles=245 and cycles=290).

My current DOSBox speed on a 1.3 GHz Athlon is cycles=245. At such low DOSBox speeds I am finding about a 1% difference between [[dosbox.conf#.5Bcpu.5D|Normal CPU Mode]] and [[dosbox.conf#.5Bcpu.5D|Dynamic CPU Mode]]. Therefore, you shouldn’t need to worry about benchmarking that setting. Interestingly, with dynamic mode versus normal mode, the Integer Instructions benchmark ~3% slower and Register to Register benchmarks ~10% faster (the other benchmarks are proportionately 1% faster). Dynamic mode plays a larger role at higher speeds.

Other benchmarks:
* [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14] - CPU benchmark with data from XT to Pentium 200 MHz. Results are close to MIPS general instructions.
* [ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/ctest260.zip COMPTEST 2.60] - close to MIPS general instructions rating and offers floating-point benchmarks. Not dynamic mode compatible. Speed is determined by executing a block of FSQRT instructions.
* [ftp://ftp.sunet.se/pub/simtelnet/msdos/sysutl/slodn200.zip SLOWDOWN 2.00] - tends to agree with the MIPS performance rating but varies a bit depending on what speed you are slowing down from. Not dynamic mode compatible. Usage: slowdown /xt

== Additional benchmark tools ==

*[http://web.archive.org/web/20150911095745/http://ftp.isu.edu.tw/pub/CPatch/sysutil/hwinfo/source/hwinf489.zip HWiNFO 4.8.9]

*[ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/pcben60a.zip PC Benchmark 6.0]

4.77 MHz

2015-09-10T15:47:42Z

Tertz2:

The IBM PC XT ran at 4.77 MHz. This describes how to run DOSBox at XT-like speeds for programs that do not perform their own timing. Keep in mind that DOSBox cannot run at exactly 4.77 MHz. At least, not exactly the way an IBM PC XT did. You can, however, get pretty darn close by testing with some benchmark tools.

As you will see in the testing below, various types of computer instructions run at widely various speeds on the different types of computer chips out there. The most striking example is perhaps math instructions that involve real numbers such as: 1.1 x 2.2 = 2.42. This is called floating-point math. Floating-point instructions were extremely slow on the 8086 CPU unless you installed the optional 8087 co-processor. It wasn't until the Pentium age that floating-point hardware was built into all PC CPU's. Anyway, the point is that DOSBox has only one speed control, and it slows down all computer instructions by the same percentage (more or less). It is therefore not possible to tell DOSBox to slow integer math by X%, floating-point math by Y%, and non-math by Z%, etc. Near-perfect 4.77 MHz speed will not be possible until someone builds an XT emulator specifically for this purpose. This is not likely to happen because close enough will always be, quite frankly, good enough.

== Searching for 4.77 MHz (XT) ==

[ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/mips.zip MIPS 1.10] is accurate and easy tool in the quest for 4.77 MHz.

From MIPS.DOC:
<code>
FUNCTIONS: Measures Million(s) of Instructions Per Second

(1) General Instructions - random
(2) Integer Instructions - ADD SUB MUL DIV
(3) Memory to Memory - MOV RAM to RAM
(4) Register to Register - MOV REG to REG
(5) Register to Memory - MOV REG to RAM
(6) Performance Rating - average
</code>

Running MIPS produces a screen similar to this:
<code>
+---------------------------------------------------+
| MIPS v1.10 CPU Benchmark and Performance Test |
+-----------------------------------------------------------+
| | Million Instructions Per Second | 10:10:00 |
+-----------------------------------------------------------+
| BENCHMARK: | IBM/XT IBM/AT COMPAQ | |
| | 4.7Mhz 8Mhz 386 | MIPS |
|----------------------|----------------------------|-------|
| General Instructions | 25.83 7.51 3.79 | 4.29 |
| Integer Instructions | 16.92 2.64 1.16 | 2.85 |
| Memory to Memory | 7.79 2.40 1.34 | 1.85 |
| Register to Register | 18.07 2.35 0.98 | 3.25 |
| Register to Memory | 20.72 6.22 3.43 | 6.39 |
| | | |
| Performance Rating | 18.24 4.40 2.16 | 3.72 |
+-----------------------------------------------------------+
</code>

'''''Note:''' If you run MIPS at too high a speed, the numbers will get large enough to screw up the formatting and make the results mostly unreadable.''

=== Steps to Find 4.77 MHz ===

#Download MIPS and place it in an easy-to-find folder. (I created a DOSTOOLS folder inside my DOSBOX folder.)
#Make these changes to your [[dosbox.conf]] file:
#:[[dosbox.conf#.5Bsdl.5D|[sdl]]]
#:fullscreen=false
#:[[dosbox.conf#.5Bcpu.5D|[cpu]]]
#:cycles=300
#:cycleup=1
#:cycledown=1
#:[[dosbox.conf#.5Bautoexec.5D|[autoexec]]]
#:mount C "C:\Program Files\DOSBox\DOSTools\"
#:C:
#[[Basic Setup and Installation of DosBox|Launch]] DOSBox. Then run MIPS from the [[Command Line|command line]].
#Your goal is to get the Performance Rating in the IBM/XT column to equal 1.00. To do this, press [[Special Keys|Ctrl-F11]] (slow down) or [[Special Keys|Ctrl-F12]] (speed up) several times while watching the CPU Cycles in DOXBox’s [[:file:Dosbox2.jpg|title bar]] change from 300 to your next test value.
#Run MIPS again. Repeat steps 4 and 5 until you get a Performance Rating of 1.00
#Make a note of your final CPU Cycles value and set "cycles=xxx" to this value in your dosbox.conf whenever you need 4.77-MHz-like speed.

You should get something like:

''core=normal, cycles=245''
<code>
+---------------------------------------------------+
| MIPS v1.10 CPU Benchmark and Performance Test |
+-----------------------------------------------------------+
| | Million Instructions Per Second | 10:10:00 |
+-----------------------------------------------------------+
| BENCHMARK: | IBM/XT IBM/AT COMPAQ | |
| | 4.7Mhz 8Mhz 386 | MIPS |
|----------------------|----------------------------|-------|
| General Instructions | 0.85 0.25 0.12 | 0.14 |
| Integer Instructions | 1.48 0.23 0.10 | 0.24 |
| Memory to Memory | 1.02 0.31 0.18 | 0.24 |
| Register to Register | 1.35 0.18 0.07 | 0.24 |
| Register to Memory | 0.79 0.24 0.13 | 0.24 |
| | | |
| Performance Rating | 1.00 0.24 0.12 | 0.22 |
+-----------------------------------------------------------+
</code>

=== Notes ===

Some users may prefer a speed at which General Instructions equals 1.00 (instead of Performance Rating). This depends entirely upon what kinds of instructions you feel affect the program’s speed the most. 2D games should not be using any floating-point math so no worries there. But predicting whether a program is integer heavy, memory heavy, or whatever heavy, would be pure sorcery. [Anyone care to modify a debugger to analyze this? Didn’t think so.] Really, just choose what feels best to you (actually, I can hardly tell the difference between cycles=245 and cycles=290).

My current DOSBox speed on a 1.3 GHz Athlon is cycles=245. At such low DOSBox speeds I am finding about a 1% difference between [[dosbox.conf#.5Bcpu.5D|Normal CPU Mode]] and [[dosbox.conf#.5Bcpu.5D|Dynamic CPU Mode]]. Therefore, you shouldn’t need to worry about benchmarking that setting. Interestingly, with dynamic mode versus normal mode, the Integer Instructions benchmark ~3% slower and Register to Register benchmarks ~10% faster (the other benchmarks are proportionately 1% faster). Dynamic mode plays a larger role at higher speeds.

Other benchmarks:
* [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test 1.14] - CPU benchmark with data from XT to Pentium 200 MHz. Results are close to MIPS general instructions.
* [ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/ctest260.zip COMPTEST 2.60] - close to MIPS general instructions rating and offers floating-point benchmarks. Not dynamic mode compatible. Speed is determined by executing a block of FSQRT instructions.
* [ftp://ftp.sunet.se/pub/simtelnet/msdos/sysutl/slodn200.zip SLOWDOWN 2.00] - tends to agree with the MIPS performance rating but varies a bit depending on what speed you are slowing down from. Not dynamic mode compatible. Usage: slowdown /xt

== Other tools ==

;PC Benchmark 6.0: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/pcben60a.zip

4.77 MHz

2015-09-10T15:37:39Z

Tertz2:

The IBM PC XT ran at 4.77 MHz. This describes how to run DOSBox at XT-like speeds for programs that do not perform their own timing. Keep in mind that DOSBox cannot run at exactly 4.77 MHz. At least, not exactly the way an IBM PC XT did. You can, however, get pretty darn close by testing with some benchmark tools.

As you will see in the testing below, various types of computer instructions run at widely various speeds on the different types of computer chips out there. The most striking example is perhaps math instructions that involve real numbers such as: 1.1 x 2.2 = 2.42. This is called floating-point math. Floating-point instructions were extremely slow on the 8086 CPU unless you installed the optional 8087 co-processor. It wasn't until the Pentium age that floating-point hardware was built into all PC CPU's. Anyway, the point is that DOSBox has only one speed control, and it slows down all computer instructions by the same percentage (more or less). It is therefore not possible to tell DOSBox to slow integer math by X%, floating-point math by Y%, and non-math by Z%, etc. Near-perfect 4.77 MHz speed will not be possible until someone builds an XT emulator specifically for this purpose. This is not likely to happen because close enough will always be, quite frankly, good enough.

== Searching for 4.77 MHz (XT) ==

MIPS is accurate and easy tool in the quest for 4.77 MHz.

From MIPS.DOC:
<code>
FUNCTIONS: Measures Million(s) of Instructions Per Second

(1) General Instructions - random
(2) Integer Instructions - ADD SUB MUL DIV
(3) Memory to Memory - MOV RAM to RAM
(4) Register to Register - MOV REG to REG
(5) Register to Memory - MOV REG to RAM
(6) Performance Rating - average
</code>

Running MIPS produces a screen similar to this:
<code>
+---------------------------------------------------+
| MIPS v1.10 CPU Benchmark and Performance Test |
+-----------------------------------------------------------+
| | Million Instructions Per Second | 10:10:00 |
+-----------------------------------------------------------+
| BENCHMARK: | IBM/XT IBM/AT COMPAQ | |
| | 4.7Mhz 8Mhz 386 | MIPS |
|----------------------|----------------------------|-------|
| General Instructions | 25.83 7.51 3.79 | 4.29 |
| Integer Instructions | 16.92 2.64 1.16 | 2.85 |
| Memory to Memory | 7.79 2.40 1.34 | 1.85 |
| Register to Register | 18.07 2.35 0.98 | 3.25 |
| Register to Memory | 20.72 6.22 3.43 | 6.39 |
| | | |
| Performance Rating | 18.24 4.40 2.16 | 3.72 |
+-----------------------------------------------------------+
</code>

'''''Note:''' If you run MIPS at too high a speed, the numbers will get large enough to screw up the formatting and make the results mostly unreadable.''

=== Steps to Find 4.77 MHz ===

#Download MIPS and place it in an easy-to-find folder. (I created a DOSTOOLS folder inside my DOSBOX folder.)
#Make these changes to your [[dosbox.conf]] file:
#:[[dosbox.conf#.5Bsdl.5D|[sdl]]]
#:fullscreen=false
#:[[dosbox.conf#.5Bcpu.5D|[cpu]]]
#:cycles=300
#:cycleup=1
#:cycledown=1
#:[[dosbox.conf#.5Bautoexec.5D|[autoexec]]]
#:mount C "C:\Program Files\DOSBox\DOSTools\"
#:C:
#[[Basic Setup and Installation of DosBox|Launch]] DOSBox. Then run MIPS from the [[Command Line|command line]].
#Your goal is to get the Performance Rating in the IBM/XT column to equal 1.00. To do this, press [[Special Keys|Ctrl-F11]] (slow down) or [[Special Keys|Ctrl-F12]] (speed up) several times while watching the CPU Cycles in DOXBox’s [[:file:Dosbox2.jpg|title bar]] change from 300 to your next test value.
#Run MIPS again. Repeat steps 4 and 5 until you get a Performance Rating of 1.00
#Make a note of your final CPU Cycles value and set "cycles=xxx" to this value in your dosbox.conf whenever you need 4.77-MHz-like speed.

You should get something like:

''core=normal, cycles=245''
<code>
+---------------------------------------------------+
| MIPS v1.10 CPU Benchmark and Performance Test |
+-----------------------------------------------------------+
| | Million Instructions Per Second | 10:10:00 |
+-----------------------------------------------------------+
| BENCHMARK: | IBM/XT IBM/AT COMPAQ | |
| | 4.7Mhz 8Mhz 386 | MIPS |
|----------------------|----------------------------|-------|
| General Instructions | 0.85 0.25 0.12 | 0.14 |
| Integer Instructions | 1.48 0.23 0.10 | 0.24 |
| Memory to Memory | 1.02 0.31 0.18 | 0.24 |
| Register to Register | 1.35 0.18 0.07 | 0.24 |
| Register to Memory | 0.79 0.24 0.13 | 0.24 |
| | | |
| Performance Rating | 1.00 0.24 0.12 | 0.22 |
+-----------------------------------------------------------+
</code>

=== Notes ===

Some users may prefer a speed at which General Instructions equals 1.00 (instead of Performance Rating). This depends entirely upon what kinds of instructions you feel affect the program’s speed the most. 2D games should not be using any floating-point math so no worries there. But predicting whether a program is integer heavy, memory heavy, or whatever heavy, would be pure sorcery. [Anyone care to modify a debugger to analyze this? Didn’t think so.] Really, just choose what feels best to you (actually, I can hardly tell the difference between cycles=245 and cycles=290).

My current DOSBox speed on a 1.3 GHz Athlon is cycles=245. At such low DOSBox speeds I am finding about a 1% difference between [[dosbox.conf#.5Bcpu.5D|Normal CPU Mode]] and [[dosbox.conf#.5Bcpu.5D|Dynamic CPU Mode]]. Therefore, you shouldn’t need to worry about benchmarking that setting. Interestingly, with dynamic mode versus normal mode, the Integer Instructions benchmark ~3% slower and Register to Register benchmarks ~10% faster (the other benchmarks are proportionately 1% faster). Dynamic mode plays a larger role at higher speeds.

Other benchmarks:
* Speed Test - CPU benchmark with data from XT to Pentium 200 MHz. Results are close to MIPS general instructions.
* COMPTEST - close to MIPS general instructions rating and offers floating-point benchmarks. Not dynamic mode compatible. Speed is determined by executing a block of FSQRT instructions.
* SLOWDOWN - tends to agree with the MIPS performance rating but varies a bit depending on what speed you are slowing down from. Not dynamic mode compatible. Usage: slowdown /xt

== Benchmarks ==

;MIPS 1.10: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/mips.zip
;COMPTEST 2.60: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/ctest260.zip
;Speed Test 1.14: [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip http://www.agababyan.ru/FILES/UTIL/speedtst.zip]
;SLOWDOWN 2.00: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysutl/slodn200.zip
;PC Benchmark 6.0: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/pcben60a.zip

4.77 MHz

2015-09-10T14:53:18Z

Tertz2: /* Other Tools You May Find Useful */

The IBM PC XT ran at 4.77 MHz. This describes how to run DOSBox at XT-like speeds for programs that do not perform their own timing. Keep in mind that DOSBox cannot run at exactly 4.77 MHz. At least, not exactly the way an IBM PC XT did. You can, however, get pretty darn close by testing with some benchmark tools.

As you will see in the testing below, various types of computer instructions run at widely various speeds on the different types of computer chips out there. The most striking example is perhaps math instructions that involve real numbers such as: 1.1 x 2.2 = 2.42. This is called floating-point math. Floating-point instructions were extremely slow on the 8086 CPU unless you installed the optional 8087 co-processor. It wasn't until the Pentium age that floating-point hardware was built into all PC CPU's. Anyway, the point is that DOSBox has only one speed control, and it slows down all computer instructions by the same percentage (more or less). It is therefore not possible to tell DOSBox to slow integer math by X%, floating-point math by Y%, and non-math by Z%, etc. Near-perfect 4.77 MHz speed will not be possible until someone builds an XT emulator specifically for this purpose. This is not likely to happen because close enough will always be, quite frankly, good enough.

== Searching for 4.77 MHz (XT) ==

Personally, I found the old DOS tool, MIPS, to be the most accurate and easiest-to-use tool thus far for use in the quest for 4.77 MHz. Look for MIPS.ZIP at the following FTP site (or [ftp://ftp.simtel.net/pub/simtelnet/msdos/sysinfo/mips.zip click here] [http://www.oldskool.org/guides/oldonnew/resources/mips.zip or here] to get it now):

:ftp://ftp.simtel.net/pub/simtelnet/msdos/sysinfo/ ([http://www.angelfire.com/in/Ronan/mirrors.html list of mirrors])

'''The contents of MIPS.DOC:'''

<code>
PROGRAM: MIPS.COM - Version 1.10 1986
PURPOSE: CPU Benchmark and Performance Test
USAGE: MIPS [Enter]

FUNCTIONS: Measures Million(s) of Instructions Per Second

(1) General Instructions - random
(2) Integer Instructions - ADD SUB MUL DIV
(3) Memory to Memory - MOV RAM to RAM
(4) Register to Register - MOV REG to REG
(5) Register to Memory - MOV REG to RAM

(6) Performance Rating - average

COPYRIGHT: (C) 1986 Chips and Technologies, Inc.
</code>

'''Running MIPS produces a screen similar to this:'''

<code>
+---------------------------------------------------+
| MIPS v1.10 CPU Benchmark and Performance Test |
+-----------------------------------------------------------+
| | Million Instructions Per Second | 10:10:00 |
+-----------------------------------------------------------+
| BENCHMARK: | IBM/XT IBM/AT COMPAQ | |
| | 4.7Mhz 8Mhz 386 | MIPS |
|----------------------|----------------------------|-------|
| General Instructions | 25.83 7.51 3.79 | 4.29 |
| Integer Instructions | 16.92 2.64 1.16 | 2.85 |
| Memory to Memory | 7.79 2.40 1.34 | 1.85 |
| Register to Register | 18.07 2.35 0.98 | 3.25 |
| Register to Memory | 20.72 6.22 3.43 | 6.39 |
| | | |
| Performance Rating | 18.24 4.40 2.16 | 3.72 |
+-----------------------------------------------------------+
</code>

'''''Note:''' If you run MIPS at too high a speed, the numbers will get large enough to screw up the formatting and make the results mostly unreadable.''

=== Steps to Find 4.77 MHz ===

#Download MIPS and place it in an easy-to-find folder. (I created a DOSTOOLS folder inside my DOSBOX folder.)
#Make these changes to your [[dosbox.conf]] file:
#:[[dosbox.conf#.5Bsdl.5D|[sdl]]]
#:fullscreen=false
#:[[dosbox.conf#.5Bcpu.5D|[cpu]]]
#:cycles=300
#:cycleup=1
#:cycledown=1
#:[[dosbox.conf#.5Bautoexec.5D|[autoexec]]]
#:mount C "C:\Program Files\DOSBox\DOSTools\"
#:C:
#:cd \
#[[Basic Setup and Installation of DosBox|Launch]] DOSBox. Then run MIPS from the [[Command Line|command line]].
#Your goal is to get the Performance Rating in the IBM/XT column to equal 1.00. To do this, press [[Special Keys|Ctrl-F11]] (slow down) or [[Special Keys|Ctrl-F12]] (speed up) several times while watching the CPU Cycles in DOXBox’s [[:file:Dosbox2.jpg|title bar]] change from 300 to your next test value.
#Run MIPS again. Repeat steps 4 and 5 until you get a Performance Rating of 1.00 (or as close as you need).
#Make a note of your final CPU Cycles value and set "cycles=xxx" to this value in your dosbox.conf whenever you need 4.77-MHz-like speed.

'''''Hint:''' I use Ronald Blankendaal’s great DBGL (DOSBox Game Launcher) [[DOSBoxFrontends|frontend]] to simplify many of the above tasks. Just point it to your MIPS.COM file and be sure to UNcheck the "Exit afterwards" box in the General tab to stay at the command line.''

=== Notes ===

Some users may prefer a speed at which General Instructions equals 1.00 (instead of Performance Rating). This depends entirely upon what kinds of instructions you feel affect the program’s speed the most. 2D games should not be using any floating-point math so no worries there. But predicting whether a program is integer heavy, memory heavy, or whatever heavy, would be pure sorcery. [Anyone care to modify a debugger to analyze this? Didn’t think so.] Really, just choose what feels best to you (actually, I can hardly tell the difference between cycles=245 and cycles=290).

Some testing was done with other benchmark tools to ''somewhat'' validate the MIPS results:
*SLOWDOWN 2.00 tends to agree with the MIPS Performance Rating but varies a bit depending on what speed you are slowing down from. (usage: slowdown /xt) (Not dynamic mode compatible.)
*COMPTEST 2.60 tends to agree with the MIPS General Instructions rating and also offers some interesting floating-point benchmarks. Speed is determined by executing a block of FSQRT instructions. (Not dynamic mode compatible.)
*CPUTEST (1989) will lead you towards setting CPU Cycles to about twice as high as these others and I have chosen to disregard these results due to “feel” of the XT programs at this higher speed.

My current DOSBox speed on a 1.3 GHz Athlon is cycles=245. At such low DOSBox speeds I am finding about a 1% difference between [[dosbox.conf#.5Bcpu.5D|Normal CPU Mode]] and [[dosbox.conf#.5Bcpu.5D|Dynamic CPU Mode]]. Therefore, you shouldn’t need to worry about benchmarking that setting. Interestingly, with dynamic mode versus normal mode, the Integer Instructions benchmark ~3% slower and Register to Register benchmarks ~10% faster (the other benchmarks are proportionately 1% faster). [No doubt, however, that dynamic mode plays a larger role at higher speeds.]

'''core=dynamic, cycles=243:'''
<code>
+---------------------------------------------------+
| MIPS v1.10 CPU Benchmark and Performance Test |
+-----------------------------------------------------------+
| | Million Instructions Per Second | 10:10:00 |
+-----------------------------------------------------------+
| BENCHMARK: | IBM/XT IBM/AT COMPAQ | |
| | 4.7Mhz 8Mhz 386 | MIPS |
|----------------------|----------------------------|-------|
| General Instructions | 0.85 0.25 0.12 | 0.14 |
| Integer Instructions | 1.42 0.22 0.10 | 0.23 |
| Memory to Memory | 1.02 0.31 0.17 | 0.24 |
| Register to Register | 1.48 0.19 0.08 | 0.26 |
| Register to Memory | 0.79 0.24 0.13 | 0.24 |
| | | |
| Performance Rating | 1.00 0.24 0.12 | 0.22 |
+-----------------------------------------------------------+
</code>

'''core=normal, cycles=245:'''
<code>
+---------------------------------------------------+
| MIPS v1.10 CPU Benchmark and Performance Test |
+-----------------------------------------------------------+
| | Million Instructions Per Second | 10:10:00 |
+-----------------------------------------------------------+
| BENCHMARK: | IBM/XT IBM/AT COMPAQ | |
| | 4.7Mhz 8Mhz 386 | MIPS |
|----------------------|----------------------------|-------|
| General Instructions | 0.85 0.25 0.12 | 0.14 |
| Integer Instructions | 1.48 0.23 0.10 | 0.24 |
| Memory to Memory | 1.02 0.31 0.18 | 0.24 |
| Register to Register | 1.35 0.18 0.07 | 0.24 |
| Register to Memory | 0.79 0.24 0.13 | 0.24 |
| | | |
| Performance Rating | 1.00 0.24 0.12 | 0.22 |
+-----------------------------------------------------------+
</code>

== Searching for 8 MHz (AT) ==

Does anyone really need to tell you to follow the above instructions for 4.77 MHz and use the IBM/AT column in MIPS instead of the IBM/XT column. Oh yeah, you might also want to start with cycles=500.

== Other Tools You May Find Useful ==

;MIPS 1.10: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/mips.zip
;COMPTEST 2.60: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/ctest260.zip
;Speed Test 1.14: http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip
;CPUTEST: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/cputest.zip
;SLOWDOWN 2.00: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysutl/slodn200.zip
;PC Benchmark 6.0 : ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/pcben60a.zip

Performance

2015-09-09T14:36:07Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 400 MHz||386
|-
||Pentium III 1.0 GHz||486
|-
||Pentium III 1.4 GHz||486
|-
||Athlon XP 1.8 GHz||Pentium
|-
||Pentium 4 3.0 GHz||Pentium 166 MHz
|-
||Athlon 64 1.8 GHz||Pentium II
|-
||Core 2 Duo 8xxx 3.3 GHz||Pentium II 450 MHz
|-
||Core i7/i5 4xxx 4.0 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
''Note'': Based (generally) on [http://web.archive.org/web/20070127180145/http://www.gamers.org/pub/idgames/idstuff/quake/quake106.zip Quake 1.06] fps.

 
Rough dependency between cycles (core=normal) and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||310
|-
||286 12.5 MHz||2750
|-
||386 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|}
''Note'': Cycles are based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test Benchmark 1.14] by R. Agababyan

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-09-05T15:53:05Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium 200 MHz||386 20 MHz
|-
||Pentium II 400 MHz||386
|-
||Pentium III 1.0 GHz||486
|-
||Pentium III 1.4 GHz||486
|-
||Athlon XP 1.8 GHz||Pentium
|-
||Pentium 4 3.0 GHz||Pentium 166 MHz
|-
||Athlon 64 1.8 GHz||Pentium II
|-
||Core 2 Duo 8xxx 3.3 GHz||Pentium II 450 MHz
|-
||Core i7/i5 4xxx 4.0 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
''Note'': Based (generally) on [http://web.archive.org/web/20070127180145/http://www.gamers.org/pub/idgames/idstuff/quake/quake106.zip Quake 1.06] fps.

 
Rough dependency between cycles (core=normal) and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||310
|-
||286 12.5 MHz||2750
|-
||386 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|}
''Note'': Cycles are based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test Benchmark 1.14] by R. Agababyan

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-09-02T08:27:22Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium 200 MHz||386 20 MHz
|-
||Pentium II 400 MHz||386
|-
||Pentium III 1.0 GHz||486
|-
||Pentium III 1.4 GHz||486
|-
||Athlon XP 1.8 GHz||Pentium
|-
||Pentium 4 3.0 GHz||Pentium 166 MHz
|-
||Athlon 64 1.8 GHz||Pentium II
|-
||Core 2 Duo 8xxx 3.3 GHz||Pentium II 450 MHz
|-
||Core i7/i5 4xxx 4.0 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
''Note'': Based (generally) on [http://web.archive.org/web/20070127180145/http://www.gamers.org/pub/idgames/idstuff/quake/quake106.zip Quake 1.06] fps.

 
Rough dependency between cycles (core=normal) and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||310
|-
||286 16 MHz||3350
|-
||386 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|}
''Note'': Cycles are based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test Benchmark 1.14] by R. Agababyan

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-09-02T08:24:09Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium 200 MHz||386 20 MHz
|-
||Pentium II 400 MHz||386
|-
||Pentium III 1.0 GHz||486
|-
||Pentium III 1.4 GHz||486
|-
||Athlon XP 1.8 GHz||Pentium
|-
||Pentium 4 3.0 GHz||Pentium 166 MHz
|-
||Athlon 64 1.8 GHz||Pentium II
|-
||Core 2 Duo 8xxx 3.3 GHz||Pentium II 450 MHz
|-
||Core i7/i5 4xxx 4.0 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
''Note'': Based (generally) on [http://web.archive.org/web/20070127180145/http://www.gamers.org/pub/idgames/idstuff/quake/quake106.zip Quake 1.06] fps.

 
Rough dependency between cycles (core=normal) and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||310
|-
||286 16 MHz||3350
|-
||386DX 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|}
''Note'': Cycles are based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test Benchmark 1.14] by R. Agababyan

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

SVN Builds

2015-07-07T21:48:29Z

Tertz2: /* OS/2 */

This article is a discussion of the general purpose of DOSBox SVN builds, and a list of which known public ones exist and where to get them. The first part is a FAQ covering various questions regarding DOSBox SVN builds; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.

==SVN Builds FAQ==

===What are SVN builds?===
SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on [http://www.sourceforge.net/ sourceforge.net] in something called an SVN repository. SVN builds contain changes that have been made by the DOSBox developers since the latest official release. Some enhanced SVN builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.

===Why should I use an SVN build?===
Every so often a new official version of DOSBox is released. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release is several years old, and is therefore missing a significant amount of work performed by the developers. If you're having trouble running a game with the current DOSBox release, it's worth trying an SVN build to see if the problem has been addressed since then. You may also want access to the new features or optimizations if you are having compatibility or performance issues.

===Which one should I use?===
That's up to you. Consult the list below to see which features the different builds contain and decide which one you want to try first. If you are interested in trying an SVN build in hopes that it will fix a problem you're having in the latest release version, you should probably start with a "plain" (no-enhancements) SVN build. Also, see replies to this post from the maintainers for additional info on their builds.

===How do I use it?===
Some SVN builds come packaged as a fully-functional DOSBox distribution, so you can simply unpack the archive into an empty folder and run it. Other builds contain only a custom dosbox executable binary (e.g. dosbox.exe) and possibly some supporting libraries, and require that you first install the latest official release of DOSBox and then unpack the SVN build over the top of it - replacing the release versions of the files with the SVN versions. Some developers also recommend regenerating your dosbox.conf configuration file so that you will see any new config options that have been added. Consult [http://www.vogons.org/viewtopic.php?p=68701#68701 this forum thread] for info on how to regenerate a config file.

===What do I do if I find bugs in an SVN build?===
First, search the DOSBox community forums to see if it's already been reported. If it hasn't, post as much information as possible (see the [http://www.vogons.org/viewtopic.php?t=2949 help request guidelines]). ''Update:'' Note that bugs in plain SVN builds are probably the only ones of interest to the DOSBox developers. Problem reports for the other builds should be addressed to their respective maintainers, as problems could be caused by experimental patches that aren't part of the official SVN source code.

===Where can I go to talk about SVN builds? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://www.vogons.org/viewtopic.php?t=9306 forum thread] where this article originally started.

==List of SVN Builds==

===Plain/vanilla/clean SVN builds===
The following SVN builds are based directly off of the official DOSBox SVN source code. Use these builds to test the latest official SVN changes:

* '''EmuCR''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.7 (ppc/intel)
** URL: http://dl.dropbox.com/u/7737184/Dosbox/Dosbox-Snapshot.dmg
** Notes: Automatically updated on changes to SVN.

===Enhanced SVN builds===
The following SVN builds contain additional fixes and/or features that are not officially part of DOSBox. Many people prefer them due to the included extra features that are not included in in the SVN. Note that if you have problems with these builds, it may be due to the unofficial changes that have been made by their maintainers and not the official DOSBox code itself that is to blame:

* '''DOSBox with Long File Name (LFN) and mouse copy/past support''' by Wengier
** Last updated: 2014-10-26
** SVN base version: r3871
** URL: http://www.vogons.org/viewtopic.php?t=40610 (discussion + source + Windows binary)
** URL: http://www.vogons.org/viewtopic.php?t=41179 (discussion + source + Windows binary)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** Description: This is a build of DOSBox based on its SVN version that adds Long File Name (LFN) and mouse copy/past support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). Windows binaries are provided, but sources should work on other platforms too (pdcurses is required for the cross-platform clipboard copy/paste feature).

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** URL: http://cafe.daum.net/dosbox
** Description: The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc. Recent versions include DOSBox-X branch changes as well.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

===Obsolete SVN/CVS builds===
These builds appear to be no longer maintained, and are listed here for historical reference.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''Tharos (by XTale)'''
** Last updated: 2010-03-28
** <s>URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc</s>
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

* '''gulikoza'''
** Last Updated: 2009-07-09
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** Description: Recently Moe has decided to provide a DOSBox Linux (x86, 32-bit, Athlon64-optimized) binary including some useful patches. It is built against latest CVS and includes at least these patches: addkey, adlib optimize, Innovation SSI-2001, Self-Modifying-Code optimizations, SVGA chipsets, CD-Image cycling, Glide emulation, Printer emulation.
** Notes: Moe is also the creator of OPENGL-HQ. OPENGL-HQ is another scaler that is implemented in SDL.dll. Unfortunately it may be some time (or never), until OPENGL-HQ is implemented in the official SDL so until then you'll have to download it from here (or compile it yourself). Neat thing about this is that you can use this SDL.DLL with any SDL program (e.g. DOSBox, SCUMMVM...).

* '''DOSBox with MT-32 emulation (by Canadacow)'''
** Last updated: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** Description: ''This build is no longer useful''; it was made before DOSBox 0.63 came out and contains MT-32 emulation code that is much older than the current Munt releases. Note that more current MT-32 emulation is also included as an unofficial feature of some of the newer SVN builds.

==Useful Links==

===SVN changelog===
The following links list the latest changes to the official DOSBox source code on its sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://sourceforge.net/p/dosbox/code-0/3852/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2014-01-01'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://www.vogons.org/viewtopic.php?t=7323

===Making your own SVN build===
The following DOSBoxWiki article discusses the process of making your own SVN build from the official DOSBox SVN source code:
* [[BuildingDOSBox]]

===Snapshot of latest DOSBox SVN source code===
Snapshots of the latest SVN versions of the DOSBox source code are available at the following URL(s) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/?view=tar (auto-generated tarball created by sourceforge.net)
* http://sourceforge.net/scm/?type=svn&group_id=52551 (sourceforge.net instructions for accessing official DOSBox SVN repository)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)

==Unofficial ports==
These builds are for other Operating Systems and hardware platforms and are not in any way supported by the DOSBox team.

===Android===
* '''AnDOSBox''' (ver. 0.74, v1.2.8, 2012-10-18)
** URL: http://sites.google.com/site/andosbox/

* '''DosBox Turbo''' (ver. 0.74 SVN, v2.1.20, 2015-02-25)
** URL: http://sites.google.com/site/dosboxturbo/

* '''Magic Dosbox''' (ver. 0.74, v1.0.29, 2015-06-30)
** URL: http://magicbox.imejl.sk

* '''aDOSBox''' (ver. 0.73, v0.2.5, 2011-05-16)
** URL: http://play.google.com/store/apps/details?id=org.hystudio.android.dosbox

===iOS===
* '''DOSPad''' (ver. 0.74, v1.96, 2011-01)
** URL: http://www.litchie.com/?page_id=123

===PSP===
* '''DOSBox PSP''' (ver. 0.71, 2008-08-03)
** <s>URL: http://www.qj.net/tag/crazyc-gaming-news.html</s>
** URL: http://www.pspdosbox.co.uk
** <s>URL: http://forums.ps2dev.org/viewtopic.php?t=9564</s>

===Symbian===
* '''Symbian DOSBox''' (ver. 0.73, 2009-12-07)
** URL: http://sourceforge.net/projects/s60dosbox/

===Pocket PC / Windows Mobile===
* '''DosBox PPC''' (ver. 0.73, 2009-07-06)
** URL: http://n0p.8bit.fm

===Wii===
* '''DOSBox for Wii''' (ver. 0.74, v1.7, 2012-06-30)
** URL: http://code.google.com/p/dosbox-wii/

===Dreamcast===
* '''DOSBox for Dreamcast''' (ver. 0.60, 2005?)
** URL: http://gpf.dcemu.co.uk/dcdoxbox.shtml

===GP2x===
* '''DOSBox for GP2x''' (ver. 0.72, 2009-01-03)
** URL: http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,72,2534
** <s>URL: http://wiki.gp2x.org/wiki/DosBox</s>

* '''DOSBox for GP2x Wiz''' (ver. 0.72, 2009-08-27)
** URL: http://dl.openhandhelds.org/cgi-bin/wiz.cgi?0,0,0,0,72,198

* '''DOSBox for GP2x Caanoo''' (ver. 0.74, 2012-01-14)
** URL: http://dl.openhandhelds.org/cgi-bin/caanoo.cgi?0,0,0,0,72,826

===Dingoo A320===
* '''DOSBox for Dingoo A320''' (ver. 0.74, 2013-03-11)
** URL: http://www.slaanesh.net/2013/03/dosbox-074-open-dingux.html

===OS/2===
* '''DOSBox/2''' (ver. 0.74 SVN, 2015-06-05)
** URL: http://www.joschs-robotics.de/dosbox/
** URL: http://wiki.netlabs.org/index.php/DOSBox_Port

===AmigaOS 4.0===
* '''DOSBox for AmigaOS 4.0''' (ver. 0.72, 2009-06-14)
** URL: http://www.os4depot.net/share/emulation/computer/dosbox.lha
** URL: http://www.os4depot.net/index.php?function=browse&cat=emulation/computer

===Java===
* '''jDosbox''' (ver. v0.74, v0.74.28, 2013-02-27)
** URL: http://jdosbox.sourceforge.net

===JavaScript===
* '''JsDOSBox''' (ver. 0.74, v3.2, 2015-02-14)
** URL: http://sourceforge.net/projects/jsdosbox/

===IRIX===
* '''DOSBox for IRIX''' (ver. 0.71, 2007?)
** URL: http://www.spam-filter.de/dosbox/dosbox_on_irix
** <s>URL: http://www.enosnusnu.de/index.php?/archives/98-DOSBox-on-IRIX.html</s>
** Notes: Original enosnusnu.de link seems to now redirect to spam-filter.de. I added a link to a DOSBox on IRIX page on the latter site, but it appears that it may only offer a source code tarball and no binary.

===PXA270===
* '''DOSBox "Optimized" for PXA270 (by wellswang & kkazakov)''' (ver. 0.70, 2007-03-19)
** <s>URL: http://www.oesf.org/forum/index.php?showtopic=18415&st=270&p=156742&#entry156742</s>
** URL: http://wells.osall.com/files/download.php?id=1727
** URL: http://www.oesf.org/forums/index.php?s=1dec7dd003587d385fbec45efb1ffbaa&showtopic=18415&st=270&p=156742&#entry156742

SVN Builds

2015-07-07T21:44:13Z

Tertz2: /* Unofficial ports */

This article is a discussion of the general purpose of DOSBox SVN builds, and a list of which known public ones exist and where to get them. The first part is a FAQ covering various questions regarding DOSBox SVN builds; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.

==SVN Builds FAQ==

===What are SVN builds?===
SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on [http://www.sourceforge.net/ sourceforge.net] in something called an SVN repository. SVN builds contain changes that have been made by the DOSBox developers since the latest official release. Some enhanced SVN builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.

===Why should I use an SVN build?===
Every so often a new official version of DOSBox is released. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release is several years old, and is therefore missing a significant amount of work performed by the developers. If you're having trouble running a game with the current DOSBox release, it's worth trying an SVN build to see if the problem has been addressed since then. You may also want access to the new features or optimizations if you are having compatibility or performance issues.

===Which one should I use?===
That's up to you. Consult the list below to see which features the different builds contain and decide which one you want to try first. If you are interested in trying an SVN build in hopes that it will fix a problem you're having in the latest release version, you should probably start with a "plain" (no-enhancements) SVN build. Also, see replies to this post from the maintainers for additional info on their builds.

===How do I use it?===
Some SVN builds come packaged as a fully-functional DOSBox distribution, so you can simply unpack the archive into an empty folder and run it. Other builds contain only a custom dosbox executable binary (e.g. dosbox.exe) and possibly some supporting libraries, and require that you first install the latest official release of DOSBox and then unpack the SVN build over the top of it - replacing the release versions of the files with the SVN versions. Some developers also recommend regenerating your dosbox.conf configuration file so that you will see any new config options that have been added. Consult [http://www.vogons.org/viewtopic.php?p=68701#68701 this forum thread] for info on how to regenerate a config file.

===What do I do if I find bugs in an SVN build?===
First, search the DOSBox community forums to see if it's already been reported. If it hasn't, post as much information as possible (see the [http://www.vogons.org/viewtopic.php?t=2949 help request guidelines]). ''Update:'' Note that bugs in plain SVN builds are probably the only ones of interest to the DOSBox developers. Problem reports for the other builds should be addressed to their respective maintainers, as problems could be caused by experimental patches that aren't part of the official SVN source code.

===Where can I go to talk about SVN builds? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://www.vogons.org/viewtopic.php?t=9306 forum thread] where this article originally started.

==List of SVN Builds==

===Plain/vanilla/clean SVN builds===
The following SVN builds are based directly off of the official DOSBox SVN source code. Use these builds to test the latest official SVN changes:

* '''EmuCR''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.7 (ppc/intel)
** URL: http://dl.dropbox.com/u/7737184/Dosbox/Dosbox-Snapshot.dmg
** Notes: Automatically updated on changes to SVN.

===Enhanced SVN builds===
The following SVN builds contain additional fixes and/or features that are not officially part of DOSBox. Many people prefer them due to the included extra features that are not included in in the SVN. Note that if you have problems with these builds, it may be due to the unofficial changes that have been made by their maintainers and not the official DOSBox code itself that is to blame:

* '''DOSBox with Long File Name (LFN) and mouse copy/past support''' by Wengier
** Last updated: 2014-10-26
** SVN base version: r3871
** URL: http://www.vogons.org/viewtopic.php?t=40610 (discussion + source + Windows binary)
** URL: http://www.vogons.org/viewtopic.php?t=41179 (discussion + source + Windows binary)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** Description: This is a build of DOSBox based on its SVN version that adds Long File Name (LFN) and mouse copy/past support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). Windows binaries are provided, but sources should work on other platforms too (pdcurses is required for the cross-platform clipboard copy/paste feature).

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** URL: http://cafe.daum.net/dosbox
** Description: The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc. Recent versions include DOSBox-X branch changes as well.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

===Obsolete SVN/CVS builds===
These builds appear to be no longer maintained, and are listed here for historical reference.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''Tharos (by XTale)'''
** Last updated: 2010-03-28
** <s>URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc</s>
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

* '''gulikoza'''
** Last Updated: 2009-07-09
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** Description: Recently Moe has decided to provide a DOSBox Linux (x86, 32-bit, Athlon64-optimized) binary including some useful patches. It is built against latest CVS and includes at least these patches: addkey, adlib optimize, Innovation SSI-2001, Self-Modifying-Code optimizations, SVGA chipsets, CD-Image cycling, Glide emulation, Printer emulation.
** Notes: Moe is also the creator of OPENGL-HQ. OPENGL-HQ is another scaler that is implemented in SDL.dll. Unfortunately it may be some time (or never), until OPENGL-HQ is implemented in the official SDL so until then you'll have to download it from here (or compile it yourself). Neat thing about this is that you can use this SDL.DLL with any SDL program (e.g. DOSBox, SCUMMVM...).

* '''DOSBox with MT-32 emulation (by Canadacow)'''
** Last updated: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** Description: ''This build is no longer useful''; it was made before DOSBox 0.63 came out and contains MT-32 emulation code that is much older than the current Munt releases. Note that more current MT-32 emulation is also included as an unofficial feature of some of the newer SVN builds.

==Useful Links==

===SVN changelog===
The following links list the latest changes to the official DOSBox source code on its sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://sourceforge.net/p/dosbox/code-0/3852/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2014-01-01'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://www.vogons.org/viewtopic.php?t=7323

===Making your own SVN build===
The following DOSBoxWiki article discusses the process of making your own SVN build from the official DOSBox SVN source code:
* [[BuildingDOSBox]]

===Snapshot of latest DOSBox SVN source code===
Snapshots of the latest SVN versions of the DOSBox source code are available at the following URL(s) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/?view=tar (auto-generated tarball created by sourceforge.net)
* http://sourceforge.net/scm/?type=svn&group_id=52551 (sourceforge.net instructions for accessing official DOSBox SVN repository)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)

==Unofficial ports==
These builds are for other Operating Systems and hardware platforms and are not in any way supported by the DOSBox team.

===Android===
* '''AnDOSBox''' (ver. 0.74, v1.2.8, 2012-10-18)
** URL: http://sites.google.com/site/andosbox/

* '''DosBox Turbo''' (ver. 0.74 SVN, v2.1.20, 2015-02-25)
** URL: http://sites.google.com/site/dosboxturbo/

* '''Magic Dosbox''' (ver. 0.74, v1.0.29, 2015-06-30)
** URL: http://magicbox.imejl.sk

* '''aDOSBox''' (ver. 0.73, v0.2.5, 2011-05-16)
** URL: http://play.google.com/store/apps/details?id=org.hystudio.android.dosbox

===iOS===
* '''DOSPad''' (ver. 0.74, v1.96, 2011-01)
** URL: http://www.litchie.com/?page_id=123

===PSP===
* '''DOSBox PSP''' (ver. 0.71, 2008-08-03)
** <s>URL: http://www.qj.net/tag/crazyc-gaming-news.html</s>
** URL: http://www.pspdosbox.co.uk
** <s>URL: http://forums.ps2dev.org/viewtopic.php?t=9564</s>

===Symbian===
* '''Symbian DOSBox''' (ver. 0.73, 2009-12-07)
** URL: http://sourceforge.net/projects/s60dosbox/

===Pocket PC / Windows Mobile===
* '''DosBox PPC''' (ver. 0.73, 2009-07-06)
** URL: http://n0p.8bit.fm

===Wii===
* '''DOSBox for Wii''' (ver. 0.74, v1.7, 2012-06-30)
** URL: http://code.google.com/p/dosbox-wii/

===Dreamcast===
* '''DOSBox for Dreamcast''' (ver. 0.60, 2005?)
** URL: http://gpf.dcemu.co.uk/dcdoxbox.shtml

===GP2x===
* '''DOSBox for GP2x''' (ver. 0.72, 2009-01-03)
** URL: http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,72,2534
** <s>URL: http://wiki.gp2x.org/wiki/DosBox</s>

* '''DOSBox for GP2x Wiz''' (ver. 0.72, 2009-08-27)
** URL: http://dl.openhandhelds.org/cgi-bin/wiz.cgi?0,0,0,0,72,198

* '''DOSBox for GP2x Caanoo''' (ver. 0.74, 2012-01-14)
** URL: http://dl.openhandhelds.org/cgi-bin/caanoo.cgi?0,0,0,0,72,826

===Dingoo A320===
* '''DOSBox for Dingoo A320''' (ver. 0.74, 2013-03-11)
** URL: http://www.slaanesh.net/2013/03/dosbox-074-open-dingux.html

===OS/2===
* '''DOSBox/2''' (ver. 0.74, 2010-09-17)
** <s>URL: http://www.os2site.com/sw/emulators/dosbox/index.html<s/>
** URL: http://www.joschs-robotics.de/dosbox/
** URL: http://wiki.netlabs.org/index.php/DOSBox_Port

===AmigaOS 4.0===
* '''DOSBox for AmigaOS 4.0''' (ver. 0.72, 2009-06-14)
** URL: http://www.os4depot.net/share/emulation/computer/dosbox.lha
** URL: http://www.os4depot.net/index.php?function=browse&cat=emulation/computer

===Java===
* '''jDosbox''' (ver. v0.74, v0.74.28, 2013-02-27)
** URL: http://jdosbox.sourceforge.net

===JavaScript===
* '''JsDOSBox''' (ver. 0.74, v3.2, 2015-02-14)
** URL: http://sourceforge.net/projects/jsdosbox/

===IRIX===
* '''DOSBox for IRIX''' (ver. 0.71, 2007?)
** URL: http://www.spam-filter.de/dosbox/dosbox_on_irix
** <s>URL: http://www.enosnusnu.de/index.php?/archives/98-DOSBox-on-IRIX.html</s>
** Notes: Original enosnusnu.de link seems to now redirect to spam-filter.de. I added a link to a DOSBox on IRIX page on the latter site, but it appears that it may only offer a source code tarball and no binary.

===PXA270===
* '''DOSBox "Optimized" for PXA270 (by wellswang & kkazakov)''' (ver. 0.70, 2007-03-19)
** <s>URL: http://www.oesf.org/forum/index.php?showtopic=18415&st=270&p=156742&#entry156742</s>
** URL: http://wells.osall.com/files/download.php?id=1727
** URL: http://www.oesf.org/forums/index.php?s=1dec7dd003587d385fbec45efb1ffbaa&showtopic=18415&st=270&p=156742&#entry156742

SVN Builds

2015-07-07T21:12:48Z

Tertz2: /* Android */

This article is a discussion of the general purpose of DOSBox SVN builds, and a list of which known public ones exist and where to get them. The first part is a FAQ covering various questions regarding DOSBox SVN builds; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.

==SVN Builds FAQ==

===What are SVN builds?===
SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on [http://www.sourceforge.net/ sourceforge.net] in something called an SVN repository. SVN builds contain changes that have been made by the DOSBox developers since the latest official release. Some enhanced SVN builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.

===Why should I use an SVN build?===
Every so often a new official version of DOSBox is released. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release is several years old, and is therefore missing a significant amount of work performed by the developers. If you're having trouble running a game with the current DOSBox release, it's worth trying an SVN build to see if the problem has been addressed since then. You may also want access to the new features or optimizations if you are having compatibility or performance issues.

===Which one should I use?===
That's up to you. Consult the list below to see which features the different builds contain and decide which one you want to try first. If you are interested in trying an SVN build in hopes that it will fix a problem you're having in the latest release version, you should probably start with a "plain" (no-enhancements) SVN build. Also, see replies to this post from the maintainers for additional info on their builds.

===How do I use it?===
Some SVN builds come packaged as a fully-functional DOSBox distribution, so you can simply unpack the archive into an empty folder and run it. Other builds contain only a custom dosbox executable binary (e.g. dosbox.exe) and possibly some supporting libraries, and require that you first install the latest official release of DOSBox and then unpack the SVN build over the top of it - replacing the release versions of the files with the SVN versions. Some developers also recommend regenerating your dosbox.conf configuration file so that you will see any new config options that have been added. Consult [http://www.vogons.org/viewtopic.php?p=68701#68701 this forum thread] for info on how to regenerate a config file.

===What do I do if I find bugs in an SVN build?===
First, search the DOSBox community forums to see if it's already been reported. If it hasn't, post as much information as possible (see the [http://www.vogons.org/viewtopic.php?t=2949 help request guidelines]). ''Update:'' Note that bugs in plain SVN builds are probably the only ones of interest to the DOSBox developers. Problem reports for the other builds should be addressed to their respective maintainers, as problems could be caused by experimental patches that aren't part of the official SVN source code.

===Where can I go to talk about SVN builds? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://www.vogons.org/viewtopic.php?t=9306 forum thread] where this article originally started.

==List of SVN Builds==

===Plain/vanilla/clean SVN builds===
The following SVN builds are based directly off of the official DOSBox SVN source code. Use these builds to test the latest official SVN changes:

* '''EmuCR''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.7 (ppc/intel)
** URL: http://dl.dropbox.com/u/7737184/Dosbox/Dosbox-Snapshot.dmg
** Notes: Automatically updated on changes to SVN.

===Enhanced SVN builds===
The following SVN builds contain additional fixes and/or features that are not officially part of DOSBox. Many people prefer them due to the included extra features that are not included in in the SVN. Note that if you have problems with these builds, it may be due to the unofficial changes that have been made by their maintainers and not the official DOSBox code itself that is to blame:

* '''DOSBox with Long File Name (LFN) and mouse copy/past support''' by Wengier
** Last updated: 2014-10-26
** SVN base version: r3871
** URL: http://www.vogons.org/viewtopic.php?t=40610 (discussion + source + Windows binary)
** URL: http://www.vogons.org/viewtopic.php?t=41179 (discussion + source + Windows binary)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** Description: This is a build of DOSBox based on its SVN version that adds Long File Name (LFN) and mouse copy/past support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). Windows binaries are provided, but sources should work on other platforms too (pdcurses is required for the cross-platform clipboard copy/paste feature).

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** URL: http://cafe.daum.net/dosbox
** Description: The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc. Recent versions include DOSBox-X branch changes as well.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

===Obsolete SVN/CVS builds===
These builds appear to be no longer maintained, and are listed here for historical reference.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''Tharos (by XTale)'''
** Last updated: 2010-03-28
** <s>URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc</s>
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

* '''gulikoza'''
** Last Updated: 2009-07-09
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** Description: Recently Moe has decided to provide a DOSBox Linux (x86, 32-bit, Athlon64-optimized) binary including some useful patches. It is built against latest CVS and includes at least these patches: addkey, adlib optimize, Innovation SSI-2001, Self-Modifying-Code optimizations, SVGA chipsets, CD-Image cycling, Glide emulation, Printer emulation.
** Notes: Moe is also the creator of OPENGL-HQ. OPENGL-HQ is another scaler that is implemented in SDL.dll. Unfortunately it may be some time (or never), until OPENGL-HQ is implemented in the official SDL so until then you'll have to download it from here (or compile it yourself). Neat thing about this is that you can use this SDL.DLL with any SDL program (e.g. DOSBox, SCUMMVM...).

* '''DOSBox with MT-32 emulation (by Canadacow)'''
** Last updated: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** Description: ''This build is no longer useful''; it was made before DOSBox 0.63 came out and contains MT-32 emulation code that is much older than the current Munt releases. Note that more current MT-32 emulation is also included as an unofficial feature of some of the newer SVN builds.

==Useful Links==

===SVN changelog===
The following links list the latest changes to the official DOSBox source code on its sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://sourceforge.net/p/dosbox/code-0/3852/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2014-01-01'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://www.vogons.org/viewtopic.php?t=7323

===Making your own SVN build===
The following DOSBoxWiki article discusses the process of making your own SVN build from the official DOSBox SVN source code:
* [[BuildingDOSBox]]

===Snapshot of latest DOSBox SVN source code===
Snapshots of the latest SVN versions of the DOSBox source code are available at the following URL(s) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/?view=tar (auto-generated tarball created by sourceforge.net)
* http://sourceforge.net/scm/?type=svn&group_id=52551 (sourceforge.net instructions for accessing official DOSBox SVN repository)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)

==Unofficial ports==
These builds are for other Operating Systems and hardware platforms and are not in any way supported by the DOSBox team.

===Android===
* '''AnDOSBox''' (ver. 0.74, v1.2.8, 2012-10-18)
** URL: http://sites.google.com/site/andosbox/

* '''DosBox Turbo''' (ver. 0.74 SVN, v2.1.20, 2015-02-25)
** URL: http://sites.google.com/site/dosboxturbo/

* '''Magic Dosbox''' (ver. 0.74, v1.0.29, 2015-06-30)
** URL: http://magicbox.imejl.sk

* '''aDOSBox''' (ver. 0.73, v0.2.5, 2011-05-16)
** URL: http://play.google.com/store/apps/details?id=org.hystudio.android.dosbox

===iOS===
* '''DOSPad''' (ver. 0.74, v1.96, 2011-01)
** URL: http://www.litchie.com/?page_id=123

===PSP===
* '''DOSBox PSP''' (ver. 0.71, 2008-08-03)
** <s>URL: http://www.qj.net/tag/crazyc-gaming-news.html</s>
** URL: http://www.pspdosbox.co.uk
** <s>URL: http://forums.ps2dev.org/viewtopic.php?t=9564</s>

===Pocket PC / Windows Mobile===
* '''DosBox PPC''' (ver. 0.73, 2009-07-06)
** URL: http://n0p.8bit.fm

===Wii===
* '''DOSBox for Wii''' (ver. 0.74, v1.7, 2012-06-30)
** URL: http://code.google.com/p/dosbox-wii/

===Dreamcast===
* '''DOSBox for Dreamcast''' (ver. 0.60, 2005?)
** URL: http://gpf.dcemu.co.uk/dcdoxbox.shtml

===GP2x===
* '''DOSBox for GP2x''' (ver. 0.72, 2009-01-03)
** URL: http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,72,2534
** <s>URL: http://wiki.gp2x.org/wiki/DosBox</s>

* '''DOSBox for GP2x Wiz''' (ver. 0.72, 2009-08-27)
** URL: http://dl.openhandhelds.org/cgi-bin/wiz.cgi?0,0,0,0,72,198

* '''DOSBox for GP2x Caanoo''' (ver. 0.74, 2012-01-14)
** URL: http://dl.openhandhelds.org/cgi-bin/caanoo.cgi?0,0,0,0,72,826

===Dingoo A320===
* '''DOSBox for Dingoo A320''' (ver. 0.74, 2013-03-11)
** URL: http://www.slaanesh.net/2013/03/dosbox-074-open-dingux.html

===OS/2===
* '''DOSBox/2''' (ver. 0.74, 2010-09-17)
** <s>URL: http://www.os2site.com/sw/emulators/dosbox/index.html<s/>
** URL: http://www.joschs-robotics.de/dosbox/
** URL: http://wiki.netlabs.org/index.php/DOSBox_Port

===AmigaOS 4.0===
* '''DOSBox for AmigaOS 4.0''' (ver. 0.72, 2009-06-14)
** URL: http://www.os4depot.net/share/emulation/computer/dosbox.lha
** URL: http://www.os4depot.net/index.php?function=browse&cat=emulation/computer

===Java===
* '''jDosbox''' (ver. v0.74, v0.74.28, 2013-02-27)
** URL: http://jdosbox.sourceforge.net

===JavaScript===
* '''JsDOSBox''' (ver. 0.74, v3.2, 2015-02-14)
** URL: http://sourceforge.net/projects/jsdosbox/

===IRIX===
* '''DOSBox for IRIX''' (ver. 0.71, 2007?)
** URL: http://www.spam-filter.de/dosbox/dosbox_on_irix
** <s>URL: http://www.enosnusnu.de/index.php?/archives/98-DOSBox-on-IRIX.html</s>
** Notes: Original enosnusnu.de link seems to now redirect to spam-filter.de. I added a link to a DOSBox on IRIX page on the latter site, but it appears that it may only offer a source code tarball and no binary.

===PXA270===
* '''DOSBox "Optimized" for PXA270 (by wellswang & kkazakov)''' (ver. 0.70, 2007-03-19)
** <s>URL: http://www.oesf.org/forum/index.php?showtopic=18415&st=270&p=156742&#entry156742</s>
** URL: http://wells.osall.com/files/download.php?id=1727
** URL: http://www.oesf.org/forums/index.php?s=1dec7dd003587d385fbec45efb1ffbaa&showtopic=18415&st=270&p=156742&#entry156742

SVN Builds

2015-07-07T21:04:50Z

Tertz2: /* Android */

This article is a discussion of the general purpose of DOSBox SVN builds, and a list of which known public ones exist and where to get them. The first part is a FAQ covering various questions regarding DOSBox SVN builds; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.

==SVN Builds FAQ==

===What are SVN builds?===
SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on [http://www.sourceforge.net/ sourceforge.net] in something called an SVN repository. SVN builds contain changes that have been made by the DOSBox developers since the latest official release. Some enhanced SVN builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.

===Why should I use an SVN build?===
Every so often a new official version of DOSBox is released. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release is several years old, and is therefore missing a significant amount of work performed by the developers. If you're having trouble running a game with the current DOSBox release, it's worth trying an SVN build to see if the problem has been addressed since then. You may also want access to the new features or optimizations if you are having compatibility or performance issues.

===Which one should I use?===
That's up to you. Consult the list below to see which features the different builds contain and decide which one you want to try first. If you are interested in trying an SVN build in hopes that it will fix a problem you're having in the latest release version, you should probably start with a "plain" (no-enhancements) SVN build. Also, see replies to this post from the maintainers for additional info on their builds.

===How do I use it?===
Some SVN builds come packaged as a fully-functional DOSBox distribution, so you can simply unpack the archive into an empty folder and run it. Other builds contain only a custom dosbox executable binary (e.g. dosbox.exe) and possibly some supporting libraries, and require that you first install the latest official release of DOSBox and then unpack the SVN build over the top of it - replacing the release versions of the files with the SVN versions. Some developers also recommend regenerating your dosbox.conf configuration file so that you will see any new config options that have been added. Consult [http://www.vogons.org/viewtopic.php?p=68701#68701 this forum thread] for info on how to regenerate a config file.

===What do I do if I find bugs in an SVN build?===
First, search the DOSBox community forums to see if it's already been reported. If it hasn't, post as much information as possible (see the [http://www.vogons.org/viewtopic.php?t=2949 help request guidelines]). ''Update:'' Note that bugs in plain SVN builds are probably the only ones of interest to the DOSBox developers. Problem reports for the other builds should be addressed to their respective maintainers, as problems could be caused by experimental patches that aren't part of the official SVN source code.

===Where can I go to talk about SVN builds? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://www.vogons.org/viewtopic.php?t=9306 forum thread] where this article originally started.

==List of SVN Builds==

===Plain/vanilla/clean SVN builds===
The following SVN builds are based directly off of the official DOSBox SVN source code. Use these builds to test the latest official SVN changes:

* '''EmuCR''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.7 (ppc/intel)
** URL: http://dl.dropbox.com/u/7737184/Dosbox/Dosbox-Snapshot.dmg
** Notes: Automatically updated on changes to SVN.

===Enhanced SVN builds===
The following SVN builds contain additional fixes and/or features that are not officially part of DOSBox. Many people prefer them due to the included extra features that are not included in in the SVN. Note that if you have problems with these builds, it may be due to the unofficial changes that have been made by their maintainers and not the official DOSBox code itself that is to blame:

* '''DOSBox with Long File Name (LFN) and mouse copy/past support''' by Wengier
** Last updated: 2014-10-26
** SVN base version: r3871
** URL: http://www.vogons.org/viewtopic.php?t=40610 (discussion + source + Windows binary)
** URL: http://www.vogons.org/viewtopic.php?t=41179 (discussion + source + Windows binary)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** Description: This is a build of DOSBox based on its SVN version that adds Long File Name (LFN) and mouse copy/past support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). Windows binaries are provided, but sources should work on other platforms too (pdcurses is required for the cross-platform clipboard copy/paste feature).

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** URL: http://cafe.daum.net/dosbox
** Description: The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc. Recent versions include DOSBox-X branch changes as well.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

===Obsolete SVN/CVS builds===
These builds appear to be no longer maintained, and are listed here for historical reference.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''Tharos (by XTale)'''
** Last updated: 2010-03-28
** <s>URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc</s>
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

* '''gulikoza'''
** Last Updated: 2009-07-09
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** Description: Recently Moe has decided to provide a DOSBox Linux (x86, 32-bit, Athlon64-optimized) binary including some useful patches. It is built against latest CVS and includes at least these patches: addkey, adlib optimize, Innovation SSI-2001, Self-Modifying-Code optimizations, SVGA chipsets, CD-Image cycling, Glide emulation, Printer emulation.
** Notes: Moe is also the creator of OPENGL-HQ. OPENGL-HQ is another scaler that is implemented in SDL.dll. Unfortunately it may be some time (or never), until OPENGL-HQ is implemented in the official SDL so until then you'll have to download it from here (or compile it yourself). Neat thing about this is that you can use this SDL.DLL with any SDL program (e.g. DOSBox, SCUMMVM...).

* '''DOSBox with MT-32 emulation (by Canadacow)'''
** Last updated: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** Description: ''This build is no longer useful''; it was made before DOSBox 0.63 came out and contains MT-32 emulation code that is much older than the current Munt releases. Note that more current MT-32 emulation is also included as an unofficial feature of some of the newer SVN builds.

==Useful Links==

===SVN changelog===
The following links list the latest changes to the official DOSBox source code on its sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://sourceforge.net/p/dosbox/code-0/3852/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2014-01-01'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://www.vogons.org/viewtopic.php?t=7323

===Making your own SVN build===
The following DOSBoxWiki article discusses the process of making your own SVN build from the official DOSBox SVN source code:
* [[BuildingDOSBox]]

===Snapshot of latest DOSBox SVN source code===
Snapshots of the latest SVN versions of the DOSBox source code are available at the following URL(s) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/?view=tar (auto-generated tarball created by sourceforge.net)
* http://sourceforge.net/scm/?type=svn&group_id=52551 (sourceforge.net instructions for accessing official DOSBox SVN repository)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)

==Unofficial ports==
These builds are for other Operating Systems and hardware platforms and are not in any way supported by the DOSBox team.

===Android===
* '''AnDOSBox''' (ver. 0.74, v1.2.8, 2012-10-18)
** URL: http://sites.google.com/site/andosbox/

* '''DosBox Turbo''' (ver. 0.74 SVN, v2.1.20, 2015-02-25)
** URL: http://sites.google.com/site/dosboxturbo/

* '''Magic Dosbox''' (ver. 0.74, v1.0.29, 2015-06-30)
** URL: http://magicbox.imejl.sk

* '''aDOSBox''' (ver. 0.73, v0.2.5, 2011-05-16)
** URL: http://androiddosbox.appspot.com

===iOS===
* '''DOSPad''' (ver. 0.74, v1.96, 2011-01)
** URL: http://www.litchie.com/?page_id=123

===PSP===
* '''DOSBox PSP''' (ver. 0.71, 2008-08-03)
** <s>URL: http://www.qj.net/tag/crazyc-gaming-news.html</s>
** URL: http://www.pspdosbox.co.uk
** <s>URL: http://forums.ps2dev.org/viewtopic.php?t=9564</s>

===Pocket PC / Windows Mobile===
* '''DosBox PPC''' (ver. 0.73, 2009-07-06)
** URL: http://n0p.8bit.fm

===Wii===
* '''DOSBox for Wii''' (ver. 0.74, v1.7, 2012-06-30)
** URL: http://code.google.com/p/dosbox-wii/

===Dreamcast===
* '''DOSBox for Dreamcast''' (ver. 0.60, 2005?)
** URL: http://gpf.dcemu.co.uk/dcdoxbox.shtml

===GP2x===
* '''DOSBox for GP2x''' (ver. 0.72, 2009-01-03)
** URL: http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,72,2534
** <s>URL: http://wiki.gp2x.org/wiki/DosBox</s>

* '''DOSBox for GP2x Wiz''' (ver. 0.72, 2009-08-27)
** URL: http://dl.openhandhelds.org/cgi-bin/wiz.cgi?0,0,0,0,72,198

* '''DOSBox for GP2x Caanoo''' (ver. 0.74, 2012-01-14)
** URL: http://dl.openhandhelds.org/cgi-bin/caanoo.cgi?0,0,0,0,72,826

===Dingoo A320===
* '''DOSBox for Dingoo A320''' (ver. 0.74, 2013-03-11)
** URL: http://www.slaanesh.net/2013/03/dosbox-074-open-dingux.html

===OS/2===
* '''DOSBox/2''' (ver. 0.74, 2010-09-17)
** <s>URL: http://www.os2site.com/sw/emulators/dosbox/index.html<s/>
** URL: http://www.joschs-robotics.de/dosbox/
** URL: http://wiki.netlabs.org/index.php/DOSBox_Port

===AmigaOS 4.0===
* '''DOSBox for AmigaOS 4.0''' (ver. 0.72, 2009-06-14)
** URL: http://www.os4depot.net/share/emulation/computer/dosbox.lha
** URL: http://www.os4depot.net/index.php?function=browse&cat=emulation/computer

===Java===
* '''jDosbox''' (ver. v0.74, v0.74.28, 2013-02-27)
** URL: http://jdosbox.sourceforge.net

===JavaScript===
* '''JsDOSBox''' (ver. 0.74, v3.2, 2015-02-14)
** URL: http://sourceforge.net/projects/jsdosbox/

===IRIX===
* '''DOSBox for IRIX''' (ver. 0.71, 2007?)
** URL: http://www.spam-filter.de/dosbox/dosbox_on_irix
** <s>URL: http://www.enosnusnu.de/index.php?/archives/98-DOSBox-on-IRIX.html</s>
** Notes: Original enosnusnu.de link seems to now redirect to spam-filter.de. I added a link to a DOSBox on IRIX page on the latter site, but it appears that it may only offer a source code tarball and no binary.

===PXA270===
* '''DOSBox "Optimized" for PXA270 (by wellswang & kkazakov)''' (ver. 0.70, 2007-03-19)
** <s>URL: http://www.oesf.org/forum/index.php?showtopic=18415&st=270&p=156742&#entry156742</s>
** URL: http://wells.osall.com/files/download.php?id=1727
** URL: http://www.oesf.org/forums/index.php?s=1dec7dd003587d385fbec45efb1ffbaa&showtopic=18415&st=270&p=156742&#entry156742

SVN Builds

2015-07-07T19:57:59Z

Tertz2: /* Dingoo A320 */

This article is a discussion of the general purpose of DOSBox SVN builds, and a list of which known public ones exist and where to get them. The first part is a FAQ covering various questions regarding DOSBox SVN builds; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.

==SVN Builds FAQ==

===What are SVN builds?===
SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on [http://www.sourceforge.net/ sourceforge.net] in something called an SVN repository. SVN builds contain changes that have been made by the DOSBox developers since the latest official release. Some enhanced SVN builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.

===Why should I use an SVN build?===
Every so often a new official version of DOSBox is released. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release is several years old, and is therefore missing a significant amount of work performed by the developers. If you're having trouble running a game with the current DOSBox release, it's worth trying an SVN build to see if the problem has been addressed since then. You may also want access to the new features or optimizations if you are having compatibility or performance issues.

===Which one should I use?===
That's up to you. Consult the list below to see which features the different builds contain and decide which one you want to try first. If you are interested in trying an SVN build in hopes that it will fix a problem you're having in the latest release version, you should probably start with a "plain" (no-enhancements) SVN build. Also, see replies to this post from the maintainers for additional info on their builds.

===How do I use it?===
Some SVN builds come packaged as a fully-functional DOSBox distribution, so you can simply unpack the archive into an empty folder and run it. Other builds contain only a custom dosbox executable binary (e.g. dosbox.exe) and possibly some supporting libraries, and require that you first install the latest official release of DOSBox and then unpack the SVN build over the top of it - replacing the release versions of the files with the SVN versions. Some developers also recommend regenerating your dosbox.conf configuration file so that you will see any new config options that have been added. Consult [http://www.vogons.org/viewtopic.php?p=68701#68701 this forum thread] for info on how to regenerate a config file.

===What do I do if I find bugs in an SVN build?===
First, search the DOSBox community forums to see if it's already been reported. If it hasn't, post as much information as possible (see the [http://www.vogons.org/viewtopic.php?t=2949 help request guidelines]). ''Update:'' Note that bugs in plain SVN builds are probably the only ones of interest to the DOSBox developers. Problem reports for the other builds should be addressed to their respective maintainers, as problems could be caused by experimental patches that aren't part of the official SVN source code.

===Where can I go to talk about SVN builds? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://www.vogons.org/viewtopic.php?t=9306 forum thread] where this article originally started.

==List of SVN Builds==

===Plain/vanilla/clean SVN builds===
The following SVN builds are based directly off of the official DOSBox SVN source code. Use these builds to test the latest official SVN changes:

* '''EmuCR''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.7 (ppc/intel)
** URL: http://dl.dropbox.com/u/7737184/Dosbox/Dosbox-Snapshot.dmg
** Notes: Automatically updated on changes to SVN.

===Enhanced SVN builds===
The following SVN builds contain additional fixes and/or features that are not officially part of DOSBox. Many people prefer them due to the included extra features that are not included in in the SVN. Note that if you have problems with these builds, it may be due to the unofficial changes that have been made by their maintainers and not the official DOSBox code itself that is to blame:

* '''DOSBox with Long File Name (LFN) and mouse copy/past support''' by Wengier
** Last updated: 2014-10-26
** SVN base version: r3871
** URL: http://www.vogons.org/viewtopic.php?t=40610 (discussion + source + Windows binary)
** URL: http://www.vogons.org/viewtopic.php?t=41179 (discussion + source + Windows binary)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** Description: This is a build of DOSBox based on its SVN version that adds Long File Name (LFN) and mouse copy/past support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). Windows binaries are provided, but sources should work on other platforms too (pdcurses is required for the cross-platform clipboard copy/paste feature).

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** URL: http://cafe.daum.net/dosbox
** Description: The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc. Recent versions include DOSBox-X branch changes as well.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

===Obsolete SVN/CVS builds===
These builds appear to be no longer maintained, and are listed here for historical reference.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''Tharos (by XTale)'''
** Last updated: 2010-03-28
** <s>URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc</s>
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

* '''gulikoza'''
** Last Updated: 2009-07-09
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** Description: Recently Moe has decided to provide a DOSBox Linux (x86, 32-bit, Athlon64-optimized) binary including some useful patches. It is built against latest CVS and includes at least these patches: addkey, adlib optimize, Innovation SSI-2001, Self-Modifying-Code optimizations, SVGA chipsets, CD-Image cycling, Glide emulation, Printer emulation.
** Notes: Moe is also the creator of OPENGL-HQ. OPENGL-HQ is another scaler that is implemented in SDL.dll. Unfortunately it may be some time (or never), until OPENGL-HQ is implemented in the official SDL so until then you'll have to download it from here (or compile it yourself). Neat thing about this is that you can use this SDL.DLL with any SDL program (e.g. DOSBox, SCUMMVM...).

* '''DOSBox with MT-32 emulation (by Canadacow)'''
** Last updated: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** Description: ''This build is no longer useful''; it was made before DOSBox 0.63 came out and contains MT-32 emulation code that is much older than the current Munt releases. Note that more current MT-32 emulation is also included as an unofficial feature of some of the newer SVN builds.

==Useful Links==

===SVN changelog===
The following links list the latest changes to the official DOSBox source code on its sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://sourceforge.net/p/dosbox/code-0/3852/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2014-01-01'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://www.vogons.org/viewtopic.php?t=7323

===Making your own SVN build===
The following DOSBoxWiki article discusses the process of making your own SVN build from the official DOSBox SVN source code:
* [[BuildingDOSBox]]

===Snapshot of latest DOSBox SVN source code===
Snapshots of the latest SVN versions of the DOSBox source code are available at the following URL(s) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/?view=tar (auto-generated tarball created by sourceforge.net)
* http://sourceforge.net/scm/?type=svn&group_id=52551 (sourceforge.net instructions for accessing official DOSBox SVN repository)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)

==Unofficial ports==
These builds are for other Operating Systems and hardware platforms and are not in any way supported by the DOSBox team.

===Android===
* '''AnDOSBox''' (ver. 0.74, v1.2.8, 2012-10-18)
** URL: http://sites.google.com/site/andosbox/

* '''DosBox Turbo''' (ver. 0.74 SVN, v2.1.19, 2015-02-25)
** URL: http://sites.google.com/site/dosboxturbo/

* '''Magic Dosbox''' (ver. 0.74, v1.0.29, 2015-06-30)
** URL: http://magicbox.imejl.sk

* '''aDOSBox''' (ver. 0.73, v0.2.5, 2011-05-16)
** URL: http://androiddosbox.appspot.com

===iOS===
* '''DOSPad''' (ver. 0.74, v1.96, 2011-01)
** URL: http://www.litchie.com/?page_id=123

===PSP===
* '''DOSBox PSP''' (ver. 0.71, 2008-08-03)
** <s>URL: http://www.qj.net/tag/crazyc-gaming-news.html</s>
** URL: http://www.pspdosbox.co.uk
** <s>URL: http://forums.ps2dev.org/viewtopic.php?t=9564</s>

===Pocket PC / Windows Mobile===
* '''DosBox PPC''' (ver. 0.73, 2009-07-06)
** URL: http://n0p.8bit.fm

===Wii===
* '''DOSBox for Wii''' (ver. 0.74, v1.7, 2012-06-30)
** URL: http://code.google.com/p/dosbox-wii/

===Dreamcast===
* '''DOSBox for Dreamcast''' (ver. 0.60, 2005?)
** URL: http://gpf.dcemu.co.uk/dcdoxbox.shtml

===GP2x===
* '''DOSBox for GP2x''' (ver. 0.72, 2009-01-03)
** URL: http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,72,2534
** <s>URL: http://wiki.gp2x.org/wiki/DosBox</s>

* '''DOSBox for GP2x Wiz''' (ver. 0.72, 2009-08-27)
** URL: http://dl.openhandhelds.org/cgi-bin/wiz.cgi?0,0,0,0,72,198

* '''DOSBox for GP2x Caanoo''' (ver. 0.74, 2012-01-14)
** URL: http://dl.openhandhelds.org/cgi-bin/caanoo.cgi?0,0,0,0,72,826

===Dingoo A320===
* '''DOSBox for Dingoo A320''' (ver. 0.74, 2013-03-11)
** URL: http://www.slaanesh.net/2013/03/dosbox-074-open-dingux.html

===OS/2===
* '''DOSBox/2''' (ver. 0.74, 2010-09-17)
** <s>URL: http://www.os2site.com/sw/emulators/dosbox/index.html<s/>
** URL: http://www.joschs-robotics.de/dosbox/
** URL: http://wiki.netlabs.org/index.php/DOSBox_Port

===AmigaOS 4.0===
* '''DOSBox for AmigaOS 4.0''' (ver. 0.72, 2009-06-14)
** URL: http://www.os4depot.net/share/emulation/computer/dosbox.lha
** URL: http://www.os4depot.net/index.php?function=browse&cat=emulation/computer

===Java===
* '''jDosbox''' (ver. v0.74, v0.74.28, 2013-02-27)
** URL: http://jdosbox.sourceforge.net

===JavaScript===
* '''JsDOSBox''' (ver. 0.74, v3.2, 2015-02-14)
** URL: http://sourceforge.net/projects/jsdosbox/

===IRIX===
* '''DOSBox for IRIX''' (ver. 0.71, 2007?)
** URL: http://www.spam-filter.de/dosbox/dosbox_on_irix
** <s>URL: http://www.enosnusnu.de/index.php?/archives/98-DOSBox-on-IRIX.html</s>
** Notes: Original enosnusnu.de link seems to now redirect to spam-filter.de. I added a link to a DOSBox on IRIX page on the latter site, but it appears that it may only offer a source code tarball and no binary.

===PXA270===
* '''DOSBox "Optimized" for PXA270 (by wellswang & kkazakov)''' (ver. 0.70, 2007-03-19)
** <s>URL: http://www.oesf.org/forum/index.php?showtopic=18415&st=270&p=156742&#entry156742</s>
** URL: http://wells.osall.com/files/download.php?id=1727
** URL: http://www.oesf.org/forums/index.php?s=1dec7dd003587d385fbec45efb1ffbaa&showtopic=18415&st=270&p=156742&#entry156742

SVN Builds

2015-07-07T19:50:05Z

Tertz2: /* Java */

This article is a discussion of the general purpose of DOSBox SVN builds, and a list of which known public ones exist and where to get them. The first part is a FAQ covering various questions regarding DOSBox SVN builds; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.

==SVN Builds FAQ==

===What are SVN builds?===
SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on [http://www.sourceforge.net/ sourceforge.net] in something called an SVN repository. SVN builds contain changes that have been made by the DOSBox developers since the latest official release. Some enhanced SVN builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.

===Why should I use an SVN build?===
Every so often a new official version of DOSBox is released. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release is several years old, and is therefore missing a significant amount of work performed by the developers. If you're having trouble running a game with the current DOSBox release, it's worth trying an SVN build to see if the problem has been addressed since then. You may also want access to the new features or optimizations if you are having compatibility or performance issues.

===Which one should I use?===
That's up to you. Consult the list below to see which features the different builds contain and decide which one you want to try first. If you are interested in trying an SVN build in hopes that it will fix a problem you're having in the latest release version, you should probably start with a "plain" (no-enhancements) SVN build. Also, see replies to this post from the maintainers for additional info on their builds.

===How do I use it?===
Some SVN builds come packaged as a fully-functional DOSBox distribution, so you can simply unpack the archive into an empty folder and run it. Other builds contain only a custom dosbox executable binary (e.g. dosbox.exe) and possibly some supporting libraries, and require that you first install the latest official release of DOSBox and then unpack the SVN build over the top of it - replacing the release versions of the files with the SVN versions. Some developers also recommend regenerating your dosbox.conf configuration file so that you will see any new config options that have been added. Consult [http://www.vogons.org/viewtopic.php?p=68701#68701 this forum thread] for info on how to regenerate a config file.

===What do I do if I find bugs in an SVN build?===
First, search the DOSBox community forums to see if it's already been reported. If it hasn't, post as much information as possible (see the [http://www.vogons.org/viewtopic.php?t=2949 help request guidelines]). ''Update:'' Note that bugs in plain SVN builds are probably the only ones of interest to the DOSBox developers. Problem reports for the other builds should be addressed to their respective maintainers, as problems could be caused by experimental patches that aren't part of the official SVN source code.

===Where can I go to talk about SVN builds? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://www.vogons.org/viewtopic.php?t=9306 forum thread] where this article originally started.

==List of SVN Builds==

===Plain/vanilla/clean SVN builds===
The following SVN builds are based directly off of the official DOSBox SVN source code. Use these builds to test the latest official SVN changes:

* '''EmuCR''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.7 (ppc/intel)
** URL: http://dl.dropbox.com/u/7737184/Dosbox/Dosbox-Snapshot.dmg
** Notes: Automatically updated on changes to SVN.

===Enhanced SVN builds===
The following SVN builds contain additional fixes and/or features that are not officially part of DOSBox. Many people prefer them due to the included extra features that are not included in in the SVN. Note that if you have problems with these builds, it may be due to the unofficial changes that have been made by their maintainers and not the official DOSBox code itself that is to blame:

* '''DOSBox with Long File Name (LFN) and mouse copy/past support''' by Wengier
** Last updated: 2014-10-26
** SVN base version: r3871
** URL: http://www.vogons.org/viewtopic.php?t=40610 (discussion + source + Windows binary)
** URL: http://www.vogons.org/viewtopic.php?t=41179 (discussion + source + Windows binary)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** Description: This is a build of DOSBox based on its SVN version that adds Long File Name (LFN) and mouse copy/past support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). Windows binaries are provided, but sources should work on other platforms too (pdcurses is required for the cross-platform clipboard copy/paste feature).

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** URL: http://cafe.daum.net/dosbox
** Description: The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc. Recent versions include DOSBox-X branch changes as well.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

===Obsolete SVN/CVS builds===
These builds appear to be no longer maintained, and are listed here for historical reference.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''Tharos (by XTale)'''
** Last updated: 2010-03-28
** <s>URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc</s>
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

* '''gulikoza'''
** Last Updated: 2009-07-09
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** Description: Recently Moe has decided to provide a DOSBox Linux (x86, 32-bit, Athlon64-optimized) binary including some useful patches. It is built against latest CVS and includes at least these patches: addkey, adlib optimize, Innovation SSI-2001, Self-Modifying-Code optimizations, SVGA chipsets, CD-Image cycling, Glide emulation, Printer emulation.
** Notes: Moe is also the creator of OPENGL-HQ. OPENGL-HQ is another scaler that is implemented in SDL.dll. Unfortunately it may be some time (or never), until OPENGL-HQ is implemented in the official SDL so until then you'll have to download it from here (or compile it yourself). Neat thing about this is that you can use this SDL.DLL with any SDL program (e.g. DOSBox, SCUMMVM...).

* '''DOSBox with MT-32 emulation (by Canadacow)'''
** Last updated: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** Description: ''This build is no longer useful''; it was made before DOSBox 0.63 came out and contains MT-32 emulation code that is much older than the current Munt releases. Note that more current MT-32 emulation is also included as an unofficial feature of some of the newer SVN builds.

==Useful Links==

===SVN changelog===
The following links list the latest changes to the official DOSBox source code on its sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://sourceforge.net/p/dosbox/code-0/3852/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2014-01-01'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://www.vogons.org/viewtopic.php?t=7323

===Making your own SVN build===
The following DOSBoxWiki article discusses the process of making your own SVN build from the official DOSBox SVN source code:
* [[BuildingDOSBox]]

===Snapshot of latest DOSBox SVN source code===
Snapshots of the latest SVN versions of the DOSBox source code are available at the following URL(s) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/?view=tar (auto-generated tarball created by sourceforge.net)
* http://sourceforge.net/scm/?type=svn&group_id=52551 (sourceforge.net instructions for accessing official DOSBox SVN repository)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)

==Unofficial ports==
These builds are for other Operating Systems and hardware platforms and are not in any way supported by the DOSBox team.

===Android===
* '''AnDOSBox''' (ver. 0.74, v1.2.8, 2012-10-18)
** URL: http://sites.google.com/site/andosbox/

* '''DosBox Turbo''' (ver. 0.74 SVN, v2.1.19, 2015-02-25)
** URL: http://sites.google.com/site/dosboxturbo/

* '''Magic Dosbox''' (ver. 0.74, v1.0.29, 2015-06-30)
** URL: http://magicbox.imejl.sk

* '''aDOSBox''' (ver. 0.73, v0.2.5, 2011-05-16)
** URL: http://androiddosbox.appspot.com

===iOS===
* '''DOSPad''' (ver. 0.74, v1.96, 2011-01)
** URL: http://www.litchie.com/?page_id=123

===PSP===
* '''DOSBox PSP''' (ver. 0.71, 2008-08-03)
** <s>URL: http://www.qj.net/tag/crazyc-gaming-news.html</s>
** URL: http://www.pspdosbox.co.uk
** <s>URL: http://forums.ps2dev.org/viewtopic.php?t=9564</s>

===Pocket PC / Windows Mobile===
* '''DosBox PPC''' (ver. 0.73, 2009-07-06)
** URL: http://n0p.8bit.fm

===Wii===
* '''DOSBox for Wii''' (ver. 0.74, v1.7, 2012-06-30)
** URL: http://code.google.com/p/dosbox-wii/

===Dreamcast===
* '''DOSBox for Dreamcast''' (ver. 0.60, 2005?)
** URL: http://gpf.dcemu.co.uk/dcdoxbox.shtml

===GP2x===
* '''DOSBox for GP2x''' (ver. 0.72, 2009-01-03)
** URL: http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,72,2534
** <s>URL: http://wiki.gp2x.org/wiki/DosBox</s>

* '''DOSBox for GP2x Wiz''' (ver. 0.72, 2009-08-27)
** URL: http://dl.openhandhelds.org/cgi-bin/wiz.cgi?0,0,0,0,72,198

* '''DOSBox for GP2x Caanoo''' (ver. 0.74, 2012-01-14)
** URL: http://dl.openhandhelds.org/cgi-bin/caanoo.cgi?0,0,0,0,72,826

===Dingoo A320===
* '''DOSBox for Dingoo A320''' (ver. 0.73, 2010-04-26)
** URL: http://www.slaanesh.net/2010/04/dosbox-073-for-dingoo-a320-and-ben.html

===OS/2===
* '''DOSBox/2''' (ver. 0.74, 2010-09-17)
** <s>URL: http://www.os2site.com/sw/emulators/dosbox/index.html<s/>
** URL: http://www.joschs-robotics.de/dosbox/
** URL: http://wiki.netlabs.org/index.php/DOSBox_Port

===AmigaOS 4.0===
* '''DOSBox for AmigaOS 4.0''' (ver. 0.72, 2009-06-14)
** URL: http://www.os4depot.net/share/emulation/computer/dosbox.lha
** URL: http://www.os4depot.net/index.php?function=browse&cat=emulation/computer

===Java===
* '''jDosbox''' (ver. v0.74, v0.74.28, 2013-02-27)
** URL: http://jdosbox.sourceforge.net

===JavaScript===
* '''JsDOSBox''' (ver. 0.74, v3.2, 2015-02-14)
** URL: http://sourceforge.net/projects/jsdosbox/

===IRIX===
* '''DOSBox for IRIX''' (ver. 0.71, 2007?)
** URL: http://www.spam-filter.de/dosbox/dosbox_on_irix
** <s>URL: http://www.enosnusnu.de/index.php?/archives/98-DOSBox-on-IRIX.html</s>
** Notes: Original enosnusnu.de link seems to now redirect to spam-filter.de. I added a link to a DOSBox on IRIX page on the latter site, but it appears that it may only offer a source code tarball and no binary.

===PXA270===
* '''DOSBox "Optimized" for PXA270 (by wellswang & kkazakov)''' (ver. 0.70, 2007-03-19)
** <s>URL: http://www.oesf.org/forum/index.php?showtopic=18415&st=270&p=156742&#entry156742</s>
** URL: http://wells.osall.com/files/download.php?id=1727
** URL: http://www.oesf.org/forums/index.php?s=1dec7dd003587d385fbec45efb1ffbaa&showtopic=18415&st=270&p=156742&#entry156742

SVN Builds

2015-07-07T19:45:58Z

Tertz2: /* JavaScript */

This article is a discussion of the general purpose of DOSBox SVN builds, and a list of which known public ones exist and where to get them. The first part is a FAQ covering various questions regarding DOSBox SVN builds; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.

==SVN Builds FAQ==

===What are SVN builds?===
SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on [http://www.sourceforge.net/ sourceforge.net] in something called an SVN repository. SVN builds contain changes that have been made by the DOSBox developers since the latest official release. Some enhanced SVN builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.

===Why should I use an SVN build?===
Every so often a new official version of DOSBox is released. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release is several years old, and is therefore missing a significant amount of work performed by the developers. If you're having trouble running a game with the current DOSBox release, it's worth trying an SVN build to see if the problem has been addressed since then. You may also want access to the new features or optimizations if you are having compatibility or performance issues.

===Which one should I use?===
That's up to you. Consult the list below to see which features the different builds contain and decide which one you want to try first. If you are interested in trying an SVN build in hopes that it will fix a problem you're having in the latest release version, you should probably start with a "plain" (no-enhancements) SVN build. Also, see replies to this post from the maintainers for additional info on their builds.

===How do I use it?===
Some SVN builds come packaged as a fully-functional DOSBox distribution, so you can simply unpack the archive into an empty folder and run it. Other builds contain only a custom dosbox executable binary (e.g. dosbox.exe) and possibly some supporting libraries, and require that you first install the latest official release of DOSBox and then unpack the SVN build over the top of it - replacing the release versions of the files with the SVN versions. Some developers also recommend regenerating your dosbox.conf configuration file so that you will see any new config options that have been added. Consult [http://www.vogons.org/viewtopic.php?p=68701#68701 this forum thread] for info on how to regenerate a config file.

===What do I do if I find bugs in an SVN build?===
First, search the DOSBox community forums to see if it's already been reported. If it hasn't, post as much information as possible (see the [http://www.vogons.org/viewtopic.php?t=2949 help request guidelines]). ''Update:'' Note that bugs in plain SVN builds are probably the only ones of interest to the DOSBox developers. Problem reports for the other builds should be addressed to their respective maintainers, as problems could be caused by experimental patches that aren't part of the official SVN source code.

===Where can I go to talk about SVN builds? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://www.vogons.org/viewtopic.php?t=9306 forum thread] where this article originally started.

==List of SVN Builds==

===Plain/vanilla/clean SVN builds===
The following SVN builds are based directly off of the official DOSBox SVN source code. Use these builds to test the latest official SVN changes:

* '''EmuCR''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.7 (ppc/intel)
** URL: http://dl.dropbox.com/u/7737184/Dosbox/Dosbox-Snapshot.dmg
** Notes: Automatically updated on changes to SVN.

===Enhanced SVN builds===
The following SVN builds contain additional fixes and/or features that are not officially part of DOSBox. Many people prefer them due to the included extra features that are not included in in the SVN. Note that if you have problems with these builds, it may be due to the unofficial changes that have been made by their maintainers and not the official DOSBox code itself that is to blame:

* '''DOSBox with Long File Name (LFN) and mouse copy/past support''' by Wengier
** Last updated: 2014-10-26
** SVN base version: r3871
** URL: http://www.vogons.org/viewtopic.php?t=40610 (discussion + source + Windows binary)
** URL: http://www.vogons.org/viewtopic.php?t=41179 (discussion + source + Windows binary)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** Description: This is a build of DOSBox based on its SVN version that adds Long File Name (LFN) and mouse copy/past support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). Windows binaries are provided, but sources should work on other platforms too (pdcurses is required for the cross-platform clipboard copy/paste feature).

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** URL: http://cafe.daum.net/dosbox
** Description: The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc. Recent versions include DOSBox-X branch changes as well.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

===Obsolete SVN/CVS builds===
These builds appear to be no longer maintained, and are listed here for historical reference.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''Tharos (by XTale)'''
** Last updated: 2010-03-28
** <s>URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc</s>
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

* '''gulikoza'''
** Last Updated: 2009-07-09
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** Description: Recently Moe has decided to provide a DOSBox Linux (x86, 32-bit, Athlon64-optimized) binary including some useful patches. It is built against latest CVS and includes at least these patches: addkey, adlib optimize, Innovation SSI-2001, Self-Modifying-Code optimizations, SVGA chipsets, CD-Image cycling, Glide emulation, Printer emulation.
** Notes: Moe is also the creator of OPENGL-HQ. OPENGL-HQ is another scaler that is implemented in SDL.dll. Unfortunately it may be some time (or never), until OPENGL-HQ is implemented in the official SDL so until then you'll have to download it from here (or compile it yourself). Neat thing about this is that you can use this SDL.DLL with any SDL program (e.g. DOSBox, SCUMMVM...).

* '''DOSBox with MT-32 emulation (by Canadacow)'''
** Last updated: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** Description: ''This build is no longer useful''; it was made before DOSBox 0.63 came out and contains MT-32 emulation code that is much older than the current Munt releases. Note that more current MT-32 emulation is also included as an unofficial feature of some of the newer SVN builds.

==Useful Links==

===SVN changelog===
The following links list the latest changes to the official DOSBox source code on its sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://sourceforge.net/p/dosbox/code-0/3852/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2014-01-01'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://www.vogons.org/viewtopic.php?t=7323

===Making your own SVN build===
The following DOSBoxWiki article discusses the process of making your own SVN build from the official DOSBox SVN source code:
* [[BuildingDOSBox]]

===Snapshot of latest DOSBox SVN source code===
Snapshots of the latest SVN versions of the DOSBox source code are available at the following URL(s) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/?view=tar (auto-generated tarball created by sourceforge.net)
* http://sourceforge.net/scm/?type=svn&group_id=52551 (sourceforge.net instructions for accessing official DOSBox SVN repository)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)

==Unofficial ports==
These builds are for other Operating Systems and hardware platforms and are not in any way supported by the DOSBox team.

===Android===
* '''AnDOSBox''' (ver. 0.74, v1.2.8, 2012-10-18)
** URL: http://sites.google.com/site/andosbox/

* '''DosBox Turbo''' (ver. 0.74 SVN, v2.1.19, 2015-02-25)
** URL: http://sites.google.com/site/dosboxturbo/

* '''Magic Dosbox''' (ver. 0.74, v1.0.29, 2015-06-30)
** URL: http://magicbox.imejl.sk

* '''aDOSBox''' (ver. 0.73, v0.2.5, 2011-05-16)
** URL: http://androiddosbox.appspot.com

===iOS===
* '''DOSPad''' (ver. 0.74, v1.96, 2011-01)
** URL: http://www.litchie.com/?page_id=123

===PSP===
* '''DOSBox PSP''' (ver. 0.71, 2008-08-03)
** <s>URL: http://www.qj.net/tag/crazyc-gaming-news.html</s>
** URL: http://www.pspdosbox.co.uk
** <s>URL: http://forums.ps2dev.org/viewtopic.php?t=9564</s>

===Pocket PC / Windows Mobile===
* '''DosBox PPC''' (ver. 0.73, 2009-07-06)
** URL: http://n0p.8bit.fm

===Wii===
* '''DOSBox for Wii''' (ver. 0.74, v1.7, 2012-06-30)
** URL: http://code.google.com/p/dosbox-wii/

===Dreamcast===
* '''DOSBox for Dreamcast''' (ver. 0.60, 2005?)
** URL: http://gpf.dcemu.co.uk/dcdoxbox.shtml

===GP2x===
* '''DOSBox for GP2x''' (ver. 0.72, 2009-01-03)
** URL: http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,72,2534
** <s>URL: http://wiki.gp2x.org/wiki/DosBox</s>

* '''DOSBox for GP2x Wiz''' (ver. 0.72, 2009-08-27)
** URL: http://dl.openhandhelds.org/cgi-bin/wiz.cgi?0,0,0,0,72,198

* '''DOSBox for GP2x Caanoo''' (ver. 0.74, 2012-01-14)
** URL: http://dl.openhandhelds.org/cgi-bin/caanoo.cgi?0,0,0,0,72,826

===Dingoo A320===
* '''DOSBox for Dingoo A320''' (ver. 0.73, 2010-04-26)
** URL: http://www.slaanesh.net/2010/04/dosbox-073-for-dingoo-a320-and-ben.html

===OS/2===
* '''DOSBox/2''' (ver. 0.74, 2010-09-17)
** <s>URL: http://www.os2site.com/sw/emulators/dosbox/index.html<s/>
** URL: http://www.joschs-robotics.de/dosbox/
** URL: http://wiki.netlabs.org/index.php/DOSBox_Port

===AmigaOS 4.0===
* '''DOSBox for AmigaOS 4.0''' (ver. 0.72, 2009-06-14)
** URL: http://www.os4depot.net/share/emulation/computer/dosbox.lha
** URL: http://www.os4depot.net/index.php?function=browse&cat=emulation/computer

===Java===
* '''jDosbox''' (ver. v0.74, v0.74.25, 2011-08-25)
** URL: http://jdosbox.sourceforge.net

===JavaScript===
* '''JsDOSBox''' (ver. 0.74, v3.2, 2015-02-14)
** URL: http://sourceforge.net/projects/jsdosbox/

===IRIX===
* '''DOSBox for IRIX''' (ver. 0.71, 2007?)
** URL: http://www.spam-filter.de/dosbox/dosbox_on_irix
** <s>URL: http://www.enosnusnu.de/index.php?/archives/98-DOSBox-on-IRIX.html</s>
** Notes: Original enosnusnu.de link seems to now redirect to spam-filter.de. I added a link to a DOSBox on IRIX page on the latter site, but it appears that it may only offer a source code tarball and no binary.

===PXA270===
* '''DOSBox "Optimized" for PXA270 (by wellswang & kkazakov)''' (ver. 0.70, 2007-03-19)
** <s>URL: http://www.oesf.org/forum/index.php?showtopic=18415&st=270&p=156742&#entry156742</s>
** URL: http://wells.osall.com/files/download.php?id=1727
** URL: http://www.oesf.org/forums/index.php?s=1dec7dd003587d385fbec45efb1ffbaa&showtopic=18415&st=270&p=156742&#entry156742

SVN Builds

2015-07-07T19:37:47Z

Tertz2: /* Android */

This article is a discussion of the general purpose of DOSBox SVN builds, and a list of which known public ones exist and where to get them. The first part is a FAQ covering various questions regarding DOSBox SVN builds; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.

==SVN Builds FAQ==

===What are SVN builds?===
SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on [http://www.sourceforge.net/ sourceforge.net] in something called an SVN repository. SVN builds contain changes that have been made by the DOSBox developers since the latest official release. Some enhanced SVN builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.

===Why should I use an SVN build?===
Every so often a new official version of DOSBox is released. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release is several years old, and is therefore missing a significant amount of work performed by the developers. If you're having trouble running a game with the current DOSBox release, it's worth trying an SVN build to see if the problem has been addressed since then. You may also want access to the new features or optimizations if you are having compatibility or performance issues.

===Which one should I use?===
That's up to you. Consult the list below to see which features the different builds contain and decide which one you want to try first. If you are interested in trying an SVN build in hopes that it will fix a problem you're having in the latest release version, you should probably start with a "plain" (no-enhancements) SVN build. Also, see replies to this post from the maintainers for additional info on their builds.

===How do I use it?===
Some SVN builds come packaged as a fully-functional DOSBox distribution, so you can simply unpack the archive into an empty folder and run it. Other builds contain only a custom dosbox executable binary (e.g. dosbox.exe) and possibly some supporting libraries, and require that you first install the latest official release of DOSBox and then unpack the SVN build over the top of it - replacing the release versions of the files with the SVN versions. Some developers also recommend regenerating your dosbox.conf configuration file so that you will see any new config options that have been added. Consult [http://www.vogons.org/viewtopic.php?p=68701#68701 this forum thread] for info on how to regenerate a config file.

===What do I do if I find bugs in an SVN build?===
First, search the DOSBox community forums to see if it's already been reported. If it hasn't, post as much information as possible (see the [http://www.vogons.org/viewtopic.php?t=2949 help request guidelines]). ''Update:'' Note that bugs in plain SVN builds are probably the only ones of interest to the DOSBox developers. Problem reports for the other builds should be addressed to their respective maintainers, as problems could be caused by experimental patches that aren't part of the official SVN source code.

===Where can I go to talk about SVN builds? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://www.vogons.org/viewtopic.php?t=9306 forum thread] where this article originally started.

==List of SVN Builds==

===Plain/vanilla/clean SVN builds===
The following SVN builds are based directly off of the official DOSBox SVN source code. Use these builds to test the latest official SVN changes:

* '''EmuCR''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.7 (ppc/intel)
** URL: http://dl.dropbox.com/u/7737184/Dosbox/Dosbox-Snapshot.dmg
** Notes: Automatically updated on changes to SVN.

===Enhanced SVN builds===
The following SVN builds contain additional fixes and/or features that are not officially part of DOSBox. Many people prefer them due to the included extra features that are not included in in the SVN. Note that if you have problems with these builds, it may be due to the unofficial changes that have been made by their maintainers and not the official DOSBox code itself that is to blame:

* '''DOSBox with Long File Name (LFN) and mouse copy/past support''' by Wengier
** Last updated: 2014-10-26
** SVN base version: r3871
** URL: http://www.vogons.org/viewtopic.php?t=40610 (discussion + source + Windows binary)
** URL: http://www.vogons.org/viewtopic.php?t=41179 (discussion + source + Windows binary)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** Description: This is a build of DOSBox based on its SVN version that adds Long File Name (LFN) and mouse copy/past support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). Windows binaries are provided, but sources should work on other platforms too (pdcurses is required for the cross-platform clipboard copy/paste feature).

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** URL: http://cafe.daum.net/dosbox
** Description: The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc. Recent versions include DOSBox-X branch changes as well.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

===Obsolete SVN/CVS builds===
These builds appear to be no longer maintained, and are listed here for historical reference.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''Tharos (by XTale)'''
** Last updated: 2010-03-28
** <s>URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc</s>
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

* '''gulikoza'''
** Last Updated: 2009-07-09
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** Description: Recently Moe has decided to provide a DOSBox Linux (x86, 32-bit, Athlon64-optimized) binary including some useful patches. It is built against latest CVS and includes at least these patches: addkey, adlib optimize, Innovation SSI-2001, Self-Modifying-Code optimizations, SVGA chipsets, CD-Image cycling, Glide emulation, Printer emulation.
** Notes: Moe is also the creator of OPENGL-HQ. OPENGL-HQ is another scaler that is implemented in SDL.dll. Unfortunately it may be some time (or never), until OPENGL-HQ is implemented in the official SDL so until then you'll have to download it from here (or compile it yourself). Neat thing about this is that you can use this SDL.DLL with any SDL program (e.g. DOSBox, SCUMMVM...).

* '''DOSBox with MT-32 emulation (by Canadacow)'''
** Last updated: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** Description: ''This build is no longer useful''; it was made before DOSBox 0.63 came out and contains MT-32 emulation code that is much older than the current Munt releases. Note that more current MT-32 emulation is also included as an unofficial feature of some of the newer SVN builds.

==Useful Links==

===SVN changelog===
The following links list the latest changes to the official DOSBox source code on its sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://sourceforge.net/p/dosbox/code-0/3852/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2014-01-01'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://www.vogons.org/viewtopic.php?t=7323

===Making your own SVN build===
The following DOSBoxWiki article discusses the process of making your own SVN build from the official DOSBox SVN source code:
* [[BuildingDOSBox]]

===Snapshot of latest DOSBox SVN source code===
Snapshots of the latest SVN versions of the DOSBox source code are available at the following URL(s) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/?view=tar (auto-generated tarball created by sourceforge.net)
* http://sourceforge.net/scm/?type=svn&group_id=52551 (sourceforge.net instructions for accessing official DOSBox SVN repository)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)

==Unofficial ports==
These builds are for other Operating Systems and hardware platforms and are not in any way supported by the DOSBox team.

===Android===
* '''AnDOSBox''' (ver. 0.74, v1.2.8, 2012-10-18)
** URL: http://sites.google.com/site/andosbox/

* '''DosBox Turbo''' (ver. 0.74 SVN, v2.1.19, 2015-02-25)
** URL: http://sites.google.com/site/dosboxturbo/

* '''Magic Dosbox''' (ver. 0.74, v1.0.29, 2015-06-30)
** URL: http://magicbox.imejl.sk

* '''aDOSBox''' (ver. 0.73, v0.2.5, 2011-05-16)
** URL: http://androiddosbox.appspot.com

===iOS===
* '''DOSPad''' (ver. 0.74, v1.96, 2011-01)
** URL: http://www.litchie.com/?page_id=123

===PSP===
* '''DOSBox PSP''' (ver. 0.71, 2008-08-03)
** <s>URL: http://www.qj.net/tag/crazyc-gaming-news.html</s>
** URL: http://www.pspdosbox.co.uk
** <s>URL: http://forums.ps2dev.org/viewtopic.php?t=9564</s>

===Pocket PC / Windows Mobile===
* '''DosBox PPC''' (ver. 0.73, 2009-07-06)
** URL: http://n0p.8bit.fm

===Wii===
* '''DOSBox for Wii''' (ver. 0.74, v1.7, 2012-06-30)
** URL: http://code.google.com/p/dosbox-wii/

===Dreamcast===
* '''DOSBox for Dreamcast''' (ver. 0.60, 2005?)
** URL: http://gpf.dcemu.co.uk/dcdoxbox.shtml

===GP2x===
* '''DOSBox for GP2x''' (ver. 0.72, 2009-01-03)
** URL: http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,72,2534
** <s>URL: http://wiki.gp2x.org/wiki/DosBox</s>

* '''DOSBox for GP2x Wiz''' (ver. 0.72, 2009-08-27)
** URL: http://dl.openhandhelds.org/cgi-bin/wiz.cgi?0,0,0,0,72,198

* '''DOSBox for GP2x Caanoo''' (ver. 0.74, 2012-01-14)
** URL: http://dl.openhandhelds.org/cgi-bin/caanoo.cgi?0,0,0,0,72,826

===Dingoo A320===
* '''DOSBox for Dingoo A320''' (ver. 0.73, 2010-04-26)
** URL: http://www.slaanesh.net/2010/04/dosbox-073-for-dingoo-a320-and-ben.html

===OS/2===
* '''DOSBox/2''' (ver. 0.74, 2010-09-17)
** <s>URL: http://www.os2site.com/sw/emulators/dosbox/index.html<s/>
** URL: http://www.joschs-robotics.de/dosbox/
** URL: http://wiki.netlabs.org/index.php/DOSBox_Port

===AmigaOS 4.0===
* '''DOSBox for AmigaOS 4.0''' (ver. 0.72, 2009-06-14)
** URL: http://www.os4depot.net/share/emulation/computer/dosbox.lha
** URL: http://www.os4depot.net/index.php?function=browse&cat=emulation/computer

===Java===
* '''jDosbox''' (ver. v0.74, v0.74.25, 2011-08-25)
** URL: http://jdosbox.sourceforge.net

===JavaScript===
* '''JsDOSBox''' (ver. 0.74, 2012-07)
** URL: http://sourceforge.net/projects/jsdosbox/

===IRIX===
* '''DOSBox for IRIX''' (ver. 0.71, 2007?)
** URL: http://www.spam-filter.de/dosbox/dosbox_on_irix
** <s>URL: http://www.enosnusnu.de/index.php?/archives/98-DOSBox-on-IRIX.html</s>
** Notes: Original enosnusnu.de link seems to now redirect to spam-filter.de. I added a link to a DOSBox on IRIX page on the latter site, but it appears that it may only offer a source code tarball and no binary.

===PXA270===
* '''DOSBox "Optimized" for PXA270 (by wellswang & kkazakov)''' (ver. 0.70, 2007-03-19)
** <s>URL: http://www.oesf.org/forum/index.php?showtopic=18415&st=270&p=156742&#entry156742</s>
** URL: http://wells.osall.com/files/download.php?id=1727
** URL: http://www.oesf.org/forums/index.php?s=1dec7dd003587d385fbec45efb1ffbaa&showtopic=18415&st=270&p=156742&#entry156742

4.77 MHz

2015-06-15T18:14:52Z

Tertz2: /* Other Tools You May Find Useful */

The IBM PC XT ran at 4.77 MHz. This describes how to run DOSBox at XT-like speeds for programs that do not perform their own timing. Keep in mind that DOSBox cannot run at exactly 4.77 MHz. At least, not exactly the way an IBM PC XT did. You can, however, get pretty darn close by testing with some benchmark tools.

As you will see in the testing below, various types of computer instructions run at widely various speeds on the different types of computer chips out there. The most striking example is perhaps math instructions that involve real numbers such as: 1.1 x 2.2 = 2.42. This is called floating-point math. Floating-point instructions were extremely slow on the 8086 CPU unless you installed the optional 8087 co-processor. It wasn't until the Pentium age that floating-point hardware was built into all PC CPU's. Anyway, the point is that DOSBox has only one speed control, and it slows down all computer instructions by the same percentage (more or less). It is therefore not possible to tell DOSBox to slow integer math by X%, floating-point math by Y%, and non-math by Z%, etc. Near-perfect 4.77 MHz speed will not be possible until someone builds an XT emulator specifically for this purpose. This is not likely to happen because close enough will always be, quite frankly, good enough.

== Searching for 4.77 MHz (XT) ==

Personally, I found the old DOS tool, MIPS, to be the most accurate and easiest-to-use tool thus far for use in the quest for 4.77 MHz. Look for MIPS.ZIP at the following FTP site (or [ftp://ftp.simtel.net/pub/simtelnet/msdos/sysinfo/mips.zip click here] [http://www.oldskool.org/guides/oldonnew/resources/mips.zip or here] to get it now):

:ftp://ftp.simtel.net/pub/simtelnet/msdos/sysinfo/ ([http://www.angelfire.com/in/Ronan/mirrors.html list of mirrors])

'''The contents of MIPS.DOC:'''

<code>
PROGRAM: MIPS.COM - Version 1.10 1986
PURPOSE: CPU Benchmark and Performance Test
USAGE: MIPS [Enter]

FUNCTIONS: Measures Million(s) of Instructions Per Second

(1) General Instructions - random
(2) Integer Instructions - ADD SUB MUL DIV
(3) Memory to Memory - MOV RAM to RAM
(4) Register to Register - MOV REG to REG
(5) Register to Memory - MOV REG to RAM

(6) Performance Rating - average

COPYRIGHT: (C) 1986 Chips and Technologies, Inc.
</code>

'''Running MIPS produces a screen similar to this:'''

<code>
+---------------------------------------------------+
| MIPS v1.10 CPU Benchmark and Performance Test |
+-----------------------------------------------------------+
| | Million Instructions Per Second | 10:10:00 |
+-----------------------------------------------------------+
| BENCHMARK: | IBM/XT IBM/AT COMPAQ | |
| | 4.7Mhz 8Mhz 386 | MIPS |
|----------------------|----------------------------|-------|
| General Instructions | 25.83 7.51 3.79 | 4.29 |
| Integer Instructions | 16.92 2.64 1.16 | 2.85 |
| Memory to Memory | 7.79 2.40 1.34 | 1.85 |
| Register to Register | 18.07 2.35 0.98 | 3.25 |
| Register to Memory | 20.72 6.22 3.43 | 6.39 |
| | | |
| Performance Rating | 18.24 4.40 2.16 | 3.72 |
+-----------------------------------------------------------+
</code>

'''''Note:''' If you run MIPS at too high a speed, the numbers will get large enough to screw up the formatting and make the results mostly unreadable.''

=== Steps to Find 4.77 MHz ===

#Download MIPS and place it in an easy-to-find folder. (I created a DOSTOOLS folder inside my DOSBOX folder.)
#Make these changes to your [[dosbox.conf]] file:
#:[[dosbox.conf#.5Bsdl.5D|[sdl]]]
#:fullscreen=false
#:[[dosbox.conf#.5Bcpu.5D|[cpu]]]
#:cycles=300
#:cycleup=1
#:cycledown=1
#:[[dosbox.conf#.5Bautoexec.5D|[autoexec]]]
#:mount C "C:\Program Files\DOSBox\DOSTools\"
#:C:
#:cd \
#[[Basic Setup and Installation of DosBox|Launch]] DOSBox. Then run MIPS from the [[Command Line|command line]].
#Your goal is to get the Performance Rating in the IBM/XT column to equal 1.00. To do this, press [[Special Keys|Ctrl-F11]] (slow down) or [[Special Keys|Ctrl-F12]] (speed up) several times while watching the CPU Cycles in DOXBox’s [[:file:Dosbox2.jpg|title bar]] change from 300 to your next test value.
#Run MIPS again. Repeat steps 4 and 5 until you get a Performance Rating of 1.00 (or as close as you need).
#Make a note of your final CPU Cycles value and set "cycles=xxx" to this value in your dosbox.conf whenever you need 4.77-MHz-like speed.

'''''Hint:''' I use Ronald Blankendaal’s great DBGL (DOSBox Game Launcher) [[DOSBoxFrontends|frontend]] to simplify many of the above tasks. Just point it to your MIPS.COM file and be sure to UNcheck the "Exit afterwards" box in the General tab to stay at the command line.''

=== Notes ===

Some users may prefer a speed at which General Instructions equals 1.00 (instead of Performance Rating). This depends entirely upon what kinds of instructions you feel affect the program’s speed the most. 2D games should not be using any floating-point math so no worries there. But predicting whether a program is integer heavy, memory heavy, or whatever heavy, would be pure sorcery. [Anyone care to modify a debugger to analyze this? Didn’t think so.] Really, just choose what feels best to you (actually, I can hardly tell the difference between cycles=245 and cycles=290).

Some testing was done with other benchmark tools to ''somewhat'' validate the MIPS results:
*SLOWDOWN 2.00 tends to agree with the MIPS Performance Rating but varies a bit depending on what speed you are slowing down from. (usage: slowdown /xt) (Not dynamic mode compatible.)
*COMPTEST 2.60 tends to agree with the MIPS General Instructions rating and also offers some interesting floating-point benchmarks. Speed is determined by executing a block of FSQRT instructions. (Not dynamic mode compatible.)
*CPUTEST (1989) will lead you towards setting CPU Cycles to about twice as high as these others and I have chosen to disregard these results due to “feel” of the XT programs at this higher speed.

My current DOSBox speed on a 1.3 GHz Athlon is cycles=245. At such low DOSBox speeds I am finding about a 1% difference between [[dosbox.conf#.5Bcpu.5D|Normal CPU Mode]] and [[dosbox.conf#.5Bcpu.5D|Dynamic CPU Mode]]. Therefore, you shouldn’t need to worry about benchmarking that setting. Interestingly, with dynamic mode versus normal mode, the Integer Instructions benchmark ~3% slower and Register to Register benchmarks ~10% faster (the other benchmarks are proportionately 1% faster). [No doubt, however, that dynamic mode plays a larger role at higher speeds.]

'''core=dynamic, cycles=243:'''
<code>
+---------------------------------------------------+
| MIPS v1.10 CPU Benchmark and Performance Test |
+-----------------------------------------------------------+
| | Million Instructions Per Second | 10:10:00 |
+-----------------------------------------------------------+
| BENCHMARK: | IBM/XT IBM/AT COMPAQ | |
| | 4.7Mhz 8Mhz 386 | MIPS |
|----------------------|----------------------------|-------|
| General Instructions | 0.85 0.25 0.12 | 0.14 |
| Integer Instructions | 1.42 0.22 0.10 | 0.23 |
| Memory to Memory | 1.02 0.31 0.17 | 0.24 |
| Register to Register | 1.48 0.19 0.08 | 0.26 |
| Register to Memory | 0.79 0.24 0.13 | 0.24 |
| | | |
| Performance Rating | 1.00 0.24 0.12 | 0.22 |
+-----------------------------------------------------------+
</code>

'''core=normal, cycles=245:'''
<code>
+---------------------------------------------------+
| MIPS v1.10 CPU Benchmark and Performance Test |
+-----------------------------------------------------------+
| | Million Instructions Per Second | 10:10:00 |
+-----------------------------------------------------------+
| BENCHMARK: | IBM/XT IBM/AT COMPAQ | |
| | 4.7Mhz 8Mhz 386 | MIPS |
|----------------------|----------------------------|-------|
| General Instructions | 0.85 0.25 0.12 | 0.14 |
| Integer Instructions | 1.48 0.23 0.10 | 0.24 |
| Memory to Memory | 1.02 0.31 0.18 | 0.24 |
| Register to Register | 1.35 0.18 0.07 | 0.24 |
| Register to Memory | 0.79 0.24 0.13 | 0.24 |
| | | |
| Performance Rating | 1.00 0.24 0.12 | 0.22 |
+-----------------------------------------------------------+
</code>

== Searching for 8 MHz (AT) ==

Does anyone really need to tell you to follow the above instructions for 4.77 MHz and use the IBM/AT column in MIPS instead of the IBM/XT column. Oh yeah, you might also want to start with cycles=500.

== Other Tools You May Find Useful ==

I tested several slowdown and benchmark tools and these are the ones that I have found so far to be useful/compatible in DOSBox:
;MIPS 1.10: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/mips.zip
;COMPTEST 2.60: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/ctest260.zip
;CPUTEST: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/cputest.zip
;SLOWDOWN 2.00: ftp://ftp.sunet.se/pub/simtelnet/msdos/sysutl/slodn200.zip
;PC Benchmark 6.0 : ftp://ftp.sunet.se/pub/simtelnet/msdos/sysinfo/pcben60a.zip

Performance

2015-06-10T18:53:26Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 400 MHz||386
|-
||Pentium III 1.0 GHz||486
|-
||Pentium III 1.4 GHz||486
|-
||Athlon XP 1.8 GHz||Pentium
|-
||Pentium 4 3.0 GHz||Pentium 166 MHz
|-
||Athlon 64 1.8 GHz||Pentium II
|-
||Core 2 Duo 8xxx 3.3 GHz||Pentium II 450 MHz
|-
||Core i7/i5 4xxx 4.0 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
''Note'': Based (generally) on [http://web.archive.org/web/20070127180145/http://www.gamers.org/pub/idgames/idstuff/quake/quake106.zip Quake 1.06] fps.

 
Rough dependency between cycles (core=normal) and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||310
|-
||286 16 MHz||3350
|-
||386DX 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|}
''Note'': Cycles are based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test Benchmark 1.14] by R. Agababyan

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-06-06T22:25:13Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 400 MHz||386
|-
||Pentium III 1.0 GHz||486
|-
||Pentium III 1.4 GHz||486
|-
||Athlon XP 1.8 GHz||Pentium
|-
||Pentium 4 3.0 GHz||Pentium 133 MHz
|-
||Athlon 64 1.8 GHz||Pentium II
|-
||Core 2 Duo 8xxx 3.3 GHz||Pentium II 450 MHz
|-
||Core i7/i5 4xxx 4.0 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
''Note'': Based (generally) on [http://web.archive.org/web/20070127180145/http://www.gamers.org/pub/idgames/idstuff/quake/quake106.zip Quake 1.06] fps.

 
Rough dependency between cycles (core=normal) and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||310
|-
||286 16 MHz||3350
|-
||386DX 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|}
''Note'': Cycles are based on [http://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test Benchmark 1.14] by R. Agababyan

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-06-06T10:40:15Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 400 MHz||386
|-
||Pentium III 1.0 GHz||486
|-
||Pentium III 1.4 GHz||486
|-
||Athlon XP 1.8 GHz||Pentium
|-
||Pentium 4 3.0 GHz||Pentium 133 MHz
|-
||Athlon 64 1.8 GHz||Pentium II
|-
||Core 2 Duo 8xxx 3.3 GHz||Pentium II 450 MHz
|-
||Core i5/i7 4xxx 4.4 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
''Note'': Based (generally) on [http://web.archive.org/web/20070127180145/http://www.gamers.org/pub/idgames/idstuff/quake/quake106.zip Quake 1.06] fps.

 
Rough dependency between cycles (core=normal) and emulated CPU. Different applications, even their parts, may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||310
|-
||286 16 MHz||3350
|-
||386DX 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|}
''Note'': Cycles are based on [https://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test Benchmark 1.14] by R. Agababyan

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-06-06T01:01:03Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. It's for core=dynamic (cycles=max), while core=normal may to be 10 times slower.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 400 MHz||386
|-
||Duron 800 MHz||486
|-
||Pentium III 1.0 GHz||486
|-
||Intel Atom 1.6 GHz||486
|-
||Pentium III 1.4 GHz||Pentium 75 MHz
|-
||Pentium 4 3.0 GHz||Pentium 166 MHz
|-
||Athlon XP 1.8 GHz||Pentium II
|-
||Athlon 64 1.8 GHz||Pentium II
|-
||Core 2 Duo 8xxx 3.3 GHz||Pentium II 450 MHz
|-
||Core i5/i7 4xxx 4.4 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
''Note'': Based (generally) on [https://web.archive.org/web/20070127180145/http://www.gamers.org/pub/idgames/idstuff/quake/quake106.zip Quake 1.06] speed.

 
Rough dependency between cycles (core=normal) and emulated CPU. Different applications may have different this dependency.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Emulated CPU!!Cycles
|-
||8088 4.77 MHz||310
|-
||286 16 MHz||3350
|-
||386DX 33 MHz||7800
|-
||486 66 MHz||26800
|-
||Pentium 100||77000
|}
''Note'': Cycles are based on [https://web.archive.org/web/20060201052402/http://www.agababyan.ru/FILES/UTIL/speedtst.zip Speed Test Benchmark 1.14] by R. Agababyan

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-05-25T15:10:41Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. For core=dynamic (cycles=max), while core=normal may to be 10 times slower.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 400 MHz||386
|-
||Duron 800 MHz||486
|-
||Pentium III 1.0 GHz||486
|-
||Intel Atom 1.6 GHz||486
|-
||Pentium III 1.4 GHz||Pentium 75 MHz
|-
||Pentium 4 3.0 GHz||Pentium 166 MHz
|-
||Athlon XP 1.8 GHz||Pentium II
|-
||Athlon 64 1.8 GHz||Pentium II
|-
||Core 2 Duo 8xxx 3.3 GHz||Pentium II 450 MHz
|-
||Core i5/i7 4xxx 4.4 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-05-23T00:04:56Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. For core=dynamic (cycles=max), while core=normal may to be 10 times slower.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 400 MHz||386
|-
||Duron 800 MHz||486
|-
||Pentium III 1.0 GHz||486
|-
||Intel Atom 1.6 GHz||486
|-
||Pentium III 1.4 GHz||Pentium 75 MHz
|-
||Pentium 4 3.0 GHz||Pentium 166 MHz
|-
||Pentium M 1.8 GHz||Pentium II
|-
||Athlon XP 1.8 GHz||Pentium II
|-
||Athlon 64 1.8 GHz||Pentium III
|-
||Core 2 Duo 1.8 GHz||Pentium III
|-
||Core i5/i7 4xxx 4.4 GHz||Pentium III 1 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-05-22T23:55:03Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough speed equivalent of emulated CPU for different host CPUs. For core=dynamic (cycles=max), while core=normal may to be 10 times slower.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 400 MHz||386
|-
||Duron 800 MHz||486
|-
||Pentium III 1.0 GHz||486
|-
||Intel Atom 1.6 GHz||486
|-
||Pentium III 1.4 GHz||Pentium 75 MHz
|-
||Pentium 4 3.0 GHz||Pentium 166 MHz
|-
||Pentium M 1.8 GHz||Pentium II
|-
||Athlon XP 1.8 GHz||Pentium II
|-
||Athlon 64 1.8 GHz||Pentium III
|-
||Core 2 Duo 1.8 GHz||Pentium III
|-
||Core i5/i7 4xxx 4.4 GHz||Pentium III 1.2 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-05-22T22:31:55Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough equivalency of emulated CPU for different host CPUs. For core=dynamic.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 400 MHz||386
|-
||Duron 800 MHz||486
|-
||Pentium III 1.0 GHz||486
|-
||Intel Atom 1.6 GHz||486
|-
||Pentium 4 3.0 GHz||Pentium 166 MHz
|-
||Pentium M 1.8 GHz||Pentium II
|-
||Athlon XP 1.8 GHz||Pentium II
|-
||Athlon 64 1.8 GHz||Pentium III
|-
||Core 2 Duo 1.8 GHz||Pentium III
|-
||Core i5/i7 4xxx 4.4 GHz||Pentium III 1.2 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Performance

2015-05-22T19:40:21Z

Tertz2: /* Emulated CPU equivalency */

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough equivalency of emulated CPU for different host CPUs. For core=dynamic.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 400 MHz||386
|-
||Duron 800 MHz||486
|-
||Pentium III 1.0 GHz||486
|-
||Intel Atom 1.6 GHz||486
|-
||Pentium 4 3.0 GHz||Pentium (*)
|-
||Pentium M 1.8 GHz||Pentium II
|-
||Athlon XP 1.8 GHz||Pentium II
|-
||Athlon 64 1.8 GHz||Pentium III
|-
||Core 2 Duo 1.8 GHz||Pentium III
|-
||Core i5/i7 4xxx 4.4 GHz||Pentium III 1.2 GHz
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
*) Duke Nukem 3D runs smooth at 640x480; Quake runs at 40 fps at 320x200.

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

System Requirements

2015-05-22T19:27:32Z

Tertz2:

The main requirement is a port of [http://www.libsdl.org libsdl] for your system. DOSBox should compile on every system with a decent C++ compiler like GCC.
----

Minimum requirements for Win32 port to run are minimum requirements for Windows 9x and SVGA card. But system requirements for smooth gaming depend on the requirements of the concrete game and the hardware choosen to be emulated in DOSBox.

Protected mode games are more resource-demanding. Although they will likely run on a 1 GHz machine, it is unlikely they will run quickly or smoothly. Be sure to read the sections on [[SpecialKeys|special function keys]] used by DOSBox, and how to run [[RunningResourceDemandingGames|resource demanding games]].

== See also ==
* [[Performance]]

Performance

2015-05-22T19:19:22Z

Tertz2:

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
The cycles=auto and cycles=max settings can be parameterized to have different startup defaults. The syntax is

cycles=auto ["realmode default"] ["protected mode default"%]
[limit "cycle limit"]
cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000

This will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000

== Emulated CPU equivalency ==

Rough equivalency of emulated CPU for different host CPUs. For core=dynamic.

{| border="1" cellspacing="0" cellpadding="5" style="text-align:center"
! Host CPU!!Emulated CPU
|-
||Pentium II 400 MHz||386
|-
||Duron 800 MHz||486
|-
||Pentium III 1.0 GHz||486
|-
||Intel Atom 1.6 GHz||486
|-
||Pentium 4 3.0 GHz||Pentium (*)
|-
||Pentium M 1.8 GHz||Pentium II
|-
||Athlon XP 1.8 GHz||Pentium II
|-
||Athlon 64 1.8 GHz||Pentium III
|-
||Core 2 Duo 1.8 GHz||Pentium III
|-
||Apple G3 500 MHz||386
|-
||Apple G4 1.0 GHz||486
|}
*) Duke Nukem 3D runs smooth at 640x480; Quake runs at 40 fps at 320x200.

== See also ==

* [[4.77 MHz]]
* [[DOSBox FAQ#Performance|DOSBox FAQ]]

Scaler

2013-12-17T12:35:50Z

Tertz2: output resolution tip

Back in the original days of DOS, games ran on specific resolutions on CRT monitors (and occasionally televisions). Limited hardware required these games to run on what is today considered extremely low resolutions. A Scaler is like a filter, that reprocesses the emulated screen before it is drawn on the physical monitor, and enables old games to take on a slightly updated look (or stylized look).

The scaler used can be changed in the [[dosbox.conf]] file; it can also be changed in DosBox session by using the ''scaler [name]'' command. The ''scaler'' command by itself will display the name of the active scaler.

To make screen's image to look more correct and less blurry, you need to set output monitor resolution as multiple of original game's resolution. For example, if a game works in 320x200, then good output resolutions are: 640x480, 960x720, 1280x960, 1600x1200, 1920x1440, etc. For correct image proportions you may need to set: aspect=true.

== Examples ==
These screen shots (of [[GAMES:Doom|Doom]]) represent a small section of the full game screen, and have been blown up 200% to better show how the image is being altered. Some effects are more subtle or visible depending on the range of colors displayed on the screen at individual moments.

{|
|-
|style="vertical-align: top;padding-left:30px"|

{|
|-
!Scaler
!Example
|-
|style="vertical-align: top;"|normal2x
normal3x
|[[Image:Scaler-normal2x.png]]
|-
|style="vertical-align: top;"|advmame2x
advmame3x
|[[Image:Scaler-advmame2x.png]]
|-
|style="vertical-align: top;"|hq2x
hq3x
|[[Image:Scaler-hq2x.png]]
|}

|style="vertical-align: top;padding-left:30px"|

{|
|-
!Scaler
!Example
|-
|style="vertical-align: top;"|2xsai
|[[Image:Scaler-2xsai.png]]
|-
|style="vertical-align: top;"|super2xsai
|[[Image:Scaler-super2xsai.png]]
|-
|style="vertical-align: top;"|advinterp2x
advinterp3x
|[[Image:Scaler-advinterp2x.png]]
|}

|style="vertical-align: top;padding-left:30px"|

{|
|-
!Scaler
!Example
|-
|style="vertical-align: top;"|tv2x
tv3x
|[[Image:Scaler-tv2x.png]]
|-
|style="vertical-align: top;"|rgb2x
rgb3x
|[[Image:Scaler-rgb2x.png]]
|-
|style="vertical-align: top;"|scan2x
scan3x
|[[Image:Scaler-scan2x.png]]
|}

|}