Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license

[Paul Dufresne via Freedos-devel]

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

[Paul Dufresne via Freedos-devel]

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

[Paul Dufresne via Freedos-devel]

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]

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

[Paul Dufresne via Freedos-devel]

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

[Paul Dufresne via Freedos-devel]

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 (line endings)

[Paul Dufresne via Freedos-devel]

 Le sam., 27 avr. 2024 05:02:14 -0400 tom ehlert via Freedos-devel  a écrit 


 > all GITHUB files have LF line endings. 
 > as old MSDOS tools insist on CRLF line endings, you have to convert the 
 > files first. 
 >  
 > Tom 

Git handles CRLF conversions... see: 
https://www.codeandweb.com/babeledit/tutorials/how-to-handle-line-endings-in-git


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] I16GCC would need DJGPP, but DJGPP not present in FDT2404 (fixed!)

[Paul Dufresne via Freedos-devel]

But installing I16BUTIIL,

SET DJDIR=C:\DEVEL\I16GNU

i16gcc -o hel2.exe hel2.c

works!



Even printf works now! (only if I16NEWLI is installed)



So in summary, needs I16BUTIl,I16GCC,I16NEWLI (I also have I16GCDOC),

and SET DJDIR=C:\DEVEL\I16GNU

to compile a program with:

i16gcc -o prog.exe prog.c



Thanks... hope it was not too much noise!___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] I16GCC would need DJGPP, but DJGPP not present in FDT2404

[Paul Dufresne via Freedos-devel]

In fact,

SET DJDIR=C:\DONTEXIST

does the same...



SET DJDIR=

i16gcc hel2.c

result in error message environment variable DJGPP is not defined



since first message I have added I16NEWLI package... but it did not seems to 
provide stdio.h like I expected.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] I16GCC would need DJGPP, but DJGPP not present in FDT2404

[Paul Dufresne via Freedos-devel]

It does help, but just a little:



C:\HELLO>SET DJDIR=C:\DEVEL\I16GNU

C:\HELLO>type hel2.c

int main()

{

    return 5;

}

C:\HELLO>i16gcc hel2.c

Exiting due signal SIGSEGV

Page fault at eip=000b0d74 error=0004

...

program=C:\DEVEL\I16GNU\BIN\I16GCC.EXE

...



I have tried to give 128Mb rather than 32 Mb to QEMU machine , but seems to be 
same result.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] I16GCC would need DJGPP, but DJGPP not present in FDT2404

[Paul Dufresne via Freedos-devel]

I tried to install I16GCC from bonus CD of FDT2404.
When I tried to compile a program it says I need to set DJGPP environment 
variable.
https://gitlab.com/tkchia/build-ia16/-/releases says:

"If you get the error message i16gcc.exe: fatal error: environment variable 
DJGPP not defined when running i16gcc.exe, you can do one of the following:

Install the DJGPP base environment first, and then set the DJGPP DOS variable 
to point to its djgpp.env, e.g. set DJGPP=c:\devel\djgpp\djgpp.env. (See 
DJGPP's readme.1st for more information.)
Alternatively, if you do not wish to install DJGPP, just set a DJDIR 
environment variable thus: set DJDIR=c:\devel\djgpp."

Doing "set DJDIR=c:\devel\djgpp" I get stdio.h not found when compiling hello 
world.

And it seems DJGPP is not on FDT2404-BNS.ZIP.

On 1.3, DJGPP programs are listed:
http://ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.3/official/report.html

But not at all in:
http://ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/report.html

What I need to have i16gcc working in FDT2404?

Is DJGPP supposed to be in FDT24040?







___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Calculator for DOS with GUI

[Paul Dufresne via Freedos-devel]

 Le sam., 07 oct. 2023 20:08:05 -0400 Pedro Luis Carballosa Mass via 
Freedos-devel  a écrit 
 > Indeed, but that line can be changed (consider it GNU license), as author I 
 > guarantee that the code can be used to be improved if that serves for 
 > something to someone.  
Then I would suggest you read/use https://www.gnu.org/licenses/gpl-howto.en.html

 > Note: The calculator also use a bit of code shared by others (mouse 
 > subroutines by Andreas Andersson (alhambr...@hotmail.com)) as I mencioned in 
 > the tutorial 
 > (https://cubansolutions.blogspot.com/2022/11/diseno-e-implementacion-de-una-gui.html).
 >   
If it was me, I would probably then only publish the .bas file with that part 
removed... unless you are able to contact him and get the permission to publish 
it.

The code is likely to be interesting to build graphical programs other than a 
calculator, as the calculator seems to mostly be an example of GUI routines.

___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Calculator for DOS with GUI

[Paul Dufresne via Freedos-devel]

 Le ven., 06 oct. 2023 18:02:11 -0400 Jim Hall via Freedos-devel  a écrit 

 > Thanks for sharing your calculator program. However, I cannot run it
 > on FreeDOS. This is the error I get when trying to run CALC16.EXE on
 > FreeDOS:
 > 
 > > Cargando fuente del sistema, por favor, espere...
 > >
 > > Illegal function call in line 0 of module CALC at address 078D:02C0
 > >
 > > Hit any key to return to system
 > 
 > 
 > Perhaps this was compiled to require the BASIC runtime?
 > 
 > I get the error when I'm booting FreeDOS T2310, even if I boot without
 > drivers. I'm running this under QEMU, if that matters (though it
 > shouldn't).
 > 
 > 
 > Jim
 
Although I can confirm the problem with QEMU, it works for me under VirtualBox.

However, because license seems to be just that line:
'*  Copyright (C) 2021 Cuban Solutions   *
Then there is not much we can do with it (apart learning a bit about your way 
of doing Basic).
Maybe take a look at: https://choosealicense.com/
and add a LICENSE.TXT file to the archive (and add a line in CALC.BAS to say it 
is distributed under the license in LICENSE.TXT).___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS Interim Build T2310 - no free space on CD

[Paul Dufresne via Freedos-devel]

--- Le mar., 03 oct. 2023 14:30:08 -0400 Michael Brutman via Freedos-devel  
have written 
 > There is no point in punishing everybody by shipping tools that most people 
 > don't use.  You can probably count all of the active DOS developers on your 
 > fingers and toes.
 > 
 > All of the various tools and compilers remain available for download.  Not 
 > being on the CD image is not the barrier it used to be.
 > 

The only time I downloaded the Bonus CD, was to figure out if it contained only 
binary packages.
The answer was that there was an about 7 Mb FreeDOS distribution 
(kernel+command) with it, but mostly just binary packages.

I continue to plea for a DJGPP (gcc + i16gcc ) optional CD.
Then the price is a storage price, as it is optional, it would benefit only 
people using this (those) compiler.

Downloading the .zip from DJGPP is relatively hard.

Transfering the result to the VM or real FreeDOS machine is quite hard,
as you cannot put it on a USB key and get it from FreeDOS, the more logical 
approach is to build an ISO CD image from the files.
Which is what the GCC CD would be.

Having two systems, the distribution packages, and the medias, is a bit strange 
to me.
My guess I would think that going everything on the medias, make more sense, 
mostly because that there is a build system automating
the making of the packages (rather than a manual process).

So as I see it... there is a little price for people paying for storage and 
bandwith...
and a big price for mostly me, that pretend he/I would maintain the packages on 
Gitlab.
Oh yeah... maybe you are right! ;-)

Part of the reason I am ready to take that price is that I often change my 
active hard disk... and so get to often want a gcc compiler and libraries.
And I know, it is relatively hard to redo the process from DJGPP site.

I admit sites like build-djgpp is usefull... but then there is the problem of 
libraries and tools... and being able to add/remove them as package, is a great 
help.

The more it goes, the more project use gcc and g++... I think I remember Watcom 
C++ did not handle well (if at all) namespaces... so it come necessary to
use gcc. The point of a recent gcc is not to have to think much if a feature is 
supported by the compiler.
Mostly a recent gcc version is very big... but also have all the new features.



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS Interim Build T2310

[Paul Dufresne via Freedos-devel]

 Le dim., 01 oct. 2023 23:21:53 -0400 Jerome Shidel via Freedos-devel  a 
écrit 

 > I’m not a DJGPP user and don’t want to break those packages. So, I’m not 
 > updating them. However, Paul Dufresne was working on the packages in the 
 > FreeDOS archive.
 >Unfortunately, I think that work has stagnated. 
I indeed did not put more than a few hours in last year I fear.
But I was/am kind of waiting to see the next month release hoping to see/test 
my packages, and see how it goes in the release process.
So, it is a bit of a chicken and egg problem.

Thinking maybe I should just build the release myself,
I took a look at:
https://gitlab.com/FreeDOS/OS/builder/-/tree/master/packages?ref_type=heads
was expecting to find a list of packages pull from Gitlab I think... and since 
I did not found that... I did not tried.
But maybe I should just put my zip files downloaded from gitlab in this 
directory... and try it.  (did not download RBE yet).

Was also working for my FreeDOS packager program (now translating to Raku) but 
did not touch that since last time I mentioned it a few days ago.


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : GCC 12.2 for DJGPP 2.05 (was Re: Ré : unstable should be build from unstable branch)

[Paul Dufresne via Freedos-devel]

Don't know why I did not found your message on 
https://www.mail-archive.com/freedos-devel@lists.sourceforge.net/maillist.html .

 Le Thu, 21 Sep 2023 02:49:13 -0400 Rugxulo via Freedos-devel  a écrit 
 > Hi,
 > 
 > On Sun, Sep 17, 2023 at 1:35 PM Jerome Shidel via Freedos-devel
 > freedos-devel@lists.sourceforge.net> wrote:
 > >
 > > On Sep 17, 2023, at 10:56 AM, Paul Dufresne via Freedos-devel 
 > > freedos-devel@lists.sourceforge.net> wrote:
 > >
 > > Title:DJGPP.GCC
 > > Version:  12.2.0
 > > Entered-date: 2022-08-31
 > 
 > Two comments I want to make here:
 > 
 > 1). gcc122b.zip is 51 MB (upstream) and needs (at minimum):
 > bnu2351b.zip (6 MB) and djdev205.zip (2.4 MB) and of course
 > csdpmi7b.zip (70 kb).
 
For me, size is not a big thing...
using FreeDOS under QEMU, have plenty of hard disk space.

I believe it would be appropriate to have a DJGPP gcc bonus "CD".
Because the big size is really because of DJGPP gcc and associated packages.
Maybe include i16gcc (as this is the same source?... unsure).

Was proposed to have a development bonus separate of the rest...
don't remember really what was the conclusion.
 
I tend to think latest version should be better... don't really want
to think too much to which version I need. Last one suppose to work.
That said, often FreeDOS programs are old and are harder to compile
with most recent version... although I remember that there use to
be some command line options to support older projects.

I believe in updating projects to compile with newer versions... so I tend
to think the newest version is the best.

 > And since FreeDOS includes sources, it's going to be much bigger,
 > right?
Gcc is under GPL v.3... I think it is more ok to split to a gcc source package,
and have a gcc binary package only... maybe an ADA binary package too.
I believe it is more ok for v.3 to have a link to source on a server (compare 
to v.2).

