VOGONS


Reply 40 of 49, by theelf

User metadata
Rank Oldbie
Rank
Oldbie
ripsaw8080 wrote on 2024-07-10, 15:58:
The attached loader program modifies the game in memory to have Roland music with SB speech/sfx. There are no Roland sfx when us […]
Show full quote

The attached loader program modifies the game in memory to have Roland music with SB speech/sfx. There are no Roland sfx when using SB speech/sfx because it is one or the other with those drivers; however, I think it works well with the MT-32 because there is less need for the extra sounds of the CM-series.

The attachment skydrv.zip is no longer available

The program has a no-CD feature that allows the game to be run entirely from HDD, and it's probably easiest to just put it where the config and save files are stored.

AFAIK, all CD-ROM releases are supported -- version 0.0368 (Europe, UK, Germany) and version 0.0372 (US, Taiwan) -- the freeware release is version 0.0368

Note that speech + text can be selected from the in-game options (F5 key)

Example running from an HDD directory with all files from the CD copied to it:
SKYDRV CFG=.

Example running from the CD:
D:
C:\SKY\SKYDRV CFG=C:\SKY

Keep in mind that the loader program executes SKY.EXE in the current directory when trying other arrangements. The CFG= parameter specifies the directory where the config file and save files go -- \STEELSKY is the default if not specified.

Update: The loader program now uses the hardware configuration rather than always relying on the game's auto-detection. The "Port Addresses" in INSTALL.EXE all default to auto-detection, so if SB sound is not working on your system then select port, IRQ, DMA and "Save Setup".

Hello, I know this is an old post, but I want to run your patch on my 486. I have an AWE64 + MT-32. When I run the game normally, I get music and FX through the MT-32 without problems, or music + FX + voices through the AWE64. But with your patch I can get sound FX with SB, but no music with MT-32

One thing I notice is that when i load SKY with your patch, my MT32 get crazy, the screen show strange and random things, and i need to turn off/on to have sound again in another game. Funny thing i tested with a MT32-Pi and same thing happen! no sound in another game only when turn off PC, and the screen show random stuff too

Any ideas?

I get this error in the game, i dont know is relevant? maybe not

It’s in Spanish: the first screenshot says MISSING TEXT OR GRAPHICS, and in the second screenshot it says BUY A HARD DRIVE, NOW.

The attachment IMG_20260325_221608.jpg is no longer available
The attachment IMG_20260325_221613.jpg is no longer available

Thanks!

Reply 41 of 49, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Hmm, could be a version of the game that is not supported by the patch. Make sure you're using a CD-ROM version of the game, not a floppy version, and if all else fails then use the freeware release which should work.

Reply 42 of 49, by Law212

User metadata
Rank Member
Rank
Member
Dimitris1980 wrote on 2024-07-05, 09:57:

I would really like to play the cd version with speech and Roland for the music. This game has extra sound effects with Roland CM32L/CM64/LAPC-I . For instance there is a scene in this lady's apartment where the dog barks. The barking can be heard with Roland CM32L/CM64/LAPC-I but not with the Roland MT-32.

REMOVED. It has also a version of Beneath a Steel Sky with enhaced music and it is really great. I think it is written with Yamaha.

Personally I am lot more into real equipment than emulators.

Real hardware is the way to go. This thread makes me want to play this game. I will have to pull it out of storage and install it.

Reply 43 of 49, by theelf

User metadata
Rank Oldbie
Rank
Oldbie
ripsaw8080 wrote on 2026-03-26, 01:05:

Hmm, could be a version of the game that is not supported by the patch. Make sure you're using a CD-ROM version of the game, not a floppy version, and if all else fails then use the freeware release which should work.

Hi! thabnks for reply, i realize of something, if I connect the MT-32 to the sound card, your patch work fine

The problem is not game or MT-32, the problem is the PicoGUS, because i use picogus to connect MT-32. This is the only icompatibility i found so far of picogus. SKY+Picogus+MT32 OK, your patch+SB16+MT32 OK, your patch+Picogus+MT32 FAIL

Reply 44 of 49, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie
theelf wrote on Yesterday, 23:31:

The problem is not game or MT-32, the problem is the PicoGUS, because i use picogus to connect MT-32. This is the only icompatibility i found so far of picogus. SKY+Picogus+MT32 OK, your patch+SB16+MT32 OK, your patch+Picogus+MT32 FAIL

What port/address is the SB16 MPU401 and the PicoGUS MPU401? Are they both on port 330?

Last edited by NeoG_ on 2026-03-28, 00:57. Edited 1 time in total.

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 45 of 49, by theelf

User metadata
Rank Oldbie
Rank
Oldbie
NeoG_ wrote on Today, 00:32:
theelf wrote on Yesterday, 23:31:

The problem is not game or MT-32, the problem is the PicoGUS, because i use picogus to connect MT-32. This is the only icompatibility i found so far of picogus. SKY+Picogus+MT32 OK, your patch+SB16+MT32 OK, your patch+Picogus+MT32 FAIL

What port/address is the SB16 PU401 and the PicoGUS MPU401? Are they both on port 330?

No, SB16 300, Picogus 330

Reply 46 of 49, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie
theelf wrote on Today, 00:54:

No, SB16 300, Picogus 330

The other explaination is that the game is sticking to port 300, perhaps because P300 is in the blaster variable, or some detection routine starts at lower ports and goes upwards, detecting the MPU401 at 300 first

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 47 of 49, by theelf

User metadata
Rank Oldbie
Rank
Oldbie
NeoG_ wrote on Today, 00:58:
theelf wrote on Today, 00:54:

No, SB16 300, Picogus 330

The other explaination is that the game is sticking to port 300, perhaps because P300 is in the blaster variable, or some detection routine starts at lower ports and goes upwards, detecting the MPU401 at 300 first

No, i do something like this when i have SB16+PicoGUS

Set blaster=a220 i5 d1 P300
Unisound
Set blaster=a220 i5 d1 P330

Set blaster is always 330, i dont care about SB16 midi port, i use picogus+wavetable only for mpu. To test real MT32 i just remove picogus card and set P330 before unisound

Reply 48 of 49, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie
theelf wrote on Today, 01:00:
Set blaster=a220 i5 d1 P300 Unisound Set blaster=a220 i5 d1 P330 […]
Show full quote

Set blaster=a220 i5 d1 P300
Unisound
Set blaster=a220 i5 d1 P330

Set blaster is always 330, i dont care about SB16 midi port, i use picogus+wavetable only for mpu. To test real MT32 i just remove picogus card and set P330 before unisound

I would test by temporarily changing the picogus to 300 and SB16 to 330 to make sure the issue doesn't follow the port number before concluding a compatibility issue

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 49 of 49, by theelf

User metadata
Rank Oldbie
Rank
Oldbie
NeoG_ wrote on Today, 01:04:
theelf wrote on Today, 01:00:
Set blaster=a220 i5 d1 P300 Unisound Set blaster=a220 i5 d1 P330 […]
Show full quote

Set blaster=a220 i5 d1 P300
Unisound
Set blaster=a220 i5 d1 P330

Set blaster is always 330, i dont care about SB16 midi port, i use picogus+wavetable only for mpu. To test real MT32 i just remove picogus card and set P330 before unisound

I would test by temporarily changing the picogus to 300 and SB16 to 330 to make sure the issue doesn't follow the port number before concluding a compatibility issue

Yes, i already did this, use different sound cards just in case, AWE64, SB16, CMI8330, ESS, different picogus firmware, old version, new ones, change sound card IRQ 5-7, change wavetable to GM and MT-32 modes, set picogus as intelligent MPU, and i dont remember whats else test already