Network Q RAC Rally Championship installer issue \ VOGONS

Network Q RAC Rally Championship installer issue

Topic actions

First post, by P4R4D0X

Posted on 2013-05-14, 17:01

P4R4D0X Offline

Rank Member

Rank: Member
Posts: 100
Joined: 2012-10-06, 14:46

Yesterday I found an issue in DOSBox while I was trying to install Network Q RAC Rally Championship and it may be a bug. Posted it on the IRC channel and got no response, so I thought this should be mentioned here as well just in case it's something serious. Luckily I found workarounds and this is about the installer and not the game. Looked for similar topics here on VOGONS about the same issue, but there are none of them.

The ones I found are the following ones:
Network Q RAC Rally Championship (problem with installation)
This one is about installation issues, but that's due to the fact that no C:\ drive was mounted. mkkala claims that he got it to work, and so do I, but that's very little information given. I can confirm that the game works just fine, and there are no audio issues. He probably referred to this topic:
Network Q RAC Rally Championship sound problems

Pretty much I can reproduce it every time in DOSBox 0.74 and SVN. Tried messing around with various settings and still nothing. Here's what I did and what to look for. These are my mountings just in case someone asks. It's the plain good old mount commands that I always use with the default configuration.

1mount c c:\test
2mount d f:\ -t cdrom

Next I ran INSTALL.EXE from the disk to start the installer. It's actually very simple and looks amazing! For the keyboard layout I have chosen British and hit Enter.

The attachment install_000_205.png is no longer available

Next I was asked about installation type and I've chosen the Full (92Mb) one, to enjoy the movie clips and the CD audio tracks.

The attachment install_001.png is no longer available

For the destination directory I've kept the default one, and that's c:\rallyc\

The attachment install_002.png is no longer available

The installation will begin after pressing Enter, and you will see the progress bar filling up and eventually reaching 100%. It will even tell you that the installation has been completed. All nice and good until now.

The attachment install_003.png is no longer available

The installer will now run the sound setup program and this is where the problem will begin. I haven't pressed any button when I got the Installation completed message. I waited until SETSOUND.EXE was launched automatically. It will eventually launch and you will be stuck on the following screen:

The attachment setsound_000.png is no longer available

Nothing will show up and I can't do anything other than moving the cursor. The menus will simply refuse to show up to configure the sound card until I quit DOSBox, running it again, remounting the same drives and running SETSOUND.BAT or MSS\SETSOUND.EXE from the game directory. That's the only workaround I found, but that still leaves the installer broken. While I was looking in the debugger I get different results almost every time.

Here's what I get if I don't press anything and wait for the sound setup utility:

1  42938756: FILES:file open command 0 file C:\RALLYC\MSS\SETSOUND.EXE
2  42938761: DOSMISC:DOS:Multiplex Unhandled call 1687
3  42938765: DOSMISC:Get SDA, Let's hope for the best!
4  42943920: FILES:file open command 0 file C:\RALLYC\MSS\SETSOUND.EXE
5  42944085: FILES:file open command 0 file C:\RALLYC\MSS\SETSOUND.EXE
6  42945888: FILES:file open command 0 file C:\RALLYC\MSS\SETSOUND.EXE
7  42950111: DOSMISC:DOS:Multiplex Unhandled call 1684
8  42950132: PIT:PIT 0 Timer at 18.2065 Hz mode 2
9  42950708: MOUSE:New video is the same as the old
10  42950919: FILES:file open command 0 file ADRV688.DIG
11  42951052: FILES:file open command 0 file IWAV.DIG
12  42951168: FILES:file open command 0 file JAMMER.DIG
13  42951284: FILES:file open command 0 file NVDIG.DIG
14  42951400: FILES:file open command 0 file PROAUDIO.DIG
15  42952193: FILES:file open command 0 file RAP10.DIG
16  42952309: FILES:file open command 0 file SB16.DIG
17  42952425: FILES:file open command 0 file SBLASTER.DIG
18  42952541: FILES:file open command 0 file SBPRO.DIG
19  42952657: FILES:file open command 0 file SNDSCAPE.DIG
20  42952773: FILES:file open command 0 file SNDSYS.DIG
21  42952889: FILES:file open command 0 file ULTRA.DIG
22  42953849: FILES:file open command 0 file ADLIB.MDI
23  42953982: FILES:file open command 0 file ADLIBG.MDI
24  42955033: FILES:file open command 0 file ESFM.MDI
25  42955166: FILES:file open command 0 file IWAV.MDI
26  42955282: FILES:file open command 0 file MPU401.MDI
27  42955398: FILES:file open command 0 file MT32MPU.MDI
28  42955530: FILES:file open command 0 file NULL.MDI
29  42955646: FILES:file open command 0 file NVMPU.MDI
30  42956663: FILES:file open command 0 file OPL3.MDI
31  42956813: FILES:file open command 0 file PAS.MDI
32  42957877: FILES:file open command 0 file PASPLUS.MDI
33  42958606: FILES:file open command 0 file PCSPKR.MDI
34  42958722: FILES:file open command 0 file SBAWE32.MDI
35  42959451: FILES:file open command 0 file SBLASTER.MDI
36  42960196: FILES:file open command 0 file SBPRO1.MDI
37  42960925: FILES:file open command 0 file SBPRO2.MDI
38  42961654: FILES:file open command 0 file SNDSCAPE.MDI
39  42961770: FILES:file open command 0 file TANDY.MDI
40  42962499: FILES:file open command 0 file ULTRA.MDI
41  42963228: FILES:file open command 0 file MSSDRVR.LST
42  43284617: IO:Writing 00 to port 3246
43  43284619: IO:Writing 00 to port 3247
44  43284620: IO:Read from port 3246
45  43284620: IO:Read from port 3247
46  43284622: CPU:CPU:GRP5:Illegal opcode 0xff
47  43284623: CPU:CPU:GRP5:Illegal Call  7
48  43284623: CPU:Illegal/Unhandled opcode FFFF
49  43284624: CPU:CPU:GRP5:Illegal opcode 0xff
50  43284625: CPU:CPU:GRP5:Illegal Call  7
51  43284625: CPU:Illegal/Unhandled opcode FFFF
52  43284627: CPU:CPU:GRP5:Illegal Call  7
53  43284627: CPU:Illegal/Unhandled opcode FFFF
54  43284629: CPU:CPU:GRP5:Illegal Call  7
55  43284629: CPU:Illegal/Unhandled opcode FFFF

