Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license
On Thu, 2 May 2024, Liam Proven via Freedos-devel wrote: On Fri, 26 Apr 2024 at 08:25, Steve Nickolas via Freedos-devel wrote: Everything but himem, dosshell, gwbasic, and parts of xmaem/xma2ems, apparently. I got most of it compiled using the tools in the archive. That being the case, is it possible to get it working with 386MAX instead, as that's now FOSS as well? https://github.com/sudleyplace/386MAX I've never seen it rolled, so I can't say if the current code will work on DOS 4, but 8.03 does. -uso. ___ 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
On Fri, 26 Apr 2024 at 08:25, Steve Nickolas via Freedos-devel wrote: > Everything but himem, dosshell, gwbasic, and parts of xmaem/xma2ems, > apparently. I got most of it compiled using the tools in the archive. That being the case, is it possible to get it working with 386MAX instead, as that's now FOSS as well? https://github.com/sudleyplace/386MAX -- Liam Proven ~ Profile: https://about.me/liamproven Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com Twitter/LinkedIn: lproven ~ Skype: liamproven IoM: (+44) 7624 277612: UK: (+44) 7939-087884 Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053 ___ 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
On Thu, 2 May 2024, Eric Auer via Freedos-devel wrote: Hi! I have no life - I can devote the time and energy to it, just don't have the brainpower I'd like to think I have. I hope that will get better :-o Eric Well, I certainly know more about C, 8088 ASM, and MS-DOS than I did going into this thing about 25 years ago... holy hell, I was a n00b then :P -uso. ___ 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
Hi! I have no life - I can devote the time and energy to it, just don't have the brainpower I'd like to think I have. I hope that will get better :-o Eric ___ 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
On Tue, 30 Apr 2024, tom ehlert via Freedos-devel wrote: I have no idea why I would recompile old MS stuff, but as a hobby it's ok. 6.21 would be much more useful and no doubt a lot more people would want to do what I'm trying to do for 4.01 with a 6.21 source drop. (Even 5.0 would be more useful. But really only for io.sys, msdos.sys and command.com. Then...same for 6.2) I have no life - I can devote the time and energy to it, just don't have the brainpower I'd like to think I have. JWASM is supposed to be better MASM compatible; at least Japteth changed some things as he had problems with "WASM not compatible enough". Hmm. -uso. ___ 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
Hallo Herr Steve Nickolas via Freedos-devel, am Dienstag, 30. April 2024 um 17:07 schrieben Sie: > On Tue, 30 Apr 2024, Bernd Böckmann via Freedos-devel wrote: >> Sadly not. Only the binaries are released under MIT through the repository. >> >>> Does that mean we finally have a genuinely open sourced OMF linker? >>> >>> -hpa > It's my opinion that including them was more of a fortuitous accident than > actual intent. I'd _like_ to try to migrate as much as possible away from > them and onto something like OpenWatcom 1.9, but it's proving to be a pain in > the neck. Ideally, I'd like to organize the source a little better too so > that there isn't a lot of stuff being compiled and assembled in the INC > folder. > I started bashing on a copy of the tree, and I started to get stuff rolled in > Watcom, but mainly ran into trouble over parse(), sysloadmsg() and > sysdispmsg(), which are ASM and mostly call into deep, dark, officially > undocumented parts of DOS and could probably be replaced, if I could figure > out what they were doing in the first place... > No luck doing the same with the kernel or any of the other ASM stuff. > Watcom's MASM emulation isn't 5.1-tier. I have no idea why I would recompile old MS stuff, but as a hobby it's ok. JWASM is supposed to be better MASM compatible; at least Japteth changed some things as he had problems with "WASM not compatible enough". Tom ___ 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
On Tue, 30 Apr 2024, Bernd Böckmann via Freedos-devel wrote: Sadly not. Only the binaries are released under MIT through the repository. Does that mean we finally have a genuinely open sourced OMF linker? -hpa It's my opinion that including them was more of a fortuitous accident than actual intent. I'd _like_ to try to migrate as much as possible away from them and onto something like OpenWatcom 1.9, but it's proving to be a pain in the neck. Ideally, I'd like to organize the source a little better too so that there isn't a lot of stuff being compiled and assembled in the INC folder. I started bashing on a copy of the tree, and I started to get stuff rolled in Watcom, but mainly ran into trouble over parse(), sysloadmsg() and sysdispmsg(), which are ASM and mostly call into deep, dark, officially undocumented parts of DOS and could probably be replaced, if I could figure out what they were doing in the first place... No luck doing the same with the kernel or any of the other ASM stuff. Watcom's MASM emulation isn't 5.1-tier. -uso.___ 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
Sadly not. Only the binaries are released under MIT through the repository. > Does that mean we finally have a genuinely open sourced OMF linker? > > -hpa > ___ 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
On Sun, Apr 28, 2024 at 4:33 PM Han Held via Freedos-devel wrote: > > For anyone interested, Neozeed has a youtube video that he put up that walks > through the steps of fetching dos 4's source from github and building a > bootable copy of it. > [Compiling MS-DOS 4.0 using DOSbox & Qemu] > I also posted a video on the FreeDOS YouTube channel, earlier today, showing how to MS-DOS 4.00 on FreeDOS. (All credit to ecm's fixes.) This uses a fresh, vanilla FreeDOS 1.3 "plain DOS" install, with the FDAUTO.BAT file replaced with a single PATH statement (only because I didn't need all the other stuff to do the build). https://youtu.be/X7r76V_gWQ8 ___ 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
For anyone interested, Neozeed has a youtube video that he put up that walks through the steps of fetching dos 4's source from github and building a bootable copy of it. Compiling MS-DOS 4.0 using DOSbox & Qemu | | | | | | | | | | | Compiling MS-DOS 4.0 using DOSbox & Qemu | | | On Saturday, April 27, 2024 at 09:44:36 PM AKDT, Paul Dufresne via Freedos-devel wrote: paul@fedora:~/MS-DOS/v4.0/src$ LANG=C diff OUTBIN/ /run/media/paul/2A43-1BF3/|grep -v ^Only Binary files OUTBIN/LCD.CPI and /run/media/paul/2A43-1BF3/LCD.CPI differ Binary files OUTBIN/SELECT.DAT and /run/media/paul/2A43-1BF3/SELECT.DAT differ Binary files OUTBIN/SELECT.EXE and /run/media/paul/2A43-1BF3/SELECT.EXE differ paul@fedora:~/MS-DOS/v4.0/src$ Install disk was ok. ___ 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] MS-DOS 4.0 source released as open source under MIT license
paul@fedora:~/MS-DOS/v4.0/src$ LANG=C diff OUTBIN/ /run/media/paul/2A43-1BF3/|grep -v ^Only Binary files OUTBIN/LCD.CPI and /run/media/paul/2A43-1BF3/LCD.CPI differ Binary files OUTBIN/SELECT.DAT and /run/media/paul/2A43-1BF3/SELECT.DAT differ Binary files OUTBIN/SELECT.EXE and /run/media/paul/2A43-1BF3/SELECT.EXE differ paul@fedora:~/MS-DOS/v4.0/src$ Install disk was ok. ___ 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
I compared with Linux diff command files from https://winworldpc.com/download/d93cf841-4562-11eb-b764-028a0da4 and the one I compiled... had not compare all files, but the one I compared were identical (operating disk 1-3) Had to edit one to make sure it detect the diff. ___ 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
Now, frankly, I feel stupid, because I think I would need a binary disk of MS-DOS 4.0 to test the binary files of MS-DOS 4.0 I compiled. I guess this is where your bootimg.asm script and: > nasm -I ../../lmacros/ -I ../../bootimg/ ../../bootimg/bootimg.asm -D_PAYLOADFILE="io.sys,msdos.sys,mem.exe,sys.com,../../ldebug/bin/callver.com,::rename,../../../.dosemu/drive_c/command.com,freecom.exe,command.com" -o disk.img -D_MEDIAID=0F8h -D_BPE=16 -D_ERROR_SMALL32=0 -D_SPF=256 -D_SPI=128000 -D_SPC=2 -D_MBR -D_MBR_PART_TYPE=fat16_chs -D_CHS_HEADS=128 -D_CHS_SECTORS=32 -D_OEM_NAME="'IBM 3.1'" magic line have a role to play.___ 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] MS-DOS 4.0 source released as open source under MIT license
May as well show the result: mkdir outbin cpy outbin cd outbin edlin.com result in Incorrect DOS version In Linux: paul@fedora:~/MS-DOS/v4.0/src$ ls -lh OUTBIN total 1,3M -rw-r--r--. 1 paul paul 6,3K 27 avr 21:51 4201.CPI -rw-r--r--. 1 paul paul 720 27 avr 21:51 4208.CPI -rw-r--r--. 1 paul paul 370 27 avr 21:51 5202.CPI -rw-r--r--. 1 paul paul 8,9K 27 avr 21:51 ANSI.SYS -rw-r--r--. 1 paul paul 11K 27 avr 21:51 APPEND.EXE -rw-r--r--. 1 paul paul 5,7K 27 avr 21:51 ASSIGN.COM -rw-r--r--. 1 paul paul 18K 27 avr 21:51 ATTRIB.EXE -rw-r--r--. 1 paul paul 37K 27 avr 21:51 BACKUP.COM -rw-r--r--. 1 paul paul 18K 27 avr 21:51 CHKDSK.COM -rw-r--r--. 1 paul paul 37K 27 avr 21:51 COMMAND.COM -rw-r--r--. 1 paul paul 9,3K 27 avr 21:51 COMP.COM -rw-r--r--. 1 paul paul 13K 27 avr 21:51 COUNTRY.SYS -rw-r--r--. 1 paul paul 22K 27 avr 21:51 DEBUG.COM -rw-r--r--. 1 paul paul 9,7K 27 avr 21:51 DISKCOMP.COM -rw-r--r--. 1 paul paul 11K 27 avr 21:51 DISKCOPY.COM -rw-r--r--. 1 paul paul 16K 27 avr 21:51 DISPLAY.SYS -rw-r--r--. 1 paul paul 5,2K 27 avr 21:51 DRIVER.SYS -rw-r--r--. 1 paul paul 14K 27 avr 21:51 EDLIN.COM -rw-r--r--. 1 paul paul 48K 27 avr 21:51 EGA.CPI -rw-r--r--. 1 paul paul 86K 27 avr 21:51 EMM386.SYS -rw-r--r--. 1 paul paul 7,8K 27 avr 21:51 EXE2BIN.EXE -rw-r--r--. 1 paul paul 17K 27 avr 21:51 FASTOPEN.EXE -rw-r--r--. 1 paul paul 16K 27 avr 21:51 FC.EXE -rw-r--r--. 1 paul paul 60K 27 avr 21:51 FDISK.EXE -rw-r--r--. 1 paul paul 11K 27 avr 21:51 FILESYS.EXE -rw-r--r--. 1 paul paul 5,9K 27 avr 21:51 FIND.EXE -rw-r--r--. 1 paul paul 23K 27 avr 21:51 FORMAT.COM -rw-r--r--. 1 paul paul 10K 27 avr 21:51 GRAFTABL.COM -rw-r--r--. 1 paul paul 17K 27 avr 21:51 GRAPHICS.COM -rw-r--r--. 1 paul paul 9,2K 27 avr 21:51 GRAPHICS.PRO -rw-r--r--. 1 paul paul 22K 27 avr 21:51 IFSFUNC.EXE -rw-r--r--. 1 paul paul 33K 27 avr 21:51 IO.SYS -rw-r--r--. 1 paul paul 18K 27 avr 21:51 JOIN.EXE -rw-r--r--. 1 paul paul 15K 27 avr 21:51 KEYB.COM -rw-r--r--. 1 paul paul 23K 27 avr 21:51 KEYBOARD.SYS -rw-r--r--. 1 paul paul 4,4K 27 avr 21:51 LABEL.COM -rw-r--r--. 1 paul paul 11K 27 avr 21:51 LCD.CPI -rw-r--r--. 1 paul paul 20K 27 avr 21:51 MEM.EXE -rw-r--r--. 1 paul paul 23K 27 avr 21:51 MODE.COM -rw-r--r--. 1 paul paul 2,1K 27 avr 21:51 MORE.COM -rw-r--r--. 1 paul paul 37K 27 avr 21:51 MSDOS.SYS -rw-r--r--. 1 paul paul 6,8K 27 avr 21:51 NLSFUNC.EXE -rw-r--r--. 1 paul paul 14K 27 avr 21:51 PRINT.COM -rw-r--r--. 1 paul paul 19K 27 avr 21:51 PRINTER.SYS -rw-r--r--. 1 paul paul 8,1K 27 avr 21:51 RAMDRIVE.SYS -rw-r--r--. 1 paul paul 11K 27 avr 21:51 RECOVER.COM -rw-r--r--. 1 paul paul 19K 27 avr 21:51 REPLACE.EXE -rw-r--r--. 1 paul paul 37K 27 avr 21:51 RESTORE.COM -rw-r--r--. 1 paul paul 3,6K 27 avr 21:51 SELECT.COM -rw-r--r--. 1 paul paul 24K 27 avr 21:51 SELECT.DAT -rw-r--r--. 1 paul paul 93K 27 avr 21:51 SELECT.EXE -rw-r--r--. 1 paul paul 29K 27 avr 21:51 SELECT.HLP -rw-r--r--. 1 paul paul 1,3K 27 avr 21:51 SELECT.PRT -rw-r--r--. 1 paul paul 14K 27 avr 21:51 SHARE.EXE -rw-r--r--. 1 paul paul 10K 27 avr 21:51 SMARTDRV.SYS -rw-r--r--. 1 paul paul 5,8K 27 avr 21:51 SORT.EXE -rw-r--r--. 1 paul paul 19K 27 avr 21:51 SUBST.EXE -rw-r--r--. 1 paul paul 12K 27 avr 21:51 SYS.COM -rw-r--r--. 1 paul paul 6,2K 27 avr 21:51 TREE.COM -rw-r--r--. 1 paul paul 17K 27 avr 21:51 XCOPY.EXE -rw-r--r--. 1 paul paul 29K 27 avr 21:51 XMA2EMS.SYS -rw-r--r--. 1 paul paul 19K 27 avr 21:51 XMAEM.SYS paul@fedora:~/MS-DOS/v4.0/src$___ 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
Using nmake > OUT.TXT I have at the end of OUT.TXT: cd ..\xmaem nmake nosrvbld xmaem.skl ..\..\messages\usa-ms.msg Creating .CT? files for xmaem.skl using ..\..\messages\usa-ms.msg file of messages. SKL, MSG and IDX files have been opened for reading. Writing to xmaem.cl1 Message files for xmaem.skl completed. masm -Mx -t -I. -I..\..\inc -I..\..\dos INDEmsg.asm,INDEmsg.obj; link @xmaem.lnk Microsoft (R) Overlay Linker Version 3.65 Copyright (C) Microsoft Corp 1983-1988. All rights reserved. Object Modules [.OBJ]: INDEINI+ Object Modules [.OBJ]: INDEEXC+ Object Modules [.OBJ]: INDEEMU+ Object Modules [.OBJ]: INDEXMA+ Object Modules [.OBJ]: INDEDMA+ Object Modules [.OBJ]: INDEI15+ Object Modules [.OBJ]: INDEIDT+ Object Modules [.OBJ]: INDEGDT+ Object Modules [.OBJ]: INDEMSG+ Object Modules [.OBJ]: INDEPAT Run File [INDEINI.EXE]: XMAEM.SYS List File [NUL.MAP]: NUL; LINK : warning L4021: no stack segment cd .. cd ..\select nmake cd ..\memm nmake cd emm nmake cd ..\memm nmake link /NOI @emm386.lnk Microsoft (R) Overlay Linker Version 3.65 Copyright (C) Microsoft Corp 1983-1988. All rights reserved. Object Modules [.OBJ]: MEMM386+ Object Modules [.OBJ]: ELIMFUNC+ Object Modules [.OBJ]: EMM+ Object Modules [.OBJ]: EMMMES+ Object Modules [.OBJ]: EMMINIT+ Object Modules [.OBJ]: MEMMONF+ Object Modules [.OBJ]: INIT+ Object Modules [.OBJ]: M_STATE+ Object Modules [.OBJ]: ROM_SRCH+ Object Modules [.OBJ]: PPAGE+ Object Modules [.OBJ]: ALLOCMEM+ Object Modules [.OBJ]: INITTAB+ Object Modules [.OBJ]: SHIPHI+ Object Modules [.OBJ]: EXTPOOL+ Object Modules [.OBJ]: VDMINIT+ Object Modules [.OBJ]: I286+ Object Modules [.OBJ]: I386+ Object Modules [.OBJ]: TABDEF+ Object Modules [.OBJ]: TRAPDEF+ Object Modules [.OBJ]: VMTRAP+ Object Modules [.OBJ]: VMINST+ Object Modules [.OBJ]: ELIMTRAP+ Object Modules [.OBJ]: IOTRAP+ Object Modules [.OBJ]: A20TRAP+ Object Modules [.OBJ]: OEMPROC+ Object Modules [.OBJ]: INITEPG+ Object Modules [.OBJ]: VMINIT+ Object Modules [.OBJ]: EM286LL+ Object Modules [.OBJ]: EM386LL+ Object Modules [.OBJ]: MOVEB+ Object Modules [.OBJ]: MAPLIN+ Object Modules [.OBJ]: RETREAL+ Object Modules [.OBJ]: RRTRAP+ Object Modules [.OBJ]: ERRHNDLR+ Object Modules [.OBJ]: EKBD+ Object Modules [.OBJ]: UTIL+ Object Modules [.OBJ]: INITDEB+ Object Modules [.OBJ]: MAPDMA Run File [MEMM386.EXE]: EMM386.EXE List File [NUL.MAP]: EMM386.MAP/M Libraries [.LIB]: ..\EMM\EMMLIB.LIB del emm386.sys ren emm386.exe emm386.sys cd .. cd .. As the Makefile finish with: cd ..\memm $(make) cd .. maybe it finished normally after all. ___ 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
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] ... 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
Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license
all GITHUB files have LF line endings. as old MSDOS tools insist on CRLF line endings, you have to convert the files first. Tom ___ 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
To correct myself: I was getting a bunch of unrelated errors because I made a mistake in my SETENV.BAT file. I set the CL, LINK, and MASM variables to point to the executables (similar to what you might do on Unix makefiles with CC, CFLAGS, etc) But those variables are options to those commands (like DIRCMD) so that was causing additional garbage. If I clear out the CL, LINK, and MASM variables, my build attempt fails in the same way that the OS/2 Museum does. But hey, MS-DOS Edlin builds correctly - so there's that! But it won't run on FreeDOS because "Incorrect DOS version." :-) ___ 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
On at 2024-04-26 14:28 -0500, Jim Hall via Freedos-devel wrote: On Fri, 26 Apr 2024, Bernd Böckmann via Freedos-devel wrote: Microsoft and IBM released the source code of MS-DOS 4.0 under MIT license [1]. To me, it looks fairly complete. On Fri, Apr 26, 2024 at 2:25 AM Steve Nickolas via Freedos-devel wrote: Everything but himem, dosshell, gwbasic, and parts of xmaem/xma2ems, apparently. I got most of it compiled using the tools in the archive. How did you compile it? I'm having trouble getting the compile to work. Here's what I'm doing: I've booted my system using FreeDOS but using their tools. My C: drive is FreeDOS, and my D: drive is empty except for the SRC directory from the MS-DOS 4.0 release on GitHub. I set up my environment by editing the SETENV.BAT and running it: @echo off echo setting up system to build the MS-DOS 4.01 SOURCE BAK... set COUNTRY=usa-ms set BAKROOT=D: rem BAKROOT points to the home drive/directory of the sources. set LIB=%BAKROOT%\src\lib set INIT=%BAKROOT%\src\tools set INCLUDE=%BAKROOT%\src\inc set PATH=%BAKROOT%\src\tools;C:\freedos\bin set CL=%INIT%\CL.EXE set LINK=%INIT%\LINK.EXE set MASM=%INIT%\MASM.EXE This is my PATH: D:\>path PATH=D:\src\tools;C:\freedos\bin Yes, I'm really running the Microsoft NMAKE from their tree: D:\>nmake Microsoft (R) Program Maintenance Utility Version 1.00.05 Copyright (c) Microsoft Corp 1987, 1988. All rights reserved. NMAKE : fatal error U1051: usage : 'NMAKE' [-bcdeinpqrst -f makefile -x stderrfi le] [macrodefs] [targets] Stop. But when I try to build it, it fails in the MAPPER directory with "line too long": D:\>cd src D:\SRC>nmake I had similar errors, in mapper/getmsg.asm, select/select2.asm, and select/usa.inf For me these turned out to be errors involving a single-byte character being expanded to a three-byte UTF-8 encoded value. When nearly a whole line (of 80 columns) is filled with these EF BF BD strings then MASM (the version shipped with the repo) doesn't like the total line length in bytes. I eventually fixed this by running: (After manually deleting a few lines to work around the problem.) > sed -i -re 's/\xEF\xBF\xBD|\xC4\xBF|\xC4\xB4/#/g' FILENAMES... I had many more errors, starting with nosrvbld.exe running on eg boot/boot.skl complaining it couldn't find something. The something was named as a bunch of gibberish text however. This, and some other problems, turned out to be because git and/or Microsoft spat out text files with LF line endings whereas many of the DOS tools expect CR LF line endings. The following command worked for me: > find -iname '*.bat' -o -iname '*.asm' -o -iname '*.skl' -o -iname 'zero.dat' -o -iname 'locscr' | xargs unix2dos -f (The zero.dat and locscr files are used to redirect numbers into exe2bin's relocation number prompt. Failure to unix2dos those ended up hanging dosemu2 and/or ConnectBot, and spamming notifications to ConnectBot. Likely related to the old problem of int 21h service 0Ah not properly detecting and handling an EOF.) To successfully compile the C program parts, I had to fix the setenv.bat script (apart from using another drive) to point to the headers and libraries that actually ship with the repo: $ cat src/e.bat @echo off echo setting up system to build the MS-DOS 4.01 SOURCE BAK... set CL= set LINK= set MASM= set COUNTRY=usa-ms set BAKROOT=e: rem BAKROOT points to the home drive/directory of the sources. set LIB=%BAKROOT%\src\tools\bld\lib set INIT=%BAKROOT%\src\tools set INCLUDE=%BAKROOT%\src\tools\bld\inc set PATH=%BAKROOT%\src\tools;%PATH% To boot the kernel, I used lDebug's command BOOT PROTOCOL MSDOS6 hda1/ to boot off a file system that I created using my bootimg.asm script. I had to set -D_OEM_NAME="'IBM 3.1'" to make the kernel accept my file system; with my default it calculated a wrong (at least) Sectors per Cluster value of 4 and failed to load the DOS module. This is my command line to create the image: > nasm -I ../../lmacros/ -I ../../bootimg/ ../../bootimg/bootimg.asm -D_PAYLOADFILE="io.sys,msdos.sys,mem.exe,sys.com,../../ldebug/bin/callver.com,::rename,../../../.dosemu/drive_c/command.com,freecom.exe,command.com" -o disk.img -D_MEDIAID=0F8h -D_BPE=16 -D_ERROR_SMALL32=0 -D_SPF=256 -D_SPI=128000 -D_SPC=2 -D_MBR -D_MBR_PART_TYPE=fat16_chs -D_CHS_HEADS=128 -D_CHS_SECTORS=32 -D_OEM_NAME="'IBM 3.1'" Regards, ecm ___ 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
Jim Hall wrote: [..] > > But when I try to build it, it fails in the MAPPER directory with > > "line too long": > > [..] > >> cd ..\mapper > >> nmake > >> > >> Microsoft (R) Program Maintenance Utility Version 1.00.05 > >> Copyright (c) Microsoft Corp 1987, 1988. All rights reserved. > >> > >> masm -Mx -t -I. -I..\inc -I..\dos chdir.asm,chdir.obj; > >> D:\src\tools\MASM.EXE(1): error A2106: Line too long > Robert Riebisch wrote: > UTF-8 conversion is the culprit: > https://www.os2museum.com/wp/how-not-to-release-historic-source-code/ Well, that's unfortunate. But at least it's not just me. Before I saw your reply, I also realized that the source files were converted to UNIX LF ending (missing CR) so I ran unix2dos on Linux using 'find' to get all the *.INC and *.ASM files: unix2dos -f -ascii -437 ..but that didn't help. I'm kind of busy with other things, so I'm not going to throw myself at this. But please share if they provide a fixed version. ___ 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
Hi Jim, >> D:\>nmake >> >> Microsoft (R) Program Maintenance Utility Version 1.00.05 >> Copyright (c) Microsoft Corp 1987, 1988. All rights reserved. >> >> NMAKE : fatal error U1051: usage : 'NMAKE' [-bcdeinpqrst -f makefile -x >> stderrfi >> le] [macrodefs] [targets] >> Stop. > > > But when I try to build it, it fails in the MAPPER directory with > "line too long": > >> D:\>cd src >> D:\SRC>nmake >> >> Microsoft (R) Program Maintenance Utility Version 1.00.05 >> Copyright (c) Microsoft Corp 1987, 1988. All rights reserved. >> >> cd messages >> nmake >> >> Microsoft (R) Program Maintenance Utility Version 1.00.05 >> Copyright (c) Microsoft Corp 1987, 1988. All rights reserved. >> >> attrib -R usa-ms.msg >> buildidx usa-ms.msg >> Index file and message file are of different levels. >> Message file and index file will be updated. >> Message file updated. >> Index file updated. >> attrib +R usa-ms.msg >> cd ..\mapper >> nmake >> >> Microsoft (R) Program Maintenance Utility Version 1.00.05 >> Copyright (c) Microsoft Corp 1987, 1988. All rights reserved. >> >> masm -Mx -t -I. -I..\inc -I..\dos chdir.asm,chdir.obj; >> D:\src\tools\MASM.EXE(1): error A2106: Line too long [snip] UTF-8 conversion is the culprit: https://www.os2museum.com/wp/how-not-to-release-historic-source-code/ Cheers, Robert -- BTTR Software https://www.bttr-software.de/ DOS ain't dead https://www.bttr-software.de/forum/ ___ 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
On Fri, Apr 26, 2024 at 2:28 PM Jim Hall wrote: > [..] > How did you compile it? I'm having trouble getting the compile to work. > > Here's what I'm doing: I've booted my system using FreeDOS but using > their tools. My C: drive is FreeDOS, and my D: drive is empty except > for the SRC directory from the MS-DOS 4.0 release on GitHub. I set up > my environment by editing the SETENV.BAT and running it: > [..] > > It's interesting that line 1 of CHDIR.ASM is just an empty ";" comment > (line 1 is 1 character long) so I don't get why MASM says line 1 is > too long. Also interesting is that when the build fails, CHDIR.ASM has been deleted: > D:\SRC\MAPPER>dir chdir.* > Volume in drive D is MSDOS4 > Volume Serial Number is 3353-1607 > > Directory of D:\SRC\MAPPER > > CHDIROBJ14,702 04-26-24 6:53p > 1 file(s) 14,702 bytes > 0 dir(s) 489,603,072 bytes free ___ 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
> On Fri, 26 Apr 2024, Bernd Böckmann via Freedos-devel wrote: > > > Microsoft and IBM released the source code of MS-DOS 4.0 under MIT > > license [1]. To me, it looks fairly complete. On Fri, Apr 26, 2024 at 2:25 AM Steve Nickolas via Freedos-devel wrote: > > Everything but himem, dosshell, gwbasic, and parts of xmaem/xma2ems, > apparently. I got most of it compiled using the tools in the archive. How did you compile it? I'm having trouble getting the compile to work. Here's what I'm doing: I've booted my system using FreeDOS but using their tools. My C: drive is FreeDOS, and my D: drive is empty except for the SRC directory from the MS-DOS 4.0 release on GitHub. I set up my environment by editing the SETENV.BAT and running it: @echo off echo setting up system to build the MS-DOS 4.01 SOURCE BAK... set COUNTRY=usa-ms set BAKROOT=D: rem BAKROOT points to the home drive/directory of the sources. set LIB=%BAKROOT%\src\lib set INIT=%BAKROOT%\src\tools set INCLUDE=%BAKROOT%\src\inc set PATH=%BAKROOT%\src\tools;C:\freedos\bin set CL=%INIT%\CL.EXE set LINK=%INIT%\LINK.EXE set MASM=%INIT%\MASM.EXE This is my PATH: > D:\>path > PATH=D:\src\tools;C:\freedos\bin Yes, I'm really running the Microsoft NMAKE from their tree: > D:\>nmake > > Microsoft (R) Program Maintenance Utility Version 1.00.05 > Copyright (c) Microsoft Corp 1987, 1988. All rights reserved. > > NMAKE : fatal error U1051: usage : 'NMAKE' [-bcdeinpqrst -f makefile -x > stderrfi > le] [macrodefs] [targets] > Stop. But when I try to build it, it fails in the MAPPER directory with "line too long": > D:\>cd src > D:\SRC>nmake > > Microsoft (R) Program Maintenance Utility Version 1.00.05 > Copyright (c) Microsoft Corp 1987, 1988. All rights reserved. > > cd messages > nmake > > Microsoft (R) Program Maintenance Utility Version 1.00.05 > Copyright (c) Microsoft Corp 1987, 1988. All rights reserved. > > attrib -R usa-ms.msg > buildidx usa-ms.msg > Index file and message file are of different levels. > Message file and index file will be updated. > Message file updated. > Index file updated. > attrib +R usa-ms.msg > cd ..\mapper > nmake > > Microsoft (R) Program Maintenance Utility Version 1.00.05 > Copyright (c) Microsoft Corp 1987, 1988. All rights reserved. > > masm -Mx -t -I. -I..\inc -I..\dos chdir.asm,chdir.obj; > D:\src\tools\MASM.EXE(1): error A2106: Line too long > D:\src\tools\MASM.EXE(10): error A2106: Line too long > D:\src\tools\MASM.EXE(11): error A2106: Line too long > D:\src\tools\MASM.EXE(13): error A2106: Line too long > D:\src\tools\MASM.EXE(19): error A2106: Line too long > D:\src\tools\MASM.EXE(31): error A2106: Line too long > D:\src\tools\MASM.EXE(34): error A2106: Line too long > D:\src\tools\MASM.EXE(36): error A2106: Line too long > D:\src\tools\MASM.EXE(38): error A2106: Line too long > D:\src\tools\MASM.EXE(40): error A2106: Line too long > D:\src\tools\MASM.EXE(41): error A2106: Line too long > D:\src\tools\MASM.EXE(47): error A2106: Line too long > D:\src\tools\MASM.EXE(48): error A2106: Line too long > D:\src\tools\MASM.EXE(77): error A2106: Line too long > D:\src\tools\MASM.EXE(88): error A2106: Line too long > D:\src\tools\MASM.EXE(114): error A2106: Line too long > D:\src\tools\MASM.EXE(120): error A2106: Line too long > D:\src\tools\MASM.EXE(127): error A2106: Line too long > D:\src\tools\MASM.EXE(141): error A2106: Line too long > D:\src\tools\MASM.EXE(142): error A2106: Line too long > D:\src\tools\MASM.EXE(150): error A2106: Line too long > D:\src\tools\MASM.EXE(154): error A2106: Line too long > D:\src\tools\MASM.EXE(156): error A2106: Line too long > D:\src\tools\MASM.EXE(164): error A2106: Line too long > D:\src\tools\MASM.EXE(165): error A2106: Line too long > D:\src\tools\MASM.EXE(166): error A2106: Line too long > D:\src\tools\MASM.EXE(167): error A2106: Line too long > D:\src\tools\MASM.EXE(168): error A2106: Line too long > D:\src\tools\MASM.EXE(169): error A2106: Line too long > D:\src\tools\MASM.EXE(171): error A2106: Line too long > D:\src\tools\MASM.EXE(172): error A2106: Line too long > D:\src\tools\MASM.EXE(174): error A2106: Line too long > D:\src\tools\MASM.EXE(184): error A2106: Line too long > D:\src\tools\MASM.EXE(185): error A2106: Line too long > D:\src\tools\MASM.EXE(188): error A2106: Line too long > D:\src\tools\MASM.EXE(194): error A2106: Line too long > D:\src\tools\MASM.EXE(202): error A2106: Line too long > D:\src\tools\MASM.EXE(207): error A2106: Line too long > D:\src\tools\MASM.EXE(218): error A2106: Line too long > D:\src\tools\MASM.EXE(219): error A2106: Line too long > D:\src\tools\MASM.EXE(231): error A2106: Line too long > D:\src\tools\MASM.EXE(237): error A2106: Line too long > D:\src\tools\MASM.EXE(239): error A2106: Line too long > D:\src\tools\MASM.EXE(241): error A2106: Line too long > D:\src\tools\MASM.EXE(246): error A2106: Line too long > D:\src\tools\MASM.EXE(251): error A2106: Line too
Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license
> Am 26.04.2024 um 09:08 schrieb Steve Nickolas via Freedos-devel > : > > I got most of it compiled using the tools in the archive. Side effect of having these tools in the repo is that these are released under MIT license too, espectially: - MASM 5.1 - Microsoft LINK 3.65 - Microsoft C 5.1 (without standard C library) ___ 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
On Fri, 26 Apr 2024, Eric Auer via Freedos-devel wrote: As mentioned by DOSEMU2 people, this is a somewhat exotic, but interesting MS DOS 4.00, not the once widespread 4.01: Actually, apart from having the io.sys sources to the multitasking 4, this is the regular 4.x line from 1988. Most of the binaries in 4.01 didn't change at all from 4.00, as a SFV of both versions will reveal. -uso. ___ 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
On Fri, 26 Apr 2024, Bernd Böckmann via Freedos-devel wrote: Microsoft and IBM released the source code of MS-DOS 4.0 under MIT license [1]. To me, it looks fairly complete. Everything but himem, dosshell, gwbasic, and parts of xmaem/xma2ems, apparently. I got most of it compiled using the tools in the archive. -uso.___ 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
Much more interesting is the multitasking version: https://github.com/microsoft/MS-DOS/tree/main/v4.0-ozzie =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Remitente:Eric Auer via Freedos-devel Destinatario: freedos-devel@lists.sourceforge.net Fecha:viernes, 26 de abril de 2024, 8:23:03 Asunto: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license Archivos: --===-- Hi Bernd, > Microsoft and IBM released the source code of MS-DOS 4.0 > under MIT license [1]. To me, it looks fairly complete. > > Greetings, Bernd > > [1] https://github.com/microsoft/MS-DOS/tree/main/v4.0 As mentioned by DOSEMU2 people, this is a somewhat exotic, but interesting MS DOS 4.00, not the once widespread 4.01: https://cloudblogs.microsoft.com/opensource/2024/04/25/open-sourcing-ms-dos-4-0/ Cheers, Eric ___ 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] MS-DOS 4.0 source released as open source under MIT license
Hi Bernd, Microsoft and IBM released the source code of MS-DOS 4.0 under MIT license [1]. To me, it looks fairly complete. Greetings, Bernd [1] https://github.com/microsoft/MS-DOS/tree/main/v4.0 As mentioned by DOSEMU2 people, this is a somewhat exotic, but interesting MS DOS 4.00, not the once widespread 4.01: https://cloudblogs.microsoft.com/opensource/2024/04/25/open-sourcing-ms-dos-4-0/ Cheers, Eric ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
