PCem

Look at the parameters being passed to piix_init()...

I'm trying to add a new computer - IBM 300GL model 6282 - It has the 430VX chipset (already emulated) and the PC87307 Super I/O (only the PC87306 has been coded) I tried to compile the new model using the PC87306 Super I/O but doesn't work. When I try to run the new model the emulator quits - I sea...

The extra 128kB should be accessible as conventional/base memory if you're using MDA/CGA/Hercules video. EGA/VGA and later will render it inaccessible.

That's normal. PCem generally limits RAM to what would be possible on the real system you've selected.

No. I don't know how many times I have to say this...

I'd forgotten to actually test that, so I'm glad to see the K6 timings are accurate enough to break Win95a.

No.

You can see how much CPU time the Voodoo threads are taking in the PCem status window. The percentage before the frames/sec line is the FIFO thread (though I think this is a grotesque overestimate, and counts the time this thread waits on the render threads), the two percentages below frames/sec are...

No. Currently FPU is only emulated on 486DX and later CPUs.

You want a reaction from me? I honestly don't care about this in the slightest.

Not a lot for the most part; the main CPU load is the CPU emulation, and that's strictly single threaded. The only reason to go past 4 cores is if you want to emulate a Voodoo 2 SLI setup, as the Voodoo emulation can use up to 3 threads per card.

One of the problems with implementing timing for the K5 is that AMD never publicly documented what actually changed between the SSA/5 and 5K86 - and clearly there were some major changes, given how different the per-clock performance on the two cores is! At some point I need to sit down with both ch...

Sorry, may be I made a mistake, I use the following to compile will be show the error, $cd pcem/src $make -f Makefile.mingw-wx-sdl2-network That makefile has no references to codegen_x86-64.c (which doesn't exist in v15). Are you sure you've actually got a clean checkout of v15, and aren't mixing f...

On a Pi3 I can run Doom 2 at 486/25, but most things are happier at 486/16. The A53 is not a fast cpu.

rex_c wrote: ↑

Mon 20 May, 2019 1:38 pm

One more thing, seem forget to change the version no. here....

I forgot there even was an About dialogue. Fixed with a hex editor...

omarsis81 wrote: ↑

Sun 19 May, 2019 10:09 pm

Thank you! v15 finally arrived!
One question Sarah: do you have more ideas for further optimisations?

Yes. It's mainly a matter of time and energy, and I don't have any of the latter left at the moment!

Not sure what I can suggest for that. Try a newer GCC?

PCem v15 is (finally!) available. Changes since v14 : New machines added - Zenith Data SupersPort, Bull Micral 45, Tulip AT Compact, Amstrad PPC512/640, Packard Bell PB410A, ASUS P/I-P55TVP4, ASUS P/I-P55T2P4, Epox P55-VA, FIC VA-503+ New graphics cards added - Image Manager 1024, Sigma Designs Colo...

FDC fixed in rev 1471.

Try :

config.sys autoexec.bat

Code: Select all

It's been broken a lot longer than the last commit...

Fixed in rev 1461.

Known issue.

EDIT: Just found a dynarec-related music stutter bug with Command & Conquer (DOS) and Red Alert (DOS). AMI WinBIOS 486 iDX4/75, Win95A, Trio64, SB16. Occurs during 100% execution. Fine on interpreter. Windows 95 versions are fine. I'm getting stuttering on the interpreter as well, doesn't seem to b...

Fixed in rev 1457.

OK i've went through the whole PC-DOS mini image FIC VA-503+, AMD K6-2/300, 64mb, ViRGE/DX 4mb, SBPro 2 (IRQ5 DMA1 220H), FreeDOS "PC-DOS MINI" HD image (Full of demos on a launcher with FreeDOS) Working: Wolfenstein 3D demo About Wolf3D,in some cases (huge room with many foes) the new dynarec is s...

leilei wrote: ↑

Mon 13 May, 2019 1:20 am

Code: Select all

Some issues:
	Sacrifice (Black screen hangs sometimes)

Not yet been able to reproduce this. How often does it happen?

Don't know if it's the same bug, but I just committed a fix for a crash bug relating to PS/2 systems at rev 1454.

Rev 1449 should fix the CMDFIFO issues. Turned out to be an MMX bug, triggered by Creative's AudioPCI drivers using MMX/FPU in the background - which the drivers included in Windows ME apparently don't. Seems VIA can be let off the hook for this one.

Rev 1447 fixes Battlezone. That was a fun bug to track down...

Not for v15.