PCem

Bump.
This is getting annoying I guess.

I guess this would work.

Yeah, no longer crashes, but now it throws glitches (white parts almost everywhere).

Well, for another bug report of this, 8MB is supported on the Matrox through an add-on module but let's get into the details now. AMIDIAG for DOS, when it's in the part "Initializing Multiprocesor test", it crashes with the following log: "mystique_start_blit: unknown blit 0effffff". Any PCI-based m...

Well, I know, WIP, so it's still early, but are the official and latest Matrox Mystique PCI (1064SG) drivers from 2000-2002 compatible on PCem under Win2000/XP? In the sense, here upon reaching the desktop, it fatals with Mystique busy in the blit.
Happens on any PCI-based machine of course.

Well, whenever I click and drag the cursor over the desktop or inside a folder or whatever, it results in glitches in 16bpp and 24/32bpp modes. Happens in anything that is able to handle a S3 ViRGE or a Mach64GX/VT2 card regarding the PCem configuration used under Win2000 and WinXP, and in version 1...

And I hope it won't have that annoying glitch like the mach64 and virge have in win2000. Pheraps I should open a bug report in the appropriate section about this.
Edit: Bug report done.

Pardon my question, but does the currently in development mystique (on Sarah's end) work on win2k or something outside DOS? I know it's a bit early to talk about this.

Following that after a while, there's this:

As said above, anything that uses the dynarec, even Pentium boards.
Screenshot is here:

The OS/2 PM subsystem add-on on NT 3.51 doesn't load correctly, in the sense, that its driver is installed normally, running the PM shell causes a lockup in the dynarec, no such issues using interpreter.
This happens in anything that uses the dynarec, no matter what video card, sound, machine, etc.

Is it actually supposed to be supported on Windows 98 SE?

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?