Great, now here's the same thing, I did the same thing and after FILES:file open command 0 file MSSDRVR.LST shows me this instead and it just spits out stuff like these:

1  42494491: CPU:Illegal/Unhandled opcode 0F00
2  42494494: CPU:Illegal/Unhandled opcode 0F00
3  42494497: CPU:Illegal/Unhandled opcode 0F00
4  42494500: CPU:Illegal/Unhandled opcode 0F00
5  42494503: CPU:Illegal/Unhandled opcode 0F00
6  42494506: CPU:Illegal/Unhandled opcode 0F00
7  42494509: CPU:Illegal/Unhandled opcode 0F00
8  42494512: CPU:Illegal/Unhandled opcode 0F00
9  42494513: DMA_CONTROL:Trying to read undefined DMA port 9
10  42494514: DMA_CONTROL:Trying to read undefined DMA port 9
11  42494515: CPU:Illegal/Unhandled opcode 0F00
12  42494516: DMA_CONTROL:Trying to read undefined DMA port a
13  42494517: DMA_CONTROL:Trying to read undefined DMA port a
14  42494518: CPU:Illegal/Unhandled opcode 0F00
15  42494519: DMA_CONTROL:Trying to read undefined DMA port b
16  42494520: DMA_CONTROL:Trying to read undefined DMA port b
17  42494521: CPU:Illegal/Unhandled opcode 0F00
18  42494522: DMA_CONTROL:Trying to read undefined DMA port c
19  42494523: DMA_CONTROL:Trying to read undefined DMA port c
20  42494524: CPU:Illegal/Unhandled opcode 0F00
21  42494525: DMA_CONTROL:Trying to read undefined DMA port d
22  42494526: DMA_CONTROL:Trying to read undefined DMA port d
23  42494527: CPU:Illegal/Unhandled opcode 0F00
24  42494528: DMA_CONTROL:Trying to read undefined DMA port e
25  42494529: DMA_CONTROL:Trying to read undefined DMA port e
26  42494530: CPU:Illegal/Unhandled opcode 0F00
27  42494531: DMA_CONTROL:Trying to read undefined DMA port f
28  42494532: DMA_CONTROL:Trying to read undefined DMA port f
29  42494533: CPU:Illegal/Unhandled opcode 0F00
30  42494534: IO:Read from port 0010
31  42494536: CPU:Illegal/Unhandled opcode 0F00
32  42494537: IO:Read from port 0011
33  42494539: CPU:Illegal/Unhandled opcode 0F00
34  42494540: IO:Read from port 0012
35  42494542: CPU:Illegal/Unhandled opcode 0F00
36  42494543: IO:Read from port 0013
37  42494545: CPU:Illegal/Unhandled opcode 0F00
38  42494546: IO:Read from port 0014
39  42494548: CPU:Illegal/Unhandled opcode 0F00
40  42494549: IO:Read from port 0015
41  42494551: CPU:Illegal/Unhandled opcode 0F00
42  42494552: IO:Read from port 0016
43  42494554: CPU:Illegal/Unhandled opcode 0F00
44  42494555: IO:Read from port 0017
45  42494557: CPU:Illegal/Unhandled opcode 0F00
46  42494558: IO:Read from port 0018
47  42494560: CPU:Illegal/Unhandled opcode 0F00
48  42494561: IO:Read from port 0019
49  42494563: CPU:Illegal/Unhandled opcode 0F00
50  42494564: IO:Read from port 001A
51  42494566: CPU:Illegal/Unhandled opcode 0F00
52  42494567: IO:Read from port 001B
53  42494569: CPU:Illegal/Unhandled opcode 0F00
54  42494570: IO:Read from port 001C

