te? I can
> update the old news item, or I can delete that one and add a new item.
>
>
> Jim
>
>
> On Sun, Sep 8, 2024 at 2:18 PM perditionc--- via Freedos-devel
> wrote:
> >
> > For further review and feedback - format 0.92a (this is a test release).
> >
>
For further review and feedback - format 0.92a (this is a test release).
https://github.com/FDOS/format/releases/tag/v0.92a
- fix failure formatting on first diskette access (GitHub issue #5)
- initial translated message support; currently supports most of
messages in FR and TR (some have been ad
This is something that should work. I will have to look into it and see
why it doesn't work. I have a few ideas, but am working this weekend so
may be a few days before I can look into it. I'm currently trying to track
down an unrelated stack trashing issue in some kernel changes related to
flo
Version 1.7 released
https://github.com/FDOS/xcopy/releases/tag/v1.7
- really fix timestamp bug (hopefully), delays updating timestamp
until after copy complete
- fix sourceforge bug# 178, allow switches specified without spaces between them
- fix /D: to work skip older files than date even if no f
On Wed, Aug 7, 2024 at 11:11 PM wrote:
>
> On Tue, Aug 6, 2024, 4:48 AM Ben Russell via Freedos-devel
> wrote:
>>
>> On 06/08/2024 04:55, Wilhelm Spiegl via Freedos-devel wrote:
>>
>> I just stumbled over this old bug report referring to xcopy:
>>
>> https://sourceforge.net/p/freedos/bugs/346/
>
>
> ...
> *We're all volunteers, if you see a new version of a program and no one is
> talking about it, share that news on the email list.
> ...
>
I published a new version of format to fix the couple bugs reported and
finally got around to merging a pull request adding 128KB cluster support.
ht
>
>
> tree: do not know the actual situation, I got a promise that someone will
> check whats the matter.
>
> xcopy version 1.4 or 1.5? See discussion at FD mailing list or bttr.
>
> ...
>
tree is on my todo list, I need to make sure latest version is in the
FreeDOS distribution. Github/FDO
On Tue, Aug 6, 2024, 4:48 AM Ben Russell via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:
> On 06/08/2024 04:55, Wilhelm Spiegl via Freedos-devel wrote:
>
> I just stumbled over this old bug report referring to xcopy:
>
> https://sourceforge.net/p/freedos/bugs/346/
>
> It is still a
On Mon, Jun 3, 2024, 6:26 PM Eric Auer via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:
>
> Hi Jim,
>
> from an engineering point of view, I would say LBA avoids
> problems related to mismatching CHS geometries on different
> computers, so I still prefer the MANUAL method where user
On Sun, Jun 2, 2024, 12:25 PM Jerome Shidel via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:
> Glad you got it working Jim.
>
> So, for fixing the issue…
>
> It would be possible to add an additional screen to the installer
> (probably only advanced mode) to use the /FORCE:CHS optio
On Sun, Jun 2, 2024, 8:05 AM Bernd Böckmann via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:
>
> > but then I realized that since it doesn't know about it, it doesn't
> actually get the full line. It does only see the first 127 characters,
> > which is why you can get odd errors eve
On Sat, Feb 17, 2024 at 9:09 AM Wilhelm Spiegl via Freedos-devel
wrote:
>
> Hi Jim,
> thanks for your response. Xcopy is not the only thing, maybe you remember
> tree 3.72 in this forum?
>
...
>
> tree: do not know the actual situation, I got a promise that someone will
> check whats the matter.
On Sun, Feb 4, 2024, 7:39 AM roytam--- via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:
> Hello,
>
> perditionc--- via Freedos-devel
> wrote:
> >
> > On Sun, Feb 4, 2024, 6:32 AM Eric Auer via Freedos-devel <
> freedos-devel@lists.sourcefor
On Sun, Feb 4, 2024, 6:32 AM Eric Auer via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:
>
> Hi Jim,
>
> > I'm glad you're bringing this conversation back to freedos-devel ..
> > because this is a good place to discuss FreeDOS things.
>
> In related news, the dosemu2 people also find
On Wed, Nov 8, 2023 at 3:21 AM Walter Oesch via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:
> I want to build the FreeDOS Kernel.
> I use Dosbox in Ubuntu Linux and watcom comiler from FreeDOS, version 1.9.
>
> I changed config.b to use watcom and copied to config.bat, then start w
I will look into it.
Jeremy
On Wed, Aug 2, 2023, 12:07 PM Wilhelm Spiegl via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:
> Hi all,
>
> I just worked on checking tree 3.7.2 - it is a little bit tricky. The
> source code of 3.7.2 seems to be identical with 3.7.1, but the .exe is
>
On Sun, Jul 23, 2023, 7:54 AM Liam Proven via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:
> On Sun, 23 Jul 2023 at 02:52, Paul Edwards via Freedos-devel
> wrote:
> >
> > My main interest is using Freedos+HX as a substitute for Windows 95.
>
> AFAICS you never explain. What is "HX"
On Thu, Oct 27, 2022, 1:53 PM tom ehlert wrote:
>
> > correcting for this, the the boooting kernel goes as far as
>
> ...
>
> I did my tests on a virtual machine on top of VirtualBox 5.2.44
> running on top of WindowsXP.
>
> I can send you the virtual machine by PM or FTP
>
> Tom
> .
If it is
On Tue, Oct 25, 2022, 6:05 AM tom ehlert wrote:
>
> Sorry,
>
> I posted this under the wrong topic.
>
> so:
>
> when downloading https://github.com/FDOS/kernel via
>
> [code] downnload ZIP
>
> the downloaded kernel-master\country directory is empty, and the
> project does not build.
>
This is a
On Fri, Dec 24, 2021, 9:39 AM Jerome Shidel wrote:
> Hello Everyone,
> ...
>
> One such item I noticed was the ATAPICDD driver. It might be nice to have
> an alternate CD driver that might cover some additional hardware. So, I
> added to that one to the repos. But, I don’t know much about this dr
I will look into it. It might have to wait for the next release, but I
will see what I can do. I wanted have a pre-release out so I could do the
release on Halloween, but looks like it might be Halloween until I get the
pre-release out with release to follow soon after (depends on issues
raised).
On Fri, Aug 20, 2021, 6:46 PM Aitor Santamaría wrote:
> Hello Jeremy,
>
> ...
>
> Thus sprintf and processEscChars differ in behaviour (although for this
> "buggy" string definition). I suppose that this new function
> (processEscChars) is added to avoid problems with the % symbol...
>
> Aitor
>
On Fri, Aug 20, 2021 at 4:48 PM Aitor Santamaría wrote:
>
> Hi,
>
> Thanks Jeremy.
>
> On Fri, 20 Aug 2021 at 13:03, wrote:
>>
>> > I was trying to figure out how KITTEN/KITTENC works. Seems to attach each
>> > NLS file with the "KITTENC" signal by the end of the executable. I've read
>> > abou
This is my understanding from reading the code a few days ago:
On Fri, Aug 20, 2021 at 6:32 AM Aitor Santamaría wrote:
>
> Hello,
>
> Sorry about the SPAM. I found the older thread too long, so I'm starting a
> new one with the same content (please comment here if you want to ).
>
> I was trying
On Sun, Aug 15, 2021, 5:53 PM Jim Hall wrote:
> Hi everyone
>
...
> 3. Fixed Codepage and time separator data errors in COUNTRY.SYS
>
>
I will publish with updated kernel release, unless a release by itself is
wanted? in which case I can do that too.
Jeremy
For a fairly comprehensive* list I ran across this site, it lists code
pages and the first version of DOS seen
https://www.aivosto.com/articles/charsets-codepages-dos.html
* where by comprehensive I mean just DOS based code pages, not
including the many additional ones available in other OSes suc
On Fri, Jul 30, 2021, 8:46 AM wrote:
> I am going to issue a pull request for the FreeCom changes, just haven't
> had a chance yet as I need to make sure I don't screw up codepages in the
> process. The changes are updating an email address and url and adding an
> additional % so mostly direct fi
I am going to issue a pull request for the FreeCom changes, just haven't
had a chance yet as I need to make sure I don't screw up codepages in the
process. The changes are updating an email address and url and adding an
additional % so mostly direct find and replace changes.
Jeremy
On Fri, Jul 30
On Thu, Jul 29, 2021, 9:02 AM tom ehlert wrote:
> with the changes below the kernel no longer splits disk transfers
> on disks that report via int13/48 'DMA boundary errors are handled
> transparently'
>
> ...
>
>
> changes:
>
> ***
Hello everyone,
So it took me a bit longer than I planned, but below is the
information needed to reproduce and links to sources. (Be kind, I
know that the code needs more work.)
To see it in action, from installing FreeDOS & Windows to running I
posted an updated the video (about 4 minutes, spe
On Sat, Jul 24, 2021, 6:43 AM Eric Auer wrote:
>
> Hi Jeremy,
>
> does that mean the unstable kernel already supported Win 3.1 386enh?
>
Yes, but it didn't work as well for running a dos prompt, 1st character
typed was lost and possibly other issues
> Cool to know :-) How about Windows for Wo
Hello all,
I thought some of you might enjoy this (others may really dislike it).
Link is to a (posted to YouTube) about 2 minute video of (version
2043+patches) FreeDOS kernel running Windows 3.1 in Enhanced and
Standard mode. I haven't pushed the changes to the public GitHub
repository yet as t
On Sun, Jul 18, 2021, 3:31 PM Jerome Shidel wrote:
> Hi,
>
> Couple quick questions…
>
> Is this a “(hopefully) ready-to-ship" version? Or, an intermediary
> “ready-to-test (more changes/fixes coming)” version?
>
ready-to-ship, but I sent the announcement to the dev list for wider
feedback. I t
Good morning,
I have published an updated (a) release of FreeCOM to address some
shortcomings from the previous 0.85 release.
https://github.com/FDOS/freecom/releases/tag/com085a
As before, the release provides multiple variants with the
recommendation to use one of the Open Watcom xms-swap versio
On Sun, Jun 13, 2021 at 6:27 PM wrote:
> ...
> If anyone has suggestions for how to get git to set timestamps on files, I
> would be greatful. I currently use diffs and git history to see changes.
> ...
>
After some suggestions and research I found a decent compromise.
Using git-tools, the fi
On Tue, Jun 15, 2021, 9:06 PM Paul Dufresne via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:
> I ...
>
> I am a bit confused...
>
1.3.4 is the latest release I am aware of, it was released in February.
The ones on GitHub are a mirror, I only recently updated the source from
1.3.2
On Sun, Jun 13, 2021, 4:44 PM tom ehlert wrote:
>
> > While I have not seen it discussed here yet,
>
> >
> https://sourceforge.net/p/freedos/news/2021/06/freedos-kernel-2043-and-freecom-085/
>
> IMHO this is not acceptable.
>
> freedos-devel@lists.sourceforge.net used to be the place to discuss
>
On Sun, Jun 13, 2021, 4:07 PM Eric Auer wrote:
>
> Hi Jeremy, Jim and remaining kernel and shell experts,
>
> While I have not seen it discussed here yet,
>
>
> https://sourceforge.net/p/freedos/news/2021/06/freedos-kernel-2043-and-freecom-085/
>
> writes:
>
> > FreeDOS kernel 2043 and FreeCOM 0.
2042 is kernel version 2.42, specifically the kernel build # is major *
1000 + minor which currently equals 2000 + 43 = 2.43 for 0xFD kernels.
Note that the kernel releases just have a version number to identify them,
whereas development builds should include cvs/svn/git (depending on how
old) as
I will be making a new kernel release as soon as I can. This weekend if my
computer behaves. I also have a few other programs that may need new
releases just for updated translations. I'm aware it's late in release, so
these may just be post release updates.
Jeremy
_
pdtree is the current version of tree, I haven't made a new package just
calling it tree, but that's mostly because I haven't needed to fix any
issues
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/l
On Sun, Feb 28, 2021, 8:26 AM Eric Auer wrote:
Hi! I remember that some of our SYS versions have some
extra options to make them more flexible to load other
kernels. I would like to know HOW flexible. In particular,
ECM mentions some special requirements for MS DOS / PC DOS:
https://www.bttr-so
On Sat, Jun 6, 2020, 8:29 PM Jerome Shidel wrote:
> Hi Eric,
>
> ...
> Overall, I think a better solution would be for the kernel team
> (PerditionC) to
> build the 8086 kernel with a comparable feature set to the 386 kernel
> where
> possible.
>
> Maybe the i
On Mon, May 18, 2020, 3:58 PM thraex wrote:
>
>
> On 18.05.2020 15:17, Jerome Shidel wrote:
>
> > First, http://freedoslocal.sourceforge.net is no longer maintained.
>
> Indeed, that's a resource I miss sorely as a translator :(
>
> > Occasionally, individuals have sent me translations for packag
I am going to go through bug reports on SF, my email archive and anything
posted to GitHub in next few weeks. I am going to try to make a new
release.
If there is anything specific you want me to focus on, feel free to send
me/the list an email or post on GitHub.
Please let me if there are any o
I am going to go through bug reports on SF, my email archive and anything
posted to GitHub in next few weeks. I am going to try to make a release
build of FreeCom, no pre#. I may post some test builds in the process
though.
Please let me if there are any objections or comments about this. If th
On Fri, May 15, 2020, 4:09 PM Robert Riebisch wrote:
> Hi Jim,
>
> > Email
...
> > And we also have the Wiki for documentation and other information, and
> > the bug tracker on SourceForge to track bugs and feature requests.
>
> And we can't keep up with fixing things and updating items. :-/
.
/kernel
Jeremy
On Mon, Jul 16, 2018 at 2:24 PM, Louis Santillan wrote:
> Are there any thought as to how TK Chia's gcc-i16 port [0] and Bart
> Oldeman's patches [1][2] might fit into 1.3+ plans?
>
>
> [0] https://github.com/tkchia/gcc-ia16
> [1] https://github.com/Perd
On Tue, Feb 27, 2018, 4:32 PM Mark Olesen wrote:
> I need help in deciding how to port Fl_Preferences for fltkal (port of
> FLTK). Fl_Preferences is like an INI file.
>
> ...
>
> Any suggestions. Thanks in advance.
>
>
I would suggest both, default to relative to exe, but allow the user to
ove
For clarification, it crashes on startup or immediately returns to command
prompt, or doesn't do something? What kernel and freecom versions? Have
you tried without any memory managers?
Thanks for the answers. I will see if I can duplicate (and hopefully track
down the issue).
Jeremy
-
On Oct 1, 2016 2:59 PM, "Matej Horvat" wrote:
>
> >
...
>
> This is one of several bugs that occurs if FreeCOM is compiled with Open
> Watcom. Is that the case here?
>
Yes, I usually compile with Open Watcom; whether it's the cause of issues
or not, I haven't looked into it.
-
On Thu, Sep 29, 2016 at 8:54 AM, Tom Ehlert wrote:
>
...
> with some patience (and a little ingenuity) I even located
> http://www.fdos.org/kernel/
>
> with http://www.fdos.org/kernel/command/, and could reproduce the bug.
> unfortunately, no source.
>
This is an unmodified build from svn (down
On May 6, 2016 6:42 AM, "MikeSun(孙国祥)" wrote:
>
> Hello developer,
>
>
>
> I’m BIOS vendor-AMI.
>
> When we test FreeDOS latest version, w found beep command can't stop
sounding in Intel Skylake platform.
>
>
>
> But we build beep source code(from FreeDos open source) by Watcom C tool
and run beep
Thanks, I will look at them tonight. I apparently have some in a local
repository as well that I need to see if should be applied or not.
Jeremy
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
AP
On Tue, Jan 12, 2016 at 1:36 PM, Tom Ehlert wrote:
> Hi,
>
> just wondering what the 'official' most recent version of COMMAND.COM
> is.
>
> is it http://sourceforge.net/p/freedos/svn/HEAD/tree/freecom/trunk/ ?
>
> I remember that Bart ported command.com 'mostly' to WATCOM; is the
> port now finis
On Jan 12, 2016 1:37 PM, "Tom Ehlert" wrote:
>
> Hi,
>
> just wondering what the 'official' most recent version of COMMAND.COM
> is.
>
> is it http://sourceforge.net/p/freedos/svn/HEAD/tree/freecom/trunk/ ?
>
> I remember that Bart ported command.com 'mostly' to WATCOM; is the
> port now finished,
On Sat, Jan 9, 2016 at 11:44 AM, Tom Ehlert wrote:
> Hi,
>
> whoever is responsible currently for XCOPY (Blair?):
>
>
> in line ~450, don't use
>
>
>if (chsize(fddest,filelength(fdsrc)) == -1)
> ...
>
...
Which version of XCOPY? and which file? I don't see this line so I'm
trying to fi
On Dec 18, 2015 8:18 AM, "Paul Dufresne" wrote:
>
> Me again! ;) This FREEDOS page about country.sys:
> http://help.fdos.org/en/hhstndrd/base/cntrysys.htm
> It speaks about stable vs unstable kernel... (written in 2008) do we
> still have these today?
>
No, there is only one active branch (stable
On Oct 9, 2015 10:36 AM, "Joe Forster/STA" wrote:
>
> Hi guys,
>
>
>> A normal DOS app can only access the first 4 GB of a file, or at least
it can not seek beyond that, nor can it know about file sizes being beyond
that.
>
>
> This came to my mind, too! Where is INT 21h, AX=7142h, the
LFN/extende
I did some testing in VirtualBox, and yes the current kernel does not work
in Windows 3.1 enhanced mode (you must use my 0xDC kernel [see FDOS project
on SF], but I couldn't get the DOS boxes to work anymore).
I will have to do some checking as I expected either to work. When running
Windows 3.x,
I will try to look at this in next day or so; email me directly if not
as it means I got sidetracked ...
Jeremy
On Thu, May 28, 2015 at 2:11 AM, Mateusz Viste wrote:
> On 24/05/2015 11:29, Mateusz Viste wrote:
>> DIR: When using DIR/P, DIR seems to think that the screen is 1-row high,
>> and ask
There are multiple issues being brought up in this discussion.
1 - there is a desire for an 8086 compatibility [a goal of FreeDOS project]
2 - there is desire still for 360KB floppy images [haven't seen a request
for in years (that I recall off-hand), but something easily supported]
3 - video requ
On May 18, 2015 7:14 PM, "J.K. Benedict" wrote:
>...
> I was thinking of tackling the laplink-style copy (for many reasons, such
as reliability and preserving nostalgia)
>
... Feedback/thoughts welcomed, such as what to "name" the program
(portlink?), any desired argument flag format? IE, retries,
On Apr 4, 2015 4:52 PM, "Aitor Santamaría" wrote:
>
> Hi,
>
> And that's such a sad news, if Japheth's software cannot be accessed
anymore.
>
> Oh well...
> Aitor
>
>
> 2015-04-04 22:08 GMT+02:00 Rugxulo :
>>
>> Welp, it was fun while it lasted
>>
...
>> >> On Fri, Jan 2, 2015 at 1:39 PM, A
On Mar 30, 2015 2:56 PM, "Eric Auer" wrote:
...
>
> PPS: Can anybody check if similar "Asuses" have the same issue?
...
I have never had a problem with this for any of my Asus motherboards; I
have had several through the years. I once had an issue booting a
nonstandard bootdisk but I don't recal
On Mar 19, 2015 9:23 PM, "Teddy T." wrote:
>
> Good Evening,
>
...
> Could someone please confirm if FreeDOS may really cause this kind of
problem, if it could prevent a BIOS from using several boot options, making
it unable to switch automatically between them ? And if this behaviour is
really ca
but effectively working, even if such sector sizes
> are ineffective and arguably ridiculous).
>
> I'd like to hear from the Kernel team (is that just one-man, aka
> PerditionC ?) on this subject.
>
> A proposed roadmap could have, ideally :
>
...
My current plans are to
luding source archive.
http://www.fdos.org/kernel/testing/git/
This is a fairly stable location and referenced in my github page (
https://github.com/PerditionC/fdkernel).
I have a temporary* build of FreeCom at
http://www.fdos.org/kernel/command/FreeCom/test/
* where temporary means will be there unti
On Sat, Jul 19, 2014 at 3:18 PM, Eric Auer wrote:
>
> Hi Jeremy,
>
> > In shell/command.c the following patch should fix the issue (assuming
> > switchar changed).
> > @@ -331,8 +331,10 @@
> > break;
> >case CMD_SPECIAL_DIR: /* pass '\\' & '.' too */
> > if(*rest == '\\'
On Fri, Jul 18, 2014 at 3:00 PM, Juan Manuel Guerrero
wrote:
> I do not know if this is the right place to report this FreCom issue and
> I do not know if this issue is already well known but I would like to
> report it anyway.
> Please inspect the following batch file:
>
> @echo off
> @echo %0
>
I am doing some testing of basic stuff and would appreciate the image. You
can email me or let me know where I can download from. I am playing with
the test image, some rough edges but I like the isolinux menu.
Jeremy
--
I will try to respond better when I'm home. Kernel 2040 is released but not
yet announced. Use share & country that is with kernel. I believe I
checked all versions floating around a year or so ago & have latest share
with kernel (I need to verify both SVN versions). I don't know much about
us
On Mon, May 23, 2011 at 2:33 PM, Bernd Blaauw wrote:
> (I'm not sure I'm a member of the FreeDOS kernel mailinglist, can't find
> anything, so sticking to development list)
>
> Right now when experimenting I'm experiencing an issue:
> switching to B: by entering B: seems to give the following erro
On Mon, May 23, 2011 at 2:50 PM, Bernd Blaauw wrote:
> For a Bootable CD I'd like to offer the user the choice between a few
> memory/driver options (no drivers, or XMS, or XMS/EMS/UMB)
> Despite commandline loadable memory drivers like JEMMEX LOAD or DEVLOAD
> HIMEMX.EXE, the optimal result is ga
74 matches
Mail list logo
