Donald Duck Goin' Quackers (NTSC/PAL) -> with 3dfx, just black screens (not driver-related, since I've tried every 3dfx Voodoo1 driver for Windows 9x) once it proceeds examining the resolutions, so, not working at all.

well, I'm adding them alone

Since NT 3.1 doesn't have any built-in atapi support, I (actually we, Battler too) would like to have other storage driver (in terms of modifying the source code of the emulator) support for cdrom for NT 3.1 (you can get NT 3.1's iso on google, just search, either floppy or CD versions) for PCem, si...

Tseng ET4000AX drivers for win3.1 (they work on 3.0).

Well that game works perfectly under WinXP on VMware, but I thought of testing it on a Windows 95/98/ME guest on PCem would be quite retro :p It originally came out in 2000 (between the releases of Windows 2000 and Windows ME to be precise) but also designed to work on Windows 95 and Windows 98 (inc...

Have you guys tried Donald Duck Goin' Quackers for Windows 9x? It requires a Voodoo1 as a minimum 3D card but here it just stays black after initializing the resolutions (on PCem that is).

both drivers, and actually, the glitch doesn't always appear, it mainly appears when moving the open program or window to the borders of the screen. (And for some info, this glitch is totally absent in the trio64).

These are slight minor glitches but can also be annoying for proper visualization, and I'm asking if they can be fixed :) Emulated specs: Machine emulated: 430VX PCI Video card: S3 ViRGE/DX (375) PCI (everything from its config enabled) (1024x768x24bpp but happens in any video mode from 8bpp to 24bp...

Update: seems to be also related to the read 10 (0x28) command and on the ioctl_readsector function on cdrom-ioctl.c

Alegend45 wrote:Holy shit UltraHLE in a PC emulator. That's funny.

Correction, it is a N64 emulator for PC.

Every time I start some cdaudio testing on win95 (original release from 1995), it just skips all the tracks (any audio cd, but mixed mode ones work fine) and doesn't play audio from the cdplayer (or any other cdplayer). This problem doesn't happen at all on OSR2 or later or on NT or on Win3.x. Testi...

Config:

Award 430VX, cpus set to Pentium (MMX and non-MMX count and variable Mhz), S3 Trio64, SB16, ram set to around 128-256MB.

recompiler actually

It's typically in C:\windows

nerd73 wrote:

SA1988 wrote:it actually works, it's the "CombineVXD" in wininit.ini that got broken in these revs.

Is wininit.ini a text file?

it is.

it actually works, it's the "CombineVXD" in wininit.ini that got broken in these revs.

one of the main reasons to migrate to PCem for legacy operating systems

well 43hz is required for the interlaced 1024x768x32bpp for the S3 Trio32/64 and S3 Vision864.

this also happens on Win3.1, especially in Minesweeper and Calculator.

my biggest problem with my ne2000 patch is a configurable mac address, I just don't know how to make it configurable from within the cfg file (and as a conseguence of not knowing much about C and in win-config.c)

my ne2000 patch is not based on qemu's anymore.

well yes, I forgot, I have tested it on the Award 430VX, AMI 486 clones as well as the Award 486 one (Award 496/497), IBM AT (interpreter), AMI 286 and others (including AMI 386) and cdaudio is re-enabled.

With this patch, I don't encounter any checksum errors in the Advanced/EV machine.

Here's the patch. https://mega.co.nz/#!ARFXHQKa!XdnpkVcVYa489jSRYJdL5lqun0QT1jt6g3Ha6aS-93A Note: ignore the network adapter stuff I put, the important ones are in the following sections of the patch: @@ -238,6 +240,19 @@ void initpc() @@ -542,7 +546,6 @@ int WINAPI WinMain (HINSTANCE hThisInsta

startmenu wrote:The dynamic recompiler enabled build does not run Windows 95. "IFSMGR" was mentioned on the BSoD screen.

same here

confirmed the issue occurs from rv184 and up (doesn't on 183 and earlier).

- SA1988: Most probably something just reports the wrong starting time for the first tracks to PCem. Remember, pretty much all Audio CD's start with a 2 second pause, the Red Book standard says they must, so all CD player software is most probably designed to skip those 2 seconds. Most probably whe...

same thing happens.

Although the readme says that it has bugs, some basic functions of the cdaudio handling are still buggy, especially when it first plays a song (it plays 1 or 2 seconds late than normal, therefore, skipping the first 2 seconds of the song) and sometimes won't play at all (both on DOS and Windows; for...

Windows9xFan wrote:

SA1988 wrote:he has no interest for beta releases.

But IIRC you created a patch to make PCem not to use the host OS date/time.

true, but most likely won't be merged into the upstream PCem on his hg site.