VOGONS

Common searches


Search results

Display options

Re: Problem with Powerslave on Windows 10

the Runtime Error 200 occurs when DOSBox auto-switches to dynamic core on default settings. That error may occur with dynamic core, but it depends on the host processor. There is one piece of game code that uses specific flag behavior of multiply instructions that often exists in legacy processors. …

Re: Speedy3D support in DOSBox

It's hard to know exactly what you refer to: IRQ or INT. FYI, IRQ numbers are generally noted in decimal, INT numbers in hex. EGA cards (and apparently a very few VGA cards) generate IRQ 9 on vertical retrace, which is INT 0x71, and the BIOS handler for that interrupt calls INT 0x0A (cascade from …

Re: Speedy3D support in DOSBox

The C800-CFFF segment range is implemented as RAM for the emulated DOS private area. The internal mouse driver INT 33h handler is there and can be corrupted by errant programs. At C7FF:0010 an EB (short jump) appears to have been somehow changed to FF in your example.

Re: Speedy3D support in DOSBox

You seem to have the stack order backwards: a push subtracts from SP, a pop adds to SP, so the flags are at SP+4 for code inside an interrupt handler. Anyway, in cpu/callback.cpp are a few functions: CALLBACK_SZF, CALLBACK_SCF, and CALLBACK_SIF for setting the Z, C, and I flags on the return stack. …

Re: MULE386 does not draw certain screens

On the main menu, the "configure hardware" option has 4 keyboard icons -- presumably keys for each player, and the "button" key for player 1 is "S" by default, so press that. ;) BTW, the game is using a register-tweaked variant of video mode 13h, which seems to be why it's not compatible with the …

Re: Speedy3D support in DOSBox

Presumably there is DPMI or some DOS extender that switches to real mode for calling DOS functions. In any case, you get a handle for a device (probably a character device) by opening (INT 21/3D) its device name as if it were a file name. Note that support for loaded device drivers (e.g., DEVICE= …

Re: Speedy3D support in DOSBox

FYI, segment 0xF000 is the system BIOS region, segment 0xC000 is the video BIOS region (for EGA/VGA). Use phys_write to write to BIOS (read-only) regions, because mem_write cannot. Perhaps this was your intent: Copy code to clipboard 1 phys_writed(PhysMake(0xF000, 0x09FC), 0x00000079);

Re: swapping CDs in a physical CD ROM drive

FYI, in addition to swapping mounted images, Control-F4 also rescans drives (by discarding the cached directory contents), so that may have been the solution after inserting a different disc in the physical optical drive. Rescanning isn't necessary when switching disks with physical floppy drives …

Re: Lunicus, DosBox 0.74, Win3.1

Perhaps I have a different version of the game, as it appears to work fine in 0.74 and SVN with Windows 3.1 or 3.11 enhanced mode with Win32s installed. I saw no mention of SHARE during installation. However, there are paging access errors with the default CPU type (the infamous "Unexpected DOS …

Page 1 of 195