basic2004, have you though of applying the patch to add support for EGA and VGA monochrome displays yet? It would be awesome to add support!

Great work on the memory settings patch! Can this setting be applied to 286, 386 and 386SX clones? I know for a fact that the IBM PS/1 Model 2011 started out with 512 KB of base memory. Yes. I've just added if AT machines granularity value less than 128, consider memory size is MB and greater or eq...

Great work on the memory settings patch!

Can this setting be applied to 286, 386 and 386SX clones? I know for a fact that the IBM PS/1 Model 2011 started out with 512 KB of base memory.

I don't, but Sarah clearly pointed the issue in her last post. Yes, because DOS is idling waiting for the IDE transfer to complete. It's not the disk IO that causes the slowdown, it's the CPU emulation of the DOS idle loop that causes the slowdown. I can only test and measure from the outside, but ...

I've created an RAM disk using XMSDSK to remove the HDD emulation completely out of the way, and indeed playing games from this ram disk is now as smooth as DOSBox or my hardware Pentium PC. It is obviously your choice to completely ignore that issue SarahWalker, but I think you should at least ack...

Hang on, I remember this now. There's a bit in the CMOS RAM of the 55SX that prevents it from booting from hard disc, and isn't exposed through the reference disc. I've committed default NVR files for all of the PS/2 models in rev 718 - use the file in that commit as a starting point and it should ...

The Wikipedia article on the PS/2 states that the Model 55SX has support for the ESDI controller while the Model 50 doesn't. The Model 50 has to rely on HDD controllers other than ESDI. IMHO, if Wikipedia says that, then it's wrong on this one. AFAIK, both model 50 and 55 (and 70) can support "...

> I bet that the inability to boot from the ESDI hard disk also affects the emulated IBM PS/2 Model 50 and IBM PS/2 Model 80 as well, but those machines have not been tested at this time. Note that the ESDI controller in model 80 is very different and incompatible with that in models 50 and 55. Eep...

I'm having a problem with the emulated IBM PS/2 Model 55SX is that I can't boot from the ESDI hard disk. Instead, the emulated machine goes to ROM BASIC: PS2M55SX_ROM_BASIC.png I have the IBM ESDI Fixed Disk Adapter enabled and the hard disk geometry for the boot drive is 615 cylinders, 8 heads and ...

I have made modifications to the @DDFF.ADF file to add support for specific adapter memory locations for the IBM ESDI Fixed Disk Adapter. The English version of the file can be download here:

I would like to this feature request! I currently have a 512 MB, 1 GB and 2 GB flash drive formatted as a FAT partition, a 1 GB and 2 GB compact flash and a 2 GB SD card that can be used to run under MS-DOS/Windows 95. I suspect reading from a FAT32 host would be much easier to implement FAT32 is a...

I would like to this feature request!

I currently have a 512 MB, 1 GB and 2 GB flash drive formatted as a FAT partition, a 1 GB and 2 GB compact flash and a 2 GB SD card that can be used to run under MS-DOS/Windows 95.

HIMEM.SYS issues fixed in rev 716. I'm still not sure what chipset is being used here; it's apparently a Chips & Technology one, but the BIOS doesn't access any of the NEAT or SCAT ports. I suspect it might be a CS8220 with some custom stuff on top, but as that doesn't define any registers it d...

:?: Maybe I should have put all this on another topic? If so please sorry for not thinking about it before... :oops: On next days I will look for some 286 protected mode software to test directly in DOS and within Windows 3.1 to see if there are other problems. BIOS may expect something non standar...

From the look of these screenhots, I believe that Windows for Workgroups 3.1 was the last to work on a 286. Windows for Workgroups 3.11 dropped Standard Mode support on all 286-based machines and required at least a 386 or better to run.

Thank you for the screenshots, btw.

What chipset does the System 200 use anyway? PCem uses the generic at_init() for it, but that may or may not be correct. I can't find any information regarding what chipset the System 200 uses. I'll have to do a search for the Dell System 200 and the motherboard specs. I thought that the Dell Syste...

The Dell System 200 does work with Windows 3.0 and Windows 3.0a. I can only test this on PCem right now. Does Windows 3.0 run in real or protected mode? What happens when you run "win /r" and "win /s"? Did you check if HIMEM.SYS from Windows 3.0 works? Windows 3.0 runs in Standa...

The Dell System 200 does work with MS-DOS 3.31/MS-DOS 4.0x. Does it work with Windows 3.1? Does it work with any protected mode software at all? If not and it can't be repaired then really there is not much reason to keep it, IMHO. The Dell System 200 does work with Windows 3.0 and Windows 3.0a. I ...

In my corruption incident, neither Windows nor a PCI video card were involved (ET4000AX is ISA) Earlier today, I tried to disable Win32s, but for some reason, the corruption persisted when I used CHKDSK in a MS-DOS prompt under Windows 3.1. I'm guessing that this might pin down to the use of expand...

- ppgrainbow: I wouldn't be surprised if it was caused by Win32s, as that's known to be an unstable mess. That's what I could be thinking all along. I'm using the latest version of Win32s, I will either have to: 1. Use the DR-DOS 6.0 version of CHKDSK to prevent disk from being checked inside the M...

The Dell System 200 does work with MS-DOS 3.31/MS-DOS 4.0x. I would be really shameful to permanent remove the Dell System 200 emulation.
Just not with DOS 5.0+.

- ppgrainbow: It's a bug with the specific Trident card. Why not try the Phoenix S3 Trio64 (which incidentally, also had a VLB version) and see if the same corruption happens. The Phoenix S3 Trio64 works with the AMI WinBIOS 486. :) I will ditch the Trident 8900D graphics card for the Phoenix S3 Tr...

I personally don't think that the Dell System 200 is broken and should be commented out. I can run MS-DOS 3.31 on the System 200 and then use HIMEM.SYS from MS-DOS 6.22 just fine without any A20 detection. :) It should work if I have at least 2 MB of RAM allocated to the emulated machine or if I set...

That means nothing. I am quite sure a VLB version of the TGUI9440 existed. The card is just poorly emulated right now. It is quite unclear to me how you made the logic jump from "the bug occurs on a specific card only" to "the bug occurs because the card is not compatible with ISA-on...

- ppgrainbow: More like I suspect that graphics card's (Trident TGUI 9440) BIOS is messing things up, it might be a video BIOS bug as well. Or, alternately, something in that card's code is writing out of bounds and causing other parts of the emulator to get trashed. That card is definitely not PCI...

I fixed my problem. The TGUI9440 is a PCI-based graphics card, not a ISA version. Since the AMI WinBIOS 486 is ISA-only, PCI, I had to stick with the TVGA8900D and everything works now.

I've had similar data corruption after running DOS 6.22's undelete on a 360kb floppy image (Cx486dx40 on sis496). It would freeze on the undelete and show a corrupted dir outut after restarting and chekcing the disk. Sadly I couldn't reproduce these steps =( I think that I finally solved my problem...

There is some sort of a problem getting the Trident TGUI9440UI display driver working on Windows 3.1. When I tried the 1024 x 768 x 8bpp and 1280 x 1024 x 8bpp display, the emulated screen would go blank. But when I select 800 x 600 x 8bpp, the display ends up garbled/corrupt: tgui9440.png Can anyon...

I ran Navrátil Software System Information under one of the latest revisions of PCem by typing NSSI at the MS-DOS prompt. NSSI collects information about the computer that you're running. However, this is what could be irritating me, when I exit NSSI and return to the MS-DOS prompt, massive data cor...

It looks like that something appears to be amiss with the S3 Virge 325/375 drivers. See if you can try to note SarahWalker of this issue.