Re: Mouse causes screen distortions in Spellcasting 101 (Lack of refresh?)
Posted on 2024-04-23, 07:50
Maybe adding the XMOUSE parameter to your command line helps: S101 XMOUSE
Re: Text modes with more than 25 lines and the internal ANSI support
Posted on 2024-04-16, 22:28
Switching from 80x25 to 80x50 only involves loading the 8-line font, which you can do with a video BIOS function: https://www.delorie.com/djgpp/doc/rbinter/id/52/1.html mov ax,1112h mov bl,0 int 10h
Re: Problem with Powerslave on Windows 10
Posted on 2024-04-11, 13:22
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
Posted on 2024-03-30, 12:36
cpu.pmode is true if in protected mode GETFLAG(VM) is non-zero if in V86 mode if in protected mode, cpu.code.big is true if 32 bit, otherwise 16 bit
Re: SHSUCDX - can't open CD driver SHSU-CDH
Posted on 2024-03-27, 18:57
Since you're mounting an ISO either way, you could do it by calling a batch file with parameters, and then you'd only need to change that one batch file depending on the system. You can also do conditional processing within batch files, such as: IF EXISTS Z:\COMMAND.COM GOTO DOSBOX
Re: SHSUCDX - can't open CD driver SHSU-CDH
Posted on 2024-03-27, 17:52
Device drivers aren't supported by the DOS emulation. You can boot real DOS in DOSBox, but then your ISO file will have to be contained on an HDD image. Why not use IMGMOUNT to mount the ISO directly? DOSBox internally emulates a CD-ROM device driver and MSCDEX, so there's no need to load them.
Re: Speedy3D support in DOSBox
Posted on 2024-03-15, 13:10
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
Posted on 2024-03-10, 10:50
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
Posted on 2024-02-27, 14:31
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
Posted on 2024-02-21, 18:12
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: MULE386 does not draw certain screens
Posted on 2024-02-21, 17:25
Try with machine=svga_et4000 On the player review screen press left/right to select a character, then up and left/right to select a color, after which pressing Return should proceed.
Re: Speedy3D support in DOSBox
Posted on 2024-02-20, 20:25
The handler is in bios.cpp, but that call appears to be for PCI BIOS: https://www.delorie.com/djgpp/doc/rbinter/ix/1A/B1.html
Re: MOO2 - Ran fine for weeks, suddenly started having stuttering problems
Posted on 2024-02-17, 16:59
Make sure you are not enabling vsync in the Nvidia settings, as it is known to cause stuttering with opengl output.
Re: Speedy3D support in DOSBox
Posted on 2024-02-10, 14:40
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
Posted on 2024-02-08, 15:13
Perhaps 16 is hexadecimal? If so, bit 22 (decimal) refers to the D/B (Default operand size/Big) bit from the segment descriptor: 0=16-bit, 1=32-bit, and in your example the bit is set.
Re: Speedy3D support in DOSBox
Posted on 2024-02-07, 15:31
LEA calculates an address and doesn't access memory.
Re: Speedy3D support in DOSBox
Posted on 2024-01-06, 05:17
Video BIOS is at C000:0000, linear address 0xC00000. My example with PhysMake was based on real mode segment and offset for the system BIOS. Perhaps the apps you are looking at use protected mode, and thus reference 32-bit offsets within a descriptor.
Re: Speedy3D support in DOSBox
Posted on 2023-12-10, 00:40
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: Speedy3D support in DOSBox
Posted on 2023-12-06, 07:26
Make sure you are using the core=normal setting, as the instruction pointer skipping around could be due to the dynamic core that executes blocks of instructions where the debugger can only be active between blocks.
Re: swapping CDs in a physical CD ROM drive
Posted on 2023-11-28, 05:18
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 …
Page 1 of 195