Re: [Freedos-devel] freecom beep / stuck freedos core components
Hi Tom, >> * https://github.com/PerditionC/fdkernel > > AFAIK the official website www.freedos.org has a label [SOURCES]. > this points to https://sourceforge.net/p/freedos/svn/HEAD/tree/ > the last changes there are from (FreeCOM) 2018 and (kernel) 2016. > > how on earth should a non-insider like me discover hidden source code on > github? Exactly my problem, when I was posting about the buggy COUNTRY.SYS entries for Germany. Which, btw, is still not committed to any source code repository. See my reminder mail from 19.03.2020 to freedos-kernel. My fix is already from January. Cheers, Robert -- +++ BTTR Software +++ Home page: https://www.bttr-software.de/ DOS ain't dead: https://www.bttr-software.de/forum/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] freecom beep / stuck freedos core components
On Fri, May 15, 2020 at 8:43 AM tom ehlert wrote: > >> in https://sourceforge.net/p/freedos/svn/HEAD/tree/kernel/ there are > >> no recent changes. could the 'leader' please specify where official > >> sources are, who is official maintainer, aso. > > > AFAIK, the maintainer is Jeremy Davis, and he last updated it on his > > Github 13 days ago: > > > * https://github.com/PerditionC/fdkernel > > AFAIK the official website www.freedos.org has a label [SOURCES]. > this points to https://sourceforge.net/p/freedos/svn/HEAD/tree/ > the last changes there are from (FreeCOM) 2018 and (kernel) 2016. > > how on earth should a non-insider like me discover hidden source code on > github? > Actually, I didn't know about it either. That's why the link on the website points to the SourceForge SVN tree. Jim ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] freecom beep / stuck freedos core components
>> in https://sourceforge.net/p/freedos/svn/HEAD/tree/kernel/ there are >> no recent changes. could the 'leader' please specify where official >> sources are, who is official maintainer, aso. > AFAIK, the maintainer is Jeremy Davis, and he last updated it on his > Github 13 days ago: > * https://github.com/PerditionC/fdkernel AFAIK the official website www.freedos.org has a label [SOURCES]. this points to https://sourceforge.net/p/freedos/svn/HEAD/tree/ the last changes there are from (FreeCOM) 2018 and (kernel) 2016. how on earth should a non-insider like me discover hidden source code on github? >> writing and running a couple of .BAT files would be cool. > To do what or test what? I've written dozens of .BATs over the years > of varying quality. I'm not holding back any amazing scripts. Most of > my stuff is public, but it's a bit disorganized. MetaDOS had a bunch > (albeit spaghetti code) that was partially used as test, IIRC. But I > haven't had time to go back to that to try to kick the tires some > more. as the bug (stackoverflow) was detected by running your MetaDOS batches, it would be helpful to see if now all bugs are fixed. in addition a couple of 'test LFN' batches might be written also to avoid recurrence of old bugs. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] freecom beep / stuck freedos core components
Hi, On Wed, May 13, 2020 at 5:04 PM tom ehlert wrote: > > > Please shed some light on the well known reasons. > see Bart's 29 dez 2019 mail in freedos-devel Sorry, I'm preoccupied, so I haven't been doing as much contributing to FreeDOS as I'd like. So I haven't tested the latest pre-release (though I'm a good candidate to try it, it's very useful to me, at least non-professionally). > in https://sourceforge.net/p/freedos/svn/HEAD/tree/kernel/ there are > no recent changes. could the 'leader' please specify where official > sources are, who is official maintainer, aso. AFAIK, the maintainer is Jeremy Davis, and he last updated it on his Github 13 days ago: * https://github.com/PerditionC/fdkernel But I don't know his plans, don't have frequent contact with him, and only vaguely remember an email from a year ago from Juan Manuel Guerrero (DJGPP dev) about improvements in trunk (that I never investigated). That would be worth checking, but I haven't had the time nor energy. > > Is kernel development officially dead? How about freecom? > not officially. just as a matter of fact. It can always be restarted if anyone is interested in doing the work, of course. For most people, either it's good enough, too complicated to fix, or not important enough. (Or maybe "real life" worries take precedence.) Let's not sweat it too much. It's not the end of the world. > writing and running a couple of .BAT files would be cool. To do what or test what? I've written dozens of .BATs over the years of varying quality. I'm not holding back any amazing scripts. Most of my stuff is public, but it's a bit disorganized. MetaDOS had a bunch (albeit spaghetti code) that was partially used as test, IIRC. But I haven't had time to go back to that to try to kick the tires some more. I'm definitely in favor of improving FreeCOM and making sure it works on "Free" compilers. But I've also never rebuilt it (correctly), and it's a scary behemoth. Then again, I've had a bit more experience since then, so maybe I should try again. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] freecom beep / stuck freedos core components
2). 2017-Jun-9: "#189 Beep function freezes on recently intel platform (skylake/kabylake)" * https://sourceforge.net/p/freedos/bugs/189/ >> Bart added this function as it seems to be missing from ia16_gcc > Okay so it is only fixed when you cross-compile from Linux? it's related to gcc_ia16, not to crosscompile >> because nobody uses any FreeCOM binary younger then 2006 >> for well known reasons. > Please shed some light on the well known reasons. see Bart's 29 dez 2019 mail in freedos-devel >> although this has been fixed 'recently', still nobody uses or even >> tests the new (beta?) binary. > It also disappoints me that there have been ZERO replies on > freedos-kernel and freedos-devel to my alert that the kernel > development (if any?) happens without public discussions which > has led to dosemu2 using a very distant fork which can be used > as Linux library, mostly dropping backport efforts by now :-( in https://sourceforge.net/p/freedos/svn/HEAD/tree/kernel/ there are no recent changes. could the 'leader' please specify where official sources are, who is official maintainer, aso. > Or in related news: dosemu2 now uses a special SHARE tuned for > compatibility but no longer running on classic DOS kernels... I have never seen an reason to run SHARE except a FreeDOS machine as a server which is more or less impossible. or not? > Is kernel development officially dead? How about freecom? not officially. just as a matter of fact. > I still hope there are one or two developers tinkering away > on their versions behind the scenes, but without discussion, > how can we know? And who would even know what to test when? again: Bart's 29 dez 2019 mail in freedos-devel gives you a new FreeCOM; hopefully a) bugfree for normal operatons and also b) LFN aware. happy testing; in particular b) as I'm fairly certain that the actual coder of LFN support was more interested in implementing (cool) then testing/verifying (boring) things. writing and running a couple of .BAT files would be cool. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] freecom beep / stuck freedos core components
On Wednesday, May 13, 2020 3:33 PM, Eric Auer e.a...@jpberlin.de wrote: > ... > >> because nobody uses any FreeCOM binary younger then 2006 >> for well known reasons. > > Please shed some light on the well known reasons. +1 I never heard of any reasons. Granted I don't use FreeDOS on the daily, but I use 0.84 pre 7 on my VirtualBox VM with no issues in my basic use of it. > ...___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] freecom beep / stuck freedos core components
Hi Tom, >>> 2). 2017-Jun-9: "#189 Beep function freezes on recently intel platform >>> (skylake/kabylake)" >>> * https://sourceforge.net/p/freedos/bugs/189/ > Bart added this function as it seems to be missing from ia16_gcc Okay so it is only fixed when you cross-compile from Linux? > because nobody uses any FreeCOM binary younger then 2006 > for well known reasons. Please shed some light on the well known reasons. > although this has been fixed 'recently', still nobody uses or even > tests the new (beta?) binary. It also disappoints me that there have been ZERO replies on freedos-kernel and freedos-devel to my alert that the kernel development (if any?) happens without public discussions which has led to dosemu2 using a very distant fork which can be used as Linux library, mostly dropping backport efforts by now :-( Or in related news: dosemu2 now uses a special SHARE tuned for compatibility but no longer running on classic DOS kernels... Is kernel development officially dead? How about freecom? I still hope there are one or two developers tinkering away on their versions behind the scenes, but without discussion, how can we know? And who would even know what to test when? Regards, Eric ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