> I'm not sure who exactly demands GCC 12.2 over older (smaller)
> versions. And it does not bootstrap atop DOS at all.
Does not bootstrap atop DOS? What you means exactly?

I work(ed) a bit to update to Raku the Perl program to unzip a package from 
Gitlab, and
make a FreeDOS package of it. The part to make
file path to 8:3 is working... but the library to unzip a package seems to need
to unzip the full package, and not be able to unzip a single file at a time, 
like
the Perl version was.
Well, it just because I believe Raku as being more interesting than Perl.
But this means the program will not work on FreeDOS, because there is a
Perl package, not a Raku one... would need some work to make the Raku "VM"
to be ported to FreeDOS DJGPP.

I intend to upload to raku.land/ and when it will work some test files, I 
intend to
post here about it.


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : unstable should be build from unstable branch

[Paul Dufresne via Freedos-devel]

Rereading dates on:

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/unstable/devel/

most packages are not very recent... ldegug is... upx from this year, but other 
relatively old.



I have:

Title:    DJGPP.GCC

Version:  12.2.0

Entered-date: 2022-08-31



The date in the repository is 2022-09-02

so it should have been built with version 12.2 ... I think.



But my idea that all packages are rebuilt automatically each month is clearly 
wrong.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] unstable should be build from unstable branch

[Paul Dufresne via Freedos-devel]

Looks like 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/unstable/devel/dj_gcc.zip

is version 4.71 (mostly just looking at DEVEL\DJGPP \MANIFEST files), so the 
stable branch version from:

https://gitlab.com/FreeDOS/devel/dj_gcc/-/tree/master/DEVEL/DJGPP/MANIFEST

not my unstable branch from:

https://gitlab.com/FreeDOS/devel/dj_gcc/-/tree/unstable/DEVEL/DJGPP/manifest



I did not check other packages yet, but my guess is unstable is probably 
wrongly build from stable (master) branch.



I suppose 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/latest/ 
should be 1.3 at this time.

But I use fdnpkg to install in T2308, and it get it from latest, so I guess I 
need to find out how to have it pull from unstable instead.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Ré : T2308 invalid partition signature after format

[Paul Dufresne via Freedos-devel]

 Le dim., 17 sept. 2023 07:19:23 -0400 Bernd Böckmann via Freedos-devel  a 
écrit 
 > Perhaps we should change the message in the installer to make this more 
 > clear? This problem seems to occur more often than desired. 

I suspect the invalid partition signature is coming from SeaBIOS (QEMU BIOS). 
[Maybe the MBR itself?]

But my guess we could partition and format without rebooting if QEMU is 
detected.
Don't know which hardware need a reboot after partitioning and before 
formating... but I guess that exist.


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : T2308 invalid partition signature after format

[Paul Dufresne via Freedos-devel]

Ok, I figured it out by reading http://reboot.pro/index.php?showtopic=21935



Was booting without -boot order d

which seems to means (when not present): boot from hard disk if it is 
partitioned, else boot from CDROM



So I was going to partitioning hard disk, but when rebooting, it was booting 
from hard disk, showing the previous error.



So I was confused in thinking I had formated hard disk... I had it only 
partitioned. (message was correct, just me bad interpreting it).



I also removed sound stuff, because the way it was doing was to build a .wav 
file... if using for a long time, would have filed disk.



So now I am using:

qemu-system-i386 -name FreeDOS -machine 
pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -enable-kvm -cpu 486 -m 64 
-overcommit mem-lock=off -no-user-config -nodefaults -rtc 
base=utc,driftfix=slew -no-hpet -boot menu=on,strict=on -sandbox 
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg 
timestamp=on -drive format=raw,file=hd.img -vga cirrus -usbdevice mouse -cdrom 
T2308LIVE.iso -boot order=d



and it seems to works fine that way.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : Ré : T2308 invalid partition signature after format

[Paul Dufresne via Freedos-devel]

Sorry, the address was in octal,

with -Ax to have the address in hexa it feels ok to me:

[paul@fedora FDT2308]$ od -Ax -tx1 hd.img
00 fa fc 31 c0 8e d0 8e d8 bd 00 7c 8d 66 e0 fb b8
10 e0 1f 8e c0 89 ee 89 ef b9 00 01 f3 a5 ea 22 7c
20 e0 1f 8e d8 8e d0 31 c0 8e c0 8d be be 01 f6 05
30 80 75 6d 83 c7 10 81 ff fe 7d 72 f2 e8 c4 00 6e
40 6f 20 61 63 74 69 76 65 20 70 61 72 74 69 74 69
50 6f 6e 20 66 6f 75 6e 64 00 eb fe e8 a5 00 72 65
60 61 64 20 65 72 72 6f 72 20 77 68 69 6c 65 20 72
70 65 61 64 69 6e 67 20 64 72 69 76 65 00 eb da e8
80 81 00 70 61 72 74 69 74 69 6f 6e 20 73 69 67 6e
90 61 74 75 72 65 20 21 3d 20 35 35 41 41 00 eb b9
a0 e8 10 00 72 b6 26 81 3e fe 7d 55 aa 75 d1 ea 00
b0 7c 00 00 bb aa 55 b4 41 cd 13 72 32 81 fb 55 aa
c0 75 2c f6 c1 01 74 27 eb 10 10 00 04 00 00 7c 00
d0 00 00 00 00 00 00 00 00 00 8b 45 08 a3 d1 7c 8b
e0 45 0a a3 d3 7c b8 00 42 be c9 7c cd 13 c3 b8 04
f0 02 bb 00 7c 8b 4d 02 8a 75 01 cd 13 c3 31 db b4
000100 0e cd 10 5e ac 56 3c 00 75 f3 c3 00 00 00 00 00
000110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*
0001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 01
0001c0 01 00 0c fe ff ff 3f 00 00 00 c1 fd 1f 00 00 00
0001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*
0001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa
000200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*
007e00 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6
*
009e00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*
4000
[paul@fedora FDT2308]$ 

Signature at the end of 0x1f0 address line, just before 0x200.
I am a bit surprised the signature is also at the end of  0xb0 address line.



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : T2308 invalid partition signature after format

[Paul Dufresne via Freedos-devel]

OTOH, the signature is supposed to be at the end of the first 512 bytes, so 
just before 0x200,

not before 0x300 (768) like it seems to be.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] T2308 invalid partition signature after format

[Paul Dufresne via Freedos-devel]

While trying FDOS Live T2308.iso on QEMU under Fedora 38, I get a D: prompt,

I do setup, format the drive, reboot, but then I get:

partition signature != 55AA



[paul@fedora FDT2308]$ od -tx1 hd.img

000 fa fc 31 c0 8e d0 8e d8 bd 00 7c 8d 66 e0 fb b8

020 e0 1f 8e c0 89 ee 89 ef b9 00 01 f3 a5 ea 22 7c

040 e0 1f 8e d8 8e d0 31 c0 8e c0 8d be be 01 f6 05

060 80 75 6d 83 c7 10 81 ff fe 7d 72 f2 e8 c4 00 6e

100 6f 20 61 63 74 69 76 65 20 70 61 72 74 69 74 69

120 6f 6e 20 66 6f 75 6e 64 00 eb fe e8 a5 00 72 65

140 61 64 20 65 72 72 6f 72 20 77 68 69 6c 65 20 72

160 65 61 64 69 6e 67 20 64 72 69 76 65 00 eb da e8

200 81 00 70 61 72 74 69 74 69 6f 6e 20 73 69 67 6e

220 61 74 75 72 65 20 21 3d 20 35 35 41 41 00 eb b9

240 e8 10 00 72 b6 26 81 3e fe 7d 55 aa 75 d1 ea 00

260 7c 00 00 bb aa 55 b4 41 cd 13 72 32 81 fb 55 aa

300 75 2c f6 c1 01 74 27 eb 10 10 00 04 00 00 7c 00

320 00 00 00 00 00 00 00 00 00 8b 45 08 a3 d1 7c 8b

340 45 0a a3 d3 7c b8 00 42 be c9 7c cd 13 c3 b8 04

360 02 bb 00 7c 8b 4d 02 8a 75 01 cd 13 c3 31 db b4

400 0e cd 10 5e ac 56 3c 00 75 f3 c3 00 00 00 00 00

420 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

*

660 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 01

700 01 00 0c fe ff ff 3f 00 00 00 c1 fd 1f 00 00 00

720 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

*

760 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa

0001000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

*

0077000 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6 f6

*

0117000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

*

100

[paul@fedora FDT2308]$ 

Does the aa55 on line 760 seems ok? Just before 1000, for me it feel ok.



Using:

[paul@fedora FDT2308]$ qemu-system-i386 -name FreeDOS -machine 
pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -enable-kvm -cpu 486 -m 128 
-overcommit mem-lock=off -no-user-config -nodefaults -rtc 
base=utc,driftfix=slew -no-hpet -boot menu=on,strict=on -sandbox 
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg 
timestamp=on -drive format=raw,file=hd.img,format=raw -cdrom T2308LIVE.iso  
-audiodev wav,id=mysnd -device sb16,audiodev=mysnd -device adlib,audiodev=mysnd 
-machine pcspk-audiodev=mysnd  -vga cirrus -usbdevice mouse

VNC server running on ::1:5900



I had installed tigervnc and using:

vncviewer :5900

to see the result (which is a graphical window... I had installed SDL2-devel 
before, not sure it was necessary)...

this way of using vnc is new to me, but on my Fedora 38:

[paul@fedora FDT2308]$ qemu-system-i386 -display help

Available display backend types:

none___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] mode.com

[Paul Dufresne via Freedos-devel]

 Le sam., 18 mars 2023 10:49:48 -0400   a écrit 

 > Hi all,
 > 
 > sometimes trying to write FD help makes me crazy.
 > 
 > Mode is a typical example. At 
 > https://gitlab.com/FreeDOS/base/mode/-/blob/master/DOC/MODE/MODE.TXT
[...]
 > If I understand this right, the actual errorlevels should be like this 
 > (found them at modecp.c - hopefully correct?)
 >

Testing a bit, the only code error I get is 1... (not speaking of 0 for 
success). 



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : How to setup a compiler for FreePascal on Fedora Linux to FreeDOS 16 bit

[Paul Dufresne via Freedos-devel]

Yesterday I said:
>I'll show you the full file... even if I think I might have damage it a bit in 
>the long day:



Indeed fpc (the command lne one for Fedora x64) was not working anymore.

