PCem

There's strange IRQ-related issues with it at this early WIP stage i've noticed on other boards (at least that's what the Powerdesk Diagnostics bring up), and the most stable setup right now is a ZP+Win95+4.10.01.4120 EDIT: Disabling the floppy drive in the bios can potentially produce a reboot loop...

Try deleting UNIVBE.DRV and run UVCONFIG

I've used 40-60gbs fine with Win98se guests just as i've had in 1999-2005. It's those older Socket3/7 BIOSes that were fussy about hard drive size heading into 7gb at best (many large drives had a jumper for limiting to that for compatibility reasons) though you'd also be able to install that EZ-BIO...

Yes, emulating faster CPUs require faster CPUs. K6-2 has 3dnow extensions, which some drivers and games can use and require even more CPU to emulate (on top of the faster clocks) Also the Windows desktop doesn't get along with dynarec so installing a HLT-spamming thing like "cooling tools" such as R...

It's compileable. Sounds like your makefile leaving out vid_mga.c

The "proper way" back then would be dealing with whatever real-mode drivers your OEM conveniently supplied at install time, or whatever drivers your mouse/cdrom kit supplied on floppies. but nowadays you could lazily take OAKCDROM.SYS from the 95/98 boot disks, throw them in autoexec.bat/config.sys,...

Most likely the FPS gain's from the post-launch work on ref_gl.dll. Quake2 was not very multitexture optimized at 3.05's launch, and the Voodoo2 wasn't out yet (though, Carmack did have a pre-production V2 board in Jan '98)

I've seen the Nuclear Strike video corruption happen with real hardware (Voodoo Banshee) so i'm leaning towards EA goof than PCem bug.

The 3dnow! version of Q2 should be a separately obtained special v3.20 version and should display a disclaimer baked into the console background (as well as changing the names of the selectable renderers). Offiical Q2 patches are not 3dnow! optimized, and Q2 3.10 predates 3dnow (Jan 1998).

I don't like the whole git pushing either and I use git and Github for my code and I find version control as some complicated suffering with web-based repositories getting random functionality regressions. Dropping a post with a diff here feels comfortable enough I know years down the line there's g...

Given the graphics and timeframe, Motorhead's probably more for G200 and not Mystique. I also hope you're not confusing Motorhead's SGL backend for the Matrox M3D which was a PowerVR card (and there, it substituted blending functions for premultiplied alpha blends). Wonder if that the Keen4 jerkines...

Looks like Mystique yeah. Wonder if it could run Sento/Creep Clash (for the Impression)


I've never had a Mystique so this'll be interesting to try... I have "brute-forcing the Techland MSI MiniGL on all GL games" ideas in mind, imagining the alpha stippled lightmaps...

10-Six actually ever make it out of beta? I remember that game dropping off the radar. It did actually come out in February 2000 and it did in fact work on the 3dfx Voodoo2 back then. I haven't checked for any post-closure revival projects to see if that's still working in PCem. Heck I don't know i...

*off the top of my head*
Try adding this to CONFIG.SYS and then you'll have to add this in AUTOEXEC.BAT (or a separate cdrom.bat batch file to run instead in case of memory issues)

I'm in the US so all of these ads (except for the Pentium one) are all new to me! I couldn't find any adverts for the Gravis UltraSound or AdLib Gold. For GUS I vividly remember this guy. (Source: Computer Gaming World #110, September 1993, scan courtesy of cgwmuseum (note that green line so it's de...

The reason for the link request removal are exactly about the very files you are attaching right now...


Sarah doesn't need copyrighted ROMs on her forum if she wants to implement emulation of anything.

(also i could've sworn Gateway 486s used S3 Trio32s)

It's not possible to split single-core CPUs into multiple threads.

PCem already does use multiple threads for the other parts (Video, Voodoo lines*SLI)

For 2, there's the OpenGL 3.0 renderer that supports loading libretro GLSL shaders. That's where you can get your CRT fun on

I don't think Blade of Darkness ever supported the Voodoo2. When I did try the demo I believe it tried to use the slow D3D software rasterizer (and had more issues beyond that, I think the character bones messed up). It did do super-advanced-for-the-time renderer things like (Carmack's Reverse-ish) ...

My early GF2 experience back then had heavy CPU bottlenecking too and I ended up cranking the (Supersampled) FSAA for a lot of stuff to compensate the slowness with image quality of all the jaggy poly edges smoothed (and all the 2D artwork and some overdrawn buffer feedback artifacts that come with ...

Hyperthread's just more threads on a core, it won't help much when PCem uses one thread for the CPU/sound. A Core I5 without HT will still have a much better IPC than Bulldozer (and 1st-gen Ryzen) and handles V15's PMMX 233-300 often nicely. Bulldozer even had some IPC issues vs AMD's earlier Phenom...

Also for the record when I say something is possible to emulate with the information already out there for anyone willing, I don't want anyone to infer that as nudge or interpret what I said as a request. I don't like being behalfed and adding more pressure would suck out the passion of a hobby pass...

Are you sure you're looking at a bug? Keen4 (and derivative engine games) have a SVGA compatibility switch for issues like that in mind. Turning that on will make that corruption go away.

The thing is, 3dfx released about all their juicy tech/data sheets on closure. (forget if they had V4/V5 sheets though, that'd be their TNT equiv right there) nVidia's still keeping that tight for the early NV series. I think they've only released docs on one of their more recent cores (for Noveau G...

PCem isn't a virtual machine and KVM won't do any benefit regarding emulating old computers faithfully - especially considering the CPUs that support virtualization can't do 3DNow. Also note that github you linked to is not part of the DOSBox project but a rather distant fork that has big ambitions ...

I'm well aware that many games can run with wrappers, cracks and tweaks. That's besides my point within an emulator's context. I like preservation of computer experiences. Also i've noticed depth flickery on old 3d games since the dawn of D3D10 cards and that makes me sad. PCem could get some of tha...

There's still that Direct3D 6-7 primary device gap that VM software can't touch. Also as for VirtualBox, they're retiring the video device that brings 2K/XP OpenGL passthrough pretty soon. (the other newer devices don't have a 2K/XP guest additions driver (yet?))

I've always seen the overly-large disc support as an unintentional happy accident if anything. DVDs were never supported. Also real-mode CD-ROM TSRs don't like large images either.

There's a lot of DOS sound stutter in V15 on lower emulated targets and most of it seems to go away when under Win9x. Supposedly it doesn't happen under FreeDOS

The dynarec was ruled out as it does happen on interpreter, though V15 also had a lot of timer changes...