For the built-in mach64 drivers, you need a nvram tool to make other resolutions work, search for "utl-314.exe" for the utility that does it.

Well, in the code, there should be something that makes the CD-ROM not being IDE specific/hardcoded and then multiple CD-ROM drives. (For example: QEMU Manager had an option for hard disks if they were SCSI or not, this case would be the same for CD-ROMs on PCem).

Also, the Trident TVGA8900D is nothing more than small upgrade to the existing B/C series, and on most OSes it is referred to as "CL" Oh...really? So, how would I get the TVGA8900D drivers to work on Windows 3.0 then and are there any hacks or workarounds to do it? Well, simply put the Wi...

Also, the Trident TVGA8900D is nothing more than small upgrade to the existing B/C series, and on most OSes it is referred to as "CL"

The VGA Charger (28800-5) can have a maximum of 1MB of video ram. Thank you very much for telling me. :) It's no wonder why the emulated VGA Charger (28800-5) isn't even upgradable from 512 KB video RAM...so, it's gonna have to be addressed. According to vgadoc, there's a register setting for it, t...

The VGA Charger (28800-5) can have a maximum of 1MB of video ram.

Well, they could, but not the true original ones, since, as I said, they are MCA only, but I think ATI's clones of them could be implemented as well (MAME has a 8514/A implementation on ISA, but I don't know how much it's accurate for Windows).

I tried to search for Windows 3.0 graphics drives for use on the Trident 8900D, but there are none available. :( I haven´t tried, but... won´t Windows 3.1 driver work? Did you try these? https://www.vogonsdrivers.com/getfile.php?fileid=257&menustate=0 Most Trident TVGA8900D drivers for win3.1 w...

Well, the original IBM XGA is a MCA card, though some ISA clones exist.

The main purpose of adding this SCSI adapter is for operating systems that don't like IDE CD-ROMs too much, like NT 3.1 and probably some others, like NeXTStep 3.1 for x86.

hmm ok, then it should be moved, I forgot about that section. sorry

I'm in the process of finishing it for inclusion on PCem, but while testing DOS drivers as well as NT ones, it just goes on nuts with the MBIF interrupt bit set. If anyone has some knowledge of this adapter then please help me complete the Mailbox stuff. here are the files with the code inside: src_...

About the BIOS rev, what's the advantange?

I tried searching for hours where it is on PCem's code, I think it is absent from it, if anyone has managed to find some piece there, where is it? Thanks

SarahWalker, I verified in my installation (be it Easy Mode or Advanced Mode) that sb16 (non awe32) works fine, it got past that point of installation.

Are you using Warp 4 or Warp 3?

The 82C836 chipset is identical to this, but for 386 processors, though I'm struggling finding an award bios for it.

screenshot of how the display is supposed to look like with the 1.x ET4000 PM drivers from the above link (on MAME, which also emulates an ET4000)


I can provide the logs if requested

http://pastebin.com/7dmWfTjC

I tried porting it from QEMU, but yeah, it's still primitive about that command.

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.

Small update: works now if I do #if 0 between lines 1913 and 1919 in vid_voodoo.c

I do Tom, for all Windows programs.

Sorry to ask, but do I have to generate it with "bt" in gdb? Edit: nvm, figured out: here's the full log. Register Dump: (gdb) info all-registers eax 0x1628ba0 23235488 ecx 0x12c000 1228800 edx 0x19ac0020 430702624 ebx 0x0 0 esp 0x1a6dfc1c 0x1a6dfc1c ebp 0x1a6dff08 0x1a6dff08 esi 0x0 0 edi...

When the voodoo recompiler is enabled and I try to do some Direct3D tests like dxdiag, it segfaults with voodoo_x86_data() being at fault.
Note: I'm using the Voodoo1 drivers from 1999 for win9x.
Drivers: http://www.falconfly.de/voodoo1.htm 01 May 1999 ones.

Well, I tried a gazillion of drivers specifically for OS/2 2.0 and for the emulated cards of PCem, in 16 color mode, they work (ET4000AX, TVGA8900D), but 256 results in blackness during boot and I remember that it worked on mame with the ET4000AX in 256 color mode. Link for the drivers: http://files...

How it's supposed to look like:

Under Windows 95 (but not in 3.1x or 98 or WinME) in 32bpp mode (all resolutions) this happens when trying to play some win3.1x games such as 4play:
This also doesn't affect third party win95 drivers for the card, only built-in ones are.
Game here: http://citadel.rol.im/mach64_bug.rar

Under all operating systems (even Windows 3.1 as well as Windows 9x), this results in a black screen that remains in a "stopped" state, that is, the bios cursor doesn't flash and doesn't output this resolution and note, this happens with all its supported color depths (8bpp and 16bpp). Edi...

Well, even atapi uses it (and that's already emulated). However, I was wondering how I can make a sort of "replica" of it, as I was analyzing the function atapicommand so I can make a sort of "scsi_command" for my aha154x work for inclusion on mainline pcem (if possible of course...

you need 2.0.0 beta 3 of xtide for the IBM PC, XT and compatibles (though, not requested, 2.0.0 beta 3 should not be used for the PS/1, where you need 1.1.5 for it).