Attached is a patch for mem.c which corrects a minor error in the loading of the Endeavor's BIOS. The current code seems to presume that the Endeavor uses the same size BIOS as the Batman's Revenge, which is wrong. Of course, in actual hardware terms they both use similar 128 KB Flash ROMs, but in f...

Good to know. I had been confusing the HMA with one of the memory areas just below the 1 MB boundary. Realizing now that it's just above that boundary, what you say makes sense, and probably does explain what's going on here. It's not a big deal, but it would be nice to get that code sorted that's s...

For me it's definitely not related to the cache setting. There's something else going on. Are you using EMM386 or similar? If so, try disabling it. I've found that EMM386 triggers another entirely unrelated bug in PCem that drastically slows down the emulated PC under certain conditions, thereby art...

Sorry to bump this, but I've now noticed something else of interest in relation to this. Regardless of how the emulated system is configured, when DOS is loaded "low"/"noumb", the dynarec doesn't choke at the DOS prompt at all. The execution rate never dips below 100% at all, eve...

It's been years since I actually played with one of these boards, but I could have sworn that that particular BIOS managed to detect the presence of serial mice as well. I might be thinking of a different board, though.

Sorry, I must be missing something - in what way does this make the Advanced/EV unusable? The BIOS POSTs with no errors, and DOS mouse drivers and Windows correctly detect and use the serial mouse. D'oh! There are actually two issues, one of which was entirely my fault, and I appear to have conflat...

Sorry, should have been more clear--the Advanced/EV is currently unusable, because the BIOS detects no mouse at all. Battler seems to think that fixing this will be as simple as switching the mouse init on that machine over to PS/2. Been so swamped I haven't had a chance to verify that, and alas sti...

Nice one, great to see that the issue with the Premiere/PCI wasn't too much of a problem and it will be good to have it back in action. Any chance of getting the mouse re-enabled on the Advanced/EV in time for 10.1 as well? I had a quick look and it did seem as straightforward as Battler indicated b...

It could easily become an issue as PCem gains in popularity, which seems likely to happen. There will be games and other software titles that become widely known for running best in PCem, and it would then be trivial for someone to release infected versions of those titles to abandonware sites which...

Yes, it's possible, but I'd imagine demand for this would be near non-existent. I can't speak for Tom, but I'd guess that you're likely the first person who has ever bothered to ask for this. That said, it's an understandable thing to want if you're one of the vanishingly few people running a modern...

Fantastic work all around, Tom. Everything looks to be working properly with the v10 package now. I also noticed the duplication of the "4 IDE hard drives" in the feature list, but I see that neozeed beat me to it. :) I can also confirm that exiting the CMOS settings crashes PCem on the In...

That was a clean boot of DOS 6.22, on a Winchip 240 (the fastest CPU emulated when I started the recompiler, somewhat slower than the Pentium MMXes you can emulate now), on a 3.6 GHz Ivy Bridge Core i5. If your setup differs from this at all then I'd expect the performance to drop somewhat. Thanks ...

Yeah, I get it. Check out this post, though: http://pcem-emulator.co.uk/phpBB3/viewtopic.php?f=3&t=85&start=90#p1077 That's Tom's most recent dynarec performance summary. Note, right off the bat: DOS prompt - 96% faster (55% / 108%) 108% at the DOS prompt! And I believe that Tom was running ...

ecksemess, could you post your CONFIG.SYS and AUTOEXEC.BAT files here? There may be something there causing slowdown, most of my benchmarking was done on a clean boot. In general though, idling (on pretty much any operating system) hits all the weak points in the current recompiler and hence doesn'...

In general, I've been getting great performance out of the dynarec, but I've noticed that the execution percentage plummets strangely while idling at the DOS prompt, in ways that suggest that something other than the usual issue of an idle loop hitting one of the dynarec's weak points may be the cul...

An oversight in the re-ordering of the ROM set enum in r346 has caused problems for the Phoenix 386 and the DTK 386, which have now lost their 386 classification. Actually, the problem was worse than that, as there were several misclassifications even before the re-ordering in r346 (IBM PS/1 Model 2...

Granted that the cache simulation feature obviously has its shortcomings, I've found it incredibly useful as an auxiliary speed- and performance-tweaking feature when the main settings on their own aren't quite allowing me to get the emulated system to behave the way I want it to. I've spoken to sev...

Return to Zork required 19,519 *KB* of RAM for its sound drivers?! No wonder I had so much trouble getting that game running! ;) In all seriousness, yes, 580-some KB was an incredibly daunting requirement back in the day. I remember. Oh god, do I remember. I was there for "the hell that was MS-...

Don't install quemm. or emm386 or anything else like it. try to keep the configuration as PLAIN and SIMPLE as possible. More like, the bug in PCem needs to be fixed. Again, I did I=B000-B7FF on real hardware all the time and never had these problems. Only in PCem does that cause problems. PCem's me...

No worries, better late than never

By all means, give it a try--I personally have only had the issues after using fullscreen, but what you describe sounds very much like something that this patch might fix.

Apologies for the bump, but I'd like to know if anyone has applied this patch and had any sort of experience with it worth mentioning, for good or ill. I and a couple of other people I know have found it to be successful at clearing up the host mouse glitches that we've noticed occasionally during a...

Attached is a patch for win.c which should fix several annoying glitches I've noticed that sometimes cause the host mouse pointer to disappear, freeze, or behave badly after switching into or out of fullscreen mode. The bugs only come up under certain circumstances and on certain host configurations...

I'm sure I speak for many when I say that your "insanity" is one of the better things to come along in the emulation scene in many years, Tom. ;) You've single-handedly brought the current state of PC emulation up to something respectable. It's actually been quite something to observe the ...

I don't have Linux set up at the moment and therefore can't actually put this to the test, but I know a lot of people who will be thrilled about this (even to the extent that they've been waiting on such a development to really dive in and start using PCem), so many thanks on their behalf. Excellent...

I see. For what it's worth, I've greatly enjoyed having the setting there to mess about with, hack or no hack. I'd be sad to see it go, even if its value is more as a semi-novelty than an actual respectable feature. Thanks for the info.

Understood. Speaking of which, if/when you ever turn your attention toward improving the cache emulation, would it be feasible to make it settable to actual values, instead of simply "a little/some/a lot", etc.? It's a relatively minor thing, but it is somewhat jarring in contrast to the h...

rflego, now that the bug has been fixed, are you getting a consistent 100% or a consistent 30% when you run the MMX 233 on the Windows desktop? If 100%, can you try a bunch of high-intensity games and applications to see if anything you do ever makes the execution dip below 100%? You do appear to ha...

Oh, I see. Not the kind of "random dialogs" I was envisioning, but you're in luck, as I once had the same issue you're having now and it's actually quite easy to fix. Here's what's going on: some versions of the gnu compiler appear to have a bug wherein when a pointer within a certain type...

I actually tried to build the latest build, nerd73, using the kit you're talking about, and I ended up getting a build done successfully, but it had some really weird issues with the drop down menus (couldn't select the new MMX processors or 3DFX, they simply weren't there, along with some weird is...