Tux

I took the time out of curiosity to search when they did that change : in mame 177 precisely, it was in 2016! It doesn't come for this rom alone of course, there are quite a lot of changes in the cps2 roms, and they can't be applied automatically because there are some differences in the way raine and mame load these roms. Which means that I'd have to manually test each change, plus it would make the new roms incompatible with the version for raine on internet archive ! Well if you manage to find at least 1 useful change in all these changes, I'll consider it, otherwise just forget it ! The ideal would probably be to be able to load roms from some external definitions files so they can adapt to all these crazy changes for those who want to follow, but it would require quite some changes... ! Plus it would probably create some other problems in some drivers which modify the rom and expect some precise bytes at some precise places (which is not the case of the cps2 driver thankfully !).

D : I remember now, it's just that the key sequence you type is the sequence which is searched, so if you type twice D, it means you are looking for DD, which can be dangerous in case you have a game whose label contains DD, like top hunter, the neogeo game... ! If you are not sure, it's better to enable the "return mandatory" option. I didn't do that to be standard, just to find a way to be as fast as possible with the keyboard, it works well. And for the mame update : it's a never ending headache, I stopped following their nonsense years ago, all this should have been done differently normally (preserving the old rom sets and just adding the new ones with an increasing number when they are found), it would preserve compatibility with all versions, and usually the most recent version hasn't got very important changes. So well I accept patches to update the romset if you feel like it, if not, you'll have to be patient because I really hate doing this stuff !

1 - I was tempted to say it's not really a bug, it's super minor and you are the only one using this at least from what's reported on the forum, but the fix is trivial, just reset exit_options when opening the game options, so I did it. 2 - gui options / return mandatory C - yeah if it can't find the key you just pressed in the following games in the list, then is starts to look for it anywhere in the game title, that's for when you don't remember the whole title ! This thing is made to be used very fast, and I can confirm it does its job well ! D - not sure, well just press return in this case, I won't bother to look why it didn't select it as it should have done in this particular case.

No problem, it's very easy to reproduce. It comes from the very special nature of the console, contrary to other dialogs in the interface, it always exists, but since the interface has a parent system to be able to draw the background, it can create problems when the parent of the console disappears. Here because of the error, it takes one of the temporary messageboxes as parent and so the 1st time you try to display it, it just crashes because the parent has disappeared ! Yeah it's normal, this part of the gui is a hack, because I wanted the console to always exist, which is not the normal way of working for this gui. So there is a workaround, not too complex, maintain a list of active dialogs to be able to check if the parent is still active when drawing a dialog. If it's not, just remove the parent that's all. So patch very short and efficient. Pushed to git.

xp last update was in 2010 or 2011, so it doesn't make much sense to loose too much time on it. I would have kept compatibility but virtualbox removed direct3d support for xp in 6.1 because of a big security hole in their driver, I would have preferred that they would simply add a big red button to click to allow users to install this despite the security hole, but they just removed direct3d support, so it's impossible for me to run any version of raine in xp in virtualbox now, so too many people want xp to disappear. On my end I quite liked some custom xp editions like tinyxp : small, fast and efficient, but oh well, I guess it's too outdated now. And it's not hardware obsolescence, you still do what you want with your hardware, you can install something else on it, it's software obsolescence only here. And the next victim will be win7, but maybe I won't have to deal with that... !

Well you can always test the last sdl1 version to check, sdl2 started in 0.92, so the last sdl1 must be in 0.91.15. Also if you saw the post in the other thread, we became xp incompatible with 0.97.2, so it's probably because of the new function to detect the soundcard. It doesn't really matter anyway, xp is ancient now, and you are bound to hit an incompatibility like that if you keep adding new functions. Also something you probably didn't think about, but if you set Autodetect as default, then you will never see which card is selected, it probably doesn't matter much anyway as long as it can be heard, but if you want to have the detect and store result as before, the only way is not to have this autodetect as default. (or modify the interface to show which card was detected when Autodetect is selected, but I prefer to keep things as simple as possible). And for the unexpected return of the black border : I had actually tested this in windows, but apparently this function doesn't return the same thing when you call it in windowed mode and fullscreen ! So it got me, because I didn't think about saving the config and run again. And it doesn't make much sense, it's supposed to be state-less normally... ! Anyway !

1) autodetect as default : we used the other way for years and you are the 1st to have a problem with that, I think we can keep the old default for now, I prefer to see precisely my soundcard name when I go to options. 2) your haunting black border : well not for me in linux. Maybe it's windows only... I am terribly tempted to simply stop to support windows, what a marvelous idea it would be ! I might try that in windows later, but for now in linux : 1) removed my config file, started raine, went to fullscreen loaded dino, took a screenshot of the title screen, then quit 2) run raine again in the same config, loaded dino, took the same screenshot, got exactly the same picture, end of the test for now. ... and same result in windows, same picture in both case (compared the files they are identical). got it, I hadn't the latest binary in windows, it's still the same old problem because I changed the way to get the screen coordinates, in windows we get the height of an invisible windows title bar added, not in linux. 1 line fix, a function name instead of another, but it's really annoying. At least the site is fixed, back with some disk space, you can get the ultimate test binary there : https://raine.1emulation.com/archive/tux/raine.7z