Here is the essential part (not copying back the full ~/.fpc.cfg [where ~ is 
your home directory in Linux]:

#IFDEF CPUI8086

# Must be the crosscompiler to FreeDOS

-Fu/usr/lib64/fpc/$fpcversion/units/msdos/80186-$fpcmemorymodel

-Fu/usr/lib64/fpc/$fpcversion/units/msdos/80186-$fpcmemorymodel/*

-Fu/usr/lib64/fpc/$fpcversion/units/msdos/80186-$fpcmemorymodel/rtl

#ELSE

# Must be the native Linux compiler

-Fu/usr/lib64/fpc/$fpcversion/units/$fpctarget

-Fu/usr/lib64/fpc/$fpcversion/units/$fpctarget/*

-Fu/usr/lib64/fpc/$fpcversion/units/$fpctarget/rtl

#ENDIF



In the #ELSE part, I change lib to lib64, because my Linux is 64 bits so the 
fpc units are there. [had copied verbatim from the website that part]



And now I can use the same config file for both (fpc for native x86-64 Linux 
target, and ppcross8086 for FreeDOS 16 bit target)



[paul@fedora mypas]$ whereis fp

fp: /usr/bin/fp /usr/share/man/man1/fp.1.gz



[paul@fedora mypas]$ dnf provides /usr/bin/fp

Dernière vérification de l’expiration des métadonnées effectuée il y a 1 day, 
3:44:52 le dim 19 mar 2023 16:30:32.

fpc-ide-3.2.2-10.fc38.x86_64 : Free Pascal Compiler - terminal-based IDE

Dépôt       : @System

Correspondances trouvées dans  :

Nom de fichier : /usr/bin/fp



So, fp, the IDE, use a fpc.cfg file in the directory, and create one if it does 
not exist.

So even before fixing my ~/.fpc.cfg file, fp IDE was working for me.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : How to setup a compiler for FreePascal on Fedora Linux to FreeDOS 16 bit

[Paul Dufresne via Freedos-devel]

I said:
 > And now I am realizing that 80186 is kind of too advanced for FreeDos that 
 > prefer 8086... but I think the older
 > FreePascal can do is 80186.

They have done:
[paul@fedora mypas]$ ls /usr/lib64/fpc/3.2.2/units/msdos/
80186-compact  80186-medium  80286-compact  80286-medium  80386-compact  
80386-medium  8086-compact  8086-medium
80186-huge 80186-small   80286-huge 80286-small   80386-huge 
80386-small   8086-huge 8086-small
80186-large80186-tiny80286-large80286-tiny80386-large
80386-tiny8086-large8086-tiny

So they seems to have compiled units for 8086, so it is likely possible to 
compile a cross-compiler to 8086.


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] How to setup a compiler for FreePascal on Fedora Linux to FreeDOS 16 bit

[Paul Dufresne via Freedos-devel]

I am thinking about using FreePascal to write programs for DOS.

Writing an "hello world" program in FreePascal for 32 bit DOS (Go32) is easy, 
because the fpc package can be installed
with fdimples from the Live installer.

But there is no 16 bit FreePascal directly for DOS.
So one have to used some other OS like Windows or Linux, and use a FreePascal 
cross-compiler to 80186  16 bit DOS.
I say 80186, because this is the precompiled version, you would have to compile 
your own cross-compiler for like 386 16 bit DOS.
And now I am realizing that 80186 is kind of too advanced for FreeDos that 
prefer 8086... but I think the older
FreePascal can do is 80186.

It has been a little bit hard to obtain my first hello.exe file from hello.pas 
file... so I am writing this to share, and as a
memory helper for a later day.

I am using Fedora 38 (beta) and will follow a path that match that... sorry for 
other distros users.

Fedora have fpc as a package, but not the cross-compiler to FreeDOS.
So I had to download it from:
https://sourceforge.net/projects/freepascal/files/Linux/3.2.2/

More precisely for me:
https://master.dl.sourceforge.net/project/freepascal/msdos/3.2.2/fpc-i8086-msdos-3.2.2-1.x86_64.rpm?viasf=1

I did intall it with:
sudo dnf fpc-i8086-msdos-3.2.2-1.x86_64.rpm
which installed it with the fpc from Fedora as a dependency.

It is not possible to list the files in that cross compiler with:
dnf repoquery -l fpc-i8086-msdos-3.2.2-1
because it is not in Fedora repositories,
so I had to use:
repoquery -l fpc-i8086-msdos-3.2.2-1

Rather than using fpc to compile a .pas file, you use: ppcross8086
as describe in:
https://wiki.freepascal.org/DOS
which is not too clear, that's why I am writing this.

Using -vt to show the files that the cross-compiler try to open, I had figure 
out that it search in
different place the config file for fpc, called fpc.cfg:
in /lib64/fpc/etc/fpc.cfg (was at my first try /lib/fpc/etc/fpc.cfg),
then in ~/.fpc.cfg
then in /etc/fpc.cfg

So basically, I "cp /etc/fpc.cfg ~/.fpc.cfg" then "nano ~/.fpc.cfg" edit it.

I'll show you the full file... even if I think I might have damage it a bit in 
the long day:
[paul@fedora mypas]$ cat ~/.fpc.cfg
   BEGIN  ==
# Automatically created file, don't edit.

#ifdef cpui8086
-CX
-XX
-XP
#endif

# -Fu/usr/lib/fpc/$fpcversion\units\msdos/$fpctarget
# -Fu/usr/lib/fpc/$fpcversion\units\msdos/$fpctarget\*
#-Fu/usr/lib64/fpc/3.2.2/units/msdos/80186-medium/rtl/
#-Fu/chien/salivant
#IFDEF CPUI8086
-Fu/usr/lib64/fpc/$fpcversion/units/msdos/80186-$fpcmemorymodel
-Fu/usr/lib64/fpc/$fpcversion/units/msdos/80186-$fpcmemorymodel/*
-Fu/usr/lib64/fpc/$fpcversion/units/msdos/80186-$fpcmemorymodel/rtl
#ELSE
-Fu/usr/lib/fpc/$fpcversion/units/$fpctarget
-Fu/usr/lib/fpc/$fpcversion/units/$fpctarget/*
-Fu/usr/lib/fpc/$fpcversion/units/$fpctarget/rtl
#ENDIF

#IFDEF NORMAL
 -TLinux
 -Mfpc
 -Sg
 -Ci
 -CX
 -CpATHLON64
 -OpATHLON64
 -XS
 -g-
 -p-
 -b- 
 -XP
 -O1
#ENDIF

#IFDEF DEBUG
 -TLinux
 -Mfpc
 -Sg
 -Cr
 -Ci
 -Co
 -CpATHLON64
 -OpATHLON64
 # -Fu/usr/lib/fpc/$fpcversion\units\msdos/$fpctarget
 # -Fu/usr/lib/fpc/$fpcversion\units\msdos/$fpctarget\*
 # -Fu/usr/lib/fpc/$fpcversion\units\msdos/$fpctarget\rtl
 -XS
 -g
 -p-
 -b-
#ENDIF

#IFDEF RELEASE
 -TLinux
 -Mfpc
 -Sg
 -CpATHLON64
 -OpATHLON64
 # -Fu/usr/lib64/fpc/$fpcversion\units\$fpctarget
 # -Fu/usr/lib64/fpc/$fpcversion\units\$fpctarget\*
 # -Fu/usr/lib64/fpc/$fpcversion\units\$fpctarget\rtl
 -XS
 -g-
 -p-
 -b-
 
 -O2
#ENDIF
=   END   

With that I was able to compile hello.pas file:
[paul@fedora mypas]$ cat hello.pas
program hello;
begin
  writeln('Hello!');
end.

[paul@fedora mypas]$ 
with:
[paul@fedora mypas]$ ppcross8086 -WmTiny -Wtcom hello.pas
[paul@fedora mypas]$ ls -lh
total 240K
-rw-r--r--. 1 paul paul 1,6K 19 mar 23:54 crosscompile.txt
-rw-r--r--. 1 paul paul  841 19 mar 20:25 fp.cfg.old
-rwxr-xr-x. 1 paul paul 187K 19 mar 20:33 hello
-rw-r--r--. 1 paul paul 4,0K 20 mar 00:06 hello.a
-rwxr-xr-x. 1 paul paul  13K 20 mar 00:06 hello.com
-rwxr-xr-x. 1 paul paul  15K 19 mar 23:23 hello.exe
-rw-r--r--. 1 paul paul 1,2K 19 mar 23:14 hello.o
-rw-r--r--. 1 paul paul   48 19 mar 17:01 hello.pas
[paul@fedora mypas]$ 

or other commands:
ppcross8086 -WmTiny -Wtcom hello.pas
ppcross8086 -WmTiny -Wtexe hello.pas
ppcross8086 -WmSmall hello.pas
ppcross8086 -WmMedium hello.pas
ppcross8086 -WmCompact hello.pas
ppcross8086 -WmLarge hello.pas
ppcross8086 -WmHuge hello.pas

Hope it might help someone some day!


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] I wish I had a boot.log file

[Paul Dufresne via Freedos-devel]

So many messages on boot I cannot scroll back.

If only the boot process would also copy everything in a boot.log file!___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] if exist %TEMP%\fdlive.dat goto CompletelyLoaded [not done]

[Paul Dufresne via Freedos-devel]

Testing FDT2303Live.iso in QEMU.

Seems I always get:

Cute mouse loaded

then

I think the line mentioned in title does not find fdlive.dat...

So I always get the message:

FDLIVE_ERROR: Unable to load all packages (probably need more ram) ... had 
given 2Gb of ram to -m 2048M of Qemu

part of A:\freedos\bin\fdlive.bat file.



Maybe too short email... sorry.



So what is this fdlive.dat file ... and from where should it come from?___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : Problem with procedural types in 16-bit DOS FreePascal

[Paul Dufresne via Freedos-devel]

You might want to take a look at:
https://wiki.freepascal.org/How_to_use_procedural_variables



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Berndpci.com (what & where answered)

[Paul Dufresne via Freedos-devel]

Rugxulo  said:

>I can't remember exactly (would have to check), but I think I just

>used BERNDPCI.COM. 



What: a program in assemble to search a PCI device with a specified vendor ID 
and device ID



helpmsg        db "BerndPCI, the simple PCI device counter",13,10

        db "A Public Domain tool by Eric Auer 2007",13,10,13,10

        db "Usage: BERNDPCI abcd1234",13,10,13,10

        db "Returns the count of PCI devices which",13,10

        db "have vendor ID abcd and device ID 1234",13,10

        db "as errorlevel (or 255 on error)",13,10,"$"

Where: http://ericauer.cosmodata.virtuaserver.com.br/soft/specials/___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : CDs, DVD, bonus and/or devel

[Paul Dufresne via Freedos-devel]

 Le sam., 01 oct. 2022 10:48:03 -0400 Jerome Shidel  a écrit 
 > As I see it, this leaves us with 3 choices:
 > 
 > 1) Drop nearly 300mb of packages from the CD.
 > 2) Do nothing and call it a DVD
 > 3) Move all development related packages onto their own disc. Have DevelCD 
 > and seperate BonusCD. 

I am for 3) Move all development related packages onto their own disc. Have 
DevelCD and seperate BonusCD. 
The download time (and bandwidth)  make me want to go that direction... 
obviously the cost is in part in deciding which
packages goes on which CD... and the installation related stuff... but I feel 
it is worth to be done.

The fact that some would drop the new packages made me think a bit.
I realize that for many, probably most, FreeDOS is only there to make old 
programs (most likely proprietary) continue to work.
And I do ask myself a bit if the time I put on working on DJGPP related 
stuff... would not be put with more long time effect if it
was put on a more recent OS, whichever it is.

But then, there is the aspect of doing with what I already know... avoiding the 
cost of learning new stuff (which can be fun in itself however).

There is the fact that FreeDOS is a kind of ... last holder of the flag. Seems 
that a bit of the contract with ibiblio is that they give hard disk
space and bandwidth, and in exchange we give time to maintain... and develop I 
would dare to say, new tools and programs.
Because FreeDOS become less popular with time, it make sense for me that 
FreeDOS project regroup new developement done, in the hope of keeping it
(I believe it would be in serious risk of disappearing of Internet if we do not 
do it, which would be a bit sad to me).

Also, as being open-source code... even not very interesting stuff has a 
learning to code value.



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : a proposed compress_dir algo

[Paul Dufresne via Freedos-devel]

Oh well... it is just beginning to do about what it is expected to do... 
frankly not sure.
As it is, will decompress top directories in your directory.
I wanted to publish something today... even if yet not finished... pretty much 
what I am doing.

#!/usr/bin/env perl

=pod
=item License
Copyright (C) 2022 by Paul Dufresne 

Permission to use, copy, modify, and/or distribute this software for any 
purpose with or without fee is hereby granted.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH 
REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND 
FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, 
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM 
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR 
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 
PERFORMANCE OF THIS SOFTWARE
=cut
use strict;
use warnings;
use Getopt::Long;
use File::Basename;
use Archive::Zip qw ( :ERROR_CODES :MISC_CONSTANTS );
use Scalar::Util 'blessed';

sub getTopDirs;
sub copyDir;
sub copyFiles;
sub makePath8_3;
sub make8_3;

my $zip_in = "/home/paul/Téléchargements/dj_gpp-unstable.zip";
my $zip = Archive::Zip->new($zip_in);

my @members = $zip->memberNames();
my $firstname = $members[0];
my @topDirs;

my $outzip = Archive::Zip->new(); # no parameter, indicate output
# $outzip->fileAttributeFormat=Archive::Zip::Member::FA_MSDOS;
#$outzip->fileparse_set_fstype("DOS"); # was expecting it would handle 8_3 paths
# but it is unclear it does anything... maybe not called the right way?

# had tried with that too: $zip->fileparse_set_fstype("DOS"); 

@topDirs = (\@members); # in: members out
my $firstTop=$topDirs[0];
my @splitDirs=split '/',$firstTop,2;
my $topName =  $splitDirs[0];

foreach $_ (@topDirs){
  copyDir $_, $zip, $outzip;
}

$outzip->writeToFileNamed("pkgout.zip");
exit 0;

sub getTopDirs{
  my $filenames = $_[0];
  my @out;
  my @splited;
  foreach $_(@$filenames){
@splited=split("/",$_,4);
push @out, $_ if (substr($_,-1) eq "/") and ((scalar @splited) == 3);
  }
  return @out;
}

sub copyDir{
  my $theDir = shift;
  my $fromZip = shift;
  my $toZip = shift;
  my @theFiles=$fromZip->membersMatching($theDir);
  print "the dir $theDir contains " . scalar @theFiles . " files.\n";
  copyFiles($fromZip, $toZip, \@theFiles);
}

sub copyFiles{
  my $fromZip = shift;
  my $toZip = shift;
  my @theFiles = @{$_[0]};
  my $longName;
  my $dosName;
  my $tmp;
  foreach $_ (@theFiles){
$longName = $_->fileName;
$dosName=makePath8_3 $longName;
$dosName=substr($dosName,index($dosName,"/")+1); # try to remove top path 
(branch name)
print "$longName type:" . blessed($_) . "\n";
if (blessed($_) eq "Archive::Zip::ZipFileMember"){
  $fromZip->extractMember($_,$dosName);
  $toZip->addFile($dosName);
}
  }
}

sub makePath8_3{
  my $input = shift;
  my @splited=split "/",$input;
  my $output="";

  for (@splited){
my $shorten=make8_3 $_;
$output = $output . $shorten . "/";
  }
  $output = substr($output,0,length($output) - 1) if substr($input,-1) ne "/";
  return uc  $output;
}
exit 0;

sub make8_3{
  my $input = shift;
  my $lastDotIndex = rindex $input, '.';
  my $basename = "";
  my $ext = "";
  return $input if $input eq "..";
  return $input if $input eq ".";
  if ($lastDotIndex != -1){
$basename = substr $input, 0, $lastDotIndex;
$ext = "." . substr $input, $lastDotIndex + 1, 3;
  } else{
$basename = $input;
$ext = "";
  }
  $basename = substr $basename, 0, 8; 
  return $basename . $ext;
}



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] a proposed compress_dir algo

[Paul Dufresne via Freedos-devel]

Thinking about the problem... I think about writing a small program to compress 
a directory.
Here is the pseudocode I have come up to now:

Function compress_topdir(path)
  if path reference a zip file
decompress zip file to some_dir
compress_dir(some_dir)
  else
compress_dir(path)

Function compress_dir(dir)
  if dir contains only one directory file /* Gitlab zip file */
compress_dir(dir,"")
  else
compress_dir(dir,dir)

Function compress_dir (dir, tuncated_path)
  For each file in dir hereby named f
f_truncated=truncate_name(f) /* to 8.3 format */
if f is a dir
  truncated_path = truncated_path + '/' + f_truncated
  add truncated_path/f_truncated empty directory to zip
  compress_dir(dir, truncated_path)
else /* a file */
  copy dir/f to a temporary file named f_truncated
  update zip by adding truncated_path + "/" + f_truncated
  delete temporary file named f_truncated

Hope it make some sense... and that you don't feel flooded with useless 
information.
Might consider to make it as a Perl script.
Mostly because I consider learning Rakudo (Perl v. 6) but really would do 
it in plain Perl v.5. for it is installed on most Linux.


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Ré : When a system with limited filenames length combine directories into one

[Paul Dufresne via Freedos-devel]

>If that sounds like it would solve the problem, I could add it to the fdpkg.sh 
>script. Then if it works, implement the equivalent in the RBE.

Thanks for this internal description of fdnpkg.sh. I'll take a look at it...___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : When a system with limited filenames length combine directories into one

[Paul Dufresne via Freedos-devel]

I wrongly said:

>It's probably ok... because fdnpkg probably won't too.

Nonsense! fdnpkg have no way to know that many directories have been combined 
into one.



So I just need fdpkg to accept to combine directories with same 8 chars 
truncated length to be combined together.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] When a system with limited filenames length combine directories into one

