Re: [Freedos-devel] DOSLFN bugfix explanations and ideas - was: FreeDOS Interim Build T2508

2025-08-23 Thread tom ehlert via Freedos-devel
Just wondering: is it possible that all reported file system corruptions were for FAT12/FAT16 disks? Because - as I understand it - the FAT32 disk read mechanism (INT21 AX=7305) has protection against the supposed bug, while FAT16 (INT25/26) has not. Tom

Re: [Freedos-devel] DOSLFN bugfix explanations and ideas - was: FreeDOS Interim Build T2508

2025-08-15 Thread tom ehlert via Freedos-devel
in small chunks. > We're not protecting anything by keeping INT 25/26 > traffic out of it. +1 INT 25/26 traffic should behave as other kernel traffic, with (for certainty) have a "flush dirty sectors" after each INT 26 WRITE request (just in case it might be buffered). To

Re: [Freedos-devel] DOSLFN bugfix explanations and ideas - was: FreeDOS Interim Build T2508

2025-08-14 Thread tom ehlert via Freedos-devel
Hallo Herr Eric Auer via Freedos-devel, am Dienstag, 5. August 2025 um 02:00 schrieben Sie: > Hi Tom, >> cache INVALIDATION is only needed because the BUFFERS cache >> might have stale data that are not yet on disk. >> It's a brute force clutch, not a real sol

Re: [Freedos-devel] DOSLFN bugfix explanations and ideas - was: FreeDOS Interim Build T2508

2025-08-02 Thread tom ehlert via Freedos-devel
nce for another day; FreeDOS managed without it for the last 30 years. It's mind blowing better then not-delayed-write caching for certain use cases like compiling large packages repeatedly, but mostly pointless in todays SSD based virtual e

Re: [Freedos-devel] DOSLFN bugfix explanations and ideas - was: FreeDOS Interim Build T2508

2025-08-01 Thread tom ehlert via Freedos-devel
d LBACACHE shouldn't make a difference bug-wise. I don't know if ResetDrive forces a Reset down the entire chain of DOSLFN/kernel/BIOS/harddisk which would be drastic. Tom ___ Freedos-devel mailing list Freedos-devel@lists.s

Re: [Freedos-devel] File Name Bug

2025-06-10 Thread tom ehlert via Freedos-devel
ight be interesting to look what interfaces to DOS DOSLFN uses. One quick experiment would be to run the install procedure using BUFFERS=1 and see if the missing files in ADT2.LST vary. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Extended keyboard flag at 0040:0096 gets unexpectedly cleared

2025-05-31 Thread tom ehlert via Freedos-devel
Hallo Herr Bob Smith via Freedos-devel, am Freitag, 30. Mai 2025 um 22:37 schrieben Sie: > On 5/30/2025 3:14 PM, tom ehlert via Freedos-devel wrote: >> Bob, >> >>> It can be loaded from CONFIG.SYS. Perhaps the events you want to trap >> >>> appear before

Re: [Freedos-devel] Extended keyboard flag at 0040:0096 gets unexpectedly cleared

2025-05-30 Thread tom ehlert via Freedos-devel
Hallo Herr Bernd Böckmann via Freedos-devel, am Freitag, 30. Mai 2025 um 19:17 schrieben Sie: > Hi Tom, >> after all this work, it's time for the EXTKEYB.EXE utility. >> >> It's quick and efficient, patent free and listed below >> >> >> #inc

Re: [Freedos-devel] Extended keyboard flag at 0040:0096 gets unexpectedly cleared

2025-05-30 Thread tom ehlert via Freedos-devel
oaded before CONFIG.SYS. Unfortunately even this superpower tool can't catch events that don't happen (even if I had one of these machines). Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Extended keyboard flag at 0040:0096 gets unexpectedly cleared

2025-05-30 Thread tom ehlert via Freedos-devel
So this could also set 40:96, so EDIT is happy as well. Might require mKEYB US /E on some machines, but such is life;) Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Extended keyboard flag at 0040:0096 gets unexpectedly cleared

2025-05-30 Thread tom ehlert via Freedos-devel
as this. 386SWAT is probably absolutely fine. However when it appeared I had already 10+ years of experience with S-ICE. So I never changed my favorite debugger. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Extended keyboard flag at 0040:0096 gets unexpectedly cleared

