[Freedos-devel] Nano-X supposedly ported to DOS, API similar both to X and Windows GDI, small memory footprint

http://www.microwindows.org/ http://en.wikipedia.org/wiki/Microwindows Not sure how it compete with OpenGEM because I did not look to it. In fact I don't even know if OpenGEM is a full GUI or mainly a graphical file explorer.

[Freedos-devel] PicoTCP a new TCP/IP stack that FreeDOS could use?

Well, I just watched this video from FOSDEM 2014, and it made me think about FreeDOS. http://video.fosdem.org/2014/AW1121/Sunday/PicoTCP.webm or https://www.youtube.com/watch?v=AO4liMJZ0Qg The FOSDEM page: https://fosdem.org/2014/schedule/event/deviot03/ The PicoTCP page on the company web site:

Re: [Freedos-devel] Nano-X supposedly ported to DOS, API similar both to X and Windows GDI, small memory footprint

OpenGem 6 seems to have been published in july 2006, and not have any development since. From http://en.wikipedia.org/wiki/Talk:OpenGEM Too add to the guy above me, as of the date above, Shane Coughlan's site is still down, and he has essentially disappeared from the Internet, with his Twitter

Re: [Freedos-devel] Nano-X supposedly ported to DOS, API similar both to X and Windows GDI, small memory footprint

The advantage of GEM however is that it can execute pretty much any (Free)DOS program, so not only GUI programs, while microwindows seems to support only specifically created programs. well, GEM main app is a file manager, able to launch programs Sure a file manager built on top of Nano-X (that's

Re: [Freedos-devel] Nano-X supposedly ported to DOS, API similar both to X and Windows GDI, small memory footprint

If you're gonna require 32-bit, you almost might as well just go with *x *x ? As far as I know, Xorg cannot run on DOS. There is Cygwin/X but for Windows, not DOS: http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-windows-versions-supported http://www.directfb.org/ could possibly be an

Re: [Freedos-devel] AGUI user interface library released

Thank you for your christmas gift!... that I just opened today! Well, I am kind of looking for a small-easy to learn GUI for years. And as new year began, I was looking back again at Gtk, but I might find yours easier. By example, just not having pkg-config in Mingw was a stopper for me with Gtk.

Re: [Freedos-devel] mTCP/IP stack by M Brutman is now closed source

Well, I don't know how hard it would be to port picoTCO (GPL v.2) to DOS: http://docs.picotcp.com/user_doc.pdf http://www.picotcp.com/about/ Heard about it from FOSDEM 2014: https://www.youtube.com/watch?v=AO4liMJZ0Qg also http://video.fosdem.org/2014/AW1121/Sunday/PicoTCP.webm

Re: [Freedos-devel] FDI Additional Languages

Yeah, I am thinking about translating the 3 files to french... just have a little problem making it a priority. Guess you should not postpone release if you don't get results soon enough. 2015-12-17 12:27 GMT-05:00 Jerome E. Shidel Jr. : > I have no problem including any

Re: [Freedos-devel] FDI Additional Languages

Well, I am for from being an expert too on that. I tend to believe, code page 437 which was mostly the standard in DOS (at least US version)... was later mostly replaced by code page 1250 in Windows. Edit: looks like I am wrong: "ANSI Windows code pages, and especially the code page 1252, were

Re: [Freedos-devel] FDI Additional Languages

I wanted to include the following link from Microsoft in my previous post: https://www.microsoft.com/typography/unicode/cscp.htm This WGL4 font thing seems interesting, and I was wondering if FREEDOS support or will support these fonts.

Re: [Freedos-devel] FDI Additional Languages

Me again! ;) This FREEDOS page about country.sys: http://help.fdos.org/en/hhstndrd/base/cntrysys.htm It speaks about stable vs unstable kernel... (written in 2008) do we still have these today? --

Re: [Freedos-devel] fdisk translation

