I believe your driver is asking for a SCSI card in this case, especially that atapi wasn't a thing in 1993. There were sound cards with Mitsumi and/or Sony interfaces or IDE+Mitsumi+Sony or any other combination. Mitsumi used the same 40 pin cable as IDE but different pinout, very incompatible, lik...

Windows 95 RTM takes only 36.2MB with DirectX 6 installed Win95B+DX6.png And goes to 44.6MB after installing DirectX 7 Win95B+DX7.png DirectX 6 is enough (it's the version included on the game CD) to play Commandos: Behind Enemy Lines Win95B+DX6+Commandos1-BEL.jpg Steps were installing MS-DOS 5.00, ...

Windows 95 can be really small removing (not installing) most useless (for gaming) things, I think that can be done only by upgrading from 3.x and using Windows 95 floppy release but I will take a look. I did it 25 years ago to use it on a 40MB hard drive.

I guess that DOSBox can throw data to guest programs almost as fast as the host OS can read it from disk drive while PCem has to emulate the BIOS calls, interrupts, DMA transfers and all those things at speeds acording to the emulated machine.

I never liked FPS so I don't know much about Duke Nukem 3D and I killed my first Windows 98 installation with FAT32 in a few days, then to not have to deal again with data corruption due to some incompatible disk utilities I installed a secondary hard disk with MS-DOS 6.22 and Windows 3.1 on my comp...

Correction: In MS-DOS it is the Windows 3.x setup that enables SMARTDRV, not the MS-DOS setup. I just tested it with Windows 3.1 and MS-DOS 5.00 but I guess that Windows 3.0 and MS-DOS 4.0/4.01 did the same.

:o Since late 80s I have never seen an MS-DOS installation without SMARTDRV and definitelly all systems capable to run Duke Nukem 3D had SMARTDRV loaded by default... :arrow: For those too young (Windows 95+ users) installing MS-DOS isn't just taking a Windosws 9x boot floppy and running fdisk and f...

That seems to happen only on ali1429 machines :arrow: Format fails sometimes on MR386DX too so I guess it can fail on any machine under appropriate circumstances, which of course I am unaware of. Also after wiping an old image with hex editor I found that when image file is filled with 0xFF instead...

That seems to happen only on ali1429 machines

Keyboard works fine also on Windows 95, 98, 98SE and ME. Tested on a few systems from AMI WinBIOS to FIC VA-503+ and also on MR386DX clone using Cx486DLC/25 CPU and 64MB of RAM and plain VGA :!: Windows ME command prompt has always US layout and I don't know how to change it permanently but keyb.com...

OK, on PC/XT systems using keybsp.com from DOS 3.20 (on DOS 6.22 with setver.exe) instead of keyb.com everything works fine execept ">" and "<" which were moved from key 43 to key 45 and new key 43 is "RETURN" which of course works as expected so ">" and "<" symbols are missing.

Tested using MS-DOS 6.22 3.5" 720KB boot floppy with the following configuration: CONFIG.SYS: device=display.sys con=(ega,,1) country=034,850,country.sys AUTOEXEC.BAT mode con codepage prepare=((850) ega.cpi) mode con codepage select=850 KEYB SP,,KEYBOARD.SYS Testing results: Already converted from ...

Those are the differences between UK and SP keyboards: And now I'll do some tests on MS-DOS 6.22 with KEYB SP on various machines...

Yes, give me a bit of googling time to see where keys are placed on UK keyboards

Hi Sarah, did you tested it on a few machines? Because on some it works fine and on others it doesn't work at all. I'd posted my test results for v11 and v15 on a lot of machines: :!: It seems that forum links are now disabled or not working, at least for me... [url] http://pcem-emulator.co.uk/phpBB...

Yes, TASM is very fussy. I don't know a lot of assembler, just enough to understand not too complex code and write very simple programs.

Hmmm, a program with 386-instructions (" .386" at the beginning) running/testing on (e.g.) a NEC V20 or a 286? But you can take cpulevel from FreeDOS, public domain by Eric Auer 2004-2008. It only uses 386 instructions on 386 and higher CPUs and CPULEVEL does exactly the same. .386 was there only t...

This other program can tell the very exact CPU including bus width: ; ******************************************************************** ; * * ; * CPU v2.2 (c) Septiembre 1992 CiriSOFT * ; * (c) Grupo Universitario de Informática - Valladolid * ; * * ; * Este programa determina el tipo de micropro...

Hi, That TSR seems to be some kind of loader and then a plain 32KB BIOS image with the correct checksum, if it works better I guess it could be extracted and used in place of the original ROM to save the base memory wasted by the TSR. :arrow: Edit: That TSR contains a BIOS image without correct chec...

Try the AVGA2 drivers or even loading in autoexec.bat the Cirrus Logic TSR BIOS 1.2 which may include some fixes, I don't know if it can help for Windows 3.x drivers. It seems to provide VESA 1.02 extensions and make the card working as a Cirrus Logic GD5420 on Windows 9x. But I haven't tried anythi...

Some PS/1 2133 emulation is already implemented in https://github.com/86Box/86Box but please read this post before: viewtopic.php?f=2&t=502

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