2025-05-30 Thread tom ehlert via Freedos-devel
Hi Bernd, after all this work, it's time for the EXTKEYB.EXE utility. It's quick and efficient, patent free and listed below #include main() { *(unsigned char far *)MK_FP(0x40,0x96) |= 0x10; } to be run on buggy machines, before mKEYB

Re: [Freedos-devel] Kernel package question

2025-05-28 Thread tom ehlert via Freedos-devel
ractice MANY users "live" updates. And that is exactly the reason that you don't "test" a new kernel by mixing it with thousands of packages. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel]  Re: Kernel package question

2025-05-28 Thread tom ehlert via Freedos-devel
Hi Bernd, >> Am 27.05.2025 um 16:17 schrieb tom ehlert via Freedos-devel >> : >> >> I don't have any secret information. >> I'm just worried that there might be a reason PerditionC hasn't released >> *any* kernels over the last few years, whi

Re: [Freedos-devel] List of Exitcodes

2025-05-28 Thread tom ehlert via Freedos-devel
ace", "invalid handle", "access denied" etc. is used consistently between different DOS function calls. AFAIK there is no list of error codes for different DOS commands. Tom ___ Freedos-devel mailing list Freedos-devel@lists.source

Re: [Freedos-devel]  Re: Kernel package question

2025-05-27 Thread tom ehlert via Freedos-devel
Fritz, > Tom, > I am not sure if understand the trial system of FDT250x: > The kernel will be online for one month till the next version e.g. FDT2507. > So if someone reports a bigger problem with the kernel it will disappear > within one month. > I know bugs that are 20

Re: [Freedos-devel]  Re: Kernel package question

2025-05-27 Thread tom ehlert via Freedos-devel
Hallo Herr Bernd Böckmann via Freedos-devel, am Dienstag, 27. Mai 2025 um 11:52 schrieben Sie: >> Am 27.05.2025 um 09:02 schrieb tom ehlert via Freedos-devel >> : >> >> A new kernel.sys can be - and should be - tested independently of all the >> surrounding s

Re: [Freedos-devel]  Re: Kernel package question

2025-05-27 Thread tom ehlert via Freedos-devel
nents should NEVER be tested in conjunction with multiple other changes. NEVER. And that's easy for DOS. Tom > cheers, > willi > -- > Gesendet mit der mail.com Mail App > Am 26.05.25, 23:13 schrieb "Bernd Böckmann via Freedos-devel" > : > Thanks Jerom

Re: [Freedos-devel] Kernel package question

2025-05-26 Thread tom ehlert via Freedos-devel
Hallo Herr Jerome Shidel via Freedos-devel, am Montag, 26. Mai 2025 um 16:52 schrieben Sie: > Hi Tom, >> On May 26, 2025, at 10:03 AM, tom ehlert via Freedos-devel >> wrote: >> >> Hallo Herr Jerome Shidel via Freedos-devel, >> >> am Montag, 26. Mai

Re: [Freedos-devel] Kernel package question

2025-05-26 Thread tom ehlert via Freedos-devel
partitions, Whoever invented "LFS" can he please stay somewhere in the 100+ years future, (or simply OFF this list) so I don' have to turn in my grave so often? > LFN = really long file names) it has been "long file names" for ~30 y

Re: [Freedos-devel] How to idle under DOS?

2025-05-19 Thread tom ehlert via Freedos-devel
t; r.w.ax = 0x1680; >>> intr(0x2f, &r); >>> no_multiplex_int = r.h.al; >>> } >>> else { >>> cpu_hlt(); >>> } I'd recommend Bernd's method. It's the be

Re: [Freedos-devel] How to idle under DOS?

2025-05-19 Thread tom ehlert via Freedos-devel
hat > you need. Link - https://www.vogons.org/viewtopic.php?f=24&t=43384#p438763 "- 100% ASSEMBLY coded, therefore program should be both fast and small (the resident part of DOSidle is less than 3K)." And has command line optio

Re: [Freedos-devel] question on use!umb for FreeDOS XMS stuff

2025-05-12 Thread tom ehlert via Freedos-devel
ing the MCB > with 00 bytes. Maybe you have some controller buffer at the address? Nice analysis. on first glance: USE!UMB should have checked that this memory is indeed writable. It seems it's not and that is just a stupid program bug. The cool thing is that source is provided, and some g

