Re: [Freedos-devel] FreeDOS Interim Build T2508

Hi guys, the 0.42-WIP version of DOSLFN provided by Jason Hood will hopefully resolve the filesystem corruption bug that was discussed earlier on the mailing list. How does it do that? I had assumed that there was a kernel problem, but it also is plausible that DOSLFN manipulates directors clu

Re: [Freedos-devel] FreeDOS Interim Build T2508

l via Freedos-devel" To: "FreeDOS Developers" Cc: jer...@shidel.net Subject: Re: [Freedos-devel] FreeDOS Interim Build T2508     On Aug 1, 2025, at 8:26 AM, Fritz Mueller via Freedos-devel <freedos-devel@lists.sourceforge.net> wrote:   Hi, just one question, as I do not

Re: [Freedos-devel] FreeDOS Interim Build T2508

Hi, > Am 01.08.2025 um 11:54 schrieb Eric Auer via Freedos-devel > : > > How does it do that? I had assumed that there was a kernel problem, > but it also is plausible that DOSLFN manipulates directors cluster > and sector data directly, because the kernel would not do LFN itself, > so the corru

Re: [Freedos-devel] FreeDOS Interim Build T2508

> On Aug 1, 2025, at 5:54 AM, Eric Auer via Freedos-devel > wrote: > > > Hi Jerome, > >> the 0.42-WIP version of DOSLFN provided by Jason Hood will hopefully resolve >> the filesystem corruption bug that was discussed earlier on the mailing list. > > How does it do that? I had assumed that

Re: [Freedos-devel] FreeDOS Interim Build T2508

> On Aug 1, 2025, at 8:26 AM, Fritz Mueller via Freedos-devel > wrote: > > Hi, > just one question, as I do not understand it: The monthly versions are builds > to test new software. Is this correct? So, why not modifying fdnpkg.cfg to > get the latest versions automatical (too) to enable te

Re: [Freedos-devel] FreeDOS Interim Build T2508

Hi, just one question, as I do not understand it: The monthly versions are builds to test new software. Is this correct? So, why not modifying fdnpkg.cfg to get the latest versions automatical (too) to enable tests? I just got some RSS feeds that there are new programs available - and I have to mo

Re: [Freedos-devel] FreeDOS Interim Build T2508

Hi Jerome, the 0.42-WIP version of DOSLFN provided by Jason Hood will hopefully resolve the filesystem corruption bug that was discussed earlier on the mailing list. How does it do that? I had assumed that there was a kernel problem, but it also is plausible that DOSLFN manipulates directors

Re: [Freedos-devel] FreeDOS hidden partition types

Hi Bernd, Thanks for the links and the context. They look like they were a bad idea that was quickly reverted. Mike On Mon, Jul 7, 2025 at 1:33 AM Bernd Böckmann wrote: > Hi Mike, > > seems this kind of partition type got introduced by FDISK version 0.96 [1] > in 1999. However, these were a

Re: [Freedos-devel] FreeDOS hidden partition types

Hi Mike, seems this kind of partition type got introduced by FDISK version 0.96 [1] in 1999. However, these were already removed by 1.0 RC2 [2], which got released in 2001. The exact reason is unclear to me. Maybe someone involved in the project at that time knows why the types were initially i

Re: [Freedos-devel] FreeDOS repository mirror

> On Jul 6, 2025, at 2:18 PM, Andrew Bird via Freedos-devel > wrote: > > Hi all, > Can you tell me if there are any official mirrors to the package > repositories? I currently use some of the packages from there in a CI test > and I'm finding that the primary site is timing out. > > https:

Re: [Freedos-devel] FreeDOS Interim Build T2507

On Wed, Jul 2, 2025, 7:25 PM Eric Auer via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > > [..] > Does this i16 toolchain still depend on DJGPP, which we do not include? > Or am I confusing that i16 stuff with something else? > You are misremembering. The ia16 GCC compiler tool c

Re: [Freedos-devel] FreeDOS Interim Build T2507

Hi Jerome, I’ve been extremely busy over the last few days. So, I did not get to this until this morning. The FreeDOS Interim Test Build T2507 for July is now available for download at: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ Thank you :-) Changes sin

Re: [Freedos-devel] FreeDOS Repos

