Re: Text color errors under OS X

Posted on 2017-06-05, 17:36

by

by emendelson

in DOSBox Development

in DOSBox Development

There were other things than 9-dot characters you wanted, like 512 characters. I forget the reason(s) for using the 16-bpp drawing instead of 8-bpp, but that would appear to be a crucial point in the color issue. However, what I don't understand is why it's only an issue *now*, all these years …

---

Re: Text color errors under OS X

Posted on 2017-06-05, 14:08

by

by emendelson

in DOSBox Development

in DOSBox Development

OK, I think I see where the problem is, though I haven't the faintest idea of how to solve it. In vga_draw.cpp, in order to get char9 to work, I comment out one part of the code and uncomment another part, like this: /* // emendelson comment out static Bit8u * VGA_TEXT_Draw_Line(Bitu vidstart, Bitu …

---

Re: ANSI color errors under OS X

Posted on 2017-06-05, 13:29

by

by emendelson

in DOSBox Development

in DOSBox Development

Your memory is amazingly exact. I followed the link and found a fix by applying the first of the two patches in this posting: https://sourceforge.net/p/dosbox/bugs/347/#ca16 I didn't need the second patch in the message. But what really puzzles me is this: Stock SVN, built in macOS Sierra with my …

---

Text color errors under OS X

Posted on 2017-06-05, 00:50

by

by emendelson

in DOSBox Development

in DOSBox Development

]Here is a mystery I hope someone can help me solve. I've been building DOSBox for years under both OSX/macOS and Windows (using both Visual Studio and MinGW), using a modified version of the source that owes a lot to helpful people on this forum. Recently I've tried using the same source code for …

---

Re: DOSBox for Mac: cycles=max affects directory listing?

Posted on 2017-04-29, 04:12

by

by emendelson

in DOSBox Games/Apps

in DOSBox Games/Apps

happens :) I should have thought of asking you right away... Just another proof that anything but lock stock Dosbox can introduce problems that are so low level that you cannot find them right away :) A lesson learned! The background of this is that I decided a few months ago to use the code in my …

---

Re: DOSBox for Mac: cycles=max affects directory listing?

Posted on 2017-04-28, 20:05

by

by emendelson

in DOSBox Games/Apps

in DOSBox Games/Apps

And since you are building yourself sometimes, is it with lock stock Dosbox 0.74-1, or my SVN built or any other built by you? Apologies for wasting everybody's time: The problem occurs with my own customized build, not with the build that I make with pure SVN using the OneStopDOSBox script that I …

---

Re: DOSBox for Mac: cycles=max affects directory listing?

Posted on 2017-04-28, 19:45

by

by emendelson

in DOSBox Games/Apps

in DOSBox Games/Apps

Basically the same result cycles=fixed 8177 is OK cycles=fixed 8178 produces the bug Though again, as I move up or down, I often have to run the test twice before the results are consistent. Is it significant that this number is very close to 1024*8 ?? EDIT: At 9000, around 45 files out of the full …

---

Re: DOSBox for Mac: cycles=max affects directory listing?

Posted on 2017-04-28, 18:26

by

by emendelson

in DOSBox Games/Apps

in DOSBox Games/Apps

try figuring out the limit amount of cycles before the bug happens (max 100% limit 100000) or something similar. Exact syntax in the options/preferences file. This is a MacBook Air with a 2.2 GHz i7 processor. With this line, the problem does NOT occur: cycles=max limit 8100 With this line the …

---

Re: DOSBox for Mac: cycles=max affects directory listing?

Posted on 2017-04-28, 17:49

by

by emendelson

in DOSBox Games/Apps

in DOSBox Games/Apps

and does it happen with all cores and machine types? I tried all the core= settings and the results didn't change. I didn't try all the machine types, but I tried four or five, and again the results didn't change. I also tried a few cputype= settings, again with no effect on the results. One odd …

---

Re: DOSBox for Mac: cycles=max affects directory listing?

Posted on 2017-04-28, 17:22

by

by emendelson

in DOSBox Games/Apps

in DOSBox Games/Apps

First, you are not talking about it affecting the global directory listing capability (of DOSBox itself). You are talking about it affecting some feature of some specific application that uses who knows what algorithm to do what it does. This is a big difference. For this and other purposes, …

---

DOSBox for Mac: cycles=max affects directory listing?

Posted on 2017-04-28, 14:05