Re: [Freedos-devel]  Re: FreeDOS EDIT fork

2025-05-01 Thread tom ehlert via Freedos-devel
> Btw, @ tom, msedit is not from MS but from Mateusz Viste, but it is not > complete. I have decided on my DOS editor 30 years ago; so I have no opinion in this. Still interested in what is an editor that "it is not complete." ? Tom ___

Re: [Freedos-devel] SETVER support

2025-04-28 Thread tom ehlert via Freedos-devel
ve a > fixed list. extraction the version wanted out of mov AH, 30h int 21h cmp ax, ABCD <<< this is the version wanted jne exit_program is not "heuristic". So simple. It returns exactly the version required to the calling program. if this reques

Re: [Freedos-devel] FreeDOS 1.4 known issues

2025-04-28 Thread tom ehlert via Freedos-devel
eate a new editor". Unpaid time, of course. Don't complain. There are literally hundreds of free editors available for DOS. Just go ahead and locate one, for you and for us. But don't complain! Tom ___ Freedos-devel mailing list Freedos-d

Re: [Freedos-devel] SETVER support

2025-04-26 Thread tom ehlert via Freedos-devel
rick to execute them anyway;) that's easy as they are all written in assembly and probably have the same macro VERIFY_OS_VERSION included. for general programs that's pretty useless because there are sooo many variations of this. it also doesn't help for programs

Re: [Freedos-devel] Extended keyboard flag at 0040:0096 gets unexpectedly cleared

2025-04-17 Thread tom ehlert via Freedos-devel
>> Am 16.04.2025 um 21:32 schrieb tom ehlert via Freedos-devel >> : >> >> before you posted "the flag gets cleared even before the first driver is >> loaded, depending on what gets selected in the FreeDOS >> boot menu (probably more which

Re: [Freedos-devel] Extended keyboard flag at 0040:0096 gets unexpectedly cleared

2025-04-16 Thread tom ehlert via Freedos-devel
u have an extended keyboard (whatever that is) Yes/No because one buggy BIOS? absolutely NO! > , and adapting fdauto.bat accordingly. neither > Bernd Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Extended keyboard flag at 0040:0096 gets unexpectedly cleared

2025-04-14 Thread tom ehlert via Freedos-devel
Hallo Herr Bernd Böckmann via Freedos-devel, am Montag, 14. April 2025 um 20:05 schrieben Sie: >> Am 14.04.2025 um 15:50 schrieb tom ehlert via Freedos-devel >> : >> >> You are saying that this depends on the menu option being 3, independent of >> the eff

Re: [Freedos-devel] Extended keyboard flag at 0040:0096 gets unexpectedly cleared

2025-04-14 Thread tom ehlert via Freedos-devel
h JEMM386 (Expanded Memory) > MENU 4 - Load FreeDOS low with some drivers (Safe Mode) > MENU 5 - Load FreeDOS without drivers (Emergency Mode) DEVICE=C:\EXTKBD2.EXE reports 40:96 cleared? no EMM386 involved? nowhere? this would be hard to believe. time to modify the kerne

Re: [Freedos-devel] Extended keyboard flag at 0040:0096 gets unexpectedly cleared

2025-04-14 Thread tom ehlert via Freedos-devel
tform". It was easy because everybody hates VMWARE. In the current case, the suggested solution is "write a device driver that sets 0040:0096" so you can avoid /E. Or send in the machine (which he probably won't do). Tom ___

Re: [Freedos-devel] FreeDOS 1.4 News

2025-04-10 Thread tom ehlert via Freedos-devel
; than the others. > https://www.theregister.com/AMP/2025/04/09/freedos_14/ Specifically for coining "more modern than ever" and the immortal "One that we haven't tried is another free DOS-compatible OS called the Public

Re: [Freedos-devel] XCOPY 1.7 Stack Overflow

2025-04-05 Thread tom ehlert via Freedos-devel
name ... while (find_next_dir(dir_below)) { strcat(source, "\\"); strcat(source, "DIRBELOW"); do_stuff_for _directory_down(source) *origsource = '\0'; } s

Re: [Freedos-devel] release MOVE 3.4 WAS: Re: XCOPY 1.7 Stack Overflow