[Paul Dufresne via Freedos-devel]

Imagine a zip file with the following directories:

a

ab

abc

abcd



Now, if the system support a filename length of 4, we get 4 different 
directories.



But if the system only support a filename length of 2, we get 2 different 
directories:

a

ab



in a we have a,

in ab, we have combined the content of directories ab, abc and abcd



And it is ok as long as there is no file conflcts in ab, abc and abcd.



The package dj_gpp rely on  this trick:



I have got:

[paul@nixos:~/Documents/fdtest2]$ zip -k -r ../dj_gpp.zip dj_gpp/DEVEL 
dj_gpp/APPINFO

    zip warning:   first full name: 
dj_gpp/DEVEL/DJGPP/include/cxx/12/ext/pb_ds/detail/binomial_heap_/

  second full name: 
dj_gpp/DEVEL/DJGPP/include/cxx/12/ext/pb_ds/detail/binomial_heap_base_/

 name in zip file repeated: 
DJ_GPP/DEVEL/DJGPP/INCLUDE/CXX/12/EXT/PB_DS/DETAIL/BINOMIAL/



zip error: Invalid command arguments (cannot repeat names in zip file)



[paul@nixos:~/Documents/fdtest2]$ 



So... zip is too prudent, and won't accept to combine the directories.

It's probably ok... because fdnpkg probably won't too.



I would need fdpkg to accept to combine the directories... for the day someone 
will modify fdnpkg to accept to do is (if it don't).



But if you don't see dj_gpp inside FDT2210... you will have an idea why.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] source directory (DJGPP packages)

[Paul Dufresne via Freedos-devel]

 Le lun., 05 sept. 2022 18:51:10 -0400 Paul Dufresne via Freedos-devel  a 
écrit 
 > I guess it would be reasonable that I truncate the files in DEVEL myself to 
 > 8.3... probably by "zip -k" then unzipping DEVEL directories.
 > For sources...I don't know... just need the doslfn.zip files to be under 
 > SOURCE/(PKGNAME)/ not under SOURCE.
 
After some more thinking.
I should not deal myself with truncating the files in DEVEL... I think it is 
best if the program making the package does it.
I think that what I need, for T2210, is that it just truncate the files... so 
that they will be accepted by fdnpkg.
That's what happened with suggested way of installing by DJGPP when no LFN 
program is installed.
They ask that all files be unzipped in same directory... which means they get 
truncated to 8.3 filenames.

For SOURCE... I should let fdpkg decide.

Will try to continue my "work" of updating DJGPP packages, keeping the full 
names everywhere, and not having compressed files.

I may eventually check if I can modify fdpkg.sh to just do that (to test before 
T2210), unless Jerome come with a solution soon.




___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] source directory (DJGPP packages)

[Paul Dufresne via Freedos-devel]

An option could be to have fdnpkg check for files not respecting 8.3, if they 
exist, only accept to install the package if doslfn is loaded.

 ___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] source directory (DJGPP packages)

[Paul Dufresne via Freedos-devel]

I guess it would be reasonable that I truncate the files in DEVEL myself to 
8.3... probably by "zip -k" then unzipping DEVEL directories.



For sources...I don't know... just need the doslfn.zip files to be under 
SOURCE/(PKGNAME)/ not under SOURCE.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] source directory (DJGPP packages)

[Paul Dufresne via Freedos-devel]

Jerome wrote:
>The compression portion of that process has several actions it performs. It 
>will compress all sources to preserve long file names and possible 
>case-specific files. It >will also check the remaining files in other 
>directories to verify they are 8.3 compatible. If LFN files exist in those 
>directories, the are compressed by section (top >most sub-directory) into a 
>embedded LFNFILES.ZIP archive. For several reasons, this is not a perfect 
>solution. It is just a compromise that hopefully causes the >fewest problems 
>for end users. 
 
The problem I get now, is that the files DEVEL/ LFNFILES.ZIP from packages 
DJ_GDB and from DJ_GPP are in conflict.
They probably does not contain conflicting files... but the files in itself are.
Might be causing problems by trying to avoid them too much.
By that, I means, it was probably designed to works just fine, by truncating to 
8.3 files.

I am unsure what to suggest. Just formulating the problem I got/get.


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Make fdpkg.sh to work with gitlab zip files

[Paul Dufresne via Freedos-devel]

>A couple things… If you intend on updating the Git packages, why are you not 
>cloning them? Why download as a zip?

There was this barrier in my mind, between the working development 
directories... and the using of them by downloading on Gitlab.

But... yeah... will just copy my working directories... and then use them... 
should indeed work easier that way.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Make fdpkg.sh to work with gitlab zip files

[Paul Dufresne via Freedos-devel]