It's a miracle we can still post to the forum with a full disk, maybe the database uses another disk ? Anyway here is a mega.nz link for now : https://mega.nz/file/OYVAXI4b#uMADM9P6tyzFjRN3kUj90s1spQKI-B188WSJmvIBYDE

Oh, ok I surrender, I added an Autodetect choice for the soundcard in the gui, and I fixed the detection of the sample rate which was linked to the sound driver instead of the soundcard... ! You won't have a test binary for now because after the forum, it seems the ftp is broken for now, I can't send raine.7z ! (deleted the file to avoid any mistake). It's still a rare case in my opinion, but it's quite interesting to see how it can be done without having something too big. Since I had to fix the sample rate detection too it's a little longer than what I anticipated but it's still ok, and maybe someone else would use that ! Notice that the behavior is the same as before : if you don't choose "Autodetect" explicitely and you have no config file, then it will detect the soundcard only once, there's no reason to detect it all the time except on a crazy laptop changing its output device all the time ! Difference from before : now if you change the soundcard in sound options and the sound card driver has a preferred sample rate, you'll see this sample rate selected in the options in real time. Not all drivers have a preferred sample rate, if there is none the frequency is not changed. By the way the error on the server is because of a full disk !

Centering the window : of course raine keeps as many coordinates as it can, it's since we added all these windows statuses which created so many problems ! So it knows where to position precisely a window when exiting from fullscreen to return to its previous state, but if the physical screen changed and now the resolution is not the same anymore, then it will mess things up. There's not much which can be done about it, it's obliged to reduce the size to stay in the screen, but then should the position be changed too and how ? For now it isn't touched, it's the safest way, it would really become crazy to try to adjust position when the size has changed too. The black screen in windowed mode : yeah my fault, I didn't get the right values for the desktop resolution, now I ask the desktop resolution for display 0, hoping we will never handle more than 1 physical display because I don't plan to use more than 1 here. autodetect sound all the time : yeah but it would force to have a special value which says "detect the soundcard but don't store the result, just stay in autodetect", so it's a little tricky, and not necessary in most setups, your setup when plugging a new dispaly changes the soundcard priority is quite original. And always detecting the soundcard is not a good idea neither in the case where you run without a desktop, which I do on the mini computer, it has a bare environment, no desktop, and in this case it can get some rather crazy value for the detected soundcard. Now I admit that if I was to use regularly raine on that machine, I would put a window manager, at least for fullscreen, here it's bothersome... ! Anyway since it takes you only a few seconds to adjust manually, it's the easiest solution for now.

No I think it's enough for the sound. It works well enough for me. There was an autodetect for sound in the old dos days for those who didn't know which sound card they had, but the time was very different ! Since then it never came back, and you can easily do without it even now, if you forget and find you have no sound, you can restore your sound by a quick visit to sound options, so it's not worth the trouble adding an explicit autodetect choice in my point of view. For the 1080p -> 1366x768 not sure what happens, I might do some tests later. edit : after testing, it's minor, it's just about the placement of the window, not sure there is something to do about it, it's after resizing the screen so that it fits in the new resolution, so no wonder it can change the position while doing so. And it can be fixed manually without too much trouble, or just stay in fullscreen, so really minor. Cool, I finally see the end of it ! For the config not updated if you just run and quit, normal, it does nothing related to the sound in this case, you have to either load a game or go to sound options.

Nope, sound_card becomes a string value in the config file for sdl versions from now on, the old config file is converted on the fly so you don't have to edit it manually. Actually sdl2 accepts only a soundcard name when opening a soundcard, not an id, so it's easier this way. While testing I stumbled upon the case where you get a strange soundcard name with trailing spaces, in this case the trailing spaces are removed when reading from the config file which added another case to fix... ! Anyway it should work in all cases now, hopefully ! Test your thing... same link.

For the smaller screen : yeah it can be done, I thought about it after posting this binary, easily done. For replacing 1 soundcard by another one : not convenient for now, it obliges to change a number by a string as a setting, and for now I prefer to avoid it, so I think it's going to be my limit, you'll have to live with it ! edit : actually it might be possible to do something for the soundcard too, it's not convenient because it breaks compatibility with the dos version, but it shouldn't be too complex to do, I might have a closer look later.

Ok, I'll take a look later, but there's no need to make a video all the time, just saying 1 load a game while being in fullscreen, the game starts normally while in the gui 2 go fullscreen -> the screen becomes blank It's shorter, takes less time, and is more efficient for everyone. I have tested this too fast, seeing that the gui seemed ok in fullscreen I assumed it was a windowed problem only. Later, then... edit : well sorry for my mistakes, I was half awaken when I did that and it shows, I went way too fast especially for the video resizing part. For the sound I didn't think just opening the sound options would make such a mess in such a case ! Anyway it's fixed again, you can have your test which was indeed useful here : http://raine.1emulation.com/archive/tux/raine.7z