2025-04-04 Thread tom ehlert via Freedos-devel
. so it won't copy files > 2GB because there is not enough space. Same problem as in ZEROFILL. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] kernel 4GB fix, was release MOVE 3.4 WAS: Re: XCOPY 1.7 Stack Overflow

2025-03-28 Thread tom ehlert via Freedos-devel
Hallo Herr tom ehlert via Freedos-devel, am Donnerstag, 27. März 2025 um 17:56 schrieben Sie: > Hallo Herr Fritz Mueller via Freedos-devel, > am Donnerstag, 27. März 2025 um 17:51 schrieben Sie: >> thanks, I already tested it, also works fine. so only the copy command is >

Re: [Freedos-devel] Replace dosdef.com by my defender.exe?

2025-03-28 Thread tom ehlert via Freedos-devel
e don't have a joystick. > Admittedly, original game was about 20kb, and now the default version is 1.4 > Mb... but can be stripped to 800kb. absolutely amazing coding skills. (Possibly) Shrinking the app by 600k is absolutely remarkable. > The question is does it

Re: [Freedos-devel]  Re: release MOVE 3.4 WAS: Re: XCOPY 1.7 Stack Overflow

2025-03-27 Thread tom ehlert via Freedos-devel
git that 3 files with 1,6 gb and copy a +b +c 4 > gb creates a 4gb file where the rest of file c is written to the beginning of > a on the 4gb file). but this is a thing that should rarely happen and can be > fixed with the next kernel/command.com. it's a kernel bug. I will po

Re: [Freedos-devel] [Off-topic] It is almost a game now

2025-03-26 Thread tom ehlert via Freedos-devel
Dear Paul, it would be really cool if you could stop posting [Off-topic] stuff to this list. Thank you. Tom am Donnerstag, 27. März 2025 um 06:05 schrieben Sie: > I change a bit my approach to the AI. > I added a System Instruction: > I am an AI that want to translate dosdef.co

Re: [Freedos-devel] release MOVE 3.4 WAS: Re: XCOPY 1.7 Stack Overflow

2025-03-24 Thread tom ehlert via Freedos-devel
ng makefiles. and - as freedos-devel doesn't allow .zip files - the attached .SVP is a .ZIP file Tom move35.svp Description: Binary data ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] XCOPY 1.7 Stack Overflow

2025-03-21 Thread tom ehlert via Freedos-devel
ppens at the same point. See if > adding, moving or removing files or directories effects it. Log the error. Logging would be important, yes. And it's easy due to LOGGER. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] XCOPY 1.7 Stack Overflow

2025-03-21 Thread tom ehlert via Freedos-devel
c:\a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\someFile will consistently nuke XCOPY and MOVE, and we know why. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] dosdef(ender): just a blue screen

2025-03-20 Thread tom ehlert via Freedos-devel
obably DosBox should be fixed to return AH=86h when no joystick is present. > _______ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel Mit freundlichen Grüßen / with kind regards Tom Ehlert +49-15151898538 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Ré : Ré : 1.4-RC3: bolitare fail to start when doslfn is loaded

2025-03-17 Thread tom ehlert via Freedos-devel
Hallo Herr Ralf Quint via Freedos-devel, am Montag, 17. März 2025 um 20:34 schrieben Sie: > On 3/17/2025 10:58 AM, tom ehlert via Freedos-devel wrote: >> Hi Ralf, >> >> al_findfirst() seems to be implemented by the GCC RTL. This might as well be >> a bug in this imp

Re: [Freedos-devel] Ré : Ré : 1.4-RC3: bolitare fail to start when doslfn is loaded

2025-03-17 Thread tom ehlert via Freedos-devel
gt; findfirst() that craps out, as with LFN, the structure of ffblk is likely > only accounting for a "regular" 8.3 filename, space wise, but gets a longer > result back from the LFN enabled kernel file functions... most likely not so. It's certainly the right corner to look (

Re: [Freedos-devel] Freedos SOURCES

2025-03-04 Thread tom ehlert via Freedos-devel
tle FreeDOS sources, and " How to contribute" leads into internet desert. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] LANGuage Support

2025-03-04 Thread tom ehlert via Freedos-devel
Hallo Herr Bernd Böckmann via Freedos-devel, am Dienstag, 4. März 2025 um 01:18 schrieben Sie: > Hello Tom, >> Am 04.03.2025 um 00:42 schrieb tom ehlert via Freedos-devel >> : >> >> My suggestion would be to attach these language data to the end of the .exe >&

