It's now in C:\Users\username\.pcem\roms (for platform consistency)

Tools about disassembling Verite library binaries could mean anything. like disassembling vquake's to study to attempt to reimplement all the vquake techniques in c for a verite-less vquake port for one use case

If it's a Win98 system you'd probably want 4gb-13gb anyway, as most drives on the shelves at the time of 98-98se's release carried that capacity.

It's dynamic size only for the file size only (i.e. an empty drive is less than a megabyte). Once it's partitioned and formatted, it's staying that size. You can't change the physical size afterward.

Bingo
https://pcem-emulator.co.uk/phpBB3/view ... 4629#p4629

The only other LLE 3dfx emulator out there is MAME and the LOD's busted there too (as seen very visibly in nflblitz and warfa)

Banshee's when the big resolutions like 1920x1440 started getting flaunted. Larger resolutions than that warranted better cards with better DACs and there wasn't much beyond 60hz for very high >HD resolutions.

....there's so many other gaps to cover before to even think of getting to "early 2000". PCem isn't obligated to go through the course of Moore's Law. Besides, "early 2000" is already here. The Cyrix III. The K6-3. SBPCI 128. The Voodoo3s that went on clearance. To make it more o...

A bump to point out there's now an effort at reversing ESFM to understand it better
https://github.com/jwt27/esfm

PCem doesn't modify the host computer in anyway. The computer's trapped in a window or two and can only change the contents of a mounted hard drive image file (a file that's an .img or a .vhd).

https://twitter.com/canadianbryan/status/1030113304730103808 Open source developers do NOT have to: • Make your issue a priority, just because you say so. • Merge patches, just because someone sent them. • Give you any sort of "timetable", or explanation for why it's "taking too long...

Check your ROM file casing.

https://github.com/sarah-walker-pcem/pcem/issues/184 for context, the OP is trying to run Android OS and Fire OS, with the intent for tool assisted speedrunning of (likely mobile) video games. (of which PCem will not ever do. PCem emulates desktop computers generally from 1981 to 2000 - extremely di...

Name one emulator that can do all rendering in OpenCL and is actually faster. PCSX2 once had an OpenCL renderer (2014-2020), it wasn't really faster and had to e stripped for adding too much building complications (conflicting SDKs) and nVidia didn't embrace OpenCL as much as AMD and Intel did, as t...

no.

Virtualizing CPUs through brings unpredictable variables from hardware that can be out of reach and hard to debug. Also that's like the thousandth time VM'ing was suggested...

The Creative card used SDRAM. Reference banshee used SGRAM. References of Banshee being a stripped Voodoo2's a bit of a misnomer as it has a far better memory controller and can handle a scene in Quake3 with far less texture thrash hitching (especially compared to V2SLI) and has somewhat better comp...

fine, you want a rom?

Without cache penalties emulated, PCem's emulating faster results than what you would find with those real CPUs, especially regarding the Celerons and K6s. Keep that in mind

What's not "fully working"? I haven't had issues with Voodoo3 and SBPCI on XP. It's a little sluggish but that's how XP was on the 6th gen PCs, and there's always been a slow detection hump to get over after setup that always seems to be forgotten about, especially as many first impression...

8086tiny also doesn't emulate up to the 6th generation of computer hardware...


The whole point of 8086tiny is to show it's possible to have an emulator in some very small piece of code. It's more of a coder flex than practicality.


Also as for PCjs... have you tried compiling a modern web browser?

GUI toolkits' dev files are always big to unload. On the other hand, 1GB's small compared to what you'd have to grab to do any microsoft visual studio compiling on modern windows. It doesn't really matter what target it emulates, as you'll soon learn that there are some 5th gen console emulators tha...

in the google ideal world, every non-https site is broken.

The "monochrome" is not a PCem bug, it's an outside-person-who-made-some-"roms pack" error.

Voodoo2 drivers don't provide anything for the Voodoo3, and vice versa.

https://www.pouet.net/prod.php?which=91938 Hardware capture (for reference/awe) Tried it on v17 and noticed these bugs on a stock XT 4.77MHz+CGA(RGB) configuration Intro- the emulated CGA overscan border not being large enough to make the smooth screen transition Elephant - melts down when electrocu...

tk421 wrote: ↑Mon 15 Aug, 2022 7:24 am I really hope this is not the same problem as I had with Homeworld Cataclysm. It never ran no matter what I did.

That sounds like the anti-debugger stuff Sierra started putting in releases since Ground Control and also show up on Tribes 2 and Blue Shift

At this point i'd blame the disc protection. 1999's also when Safedisc/SecuROM started showing up on EA's games and sometimes they may have silent failures. When I've tested 99-02 EA games on PCem earlier, i've had PCem pointed to the host VirtualCloneDrive with my clonecd dumps mounted on them.

Quicktime has nothing to do with new video chipsets.

you'll also need DirectX 7 (minimum) installed for those drivers to work with Direct3D at all. The screenshots you posted show you're using a DX7-dependent driver with DX6.1, which is not going to work. The driver's readme also notes this: This distribution contains Voodoo drivers and control panel...