Strange that PCem crashes when dialog boxes are closed. I did some testing with PCemV14 through PCemV17 and PCemVNext on Windows XP 32-bit. PCemV14 through PCemV17 worked without issues. PCemVNext did not start but that could be caused by dll issues. The machine used was a Core i7 950 which is from ...

I would start at the code where command line arguments are parsed. That is in the initpc() function in the src/pc.c file.

Yes, Proton is a compatibility layer to run Windows games on Linux. It is based on Wine, which is compatibility layer to run Windows applications in general on Linux. The development of Proton is sponsored by Valve to make as many Windows only games possible to run on their Steam Deck handheld conso...

The function that opens the configuration window is void config_open(void *hwnd). The argument of this function is the handle of the parent window.

You do need to load the configuration first before calling this function using void loadconfig(char *fn).

Probably not. If you want to run 32-bit games designed for Windows XP, that don't run on Windows 10 or 11, you probable get better results running Windows XP itself on compatible hardware, or using a compatibility layer like Wine or Proton.

You cannot low level format a hard disk image using PCem. (The bits on a real hard disk that mark the sector boundaries do not exist in an image file.) So you should consider the disk images to be already low level formatted.

You could also investigate if a key remapping tool for Linux could solve this problem. You said you run PCem on Linux, so you probable had compiled it from source. You could change the keyboard handling in source and recompile. But PCem has a lot of keyboard related code, so it's not a trivial task ...

I don't think PCem vnext supports advanced vhd features. So If you if you need this functionality, just make a copy of the vhd while the emulated PC is turned off. The disk sizes aren't too big and you can turn on ntfs compression to save disk space.

In a nutshell: 1. Download *PCem v17 for Windows* from https://pcem-emulator.co.uk/downloads.html. 2. Extract the zip file in a place that's convenient for you. 3. Get rom files for PCem and place them in the roms folder. Rom files are not included with PCem for copyright reasons. Forum policy forbi...

This game was designed for Windows 3.1 so it may not work correctly on Windows 95 in some cases. Create a new emulated PC running DOS and Windows 3.1 and try if it works on this configuration. The system requirements are 386DX/33MHz PC, so a 486DX/2 66Mhz would be more than enough. You could also tr...

It has been over 3 years since the latest version of PCem was released and no signs of V18 has ever been released yet! You could download PCemVNext and pretend it's PCemV18. That works for me... What kind of response are you expecting? Did you know that even if you cannot program, you still can con...

Was this also the case with PnP ISA versions of the Sound Blaster 16/AWE32/AWE64? I remember the SB AWE32 Value was configured differently from the SB16 PnP.

I just checked. The diagnose program also works in a Windows 98SE dos session, however I only tested with Windows drivers for it installed. If you only want to play Windows games, the AWE32 doesn't really makes sense. This is because Windows games don't support the AWE32 directly, only the Windows m...

Restart in DOS mode (or boot from DOS), then run the diagnose.exe program. (Part of Sound Blaster 16/AWE32 DOS/Windows drivers.) If this does not work try selecting SB16 in PCem and repeat the above. If you want to run DOS games, you could consider creating a separate emulated PC, running DOS, for D...

Have you tried connecting an external keyboard (or numpad)?

Drivers for Sound Blaster 16, AWE32, 128 PCI, and others are included with Windows XP. However older ISA cards like the 16 and AWE32 may not be detected automatically, so you have to run the Add Hardware wizard manually. For Windows XP the PCI 128 is more appropriate.

This isn't the right forum to talk about (vintage) hardware. It might be more appropriate at the Vogons forum . The most easy way to copy data and/or install games from floppy is to get an USB floppy drive. I'm not sure if booting from an USB floppy drive is supported, but Windows 98 SE and Windows ...

I ended up with an AMI WinBios 484 motherboard that was much less confusing to set up, I'll try what you said thanks. I did press F2 however I didn't who what to select as C drive! At one time I had a 486DX2 66 MHz with the same kind of BIOS. It's kinda my one my favorites in PCem. (Guess which is ...

Greywolf wrote: ↑Thu 11 Jan, 2024 12:46 pm Didn’t early joysticks and controllers work on io ports on earlier hardware? I don’t remember much usb availability during win95/98

USB support was added in a special update and Windows 95 OSR 2.1. Windows 98 had USB support builtin. USB was pretty new in those days.

Aren't Human Interface Devices for USB devices? And is USB not emulated by PCem?

Those are the same roms as for PCem 17.

Forum policy is that you cannot ask where to get roms (or non public software).

At bootup press F2 to run the setup utility. Or configure the emulated PC to have a SCSI controller. You don't need to setup the hard drive in the BIOS if you have a SCSI controller. Boot times appear to be slower because of the SCSI BIOS and you probable need to run the setup utility to configure m...

Just to be sure. You are talking about setting of the emulated PC, not the BIOS settings, right? Empty BIOS settings is normal for a new emulated PC. Please check the permissions of the files in the ~/.pcem directory. Also check the pcem.cfg file for file locations and check those permissions as well.

Okay, I just did some looking myself. I choose to find out what video_fullscreen_scale does by looking at the (PCemV17) source code. The setting video_fullscreen_scale is read a few times by config_get_int() function and set to a variable with the same name. (In pc.c and wx-sdl2.c) This variable is ...

I don't think this is documented, so your best bet is to search the source code. Either in a good code editor or by using grep, something like grep -r video_fullscreen_scale *.c *.cc *.h.

How should such platform look like? Does it need to be an emulator like PCem? Or could it be a compatibility layer like Wine or Proton?

OK, so I tried making the controller a SCSI instead of an IDE, but, it simply came up with a "Missing operating system" error. SCSI and IDE handle hard drive geometry differently. You'll need to delete all the partitions disk and then repartition the disk image. Or use a fresh disk image....

You can edit the pcem.cfg and change the paths like below to get the classic behavior: [Paths] roms_paths = roms nvr_path = nvr configs_path = configs logs_path = logs screenshots_path = screenshots plugin_path = plugins PCemVNext still looks for the pcem.cfg in the %Homepath%\.pcem folder. What I d...

Did some more testing an observed the following: 1. PCem closes randomly running Windows NT 3.5 on an emulated Pentium 2. So if you have this problem on an emulated Pentium 2 or Pentium Pro, you should try running it on en emulated Pentium. I tried an emulated Intel Premiere/PCI motherboard with an ...

Not sure, after reading your inquiry, I tried a few times today, but those attempts failed for other reasons. You could try the following to avoid the ATAPI CD-ROM detection: 1. Use SCSI hard drive and CD-ROM drive. You might need to figure out which SCSI adapter is supported. 2. Or boot DOS with AT...