PCem

I'm glad it helped you! If that concerns several files it can be easier and faster to edit the Makefile instead, I noted that the provided Makefile.osx64-wx-sdl2 already has the switch -Doff64_t=__off64_t in CFLAGS variable: CFLAGS = -D__unix=1 -DPCEM_RENDER_WITH_TIMER -DPCEM_RENDER_TIMER_LOOP -Dfop...

In OS X off_t is already 64 bits so edit esdi_at.c and change the code from: #include <sys/types.h> #include "ibm.h" to: #include <sys/types.h> #define off64_t off_t #include "ibm.h" or alternatively to: #include <sys/types.h> typedef off_t off64_t; #include "ibm.h" ...and try to compile again. I'm ...

I didn't have any major trouble to compile PCem, the worst part was to build wxWidgets, it took a lot of time because I had to use a single thread to keep the my Pi cool. That's because I'm using a Pi 3 B+ with the official touchscreen and its corresponding case without active cooling, using all cor...

Thanks shermanp, that helped but it seems that my setup is missing a lot more things to be able to cross compile... So I installed VcXsrv to try the Linux executable and it worked up to certain point: PCem with WSL and VcXsrv.png Then after starting a machine I get some errors in the console about t...

In part for fun and in part because MSYS is very slow I tried to compile PCem under the WSL and it's at least 3 times faster than MSYS. Of course I got an executable for Linux. Now I'm trying to cross compile it for Windows but I get an error about OpenAL: root@cp1:~/pcem# ./configure --host=x86_64-...

Of course, PC / XT and AT use incompatible keyboards, but I think that machines with AT and PS/2 keyboard should behave all the same. I wonder if their keyboard controllers of the AT + machines which aren't working don't have standard output and/or their BIOS performs additional processing or are se...

On 8088/8086 machines loading keyb with /E parameter to force enhanced keyboard fixes most problems except:
- Alt-GR & key #45 still missing or not working.
- Left arrows become backspace.
- Numeric '/' types '-'
- Maybe something else, I tested character keys only.

Test results of PCem v15 running MS-DOS 6.22 Spanish: FIC VA-503+ MS-DOS 6.22 SP [√] Shuttle HOT-557 MS-DOS 6.22 SP [√] Epox P55-VA MS-DOS 6.22 SP [√] ASUS P/I-P55T2P4 MS-DOS 6.22 SP [×] ASUS P/I-P55TVP4 MS-DOS 6.22 SP [×] Intel Advanced/ZP MS-DOS 6.22 SP [×] Packard Bell PB520R MS-DOS 6.22 SP [×] I...

Windows ME has the same problems under VirtualBox 6.0.8 while Windows 95 OSR 2.5 and Windows 98 SE are fine.
I'm guessing that WME does the same on real computers, after all MS was ditching DOS support with Windows ME

omarsis81 wrote: ↑

Thu 04 Jul, 2019 4:04 pm

I wonder why it mentions mingw when I use MSYS2

I guess you're using MSYS2 MinGW 32-bit. The console shows MINGW32 after your username, like: user@domain MINGW32 ~/PCemv15/src

You can't compile PCem from MSYS2 MSYS.

try to use make clean before compiling again

Try downloading https://nmap.org/npcap/dist/npcap-sdk-1.03.zip Extract all the contents of 'Include' folder into <msys installation folder>\mingw32\include and all the contents of 'Lib' folder into <msys installation folder>\mingw32\lib Edit: Yes, as jznomoney said there's the proper way to do it fr...

I was doing some research, it seems that one of the international keys has the same scancode as a different US key :? so I think PCem may have to use different scancodes according to the OS locale, at least under Windows. Then if I'm correct this isn't a PCem bug but a feature not yet implemented. T...

I will try that way right now, many thanks for the advice

That's what I did: I downloaded http://pcem-emulator.co.uk/files/PCemV15Win.zip and extracted it to C:\msys64\home\username\PCemV15Win Then I run MSYS2 MinGW 32-bit and do the following $ cd PCemV15Win $ make clean $ ./configure --enable-release-build --enable-networking $ mingw32-make -j8 Then if y...

