[Freedos-devel] kraptor in VirtualBox
I now have realized that kraptor colors were completely bad in kraptor... until I select some video mode in configuration menu (first page). It seems whatever the mode I choose, colors are fixed by choosing a video mode in the configuration (there are a lot of choice). So I begin to suspect... maybe VirtualBox does not set the usual palette when switching to a graphic mode... strange idea it could just keep the default text mode palette...16 colors, where most graphics mode are 256 colors? Did not investigate that idea more.___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] allegro 4.2 branch, many problems
Le mar., 22 juin 2021 15:30:29 -0400 Ladislav Lacina écrit >The last working Allegro for DOS is the version 4.2.3 not 4.2.4 >Download the working package from here: http://www.mrdictionary.net/allegro/ >or from here: http://www.doshaven.eu/programming-tools/ Thanks! I downloaded: http://www.mrdictionary.net/allegro/20190618_DJGPP_dir_allegro423installed.zip and used it in DOSEMU2. (Allegro is precompiled) I guess one of the main diff could be that it comes with gcc 4.2.1, was using 10.3.0. At first, I was having the same issues with kraptor. Did had to erase the obj (make clean does not seems to do it) So after rebuild, I still had duplicate entries, but only for dumb functions. So I rebuild dumb. And then seems all was fixed. Only real issue, was that allegro.h was including syslimits.h (9 chars before dot). I copied syslimit.h on syslimits.h in /home/paul/.dosemu/drive_c/DJGPP/LIB/GCC/DJGPP/4.21/INCLUDE/ The result seems to do the same as the original... I don't know why I should have expected otherwise.___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] allegro 4.2 branch, many problems
The last working Allegro for DOS is the version 4.2.3 not 4.2.4 Download the working package from here: http://www.mrdictionary.net/allegro/ or from here: http://www.doshaven.eu/programming-tools/ -- Původní e-mail -- Od: Paul Dufresne via Freedos-devel Komu: Technical discussion and questions for FreeDOS developers. Datum: 22. 6. 2021 17:09:28 Předmět: Re: [Freedos-devel] allegro 4.2 branch, many problems " I fixed the missing rule to build allegro.so by adding the file: paul@kasparno:~/Téléchargements/allegro5-4.2$ cat makefile.dep lib/unix/liballeg-4.2.4.so: $(ALLEGRO_LIBRARY_SOURCES) It is not present, but included in makefile (ignoring any errors). but next: paul@kasparno:~/Téléchargements/allegro5-4.2$ LANG=C make gcc -DALLEGRO_MODULES_PATH=\"/usr/local/lib/allegro\" -DHAVE_CONFIG_H -I. - Iinclude -Iinclude/allegro -I./include -I./include/allegro -std=gnu89 - DALLEGRO_LIB_BUILD -mtune=k8 -O2 -funroll-loops -ffast-math -Wall -Wno- unused ./src/i386/asmdef.c -o obj/unix/asmdef In file included from include/allegro/base.h:41, from include/allegro.h:25, from ./src/i386/asmdef.c:27: include/allegro/internal/alconfig.h:36:16: fatal error: allegro/platform/ alplatf.h: No such file or directory 36 | #include "allegro/platform/alplatf.h" | ^~~~ compilation terminated. make: *** [makefile:232: obj/unix/asmdef] Error 1 So I just did a: touch include/allegro/platform/alplatf.h And now I get a lot errors like: include/allegro/internal/aintern.h:1038:48: error: unknown type name 'uintptr_t' 1038 | AL_FUNC(void, _poly_scanline_ptex_mask_lit32, (uintptr_t addr, int w, POLYGON_SEGMENT *info)); | ^ include/allegro/internal/alconfig.h:209:62: note: in definition of macro 'AL _FUNC' 209 | #define AL_FUNC(type, name, args) type name args | ^~~~ include/allegro/internal/aintern.h:1039:45: error: unknown type name 'uintptr_t' 1039 | AL_FUNC(void, _poly_scanline_atex_trans32, (uintptr_t addr, int w, POLYGON_SEGMENT *info)); | ^ include/allegro/internal/alconfig.h:209:62: note: in definition of macro 'AL _FUNC' 209 | #define AL_FUNC(type, name, args) type name args | ^~~~ include/allegro/internal/aintern.h:1040:45: error: unknown type name 'uintptr_t' 1040 | AL_FUNC(void, _poly_scanline_ptex_trans32, (uintptr_t addr, int w, POLYGON_SEGMENT *info)); | ^ include/allegro/internal/alconfig.h:209:62: note: in definition of macro 'AL _FUNC' 209 | #define AL_FUNC(type, name, args) type name args | ^~~~ According to: https://stackoverflow.com/questions/9042024/error-unknown-type -name-intptr-t (https://stackoverflow.com/questions/9042024/error-unknown-type-name-intptr-t) I would have to include stdint.h in those files. I have tried to add CLAGS= -std=gnu89 but it did not seems to help with that problem... but then, is is on .h file... So I begin to think to git clone the branch and work on it. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel "___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] allegro 4.2 branch, many problems
I fixed the missing rule to build allegro.so by adding the file: paul@kasparno:~/Téléchargements/allegro5-4.2$ cat makefile.dep lib/unix/liballeg-4.2.4.so: $(ALLEGRO_LIBRARY_SOURCES) It is not present, but included in makefile (ignoring any errors). but next: paul@kasparno:~/Téléchargements/allegro5-4.2$ LANG=C make gcc -DALLEGRO_MODULES_PATH=\"/usr/local/lib/allegro\" -DHAVE_CONFIG_H -I. -Iinclude -Iinclude/allegro -I./include -I./include/allegro -std=gnu89 -DALLEGRO_LIB_BUILD -mtune=k8 -O2 -funroll-loops -ffast-math -Wall -Wno-unused ./src/i386/asmdef.c -o obj/unix/asmdef In file included from include/allegro/base.h:41, from include/allegro.h:25, from ./src/i386/asmdef.c:27: include/allegro/internal/alconfig.h:36:16: fatal error: allegro/platform/alplatf.h: No such file or directory 36 | #include "allegro/platform/alplatf.h" | ^~~~ compilation terminated. make: *** [makefile:232: obj/unix/asmdef] Error 1 So I just did a: touch include/allegro/platform/alplatf.h And now I get a lot errors like: include/allegro/internal/aintern.h:1038:48: error: unknown type name 'uintptr_t' 1038 | AL_FUNC(void, _poly_scanline_ptex_mask_lit32, (uintptr_t addr, int w, POLYGON_SEGMENT *info)); | ^ include/allegro/internal/alconfig.h:209:62: note: in definition of macro 'AL_FUNC' 209 | #define AL_FUNC(type, name, args) type name args | ^~~~ include/allegro/internal/aintern.h:1039:45: error: unknown type name 'uintptr_t' 1039 | AL_FUNC(void, _poly_scanline_atex_trans32, (uintptr_t addr, int w, POLYGON_SEGMENT *info)); | ^ include/allegro/internal/alconfig.h:209:62: note: in definition of macro 'AL_FUNC' 209 | #define AL_FUNC(type, name, args) type name args | ^~~~ include/allegro/internal/aintern.h:1040:45: error: unknown type name 'uintptr_t' 1040 | AL_FUNC(void, _poly_scanline_ptex_trans32, (uintptr_t addr, int w, POLYGON_SEGMENT *info)); | ^ include/allegro/internal/alconfig.h:209:62: note: in definition of macro 'AL_FUNC' 209 | #define AL_FUNC(type, name, args) type name args | ^~~~ According to: https://stackoverflow.com/questions/9042024/error-unknown-type-name-intptr-t I would have to include stdint.h in those files. I have tried to add CLAGS= -std=gnu89 but it did not seems to help with that problem... but then, is is on .h file... So I begin to think to git clone the branch and work on it.___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] How do you use FreeDOS?
On Tue, Jun 22, 2021 at 9:26 AM Jim Hall wrote: > > Hi everyone! > > Looking for feedback on this form. >[..] > I've set up this anonymous survey to ask how people use FreeDOS. > https://docs.google.com/forms/d/e/1FAIpQLSfbD3ge4SgFQZeTTRUneMKCb5Y4LjUi3dwWIpJFVfIk1nzCJg/viewform >[..] > I'll post the survey on the website this weekend, and advertise it for > a few weeks via Twitter, Facebook, website, etc. > I should mention: Feel free to submit your own responses to the form, but for now I'll consider this in TEST MODE. I will DELETE SURVEY RESPONSES this weekend when I post the survey "for real." (If I update the survey questions/options based on feedback, new responses don't match up with previous responses .. so best to start over with responses.) Jim ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] How do you use FreeDOS?
Hi everyone! Looking for feedback on this form. Background: In this weekend's FreeDOS get-together, some folks wanted to know "how do people run FreeDOS?" and "who is running FreeDOS?" I ran a survey around 2010 or 2012, and that's how we learned that many people use FreeDOS for three key things: playing DOS games, running DOS software (usually for legacy reasons), and supporting embedded systems. I'd like to update the survey, and learn a few other things about how people use FreeDOS. I've set up this anonymous survey to ask how people use FreeDOS. https://docs.google.com/forms/d/e/1FAIpQLSfbD3ge4SgFQZeTTRUneMKCb5Y4LjUi3dwWIpJFVfIk1nzCJg/viewform Questions are: 1. What do you use FreeDOS for? (select all that apply) [play DOS games, run DOS programs, ..] 2. How do you run FreeDOS? (select all that apply) [on real hardware, in a virtual machine] 3. Does FreeDOS share the same hardware with another operating system? [yes/no .. with Windows/Linux/DOS/other] 4. What is your level of DOS experience? [1-10 scale] Thoughts on the survey? Too many questions? Too many options? Or not enough? I want to provide a balance on this survey; keep the questions + answers focused, but gather enough detail that we can learn how people are running FreeDOS, and what they are doing with it. This information can help inform "use cases" for FreeDOS, especially as we discuss software and installer options. It's also useful information to have as I update the website (see test.freedos.org) so I can provide the right info to help people. I'll post the survey on the website this weekend, and advertise it for a few weeks via Twitter, Facebook, website, etc. Jim ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