Re: [Freedos-devel] LANGuage Support

2025-03-03 Thread tom ehlert via Freedos-devel
printf("%s\n", kittengets(1,22, "can't write file. Disk full??")); is much easier to navigate then if (result != 0) printf("%s\n", kittengets(1,22)); In particular if you try to locate the issue that prints "Disk full". It's also a matte

Re: [Freedos-devel]  Re: LANGuage Support

2025-03-03 Thread tom ehlert via Freedos-devel
Hallo Willi, ich habe vermutlich dieser Tage einen KERNEL.SYS der nicht mehr mehr als 4G Files erzeugt MOVE.EXE der Files > 2G verschieben kann. Möchtest du die testen? Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net ht

Re: [Freedos-devel] LANGuage Support

2025-03-03 Thread tom ehlert via Freedos-devel
h LFNs and UniCode which are both outside the realm of "regular" > DOS. right. > BTW, one option I was considering is a single .LNG file (or something) with > all the translations inside a single file instead of needing a separate file > for each language. I don't know if that's a good idea or not -- it's > certainly incompatible with KITTEN, at least in its current form. Your program. Your data. KITTEN has no intention to read your data. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Freedos SOURCES

2025-03-02 Thread tom ehlert via Freedos-devel
Hallo Herr tom ehlert via Freedos-devel, am Sonntag, 2. März 2025 um 09:46 schrieben Sie: > Hi everybody, > just noted that DOSFSCK is missing from > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/. > Which is sad as CHKDSK doesn't touch FAT32 drives. I

Re: [Freedos-devel] FreeDOS 1.4-RC3

2025-03-02 Thread tom ehlert via Freedos-devel
"File most probably corrupted now: %s\n", argv[1]); return 75; } } silently doing nothing when compiler is GCC isn't smart (as the last version did). please do at least ... else printf("while instructed to do so

Re: [Freedos-devel] Freedos SOURCES

2025-03-02 Thread tom ehlert via Freedos-devel
o be able to handle even FAT32 partitions, but i don't know how far. have a good night, Ralf Congratulations for this marvel of software engineering. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Freedos SOURCES

2025-03-02 Thread tom ehlert via Freedos-devel
erything else just copies? Would it be possible to place a link to this at freedos.org? Is the task "FreeDOS is an open source operating system. Locate MOVE sources from freedos.org" included in Jims "usability testing" of the website? Tom _

Re: [Freedos-devel] ospimg has a bug... with 5.25 (13cm) DD disks in an HD Drive..

2025-03-02 Thread tom ehlert via Freedos-devel
you please provide help how to do this? Similar problems with landing on the moon. Many thanks in advance! Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS 1.4-RC3

2025-03-01 Thread tom ehlert via Freedos-devel
publish software with known, fixed bugs. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS 1.4-RC3

2025-03-01 Thread tom ehlert via Freedos-devel
Hallo Herr Jerome Shidel via Freedos-devel, am Samstag, 1. März 2025 um 20:22 schrieben Sie: > Hi Tom, >> On Mar 1, 2025, at 1:42 PM, tom ehlert via Freedos-devel >> wrote: >>  >>> I do not think the “out of memory” issue on VMware has had a resolution >>

[Freedos-devel] Freedos SOURCES

2025-03-01 Thread tom ehlert via Freedos-devel
edos/files/dos/keyb. How is someone supposed to find this? why does https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/ still exist when newer sources seem to exist at https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.4 ? Tom __

Re: [Freedos-devel] Fwd: Re: Problem with writes to NVMe disk

2025-02-28 Thread tom ehlert via Freedos-devel
> sizes. That makes me wonder: what is the realistic datarate of a 1,5 MB/sec UHCI connection? Is it really 1,5 MB of transferred data or more like 1/3 of that (0.5MB/sec) as is the case in USB 2.0? Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Fwd: Re: Problem with writes to NVMe disk

2025-02-28 Thread tom ehlert via Freedos-devel
Hallo Herr Kirn Gill II via Freedos-devel, am Donnerstag, 27. Februar 2025 um 23:34 schrieben Sie: > Isn't this the same argument I made for broken hypervisors? Yes. With the tiny little difference that we have one broken machine, and no broken hypervisors. Tom > -- > Kirn Gi

