Thanks, now ISO Hom & M II GOG is mounted correctly. The console reports that OGG audio tracks are loading. Unfortunately, I still have silence in the speakers :( I tried settings with Soundbaster 100% Compatible and Gravis Ultrasound.
CDROM: Loaded homm2_01.ogg [44100 Hz, 2-channel, 1.9 minutes]
CDROM: Loaded homm2_02.ogg [44100 Hz, 2-channel, 2.0 minutes]
CDROM: Loaded homm2_03.ogg [44100 Hz, 2-channel, 1.8 minutes]
CDROM: Loaded homm2_04.ogg [44100 Hz, 2-channel, 2.8 minutes]
CDROM: Loaded homm2_05.ogg [44100 Hz, 2-channel, 2.6 minutes]
CDROM: Loaded homm2_06.ogg [44100 Hz, 2-channel, 2.6 minutes]
CDROM: Loaded homm2_07.ogg [44100 Hz, 2-channel, 2.4 minutes]
CDROM: Loaded homm2_08.ogg [44100 Hz, 2-channel, 2.5 minutes]
CDROM: Loaded homm2_09.ogg [44100 Hz, 2-channel, 2.9 minutes]
CDROM: Loaded homm2_10.ogg [44100 Hz, 2-channel, 2.0 minutes]
CDROM: Loaded homm2_11.ogg [44100 Hz, 2-channel, 2.1 minutes]
CDROM: Loaded homm2_12.ogg [44100 Hz, 2-channel, 1.9 minutes]
CDROM: Loaded homm2_13.ogg [44100 Hz, 2-channel, 2.1 minutes]
CDROM: Loaded homm2_14.ogg [44100 Hz, 2-channel, 2.5 minutes]
CDROM: Loaded homm2_15.ogg [44100 Hz, 2-channel, 1.8 minutes]
CDROM: Loaded homm2_16.ogg [44100 Hz, 2-channel, 2.0 minutes]
CDROM: Loaded homm2_17.ogg [44100 Hz, 2-channel, 2.2 minutes]
CDROM: Loaded homm2_18.ogg [44100 Hz, 2-channel, 0.4 minutes]
CDROM: Loaded homm2_19.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_20.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_21.ogg [44100 Hz, 2-channel, 1.0 minutes]
CDROM: Loaded homm2_22.ogg [44100 Hz, 2-channel, 0.2 minutes]
CDROM: Loaded homm2_23.ogg [44100 Hz, 2-channel, 0.9 minutes]
CDROM: Loaded homm2_24.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_25.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_26.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_27.ogg [44100 Hz, 2-channel, 1.1 minutes]
CDROM: Loaded homm2_28.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_29.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_30.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_31.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_32.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_33.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_34.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_35.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_36.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_37.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_38.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_39.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_40.ogg [44100 Hz, 2-channel, 0.1 minutes]
CDROM: Loaded homm2_41.ogg [44100 Hz, 2-channel, 1.3 minutes]
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
CDROM: GetTrack at sector 4294967149 is outside the playable range
Hard to say if it's faster or not compared to r2, PCPBench give different results, sometimes a bit slower, sometimes a bit faster .. i think i will bench a game .. doom can be an interesting one
Aniway are you able to turn off the screenblanker of OS4 when dosbox running ?
Hard to say if it's faster or not compared to r2, PCPBench give different results, sometimes a bit slower, sometimes a bit faster .. i think i will bench a game .. doom can be an interesting one
Benchs will say nothing probabaly, they too vary all the times. But imho in case with -O3 dosbox will not gain much, just if it not worse, then it can be keept
Quote:
Aniway are you able to turn off the screenblanker of OS4 when dosbox running ?
I don't use screenblankers, so can't say. But it will be strange if way how screenblankers works somehow have connection with other apps. Probabaly you can't turn them off with any other app running then ?
But it will be strange if way how screenblankers works somehow have connection with other apps. Probabaly you can't turn them off with any other app running then ?
As for the system's screenblanker, it should be enough to register DOSBox with the Application Library and then set the APPATTR_NeedsGameMode attribute to TRUE whenever a game is started. The screenblanker engine will receive an APPLIBMT_GameModeEntered message, upon which it should stop invoking the blanker. (At least that's what the documentation says. Never tested it myself, as I don't use the screenblanker engine.)
EDIT: Sorry, I was wrong, the attribute that controls blanker activity is APPATTR_AllowsBlanker. Although APPATTR_NeedsGameMode can also be useful; see my post below.
I don't use screenblankers, so can't say. But it will be strange if way how screenblankers works somehow have connection with other apps. Probabaly you can't turn them off with any other app running then ?
Don't know exactly how it works, but for what i've understand an application need to be registered individually in order to disable the blanker engine, Huno do somethings similar with his games/ports and it works.
Pratically when a software is running, the blanker is somekind "freezed" in background letting users to mantain their application (with the content visible) always "opened" even without any user input Then the internal timer of the blanler will resume back as soon as you close the game window, so yes it's possible in OS4 even without the need disable entirely the blanker engine
EDIT: Ah it seems Trixie explain in detail how it works
As for the system's screenblanker, it should be enough to register DOSBox with the Application Library and then set the APPATTR_NeedsGameMode attribute to TRUE whenever a game is started. The screenblanker engine will receive an APPLIBMT_GameModeEntered message, upon which it should stop invoking the blanker. (At least that's what the documentation says. Never tested it myself, as I don't use the screenblanker engine.)
Probably not necessary "when game is started", but when just dosbox started ? As in terms of emualtion when we start dosbox "game is started".
Is it something which i can just copy+paste at begining of main() , and at the end when exit happens ? Nothing else need it ? I mean, can you share ready to paste code , so if something will go there wrong i will point by finger and saying "dunno, its Trixie's code" ?:)
Probably not necessary "when game is started", but when just dosbox started ? As in terms of emualtion when we start dosbox "game is started".
Yes, that'd be perfectly fine I guess. Just register DOSBox with the Application Library (see the documentation I've written for the Dev Wiki), then call
This will tell applications monitoring the APPLIBMT_GameModeEntered and APPLIBMT_GameModeLeft messages (such as audio players) that they can freely make noise again. I don't think you need to set APPATTR_AllowsBlanker to TRUE, as the app is about to finish anyway. Finally, you'll call IApplication->UnregisterApplication(appID, NULL) before you quit.
SDL_Quit_Wrapper();//Let's hope sdl will quit as well when it catches an exception
return 0;
}
So, DOSBox now shows fine in the Exchanger, all good, when i quit from it also disappear, but then, no button of Exchanger works. Not that it big deal or related to issue we deal with, but as i on it, maybe it worth to make it all good..
For example, buttons like "show user interface" and "hide user interface" do not active , but only one button "X" active, which should close app, but it do nothing. Probabaly i should do some more stuff there ? (re-reading your doc in meantime)
buttons like "show user interface" and "hide user interface" do not active , but only one button "X" active, which should close app, but it do nothing. Probably i should do some more stuff there ? (re-reading your doc in meantime)
Yes, in order to allow application control from program managers such as Exchanger, one has to implement the minimum Application Library support as described in this section of the wiki doc. Basically, you'd have to add a signal to the program's event loop to Wait() for the application port messages, and react upon them (i.e. quit when you receive APPLIBMT_Quit, etc.) But as DOSBox uses SDL, I'm not sure how the event loop is implemented, how much work that would involve, or if it is worth the effort at all.
@trixie Thematic probably was under impression that its commodities now as we see in in Exchanger, but its not commoditie but just application, which Exchanger can see.
@mufa Still can't reproduce your issue :(
I check an my settings are:
Music Preference - CD Audio MIDI Driver - Creative Labs Sound Blaster or 100% compatible Digital Driver - Creative Labs Sound Blaser 16 or AWE32
But not sure if it anyhow related..
Then, that what i do:
imgmount d homm3.ins -t iso heroes2.exe
Can you recheck that it the same for you ? And if bug still will be reproduced, can you also post your full dosbox config with which you test it.
@mufa Tried with your config of DOSBox, with your .ins, with your heroes.cfg, and it still works, damn :( will do more tests. For it always reproducable ? 100% the same result all the time ? And you 100% use exactly that archive:
Roman, is there a MIDI support in this release ? And is so, how can i enabled it ? ... i mantain "ultradir=instruments" and if i understand correctly it should work with Doom .. but i have no sound at all in game
The PLAYMIDI program for Ultrasound just works across the different emulators (Dosbox that is). As I understand it, it's the actual old player, not an emulator edition.
@All Can anybody test on x5000 (exactly on x5000) , the old version of DosBOx (which inside of osdepots's archive in directory "old"). It's SDL1 one, and for me, once i tried to use it, it always lockup and freezes. Want to understand if it problems with my hardware/setup, or common issue.