Hi Eric,
- Original Message -
From: Eric Auer [EMAIL PROTECTED]
To: Hans [EMAIL PROTECTED]; freedos-kernel@lists.sourceforge.net
Sent: Sunday, October 26, 2008 7:19 PM
Subject: Re: [Freedos-kernel] [Freedos-user] init_device crash/hang
Quite exotic. How about using a maintained open
Hi Hans,
infamous Bad or missing Command Interpreter error
This means FreeDOS looked for the boot files on the
wrong drive or failed to access any drive at all. If
it cannot open fdconfig.sys, it will try config.sys
next, and if it cannot open that, it will use a built-
in default
Hi Hans,
1Mbyte of RAM with the top 8Kbyte taken by the BIOS.
All ram is available
Exotic :-)
the BIOS test the first 704Kbyte...
Ah okay... well 640k are enough and more expected.
You could also check at b800:xx to check if DOS apps
try to do screen output there...
I used 704 as that
Hi Hans, replying via freedos-kernel...
My system seems to boot until it starts init_device() in kernel/main.c.
InitIO calls init_device 12 times before my system crashes (see below)...
KERNEL: Entering init_kernel()...
HMA moving 0268: up to 9fde: for 9cdf bytes
This message is a
Hello Alain,
One question, did you happen to manage how does WinNT perform with
such an enlarged FAT system?
I'm tired of the fact that I have to either partition or use NTFS
(rather problematic if you protect your Documents and settings with
password and then windows gets trashed), and it could
Hi!
1) new disk was used with Linux, but a first primary partition was made
but never formated
Make sure it is flagged as fat32 and as lba. Check possible
messages from initdisk early during freedos boot as well.
I recently tried making a DOS bootable partition on a new
disk, too, and found:
You are a genius...
This floppy change problem has been around for some time because it is
hard to reproduce. The steps 1 to 5 in problem 2 are all done from a
single running program? If so it may be related to a problem I
encontered a few times.
Thanks, very much
Alain
Koike Toshio
Hi!
On Fri, 5 Sep 2008, Koike Toshio wrote:
The patches are uploaded here.
http://us.f13.yahoofs.com/bc/48b6f314_185bc/bc/freedos/patch080818.zip?bfh__vIBxIiwN9fQ
Redirects to a non existing hostname:
http://bcvrf.yahoo.com/bc/48b6f314_185bc/bc/freedos/patch080818.zip
Problem 1: Maxell new
Eric Auer escreveu:
Problem 1: Maxell new FD has No 55-aa magic number in boot sector.
You might have fixed that the wrong way round... FreeDOS tries too
much to behave well for unformatted disks, which should be fixed in
www.coli.uni-saarland.de/~eric/travis.zip ... the idea is to make
Hi!
I'd have to check the sources I have here for several dos versions
Please avoid getting in touch with source code for dos versions
that are supposed to be closed source. Mixing any information
from such sources into our development would be inappropriate.
Note that share has a call that
Hi Christian,
seems to be an older issue, but BUFFERSHIGH is not recognised by
BUFFERS are always in the HMA as soon as FreeDOS uses the HMA
(DOS=HIGH) unless the BUFFERS are too many to fit in the HMA.
Of course one could make BUFFERHIGH a synonym for BUFFERS? ;-)
FreeDOS. Buffers are
Hi again... I finally found a way to make a not overly
intrusive patch which hopefully fixes Travis' problem:
http://www.coli.uni-saarland.de/~eric/travis.zip has
a diff and a binary. The patch changes several things:
- init_getdriveparm would overflow for int 13.8 returning bl=7
but this is
Hi Eric and Tom,
if (r-SI == 0) -- do not leave this test as ... == 0
...
Otherwise all typed reads would turn into writes!
I didn't look at the source any further ;-)...
But of course, you are right.
I suggest the following patch. If there are no objections, it
can go into stable
Hi Christian,
the Int 0x21, AX=0x7305, CX=0x handler (FAT32 - EXTENDED ABSOLUTE
DISK READ/WRITE) found in inthndlr.c, 355 ff., is implemented in a
very strict way ... it corresponds to www.ctyme.com/intr/rb-3229.htm
This is RBIL, Ralph Brown's Interrupt List - usually pretty useful.
Hi Eric,
how about compiling this for Christian ?
not everybody likes to download watcom, find out how to get kernel
sources compiled ...
and after he verified this private version, may be even put it on
ibiblio to be used by others ?
Tom
Hi Tom, Alain,
whatever 'ready' means when nobody (except you self)
tested it so far.
While there were no official sourceforge file releases,
there are updated versions on the rugxulo distro page
http://rugxulo.googlepages.com/ and I did mention those
on our lists from time to time. His
Hi,
suggesting a new filesystem witch in my opinion I think is easy...
Your suggestions are mostly userspace, so let us discuss
your suggestion on freedos-devel, not on freedos-kernel.
You do suggest device files, but remember that the kernel
already has that: Device files like LPT1 are in no
Hello,
2007/12/26, Eric Auer [EMAIL PROTECTED]:
Hi Marton,
CCing the kernel list about this issue... Merry Xmas everybody :-).
If I do ANY operation to the disk, say, read a directory for example, I
get a PANIC: more than two near fnodes requested at the same time!
Hmmm I did not know
Eric Auer wrote:
the FreeDOS PC it is painfully SLOW! (100kb/sec)
How fast is it with other DOS?
Definitely not 100kb/s... (hint: maybe ~750kb/s? :-)...
Maybe you tried this on a large fat32 disk? I think our FAT
writes can be pretty slow in such a context. You can also try
using a
Johnson Lam escreveu:
I always have 20, but my point is 20 is for user application, system should
not count in the list, since they are a must.
Buffers are alocated dinamicaly which is a better aproach than reserving
some for this and some for that...
What I don't understand is why you
On Sun, 28 Oct 2007 19:41:20 +0100, you wrote:
to fix any bug, it must be reproduced first.
As noone has ghost 5, 'the bug' can't be reproduced, and so can't be fixed.
Downloaded the kwc38632.dev.zip, dated 2006-07-14, nothing changed.
Eric just ask me to test in private email (again), I have no
Johnson Lam escreveu:
Did you mean set the FILES=2 really have 2 buffers?
This *should not* happen, DOS opens 5 files by default: stdin, stdout,
stderr, auxin and aux out. An extra one is needed with dos extenders. I
would say that 7 or 8 would be a minimum to keep things running.
By
--- Johnson Lam [EMAIL PROTECTED] escribió:
On Sun, 28 Oct 2007 19:41:20 +0100, you wrote:
to fix any bug, it must be reproduced first.
As noone has ghost 5, 'the bug' can't be reproduced, and so can't be
fixed.
Downloaded the kwc38632.dev.zip, dated 2006-07-14, nothing changed.
Eric
Hello,
2007/10/27, Johnson Lam [EMAIL PROTECTED]:
On Sat, 27 Oct 2007 07:19:07 +0200, you wrote:
Hi Aitor,
You're wasting precious time on outdated programs.
It might discover one more serious bug.
Most people will run Ghost 8 and 2003 on FreeDOS (including me), I
don't have a Ghost 5
Hopefully someone can found the bug and fix it, my pathetic knowledge
forbid me to help.
to fix any bug, it must be reproduced first.
As noone has ghost 5, 'the bug' can't be reproduced, and so can't be fixed.
end of story.
Tom
Hi Johnson,
1658 Ghost 5.1 fails: Needs somebody with Ghost 5.1 to fix
Just try Ghost 8.0 and Ghost 2003, if they work don't stick to Ghost
5.1, there MAYBE problem due to 5.1.
You're wasting precious time on outdated programs.
Maybe true, but I do not have ANY version of Ghost to test :-(
1658 Ghost 5.1 fails: Needs somebody with Ghost 5.1 to fix
Maybe true, but I do not have ANY version of Ghost to test :-(
If a newer version of Ghost works, then we could indeed set
the bug status to wontfix and mention that newer versions
do work fine. Or we could lower bug priority to
On Sat, 27 Oct 2007 07:19:07 +0200, you wrote:
Hi Aitor,
You're wasting precious time on outdated programs.
It might discover one more serious bug.
Most people will run Ghost 8 and 2003 on FreeDOS (including me), I
don't have a Ghost 5 to run, if Ghost 2003 works fine, I see no reason
to
On Fri, 26 Oct 2007 15:53:03 +0200 (MEST), you wrote:
Dear Developers,
1658 Ghost 5.1 fails: Needs somebody with Ghost 5.1 to fix
Please!!
Just try Ghost 8.0 and Ghost 2003, if they work don't stick to Ghost
5.1, there MAYBE problem due to 5.1.
You're wasting precious time on outdated
Hello Johnson,
2007/10/27, Johnson Lam [EMAIL PROTECTED]:
On Fri, 26 Oct 2007 15:53:03 +0200 (MEST), you wrote:
Dear Developers,
1658 Ghost 5.1 fails: Needs somebody with Ghost 5.1 to fix
Please!!
Just try Ghost 8.0 and Ghost 2003, if they work don't stick to Ghost
5.1, there MAYBE
i don't think that there is a full documentation on the internals of FreeDOS
however you can find the info you are looking for on:
1.) you can try finding some info on the wiki of freedos...
http://fd-doc.sourceforge.net/wiki/index.php
and
http://wiki.fdos.org/pmwiki.php
2.) you can dig into
Hi Japheth,
(changing subj from Some FreeDOS kernel bugs reported by
Jack R. Ellis and moving the issue to freedos-kernel...)
... just reported a bug/issue found in the FreeDOS kernel:
http://www.bttr-software.de/forum/...
I guess a few people will have bad mood after reading this,
so it
2. It is way slower in file copy/compare than other DOSes.
(maybe we should make FAT and DIR data access smarter?)
depends on a couple of factors; the huge threat on
http://www.drdosprojects.de/forum
about FreeDOS is slow was less then scientific
a) COPY
FreeDOS allocates always the
Hi Tom,
thanks for your feedback :-)
2. It is way slower in file copy/compare than other DOSes.
(maybe we should make FAT and DIR data access smarter?)
...
FreeDOS allocates always the lowest unused cluster, even if
the file should be enlarged by a large ( 1 cluster) amount.
My opinion:
F8 *should* remain, people are just used to it.
gotoxy *shoul*not* exist, that is trouble in some (too many) cases
Instead of ENTER for default, one could write ENTER for [1]
where 1 is the default in this example.
I vote ENTER for default *but* it shlould be obvious which is
Hi Lucas,
your mail did indeed arrive as html...
FreeDOS does in general support the same interrupt services
as other DOS versions. A good list of such services is in
Ralf Brown's Interrupt List (RBIL) which is mirrored on many
pages. Main location is: www.cs.cmu.edu/~ralf/files.html
I would
Hi all,
please check the current kernel updates with Bart's FASTBOOT
versus STACKS fix and some DOS 6 compatibility updates from me:
Binaries: www.coli.uni-saarland.de/~eric/svn-binaries-freedos.zip
Something else: Rugxulo tested the executable-unpacker IUP
Hi,
2007/7/23, Bart Oldeman [EMAIL PROTECTED]:
Although the ioctl.c restructuring is good, most of the chario.c
savings also help. A lot more could be saved in initdisk.c by using
the fact that the sector size equals 512 (the DOS code cannot assume
that with ram disks etc, but the BIOS code
On 7/22/07, Eric Auer [EMAIL PROTECTED] wrote:
again, I think that only IRQTEXT is what broke Bochs compatibility.
So I applied a patch (revision 1341) which leaves the other 1325
changes intact. Jemm FASTBOOT should work with version 1341.
With the 1325 IRQTEXT, all versions (1325 to 1340)
On 7/21/07, Eric Auer [EMAIL PROTECTED] wrote:
Are there any volunteers to maintain the UNSTABLE
branch of the kernel?
I was looking into merging parts of UNSTABLE a few months ago but it's
a lot of work since I don't like about half of the changes. And after
that I ran out of time, and still
Hi Bart,
I was looking into merging parts of UNSTABLE a few months ago but
it's a lot of work since I don't like about half of the changes.
Actually I think it might take man-months or more to review all
the MANY changes between unstable and stable, plus merge all the
fixes of stable into
Eric Auer schreef:
Hi Bernd,
*your KERNEL.SYS in renewed archive works fine, nice job.
[ http://www.coli.uni-saarland.de/~eric/ke2007jul21.zip ]
*JEMMEX v5.64 can be compressed and works, can't see it listed in MEM /C
( MEM /C /N ) listing though, maybe it\s hiding under SYSTEM :)
(UMBs
Eric Auer schreef:
Hi Rugxulo, Robert, kernel people,
Hello Eric,
branch of the kernel? Rugxulo, KEYBUF should obsolete having a
keyboard extender around. Kernel people, IDLEHALT does not
obsolete FDAPM APMDOS but it gives you some energy-saving even
without FDAPM. I hope both can be used
Hi Bernd,
Only KERNEL2.SYS works for me, better than the Fastboot supporting
kernel I downloaded (I think) a while ago.
KERNEL.SYS in your zip hangs my machine at the HMA/BUFFERS message.
Yes, I have the same problem :-(. What I did to create kernel2 is
to undo the changes of SVN revision
Hi again,
after checking
http://freedos.svn.sourceforge.net/viewvc/freedos?view=revrevision=1325
again, I think that only IRQTEXT is what broke Bochs compatibility.
So I applied a patch (revision 1341) which leaves the other 1325
changes intact. Jemm FASTBOOT should work with version 1341.
Eric Auer schreef:
Please test :-)
You relying on me to test or does this new binary work for you in Bochs?
Sample kernel binary: www.coli.uni-saarland.de/~eric/ke2007jul21.zip
same filename yet updated release?
Bernd
Hi Andris,
I think Bart Oldeman recently fixed the GNU SED problem...
Some time ago I submitted am error report for DOSEMU about
problems running DJGPP port of GNU SED from configure scripts
http://sourceforge.net/tracker/index.php?func=detailaid=1429741group_id=49784atid=457447
and also
Eric Auer wrote:
Hi Andris,
I think Bart Oldeman recently fixed the GNU SED problem...
Some time ago I submitted am error report for DOSEMU about
problems running DJGPP port of GNU SED from configure scripts
Andris Pavenis wrote:
Eric Auer wrote:
Hi Andris,
I think Bart Oldeman recently fixed the GNU SED problem...
Some time ago I submitted am error report for DOSEMU about
problems running DJGPP port of GNU SED from configure scripts
On 6/3/07, Andris Pavenis [EMAIL PROTECTED] wrote:
kernel/int2f.asm generates reference to _nlsInfo which remains
unresolved. I had to rename it to NLSINFO there for linker to succeed.
2007/05/01 CVS version did not compiled out of box. So this problem
has appeared after that.
This problem was
Hi Nick and everybody else who wants to unsubscribe:
[furious scream of frustration]
How do I get off of this mailing list?! I've
been trying to get off of it for months. Help me!
That is ridiculously easy :-).
Each mail explains it in the headers:
List-Unsubscribe:
Hi Reddy,
http://www.delorie.com/djgpp/doc/coff/ provides lots of
COFF info, but I think there are several file formats
which are all called COFF. As DJGPP is open source, you
can also read COFF file format aware source code in the
sources of the compiler, linker / binutils, C library...
For the
Hi Bart,
here my reply to your reply to my list :-)
Few part 2 reactions first:
- what was the reason for 21.3301 modifying DL again?
- why is 2f.1228 seek disabled?
- do you want to explain the something else in nls.c?
Reactions to this first part:
Any volunteers for SYS.TXT / CONFIG.TXT /
NOTE that both versions have a typo: ... the any key ...
It's not a typo! Damnit! Still haven't found the any key?
see http://www.computergear.com/pressanykey4.html
and http://www.gadgetizer.com/2006/04/03/any-key-mistery-solved/
or just google for the any key ;)
Tom
Hi Bart,
nice to see you're still alive :)
Tom, can you explain?
1. config.c. Why use instead of =? Is there a corner case with equality?
IMO = is correct (timeout 0 should exit immediately)
2. initoem.c:
+ if (ramsize == peek(0, RAMSIZE))
if (ramsize * 64 == ebdaseg ramsize 640
Hi Bart, Tom,
some extra comment for
2. initoem.c:
+ if (ramsize == peek(0, RAMSIZE))
if (ramsize * 64 == ebdaseg ramsize 640 peek(0, RAMSIZE) == ramsize)
the extra double check looks strange to me, why check twice?
Something strange with short-circuit boolean evaluation?
... I got
Part 2...
On 1/1/07, Eric Auer [EMAIL PROTECTED] wrote:
inthndlr.c: Toms version modifies DL on return from int 21.3301
(set ctrl c flag), while the CVS does not - CVS is better.
TA -- discussed earlier
The CVS version uses the new dpb16to32 function for shorter code.
CN
TOMS
Hi!
12-Янв-2007 15:27 [EMAIL PROTECTED] (Leonardo Hirokazu de Souza
Hamada) wrote to freedos-kernel@lists.sourceforge.net:
LHH I read somewere that FAT32 support in FreeDos is not yet complete so
It _is_ complete - FreeDOS fully supports reading/writing to FAT32
partitions.
Welcome in 2007 :-)
Here part 2 of my mail from last year ;-), comparing Toms
extra stable 2035c kernel to the CVS stable HEAD 2036 kernel.
inthndlr.c: Toms version modifies DL on return from int 21.3301
(set ctrl c flag), while the CVS does not - CVS is better.
The CVS version uses the
Hi, have some answers :-). Maybe you can push them
into alt.os.free-dos somehow, in a spam-safe way...
Google Groups is a nice webUSENET interface. Have a look at
http://groups.google.com/group/alt.os.free-dos
Look for Kernel Bug (the first message right now) and
FreeDOS Install Language
Hi Jackie,
basically other DOSes include a workaround to protect
programs from themselves when they try to do disk access
with buffers which cross multiples of 64k address-wise,
while FreeDOS does not, yet, have such a workaround in
the kernel. As far as I know, that part would be written
in
Pavel Roskin wrote:
I downloaded the floppy image for FreeDOS 1.0, fdboot.img. I tried to
boot it on a desktop system with AMD XP 2000+ CPU and a CD-ROM drive.
Selecting item 5 (FreeDOS Live CD only) resulted in an Invalid Opcode.
This is an error in the 8086 version (corrupted stack). I
There are no updates since 1.0.
On 9/22/06, hiratak [EMAIL PROTECTED] wrote:
Good afternoon,
What happened to the lovely directory of the latest compiled kernel and
command
that used to be available at http://fdos.org/kernel/ ? When I click
directory,
I go to
- int 2f.4a00.cx=0 the kernel has to call this before it displays
the Insert diskette for drive B: (or A:...) message, to let
Win3 and the like show a GUI dialog instead of the message, DOS 5.0
seems to have been lost; should be
STATIC WORD play_dj(ddt * pddt)
{
/* play the DJ ... */
--- Arkady V.Belousov [EMAIL PROTECTED] wrote:
Then I completely not understand you. DTA is a name for area, which
used for findfirst/findnext. What _you_ name as DTA?
My mistake - I was confusing SHSUCDX (the redirector has what is called
a DTA to point to the read address) and the
Hi!
30-Авг-2006 15:55 [EMAIL PROTECTED] (Jason Hood) wrote to
freedos-kernel@lists.sourceforge.net:
Not sure, if I understand your problem, but what prevents you from
setting your own address of DTA (INT 21/1A)?
JH Perhaps I should have been a bit more clear. The DTA I was referring
JH
--- Arkady V.Belousov [EMAIL PROTECTED] wrote:
Not sure, if I understand your problem, but what prevents you from
setting your own address of DTA (INT 21/1A)?
Perhaps I should have been a bit more clear. The DTA I was referring
to passes the pointer to the buffer for the read request.
Hi!
23-Авг-2006 16:11 [EMAIL PROTECTED] (Jason Hood) wrote to
freedos-kernel@lists.sourceforge.net:
JH I received a bug report about SHSUFDRV not working in FreeDOS, but
JH it worked fine in MS-DOS; RDRV also worked fine. After failing to
JH replicate the problem with the versions of FreeDOS I
is loaded.
Eric
PS: This is the 2nd attempt to post this message, maybe
there is something wrong with the mailinglist for me...?
--
Message: 3
Date: Sat, 22 Jul 2006 19:05:26 -0400
From: Kenneth J. Davis [EMAIL PROTECTED]
Subject: Re: [Freedos-kernel] bug
Abrahan Sanjuas wrote:
...
I suppose that this kernel is not compiled with WIN31SUPPORT option
because the debugging messages in the end of execution of a program does
not shown on screen. And how i can view if kernel is compiled with
WIN31SUPPORT or NOT???
The simplest way I can
Speaking of Windows compat, by the way: WIN /S works fine with 2036,
but WIN /3 does not work with 2036 nor with 2037 for me. It just
returns to the prompt. Bug 2037 is supposed to add Win386 support...
You're supposed to make a system.ini change as well and load MS's
EMM386/HIMEM. See the
On Sun, 21 May 2006, Eric Auer wrote:
As a next step, I would like to update the UNSTABLE kernel
branch. If anybody can tell me how this is accessible via
cvs, that is.
you have to give cvs the command line option -r UNSTABLE.
PS: If you want Turbo C compiled kernels published, please help
Hi Bart,
you have to give cvs the command line option -r UNSTABLE.
interesting!
Turbo C insists that the source files have CRLF line endings.
You ran into the old problem that UNIX CVS clients check out source
files
using LF line endings and Windows (not sure if anyone uses a DOS CVS
On Sun, 21 May 2006, Eric Auer wrote:
kernel for over a year now has a new name and a new home:
...
Directory BIN is absent in a tree of kernel2036-source.zip/
--
Take care. Your friend,
dima 7509107*mail,ru 2:550/112
---
Using Tomcat but
najmus saqib wrote:
HELLO
I want to ask something about DOS interrupts. Does freeDOS uses
MSDOS interrrupts. How can i do the same. can any1 tell me about the
Yes, it uses the same interrupts and parameter interface as MSDOS. More
specifically, it attempts to implement nearly 100%
Kenneth J. Davis wrote:
Eric Auer wrote:
Hi, I looked at the issue kernel acts weird if there is no
diskette drive... In short:
...
Eric
for testing, a very similar patch, please try
http://www.fdos.org/kernel/test/kernel.boot.sys
Jeremy
Hi Jeremy:
Well, that kernel works on the
Kenneth J. Davis wrote:
for testing, a very similar patch, please try
http://www.fdos.org/kernel/test/kernel.boot.sys
Jeremy
Hi Jeremy:
This modified kernel also works fine in the cursed compaq,
booting in HDD mode (with an MBR). The HP utility also works
fine on this machine.
Eric Auer wrote:
Hi, I looked at the issue kernel acts weird if there is no
diskette drive... In short:
...
Eric
for testing, a very similar patch, please try
http://www.fdos.org/kernel/test/kernel.boot.sys
PS: As a bonus possible problem, I noticed that the cvs unstable SYS
FAT1x
Charles Doty wrote:
Is there a specific reason to compile out the check and not simply use
the config option to disable the 2 second f5/f8 check?
I missed that config option. Is it in config.b?
No, perhaps I should have been more clear. It is a settable
configuration option via sys
Is there a specific reason to compile out the check and not simply use
the config option to disable the 2 second f5/f8 check?
I missed that config option. Is it in config.b?
---
This SF.Net email is sponsored by xPML, a groundbreaking
Charles Doty wrote:
I modified the following files to allow the kernel to boot from a floppy
without all of the delays:
config.c (around line 693):
...
Is there a specific reason to compile out the check and not simply use
the config option to disable the 2 second f5/f8 check?
I will
and
increasethe kernel version (Robert Riebisch)
--__--__--
Message: 1
Date: Fri, 27 Jan 2006 11:32:12 +0100
From: Robert Riebisch [EMAIL PROTECTED]
Organization: BTTR Software
To: freedos-kernel@lists.sourceforge.net
Subject: Re: [Freedos-kernel] please change the default freecom
Alain wrote:
Would averyone agree to include it?
I agree. ;-)
Robert Riebisch
--
BTTR Software
http://www.bttr-software.de/
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the
David O'Shea schreef:
It says The UNSTABLE (aka development) branch is what I refer to as the
development kernel (kernels with w suffix). It looks like those kernels
actually have .dev or .dbgdev in them, right?
There doesn't seem to be a discussion of the naming convention for FreeCOM.
On Thu, 26 Jan 2006, Bernd Blaauw wrote:
David O'Shea schreef:
It says The UNSTABLE (aka development) branch is what I refer to as the
development kernel (kernels with w suffix). It looks like those kernels
actually have .dev or .dbgdev in them, right?
There doesn't seem to be a discussion
Hi!
26-Янв-2006 22:48 [EMAIL PROTECTED] (Bart Oldeman) wrote to
freedos-kernel@lists.sourceforge.net:
well, we have:
kernel 2034, 2035 released by Bart
kernel 2035A released by Jeremy
kernel 2035B by Jeremy (2035A + stable features backported from 2035W)
kernel 2035W by Jeremy,
Hello Bart,
well, we have:
kernel 2034, 2035 released by Bart
kernel 2035A released by Jeremy
kernel 2035B by Jeremy (2035A + stable features backported from 2035W)
kernel 2035W by Jeremy, experimental/development line
isn't there also still a kernel 2035-Tom somewhere (drivesnapshot.de)?
Bart Oldeman schreef:
To be fair I found Eric's email rather demanding. In general if you
want things to happen in the NEAR future you either have to do it
yourself or pay big bucks, not just pizza money. Certainly when the
kernel doesn't have a real maintainer (just an interim one who does
Eric Auer escreveu:
Hi,
http://fdos.org/kernel/
makes people use 8086 FreeCOM if I understand the text right.
This means they will likely have no XMS swap and no LOADHIGH.
In short, they will think FreeCOM is really a BAD command.com
I agree.
My other wish is using a new version number.
飘似沙鸥 飘 wrote:
Hi, I'm a newer to FreeDOS and I want to know if FreeDOS can be
installed on embedded system based on 80186/80188? If yes, is it
The FreeDOS kernel and most programs are fully compatible with 8086* and
higher computers, so if the embedded system is similar enough standard
IBM
Hi!
16-Дек-2005 19:45 [EMAIL PROTECTED] (╞о╦╞╔│┼╕ ╞о) wrote to
freedos-kernel@lists.sourceforge.net:
оо Hi, I'm a newer to FreeDOS and I want to know if FreeDOS can be installed
оо on embedded system based on 80186/80188?
Yes.
оо If yes, is it possible that
оо freeDOS work on an embedded
Hi!
16-Дек-2005 13:50 [EMAIL PROTECTED] (Eric Auer) wrote to
freedos-kernel@lists.sourceforge.net:
EA EDIT 0.7d and MKEYB, which should work even on 8086. Or use no
MKEYB uses INT15 service, which not present on XT.
---
This SF.net
On 12/16/05, 飘似沙鸥 飘 [EMAIL PROTECTED] wrote:
Hi, I'm a newer to FreeDOS and I want to know if FreeDOS can be installed
on embedded system based on 80186/80188? If yes, is it possible that
freeDOS work on an embedded system without BIOS?
I explored this issue two years ago trying to use
Arkady V.Belousov wrote:
...
BTW, bug! Function number should come in AH, not AL! So:
...
I will try to fix in the morning, thanks.
Jeremy
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for
Eduardo Casino wrote:
Hello All,
This patch adds support for int 2F122B (Internal IOCTL) and int 2F122D
(Internal Get Extended Error) to kernel.
Those are necessary for the upcoming new version of NLSFUNC to work with
DISPLAY 1.0.
Regards,
Eduardo.
Thank you, committed.
Jeremy
[EMAIL PROTECTED] escribió:
Send Freedos-kernel mailing list submissions to
freedos-kernel@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
or, via email, send a message with subject or
Arkady V.Belousov wrote:
Hi!
30-Ноя-2005 21:59 [EMAIL PROTECTED] (Kenneth Davis) wrote to
[EMAIL PROTECTED]:
+++ sys.c 30 Nov 2005 21:59:18 - 1.41.2.21
-extern int VA_CDECL printf(const char * fmt, ...);
-extern int VA_CDECL sprintf(char * buff, const char * fmt, ...);
+extern
On Sun, 20 Nov 2005, Kenneth J. Davis wrote:
The reason for these -zu compatible fixes is that in cases where SS is not
the same as DS (DGROUP) certain calls behave oddly, such as printf, since the
compiler is passing an offset on the stack where it assumes DS==SS so the
function receiving
Arkady V.Belousov wrote:
Hi!
20-Ноя-2005 16:57 [EMAIL PROTECTED] (Kenneth Davis) wrote to
[EMAIL PROTECTED]:
--- NEW FILE: intwrap.asm ---
reloc_call_int13_handler:
cli ; disable other interrupts for now
INT instruction already disables IFlag.
stc ;
Hi!
20-Ноя-2005 13:50 [EMAIL PROTECTED] (Kenneth J. Davis) wrote to
freedos-kernel@lists.sourceforge.net:
int13iret:
inc sp ; clean up stack
inc sp
sti ; ensure int's are renabled
retf 2 ; return to caller leaving flags asis
I don't think that
301 - 400 of 1070 matches
Mail list logo