> On Jun 23, 2025, at 5:33 PM, Eric Auer via Freedos-devel > wrote: > >  > Hi! > > Quick question... > > Does the online FDRepo v3 data also support existing > installations which expect older data online, or will > everybody who has installed FreeDOS in the recent past > have to reinstall

Re: [Freedos-devel] FreeDOS Repos

Hi! Quick question... Does the online FDRepo v3 data also support existing installations which expect older data online, or will everybody who has installed FreeDOS in the recent past have to reinstall and/or update repo handling tools? Regards, Eric PS: I also think we should keep offering

Re: [Freedos-devel] FreeDOS Repos

Hi! I think it is probable best to use values "Ä” instead of "Ä” for the “Ä” character. It is likely to be supported better than using name on some browsers. I disagree. Auml tells the browser what you want, kind of. Using numbers would just rely on the font to be complete. If I would write

Re: [Freedos-devel] FreeDOS Repos

> On Jun 23, 2025, at 8:15 AM, Fritz Mueller via Freedos-devel > wrote: > > Ah, I understand. The problem is close to what we have with htmlhelp. > > Have a look at: https://www.wolfgang-frank.eu/hc.php Thank you for this link. It is a great page and I like it better than the W3C version.

Re: [Freedos-devel] FreeDOS Repos

replacements work on the server.   Willi     Sent: Monday, June 23, 2025 at 1:13 PM From: "Jerome Shidel via Freedos-devel" To: "FreeDOS Developers" Cc: jer...@shidel.net Subject: Re: [Freedos-devel] FreeDOS Repos Hi Willi,   On Jun 23, 2025, at 6:31 AM, Fritz Muell

Re: [Freedos-devel] FreeDOS Repos

Hi Willi, > On Jun 23, 2025, at 6:31 AM, Fritz Mueller via Freedos-devel > wrote: > > Hi Jerome, > german uses only the special characters: äÄ, öÖ,üÜ and ß, these are even part > of CP 437. > So I think adding german should work. > You can find the characters äöü at > https://fd.lod.bz/reposi

Re: [Freedos-devel] FreeDOS Repos

Hi Jerome, german uses only the special characters: äÄ, öÖ,üÜ and ß, these are even part of CP 437. So I think adding german should work. You can find the characters äöü at https://fd.lod.bz/repository/latest/html/de/index.html.   I am sure ÄÖÜ will work too.   So it is enough to simply copy

Re: [Freedos-devel] FreeDOS Interim Build T2506

Hi! Thanks for the updates :-) So when not counting the revision and NLS items, I get: The FreeDOS Interim Test Build T2506 for June is now available for download at: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ Bigger Changes since T2505: 2025-05-30 09:5

Re: [Freedos-devel] FreeDOS EDIT fork

> Am 18.05.2025 um 15:37 schrieb Eric Auer via Freedos-devel > : > >> - fix edit not being able to save a file of zero size > > ... > >> The following still applies: > ... >> - EDIT always appends a NL character to the last line when >> editing it > > So how does one type an empty file at

Re: [Freedos-devel] FreeDOS EDIT fork

>> - fix IVT corruption on new document creation > > Sounds like a null pointer? Correct. >> - EDIT always appends a NL character to the last line when >> editing it > > So how does one type an empty file at the moment? :-) Creating a new document and then immediately save it. NL is appende

Re: [Freedos-devel] FreeDOS EDIT fork

Hi Bernd, thanks for all those EDIT updates! - fix IVT corruption on new document creation Sounds like a null pointer? - fix memory corruption on text paste caused by broken size check :-o - fix edit not being able to save a file of zero size ... The following still applies: ...

Re: [Freedos-devel] FreeDOS EDIT fork

Hi, I fixed a few more EDIT bugs and uploaded a new binary to my Nextcloud. Binary may be downloaded from: https://nextcloud.iww.rwth-aachen.de/index.php/s/MT9cpqeT7wpAnft The binary is built from the sources at: https://github.com/boeckmann/edit If no new bugs are found, I think this can be re

Re: [Freedos-devel] FreeDOS EDIT fork

On 5/1/2025 9:42 AM, Eric Auer via Freedos-devel wrote: I don't need to know what time it is, I have a bunch of other clocks for that. :-) Let's also remove the calendar. Saves ~0x500 bytes :) Disagree again. And please keep the ASCII character table, too. A bit "late to the party", but

Re: [Freedos-devel] FreeDOS EDIT fork

