The readme.txt file includes the names and relative paths of the roms supported, relative to the "roms" folder. There are a few threads on the boards that talk about applications that work, but I don't know of a detailed list of limitations (Note that some things perceived as limitations are actuall...

And to add to the virtual machines talk... VirtualBox has had experimental support for 3D on WinXP (which seems that it was done replacing some DirectX libraries but I couldn't do anything serious), and version 6.1 has removed it.
Now 3D support is only present for Windows Vista onwards.

You don't interface directly with that library. That library simply translates code generated expecting a POSIX system into something that Windows understands. You should simply search for posix threads ( pthreads literally means posix threads) and compile with the compiler that uses that library, w...

Have you tried changing the buffer length on the Sound menu? I have it at 200ms here on a core i7 Win10 and works fine.

There was a name change for one of the bios for pentium. Possibly that's the reason.
Also remember that on linux, the filenames are case sensitive, so bios1 is not the same as BIOS1. Ensure that the correct name is on the .cfg file.

There is a thread about the possibility of emulating Voodoo 3 and basically it summarizes to: It isn't really worth, with the current hardware emulated.

So Voodoo 5 is at least many years out of question currently.

yes. the slirp kind of connection emulates a NAT, and that gateway is actually your host.

If they were thinking about a base image and specific diff-images on it, that should have worked sufficiently well with the support of VHD disk images that another user was implementing. Then you wouldn't need any command line switches, just one .cfg configuration for each differential disk that you...

No there is no way because DOSBox emulates one single system (MS-DOS on an x86 PC) while PCem emulates the x86 hardware and can run any kind of system.
So if it assumed a prompt based system, then that would not work for a windowed system, and each windowed system would require its own method.

It should be possible, if you use the pcap driver and configuring a bridge card. (I haven't really tested that, and the release build of PCem only has the SLiRP driver )
Not with the slirp driver, since that doesn't make it visible outside of the PCem instance where it is running.

https://wiki.gentoo.org/wiki/Gcc_10_porting_notes/fno_common It seems it could be complicated to rearrange the code in some places . Basically, ".h" files should not have variable instantiations ( like, for example bios_high_mapping in mem.h ). Instead, they should be defined on one .c file, and use...

There's one place where the host GPU acceleration could help, which is if you use the opengl3 render driver (under video menu) and use some shaders (configurable on the opengl 3.0 renderer sub menu ). But since you plan to use a CRT display, it might or might not be usefull. As for the CPU, I have a...

Hi Sarah. You missed one place to change the version number, the about dialog. IIRC you missed that for v15 too and modified it in an Hex editor
(I also missed some places in my patch: https://pcem-emulator.co.uk/phpBB3/viewtopic.php?f=4&t=3434 )

On AT (DIN) keyboard machines there are still problems. I think only newer (PS/2) machines work.
MS-DOS 6.22

On the Pcem side, the router IP is your host. ( verify it, but it should be 10.0.2.2)
I've been using a little http server application to copy files on both directions (server on host, IE on pcem). The http server is hfs. https://www.rejetto.com/hfs

This patch is only intended as a reminder on where to change the version values previous to the release of the next version.

I just searched for v14 and v15. Tried searching also for 14 and 15 but that showed too many results to see if any of them was a version locationn.

Not sure what really happened, and probably I did something stupid. I had an emulated win98 where I had the creative drivers and software for AWE32, and then installed the ones for an AWE64 Value. Somehow, midi started to not play correctly and I saw that another sf2 worked fine, but using the rom b...

RE: AWE64: The AWE64 didn't use 30 pin SIMM, but some Creative-specific memory modules. Also, the AWE64 drivers are not really compatible with this AWE32 emulation (concretely, the 1MB ROM bank that this emulation supports). I tried it on an emulated win98 and I had to recover the sbk from an old co...

You definitely cannot use more than 28MB by means of the AWE32 API, because the addresses that would permit addressing those 4 remaining megabytes address the internal ROM memory. About 4MB and 16MB, that's more about hardware accuracy. You had to use two 30pin SIMM modules ( https://en.wikipedia.or...

Each card is useful for the software it is intended to be used with. Oldest soundblaster or adlib cards are mostly for DOS based games that specifically use those. Newer SB16 is the all-compatible soundcard for newer DOS and Windows. AWE32 is specifically useful if the software uses it to play music...

Yes, that happens.

I had a quick look back then and I believe that it is not easily fixable with the current audio API. (Have a similar problem: headphones and monitor speakers).
Basically, programs that can switch audio like that do so because they connect to the default soundcard.

It definitely will not show under PCI audio, because it is an ISA card, not a PCI card.
Also, if you don't have the audio ROM, it will not work. Configure an SB16 in that case.

JIRA is an issue tracker software, not a source repository software.

You need to change the mixer values on DOS or on the emulated Windows, not on your host Windows system. When I implemented the new mixers for the soundblasters, I followed the programming guide that suggested that the default for the CD audio was silence (which in this context means -60dBs, so not c...

I can only confirm your findings (at least about ami 386 and xi8088)

It's clear that the keyboard emulation that was added on that commit that we identified, is making these systems use an incorrect key mapping.

Official pcem is not compiled with MSYS2. it is compiled with the other mingw and not using the exact same versions of the dependencies.
You need to use the dlls that are in msys2.

@omarsis81: more information is needed to know what are you doing wrong. Given that not even hg worked for you, maybe we should first verify that the environment is correctly installed. Anyway, you don't need to use hg inside msys2. you can still use TortoiseHG or whatever windows tool that you alre...

I am unsure why you have the problem on MS-DOS, since it works here, but since I had the problem in WinMe, I tried recompiling the sources and located the commit 1432 "Add ability to change AT keyboard scancode and disable translation. Fixes keyboard in Solaris 8." to cause the command prompt on Win...

MS DOS 6.22 -> Fine
Command prompt on Windows 98 -> Fine
PCem V15 Command prompt on Windows Me -> Error as in ruben's post.
PCem V14 Command prompt on Windows Me -> Works ( same disk image and config as above)

MS-DOS 6.22 here and all fine ( normal, shift and alt+gr characters)

config.sys:
COUNTRY=034,,C:\DOS\COUNTRY.SYS
DEVICEHIGH=C:\DOS\DISPLAY.SYS CON=(EGA,,1)

autoexec.bat
MODE CON CODEPAGE PREPARE=((850) C:\DOS\EGA.CPI)
MODE CON CODEPAGE SELECT=850

KEYB SP,,C:\DOS\KEYBOARD.SYS