Re: [Freedos-devel] Fwd: Re: Problem with writes to NVMe disk

2025-02-27 Thread tom ehlert via Freedos-devel
nothing about *this particular* machine. It's most likely a buggy BIOS/CSM or buggy firmware (unlikely, else windows wouldn't work), and not worth throwing valuable developer time at. Just don't execute DOS on this system. Tom ___ Freed

Re: [Freedos-devel] MEM null string bug fix

2025-02-25 Thread tom ehlert via Freedos-devel
C in EDR-DOS). Even ~22 years ago I wasn't too fluent in alphabet soup. Today, even less so. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] MEM null string bug fix

2025-02-25 Thread tom ehlert via Freedos-devel
rent->size; +end=parent->seg + parent->size + 1; so what. might be wrong, but then only the wrong size reported. should be not important. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Make make great again!

2025-02-25 Thread tom ehlert via Freedos-devel
Hallo Herr Gregory Pietsch via Freedos-devel, am Donnerstag, 24. Oktober 2024 um 19:17 schrieben Sie: > I am sending a GPLed version of the Unix make utility in the hopes that other > programmers can make it great again! Please send back improvements. Place it into the next garbage bin

Re: [Freedos-devel] New libm-0.10!

2025-02-25 Thread tom ehlert via Freedos-devel
or(__LINE__); or similar. How is the correctness assured? >- Testing, testing, more testing, and debugging of the functions that >are already written. That's ridiculous without indication what has already debugged, and what not. So certainly not "1.

Re: [Freedos-devel] Suggestion: Disclaim support for Broadcom virtualization products.

2025-02-22 Thread tom ehlert via Freedos-devel
onale for change: Peace and quiet from someone else's bugs. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] What the AI says about the problem of Out of memory

2025-02-21 Thread tom ehlert via Freedos-devel
UMB is available). in that case the automatically expanded MCB is stopped at the first loaded TSR. FreeCOM command that rely on malloc() for what they do may fail because "extraMin minimal and dynamically adjusts its MCB" is no longer available. Fre

Re: [Freedos-devel] I would prefer DOS not to load in high if XMS_SWAP is available

2025-02-21 Thread tom ehlert via Freedos-devel
Hallo Herr Eric Auer via Freedos-devel, am Freitag, 21. Februar 2025 um 13:20 schrieben Sie: > Hi Tom, >>> As you already say, XMS SWAP in FreeCOM already makes DOS >>> memory footprint very small while apps run, >> Which is true - because XMS_SWAP >>&

Re: [Freedos-devel] I would prefer DOS not to load in high if XMS_SWAP is available

2025-02-21 Thread tom ehlert via Freedos-devel
space to residents programs. > So my proposition is to load DOS low, if XMS_SWAP is available. My suggestion is to learn your "101 DOS memory allocation" and "202 DOS advanced memory juggling" before coming up with propositions. Thanks for your time. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] I would prefer DOS not to load in high if XMS_SWAP is available

2025-02-21 Thread tom ehlert via Freedos-devel
oad it high into precious UMB, where it > would require quite a bit of memory while no app runs! Which is nonsense - because XMS_SWAP. Low memory is still more precious then UMB memory. > So I support your suggestion: No SHELLHIGH of XMS SWAP > FreeCOM in the default c

Re: [Freedos-devel] What the AI says about the problem of Out of memory

2025-02-19 Thread tom ehlert via Freedos-devel
Hallo Herr Bernd Böckmann via Freedos-devel, am Mittwoch, 19. Februar 2025 um 21:05 schrieben Sie: > I agree with Tom that changing the EXE header should be to way to go. > I did a quick test by patching the COMMAND.COM header by hand with a hex > editor. > When I patch offse

Re: [Freedos-devel] What the AI says about the problem of Out of memory

2025-02-19 Thread tom ehlert via Freedos-devel
likely tools\patchsize command.com +6K does the same, but should be changed to tools\patchsize command.com +8K I don't have VMWARE to reproduce the bug Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Usability testing on www.freedos.org