I am in the learning about translating programs. I was aware of that page: https://ftp.gnu.org/old-gnu/Manuals/glibc-2.2.3/html_chapter/libc_8.html Basicaly, there is two different methods (and set of C functions) to translate a string. The first method is: char * catgets (nl_catd catalog_desc,

Re: [Freedos-devel] fdisk translation

I now see: https://sourceforge.net/p/freedos/bugs/65/ although I am unaware of a 1,3.2 version. But I will not look any further on this for next 10 hours. -- ___ Freedos-devel

[Freedos-devel] Translation tables

ftp://ftp.tuwien.ac.at/.vhost/www.freedos.org/fd-doc/contrib-howto.html mentions at 2. For the non-programmer: If you speak a language other than English, translate the FreeDOS Internationalization table. This is a list of computer terms in English, Spanish, Italian, and other languages. but the

[Freedos-devel] fdisk translation

When testing the installer, it was not feeling right to go from the french installer to the english fdisk... how could fdisk be translated? -- ___ Freedos-devel mailing list

Re: [Freedos-devel] FDI Language Translations

>There are two ways to test translations. >1) Best way, Thanks for explaining how to use this new tool... will try it when I find time -- ___ Freedos-devel mailing list

Re: [Freedos-devel] fdisk translation

I have encountered a little bit similar problem that is not really one, but looks like one. That was with testing the new installer floppy image, with a freshly created disk of 100Mb, and all_cd.iso under QEMU­. After fdisk had created the partition, the virtual system reboot. After reboot, the

Re: [Freedos-devel] FDI Additional Languages

I am not sure we can expect most languages could be encoded in CP437 (Code page 437 [IBM]). Maybe a file in CP437 should have something like "CP=850" and then the 3 others file would be encoded in that specific code page. Then the installer could use chcp to select the codepage before

Re: [Freedos-devel] FDI Translations

Translating it in french is easy: "Enlevez le média d'installation puis pressez une touche pour redémarrer le système, sinon tapez CTRL-C pour sortir." What's hard is edit the translation file and retest it. ;) --

Re: [Freedos-devel] FDISK Update

I am a bit confused as to what is/should be the current version. Antony Gordon said he made modifications to v. 1.2.1 and 1.3 but I don't know if the changes have been published and if so where. Then there is (same code, two different categories):

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

Your suggestion to "fdisk /mbr:81" (81=D:) was making much sense to me because the disk was having grub on it before I erase all with fdisk to make place for FreeDOS. So yes, it made sense that grub being installed in MBR might made me not having normal MBR. But trying "fdisk /mbr:81" have not

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

>What exact partition i.d. is your FAT? Perhaps it needs to be LBA >aware (0xC)? I don't remember offhand. Yes, looks like you found the problem. I changed it in Linux, from b (W95 FAT32) to c (W95 FAT32 LBA). Then tried to boot my partition (that is now in GRUB since I just installed a Linux to

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

I have tried the latest FDI-USB.IMG and I would almost be happy with it. Yes, I can now install in french fine. Yes, fdisk now select the D: drive that is my hard disk. Yes, all the installation goes fine. Except when I reboot, it reboot in loop. My hard drive is SATA did read it should works

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

Note that I still used 4000 Mb primary FAT32 (big drive?) partition. -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

Ok, I open my box and literally found an old forgotten dusty unconnected PATA 40Gb drive. I connected it (after disconnecting SATA drive). And reinstall FreeDOS from USB key. Worked flawlessly this time. At least a few seconds until I try to type 'help dir' or 'help' (as suggested) which make the

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

At least with fdisk /XO [Extended Options in user interface] on (set at the end of fdisk.ini), we have access to functions to change type of a partition in the interface. Looking a bit in the code, there seems to be an option for extended interrupt 13h functions. And it seems to use (more) LBA in

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