Sadly... fdpkg.sh does not work on dowloaded zip project files from Gitlab, 
most probably because the wanted dirs (APPINFO, SOURCE, etc) are not in root.



Would you consider to edit fdpkg.sh to work for these zip files too?

...

Or would you prefer to let it as an exercise to the user?___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] source directory (DJGPP packages)

[Paul Dufresne via Freedos-devel]

Thank you, that clarify things!

Will try your tool... not in my git directories.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] source directory (DJGPP packages)

[Paul Dufresne via Freedos-devel]

Is there a process that will take the files in SOURCE/(PKG)/ and make them a 
SOURCES.ZIP file?



I explore a bit and saw that some packages are just source files (not 
compressed)... and some packages have sources.zip.

So I begin to think that there is nothing special that produce SOURCES.ZIP 
files... and so, that would means my source files should be

8.3 compatible (for fdnpkg to accept them).



Using zip -k (yeah... I was using my GUI Zip archive... that was causing 
incompatibility with fdnpkg... but install zip that I believe will be 
compatible) that coerce

long file names to compatible DOS filenames and that check for conflicts with 
truncated files... I could generate 8.3 ok files... but with very very annoying 
and dangerous

efforts (any change risk to make the code not to compile I think).



Remember... source code for DJGPP packages are source code used on Linux 
(mostly)... so they were not designed with 8.3 filenames... and could even

contains some unicode sometimes.. I think.



Also, some are very big like:

http://www.delorie.com/pub/djgpp/current/v2gnu/gcc1220s.zip

which is 116 Mb zipped. (For this particular case I proposed a separate source 
package: https://gitlab.com/FreeDOS/devel/dj_gcc/-/issues/1)



So my intention goes toward in most cases, to just include the zip files 
dowloaded from DJGPP (renamed SOURCES.ZIP ... or not renamed... unsure about 
that).



This message is mostly a ... does it seems an appropriate decision?___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] no sys/socket.h ... need dj_watcp package

[Paul Dufresne via Freedos-devel]

 Le dim., 04 sept. 2022 01:55:01 -0400 Louis Santillan  
a écrit 

>You know you know you can get a precompiled copy of WatTCP and other djgpp 
>zips at http://delorie.com or a mirror near you?

>

>

http://www.delorie.com/pub/djgpp/current/

http://www.delorie.com/pub/djgpp/current/v2tk/wat3211b.zip







I should have guess! Thanks!

Had mislead myself to think it was probably similar to:

http://www.watt-32.net/watt32b.zip

that even so, I now realized do contains dll (not really usefull for us).___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] no sys/socket.h ... need dj_watcp package

[Paul Dufresne via Freedos-devel]

While trying to compile fdnpkg (resolved a few issues), I now face:

net.c sys/socket.h no such file



And the reason... to build the binaries that connect to Internet, I would need 
to add the include files and the libraries for DJGPP.

This is done with:

http://www.delorie.com/pub/djgpp/current/v2tk/wat3211s.zip



Note that it seems that there is no distributions of binariy libs... it is the 
source code of the libs to build the binaries lib (for specified compiler).



And this suggest to add a package dj_watcp for compiling programs accessing 
Internet.



Frankly... myself find that it does quite a number of packages.

I thought about building a DJGPP package with most useful libs included... 
rather than packages for the libs...

I am not decided yet if this is a good or bad idea.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Have a common zlib package

[Paul Dufresne via Freedos-devel]

 Le sam., 03 sept. 2022 17:43:42 -0400 Paul Dufresne via Freedos-devel  a 
écrit 
 > First, fdnpkg contains zlib to handle zip files.
 > It's version is the 2013 version (1.2.8) while most recent is 1.2.12 (2022).
 > 
 > Maybe the invalid zip sig is linked to that... unsure.
 
Request to add a dj_zlib package:
 https://gitlab.com/FreeDOS/issue-reporting/-/issues/36


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] package contains an invalid filename

[Paul Dufresne via Freedos-devel]

First, fdnpkg contains zlib to handle zip files.

It's version is the 2013 version (1.2.8) while most recent is 1.2.12 (2022).



Maybe the invalid zip sig is linked to that... unsure.





Also, pkginst.c have:

/* validate a filename (8+3, no weird characters, etc). returns 0 on success,

 * nonzero otherwise. */

static int validfilename(char *fname) {

  int i, i2;

  char *validchars = "!#$%&'()-@^_`{}~";

  int elemlen = 0;

  int elemmaxlen = 8; /* switches from 8 to 3 depending wheter I am analyzing

 a filename or an extension */

  /* look for invalid chars in the entire string, and check the length of the

   * element at the same time */



So yeah... I guess this is linked to the fact that Gitlab insert a directory 
name with the name of the project-name of branch at the top of zip file.

This make it invalid... too long.

But also it is unclear it would know that it must look for source not in top, 
but in the single directory in top of the archive.



So... maybe should begin to update to latest zlib... then find a way to ignore 
first part of paths.



Of course... if I wait one month... the OS installer thing would do a valid 
archive ... hopefully (I wanted to early test).

Sent using https://www.zoho.com/mail/








 Le sam., 03 sept. 2022 16:28:01 -0400 Paul Dufresne via Freedos-devel 
 a écrit 



unzip djgpp.zip in FreeDOS was happy to execute without errors.

funny... the whatin.sh file was the last one inflated.






___ 
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] package contains an invalid filename

[Paul Dufresne via Freedos-devel]

unzip djgpp.zip in FreeDOS was happy to execute without errors.

funny... the whatin.sh file was the last one inflated.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] package contains an invalid filename

[Paul Dufresne via Freedos-devel]

hum... maybe... but it' always on .md file, .ver file (or this time .sh) files.



I just tried to extract in Linux, rename the djgpp_unstable to just djgpp, 
rezip...



But then in FreeDOS on the fdnpkg command I got:

unknow zip sig: 0x92cb9dd5

Error: Invalid zip archive! Package not installed.



Tried to search that ID... did not found something.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] package contains an invalid filename

[Paul Dufresne via Freedos-devel]

Like the guy that wrote a small program... and come to the compiler and naively 
expect it to compile it without errors...

I have come to "fdnpkg install-nosrc djgpp_uns~1.zip" and was replied with:

Error: Package contains an invalid filename: 

  djpp_unstable\source\djgpp\utils\whatin.sh



Is it the .sh (Unix shell ) ...

does it handle correctly LongFileNames? (I did not remember to have called 
doslfn.exe...) but djgpp_unstable seems ok... and not 8.3.



Well... do I need to be strict like this in my source directory?

Frankly... I did just unzip upstream in it... without thinking much more.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] group-devel.htm file broken by dj_ renaming

[Paul Dufresne via Freedos-devel]

Yes, indeed... (the cache issue again), sorry.

using Firefox 104.0.1 under NixOS___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] group-devel.htm file broken by dj_ renaming

[Paul Dufresne via Freedos-devel]

On:

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/unstable/pkg-html/group-devel.html

the DJGPP packages seems to not work anymore due to the package renaming.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] An allegro game library version 4.2.2 package

[Paul Dufresne via Freedos-devel]

I added a file dj_alego.zip (using my suggestion for renaming files from 
djgpp_ab, to dj_abcde) to my DJGPP packages at:



Allegro is a library to write games... this is the version on DJGPP site: 4.2.2.



https://gitlab.com/dufresnep/freedos-djgpp



Supposing that you managed to have all the files there inside your FreeDOS VM, 
you could build an allegro test.c file by:



fdnpkg insall-nosrc djgpp

fdnpkg install-nosrc djgpp_bn.zip

fdnpkg install-nosrc djgpp_gc.zip

fdnpkg install-wsrc dj_alego.zip



cd FreeDOS\Source

cd dj_alego

unzip all422s.zip

[some errors will happen because the file contains  some more  than 8 chars 
name... I said yes]

cd allegro

cd tests

gcc -o test.exe test.c -lalleg

test.exe

strip test.exe  [make the file smaller by removing debugging symbols]___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Ré : FreeDOS T2209

[Paul Dufresne via Freedos-devel]

Indeed, fixed by refreshing.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : FreeDOS T2209

[Paul Dufresne via Freedos-devel]

the report.htm seems up to date... but the title is still about T2208, and it 
says it was built: 
Monday August  1, 2022 at 05:56:27 AM EDT



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] GPL need source nearby

[Paul Dufresne via Freedos-devel]

 Le mer., 31 août 2022 23:47:55 -0400 Jim Hall  a écrit 

 > 
 > Since GCC is definitely distributed under the GNU General Public License, 
 > and the GNU GPL requires that you must provide source code if you distribute 
 > the binary, you might reconsider your "no source."
 > 
 > And unfortunately, linking to the place where you downloaded your copy of 
 > the source code is not sufficient to meet the GNU GPL. You need to provide 
 > the same source code used to build the binary, either as part of the binary 
 > package, or make it available to download from the same place (such as 
 > alongside) as the binary.
 > 

If you look at:
https://gitlab.com/FreeDOS/devel/djgpp_bn
or
https://gitlab.com/FreeDOS/devel/djgpp_gc

you will not see a SOURCE directory in them.

I suspect that they are many like that.


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : Ré : GCC 12.2.0 and BinUtils 2.35.1 packages

[Paul Dufresne via Freedos-devel]

I said previously:
 > Please do not try to install the previous packages for now.
 > 
 > I have created the files in DEVEL\BIN rather than DEVEL\DJGPP\BIN, etc.
 > 
 > Will fix the packages now.

I think it is fixed now.
Added a package for GCC sources too.

Again, available at:
https://gitlab.com/dufresnep/freedos-djgpp/-/tree/main


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : GCC 12.2.0 and BinUtils 2.35.1 packages

[Paul Dufresne via Freedos-devel]

Please do not try to install the previous packages for now.



I have created the files in DEVEL\BIN rather than DEVEL\DJGPP\BIN, etc.



Will fix the packages now.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : GCC 12.2.0 and BinUtils 2.35.1 packages

[Paul Dufresne via Freedos-devel]

You might want a bit more than 900Mb virtual machine. (it is almost full)

I consider remaking it, a 1600Mb one.



That should allows me to extract some sources... and do some building.



But eh... you do as you feel.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] GCC 12.2.0 and BinUtils 2.35.1 packages

[Paul Dufresne via Freedos-devel]

You did not ask for it!

You probably did not want it!

It is big!



But it is here!

GCC 12.2.0 and BinUtils (linker, assembler) version 2.35.1, now available as 
downloads at: 



https://gitlab.com/dufresnep/freedos-djgpp/-/tree/main



GCC package have no source.

BinUtils have source (and is the most part of the archive).



You will need to add in fdauto.bat

set DJGPP=\DEVEL\DJGPP\DJGPP.ENV



And I have tried to create links to most executable... but you still need to 
had it in the PATH to compile a program:

set PATH=%PATH%;C:\DEVEL\BIN



