PCem

Quick question, does this have a bios?

It also has to match the super I/O chip of the board.

Have you loaded ne2000.com?

Oh come on...not even mentioning?

Have you made sure the same mouse type is set for Win95?

Ok, looks like this scsi card, for disk writes, requires a V20 at least.

While formatting works fine, sys'ing (system transfer using sys.com C:) using the Trantor 130B in any XT clone (not on ATs where it works fine) results in the IBM/MS bios files (ibmbio/ibmdos/io.sys/msdos.sys) not being copied correctly or copied with 0 bytes. And yes: I've used the wx-SDL2 build of...

Well, have you set the BLASTER variable correctly in autoexec.bat?

Seems that the win32 version is not rendered correctly on first run (but the problem gets "fixed" in the second run and I'm sure on first run it should be rendered well first). Details: Guest os: Win98SE. CPU: Pentium at 75Mhz. Video card: Trio64 4MB at 1024x768x32bpp. Machine used: Award 430VX PCI....

Ok, here's a full description of the bug: The polygon textures change as the character walks (which shouldn't happen), the game was running under win98se using a voodoo2 dx7 driver, in any Pentium machine and using the dynarec (both cpu and voodoo). Config details: Award 430VX PCI. Pentium 75. Voodo...

This game's polygon rendering is messed up in the current code of PCem.
Done in all PCI-based machines under win98se with voodoo2 dx7 driver.

This is still on the trio64, which has improved significantly over the previous commits, however, one more bug has been found, namely when a fullscreen DOS box is triggered on win3.1 with trio64 drivers in any bpp, it would basically make the percentage down to around 30% and hang. (And in any machi...

Switching from a video card to another is not a solution.

In other words, painting in paintbrush is not "painting"... If you want a screenshot, tell me.
P.S: Well, I'm not a native English speaker and I tend to write as perfect as possible in English.

Somehow, with paintbrush, the drawn figure (or sketch, or whatever) doesn't get shown yet paintbrush says it is drawn and by the logs of what I had sometime ago, it seems it issues accel cmd 3. This also occurs in the Trio64 WinOS2 drivers (OS/2 2.1x/Warp 3/4). P.S: I'm sure this happens with the 1....

It used to work fine without needing customiz.exe, now it no longer does.

1.44MB floppies don't boot at all on PS/1 2011. Either in IBM DOS of the ROM DOS section.

Well, just tried the new patches and they indeed work, however, when switching to 32bpp under OS/2 Warp, the desktop is red and with some inverted colors. (This happens with any Trio64 driver for OS/2 btw).
8-bit and 16-bit modes are unaffected and they have the right colors.

Even after inserting the right reference disk and configuring its cmos, however, the bios still tells me error 2401 (video error), 8602 and 12903 (coprocessor error).
Are there any fixes to these?

Just tried the latest build of PCem (WX-SDL2) and the IBM AT 5170 no longer works with any configuration I've tried, even a bare bones one, like CGA and IBM VGA.

Well, https://pcem-emulator.co.uk/phpBB3/view ... f=2&t=2923 has the same issue as the 8088mph credits - it´s about the prefetch queue, not cycle exactness. The credits of 8088mph work in DOSBox, however.

try this:
http://www.mmnt.net/db/0/0/ftp.oldskool ... d%20System
(wss.zip or WSSXLAT.EXE)

Hello play is going to play with WINDOWS SOUND SYSTEM sound was too quiet until time until Tom Walker made sound amplification thank you even play with audio setup CDROM I managed to mute the sound in the source code because the soundtrack WINDOWS SOUND SYSTEM is cdrom too loud and I can not get dr...

does this work with cga or mda?

Ok, turns out it was 1.2.8.2 pro version that was tested here, not 2.0.

Tested by using ms-dos 6.22, with or without emm386, ami winbios 486, 32 mb ram, 486 dx/33, et4000ax, video speed fast 16-bit.
It basically does a flood of bad getpccache.

Ok, lmouse.drv (included with Windows 3.1), PCem configured with the amiwin486, 16mb of ram, TVGA8900D (just for a test), rest is default.

What exact crash are you having? log?

When using the Logitech serial driver in Windows 3.1 during the text setup with the Microsoft Serial Mouse selected in the PCem settings, it results in a freeze shortly before the GUI setup (but it works on real hardware).
I can give you a screenshot if needed.

Pheraps you might take a look at the s3_init function to know that the culprit is there, especially the vram_max part.