> Am 08.05.2025 um 07:29 schrieb Jerome Shidel via Freedos-devel > : > > Should this be an “unstable” update to FreeDOS Edit and on the next Interim > Build? Not this specific executable. I am still working on it. I will provide an executable for inclusion in the next interim build later thi

Re: [Freedos-devel] FreeDOS EDIT fork

> On May 7, 2025, at 3:58 PM, Bernd Böckmann via Freedos-devel > wrote: > > You may download it from [1]. It is 449k as it contains debug info... > > [1]: https://nextcloud.iww.rwth-aachen.de/index.php/s/jdggYg2igeDSMQF > > Bernd Should this be an “unstable” update to FreeDOS Edit and on th

Re: [Freedos-devel] FreeDOS EDIT fork

You may download it from [1]. It is 449k as it contains debug info... [1]: https://nextcloud.iww.rwth-aachen.de/index.php/s/jdggYg2igeDSMQF Bernd > Am 07.05.2025 um 21:52 schrieb Wilhelm Spiegl : > > Hi Bernd, > > could you publish a test version with the actual status? > > Thx > > Willi >

Re: [Freedos-devel] FreeDOS EDIT fork

I have made some changes to the FreeDOS EDIT source. EDIT 0.9a contains quite many bugs, which I find astonishing considering it is the default editor since a few decades. Things I have done so far: - fix IVT memory corruption resulting from a null ptr write when creating a new document - fix

Re: [Freedos-devel] FreeDOS Interim Build T2505

The bug in FDVCS has been fixed. I built a fresh version of T2505 and it installed without issue. I have replaced the broken Interim Build on the server with the fixed version. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https

Re: [Freedos-devel] FreeDOS Interim Build T2505

> On May 1, 2025, at 2:49 PM, Jim Hall via Freedos-devel > wrote: > > I always forget the acronyms. I think RBE is the Release Build Environment. > > I don't remember what FDVCS stands for. Which one is that? “FreeDOS” Version Control System (utility) Its primary function is automatic pres

Re: [Freedos-devel] FreeDOS Interim Build T2505

I always forget the acronyms. I think RBE is the Release Build Environment. I don't remember what FDVCS stands for. Which one is that? On Thu, May 1, 2025, 1:41 PM Jerome Shidel via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > I have looked into the issue. > > There is a bug in

Re: [Freedos-devel] FreeDOS Interim Build T2505

I have looked into the issue. There is a bug in new FDVCS when applying NLS updates to packages. RBE3 automatically performs that update using FDVCS after fetching the packages from GitLab. The possibility of obscure bugs in the new FDVCS is the reason I did not want to start using it until

Re: [Freedos-devel] FreeDOS EDIT fork

> Am 01.05.2025 um 19:12 schrieb Eric Auer via Freedos-devel > : > > Joe's versions are not strictly LATER at some point, > there were quite a few improvement ideas for Joe's > version 0.6, so I forked 0.6a 0.6b 0.6c 0.6d 0.6e and > 0.7a 0.7b 0.7c and 0.7d and you can find all 0.7x on: > > ht

Re: [Freedos-devel] FreeDOS EDIT fork

Hi! It bothers me a bit to use mail like chat but... To be honest, I have not studied the differences between the 0.6, 0.7 and later versions in detail. I took the current version and started fixing things that bothered me :) If you think that we should rollback changes introduced by later ve

Re: [Freedos-devel] FreeDOS EDIT fork

> Am 01.05.2025 um 18:38 schrieb Eric Auer via Freedos-devel > : > > I disagree here. While updating it too often could have > side effects, having a clock at all is quite nice :-) As a compromise, what about only displaying HH:MM (without seconds)?

Re: [Freedos-devel] FreeDOS EDIT fork

> Am 01.05.2025 um 18:58 schrieb Wilhelm Spiegl : > > Btw, @ tom, msedit is not from MS but from Mateusz Viste, but it is not > complete. Sadly it is "abandoned" since several years. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.

Re: [Freedos-devel] FreeDOS EDIT fork

> > thanks for maintaining EDIT! I hope you were able to find > some nice things in the EDIT 0.6x and 0.7x series to use? > > The 0.8x series by Joe Cosentino also implements many > ideas from my old 0.6x and 0.7x forks, but not all: > >> The 0.6?/0.7? versions should be more compatible to count