Up to now, only tried by compiling a printf("Hello FreeDOS people!\n) program.



I install it with:

fdnpkg install djgpp

fdnpkg install djgpp_bn.zip

fdnpkg install djgpp_gc.zip



euh... I have created a 900M image with "qemu-img create fdt2208,img 900M"

and after installatiion, and closing of the VM, I do:



losetup -f -P fdt2208.img

so that it come in my Files Window (have to enter password to mount it)



so that I can copy the zip files in the raw image file



But hopefully, it will become much easier to install if it is accepted.



Note: I did not recompiled the files, just created zip files for the packages 
and moved the files in.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Editing LSM files under Linux (code page considerations)

[Paul Dufresne via Freedos-devel]

I am trying to do a 12.2.0 packagte for GCC.

I am editing LSM files on Linux... and beginning to ask myself how much bad it 
is.

I means... I am probably transforming them to UTF-8 unicode... so the codepage 
indicated in the file would be wrong now.

And if  I would edit them in DOS... I would have to change code page before 
editing any of them... I would guess.

So... can I edit them in UTF-8 unicode... is there a tool that check that and 
add the modified-date?___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] How to install GCC in FreeDOS? (avoid the segmentation fault when running gcc)

[Paul Dufresne via Freedos-devel]

At first I did:

fdnpkg install djgpp_gc

and then tried: gcc , in some directory... was not working



I then "cd c:\devel\djgpp\bin"

I then "gcc", but then I got a segmentation fault.



I think that after some Google search (did not help)... I saw 
C:\DJGPP\README.1ST



I then:

fdnpkg install djgpp

fdnpkg install djgpp_bn



and added to c:\fdauto.bat (after other set, before aliases):

set DJGPP=C:\DEVEL\DJGPP\DJGPP.ENV

set PATH=C:\DEVEL\DJGPP\BIN;%PATH%

...

reboot



after that:

gcc --version

have given the expected result.



Wish to help others get the result faster... either creating a Wiki page would 
help.

Or maybe some line written when installing djgpp_gc?___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : Ré : Ré : suggested qemu command line to boot FreeDOS

[Paul Dufresne via Freedos-devel]

Just running QEMU with "-net nic,model=pcnet -net user" is not enough.

I means, after that if I do "fdnpkg search gcc", it results in "NO PACKET 
DRIVER".

I need to type "fdnet", and then it get an IP address through DHCP...

and then "fdnpkg search gcc" works!___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] It's "crynwr.com", not "www.crynwr.com"!

[Paul Dufresne via Freedos-devel]

There is a small mistake on the link for crynwr on:



http://wiki.freedos.org/wiki/index.php/Networking_FreeDOS_-_Packet_driver_installation

section: Where to find them (the packet drivers)



the crynwr link have www. at the beginning... it does not work because of that.

The site is really: http://crynwr.com/drivers/00index.html

without www.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : Ré : suggested qemu command line to boot FreeDOS

[Paul Dufresne via Freedos-devel]

I added "-net nic,model=pcnet -net user" to allows networking to work (based on:

https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/freedos-in-qemu-no-internet-connection-4175638386/
 )

to allows access to the network (which it is said does not work on real 
hardware for now)



So that the line I now use is:

qemu-system-i386 -cpu 486 -name FreeDOS -machine 
pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -enable-kvm -m 64 
-overcommit mem-lock=off -no-user-config -nodefaults -rtc 
base=utc,driftfix=slew -no-hpet -boot menu=on,strict=on -sandbox 
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg 
timestamp=on -drive format=raw,file=fdt2208.img,format=raw -cdrom T2208LIVE.iso 
 -audiodev pa,id=mysnd -device sb16,audiodev=mysnd -device adlib,audiodev=mysnd 
-machine pcspk-audiodev=mysnd  -vga cirrus -display sdl -usbdevice mouse -net 
nic,model=pcnet -net user 



make sure to adjust: fdt2208.img and T2208LIVE.iso to what you have.



Note:

model=e1000 or e1000e: DHCP did not got an address

model=tulip, DHCP no address



model=rtl8139, results in:

QEMU Network detected

0 Match found

1 Match found

Bad command or filenname "rtspkt.com".

Network is unreachable/unavailable.



I guess I will check for an issue about this last one... and add one if I don't 
find one.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : suggested qemu command line to boot FreeDOS

[Paul Dufresne via Freedos-devel]

Searching a bit more, I now come with:

"qemu-system-i386 -name FreeDOS -machine 
pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -enable-kvm -cpu 486 -m 64 
-overcommit mem-lock=off -no-user-config -nodefaults -rtc 
base=utc,driftfix=slew -no-hpet -boot menu=on,strict=on -sandbox 
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg 
timestamp=on -drive format=raw,file=fdt2208.img,format=raw -cdrom T2208LIVE.iso 
 -audiodev pa,id=mysnd -device sb16,audiodev=mysnd -device adlib,audiodev=mysnd 
-machine pcspk-audiodev=mysnd  -vga cirrus -display sdl -usbdevice mouse"

which should enable adlib and sb16 emulation (I think my previous message did 
not)___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] suggested qemu command line to boot FreeDOS

[Paul Dufresne via Freedos-devel]

I begin with suggested line in:



http://www.freedos.org/books/get-started/june14-manual-install.html



after creating the hard disk image with: "qemu-img create fdt2208.img 600M"



I am now using:

"qemu-system-i386 -name FreeDOS -machine 
pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -enable-kvm -cpu 486 -m 64 
-overcommit mem-lock=off -no-user-config -nodefaults -rtc 
base=utc,driftfix=slew -no-hpet -boot menu=on,strict=on -sandbox 
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg 
timestamp=on -drive format=raw,file=fdt2208.img,format=raw -cdrom T2208LIVE.iso 
 -audiodev alsa,id=mysnd -machine pcspk-audiodev=mysnd  -vga cirrus -display 
sdl -usbdevice mouse"



To be honest I don't understand all the options.



"-cpu 486" is probably slower than "-cpu host" but should give more similar 
results on different computers on which it is run.



The change is mostly a more recent version of defining sound devices (well, pa 
was maybe more recent... and unsure if pa would work),

and also specifying raw format to avoid restriction on block 0.

On some other system, I removed "-display sdl" as it was necessary because qemu 
was not compiled with SDL option (OpenSUSE Tumbleweed).___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] No simple cpu identification program returning an error code as an answer?

[Paul Dufresne via Freedos-devel]

Thanks Jim about VINFO /m to detect CPU!

I did not knew it, or at least I had totally forgotten it.



The sad part of it, is that it is so fancy that one cannot use virtual machines 
to test different CPUs, because it detects the virtual machine rather than the 
virtual CPU.



So that Eduardo's one might be more what I want to use... I'll have to try.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] No simple cpu identification program returning an error code as an answer?

[Paul Dufresne via Freedos-devel]

Following the modification of my idea proposed by Tom: run edit32 on 386+ else 
run edit... BTW thanks Tom!

I have been looking a bit for a simple program that would identify approximate 
CPU and return it as an error code that batch file could used.

I did not found that (especially with free license)... so that I am thinking 
about writing one.

Just asking if that exist already here.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Status of OpenSSL in FreeDOS?

[Paul Dufresne via Freedos-devel]

Hi!
I began investigating an issue with curl related to https urls complaining 
about not having enough randomness:
https://gitlab.com/FreeDOS/net/curl/-/issues/1

I suspect that this is a problem related to OpenSSL... and might affect the web 
browsers too, but I did not even tried.

I don't know if theses issues were known...  not using much networking in the 
past.

As you can see with curl 7.77 (latest being 7.84) the randomness issue 
disappears but then show a problem with accepting certificates.
Which make me ask: What is the status of https with FreeDOS?

We don't package OpenSSL library... but it is coming from DJGPP project... as 
far as I know.



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?

[Paul Dufresne via Freedos-devel]

At first I thought that edit was 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/unstable/pkg-html/msedit.html

and realized it was a 32 bit program, written entirely in FreeBASIC.



I did not tried it... just thinking maybe on a 386+ system, we could use it... 
and keep the other edit for older than 386 ?___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?

[Paul Dufresne via Freedos-devel]

 
>it's still beyond my understanding why you don't want to edit small 
>files with edit32 
>
> Tom

Well, because the full idea is more like:

If file < 64k
  then edit.exe the file
else (file > 64k)
  if processor 386+
edit32 the file
  else
error "sorry, file to big!"
  endif
enfif

So that it works both on 8086 and 386+.




___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?

[Paul Dufresne via Freedos-devel]

Would it be possible to have edit.exe for 64k less files... edit32.exe for 
bigger files... and edit.bat that would check fif the requested file to edit is 
bigger than 64k and then call edit32 on the file, else edit.exe on the file?___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : MBR not written by default?

[Paul Dufresne via Freedos-devel]

Checking 1st sector signature will probably not work (because FDISK probably 
create a valid signature even if no MBR present.

So I guess the correct way is to overwrite by default the MBR... so don't make 
if frightening to the user.

I would so propose:
"Install MBR (that allows booting)? (Yes/no) (only say no if you already use a 
boot loader you want to keep like Grub)"



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?

[Paul Dufresne via Freedos-devel]

 Le jeu., 25 août 2022 04:10:17 -0400 Eric Auer  a écrit 

 > That is not necessary - you mentioned a 32-bit version 
 > of some text editor, which already IS included :-) See 
 >  
 > http://freedos.org/software/ ==> 
 >  
 > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/group-edit.html
 >  
 >  
 > for example SETEDIT is 32-bit and can edit large files, 

you are asking me, the user way too much thinking!
I want edit to work on big files... not an edit for small files and an other 
that I must search for for big files.


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?

[Paul Dufresne via Freedos-devel]

While thinking about 64k limit for edit... I come to think about 16 bits and 32 
bits programs...

Why there is no two separate versions of FreeDOS, one for 16 bits CPUs (8086) 
and one for 32 bits CPU (386+)?

It seems there is a lot of programs that cannot run on 8086... and others that 
could take advantage of 32 bits compilation.

Does it should not suggest to have two separate versions foir this relatively 
different needs?





___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Could almost all packages use links?

[Paul Dufresne via Freedos-devel]

I know some packages use "Links" to make executables in the executable %PATH% 
to make them callable from any directory.
The question I ask myslf, is why is is the exception rather than the norm?
Would it make it significantly slower?





___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] MBR not written by default?

[Paul Dufresne via Freedos-devel]

I have installed FreeDOS 22.08 (interim release) on a ... frankly SMART 
reporting problematic HD.

My first attempt have failed.
I believed, not sure, it was because the disk was not having previously a 
FATish partition.
So I got the first stage where FDISK was doing it's job (in english... where I 
was installing in french... but that's been discussed at last get-together)...
so it formatted it (but now I realized without doing an MBR) ... then rebooted.
So then the installer asked me if it should overwrite the MBR... and I thought 
to myself, let's try answer no here.
And indeed it did not boot after end of installation.

To the installer credit, the installer seems to have detected and proposed to 
type some command to create MBR... but the french translation was quite bad, 
like "'est pas" rather than "n'est pas" and other stuff... that I did not time 
to read because the installer removed it after about 3 or 5 secs and decided to 
continue.