Oh well you can always test this binary, since normally it can now work around the issue of soundcard not present you shouldn't be able to reproduce this error with it. https://raine.1emulation.com/archive/tux/raine.7z

No idea how it was broken so I can't do anything about it, sorry ! I would love to have someone maintain the windows version, it would be a lot less troubles for me ! Actually there are very few patches between 0.97.1 and 0.97.2 of course since it's mainly about the sound problem alone, raine does nothing fancy in this version, just calling sdl2 functions which were not called before, so I guess your incompatibility comes from there. But as explained before there is nothing much to do about it after a certain point, Microsoft does this willingly, they do nothing to maintain their old versions, not even security patches, and keep on adding new kernel functions to the new versions which are then used by some libraries. After a while the new functions become unavoidable and you have an incompatibility.

After some thinking, it's not so hard to add a small test for the video info to keep the window within the screen boundaries in case the physical screen has changed since the config was recorded, so I did just that. And in case the recorded soundcard is not available to just force a re-detection of it. 2 small workarounds for people who change their config all the time on their laptops while still keeping things easy, it should work... But I won't track the z80 error, yeah it can report an error like that if sound config is messed up when booting the game, even if I can't seem able to reproduce it for now no matter what.

I won't try to recreate a rare bug, it's rare so just avoid it that's all. There are known issues in sound like changing the sample rate in a game which use fm music after the game has started will produce bad sound, the known workaround is just to quit when you change the sample rate. Yeah I know it's not super ideal, now if someone wants to send patches to improve all this, I'll accept them ! It's assumed people can setup their sound once and then keep the settings for normal play. A program which works in all conditions is a crazy thing, that's something you learn quickly when you learn how to program, even if you try to do it with some sample code it can quickly become crazy. Now for some safe environments where it's a necessity, people try to keep programs small to avoid that things become too crazy. For raine it's already very big, you have to be a minimum reasonable about what to do in this case, it's already working as well as possible with some pitfalls which can be easily avoided.

Not for me, and really I get more and more tired of this... !

Of course it was never thought to be used on a machine which changes its setup like that, it's supposed to be stable. Well you can always install in 2 directories, 1 for your tv and the other one for the laptop, that's clearly the fastest solution because raine has worked like that for something like 20 years so I don't think I'll change that now, and I am not even sure how I would do it anyway. For your sound option which disappears after you remove the tv, well same thing I guess, delete your config file if you want to keep just 1 install to allow it to reset its settings for the new setup. That's an idea for later eventually to allow it to detect such radical configuration changes, but I won't make a hotfix for that.

For the soundcard detection and handling when there is more than 1 soundcard on the system ! All this went haywire because sdl2 SDL_OpenAudioDevice never returns 1 for compatibility with sdl1... !!! And also the fact that I never had the opportunity to test on a proper system with 2 soundcards. So if you have only 1 soundcard and everything works fine, no need to update this time ! http://raine.1emulation.com/download/latest.html

This part alone almost made me crazy. There is a compatibility hack in sdl2 to stay compatible with sdl1 so that it never returns the device id 1 on success when opening an audio device ! So it means you must ignore the returned device id (if using something else than autodetect). Crazy stuff... I'll fix that ASAP... It's changed in sdl3, it correctly returns the logical device id which was opened, I guess sdl3 is soon now. I would have spotted this earlier if I hadn't changed my installation here, no 2nd audio card to test... oh well... !!! Ok, fixed. The autodetection is totally different now, it can't rely on opening the device as it did before, so it might work better for you now. Tested in many configurations, it should be ok everywhere. For the neocd bios, yes it looks for neocd.zip in the raine directory, it can't look anywhere else since there are no roms directory in neocd. It's always been like that.

Impressive !

No idea, but as you said, it's not important as long as the setting is properly saved and restored since it takes just a few seconds to setup that. Tested with the latest version, and it is, so that's all that matters for now, if someone wants to investigate further, he's welcome to ! for your change, I changed the way the soundcard is 1st selected in 0.97, I let sdl2 choose instead of always selecting the 1st one, but I don't know how it chooses ! It was discussed in another thread, started by mer-curious too. Notice that if you preserve your config file and always unpack a new version in the same dir, you won't notice this change.

Non issue, already talked about it. And no sorry, already said but I can't detect your desktop sound setting (and really don't care). I tested that quickly in the mini with its 2 soundcards and selecting the 2nd soundcard was saved when quiting normally using the quit command. You can check it in the config file in [Sound] section, sound_card is just a number, 1 for the 1st sound card, 2 for the 2nd, and so on. edit : and in windows too of course, I plugged this usb soundcard which became the 1st soundcard in windows for god know which reason but anyway at this point I could change or keep the soundcard in raine and it was saved all the time. End of the problem for me.