Re: [Freedos-devel] FreeDOS EDIT fork

I don't need to know what time it is, I have a bunch of other clocks for that. :-) Let's also remove the calendar. Saves ~0x500 bytes :) Disagree again. And please keep the ASCII character table, too. ___ Freedos-devel mailing list Freedos-

Re: [Freedos-devel] FreeDOS EDIT fork

Jim wrote: [..] > > I don't need to know what time it is, I > > have a bunch of other clocks for that. :-) Bernd wrote: > Let's also remove the calendar. Saves ~0x500 bytes :) Sounds good to me, I don't use that either. :-) ___ Freedos-devel mailing l

Re: [Freedos-devel] FreeDOS EDIT fork

> Am 01.05.2025 um 18:34 schrieb Jim Hall via Freedos-devel > : > > I don't need to know what time it is, I > have a bunch of other clocks for that. :-) Let's also remove the calendar. Saves ~0x500 bytes :) ___ Freedos-devel mailing list Freedos-de

Re: [Freedos-devel] FreeDOS EDIT fork

Hi! I know you said you're not planning to fix other things, but maybe you could remove the clock? It's the one thing that still annoys me about EDIT (and other editors) -- I don't need to know what time it is, I have a bunch of other clocks for that. :-) I disagree here. While updating it t

Re: [Freedos-devel] FreeDOS EDIT fork

Excellent, thanks! I have a minor edit to config.h and menus.c to change the version number to 0.9b, and to add your name next to Joe and Eric in the "About Edit" window. I'll send those files to you in a zip file off-list. I know you said you're not planning to fix other things, but maybe you co

Re: [Freedos-devel] FreeDOS EDIT fork

> Am 01.05.2025 um 18:08 schrieb roy...@gmail.com: > > Glad to hear this. I wonder if changing to openwatom producing smaller binary? Currently it's larger. But I have not started optimizing for size... ___ Freedos-devel mailing list Freedos-devel

Re: [Freedos-devel] FreeDOS EDIT fork

Hello, Bernd Böckmann via Freedos-devel wrote: > > Hi, > > I started maintaining a fork of FreeDOS EDIT [1]. The permanent flickering of > the mouse cursor drove me nuts, so I fixed it (mostly). Glad to hear this. I wonder if changing to openwatom producing smaller binary? > > I integrated the

Re: [Freedos-devel] FreeDOS EDIT fork

Hi Bernd, thanks for maintaining EDIT! I hope you were able to find some nice things in the EDIT 0.6x and 0.7x series to use? The 0.8x series by Joe Cosentino also implements many ideas from my old 0.6x and 0.7x forks, but not all: The 0.6?/0.7? versions should be more compatible to country-

Re: [Freedos-devel] FreeDOS Interim Build T2505

I should add for anyone who's new and not familiar with FreeDOS: the CDROM.BAT (in \freedos\bin) attempts multiple drivers to support the CD-ROM drive, and it uses VECHO to print messages and VDELAY to make brief pauses. Here's how to "hard-code" the CD-ROM driver manually without it: 1. CD \freed

Re: [Freedos-devel] FreeDOS Interim Build T2505

Thanks! FYI that I get an error ("Unable to install the 'tools\v8power' package) when installing T2505. My only options during the regular install are reboot or return to DOS. (I'll send you a few screenshots off-list.) I also tried SETUP ADV and was able to ignore the error (skip it) and I also g

Re: [Freedos-devel] FreeDOS Interim Build T2505

On Thu, May 1, 2025 at 7:27 AM Eric Auer via Freedos-devel wrote: > While it is nice to get NLS and installer updates, the > really cool stuff seems to be what you said at the end: > > > A few packages had updates to their unstable branch after T2503 (RC3). > > These will > > not show up in this

Re: [Freedos-devel] FreeDOS Interim Build T2505

Hi Jim, let me inline and summarize that ;-) These updates are usually shared here on freedos-devel by the developers. Others are also posted as news items on the www.freedos.org website. I didn't look them all up, but here are the links to the SF-hosted feeds for several of these: * fdisk

Re: [Freedos-devel] FreeDOS Interim Build T2505

Hi! While it is nice to get NLS and installer updates, the really cool stuff seems to be what you said at the end: A few packages had updates to their unstable branch after T2503 (RC3). These will not show up in this changes summary because they happened before FreeDOS 1.4 was released. So,

