Actually, switching to windowed mode does redraw the DOS window correctly, it just clears it immediately afterwards for some reason... Do you have the MS-DOS Prompt in Windows 3.1 configured to window by default or full screen by default? If it's the former, then it might simply redraw the old cont...

There is a discrepancy between RAM to VRAM between read and write during this process: - During write, real offset 000B8835 corresponds to VRAM offset 000020D4. - During read, real offset 000B8835 corresponds to VRAM offset 00000835. No wonder then it's reading all zeroes. Writing to real address X ...

Actually, switching to windowed mode does redraw the DOS window correctly, it just clears it immediately afterwards for some reason... Do you have the MS-DOS Prompt in Windows 3.1 configured to window by default or full screen by default? If it's the former, then it might simply redraw the old cont...

- TomWalker: Ahhh OK. BTW, as I just added to my previous post, it seems like there's something wrong with VRAM mappings in V86 mode. For some reason, writes to virtual segments A000-BFFF inside a Windows 3.1 DOS box never actually reach the VRAM, hence why they are not reflected in the real A000-BF...

After further examination, it seems to me that the Windows screen grabber reads the text buffer when going from full screen mode to windowed mode, but for some reason by the time it reads the buffer, the buffer has already been emptied. I suspect it might have to do with how VRAM to RAM memory mappi...

With some video adapters, the emulator crashes on hard reset.
The following are affected:
Standalone:
- CGA;
- MDA.
Chipset-specific:
- PC1640;
- PC200;
- Olivetti M24;
- PCjr;
- Tandy 1000.

At least for the CGA ones, the crash occurs during the recalculation of timings. Not sure about the rest.

Found a fix.

In win-deviceconfig.c, in deviceconfig_open(), find: After this, add: Then, find: Change to: It will then no longer crash.

For example, click the Configure button next to the video card selection box, and change the VRAM amount. Press OK or Cancel, it doesn't matter. Some time after that dialog closes, 64-bit PCem will crash. 32-bit PCem is not affected.

Rev 292 fixed the only bug I saw with Norton Commander 5.0 on the x86-64 recompiler, where it was complaining about corrupt source files. Didn't have any trouble with 486SX though. What's QVIEW? Never heard of it before. A hex viewer for DOS. Here is a floppy image: http://citadel.ringoflightning.n...

- ppgrainbow: As I said, it's not present in 5.0 either. I just misinterpreted certain behaviors as emulator bugs.

However, QVIEW does freeze on x64 dynarec but not on x86 dynarec so that is a bug.

Under an emulated Pentium, it starts, asks you to specify install path, then it freezes. Under an emulated 486, it does not even start, just shows a run-time error R6003, - integer divide by 0. Other information: installing from 1.44 MB floppy image to hard disk under MS-DOS 6.00. Edit: Turns out th...

So I just compiled the emulator for Win64 using MSYS 2 (which has a GCC 4.9.x), and the resulting Win64 has no sound. Internally, sound appears to be working, but I can hear nothing. No problems on the 32-bit compile. Edit: Uncommented the pclog call in the error function in soundopenal.c and now th...

- Tom Walker: No, my friend tried setting it to i686 too, it still crashed. It might be a result of too fast hardware (though then I wonder why it would happen on my Pentium Dual-Core E5700).

Well, a friend of mine did some testing just now and it seems that the crash is because of architecture set to core2 instead of i686. Edit: I just did a test myself... the crash occurs inside voodoo_generate_filter, and for some reason, having it log every single step of both loops make it no longer...

Well there's still a bug in the code if using better optimization switches causes emulator crashes. :p

but unless it is then what's the point in providing 64-bit binaries? To facilitate the abandonment of Win32 in favor of Win64. I remember when Windows 95 was released, 32-bit ports of Win16 appliations started popping up like mushrooms and in a few years, Win16 was a thing of the past. However, I'v...

It's mainly for Linux. It might turn out to be faster than 32-bit, in which case I'll release a 64-bit Windows binary, but otherwise it's of no interest for Windows users. I don't get this. Every single developer of anything I seem to read, seems to think Linux should move forward with technology, ...

Ever since revision 278, the emulator now crashes when hard resetting at any point except for in POST phase, at least with the 430VX. Edit: Turns out it was not that 278 that introduced it but leilei's Voodoo patch as it crashes during Voodoo initialization on reset (I had to make it log every step ...

Battler wrote:Saving the settings and exiting CMOS setup with the Advanced/EV causes PCem to fatal with: block->next_2->pc=0 08C29688 .

That is fixed now, but now a similar fatal occurs some time after reset: block->next_2->pc=0 073B4CF0 .

This GRUB boot disk (http://citadel.ringoflightning.net/boot.dsk) causes PCem to fatal with: Deleting deleted block .

Saving the settings and exiting CMOS setup with the Advanced/EV causes PCem to fatal with: block->next_2->pc=0 08C29688 .

Yep, it is indeed a missing Super I/O chip. The emulated 496/497 BIOS is made for an UMC 8663B Super I/O chip, which should however be reasonably close to the already emulated 8669F. Edit: Also, PCem incorrectly uses the 8669F for Batman's Revenge and Advanced/EV. In fact, the former actually has a ...

Might be a missing Super I/O chip. It'd have to be figured out what Super I/O chip the SiS 496/497 uses.

But apparently they're ready enough for you to encourage others to use your fork with them in. Which would lead me to think that they are 'ready'. Remember, I'm not a mind reader either. Because the more people test it, the more bugs are going to be found and reported, and the less bugs the finishe...

That's one of the risks when you fork a project, instead of just contributing back. If you'd contributed back your FDC changes then I would have ensured that my changes wouldn't have broken them, but I'm under no obligations to avoid changes in a certain area just because some fork somewhere (one w...

- TomWalker: Also, I was considering contributing my FDC rewrite back to you when I was done (I'm still far from done), but you went on and added in your own changes which are completely incompatible with my code. Therefore, I now feel I am unable to contribute that back to you. And I've put everyth...

- rflego: What about just adding the ability to disable cache then? That way, those who want it, can still use it, while those who don't, can just disable it.

Is there any way to modify the audio emulated code to not run out of data when the CPU drops below 100%?

- TomWalker: You could look at the PCem-X code. The FDC format command is supported and implemented (and works). And I'm working on getting XDF floppies to be loaded correctly.

- ibmpc5150: Try PCem-X. I fixed formatting there (in fact, I vastly improved on the FDC code).

Doesn't Wine exist for OS X? If yes, get it and try running PCem under it.

Edit: It does: http://wiki.winehq.org/MacOSX .