Closed BBAlpert closed 4 years ago
Thanks your reporting! Yes, I hear about access violation recently. Perhaps, it is ascribed to enable slept many functions.
Among them, I enabled serial communication function incorrectly. I fixed it.
And i tried state save & load with 'AD&D EOB2'. It worked.
Another, I don't recommend ZIP contents for NP2kai (and other PC core). FD and HD images aren't ROM. It should be extracted.
Regard.
Thanks for responding so quickly. I assume the fixes you made will be in the next release, correct? I'm very excited.
And thanks for the advice about using ZIP files. I really need to go and extract those files.
I downloaded the latest update of the core and I'm still having some issues. However, the issues may be due to me trying to run the games improperly. If I load up just the HD image in RetroArch, the game loads up fine, but it still crashes when I try to save state. This is what I had done before the serial communication function was implemented and it worked fine then.
If I load up the HD image, then hit F12 to go in and manually set the "system disk" image to FDD1 and "disk 1" image to FDD2, then hit F1 to reboot the emulation, the game loads up fine and save states also work fine.
In other words, it seems like there's still an issue when there is an HDI file loaded but no HDM files. At least that's what has been happening for me.
Great report!😳 Thank you! I investigate up.
DOS setting in this HD image is peaky... Almost PC98 games don't need 'special' memory driver. When use VEM486.EXE, user has to know PC98's structure well.
But it's lucky that this HD image has normal memory drivers and text editor! You can custom DOS environment. And I want to know how it works. Please try follow method.
That's all. Close NP2kai. Plus one.
Then run HD image again. How?
It's working! Thank you so so much!
Starting a few days ago, attempting to save or load a state in most PC-98 games results in an access violation that crashes RetroArch. It happens with the most updated versions of RetroArch and of the NP2kai cores, and it even happens on completely fresh installs of both.
Those same games using the same BIOS were able to save states without any problem up until a few days ago. Save states still work fine with other cores, and the PC-98 games still run fine with NP2kai, it's just the save state that crashes the program.
I've noticed that it only seems to happen with games that display the "V E M 4 8 6 Virtural XMS / EMS / VCPI Memory Server Version 1.29N" thing when booting up, and even then, saving states only crashes the program after that bootup screen. You can still save during the few seconds of bootup before the VEM screen.
I managed to capture a screenshot of the log window RIGHT before the program crashes, and it says that it's attempting to execute data at address 0x0000000000000![access violation](https://user-images.githubusercontent.com/64142304/80021825-1ed77e80-84a9-11ea-96b7-dc9fbab8e2b7.png)
"retroarch_debug.exe caused an Access Violation at location 0000000000000000 DEP violation at location 0000000000000000."
A sample crash log: https://pastebin.com/q1VBZqMc A log of the session when this crash happened: https://pastebin.com/NJ9dw0KR
I'm new to using GitHub, so if there is any other information you need from me, please just ask.
Thanks!