Re: [Freedos-devel] FreeDOS 1.4 known issues

seems your day was not the best...😇 what about msedit? Willi > Sent: Monday, April 28, 2025 at 8:23 PM > From: "tom ehlert via Freedos-devel" > To: "Technical discussion and questions for FreeDOS developers." > > Cc: "tom ehlert" > Subje

Re: [Freedos-devel] FreeDOS 1.4 known issues

Hallo Herr Wilhelm Spiegl, > c) edit: there are so many bugs reported at gitlab (one a small part of it > see:) >... > that it would make sense to create a new editor. But anyhow it works. And that from a guy who has not the faintest idea how much time it takes "to create a new editor". Unpai

Re: [Freedos-devel] FreeDOS 1.4 known issues

FD1.4, but can be downloaded via fdnpkg) without a given file reports:    command or filename not found. - "dmidecode". Sent: Sunday, April 27, 2025 at 1:41 AM From: "Jim Hall via Freedos-devel" To: "Technical discussion and questions for FreeDOS developers." Cc: &

Re: [Freedos-devel] FreeDOS 1.4 known issues

On Sat, Apr 26, 2025 at 4:08 PM Jerome Shidel via Freedos-devel wrote: [..] > Just my thoughts on such a list. > > I think this might be something to create in the Documentation project on the > in the FreeDOS Archive on GitLab. > > https://gitlab.com/FreeDOS/docs > > Maybe a “known_issues” subdi

Re: [Freedos-devel] FreeDOS 1.4 known issues

> Am 26.04.2025 um 23:07 schrieb Jerome Shidel via Freedos-devel > : > > I think this might be something to create in the Documentation project on the > in the FreeDOS Archive on GitLab. > > https://gitlab.com/FreeDOS/docs > > Maybe a “known_issues” subdirectory, with files for current and f

Re: [Freedos-devel] FreeDOS 1.4 known issues

Hi, > On Apr 26, 2025, at 4:18 PM, Bernd Böckmann via Freedos-devel > wrote: > > Hi, > > may we provide a list of known issues for FreeDOS 1.4 on the website? If you > think that this is a good idea, I can contribute the first bullet point: > > - FDISK shows partition type id 0x0e as "FAT-32

Re: [Freedos-devel] FreeDOS 1.4 News

On 10/04/2025 12:45, Jerome Shidel via Freedos-devel wrote: Hi All, Like many of you, I’ve been checking out various news articles that are popping up around the web covering the release of 1.4. While many are just re-posts of content written by others, there are a number of original articles

Re: [Freedos-devel] FreeDOS 1.4 News

> On Apr 10, 2025, at 5:44 PM, tom ehlert via Freedos-devel > wrote: > > Hallo Herr Jerome Shidel via Freedos-devel, > > am Donnerstag, 10. April 2025 um 13:45 schrieben Sie: > >> Hi All, > >> Like many of you, I’ve been checking out various news articles that are >> popping up around the

Re: [Freedos-devel] FreeDOS 1.4 News

Hallo Herr Jerome Shidel via Freedos-devel, am Donnerstag, 10. April 2025 um 13:45 schrieben Sie: > Hi All, > Like many of you, I’ve been checking out various news articles that are > popping up around the web covering the release of 1.4. > While many are just re-posts of content written by ot

Re: [Freedos-devel] FreeDOS 1.4 coming out today!

On Mon, Apr 7, 2025 at 2:09 PM Jim Hall wrote: > > I'm writing a bunch of articles today about FreeDOS 1.4. I'll start > with a special announcement page that I can put on www.freedos.org > that details what's new in FreeDOS 1.4. That will be up in a few > hours, but more likely sooner than that.

Re: [Freedos-devel] FreeDOS 1.4 coming out today!

On 07/04/2025 23:59, Jim Hall via Freedos-devel wrote: Here's an announcement you can link to: https://freedos.org/download/announce.html Nice one -- thanks! -- Liam Proven ~ Profile: https://about.me/liamproven Email: lpro...@cix.co.uk

Re: [Freedos-devel] FreeDOS 1.4 coming out today!

On 07/04/2025 18:50, Jerome Shidel via Freedos-devel wrote: The primary installer used on the CD-ROMs and USB images requires a 386 or better processor. It was originally the only installer for FreeDOS 1.2. It is simply called FDI (for the FreeDOS Installer). There was no floppy disk version

