PCem

Well, revision 1168 caused this bug.

Basically, if you change acc2168´s port 78 to return 0x20 instead of 0, a siren sound should be heard, but somehow with the new timer code, what you hear on the pb410 using interpreter is some garbage, but still works fine on dynarec, but its sound is distorted unless ISA_CYCLES(8) are subtracted on...

What SuperIO chip does this use?

Excellent fix! Thanks!

Though, in win3.0's built-in 512k v7 driver, it does this.



I wonder if it's about the cursor ram or something, or the vram.

Hmm the built-in win3.x video7 drivers that support the ht216-32 show this reddish bug and I wonder if it's the acceleration. Also, thanks for the above fix.

Hmmm, there some bugs in the current ht216 implementation, especially this.



Driver used is in the following link:
https://mega.nz/#!v19VTChS!lZ8uEdJtCcr6 ... nIYm0KsgfI

Are you sure this also fixes the LCD MDA/normal MDA configurations? I still get a blinking cursor on a green background, or maybe I haven't applied the patch properly.

I can't get the MDA and LCD MDA modes to work, it only sees a blinking cursor.

May you please provide some sample code? Just asking

dondiego , bro , this is not PCem but pcem clone, and anything with 86box will not be discussed here, you can download PCem source from https://bitbucket.org/pcem_emulator/pcem/downloads/ and compile yourself, then if anything is wrong it will be discussed here. Please dont mention 86Box here as it...

Here I'm using Win7 x64 SP1 with MSYS2. After injecting some files, vmm32.vxd would corrupt itself here. I don't know what's causing this, anyways, nice fix .
Edit: this doesn't happen with the Win7 disk management tools, for now.

I mean, well, once it has installed win95 and rebooted (after the whole setup routine), for now, it's fine, but once adding one file (as little as 32kb for example) in the vhd (after closing PCem), it would result in some files (not all) missing like vwin32.vxd, etc, thus, corrupting and making win9...

Your latest patch solves my issue, thanks!
Edit: At least, just partially, attempting to add files from winimage or mounted through imdisk results in missing other files or corruption again.

Well, it happens when I create the dynamic vhd's from pcem. Also, to note, I'm using Win7 x64.

Nice patch! However, I found a bug in this patch. The bug is about when win95's first phase setup is finished, opening a dynamic/sparse vhd to view files with winimage results in a corrupt/blank vhd (with winimage).

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....