VOGONS

Common searches


Search results

Display options

Re: Zork Anthology

The info in the Compatibility List is provided by users and not verified in any way, so take it with a grain of salt, particularly those entries that claim a given game is broken with no information given. That said, the Zork Anthology should work in DOSBox. Do you have the floppy or CD-ROM version? …

Re: CHiLL XL enclosure

A grille of ventilation holes above the voltage regulator on the interface would be great, as it can get quite hot. Even better would be standoff feet and a lower grille as well. With that kind of passive convective cooling you could stack multiple enclosures with less concern, but it may be asking …

Re: MASM vs NASM

Can probably use more common mnemonic instead of array: inc word ds:[bx+data], or possibly: inc word ds:[bx+offset data], just make sure the generated machine code references the correct memory. BTW, for a topic that isn't specific to DOSBox, such as this one, please post it in Milliways. That you …

Re: City Beneath the Surface

The full freeware version of the game has a bug where SETSOUND.EXE produces a SETSOUND.DAT file that is 85 bytes long, but CBS.EXE expects the file to be 86 bytes long and will not enable sound if the file is smaller. I can only guess how this situation came to be, but in any case there appear to be …

Re: Text wrap in Infocom games-Please help

in DOS
Frotz is a Z-Machine interpreter, and there is a DOS version of Frotz, so you do not really use it "instead" of DOSBox. You could use a native build of Frotz instead of a DOS-based Z-Machine interpreter running in DOSBox, though it might not seem as nostalgic. As for the text wrapping, it certainly …

Re: pentium_fast \ cpu type?

The 586 executables do run with cputype=auto, and the only instance of CPUID appears to be in the DOS4GW extender. I found a few instances of RDTSC in one subroutine in TACP.EXE (tactical), but not in UFO2P.EXE (cityscape), and no other Pentium-only instructions. So, other than the case of RDTSC, I …

Re: pentium_fast \ cpu type?

I feel like this discussion is over with judging from ripsaw8080's second reply Regarding your assertion that the 586-specific executables are less buggy than the 486-specific executables; I can neither confirm nor deny. Therefore your point remains about being able to use the 586-specific …

Re: pentium_fast \ cpu type?

I see no indications of "weird" installs. The only files that differ in installs with cputype=auto and cputype=pentium_slow are the UFO2P.EXE and TACP.EXE executable, and they are correctly copied from the CD image. Going by which files get copied, UFO2P4.EXE and TACP4.EXE on the CD are the 486 …

Re: pentium_fast \ cpu type?

AFAIK, the only difference for 486 vs. 586 is different UFO2P.EXE and TACP.EXE executables. While that is a quite significant thing, I just want to be specific because you were a bit vague about what is different. Are you looking for better operation, meaning less bugs, from the 586-specific …

Re: Crashing DosBox.

First, and most important: DOSBox emulates MS-DOS 5/6, so it does not support the /P parameter on the SET command. If you are using an SVN build then you will get an error exit (not a "crash") when you try to use a /P parameter with the SET command, and in the console window you will see this …

Page 1 of 179