Re: [Freedos-devel] FreeDOS 1.4 coming out today!

> On Apr 7, 2025, at 12:52 PM, Liam Proven via Freedos-devel > wrote: > > On Sun, 6 Apr 2025 at 01:44, Jim Hall via Freedos-devel > wrote: >> >> FreeDOS 1.4 is live! > > Great! Congrats! > > [...] > >> Please reply here to >> let me know what else I should emphasize for FreeDOS 1.4. > >

Re: [Freedos-devel] FreeDOS 1.4 coming out today!

I'm writing a bunch of articles today about FreeDOS 1.4. I'll start with a special announcement page that I can put on www.freedos.org that details what's new in FreeDOS 1.4. That will be up in a few hours, but more likely sooner than that. I'll share a link here when it's up. On Mon, Apr 7, 202

Re: [Freedos-devel] FreeDOS 1.4 coming out today!

On Sun, 6 Apr 2025 at 01:44, Jim Hall via Freedos-devel wrote: > > FreeDOS 1.4 is live! Great! Congrats! [...] > Please reply here to > let me know what else I should emphasize for FreeDOS 1.4. I am writing a news story on it. It's hard to link to the announcement on https://www.freedos.org/

Re: [Freedos-devel] FreeDOS 1.4 coming out today!

FreeDOS 1.4 is live! I've copied the FreeDOS 1.4 "GM" release to the official FreeDOS 1.4 distribution location: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.4/ I've also updated the website so it links to FreeDOS 1.4, and updated the "about FreeDOS 1.4" text on the do

Re: [Freedos-devel] FreeDOS 1.4 coming out today!

[..] > > I'll do this later today. I'm responding to other work items at the > > moment, but I can do it later this afternoon or early evening. > > > > Yay! :-) > > +1 > > Unless you want me to move it. > Then, you will just need to announce it. :-) I figure if I move it, I can coordinate that wit

Re: [Freedos-devel] FreeDOS 1.4 coming out today!

> On Apr 5, 2025, at 12:34 PM, Jim Hall via Freedos-devel > wrote: > > Sounds like this [from the "FreeDOS 1.4-GM Re-issue" email on > freedos-devel] was the only critical issue in the FreeDOS 1.4 "GM" .. > and it's been resolved. So I plan to "promote" the FreeDOS 1.4 "GM" > that's currently

Re: [Freedos-devel] FreeDOS 1.4-GM

Hi Jim, as the error messages are about exception 07, device not available, all refer to basically the same code address and one of them shows the machine code to be DB E3 which stands for FNINIT, this does indeed look very much like an app which blindly assumes some FPU (floating point unit) to b

Re: [Freedos-devel] FreeDOS 1.4-GM

