Oops, thtat is a CMOV instruction. Is any of PCem emulated CPU support this?

PCem v12
CPU: Pentium MMX 233 and WinChip 240 are tried with same result.

Battler wrote:- roytam1: Your PCem binary is 32-bit or 64-bit?

32bit

Why can't you use the boot disks or boot from CD in the 430VX? Edit: the Oak OTI-067 card is too old to be supported and I think the 486SX is also not supported on Win2000, I think it requires a full 486DX as a minimum. First, it is a bug of Recompiler. When I disable Recompiler option, PCem doesn'...

After DOS based installation is finished, it boots into Phase 1 of Windows 2000 Setup and after F6 screen PCem crashes. Unhandled exception at 0x004f9ba1 in PCem.exe: 0xC0000005: Access violation reading location 0x0000038c. Stack: PCem.exe!004f9ba1() [Frames below may be incorrect and/or missing, n...

truth wrote:It is documented on Vogons that newer versions of mingw/gcc will not build against static runtime libraries. Furthermore, statically compiling certain libraries will break multithreading operations. This is also documented.

I'd file bug report to such libraries instead.

What would be nice is a pcem build that requires no external dll's but the main problem is ppl not including them in builds (not sure the real reason why) distributing it with out the dlls is useless you may as well not bother at all as its very version dll specific you cant just get them from the ...

Test with gcc 4.8.2 to verify and by compiling on native win32 (not cross-compiling on another OS). I wonder if you miss this part: PCem.exe: $(OBJ) $(FMOBJ) $(SIDOBJ) - $(CC) $(OBJ) $(FMOBJ) $(SIDOBJ) -o "PCem.exe" $(LIBS) + $(CPP) $(OBJ) $(FMOBJ) $(SIDOBJ) -o "PCem.exe" $(LIBS)

That doesn't work on newer mingw/gcc installations. Any error messages? BTW It works for me. ;) /d/PCem/src$ gcc -v Using built-in specs. COLLECT_GCC=D:\msys\mingw\bin\gcc.exe COLLECT_LTO_WRAPPER=d:/msys/mingw/bin/../libexec/gcc/i686-w64-mingw32/4.8.1/lto-wrapper.exe Target: i686-w64-mingw32 Config...

I don't know yours but my hg-head dynrec build works.


https://mega.co.nz/#!mM8DUJSC!Yc8RDXpBc ... a2-Spz1sIY

I think it is better to link stdc++ and libgcc statically (using "-static-libgcc -static-libstdc++" switch) to reduce redist package size. --- Makefile.mingw.orig 2014-11-17 20:41:02 +0800 +++ Makefile.mingw 2014-11-18 10:39:49 +0800 @@ -23,14 +23,14 @@ win-status.o win-time.o win-video.o ...

I have Troi64V+ real card (with 2 RAM chips only, other 2 RAM sockets has no chips) Is is enough to test? EDIT: I tested the card on a PC which has ASUS P4 mainboard, and I can have 640x480 4bpp in Windows PE. JDOS 6.2: blank screen, run "cls" will return to text mode. dspvv/dispvb/IBM $F...

I have Troi64V+ real card (with 2 RAM chips only, other 2 RAM sockets has no chips) Is is enough to test? EDIT: I tested the card on a PC which has ASUS P4 mainboard, and I can have 640x480 4bpp in Windows PE. JDOS 6.2: blank screen, run "cls" will return to text mode. dspvv/dispvb/IBM $FO...

since you build yourself, you may try debugging with gdb and print a stack trace with it segfaults.
it will help locating the problem.