SarahWalker wrote: ↑Mon 04 Jun, 2018 7:06 pm Fixed in rev 1183.

Thanks.

Yeah, looks like creating a variant 4 UUID should do the trick. Can be done with some random bytes and a bit of bit manipulation. No real need for cryptographic RNG for this purpose either, although it looks like arc4random from OpenBSD would do the trick if we did need it. I'll probably just stick ...

I've been thinking about VHD support for PCem for a while. Having never contributed any code to PCem before, it looked like adding VHD support wouldn't be too difficult, so I finally decided to have a go.

And initial VHD support has been implemented. See => viewtopic.php?f=4&t=3044

2018-06-29: I consider this patch DEPRECIATED. I have now added a lot more functionality, including dynamic VHD support. I created a new topic for the patch, available here: http://pcem-emulator.co.uk/phpBB3/viewtopic.php?f=4&t=3056 After tearing my hair out figuring out wx-config.c , I have fi...

My compiler (Mingw-w64 w/ GCC 7.1) has thrown up a string overflow error in the initpc function of pc.c . The problem occurs here: strncpy(discfns[0], argv[c+1], 260); The root cause is in ibm.h here: char discfns[2][256]; I have fixed it in my local environment, but I don't particularly want to com...

That's alright, I've found a way of doing it using the method suggested here . Simple, and doesn't require compile time or run time checking. And since the only purpose is to read/write a one-time footer, performance is hardly an issue either. I think I've got the VHD footer reading working. The nex...

Sarah, is there an endian function floating around in PCem already (that doesn't rely on networking support)?

The VHD footer stores it's values in big endian, which I will need to handle in some manner.

Ugh... wx-config.c is not... pleasant.

Unfortunately, that seems to be the file one would need to modify to add VHD support. I shall see if I can figure out what needs to be added.

Sorry, there's always a huge number of other things that need doing, so this request keeps slipping. Does anyone else fancy implementing it? It shouldn't need any real knowledge of the emulator code - all the hard disc image code is abstracted into hdd_file.c so shouldn't need to touch much other c...

I've been doing some more reading, and it looks like the Precision Pro is likely the easiest candidate to add. Unlike the 3D Pro, there's no pesky analog mode emulation to have to worry about (apparently it's quite the dance getting the stick in and out of digital mode). And unlike the Game Pad, the...

More joysticks in general would be interesting, though only a few resemble the common DS3/X360 pad. Closest I can think that does in the emulated period is the SV262 and that's not a sidewinder so it's O/T :(. Yeah, not really after a something that can emulate a modern gamepad. More just wanting t...

Hi all I was wondering if anybody would be interested in adding support for MS Sidewinder joysticks such as 3D Pro and/or Precision Pro. PCem already supports the SW gamepad, and from the limited reading I've done (skimmed the Linux driver and Patent US5628686 ) the protocol is the same or similar f...

My memory is a bit vague, but I think I remember discussions about input being handled by SDL2. Maybe try looking there?

Well, I still have the problem with SB16, perhaps am I using some wrong dll? corrupt MSYS2 environment? somewhat missing? :roll: Could anyone with a successful compilation under MSYS2 upload somewhere its pcem.exe + all dll files please? even the full src folder with the good Makefile will be usefu...

These instructions are in an incorrect order: $ ./configure --enable-networking --enable-release-build $ autoreconf $ mingw32-make -j autoreconf (preferably with the -i parameter), comes before the ./configure line, as basically autoreconf will regenerate the configure script. And this is incorrect...

This looks like it could be an MSYS2 problem. Or maybe the specific libraries used. I did a fresh recompile with MSYS2, and got the same problem. (Crashes with SB16, but doesn't with no sound card) I then dusted off my TDM-GCC-32 installation and compiled PCem. It starts without any issue at all, us...

It turns out that base-devel is what's required for autoreconf. I have updated the guide for this.

And it turns out when I did a fresh compilation from scratch, it broke PCem, like ruben_balea is having.

Did you try and run autoreconf? before compilation?

I have no issue with the emulator crashing with SB16/AWE32 enabled. Running 98SE guest.

Hi all,

I've updated the guide for (hopefully) working steps to compile new revisions, especially those that have an updated Makefile.am

SarahWalker wrote: ↑Mon 12 Feb, 2018 9:47 pm Run autoreconf.

Thanks for that tip Sarah. I wasn't quite sure what needed to happen when the Makefile.am was altered. I shall update the MSYS2 instructions accordingly.

Hi all,

The guide has been streamlined and updated now that autotools can be used to configure and make PCem in MSYS2.

Please let me know if you have any problems.

Yeah, if you want speed, MSYS2 is not the way to go. It is however far more convenient to get started. All the libraries and headers required (except for pcap headers) are available from the MSYS2 repository. There is no need to try and figure out which files go where, especially with wxWidgets. Als...

The handmade Makefiles I was using with MSYS2 was almost as slow from my experience.

Also with mingw32-make, I believe its better to explicitly set -j <n>.

Although I just started a compilation and checked task manager and oh my, I see what you mean by Windows Defender!

Seems to work fine for me on MSYS2 32 bit, and Manjaro linux (64-bit). I don't think it will work on legacy MSYS/MinGW, simply due to the fact it does not have WX available as a package. Therefore wx-config is not available in this environment. It could probably be made to work with some effort, but...

Looking good so far! Everything works fine in Msys2 32bit. Configures and makes correctly (or at least appears to anyway!). I tried to compile in 64-bit mode, and it failed. Nothing wrong as such, I forgot to add the pcap headers for networking. Perhaps we should check for pcap during configure time...

Redefining MAKE is useful if using an environment where 'make' is not installed, but 'mingw32-make' is. Otherwise running mingw32-make fails when the Makefile itself tries to call make. Setting it on the command line when running ./configure does appear to work, if you don't want to change configure...

Ok, done some poking around and it looks like the configured Makefile is missing the WX resource files, which explains the lack of icons and themes. Also, most of the literature I've seen states that in a MinGW environment, the WX libraries should be linked before the other libraries. I'm going to s...

Yay! Getting closer! First, I got it to compile using mingw32-make. There is a bit of an issue with the WX stuff. The main config window does not appear to use styling, so the appearance is flat and ugly. Also there is no icon embedded in the executable. Both of these are non-issues with the predefi...

Ok, I now understand what has happened. MSYS2 has two (or three if one is being pedantic...) distinct build environments. It has the MinGW-w64 environments (32 and 64 bit), and it has the MSYS2 build environment. The MinGW-w64 build environment has its own distinct version of make (mingw32-make), gc...