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

×
avatar
Themken: Seeing how DB 0.74 is unstable on Windows 10 for some people, me included, I am sure GOG will move over to 0.75 after it has been around for while.
config of system and of DOSBox please...
avatar
FulVal: config of system and of DOSBox please...
Seeing as we are talking about my mum's computer here, I have only used GOG's standard settings and not bothered tweaking anything except increasing cycles=3000 to cycles=5000 in Master of Orion. It is not terribly unstable, just once every 100h instead of once every 3000h. It might be the fault of the anti-virus or something too.

Windows 10 home 64bit with the spring update on a ten years old laptop.
Post edited August 30, 2018 by Themken
avatar
phaolo: DOSbox 0.75 !?
Is this real life? :P

I wonder what GOG will do about it though.. probably they won't update it in the installers, sadly.
Unless something is broken for a particular game, I don't think it's necessary to update all the games to the latest version.


On the other hand, I'm glad this project is still alive. DOS was a big part of my childhood, most of my school mates had Win95/98 and PSX while I was still feeding commands to that blinking cursor.

Kudos for the news :-)
Dosbox isn't dead ! \o/
Great news !
Wow. That's pretty awesome to see!
avatar
Pouyou-pouyou: Dosbox isn't dead !
That's what they all think.
avatar
Engerek01: I thought DOSBox development had stopped after 0.74. That's good news :)
Dosbox has been always in developpement with alldays nighty builds. Only stable release had been stopped.

http://www.emucr.com/search/label/DOSBox
Post edited August 31, 2018 by stephane910
avatar
Engerek01: I thought DOSBox development had stopped after 0.74. That's good news :)
avatar
stephane910: Dosbox has been always in developpement with alldays nighty builds. Only stable release had been stopped.

http://www.emucr.com/search/label/DOSBox
Nope.
avatar
stephane910: Dosbox has been always in developpement with alldays nighty builds. Only stable release had been stopped.

http://www.emucr.com/search/label/DOSBox
avatar
FulVal: Nope.
It was although the strict reality. Now, it has changed
Post edited August 31, 2018 by stephane910
By the garlic of Warioland, this is a pleasant surprise!
Post edited August 31, 2018 by Darvond
avatar
Lucian_Galca: Any chance for vsync to be added?
DOS games didn't support vsync since they were programmed for superior monitors ;) the performance was lower and further complication is the multiple Operating Systems that DOSBox supports. There is an unofficial patch that works for some situations though. The best solution I've ever used which only worked for games that used the LFB was NOLFBLIM by Ken Silverman. I've also heard that gsync/freesync works with DOSBox but I haven't tested enough to verify.
avatar
Engerek01: I thought DOSBox development had stopped after 0.74. That's good news :)
Nope. Development is still ongoing. Just no official release since 0.74. Anyone (even companies) are free to compile the latest DOSBox SVN for the latest game fixes.
avatar
timmy010: is this official dosbox or a fork?
Official
avatar
Qbix: that problem is due to the settings selected by GOG.
Try with the default dosbox settings.
avatar
FulVal: Sry, but that game is not on GoG... I've already tried all settings...
Post your issue on vogons.
Post edited August 31, 2018 by DosFreak
avatar
dtgreene: Good to see this release.

The one complaint I have had with DOSBox is that it lacks save states and similar features that are found in other emulators.

On the other hand, I remember once using a heavy debug build of DOSBox to make a mod to Might and Magic 2; having debugging features is helpful when trying to modify a program without the source code.
Saved States is more diffcult for DOSBox than other emulators but not impossible as shown by the unofficial patch.

Debug not provided by default since most users would never use it and those who would should know how to compile and use a build that would but if you think different then make a request for it.
avatar
Themken: Seeing how DB 0.74 is unstable on Windows 10 for some people, me included, I am sure GOG will move over to 0.75 after it has been around for while.
First I've heard of this and I've used Windows 10 since it came out and check the vogons forums daily (yes really). Post your issue at vogons if you haven't already. More than likely it's a game bug though.
Post edited August 31, 2018 by DosFreak
avatar
Lucian_Galca: Any chance for vsync to be added?
avatar
DosFreak: DOS games didn't support vsync since they were programmed for superior monitors ;) the performance was lower and further complication is the multiple Operating Systems that DOSBox supports. There is an unofficial patch that works for some situations though. The best solution I've ever used which only worked for games that used the LFB was NOLFBLIM by Ken Silverman. I've also heard that gsync/freesync works with DOSBox but I haven't tested enough to verify.
I see. I remember trying out some custom version of DOSBox called Daum I think? Supposedly it supported vsync, but I couldn't figure out how to get the vsync to work.

Hmmm, perhaps I should consider gsync for when I next upgrade my PC or build a new one.
V-sync with Daum version still works bad or it doesn't work... i see some tearing and it cause slowdowns...
avatar
dtgreene: Good to see this release.

The one complaint I have had with DOSBox is that it lacks save states and similar features that are found in other emulators.

On the other hand, I remember once using a heavy debug build of DOSBox to make a mod to Might and Magic 2; having debugging features is helpful when trying to modify a program without the source code.
avatar
DosFreak: Saved States is more diffcult for DOSBox than other emulators but not impossible as shown by the unofficial patch.
Out of curiosity, is there anywhere I could find a detailed technical explanation of why save states are more difficult for DOSBox, and of what would need to be done to impoement them?

Also, is there any issue on the bug tracker (or otherwise) to track this feature request? (I am sure I am not the only one to request this.)

I know that even QEMU, which can emulate a modern PC, has save states (it calls them "snapshots", but they're not the only feature in QEMU with that name). Is DOSBox somehow different?