2025-02-19 Thread tom ehlert via Freedos-devel
available on GitHub as > artifacts for testing. My interest in testing 'artifacts' is limited. publish some kernel/command with a "this should work" note at least. > It is a nice part of using GitHub CI which > eventually will allow doing more comprehensive tests f

Re: [Freedos-devel] Useful tool: stuffkey

2025-02-18 Thread tom ehlert via Freedos-devel
table to add to FreeDOS? " mails coming next. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Proposal: replace FreeDOS Edit with SvarDOS Edit

2025-02-18 Thread tom ehlert via Freedos-devel
. it provides a minimum ASM stub, which calls a C main() which does all the hard work. highly recommended for all people that still write stuff in ASM because space... Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourc

Re: [Freedos-devel] Proposal: Remove MINIBOX (vaguely remember strcmp(argv[2]) where 2 did not exist.

2025-02-18 Thread tom ehlert via Freedos-devel
Hallo Herr Paul Dufresne via Freedos-devel, PLONK Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Proposal: remove FDTUI

2025-02-17 Thread tom ehlert via Freedos-devel
Hallo Herr Jerome Shidel via Freedos-devel, am Montag, 17. Februar 2025 um 09:02 schrieben Sie: >> On Feb 16, 2025, at 5:43 PM, tom ehlert via Freedos-devel >> wrote: >> >> Hallo Herr Jim Hall via Freedos-devel, >> >> am Sonntag, 16. Februar 2025

Re: [Freedos-devel] Proposal: remove FDTUI

2025-02-16 Thread tom ehlert via Freedos-devel
ram doesn't really do > anything and is buggy. See below for details. > I think we need to drop FDTUI, and not include it in FreeDOS 1.4. +1 Which rises the question why it was ever included. IMO FreeDOS included programs should have both a minimum usefulness and cod

Re: [Freedos-devel] Proposal: remove FDTUI

2025-02-16 Thread tom ehlert via Freedos-devel
While we are at it: Any reason for the inclusion of MINIBOX? Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] ZEROFILL R2.01 Released (was ZEROFILL R2.00 Releas ed)

2025-02-09 Thread tom ehlert via Freedos-devel
Hallo Herr Fritz Mueller via Freedos-devel, am Sonntag, 9. Februar 2025 um 19:06 schrieben Sie: > Hi Tom, > I am not happy that I have to do this now, but I think it is time "to wash > your head". Cholerical attacks are not nice for you and others, but as I had > severa

Re: [Freedos-devel] ZEROFILL R2.01 Released (was ZEROFILL R2.00 Releas ed)

2025-02-09 Thread tom ehlert via Freedos-devel
ilities. > So ZEROFILL is a milestone in supporting big HDs by FreeDOS. CONGRATULATIONS, > Nikkho! Please spare us this marketing BLA. Fixing bugs is nice, but doesn't make the 'milestones'. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Search all text file contents in directories recursively

2025-02-07 Thread tom ehlert via Freedos-devel
, and probably regexp port by now. Instead you write emails. Have fun! Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Search all text file contents in directories recursively

2025-02-07 Thread tom ehlert via Freedos-devel
ext files within a > given directory. You asked for an opportunity to contribute. Here is your first opportunity to be useful: teach FIND to search recursively; and while you are at it, teach it "expressions". Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Installing FreeDOS over other OS

2025-02-07 Thread tom ehlert via Freedos-devel
Hallo Herr Eric Auer via Freedos-devel, am Freitag, 7. Februar 2025 um 14:54 schrieben Sie: > However, there > are people working on the ability to boot DOS from FAT partitions > (FAT16 or FAT32) on GPT-partitioned disks. This is completely new to me. Any links to sh

Re: [Freedos-devel] Search all text file contents in directories recursively

2025-02-07 Thread tom ehlert via Freedos-devel
> Looking for a DOS-centric way of doing that. The DOS-centric way is not doing that at all. > As last resort I know I > can always install DJGPP's find and grep. exactly. Tom ___ Freedos-devel mailing list Freedos-devel@lists.s

Re: [Freedos-devel] Building entire FreeDOS release from source within FreeDOS

2025-02-06 Thread tom ehlert via Freedos-devel
the possibility to modify existing programs at *any* price. Even today, compilers may be free, but the computers to run these compilers (and the resulting programs) aren't free at all. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Building entire FreeDOS release from source within FreeDOS