Yes, I'm on Windows 10 x64 but with Spanish keyboard layout in PCem v11 I get also wrong/missing keys in some configurations. All tested PC and XT machines are wrong running MS-DOS 6.22 Spanish All tested AT and PS/2 machines are fine running MS-DOS 6.22 Spanish but Windows ME is even worst than in ...

There's something wrong with international keyboard layouts: incorrect, missing and duplicated keys. Recent 'keyboard_at.c' changes could have caused additional troubles ( https://pcem-emulator.co.uk/phpBB3/viewtopic.php?f=2&t=3250#p12329 ) but the strange WME behaviour was present at least since v1...

OK, I seen the updates to 'keyboard_ac.c' so I did a few more tests, KEYB SP with a PS/2 keyboard works in MS-DOS 6.22, with a XT keyboard works too but with an AT keyboard does not work. The same applies for KEYB UK but on this case seems to be wrong only the key at the left of '1' which types the ...

:roll: I've mixed the pictures while editing last topic… With KEYB UK the key at the left of '1' works as a duplicate of the key at the left of 'Z' :arrow: By the way I'm using a Spanish USB keyboard (Microsoft Wired Keyboard 600 Model 1366) on Windows 10 x64 Spanish, I'm not sure if that is relevan...

For me MS-DOS 6.22 is wrong too:
Edit: I compiled PCem five weeks ago, I will update it now and test again.
Edit 2: Only 'makefile.in' was changed since last update…
Edit 3: KEYB UK is not working 100% properly either.

I'm quite used to hte US keyboard layout, you can download a picture of that keyboard to see what key you have to press for each symbol when a KEYB command or similar is not available or not working. Please note that the backslash key located above ENTER in the US layout is placed between Left SHIFT...

No, it doesn't work correctly. Until now I thought it was fine because on Windows it was working fine... until I launched a MS-DOS session :o On Windows ME the keyboard is fine for Windows programs but for DOS programs it doesn't work. Note: KEYB command is no longer available on Windows ME, the key...

That's fine, WinHex is really useful to work with emulation related files, BIOS, disk images and so on.
I tried the 2suw001 BIOS on almost all available 286 machines without any success, perhaps it needs some feature present only on the original chipset

How did you combine both files? If you used somewaht like copy /b low.bin + high.bin out.bin that won't work because the bytes on the output file must be copied alternating one from low file and other from high file, like LHLHLHLHLHLHL... :oops: well this isn't the more scientific explanation but I ...

MSYS2 MSYS is used during setup only, to compile PCem switch to MSYS2 MinGW32

It has some kind of NVR and a clock too, the BIOS SETUP (Control+Alt+Esc) has time and date settings and says "Press ENTER-key to store information into SETUP-RAM"

With "roms folder" do you mean one copy on each machine subfolder like c:\pcem\roms\ibmxt\ide_xt.bin and so on?
Try to copy it directly to roms subfolder like c:\pcem\roms\ide_xt.bin to make it available for all machines because it's compatible with many models.

A bit of trial and error helps with those old machines

Last night while looking for another thing I found an original 256KB module from my PCS386SX and it's non parity and 2 chips type too. I was already convinced the store had not returned me those after the upgrade but it was under the bottom flap of a carton box so the other 3 may been lost by the sa...

It's interesting, I never tried non parity modules because my PCS386SX was upgraded when my Olivetti dealer was already making their own generic computers and they fitted 8x1MB Samsung parity SIMMs and really I don't know what it has before. Olivetti OEM modules could be made by Samsung too but I'd ...

Something happened with my Google Drive shares, try to download it again. Non-parity modules have an even number of chips and were used mostly on 68k machines. :arrow: All SIMM's with 3 or 9 chips have parity and should work on any x86 board, at least 256KB and 1MB ones. 4MB and 16MB may be too big ...