Search found 15 matches
- Fri 20 Nov, 2020 5:25 am
- Forum: General
- Topic: Frogger 2 Swampy's revenge fatals PCem on Voodoo 2 and earlier
- Replies: 0
- Views: 3156
Frogger 2 Swampy's revenge fatals PCem on Voodoo 2 and earlier
It outputs a log that shows "voodoo_readl : bad addr 00003E24".
- Fri 20 Nov, 2020 1:33 am
- Forum: General
- Topic: MAPEDIT 8.x lowers title bar percent a lot
- Replies: 0
- Views: 3364
MAPEDIT 8.x lowers title bar percent a lot
Since PCem v15 (so new recompiler), MAPEDIT 8.x (best WOLF3D map editor for DOS) has been making the emulator run at like 15%, 30% at most. It used to run always at 100% on v14 (old recompiler).
- Wed 18 Nov, 2020 5:31 pm
- Forum: General
- Topic: Voodoo bugs
- Replies: 2
- Views: 2425
Re: Voodoo bugs
There is also some code difference in voodoo_writew. Old: if (addr == voodoo->last_write_addr+4) cycles -= voodoo->burst_time; else cycles -= voodoo->write_time; voodoo->last_write_addr = addr; New: cycles -= voodoo->write_time; But I am not sure if this is the cause of Voodoo 2 SLI not being detect...
- Wed 18 Nov, 2020 5:03 pm
- Forum: General
- Topic: Voodoo bugs
- Replies: 2
- Views: 2425
Voodoo bugs
The first bug is, in tex_write_l (voodoo_texture.c), there are checks for type >= BANSHEE in a (type < BANSHEE) if block. The second bug is, Voodoo 2 SLI is now broken - the drivers (and Quake 2 for DOS) say that Voodoo 2 SLI is not detected. It was working fine before all the big Voodoo changes. Th...
- Sun 23 Aug, 2020 7:31 pm
- Forum: Development
- Topic: Amstrad PC5086 emulation work in progress
- Replies: 3
- Views: 3072
Re: Amstrad PC5086 emulation work in progress
I would be very interested in the preliminary patch and that I know, it is not forbidden to publish it on the forum.
- Wed 19 Feb, 2020 10:07 pm
- Forum: Merged patches
- Topic: [Patch] Aztech Sound Cards
- Replies: 26
- Views: 30371
Re: [Patch] Aztech Sound Cards
This appers to be licensed using GPL v3 while PCem is GPL v2, though GPL v2 allows for a "GPL v2 or later" clause that makes it compatible but since the code files have no header, what is the license PCem should be considered to be under? GPL 2 or GPL 2+ ("v2 or later")?
- Mon 03 Feb, 2020 5:26 pm
- Forum: General
- Topic: Matrox Mystique Windows 95/98 driver hang
- Replies: 4
- Views: 4808
Re: Matrox Mystique Windows 95/98 driver hang
After I made bit 3 settable on PCI register 7 (the Bus Master bit) as the Developer Specification says it should be, Window 95 now gives different errors on other chipsets (while still working on 430FX). Now it tries to do an iload_high in 32BGR mode (that code lacks a define for), I implemented tha...
- Sat 25 Jan, 2020 5:33 am
- Forum: General
- Topic: File x87_timings.h is missing
- Replies: 4
- Views: 4494
File x87_timings.h is missing
I am unable to compile PCem because of that.
- Thu 23 Jan, 2020 1:42 am
- Forum: General
- Topic: Matrox Mystique Windows 95/98 driver hang
- Replies: 4
- Views: 4808
Re: Matrox Mystique Windows 95/98 driver hang
Doing more test, it appears the Matrox driver is being smart and enabling/disabling features depending on what chipset it detects it is on. It will do DMA on 430VX but not on 430FX.
- Tue 21 Jan, 2020 3:59 am
- Forum: General
- Topic: Matrox Mystique Windows 95/98 driver hang
- Replies: 4
- Views: 4808
Re: Matrox Mystique Windows 95/98 driver hang
I looked at the code and it appears the machine I was attempting this on (the Shuttle) uses a 430VX chipset, it works on the ZP which has 430FX. For an experiment, I simply changed the 430VX's ID to that of 430FX, and the Matrox driver worked without issue on the other machine, so it appears to be W...
- Mon 20 Jan, 2020 5:31 am
- Forum: General
- Topic: Matrox Mystique Windows 95/98 driver hang
- Replies: 4
- Views: 4808
Matrox Mystique Windows 95/98 driver hang
This is the driver version 4.12.013 from the Matrox website. It says Windows 98 on the website but the driver installs on WIndows 95 and talks about Windows 95 in the Readme. After installing correctly, it hangs PCem because it uses the following unimplemented features (discovered by attempting a fi...
- Tue 14 Jan, 2020 9:54 pm
- Forum: General
- Topic: Bug in codegen_backend_x86_ops.c
- Replies: 1
- Views: 2783
Bug in codegen_backend_x86_ops.c
The bug occurs in this function: void host_x86_MOV32_STACK_IMM(codeblock_t *block, int32_t offset, uint32_t imm_data) { if (!offset) { codegen_alloc_bytes(block, 7); codegen_addbyte3(block, 0xc7, 0x04, 0x24); /*MOV [ESP], imm_data*/ codegen_addlong(block, imm_data); } else if (offset >= -80 || offse...
- Tue 03 Sep, 2019 12:57 am
- Forum: Patches
- Topic: [Patch] Dell Dimension XPS 466V & Dell Dimension XPS 4100V
- Replies: 10
- Views: 16244
Re: [Patch] Dell Dimension XPS 466V & Dell Dimension XPS 4100V
The labels are in the way of proper identification but the chips do not appear to be something already emulated.
- Wed 03 Jul, 2019 10:21 pm
- Forum: Development
- Topic: [Sep 2020 ed.] PCem MSYS2 build guide (with wxWidgets)
- Replies: 84
- Views: 117798
Re: [Feb 2018 ed.] PCem MSYS2 build guide (with wxWidgets)
Try to compile using the mingw make file, it appears to compile with slightly different keyboard input code than if I use configure.
- Mon 01 Jul, 2019 12:57 pm
- Forum: General
- Topic: [BUG] International keyboard layouts
- Replies: 8
- Views: 10366
Re: [BUG] International keyboard layouts
If you are on Windows, v12 introduced the closs platform UI. Maybe that affected it?