by

by emendelson

in DOSBox Games/Apps

in DOSBox Games/Apps

This has nothing to do with games, so I certainly don't expect the devs to take any interest, but I wonder if anyone else can make sense of this puzzling thing. In DOSBox for OS X/macOS (NOT for Windows), if I set cycles=max in the conf file, then WordPerfect for DOS's built-in directory list (the …

---

Re: Printing & clipboard-exchange - kludgy workaround for DOSBox under Windows (revived)

Posted on 2017-04-27, 13:31

by

by emendelson

in DOSBox Development

in DOSBox Development

I've now enhanced this (in an updated download) to work more smoothly with Windows 3.1. Here's what you need to do: 1. As shown in the previous post, add the "mount P Printout" line to your DOSBox.conf if you use the conf file to launch Windows in DOSBox. 2. In your Windows 3.11 setup, edit win.ini …

---

Re: DOSBox-X branch

Posted on 2017-04-25, 17:17

by

by emendelson

in DOSBox Patches

in DOSBox Patches

I think the problem is that I added the optional DirectX components to mingw, following the method in the wiki. So I renamed four DirectX-related headers in the mingw include directory, and then got this far: In file included from menu.cpp:23:0: ../../include/menu.h:46:36: error: '_MAX_DRIVE' was …

---

Re: DOSBox-X branch

Posted on 2017-04-25, 17:00

by

by emendelson

in DOSBox Patches

in DOSBox Patches

For what it's worth, here's the error that I got when building gui: sdlmain.cpp: In function 'int SDL_main(int, char**)': sdlmain.cpp:4482:27: error: 'ImmDisableIME' was not declared in this scope ImmDisableIME((DWORD)(-1)); EDIT: So I commented out that line in sdlmain.cpp, and got this far: g++ - …

---

Re: DOSBox-X branch

Posted on 2017-04-25, 16:54

by

by emendelson

in DOSBox Patches

in DOSBox Patches

OK, so this solved the fpu_instructions.h error (see the line below "added for mingw"): #if defined(WIN32) && defined(_MSC_VER) /* std::isinf is C99 standard how could you NOT have this VS2008??? */ # include /* the purpose of this macro is to test for -/+inf. NaN is not inf. If finite or NaN it's …

---

Re: DOSBox-X branch

Posted on 2017-04-25, 15:46

by

by emendelson

in DOSBox Patches

in DOSBox Patches

It looks like for mingw you'll need to #include for isinf to work. isinf is fairly messy across multiple targets, apparently. So I tried adding this line to fpu_instructions.h (I'm only guessing that that's where it should go), below #include #include But on building, I seem to get the same error …

---

Re: DOSBox-X branch

Posted on 2017-04-25, 15:31

by

by emendelson

in DOSBox Patches

in DOSBox Patches

Wait, I found this, renamed it endian.h, and put it in include, and got past that error: https://gist.github.com/panzi/6856583#file-portable_endian-h But then I got this error much later: mv -f .deps/core_prefetch.Tpo .deps/core_prefetch.Po g++ -DHAVE_CONFIG_H -I. -I../.. -I../../include -I/usr/ …

---

Re: DOSBox-X branch

Posted on 2017-04-25, 15:23

by

by emendelson

in DOSBox Patches

in DOSBox Patches

You just need to stop using those project files but use mingw(64?) for this ;) Now why didn't I think of that? ;) I can build DOSBox SVN in mingw (32-bit Windows 7), so I tried this, but I came up against the lack of the endian.h file that The Great Codeholio mentioned. Here's the error: make[4]: …

---

Re: DOSBox-X branch

Posted on 2017-04-25, 14:56

by

by emendelson

in DOSBox Patches

in DOSBox Patches

But I wasn't being sarcastic! I really don't know how to do this, and I wasn't asking you to do it! (It's always annoying when someone asks someone else to write something...) There are a lot of Win32 types around here who could write that file in three minutes if they wanted to build for Windows, …

---

Re: DOSBox-X branch

Posted on 2017-04-25, 14:23

by

by emendelson

in DOSBox Patches

in DOSBox Patches

Visual Studio lacks endian.h. Those are macros to byte-swap a value to/from host to little endian. Since Windows is little endian, you could make a header file with defines for each one that just passes the value through unmodified. http://man7.org/linux/man-pages/man3/endian.3.html I didn't …

---