Burn on a DVD latest SystemRescueCD but does the same as on my USB key: -divide by zero exception when trying to use FreeDOS on the DVD -SuperGrub just showing upperleft blinking cursor when booting SATA 149 GiB, FreeDOS partition But discovered that HardwareDetectionTool was showing MBR as Grub2

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

I just wrote (DD in Linux) the FDI-USB .IMG file on an USB-KEY. Think this was my first try to boot FreeDOS on USB key. Boots fine (once adjusted in BIOS). Suprise 1) Unable to select a language different than english. Others are shown, but key down does not move to others. Did not was able (or

[Freedos-devel] keyb us does not work

After installing in french, I get french keyboard... you might find it strange, but here in Quebec, we are totally lost with french keyboard. US is much more usable for us. But then, when I type keyb us the 2 output lines, seems to suggest that it worked. But I still have AZERTY (french)

Re: [Freedos-devel] keyb us does not work

I tried to run mkeyb rather than keyb (I had also tried xkeyb). mkeyb have worked first time. I closed QEMU window, retried, then it wont work. Retried, would work. When it work, it detects the other version running: different version of KEYB found 594003C != d0f4003c Is it the address of KEYB

Re: [Freedos-devel] fdnpkg: Repository download failed (ibiblio)

First, it seems lsl must be run before E1000odi.com But 18.5 give EEPROM checksum too. Guess I will go toward ne2k driver. Somehow, I have this strange feeling of having tried in the past, but not really reminding. --

Re: [Freedos-devel] fdnpkg: Repository download failed (ibiblio)

2016-11-07 20:40 GMT-05:00 Jerome Shidel : > There is also the Intel e1000 gigabit packet driver to try. > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/e1000pkt.html With it when I do: e1000pkt.com 0x60 I get: PCI BIOS is required for

Re: [Freedos-devel] fdnpkg: Repository download failed (ibiblio)

It looks like PRODOS v.19.0 (latest with executable file in it) cannot be used wth QEMU e1000 driver, because QEMU e1000 driver would not correctly set EEPROM checksum: https://bugs.launchpad.net/qemu/+bug/1639983 Will try oldest version (18.5).

Re: [Freedos-devel] fdnpkg: Repository download failed (ibiblio)

Ah, finally with PCNTPK.COM, after erasing my own WATTCP.CFG file, now fdnpkg seems to work (get it's configuration from bootp). Was able to update repos. Seems it have updated fdnpkg itself now. -- Developer Access

Re: [Freedos-devel] fdnpkg: Repository download failed (ibiblio)

I just copied and tested with source code fdnpkg.cfg. Same "Repository download failed!" but this time on packages of http://svarog386.vister.fr. 2016-11-07 8:59 GMT-05:00 Paul Dufresne <dufres...@gmail.com>: > After hours of network configuration, I have been able to have Free

Re: [Freedos-devel] keyb us does not work

2016-11-07 4:15 GMT-05:00 Mateusz Viste <mate...@nospam.viste.fr>: > On Sun, 06 Nov 2016 00:14:25 -0400, Paul Dufresne wrote: >> you might find it strange, but here in Quebec, we are totally lost with >> french keyboard. US is much more usable for us. > > Hi Paul, out

Re: [Freedos-devel] fdnpkg: Repository download failed (ibiblio)

I just copied ping.exe (WATTCP) and I now see I get ** Transmit fault ** Guess I need to put even more time to figure out how to configure network. Sorry for noise. -- Developer Access Program for Intel Xeon Phi

[Freedos-devel] fdnpkg: Repository download failed (ibiblio)

After hours of network configuration, I have been able to have FreeDOS fdnpkg giving something else than bootp and dhcp configuration failing messages under QEMU. But now I see this (as an example) for fdnpkg checkupdates: Loading

Re: [Freedos-devel] fdnpkg: Repository download failed (ibiblio)

typo: http://svarog386.viste.fr 2016-11-07 9:14 GMT-05:00 Paul Dufresne <dufres...@gmail.com>: > I just copied and tested with source code fdnpkg.cfg. > Same "Repository download failed!" but this time on packages of > http://svarog386.vister.fr. > > 2016-11-

Re: [Freedos-devel] fdnpkg: Repository download failed (ibiblio)

Just as note to others, I just learn about: qemu -device ? [to list emulated devices available] and: -device driver[,prop[=value][,...]] Add device driver. prop=value sets driver properties. Valid properties depend on the driver. To get help on possible drivers and properties, use -device help

Re: [Freedos-devel] How to rework some French translations and contribute a Turkish translation?

Oops, FDNPKG.FR you said. I was confusing with the installer, sorry. -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel

Re: [Freedos-devel] How to rework some French translations and contribute a Turkish translation?

> - FDNPKG.FR is in UTF8 but I couldn't convert it locally to ISO-8859-1. > iconv > complains about an illegal character at position 0. Hope Mateusz will know > what > to do with it. Well, it is supposed to be CP437, as far as I can tell. Which is not ISO-8859-1 nor UTF8. Here I try to look at it

[Freedos-devel] French in FreeDOS-1.3 (the problem of accented letters in package descriptions)

Was thinking of writing this for a few days, but did not came to do it. First, congrats for the 25 years of the project! I have seen the Lunduke video about it, and this convinced me to come back, see if I can contribute a bit for 1.3 release. Sadly, my contribution is much about telling

Re: [Freedos-devel] Proposition for what a DOS package should be

Well, honestly, while I was writing the first messages about packages, I did not read yet: http://wiki.freedos.org/wiki/index.php/Package but I was more thinking about what I would expect, and I still believe there is good stuff in what I propose that is missing in most packaging solutions (for

Re: [Freedos-devel] Proposition for what a DOS package should be

Beside, this is not just a a matter of trust. This is code janitoring. By recompiling programs, we make sure that the programs needed for them are still available. We can make small changes if possible, to make the programs built from more open implementations of C or assembler. Briefly,

Re: [Freedos-devel] Proposition for what a DOS package should be

Thanks Tom Ehlert, to confirm my feeling that most DOS packages have not been rebuilt from source code. We used to trust people because we knew no better way in the past. Well, I was not expecting in any way that the DOS kernel would in any way verify binaries. And I am/was finally aware

[Freedos-devel] Re : Proposition for what a DOS package should be

Well, thinking a bit more... often "packages" will be on web sites. And the user might well not care about let's say source code, even if builder wish to include it in the package. Why force the user to download source code inside the package if he/she does not want it? So I would propose

[Freedos-devel] Proposition for what a DOS package should be

I am thinking about how software is/should be distributed. I believe, source code is for programmers. I believe, executable code is for users. I believe a intermediary between the two should exist. I guess it is a package. I believe this intermediary is for installer(s). I believe this

[Freedos-devel] Re : Proposition for what a DOS package should be

This is clearly work in progress. Publishing for comments, even if rather incomplete. I am realizing I am ignoring the project current package format(s). I have the feeling the package format for 1.3 is not documented yet. Although one could look at it inside the iso image. I believe we

Re: [Freedos-devel] Re : Re : Could the installer use gcdrom to get SATA cdrom working without IDE emulation?

I should have describe a little bit more why I was suggesting it might be necessary to include AHCI driver in DOS kernel. That's because on a AHCI only computer (without PATA or SATA IDE),  you cannot access the sectors with INT 13h. Well, I have tried in Qemu with '-M Q35' machine

Re: [Freedos-devel] Re : Re : Could the installer use gcdrom to get SATA cdrom working without IDE emulation?

Le lun., 02 nov. 2020 15:32:43 -0500 Eric Auer écrit Hi Paul, > That's because on a AHCI only computer (without PATA or SATA IDE), >  you cannot access the sectors with INT 13h. Yes you can. For harddisk/SSD. I am glad to report that I was wrong. Indeed INT 13h continue to

Re: [Freedos-devel] Obsolete DJGPP in upcomming FreeDos 1.3

Le mer., 28 oct. 2020 16:13:13 -0400 Jerome Shidel écrit There are about 12 DJGPP packages mirrored on ibiblio and in the software repository. I would assume they all are outdated. It would be nice if someone provided updates for these packages. However,I

[Freedos-devel] began to list problems I see with FD 1.3-rc3

P120: 'keyb cf' works, but there is no French (Canada) in the keyboard list of the installer P121: I have chosen 'French' as language, French(alternative?) as keyboard, install essential... when rebooting the system I get 'Bienvenue au systemeParameter Error' followed by working C: prompt

[Freedos-devel] 1.3-rc3: should give meaningfull error message on AHCI (SATA) only system

If I had: '-M q35' to qemu to enable a SATA only machine, when booting in live mode 1.3-rc3: UDVD2: Nothing to use; UDVD2 not loaded. I hope UDVD return an error code we could use to give a more meaninful message like: Your computer is running in SATA only mode, so I cannot access the CD-ROM.

[Freedos-devel] I am sad less seems to be an alias on more

I wish | less would allows PageUp to go back in the text!___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] I am sad less seems to be an alias on more

Le ven., 30 oct. 2020 12:22:45 -0400 Jim Hall écrit >However, you can use u to go up by half a page. Or b to go back by a full page. Oh thanks! I kind like never learn those keys. But a newer version in 1.3 would be

[Freedos-devel] PCI BIOS

Well... I just would like to share info about PCI-BIOS, that I recently learn about. This is interrupt calls for using PCI devices. Can see them at: http://www.delorie.com/djgpp/doc/rbinter/ix/1A/B1.html I don't know how much they are implemented in real life... but I have seen MACH

[Freedos-devel] Re : PCI BIOS

Well, I was able to verify the presence of PCI-BIOS easily with debug (under Qemu): -a 100 mov ax,b101 sub di,di int 1a int 20 g=100 107 AH=00 PCIBIOS present AL=01 configuration space access mechanism 1 supported BX=0210 version 2.1 supported EDX = 20494350h (' ICP') (well I only see 4350

[Freedos-devel] Smaller C

Well, after having a problem with IA-16 gcc (which seems to requires DJGPP gcc installed and working), I have search for an other free C compiler for FreeDOS. I have found Smaller C: https://github.com/alexfru/SmallerC/blob/master/v0100/doc/smlrc.md I note: Smaller C is not an optimizing

Re: [Freedos-devel] Smaller C

I have just scan all the .exe from /v0100/bind/ directory (16 bits version) and /v0100/bindp/ directory (32 bits DPMI) and none were suspicious. Was also able to build test.exe with 32 bits DPMI version. I guess would be better to package 32 bits DPMI version because we have cwsdpmi by

[Freedos-devel] Re : Open Watcom: Install, setup, compile and link your 'first' program

Ok, since my previous message I discover: wcl and wcl386: wcl:  C/C++ compile and link utility for 16-bit targets wcl386:  C/C++ compile and link utility for 32-bit targets taken from: https://flaterco.com/kb/ow.html So rather than compile, then link in previous post, you can just do: wcl

[Freedos-devel] Open Watcom: Install, setup, compile and link your 'first' program

Hi! It is said on: https://www.freedos.org/contribute/ that: "Port FreeDOS utilities to OpenWatcom C and NASM—our preferred C compiler and Assembler for FreeDOS." I kind of just discovered the OpenWatcom C,C++ compiler yesterday, and just was able to compile and link my first program this

Re: [Freedos-devel] began to list problems I see with FD 1.3-rc3

Le sam., 31 oct. 2020 06:26:59 -0400 Jerome Shidel écrit Hi Paul, Have you listed the issues you have found on the FreeDOS "feature requests” and “bug tracker” lists on http://SourceForge.net? https://sourceforge.net/p/freedos/feature-requests/

[Freedos-devel] Priority of ticket, 1 should be highest priority

I was misinterpreting the priority of tickets on SourceForge. I thought 9 was the highest, but it seems to be the lowest, according to: https://sourceforge.net/p/forge/site-support/18975/#cc07___ Freedos-devel mailing list

[Freedos-devel] Re : Could the installer use gcdrom to get SATA cdrom working without IDE emulation?

I said: "but why don't we use gcdrom rather than UDVD2?" Obviously because a lot of DOS computers does not have a SATA "CDROM" (probably more DVD disk). Ideally I would say try gcdrom, if it does not work, use old UDVD2. But, to be more prudent I propose: try UDVD2, if it does not work,

[Freedos-devel] To boot FreeDOS from GPT partition table...

It seems not so hard in theory: Define a GUID for FreeDOS. Create a BIOS Boot partition. Write at the beginning of BIOS Boot partition a special "MBR" that search FreeDOS GUID partition in the GPT, load it and jump to it.___ Freedos-devel

[Freedos-devel] Could the installer use gcdrom to get SATA cdrom working without IDE emulation?

Hey! We already have a AHCI driver (SATA)!? I see it at: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/gcdrom.html I know the installer now fail with UDVD2 for SATA... but why don't we use gcdrom rather than

[Freedos-devel] Re : Re : Could the installer use gcdrom to get SATA cdrom working without IDE emulation?

Sorry I was confused about gcdrom.sys. (Re)reading http://www.bootablecd.de/fdhelp-internet/en/hhstndrd/base/gcdrom.htm I now realize it is still an IDE driver, not an AHCI driver like I thought. Anyway, I wonder if the kernel itself would be needed to support AHCI mode without IDE

[Freedos-devel] FD13LIVE.ISO: does not install on a new (unpartitioned) disk

Hi! I have tried http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.3/previews/1.3-rc3/FD13-LiveCD.zip with qemu, and I have come to the conclusion that I cannot install (with install from the main menu, or with setup.exe in live mode) on a newly created disk image. I

Re: [Freedos-devel] Problems on 1.3rc4 on VirtualBox and QEMU - Paku Paku 160x100 mode

Le lun., 14 juin 2021 06:33:06 -0400 Eric Auer écrit >Does the game fill the whole window with BOTH >virtualbox and qemu for you? Because it only >fills the upper half in dosemu2 at the moment. Testing on Ubuntu 21.04. With virtualbox, it is full-windows. Going full-screen

[Freedos-devel] The confusing fdisk releases

I check about 1h ago, and concluded that there was no new releases of fdisk since 1.3RC4. I went to: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.3/previews/1.3-rc4/report.html checked:

[Freedos-devel] 2 diffrent index of ibiblio?

I am a bit confused... I used to see: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/latest/pkg-html/group-devel.html but searching ibiblio from myself found: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/?C=N;O=A The first seems to be more the

Re: [Freedos-devel] Problems on 1.3rc4 on VirtualBox

Le ven., 11 juin 2021 14:14:58 -0400 Eric Auer écrit [citating only "pertinent" info] So apparently VirtualBox 6.1.22 has a surprising amount of problems with DOS games and I wonder why that is the case. I guess all games work equally well or unwell for

Re: [Freedos-devel] Problems on 1.3rc4 on VirtualBox

Resending to the list, had responded to Tom privately (thought it had sent it to me privately) Le ven., 11 juin 2021 11:14:43 -0400 Tom Ehlert Software écrit >> French: I think I have not seen any accented characters, like all replaced >> by 2 chars

Re: [Freedos-devel] Problems on 1.3rc4 on VirtualBox

After many many hours of fighting with the installer to install in dosemu... then realized that it was dosemu1 not 2, I finally managed to have FreeDOS mostly running under Dosemu2. But when I ran a program using cwsdpmi, it complains I should run cwsdpmi. And then, cwsdpmi complains it

Re: [Freedos-devel] Problems on 1.3rc4 on VirtualBox

Fixed problem of hanging after partitioning by adding -boot d to the script, that make it always boot virtual Live CD. Changed it back to -boot c after installation to boot the installed system. fmines ok freedoom, some text scrolling fast, then illegal instruction, return to command

[Freedos-devel] a color bug in VirtualBox for VGA

I have tried to find a bug report about color not working on VGA in VirtualBox: the most relevant I see seems: https://www.virtualbox.org/ticket/4777 VESA palette support broken (Closed: Obsolete)___ Freedos-devel mailing list

Re: [Freedos-devel] Problems on 1.3rc4 on VirtualBox

Yesterday, the first Linux I installed, to test outside of NixOS was Debian 11 (same computer, I make different partitions under GPT, UEFI). I was surprised that Debian got rid of VirtualBox in Debian 10 (because they don't like how the company handle CVE for older versions), and also got rid

Re: [Freedos-devel] Problems on 1.3rc4 on QEMU

Le dim., 13 juin 2021 00:11:11 -0400 Jim Hall écrit >I hadn't tried the games yet, so verifying your bug report was my first time. Then you may get the wrong impression that many games does not work. That's not really the case, I have been playing many of

Re: [Freedos-devel] FreeDOS kernel and FreeCOM command.com updates

Le dim., 13 juin 2021 19:13:45 -0400 écrit On Sun, Jun 13, 2021, 4:44 PM tom ehlert wrote: > Unfortunately, ALL files in the kernel source download have the same > timestamp, making it impossible to see what was last changed when :-o ALL times of

Re: [Freedos-devel] Problems on 1.3rc4 on VirtualBox and QEMU

Eric asked: what have change? (game was working for me, not anymore) The previous was with under VirtualBox [that I believe does not handle color palette right] And the newer results were with QEMU. I have observed that bolitare works under QEMU if I remove the option that add sb16

Re: [Freedos-devel] Why games have bad color in VirtualBox

That said, I am at least partially wrong. Changing colors works in VirtualBox, QEMU and DOSEMU2. color 0 is black, this is the default color for text mode. In Debug: -o 3c8,0 -o 3c9,0 -o 3c9,0 -o 3c9,ff Change the black to blue. (out 3c8,0 choose color 0, then first value at 3c9 is

Re: [Freedos-devel] Why games have bad color in VirtualBox

vgapal works in VirtualBox ... and DOSEMU2, not tested under QEMU. I think problematic games run under DPMI (protected mode). Might be linked to the problem for VirtualBox not handling color palettes correctly... sometime. Will have to look the source code of the games to see how they do...

Re: [Freedos-devel] Why games have bad color in VirtualBox

I was thinking... I think DOSEMU2 execute program in VM86 mode. That way, direct IN/OUT generate an interrupt that can be intercepted to emulate hardware. It is a bit unclear how QEMU/VirtualBox works... I have read, that newer CPU emulate a full CPU. But I don't know the details... and how

Re: [Freedos-devel] Why games have bad color in VirtualBox

Ok, a few minutes ago, I had no idea about which I/O ports were related to colors... and now, I begin to suspect what could be wrong in VirtualBox code, that is it seems to ignore port 0x3c6 (mask register)... which is said: "in normal use, should be 0xff"... In:

Re: [Freedos-devel] Why games have bad color in VirtualBox

More precisely, the default DAC Mask ( i 3c6 in debug) is: QEMU: FF DOSEMU2: FF VirtualBox: 00 VirtualBox default mask of 0 and the fact that it cannot be changed, could well explains changing colors directly does not work. (as I believe a mask of 0 make it not change any colors when

Re: [Freedos-devel] Additional notes on Games

I have taken a short look at: (gnuchess source for showing board) http://git.savannah.gnu.org/cgit/chess.git/tree/src/frontend/output.cc and did not have "the feeling" it was using ANSI anymore. But then according to:

Re: [Freedos-devel] Why games have bad color in VirtualBox

DOSEMU2 seems to report itself almost exactly as VirtualBOX, that is: VBE 2.0, D1=0:VGA compatible D1=0, D0=1:DAC is fixed with 6 bit by primary color This destroy my hypothesis about games USING VGA Set palette function... rather than the VBE one (AL=9... had wrongly written AH=9 in previous

Re: [Freedos-devel] Why games have bad color in VirtualBox

I think I understand what is happening. First, an extract from: https://www.phatcode.net/res/224/files/html/ch34/34-05.html The DAC Mask "There’s one register in the DAC that I haven’t mentioned yet, the DAC Mask register at 03C6H. The operation of this register is simple but powerful; it can

[Freedos-devel] Re : Wirth compilers (was: 2 diffrent index of ibiblio?)

Thanks a lot Rugxulo for your email about Wirth compilers. Some projects, I did began to look, some I was not aware. And your opinion and info about FPC now supporting 16 bit DOS is very appreciated!___ Freedos-devel mailing list

Re: [Freedos-devel] Why games have bad color in VirtualBox

QEMU, AX=4F00 INT 10h (Return VBE controller information) reports itself as version 3.0. So I use http://www.petesqbsite.com/sections/tutorials/tuts/vbe3.pdf Capabilities: D0=0 DAC is fixed width, with 6 bits per primary color D1=0 Controller is VGA compatible D2=0Normal RAMDAC operations D3=0

[Freedos-devel] Re : Wirth compilers (was: 2 diffrent index of ibiblio?)

Looks like Modula-2 could come part of GCC (GNU compiler collection): https://www.phoronix.com/scan.php?page=news_item=Modula-2-GCC-Mainline-Hope-2021 That would be great!___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net

[Freedos-devel] easily create a gcc cross compiler for compiling C on Linux making exe to be run on DJGPP

I'd like to mention: https://github.com/jwt27/build-gcc Have worked great for me. Made an hello world! in Linux for DJGPP.___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] easily create a gcc cross compiler for compiling C on Linux making exe to be run on DJGPP

And when cross-compiling on Linux for running on DJGPP you probably want: ./configure --build=i686-pc-linux-gnu --host=i386-pc-msdosdjgpp when calling configure. Details at:

[Freedos-devel] problems cross-compiling gnuchess

I guess I need to mention what I did before  and why: Ok... I directly plugged http://www.delorie.com/pub/djgpp/current/v2gnu/pth207b.zip inside: /home/paul/opt/cross/lib/gcc/i386-pc-msdosdjgpp/10.2.0/ which I feels is a bit wrong... but working cowboy approach. [I now think

[Freedos-devel] Problems cross-compiling gnuchess

Frankly, this is in part a note to myselft... but could be considered a follow-up to me trying to compile gnuchess. So after "plugging" http://www.delorie.com/pub/djgpp/current/v2gnu/gpp1020b.zip and http://www.delorie.com/pub/djgpp/current/v2tk/ls080b.zip The problem is linked to the

[Freedos-devel] Re : Problems cross-compiling gnuchess

Le dim., 20 juin 2021 20:20:17 -0400 Paul Dufresne via Freedos-devel <mailto:freedos-devel@lists.sourceforge.net> écrit >In fact I have tried: >#include >//#include > >int main (){ >  return 0; >} >which does not find cstdllib.h. yes,

[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

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

[Freedos-devel] Got a working gnuchess 5.05

I have been able to cross-compile gnuchess 5.05. Version 5 was released in 1999: Announce: https://www.tim-mann.org/gnuchess/5.00.txt According to: https://www.tim-mann.org/gnuchess.html version 6 was released in 2011 So that version, 5.05 does not use pthread, and is easier to

  1   2   3   >