VOGONS

Search

Common searches

Search results

Display options

Display options

Re: 0.62

Posted on 2004-10-01, 09:40

in DOSBox General
1) does happen as well with a different SDL ? which output did you select ? Yes, it also happens with the SDL provided with DOSBox 0.61 (which, as reported, solves the Ctrl-F1 crash). I used dosbox.conf "out of the box" as it comes with Windows installer, so no special output settings. 3) example ? …

Re: AMD64/x86_64 Solution

Posted on 2004-09-30, 09:28

Just a thought: This code requires that the memory addresses be allocated from low values to high values ( cpos-shortname). If I remember my assemby class, I think there were some architectures that do it from High to Low (shortname-cpos). Is that right? Or do all systems go from low to high? You …

Re: 0.62

Posted on 2004-09-30, 09:07

in DOSBox General
1) Full-screen mode crashes when VGA switches to 720 pixel mode, or when switching to full-screen mode when in 720 pixel mode (segmentation fault) 2) Ctrl-F1 crashes (segmentation fault) 3) User definable characters are not displayed at all (in 0.61 they were displayed as "normal" characters) So far …

Re: AMD64/x86_64 Solution

Posted on 2004-09-27, 10:28

Looking at the msdn libary and __int64, I found it strange that there is no unsinged version. Is it possible to declare an "unsigned __int64"? Yes, it is. To display __int64s with stdio, "%I64" is used as a prefix, like printf ("signed: %I64d, unsigned: %I64u", val1, val2); No doubt this isn't …

Re: AMD64/x86_64 Solution

Posted on 2004-09-24, 08:18

int == 64 and long == 32 on windows? That doesnt sound right. Why would a int be larger than a long int? That doesn't sound right indeed. My memory got me confused :). One of the articles I read around the first time 64-bits got interesting was http://www.microsoft.com/msj/0798/hood0798.aspx Win64 …

Re: AMD64/x86_64 Solution

Posted on 2004-09-23, 10:39

"case 32:*(Bit32u*)dst=val;dst+=4;break;" Problem is Bit32u is not 32 bits. Therefore adding 4 is wrong. (maybe adding by sizeof(Bit32u) would be better/safer?) You could of course let the compiler do that for you, and write ((Bit32u *)dst)++; On a 64 bit system, unsinged long is 64 bits. to fix …

Re: Using COM ports with DOSBOX

Posted on 2004-09-23, 10:20

in DOSBox General
There is another free DOS emulator that is a little bit more tricky to configure but it has functionallity for COM and LPT. http://bochs.sourceforge.net/ Bochs isn't a DOS emulator - it's a complete PC emulator. And it isn't "a little bit more tricky", but much more tricky, and it requires a copy …

Re: Ugly Glitch

Posted on 2004-08-27, 07:04

in DOSBox General
Just reporting I get ugly stuff flashing at top/bottom of my screen when playing certain games such as Biomenace, Keen 6 and Prince Of persia. This only happens in OpenGL mode with fullfixed=true, fullwidth=0, fullheight=0 (1024x768 here) and no matter the scaler. Any help?. Try upgrading your …

Re: FM synthesis

Posted on 2004-08-04, 06:57

in DOSBox General
Zorbid wrote: The next version will also support OPL3 FM synthesis (SB16), which is of course better than OPL2 (SB, Adlib). It is, although not many games have used it, since programming information was very scarse at the time, and a little later the GUS emerged which had superior sound quality. …

Re: FM synthesis

Posted on 2004-08-03, 14:51

in DOSBox General
Please, make a soundblaster FM synthesis in some next version, because some games doesnt support General Midi and adlib sounds so bad :( Errr... Can you explain what you mean? DOSbox emulates General Midi, Adlib and Soundblaster. "FM synthesis" is what the Adlib does to produce sound (and what …

Re: Screen wraps around

Posted on 2004-08-02, 11:18

in DOSBox General
As I understand it, DOSBox uses OpenGL to display the screen. It seems likely you have an OpenGL problem, although I have no explenation why it should happen only with Sierra Games. Is it possible you submit a screendump of a DOSBox window running a Sierra game having this problem? JAL

Re: Pirates! Gold

Posted on 2004-07-01, 15:33

I guess these old dos games just dont know what to do with themselves for all that extra memory :money: It's a typical bug, found in many old programs: when checking the amount of memory, the programs store the # of free KB's in a 16-bit integer, which can hold numbers up to 65535. When having > 64 …

Re: Improving with internal command ATTRIB

Posted on 2004-05-26, 06:44

While my suggestion is a *hack*, your idea is an *uggly hack*. The beauty of .ATTRIBS:DB is No filename in DOS can include a ':' A dot-directory does usually not show up in file listsing, etc. Adding filename postfixes looks messy.... Well, that's a matter of taste, I think. There's no 'beauty' in …

Re: Improving with internal command ATTRIB

Posted on 2004-05-25, 08:37

The only *hack* I can think of is to use a file with a non-DOS name (e.g. a file called .ATTRIBS:DB) inside each DOSBox directory. The .ATTRIBS:DB file could then be used by DOSBox to read/write/emulate the DOS attributes. I just thought of another hack: attach the attributes to the filenames, but …

Re: Improving with internal command ATTRIB

Posted on 2004-05-24, 13:35

This is normal. Well, I wouldn't call it quite normal. It is true that DOSBox should be runnable on multiple systems, but many users will run it on a Windows platform, on which the 'original' attributes like 'hidden' and 'system' are available. It shouldn't be to much of a problem to add this in …

Re: Anti-debugging, whatever, code in older games...?

Posted on 2004-05-18, 11:19

in DOSBox General
Some of the old stuff could rely on self modifying code in certain ways that tricked the prefetch queue into executing code in the queue rather than what was in ram at the time That might have been the case, but on a 8086 the prefetch queue is 4 bytes, and there's no cache, so it would have to …

Re: Tocuhe...

Posted on 2004-05-10, 11:31

2. Open TOUCHE.EXE in any HEX-editor, go to offset 0x17ED4 (17ED4h) and replace "75" with "EB". SAVE FILE. 75 is a JNE instruction (jump if not equal), EB a JMP instruction (unconditional jump). Of course there's no way to tell what was tested by the JNE without further investigation of the …

Re: Out of Memory Error

Posted on 2004-05-06, 08:38

in DOSBox General
There used to be programs like mark/release that allowed you to deal with such programs (and even TSRs). Here: http://www.nfbnet.org/download/memory.htm you can find a number of memory-related tools. Take a look at TSRCOM34.ZIP, which includes mark and release. I haven't tested whether they work …

Page 24 of 27

Go to top of page Go to top of page
Close window
Close window