It had seems easier to me to just reinstall (and this time choose to overwrite 
MBR) rather to try to install MBR on hard disk (I expect less technical encline 
people will do the same).

I understand the hesitation to remove previous boot loader... but I believe it 
is expected that the MBR will be installed unless the user protest:

So I believe installer should ask: "Ok to overwrite boot loader (MBR)?  (Y/n)" 
where yes is the default.
I write this and realize that it is about what we do now... but the term 
"overwrite" is kind of frightening... and kind of suppose there is one and 
it may not have.

Thinking... feeling we discussed that in the past (unsure)...

Proposition:
If MBR have valid signature then ask if you want to force an overwrite 
(defaulting to not)... else "No boot sector present, OK to write one? (Y/n)" 
defaulting to  yes. 




___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Update on website usability test

[Paul Dufresne via Freedos-devel]

 Activé mer., 04 mai 2022 14:41:28 -0400 Mercury Thirteen via Freedos-devel 
 écrit 

 > I had some spare time, so I took some liberties with ​Paul's text. Hopefully 
 > I didn't slice-n-dice it too badly from your original intent! :)
 ... modified text folowing...
 > What do y'all think?
I like it very much!


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] A web-based forum to replace the mailing-lists?

[Paul Dufresne via Freedos-devel]

I was confused by the suggested word "forums" in a previous email.



