Re: [Freedos-devel] FreeDOS Interim Build T2210
Hello Robert, Robert Riebisch wrote: > > Hi Joseph, > > > On another note, I just corresponded with Sammy Mitchell of Semware. > > The Semware Editor (TSE) has gone into Freeware, and, he tells me that > > the DOS version will also eventually be freeware and open-source. > > Oh, that would be cool. > > > Whether the license is compatible remains to be seen, but, he’s going > > into a community-supported model. > > Whatever it means. > > > It’s great to see folks wanting to preserve this software, and, use it too. > > Indeed! > > Cheers, > Robert > -- > BTTR Software https://www.bttr-software.de/ > DOS ain't dead https://www.bttr-software.de/forum/ Off-topic: It seems that bttr-software.de points to a blank Bitpalace server now. I wonder if you can still able to receive this mail. Regards, Roy ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license
Paul Dufresne via Freedos-devel wrote: > > Thank you ECM for the infos! > > I think my build did not finished normally. > After about 1h build time on my i3-8100, dosbox finished with: > Object Modules [.OBJ]: MAP DMA > Run file [MEM386.EXE]: EMM386.EXE > ... > del emm386.sys > File emm386.sys not found > D:\SRC > > At some point, was making some beeps while doing codepages. > But was not seeing error messages then. > > Quite interesting that the release seems to include the build tools (masm + > assembler) > > I'll try to resume what I done: > > Using DOSBOX on Linux (Following Bryan Lunduke article) > > Installed DOSBOX > git config --global core.autocrlf > Note the value because we will temporarily break git > git config --global core.autocrlf true > cd > git clone https://github.com/microsoft/MS-DOS.git > git config --global core.autocrlf [previously noted value] I think you can just break clone and checkout process into separated commands, without changing git's global options (in windows git bash prompt): $ git clone -n https://github.com/microsoft/MS-DOS.git Cloning into 'MS-DOS'... remote: Enumerating objects: 1859, done. remote: Counting objects: 100% (220/220), done. remote: Compressing objects: 100% (123/123), done. remote: Total 1859 (delta 104), reused 97 (delta 97), pack-reused 1639 Receiving objects: 100% (1859/1859), 117.41 MiB | 6.35 MiB/s, done. Resolving deltas: 100% (288/288), done. $ cd MS-DOS $ git config core.autocrlf true $ git checkout Your branch is up to date with 'origin/main'. $ cd v4.0 $ file LICENSE LICENSE: ASCII text, with CRLF line terminators > ... to fix git for future projects > sed -i -re 's/\xEF\xBF\xBD|\xC4\xBF|\xC4\xB4/#/g' > MS-DOS/v4.0/src/MAPPER/GETMSG.ASM > sed -i -re 's/\xEF\xBF\xBD|\xC4\xBF|\xC4\xB4/#/g' > MS-DOS/v4.0/src/SELECT/SELECT2.ASM > sed -i -re 's/\xEF\xBF\xBD|\xC4\xBF|\xC4\xB4/#/g' > MS-DOS/v4.0/src/SELECT/USA.INF > > paul@fedora:~$ git diff MS-DOS/v4.0/src/SETENV.BAT MS-DOS/v4.0/src/SETENV2.BAT > diff --git a/MS-DOS/v4.0/src/SETENV.BAT b/MS-DOS/v4.0/src/SETENV2.BAT > index 0a67782..928044f 100644 > --- a/MS-DOS/v4.0/src/SETENV.BAT > +++ b/MS-DOS/v4.0/src/SETENV2.BAT > @@ -6,7 +6,7 @@ set MASM= > set COUNTRY=usa-ms > set BAKROOT=d: > rem BAKROOT points to the home drive/directory of the sources. > -set LIB=%BAKROOT%\src\tools\lib > +set LIB=%BAKROOT%\src\tools\bld\lib > set INIT=%BAKROOT%\src\tools > -set INCLUDE=%BAKROOT%\src\tools\inc > -set PATH=%BAKROOT%\src\tools > +set INCLUDE=%BAKROOT%\src\tools\bld\inc > +set PATH=%BAKROOT%\src\tools;%PATH% > paul@fedora:~$ > > dosbox > mount d /home/paul/MS-DOS/v4.0 > keyb us > (needed for me... because for me it pass to french keyboard) > d: > cd src > SETENV2.BAT > nmake > > > > ___ > 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] Tools for building old FreeDOS EMM386?
Hello, tom ehlert via Freedos-devel wrote: > > Hello, > > > In freedos/files/dos/emm386/emm/2.2/emms226.zip, its makefile shows it > > need to use sy2pack.exe or sy3pack.exe to pack just-compiled > > emm386.exe. > > sy2pack/sy3pack used to be the only compressor that was able to compress > binaries > that act both as drivers (device=himem.exe) and executable (c:>himem.exe > /test) I think it can benefit other hybrid drivers (for example JEMMX/JEMM386). > > Bart Oldemann looked at it and disassembled/reengineered it for UPX. I wonder if the effort is backported to UPX or not? > > > > But where is sy2pack and/or sy3pack? Tried to search in the web finds > > only some posts in FreeDOS ML. > > sy2pack/sy3pack is my private invention and can't be found in the wild. I wonder if they can be released (at least, binary-only) so people can use them on other things? Since it is listed in EMMS*.ZIP's makefile, reproducible builds can't be built without them. > > Tom > Regards, Roy ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Tools for building old FreeDOS EMM386?
Hello, In freedos/files/dos/emm386/emm/2.2/emms226.zip, its makefile shows it need to use sy2pack.exe or sy3pack.exe to pack just-compiled emm386.exe. But where is sy2pack and/or sy3pack? Tried to search in the web finds only some posts in FreeDOS ML. Regards, Roy ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Fwd: lspci (pciutils) for freedos
Eric Auer via Freedos-devel wrote: > > > Hi! > > LSPCI relies on a rather large list of known PCI ID, > which is why I made PCISLEEP long ago: It just has > a small list of known vendors and types, to keep the > installation small :-) It also experiments with PCI > based standby and suspend modes, including VGA ones. > > But of course, having a full LSPCI for DOS would not > hurt either, for more detailed information :-) PCI.IDS is so large that can't even able to put it on a standard 1.44MB floppy uncompressed! > > Eric > > PS: PCISLEEP is written in Assembly language. For a > DOS version of LSPCI, I suggest using BIOS calls or > raw I/O and keeping the rest in original LSPCI style. > > > > > Hi Pali, > > > > I will forward your message regarding lspci to the FreeDOS mailinglist. > > Thanks for sharing this information! > > > > Greetings, Bernd > > > >> Anfang der weitergeleiteten Nachricht: > >> > >> Von: Pali Rohár > >> Betreff: lspci (pciutils) for freedos > >> Datum: 9. März 2024 um 12:49:53 MEZ > >> An: Bernd Boeckmann > >> > >> Hello, > >> > >> I read the freedos wiki page contribute > >> https://freedos.sourceforge.io/wiki/index.php/Contribute > >> > >> and I would like to let you know that the "lspci" tool known from the > >> linux which lists and prints information about all PCI devices connected > >> in the system, works also on freedos and the last version now has > >> pre-compiled binaries in the pciutils project page. They are in windows > >> download section, but are compiled with DJGPP toolchain. > >> http://mj.ucw.cz/sw/pciutils/ > >> > >> I saw more questions from users if there is a lspci-like tool for > >> freedos to list PCI devices, so I think that the original lspci can be > >> useful for freedos. Would you consider including it into distribution CD? > >> Note that pciutils library is used by flashrom which is already present. > >> > >> Pali > > > > > > ___ > 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] Problem booting FreeDOS on Book8088 PC-XT laptop
perditionc--- via Freedos-devel wrote: > > On Sun, Feb 4, 2024, 7:39 AM roytam--- via Freedos-devel > wrote: >> >> Hello, >> >> perditionc--- via Freedos-devel wrote: >> > >> > On Sun, Feb 4, 2024, 6:32 AM Eric Auer via Freedos-devel >> > wrote: >> >> >> >> >> >> Hi Jim, >> >> >> >> > I'm glad you're bringing this conversation back to freedos-devel .. >> >> > because this is a good place to discuss FreeDOS things. >> >> >> >> In related news, the dosemu2 people also find the problem interesting. >> >> >> ... >> >> You don't need a real Book8088 for testing. 86Box "Xi8088" machine >> with XT-IDE(CHS=1006/16/63) can reproduce this bug. >> >> > >> > Jeremy >> > >> >> Regards, >> Roy > > > Thank you. I will try that out, I need to test the cpu check logic anyway. > (It was more my excuse to get one :-) as my 808x hasn't been powered on in so > long I'm afraid it might need some work beyond the hard drive which died long > ago) and as discussion in http://www.bttr-software.de/forum/board_entry.php?id=21061, FreeDOS can boot on Book8088 once FreeDOS' LBA support is disabled. This may because of XT-IDE BIOS and/or Xi8088 BIOS handling when Int 13h,AH=41h running twice by FreeDOS kernel. > > Jeremy > > ___ > 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] Problem booting FreeDOS on Book8088 PC-XT laptop
Hello, perditionc--- via Freedos-devel wrote: > > On Sun, Feb 4, 2024, 6:32 AM Eric Auer via Freedos-devel > wrote: >> >> >> Hi Jim, >> >> > I'm glad you're bringing this conversation back to freedos-devel .. >> > because this is a good place to discuss FreeDOS things. >> >> In related news, the dosemu2 people also find the problem interesting. >> >> Their discussion mentions that FDPP, a port of the FreeDOS kernel, >> >> https://github.com/dosemu2/fdpp >> >> fixes plenty of issues listed in our kernel bug lists. So maybe >> somebody feels like backporting those to FreeDOS. However, as far >> as I remember, the diff is huge, nothing easily cherry-picked. >> >> Regards, Eric > > > > FDPP is a great project and has done a wonderful job of helping when porting > fixes to fd kernel.sys. If I had more time I'd love to be able to help there > more as I see it as the future for DOS as more and more computers are UEFI > only. I ordered a book8088 (hopefully) so i can test directly, but coming > from China so at least 2 months before delivery. Based on what I've read it > sounds like the drive is booting using CHS and the disk layout doesn't match > what the kernel thinks it is. That said, that specific spot is where boot > time memory corruption usually is noticed and anything the kernel did up to > then could be the culprit. There has been several fixes to the startup > (boot code and initialization) that may or may not be related. (I had hoped > to publish an updated kernel over Christmas but that didn't happen because I > didn't get all the changes and testing I would like done. I hope to put out > an updated kernel for testing next weekend.) You don't need a real Book8088 for testing. 86Box "Xi8088" machine with XT-IDE(CHS=1006/16/63) can reproduce this bug. > > Jeremy > Regards, Roy ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