Tried it again and I got the following, and nothing else. The only stuff the debugger showed me was the following:

1  33452793: CPU:Illegal/Unhandled opcode 63

I even got DOSBox to crash on me without any useful debug information. And this one is new to me, because I haven't got this one in my tests:

1  27267707: CPU:Illegal/Unhandled opcode 63
2Illegal read from 2b742566, CS:IP     494d:    206e
3Illegal read from 2b742567, CS:IP     494d:    206e
4  27267712: CPU:CPU:GRP5:Illegal opcode 0xff
5  27267713: CPU:CPU:GRP5:Illegal Call  7
6  27267713: CPU:Illegal/Unhandled opcode FFFF
7Illegal read from 4317a366, CS:IP        0:4317a366
8DYNX86:Can't run code in this page!
9Illegal read from 4317a366, CS:IP        0:4317a366
10Illegal read from 4317a367, CS:IP        0:4317a366
11Illegal read from 4317a368, CS:IP        0:4317a368
12Illegal read from 4317a369, CS:IP        0:4317a368
13Illegal read from 4317a36a, CS:IP        0:4317a36a
14Illegal read from 4317a36b, CS:IP        0:4317a36a
15Illegal read from 4317a36c, CS:IP        0:4317a36c
16Illegal read from 4317a36d, CS:IP        0:4317a36c
17Illegal read from 4317a36e, CS:IP        0:4317a36e
18Illegal read from 4317a36f, CS:IP        0:4317a36e
19Illegal read from 4317a370, CS:IP        0:4317a370
20Illegal read from 4317a371, CS:IP        0:4317a370
21Illegal read from 4317a372, CS:IP        0:4317a372
22Illegal read from 4317a373, CS:IP        0:4317a372
23Illegal read from 4317a374, CS:IP        0:4317a374
24Illegal read from 4317a375, CS:IP        0:4317a374
25Illegal read from 4317a376, CS:IP        0:4317a376
26Illegal read from 4317a377, CS:IP        0:4317a376

Tried loadfix, setting the core to dynamic and normal. Also fixed cycles doesn't do anything really. So I'm not entirely sure if this is a DOSBox bug or simply this is how the installer was designed. The game works as I said before, and thought I might mention it just in case it doesn't gets fixed. I could try messing in the config file but I'm sure it doesn't have any effect on this. Feel free to ask if you have any more questions!

Last edited by P4R4D0X on 2013-07-02, 16:20. Edited 1 time in total.

Reply 1 of 3, by Gamecollector

Posted on 2013-05-14, 19:12

Gamecollector Offline

Rank Oldbie

Rank: Oldbie
Posts: 1413
Joined: 2010-10-06, 22:17
Location: RU

This game isn't the only one affected. Another examples are X-Car: Experimental Racing and Extreme Assault.

Asus P4P800 SE/Pentium4 3.2E/2 Gb DDR400B,
Radeon HD3850 Agp (Sapphire), Catalyst 14.4 (XpProSp3).
Voodoo2 12 MB SLI, Win2k drivers 1.02.00 (XpProSp3).

Reply 2 of 3, by ripsaw8080

Posted on 2013-05-15, 10:06

ripsaw8080 Offline

Rank DOSBox Author

Rank: DOSBox Author
Posts: 5094
Joined: 2006-04-25, 23:24

The problem in these cases may be similar to the one described here. You can verify by looking for the string "CauseWay DOS Extender" in the SETSOUND.EXE file. When the CauseWay extender is used by a child process then loading JEMM (or EMM386) as mentioned in the linked thread could be a solution. However, running the program directly (not as a child process) is the simplest solution.

Reply 3 of 3, by P4R4D0X

Posted on 2013-05-15, 11:36

P4R4D0X Offline

Rank Member

Rank: Member
Posts: 100
Joined: 2012-10-06, 14:46

I've looked up SETSOUND.EXE and you are right. Found references for the extender. CauseWay DOS Extender v3.14 Copyright 1992-96 Michael Devore. All rights reserved. Tried to solution mentioned in the other topic, but it looks like it just crashed DOSBox entirely. Turned off XMS, EMS and UMB in the configuration file, and I tried it with JEMMEX FRAME=E000 LOAD and JEMMEX LOAD but still the same results.

Also here's an interesting fact. X-Car: Experimental Racing uses the same DOS extender and it doesn't have this issue. The game installs just fine, and when I choose YES to configure the sound it launches SETUP.EXE without freezing. The only difference is that it uses a slightly newer version of CauseWay. CauseWay DOS Extender v3.17 Copyright 1992-96 Michael Devore. All rights reserved.

Unfortunately I don't have Extreme Assault but I can show that X-Car: Experimental Racing works just fine. You can view the screen recording here: http://www.screencast.com/t/BovEgUdp5a

The good news is that we know what causes the issue. Maybe it's a buggy version of CauseWay DOS Extender, and that causes this behaviour. I'm pretty sure these games were tested before put them on store shelves.

Go to top of page Go to top of page

Back to DOSBox Games/Apps