That's why I wrote: "We also communicate through a web-based discussion program 
called Forum, but it is less used: (Link to forums)." I thought that maybe we 
had a web-based discussion program like phpBB (https://www.phpbb.com/demo/ ) 
that I was just not using because we did not used it much. But it looks like we 
use the mailing-lists because we don't have a web based forum.



At least, I would prefer we use a web-based forum, because that way, threads 
about not concluded subjects remains (supposing no one erase them), while with 
mailing lists these subjects just tend to get forgotten. Also messages can be 
edited before I see them (so that erroneous information can have been already 
fixed).



But would you use it instead of the mailing-lists if it would be there?



Would Jim consider adding such an extension to the website?___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Update on website usability test

[Paul Dufresne via Freedos-devel]

Precedently suggested web site should have at the beginning:



"I know all this" links to the following:



News (link to news)



Let's talk ( https://www.freedos.org/forums/ )



Wiki ( http://wiki.freedos.org/wiki/index.php/Main_Page )



Bugs ( https://www.freedos.org/bugs/ )



Gitlab (link to https://gitlab.com/FreeDOS )

Github (link to https://github.com/search?q=freedos)

Ibiblio ( link to https://www.ibiblio.org/pub/micro/pc-stuff/freedos/ )

Ibiblio What's included ( 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.3/official/report.html
 )

Kernel ( https://github.com/FDOS/kernel )



The downloads ( https://test.freedos.org/download/ )



Other links ( https://www.freedos.org/links/ )



Visit web page for newcomers (link to previously suggested page)___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Update on website usability test

[Paul Dufresne via Freedos-devel]

Replace:

A mailing list is a group of people to which you can subscribe to (or 
unsubscribe), and every message one send to it is redistributed by email to 
every subscribed people. (Link to mailing lists).

By:

Mailing lists are handle by a program on our server that when it received an 
email to the associated address send it to every people that are presently 
subscribed to it. You can subscribe (or unsubscribe) by visiting (link to 
mailing-lists page).___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Update on website usability test

[Paul Dufresne via Freedos-devel]

I just done a better version... as it is small given the full new version here:



FreeDOS is a free (both having the liberty to, and with no fees) to use, 
redistribute and modify reimplementation of DOS (mainly Microsoft DOS) that was 
often coming with computers in the 80s. By default, it does not come with a 
graphical environment, but rather you give text commands to see, copy, edit and 
execute files. Link: Introduction to commands. The files executed are often 
graphical programs more similar to what you can see on modern computers. Or 
they can be text-based programs (either that you manipulate with text commands 
like FreeDOS itself, or that allows you to move from fields to fields with tab 
key (or sometime even with the mouse) or to use the menus with shortcuts on the 
keyboard (or again sometime with the mouse).



FreeDOS come with a lot of programs (Link to included programs categories) but 
it also allows you to run DOS programs you already own (like games) that were 
done to run in DOS when it was popular. We cannot include every programs by 
default in FreeDOS, but there is many websites that allows you to get programs 
made to be run in DOS and so in FreeDOS (link to sites having DOS programs).



There is mainly two ways to install FreeDOS. The one we recommand is in what we 
call a virtual machine. Modern computers have (often free to use) programs that 
allows you to create, modify (add a file that would act as an hard disk, or a 
an .iso file that would act as a DVD in a DVD drive) or destroy simulated 
computers called virtual machines. The virtual machine manager programs allow 
then you to start a virtual machine that appears as a window with which you can 
interact with keyboard and mouse. (link to install in a virtual machine). If 
you have a real computer (maybe an old one) that you want to dedicate to 
FreeDOS, you can  (Link install on a real computer).



If you encounter problems while using FreeDOS, we have what is called a Wiki, 
which is like a website but which is easier for people to contribute changes. 
So it will probably have more information than the website (Link to the Wiki). 
You can also communicate with other users. We mostly communicate through 
mailing-lists. A mailing list is a group of people to which you can subscribe 
to (or unsubscribe), and every message one send to it is redistributed by email 
to every subscribed people. (Link to mailing lists). We also communicate 
through a web-based discussion program called Forum, but it is less used: (Link 
to forums). We also maintain a list of know bugs (link to bugs).



As FreeDOS is free to modify, any one can get the source code (link to source 
code) and propose modifications to it.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Update on website usability test

[Paul Dufresne via Freedos-devel]

Well, my first reaction was that a website and a wiki play very similar roles, 
and that maybe we should use just one of it.



I guess I would prefer the Wiki (but you must make it relatively easy to get an 
account on it)... but website are not too bad if they are on GitHub or GitLab.

Then they don't need you to give them permession to modify... they just need 
you to accept their suggested modifications. But HTML is a bit harder to edit.



I then had the idea to spend about 15 minutes to do as if I was to write the 
website and came with the following:



FreeDOS is a free (both having the liberty to, and with no fees) to use, 
redistribute and modify reimplementation of DOS (mainly Microsoft DOS) that was 
often coming with computers in the 80s. By default, it does not come with a 
graphical environment, but rather you give text commands to see, copy, edit and 
execute files. Link: Introduction to commands. The files executed are often 
graphical programs more similar to what you can see on modern computers, except 
maybe they often have less text fields because FreeDOS does not come with a 
default graphical environment where does are predefined, but there is also a 
lot of text-based interactive programs.



FreeDOS come with a lot of programs (Link to included programs category) but it 
also allows you to run programs (like games) that were done to run in DOS when 
it was popular.



There is mainly two ways to install FreeDOS. On a real computer, that can be a 
very old computer: (Link install on a real computer), or modern computers have 
programs that allows you to simulate a computer where a window allows you to 
interact with keyboard and mouse on the simulated computers, with simulated 
devices like hard disk, DVD reader, etc. (Link install in a virtual machine).



If you encounter problems while using FreeDOS, we have what is called a Wiki, 
which is like a website but which is easier for people to contribute changes. 
So it will probably have more information than the website (Link to the Wiki). 
You can also communicate with other users. We mostly communicate through 
mailing-lists. A mailing list is a group of people to which you can subscribe 
to (or unsubscribe), and every message one send to it is redistributed by email 
to every subscribed people. (Link to mailing lists). We also communicate 
through a web-based discussion program called Forum, but it is less used: (Link 
to forums). We also maintain a list of know bugs (link to bugs).



As FreeDOS is free to modify, any one can get the source code (link to source 
code) and propose modifications to it.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Thinking about FreeDOS 2.0

[Paul Dufresne via Freedos-devel]

 Activé jeu., 31 mars 2022 21:42:12 -0400 Michael Brutman 
 écrit 



Please forgive me for getting lost on this thread, but what exactly is the 
problem that we are trying to solve?



Are we trying to make things simpler for novice users?  Advanced users?  
FreeDOS maintainers (Jerome in particular) ?












When I said one should not modify a previous main directory of a released 
version, I think the problem I try to resolve is to allow maintainers of 
packages to compare the version on the released media with the more recent 
versions, be it to evaluate the impact of a vulnerability or a change causing 
bug in earlier version, or something similar.



My idea of releasing is, mostly upgrading the tree of packages by:

1)creating a new sub-version main repository that contains security and updates 
of the current version

2)create an empty sub-version update and a security repository

3)create a new sub-version media with the content of the newly created main 
repository created at step 1



I think part of the reason that we have not feel the need to do it like that is 
that we build the media from an alternative

place: gitlab repository. So we don't need, did not need the main repository to 
build the media.



Maybe we should come back to the question wheter we should continue to use 
ibiblio for releasing packages, or should concentrate on a (gitlab or github) 
repository.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Thinking about FreeDOS 2.0

[Paul Dufresne via Freedos-devel]

 Activé lun., 28 mars 2022 13:43:58 -0400 Jerome Shidel  
écrit 


Linux distress behave the same way. The online repository provides the newest 
version of the packages. When you select to install something from online, it 
does not install the old version that would have come with the release. It 
installs the newest version available. 






Actually, most Linux distributions do quite the reverse as far as I know.

Here is an extract (I removed not significative lines) from my 
/etc/apt/sources.list file:

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to

# newer versions of the distribution.

deb http://ca.archive.ubuntu.com/ubuntu/ impish main restricted

deb-src http://ca.archive.ubuntu.com/ubuntu/ impish universe restricted main 
multiverse #Added by software-properties

# deb-src http://ca.archive.ubuntu.com/ubuntu/ impish restricted



## Major bug fix updates produced after the final release of the

## distribution.

deb http://ca.archive.ubuntu.com/ubuntu/ impish-updates main restricted

deb-src http://ca.archive.ubuntu.com/ubuntu/ impish-updates universe restricted 
main multiverse #Added by software-properties

# deb-src http://ca.archive.ubuntu.com/ubuntu/ impish-updates main restricted





deb http://ca.archive.ubuntu.com/ubuntu/ impish-security main restricted

deb-src http://ca.archive.ubuntu.com/ubuntu/ impish-security universe 
restricted main multiverse #Added by software-properties

deb http://ca.archive.ubuntu.com/ubuntu/ impish-security universe

deb http://ca.archive.ubuntu.com/ubuntu/ impish-security multiverse



As you can see, it separate the main repositories, from the updates, and the 
security fixes.

I guess security fixes could be merged with the updates. Not sure it is a good 
idea to do so however.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Thinking about FreeDOS 2.0

[Paul Dufresne via Freedos-devel]

The branches that receive updates (1.2, 1.3, latest) contain the latest version 
of the packages that we have created. I don’t see a reason to add a new branch. 
If we decided to change package file extensions (and possibly format), 1.2 and 
1.3 would be detached from Latest. And most likely would receive few if any 
updates.



Jim already provides the ‘raw’ files under a couple directories at 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/ . They are raw mirrors 
and most are not in package format. 

Oh, I was confused thinking latest was not in package format. It is because it 
is in repositories.

I see that there is less categories in freedos/files than in the repositories 
however.



I am very surprised that 1.2 and 1.3 repositories are (still unsure) symlinks 
to latest repository.

Because in my mind, you have no right to modify 1.2 or 1.3 after they have been 
released.

But it seems the project don't share this mindset.




As for changing the extension, IDK. It would prevent users from just unzipping 
things which is good and bad. As for the extension, .dpk is already in use and 
would probably cause confusion. Not sure about .dpg. But if we were to change 
it, I think I’m partial to .fdp (F)ree(D)OS (P)ackage.








I like very much the .fdp suggestion.



I think we should set for goal to be able to use USB keys and drives for next 
version.

Almost every computer have USB, but not as much have optical drives.

USB disk images, or simply a .zip of a repository that you would copy on your 
USB drive for installation would be very nice.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Thinking about FreeDOS 2.0

[Paul Dufresne via Freedos-devel]

 Activé lun., 28 mars 2022 08:24:15 -0400 Jerome Shidel  
écrit 
>But with how easy package installation is after the initial install using 
>FDIMPLES, I wonder
> why bother with FULL at all?  Why not just install BASE? The user could 
> install additional packages later
For people installing on real hardware, DOS may not provide network drivers for 
their hardware.
For them installing almost all make much sense.

I was about writing some of my ideas about goint toward constant releases.

Current ibiblio repositories goes like:
1.1
1.2
1.3
latest

I am thinking going toward:
1.1
1.2
1.3
1.3Updates
raw
next

where 1.3 updates would contains new packages for 1.3, even if fdimples would 
probably know how to
handle it... still usefull to me to have a place with just changed packages 
since 1.3

raw would be not yet packaged files... for developers not making specifcally 
freedos packages

next would be the next version with the new ideas, maybe with a slightly 
differrent package format.
I am thinking about having an extension of .dpk or .dpg for (Free)D(os) 
packages. To make it explicit
it is a file ready to be served to fdimples, rather than some .zip file.



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Ré : doslfn need updating to version 0.41e

[Paul Dufresne via Freedos-devel]

More precisely 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/latest/drivers/doslfn.zip
 need to be updated wih:

http://adoxa.altervista.org/doslfn/ version 0.41e

more or less... I guess it need some repackaging?___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] doslfn need updating to version 0.41e

[Paul Dufresne via Freedos-devel]

 Activé sam., 26 mars 2022 06:21:55 -0400 Eric Auer  
said 

>https://www.bttr-software.de/forum/forum_entry.php?id=18909 
> 
>another bug in doslfn (Announce) 
> 
>posted by jadoxa, Queensland, Australia, 26.03.2022, 08:49 

So it seems that 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.3/pkg-html/doslfn.html
would need to be updated (but probably not in that place because 1.3 have been 
released) with:
http://adoxa.altervista.org/doslfn/ version 0.41e
 
 



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Lost in translation, tried to compiled with Lazarus

[Paul Dufresne via Freedos-devel]

Using Linux (Ubuntu 21.10) right now, I decided to give a try at compiling your 
project with Lazarus.

The version coming with Ubuntu 21.10 is: 2.0.12.



With it, opening the project file was like there was no units files in the 
project.



So I decided to try with latest version (2.2) from the website.



Now it shows the files fine.



But when I tried to compile at first I got error in:

ulog.pas:37 on "uses uAppCfg;" ... tried to comment it and then got:

ulog.pas:64 GetPropertyState unknown identifier

ulog.pas:73 SetPropertyState unknown identifier



So now I am curious if you use other libraries ... and the version you use.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Broken links for Turbo C++ 1.01 and Turbo C 2.01 on Link page

[Paul Dufresne via Freedos-devel]

The page: https://freedos.org/links/

(Programming section)

seems to have broken links for for Turbo C++ 1.01 and Turbo C 2.01.



The following link have those, with more info about license "personal use only":

https://web.archive.org/web/20050310144630/http://bdn.borland.com/all/0,1435,museum|0|30,00.html___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Does FreeDOS (or something) sometime automatically break up an hard disk in 2GB sub-disks?

[Paul Dufresne via Freedos-devel]

As the function to autoformat in fdisk is relatively small, let me copy it here:
First function in the file:
https://gitlab.com/FDOS/base/fdisk/-/blob/master/SOURCE/FDISK/FDISK/FDISKIO.C

/* Automatically partition the selected hard drive */
void Automatically_Partition_Hard_Drive()
{
  int index=0;
/*  unsigned long maximum_partition_size_in_MB; */
  Partition_Table *pDrive = _table[(flags.drive_number-128)];

  Determine_Drive_Letters();

  /* First, make sure no primary or extended partitions exist. */
  /* Compaq diagnostic partitions are ok, though.  */
  do
{
if( (brief_partition_table[(flags.drive_number-128)] [index]>0) && 
(brief_partition_table[(flags.drive_number-128)][index]!=18) )
  {
  printf("\nThe hard drive has already been partitioned...Program 
Terminated.\n");
  exit(7);
  }

index++;
}while(index<4);

  /* Create a primary partition...if the size or type is incorrect, */
  /* int Create_Primary_Partition(...) will adjust it automatically.*/
  Determine_Free_Space();
  Set_Active_Partition(Create_Primary_Partition(6,2048));

  /* Create an extended partition, if space allows. */
  Determine_Free_Space();
  if( pDrive->pri_part_largest_free_space > 0)
{
Create_Primary_Partition(5,99ul);

/* Fill the extended partition with logical drives. */
Determine_Free_Space();
do
  {

  Create_Logical_Drive(6,2048);

  Determine_Free_Space();
/*  maximum_partition_size_in_MB
   = (pDrive->ext_part_largest_free_space+1)*
   (pDrive->total_head+1)*
   pDrive->total_sect / 2048; */
  }while(  (pDrive->ext_part_largest_free_space > 0)
&& (Determine_Drive_Letters()<'Z') );
}
}

So, at first glance it confirms the idea: Make a primary 2 GB partition, then 
add 2 GB logical partitions until there is no free space.

It's better than what I expected... I mean it is written in C not in 
assembler... except for boot sector code ... of course.


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Does FreeDOS (or something) sometime automatically break up an hard disk in 2GB sub-disks?

[Paul Dufresne via Freedos-devel]

 Le ven., 24 sept. 2021 13:22:11 -0400 Eric Auer  écrit 


 > 
 > Hi Jerome, 
 >  
 > > If ... there are no partitions on the target hard drive, 
 > > it tells fdisk to automatically partition the drive... 
 >  
 > > If there is a command line option to perform automatic 
 > > partitioning using a single big partition, I am unaware of it. 
 >  
 > If FDISK defaults to making 1000 partitions of 2 GB each 
 > when you have a 2 TB drive, that is utterly useless. MOST 
 > users will have FAR more than 60 GB disk size and you can 
 > have only 24 drive letters from C: to Z: 
 >  
 > This makes FreeDOS look ridiculously 1980s, sorry. Any 
 > workarounds possible? 
 >  
 > Regards, Eric 

Well... looks like we are using indeed 1980 technology in 2021.

The FDISK docs says that /AUTO disk partition the disk with FAT16 partitions.
https://help.fdos.org/en/hhstndrd/fdisk.htm

We know FAT16 bigger partition size is 2GB:
https://softwareengineering.stackexchange.com/questions/370180/why-can-fat16-not-store-more-than-2-gb

We probably don't want to break current /AUTO for people using it to do 2 GB 
partitions... [supposing such persons exist]

Then we probably need a new option (/AUTOFAT32 ?) that would partition in ... 
well... ideally would find the minimum of "full disk"
and BIOS maximum supported size according to bits in LBA... I suppose.

... or much more simply... force user to format manually and never autoformat 
the disk?


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Does FreeDOS (or something) sometime automatically break up an hard disk in 2GB sub-disks?

[Paul Dufresne via Freedos-devel]

Ok... when I wake up this morning... I realized I knew more of this problem 
than I thought.

Having look at the installer scripts before, I kind of remember that in some 
case it split the
image file (normally the FreeDOS image file) in 2 GB chunks. I did not 
understood it clearly.

Shidel would know what I am talking... I hope.

It is a bit like if it was my hard disk that was cut in 2 GB chunks rather than 
the USB FreeDOS image.

I'll mark the laptop for future tests... like FreeDOS install on random erased 
disk.  But my priority is to figure out why an
other computer have corrupted video when coming back from suspend to ram on 
Linux.


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Does FreeDOS (or something) sometime automatically break up an hard disk in 2GB sub-disks?

[Paul Dufresne via Freedos-devel]

Tom said:
> Why do you need to subdivide the 60 GB hard disk into 2 GB partitions? 
It's not that I need to subdivide into 2 GB partition.
This newly bought old laptop was saying "No OS".
And while booting FreeDOS it was showing almost a screen full of 2 GB 
partitions...
I kind of assume it was a bug or a feature... was not really believing it had 
really many  2 GB partitions... would have to be GPT.
But I did not even launched fdisk to check... now, many hours later, I realize 
how weird it was... and wrote previous email.

I regret that I was not in a mood to investigate when it happened.


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Does FreeDOS (or something) sometime automatically break up an hard disk in 2GB sub-disks?

[Paul Dufresne via Freedos-devel]

I was testing an old laptop (Thinkpad I think, 2 cores, with a 60 GB hard disk).

I wanted to install a Linux, but as the CPU was 32 bits, I had some difficulty 
finding a 32 bits OS.

One of my USB keys, had FreeDOS beta on it... so I tried it.

When installing, I saw (was scrolling fast)... that it was assigning letters to 
a lot (maybe A: to L:), to

2 GB hard drives it was detecting. I did not care that much, and tried to 
install on the 2 Gb first disk C:.

And it installed fine... except not long after I found an other USB key with 
Debian 32 bits and installed it.



I am pretty sure the laptop have only one 60 GB hard disk and not many 2 GB 
hard disk.



I came to my mind that maybe the kernel or the installer... knows more than me 
that the BIOS is limited

to 2 GB, and somehow it chop the disk in 2 GB sub-disks... maybe the BIOS 
itself could do it...



Have you heard of such things before?___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] cpp -remap Enable special code to work around file systems which only permit very short file names, such as MS-DOS.

[Paul Dufresne via Freedos-devel]

While reading by mistake https://gcc.gnu.org/onlinedocs/cpp/Invocation.html

(I had searched for gcc invocation)

So this is the preprocessor (to gcc).



I noted these parameters that can seems usefull for FreeDOS and less for DJGPP:



-remap

Enable special code to work around file systems which only permit very
short file names, such as MS-DOS.


-fexec-charset=charset

Set the execution character set, used for string and character
constants.  The default is UTF-8. charset can be any encoding
supported by the system’s iconv library routine.


-finput-charset=charset

Set the input character set, used for translation from the character
set of the input file to the source character set used by GCC.  If the
locale does not specify, or GCC cannot get this information from the
locale, the default is UTF-8.  This can be overridden by either the locale
or this command-line option.  Currently the command-line option takes
precedence if there’s a conflict. charset can be any encoding
supported by the system’s iconv library routine.___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel