It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Just picked up an UM-ONE (roland usb to midi interface), an SC55 and an MT32.

I've gotten WC1/WC2/Xwing/a slew of sierra games (in dos box) to work with the um-one/sc55ormt32 without issue.

WCIII on the other hand seems to not like it.

Doing as I did on all the other games listed, I verified which "channel" the un-one was on (1) (see attachment), I modified the conf file of wc3 accordingly:

mpu401=intelligent
mididevice=default
midiconfig=1

But for some reason WCIII doesn't want to light up the physical gear, and wants to use "0" (the built in midi set for windows)....

Is it possible that the um-one isn't working on 330 (wcIII's setup app asks for specific address the "MPU-401" card would be running on if I had a true ISA mpu401/scc1 which I obviously don't has my modern pc doesn't have any isa slots........ [EDIT: its not the 330 issue, as I've installed a few more games and some of them asked for the 330 (ravenloft Strahd's possession, Day of the Tentacle) and they accepted that port number, and the games played through my physical midi hardware (1), and not (0) the built in midi set to windows.

I've tried setting "intelligent to "Uart" (no change), and 'none" (disables midi interface all together).

I haven't tried changing the "mididevice=default" to anything different.

Any ideas?

[edit 11-16-14]

I cannot reply to my own question on here, but someone else found the answer on the dosbox forums (vogons):
It seems that wc3 comes with dosbox 0.74, but is using a template file from an older version.

instead of config=1
it should be midiconfig=1.

after changing that line, it fired right up.

See vogons and search for topic "Wing Commander III on Dosbox with SC-55" (can't paste links right now)

If the ops can mark this as answered!
Attachments:
capture.jpg (53 Kb)
Post edited November 17, 2014 by playfulsteve
This question / problem has been solved by patricklibudaimage
On some releases GOG.com seems to use a newer version of DOSBox but with an older version of the config file.

Duke Nukem 3D is another example.

In such cases I just copy paste from a new, and blank, config file.
avatar
playfulsteve: Just picked up an UM-ONE (roland usb to midi interface), an SC55 and an MT32.

I've gotten WC1/WC2/Xwing/a slew of sierra games (in dos box) to work with the um-one/sc55ormt32 without issue.

WCIII on the other hand seems to not like it.

Doing as I did on all the other games listed, I verified which "channel" the un-one was on (1) (see attachment), I modified the conf file of wc3 accordingly:

mpu401=intelligent
mididevice=default
midiconfig=1

But for some reason WCIII doesn't want to light up the physical gear, and wants to use "0" (the built in midi set for windows)....

Is it possible that the um-one isn't working on 330 (wcIII's setup app asks for specific address the "MPU-401" card would be running on if I had a true ISA mpu401/scc1 which I obviously don't has my modern pc doesn't have any isa slots........ [EDIT: its not the 330 issue, as I've installed a few more games and some of them asked for the 330 (ravenloft Strahd's possession, Day of the Tentacle) and they accepted that port number, and the games played through my physical midi hardware (1), and not (0) the built in midi set to windows.

I've tried setting "intelligent to "Uart" (no change), and 'none" (disables midi interface all together).

I haven't tried changing the "mididevice=default" to anything different.

Any ideas?

[edit 11-16-14]

I cannot reply to my own question on here, but someone else found the answer on the dosbox forums (vogons):
It seems that wc3 comes with dosbox 0.74, but is using a template file from an older version.

instead of config=1
it should be midiconfig=1.

after changing that line, it fired right up.

See vogons and search for topic "Wing Commander III on Dosbox with SC-55" (can't paste links right now)

If the ops can mark this as answered!
Hi

Have got the same problem (and stuff). One way of solving it is to use a separate DOSBox installation and access the games causing problems manually instead of going through the GOG desktop shorcut.

The thing I do is to have a look at the EnterGameName_single.conf file in the directory of the respective game. There you will find the DOS commands to start the game. Enter them manually through your separate DOSBox installation and you should find that things suddenly work.

[Update: Yes it really does work. However, with some games you need 'midiconfig=' while 'config=' works for others.]

Cheers
Patrick
Post edited May 19, 2015 by patricklibuda
avatar
playfulsteve: Just picked up an UM-ONE (roland usb to midi interface), an SC55 and an MT32.

I've gotten WC1/WC2/Xwing/a slew of sierra games (in dos box) to work with the um-one/sc55ormt32 without issue.

WCIII on the other hand seems to not like it.

Doing as I did on all the other games listed, I verified which "channel" the un-one was on (1) (see attachment), I modified the conf file of wc3 accordingly:

mpu401=intelligent
mididevice=default
midiconfig=1

But for some reason WCIII doesn't want to light up the physical gear, and wants to use "0" (the built in midi set for windows)....

Is it possible that the um-one isn't working on 330 (wcIII's setup app asks for specific address the "MPU-401" card would be running on if I had a true ISA mpu401/scc1 which I obviously don't has my modern pc doesn't have any isa slots........ [EDIT: its not the 330 issue, as I've installed a few more games and some of them asked for the 330 (ravenloft Strahd's possession, Day of the Tentacle) and they accepted that port number, and the games played through my physical midi hardware (1), and not (0) the built in midi set to windows.

I've tried setting "intelligent to "Uart" (no change), and 'none" (disables midi interface all together).

I haven't tried changing the "mididevice=default" to anything different.

Any ideas?

[edit 11-16-14]

I cannot reply to my own question on here, but someone else found the answer on the dosbox forums (vogons):
It seems that wc3 comes with dosbox 0.74, but is using a template file from an older version.

instead of config=1
it should be midiconfig=1.

after changing that line, it fired right up.

See vogons and search for topic "Wing Commander III on Dosbox with SC-55" (can't paste links right now)

If the ops can mark this as answered!
avatar
patricklibuda: Hi

Have got the same problem (and stuff). One way of solving it is to use a separate DOSBox installation and access the games causing problems manually instead of going through the GOG desktop shorcut.

The thing I do is to have a look at the EnterGameName_single.conf file in the directory of the respective game. There you will find the DOS commands to start the game. Enter them manually through your separate DOSBox installation and you should find that things suddenly work.

[Update: Yes it really does work. However, with some games you need 'midiconfig=' while 'config=' works for others.]

Cheers
Patrick
Sorry for the late "Mark as Solution". It was a combination of your reply, and multiple .conf files......(I have dosbox installed, as well as the 'packaged' dosbox install that comes with some of these games.....I was modifying conf file for my manual dosbox install, but the referenced .conf file for the specific game had its own........all is well now (upgraded to win 10 as well, no issues on that front (um-one-mk2's driver gets installed natively by windows 10).