I tried installing DOSbox 0.70 on my laptop and my workstation. I got the Windows "Application Error" stating:
The instruction at "0x6812e699" referenced memory at "0x00000104". The memory could not be "read".
What gives?
I use ISO-8601. You should, too!
What operating system?
What video card?
What DX version?
What video card driver version are you using?
And does it happen on both your laptop and workstation, with exactly the same error?
Never thought this thread would be that long, but now, for something different.....
Kreshna Aryaguna Nurzaman.
Workstation is Windows 2003, laptop is Windows XP.
DirectX 9.0c of Feb 2007 is installed.
I use the standard drivers given by Windows.
I'm not sure if the error address and reference is exactly the same. I'll check 'em first.
{p}
I use ISO-8601. You should, too!
Tried any of the output=xxxx methods available?
Intel i7 5960X
Gigabye GA-X99-Gaming 5
8 GB DDR4 (2100)
8 GB GeForce GTX 1070 G1 Gaming (Gigabyte)
Gee, I thought I have posted my reply... 😦 ... apparently my ISP had eaten my reply. So, here's an update:
For the Windows 2003, I have installed 865 driver from Intel. Now DOSbox runs without error.
No such luck (drivers) with the laptop...
I use ISO-8601. You should, too!
Check the hardware acceleration settings and stuff like that.
What kind of video card in the laptop?
wrote:What kind of video card in the laptop?
Now that's the problem... I have no idea. It's not really my laptop, just one 'entrusted' to me by my office.
I use ISO-8601. You should, too!
Well, you could try running a system identifier software such as Everest or SiSoft Sandra to find out.
Intel i7 5960X
Gigabye GA-X99-Gaming 5
8 GB DDR4 (2100)
8 GB GeForce GTX 1070 G1 Gaming (Gigabyte)
I have the same problem, the weird thing is that DOSBox 0.65 works fine. The problem only occurs with DOSBox 0.70. but I tried the 0.70 version in my other Windows instance (clean installation) and it works good. I don't know what is the problem. :<
That's been suggested already but when I tried DOSBox on Windows 2003 I experienced the same problem. It was enough turning hardware acceleration to the max.