2025-02-06 Thread tom ehlert via Freedos-devel
Are there efforts in this regard? Does the FreeDOS project deem this as > important? Definitively NO. There is more important (and interesting) stuff to be done. FreeDOS is about open source, not about self-hosted. Please read the manifesto. Tom ___

Re: [Freedos-devel] FreeDOS 1.4-RC2

2025-02-02 Thread tom ehlert via Freedos-devel
erent this time Please note that "out of memory" doesn't mean "out of memory". "out of memory" is just the catchall message from freecom if none of some specific error messages apply. Tom ___ Freedos-devel maili

Re: [Freedos-devel] Neat Eh? [Was:  is networking working just a little bit in 1.4 RC1? (Wiki help me!)]

2025-01-31 Thread tom ehlert via Freedos-devel
logging to XMS. > After all, RLE is very quick and would reduce the amount of data that would > need sent to XMS. the time needed to copy to XMS is a constant time to switch forth and back to PM, plus the cost of memcpy. should be fast enough in any reasonable setup. Tom (1) ~12 pentium-cloc

Re: [Freedos-devel] New freeware DOS memory manager: EMS Magic

2025-01-27 Thread tom ehlert via Freedos-devel
4 still has real mode and V86 mode. However both are not available with a 64Bit host OS. AFAIK 286 protect mode too is available from x86-64, too. However there are so few 286 protected mode programs in the wild, that they are rather irrelevant. They all died with OS/2. I

Re: [Freedos-devel] New freeware DOS memory manager: EMS Magic

2025-01-22 Thread tom ehlert via Freedos-devel
ld use supported EMS anyway. > Just my two cents. USD cents? EURO cents? or just Guyana cents? Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] New freeware DOS memory manager: EMS Magic

2025-01-20 Thread tom ehlert via Freedos-devel
y opinion EMS lost relevance when the 386 was introduced. That's a LONG time ago. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Some more software updates for FDT2402 (or later):

2025-01-18 Thread tom ehlert via Freedos-devel
tends to be the sole creator of programs that *create* RAR files. This is his good right, and not "stupid". RAR was created as shareware, back in the good old times. And I hope he made (and makes) a living by his software. You may not u

Re: [Freedos-devel] Ré : Aw:  is networking working just a little bit in 1.4 RC1? (Wiki help me!)

2025-01-17 Thread tom ehlert via Freedos-devel
No Error C:\>>ping tunes.org > Resolving `tunes.org'...No Error C:\>>ping asklfjklf.jk > Resolving `asklfjklf.jk'...No Error whatever is going on here, this seems to be a bad test for internet availability. Tom ___ Freedos-devel

Re: [Freedos-devel] New mTCP version available

2025-01-16 Thread tom ehlert via Freedos-devel
hould look like C:\NET\MTCP>services time The time is 2025-01-16 14:59:41.036935977 + UTC C:\> feel free to add a services /? to echo a copyright notice; the way you did it is simply annoying. Tom _

Re: [Freedos-devel] Neat Eh? [Was:  is networking working just a little bit in 1.4 RC1? (Wiki help me!)]

2025-01-16 Thread tom ehlert via Freedos-devel
tio as color rarely changes. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Some more software updates for FDT2402 (or later):

2025-01-13 Thread tom ehlert via Freedos-devel
el string. > Are there any recommendations which is better? Which labels are > shown and updated by label-related MS DOS commands, for example? it should show the same as DIR (in command) or LABEL, preferably the same as in MSDOS or Windows. Whatever they use. Tom __

Re: [Freedos-devel] FreeCOM 0.68 [Was: replace bmp2png with dosview]

2025-01-04 Thread tom ehlert via Freedos-devel
s) is unfortunately an entirely different matter, and *much* more complicated then this innocent "for Workgroups" suggests. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS 1.4-RC1 - some minor things

2025-01-04 Thread tom ehlert via Freedos-devel
> b) fdtui is a tumbler. I think it is really enough to download it via fnpkg. +1 Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Interim Releases: switching to current Kernel and FreeCOM?

2024-12-21 Thread tom ehlert via Freedos-devel
hould be able to do this. For freecom it's even easier. Just start the new freecom from the old freecom. And now you are 100% executing in new freecom domain. say EXIT and you are using the old freecom again. Tom ___ Freedos-dev

  1   2   3   4   5   6   7   8   >