Tested the floppy installer in 86Box with an 80286 machine, the "[ISA] MR BIOS 286 clone" board (because I like having a BIOS setup menu and a PC/AT doesn't have one) with a 1200KB 5.25" floppy drive and a 1024:16:63 (504 MB) IDE hard drive. The readme says an EGA is required, so I intentional

Re: [Freedos-devel] FreeDOS 1.4-GM

> On Apr 2, 2025, at 6:33 PM, Jim Hall via Freedos-devel > wrote: > > On Wed, Apr 2, 2025 at 4:59 PM Eric Auer via Freedos-devel > > wrote: >> >> Hi Jim, as the error messages are about exception 07, >> device not available, all refer to basically

Re: [Freedos-devel] FreeDOS 1.4-GM

On Wed, Apr 2, 2025 at 4:59 PM Eric Auer via Freedos-devel wrote: > > Hi Jim, as the error messages are about exception 07, > device not available, all refer to basically the same > code address and one of them shows the machine code > to be DB E3 which stands for FNINIT, this does indeed > look v

Re: [Freedos-devel] FreeDOS 1.4-GM

(programs are below) I did a few more tests and this is not a regression. OpenWatcom FORTRAN also doesn't work in FreeDOS 1.3 on the Pocket386. (Although OpenWatcom C does work with FreeDOS 1.3 on the Pocket386.) Config 1: Reinstalled with FreeDOS 1.3 -- base system, then installed Watcomf and Wa

Re: [Freedos-devel] FreeDOS 1.4-GM

Ben Russell said today: > because I like having a BIOS setup > menu and a PC/AT doesn't have one I did not use many PC/ATs, but all those I used had a BIOS setup menu. AFAIR, it was the XTs and earlier that did not have a setup menu, because they did not have non-volatile RAM. I don't k

Re: [Freedos-devel] FreeDOS 1.4-GM

> On Apr 2, 2025, at 3:46 AM, Ben Russell via Freedos-devel > wrote: > > Tested the floppy installer in 86Box with an 80286 machine, the "[ISA] MR > BIOS 286 clone" board (because I like having a BIOS setup menu and a PC/AT > doesn't have one) with a 1200KB 5.25" floppy drive and a 1024:16:6

Re: [Freedos-devel] FreeDOS 1.4-GM

Did a few more experiments: I think the problem is the OpenWatcom DOS4gw. I can't compile with either OpenWatcom C or OpenWatcom FORTRAN (but I can compile fine with Turbo C). I get a stack trace but it was late and I needed to go to bed so I didn't capture it. I also tried booting without fdconfig

Re: [Freedos-devel] FreeDOS 1.4-GM

It would be great for others to test this too. I'll also try it again and see if it was just a poorly timed hang—the battery died shortly afterwards, so could be something with that, but I doubt it. I am not too concerned about this one issue because: 1. It works on QEMU, and I'm sure works on ot

Re: [Freedos-devel] FreeDOS 1.4-GM

> My only issue is that the OpenWatcom FORTRAN 77 compiler isn't able to > compile programs on the Pocket386 laptop. But OpenWatcom F77 works > fine on QEMU, so this is something to do with the Pocket386's 386-SX > CPU, which doesn't have a math coprocessor. That could well be the problem, but it

Re: [Freedos-devel] FreeDOS 1.4-GM

I'll do some tests on that tomorrow if it is really tied to the absence of a co-proc. Considering that Fortran was originally meant to be a math heavy language it might just as well be. Cheers, Danilo On Tue, 1 Apr 2025 at 21:30, Jim Hall via Freedos-devel wrote: > > I've installed it on both my

Re: [Freedos-devel] FreeDOS 1.4-GM

I've installed it on both my QEMU instance and on my Pocket386 computer. So far, it's running well. My only issue is that the OpenWatcom FORTRAN 77 compiler isn't able to compile programs on the Pocket386 laptop. But OpenWatcom F77 works fine on QEMU, so this is something to do with the Pocket386'

Re: [Freedos-devel] [Freedos-user] Info on creating Freedos packages?

Hey, Okay I created a merge request. There wasn't actually a separate LSM page, but I included your description from your reply. https://gitlab.com/FreeDOS/docs/-/merge_requests/4 Please review and LMK if something needs a rewrite :) --Wolf -- |\_ | .\---. / ,__/ / /Wolf _ On Wed

Re: [Freedos-devel] FreeDOS 1.4

On Mon, 17 Mar 2025, Ralf Quint via Freedos-devel wrote: On 3/16/2025 3:36 PM, Jim Hall via Freedos-devel wrote: On Sun, Mar 16, 2025 at 4:29 PM Jerome Shidel via Freedos-devel wrote: [..] PS: I will call Jenny to let her know. Just send me her number. (You would have had to be present during

Re: [Freedos-devel] FreeDOS 1.4

On 3/16/2025 3:36 PM, Jim Hall via Freedos-devel wrote: On Sun, Mar 16, 2025 at 4:29 PM Jerome Shidel via Freedos-devel wrote: [..] PS: I will call Jenny to let her know. Just send me her number. (You would have had to be present during the meeting to understand this.) I can't remember how we

Re: [Freedos-devel] FreeDOS 1.4

Just to be very clear; I know we need FDNet. I was just kind of surprised when I looked at it. Given that it has a part of mTCP as a dependency I expected it to install mTCP, or at least only include the parts of mTCP that it needs. I didn't expect it to include the entire source code and develo

Re: [Freedos-devel] FreeDOS 1.4

Additional followup... > On Mar 17, 2025, at 8:05 AM, jer...@shidel.net wrote: > > [..] > > Since the two packages will contain the same version of DHCP. I will replace > the mTCP sources with a text file in the FDNET package. The README.TXT will > say: > > FDNET uses DHCP.EXE created by Mich

Re: [Freedos-devel] FreeDOS 1.4

> On Mar 16, 2025, at 8:29 PM, Michael Brutman via Freedos-devel > wrote: > > So this is kind of funny ... > > The FDNET is basically a glorified BAT file. But it uses other things, so > that creates complications: Of course it is a BATCH file and not a very complex one. I don’t think it i

Re: [Freedos-devel] FreeDOS 1.4

So this is kind of funny ... The FDNET is basically a glorified BAT file. But it uses other things, so that creates complications: - It is using exactly one program from mTCP. The DHCP client. As a result, you are shipping all of the mTCP source code including a 250KB PDF file for dev

Re: [Freedos-devel] FreeDOS 1.4

**I am bringing back a discussion from today's virtual get-together, about FreeDOS 1.4. It sounds like there are no blocking issues in FreeDOS 1.4 Release Candidate 3. (Yay!) So the next monthly test release will be "FreeDOS 1.4" (in other words, we will not have a "FreeDOS 1.4 Release Candidate 4

Re: [Freedos-devel] FreeDOS 1.4

On Sun, Mar 16, 2025 at 4:29 PM Jerome Shidel via Freedos-devel wrote: [..] > PS: I will call Jenny to let her know. Just send me her number. > (You would have had to be present during the meeting to understand this.) I can't remember how we got onto the topic, but I suppose it shouldn't have be

Re: [Freedos-devel] FreeDOS 1.4

> On Mar 16, 2025, at 3:16 PM, Jim Hall via Freedos-devel > wrote: > > **I am bringing back a discussion from today's virtual get-together, > about FreeDOS 1.4. > > It sounds like there are no blocking issues in FreeDOS 1.4 Release > Candidate 3. (Yay!) So the next monthly test release will

Re: [Freedos-devel] Freedos SOURCES

>> Is the task "FreeDOS is an open source operating system. Locate MOVE sources >> from freedos.org" >> included in Jims "usability testing" of the website? For those who found that easy here's the task for advanced users: "Locate COMMAND.COM sources starting from freedos.org" BTW: https://f

Re: [Freedos-devel] Freedos SOURCES

Hi Tom, > On Mar 2, 2025, at 3:35 AM, tom ehlert via Freedos-devel > wrote: > > Hi Jerome, > >>> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/move/ >>> is from 2006-08-31 13:53. Is that the most recent move? > >> For the binaries, yes. > > Is https://www.ibiblio.org/pub/micro

Re: [Freedos-devel] Freedos SOURCES

Dagnabbit, that's a brilliant piece of comedy. And there I was trying to make a living by actually programming stuff for thirty years. This guy certainly had a sense of humour that we Germans are undeservedly said to be lacking. I shall, from now on, include that disclaimer in all my stuff /* if

Re: [Freedos-devel] Freedos SOURCES

scandisk i dont know if it actually works fully. the gui work son 8088 and 286 systems! :D but the disk scanning may not bee implemented On Sun, 2025-03-02 at 10:04 +0100, tom ehlert via Freedos-devel wrote: > Hallo Herr tom ehlert via Freedos-devel, > > am Sonntag, 2. März 2025 um 09:46 sc

Re: [Freedos-devel] Freedos SOURCES

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'm not aware of other > chk

Re: [Freedos-devel] FreeDOS 1.4-RC3

Hallo Herr Bernd Böckmann via Freedos-devel, am Samstag, 1. März 2025 um 20:40 schrieben Sie: >> the bug is found, fixed, and was communicated on this list. >> >> That this is not implemented in the latest RC3 is a sad shame. > It is fixed for the FreeDOS package via [1]. >> I'm fairly certain y

Re: [Freedos-devel] Freedos SOURCES

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'm not aware of other chkdsk like programs for FAT32. Instead I stumbled over this gem of software https://www.ibiblio.org/pu

Re: [Freedos-devel] Freedos SOURCES

Hi Jerome, >> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/move/ >> is from 2006-08-31 13:53. Is that the most recent move? > For the binaries, yes. Is https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/ the "official" FreeDOS source, and everything else just copies?

Re: [Freedos-devel] FreeDOS 1.4-RC3

> I do not think the “out of memory” issue on VMware has had a resolution > provided. It does. The solution is to re-enable the exe-header modification of command.com. the bug is found, fixed, and was communicated on this list. That this is not implemented in the latest RC3 is a sad shame.

  1   2   3   4   5   6   7   8   9   10   >