Hi, As stated, I have have been creating VHD support for PCem. I think I have dynamic images pretty well sorted, and I'm currently trying to get differencing support working (reading works, but I haven't got creation support yet, nor any of the parent/child integrity checks). The original VHD format...

MSYS2 is a Windows build environment Please forgive my silly question, I saw all those $ shell commands that looked like linux That's because MSYS2 is basically a stripped down linux distribution (Arch I believe) compiled to run on windows. It contains a linux shell, package manager, and all the *n...

EDIT: I deleted the contents of this post, because I realized I had made a colossal arse of myself. Turns out, the bitmap macros I was using were incorrect for VHD's (the order was reversed). This mistake will also explain why I've been having so much trouble with differencing VHD's, as they rely ex...

I mean, well, once it has installed win95 and rebooted (after the whole setup routine), for now, it's fine, but once adding one file (as little as 32kb for example) in the vhd (after closing PCem), it would result in some files (not all) missing like vwin32.vxd, etc, thus, corrupting and making win...

Your latest patch solves my issue, thanks! Edit: At least, just partially, attempting to add files from winimage or mounted through imdisk results in missing other files or corruption again. Siigh... maybe something a little less subtle is required. Are you able to provide a detailed step-by-step o...

So I went ahead and implemented some sector bitmap handling. It basically does nothing on reads, but updates the sector bitmap if required on writes. At least that's what I INTEND it to do... Whether I've done it correctly or not... I've attached a test patch, which can be applied on top of my V4 pa...

I think I can see what a potential issue MIGHT be. Unlike Windows (10) and MiniVHD, Winimage actually appears to use the sector bitmap for sparse images. This COULD lead to a potential issue where Injecting a file into the image via Winimage creates a new block with some sectors marked clean. MiniVH...

I'm going to have a closer look at this. There may be some funny business going on with Winimage. I say may, because the first thing I tried with Winimage had a problem, but subsequent uses have behaved themselves. Will try with a blank fresh VHD image to see what winimage is doing, hopefully I can ...

Just trying to narrow down whether it's a bug with my VHD code, or a bug with Winimage.

SA1988 wrote: ↑Sat 29 Dec, 2018 12:01 pm Nice patch! However, I found a bug in this patch. The bug is about when win95's first phase setup is finished, opening a dynamic/sparse vhd to view files with winimage results in a corrupt/blank vhd (with winimage).

Does this bug happen with Windows created dynamic VHD's as well?

I've updated the original guide to hopefully make it clearer that one needs to switch shells from the "Prepare and Compile PCem" step onward.

That's weird. I can't think of anything that would have fundamentally changed since I made this guide. In fact, I recently updated my own MSYS2 installation a few weeks ago. Are you using the MSYS2 MingGW shell. You should be using that, and not the MSYS2 MSYS shell. It's really strange that it's no...

Araripe wrote: ↑Tue 25 Dec, 2018 5:16 pm How do I apply the patch? I wanna test the VHD feature but I don't have a single clue on where to begin. Do I need a compiler or something?

PM sent.

Patch updated again. See this post for details => http://pcem-emulator.co.uk/phpBB3/viewtopic.php?f=4&t=3056&p=11503#p11618 As mentioned in that post, if anybody wants to assist me to try and get differencing support working, please feel free! I've basically slammed into a brick wall on that...

Unless anybody discovers any issues or bugs, I think I'm done with this. So, umm, about that.... I decided to simplify the sector read/write functions. The old "fast" path has been dropped in favor of improving the old "slow" path to be, well, not slow. Basically minimized the u...

Thanks for the update Sarah! Merry Christmas!

The biggest advantage of using a VHD in PCem to me is that I can mount the VHD in Windows and I can easily copy dos software that I downloaded from the internet to the PCem machines VHD, making transferring DOS software and games an absolute breeze, that makes getting software simple and easy as mo...

Hi, build-essential, contains the the essential tools to build any C program, and only the essentials. Basically, a compiler (GCC), make and a few other essentials. You will need to install SDL2, OpenAL, wxWidgets via your package manager. If running debian, or ubuntu, or a distribution derived from...

It doesn't appear to be a problem for me. Running Windows 10 1809. Running PCem with the following command or batch file exits PCem, and it no longer appears in the task manager when I close with the X button on the window. Have tested with both release V14, and a current development build. start /b...

This seems rather... adventurous. What would be the reason for wanting to do this, if I may ask out of curiosity? With regards to the size the PCem BIOS sees, you'll probably only have luck with sizes over 32GB using the Award 430VX BIOS. You may want to experiment setting the CHS geometry to n/16/2...

I'm starting to try it and it's been working good so far! Couldn't mount my larger VHDs beyond 32gb though :( but i'm surprised at the dynamic vhd support in this early, which is very handy for fresh setup. Yeah, unfortunately, ~32GB is the maximum size limit. More specifically, it's 65535 cylinder...

resle wrote: ↑Sat 01 Dec, 2018 7:27 pm Once again thanks, and eager to test it if a build is available.

PM sent

If Sarah is interested, I'll submit it as formal patch for inclusion upstream once the kinks have been worked out. Not especially, to be honest. The autotools system should work for almost all setups, with Ming/W being the exception. I'd rather work to fix the existing issues with the autotools set...

So, I may have decided to experiment with cmake a bit, and, um... well.... this is the result. Oops? For those who don't know what cmake is, it generates build files for a number of different build systems (eg, MAKE, Visual Studio etc.). Think of it like a cross platform alternative to the Unix auto...

I checked on my Kubuntu VM, and even without the patch, I get the MIDI selection when compiling with ALSA support. Didn't actually try using it though.

As far as MUNT is concerned, have is it set up as a Windows MIDI device?

So long as it works, yeah I will do so.

I think I found the problem for MSYS2 at least. Still not sure about your friends Linux however. Turns out Makefile.am had no instructions to build win-midi.c . Therefore, wx-sdl2-midi.c was being used, which basically provides dummy functions. This was never a problem on the bespoke platform specif...

Ok, definitely something wrong. Just compiled PCem in a freshly updated MSYS2 environment, and I'm seeing the same behavior. SB16-MIDI-msys2.png Let's see if I can figure this one out. I'm going to suspect that the issue may be with incompatibilities with a newer library version. EDIT: And now I rem...

Ummm. That's weird. Here's mine: SB16-MIDI.png SB16 on a 430VX machine. I shall try dusting off my MSYS2 installation to see what happens there. EDIT: The only other thing I can think of would be that Windows doesn't have a MIDI device "installed", but surely it would still show the defaul...

Works fine here, on the latest version. Windows 10 compile with MinGW-w64 (not MSYS/MSYS2). Windows 98 is sending MIDI to a softsynth via loopMIDI.

Ensure you are selecting a supported sound card (eg: Sound Blaster 16, AWE32 etc).