Hi!
6-Ноя-2005 19:05 [EMAIL PROTECTED] (Kenneth J. Davis) wrote to
freedos-kernel@lists.sourceforge.net:
KJD fix ATAPICDD, so a year or two down the road) is a replacement for the
KJD BIOS int 13h. How does the ontrack and such software work so DOS
KJD doesn't overwrite them?
They move
Arkady V.Belousov wrote:
...
+cmp word [_OemHook21], -1
+je no_oemhndlr
+cmp word [_OemHook21+2], -1
+je no_oemhndlr
This is if (FP_OFF (OemHook21) != -1 FP_SEG (OemHook21) != -1),
which is not equal to if
Hi!
6-Ноя-2005 17:44 [EMAIL PROTECTED] (Kenneth J. Davis) wrote to
freedos-kernel@lists.sourceforge.net:
+jmp far [ds:_OemHook21] ; invoke OEM handler (no return)
Looks like bug: if before ds=cs:_DGROUP_ DS doesn't contains segment
of _OemHook21, then it willn't contain
The main issue with FreeCom would be the location of its resources
changing. As long as the comspec env variable still pointed to the same
(or an identical) copy of the strings, it would probably be ok, but
honestly I don't know if FreeCom closes/opens or keeps open the file
with its
Hello Kenneth,
The main issue with FreeCom would be the location of its resources
changing.
under normal circumstances, FreeCom-xmsswap will have it's resources
loaded at startup and touch them never again.
Tom
---
This SF.Net email is
Eric Auer schreef:
Hi, yes, FreeCOM can handle changing drive letters. The PROBLEM
is that harddisk letters are handled by a kernel driver which
can only do one hole-free range of drive letters. So if you
could enable a new partition on the fly, all subsequent drive
letters would move. HOWEVER,
firstly, I never said FreeCom couldn't handle drive letter changes, I
said if one did something, then they need to make sure it can; in
particular the way it loads strings; although from my experience not
being able to load its strings usually just results in FreeCom issuing
useless messages
Hi!
20-Окт-2005 00:42 [EMAIL PROTECTED] (Bernd Blaauw) wrote to
freedos-kernel@lists.sourceforge.net:
style driver which MOUNTS an arbitrary FAT partition: You only
BB except it cannot re-assign already used driveletters I guess. Same as
There exists utilities, which swaps drive letters
Hi,
Very very nice discussion, I am enjoying this a lot, thanks!
Kenneth J. Davis escribió:
various details like that. And really if you wanted to be clever,
maintain the needed information about open files and TSRs won't even
notice the change, even if the file is now on a different drive
I've considered this in the past, but the consensus seems to be that it
is best just to reboot. It is possible to assuming no TSRs are loaded
that would be confused by such action, but if done in the kernel it
would involve leaving normally init time (hence transient so does not
normally
Hi!
18-Окт-2005 13:48 [EMAIL PROTECTED] (Daniel Breest) wrote to
freedos-kernel@lists.sourceforge.net:
DB The question is: is it possible to trigger the freedos kernel to reread
DB the partition table and reassign drive letters from within a running
DB freedos.
No. Code, which recognizes
Development kernel + country.sys should work.
Available at www.fdos.org/kernel
http://fdos.org/AutoIndex/index?dir=kernel/file=kwc8632.dev.zip
http://fdos.org/AutoIndex/index?dir=kernel/file=COUNTRY.dev.SYS
Thanks a lot for the links.
or more probably contains a slight error.
Hi!
20-Сен-2005 21:52 [EMAIL PROTECTED] (David O'Shea) wrote to
freedos-kernel@lists.sourceforge.net:
DO Could we not just initialize 26 but still make the memory for the
DO unused ones E: available after the drivers are loaded?
It is.
cstarter wrote:
%define bsOemName bp+0x03 ; OEM label
%define bsBytesPerSec bp+0x0b ; bytes/sector
%define bsSecPerClust bp+0x0d ; sectors/allocation unit
%define bsResSectorsbp+0x0e ; # reserved sectors
%define bsFATs bp+0x10 ; # of fats
Hi Florian,
What is ... supposed to be?
Aitor
Florian Xaver escribió:
Hi!
Another idea: Why not including ... ? I am using 4DOS very often, and
am happy with it. I mostly don't need more points :-)
Bye, Flo
---
SF.Net email is
Hi!
Another idea: Why not including ... ? I am using 4DOS very often, and
am happy with it. I mostly don't need more points :-)
Bye, Flo
Eric, I have uploaded a test kernel [stable branch] for you to try.
http://www.fdos.org/kernel/test/kernel.eric.sys
It implements the two items you
Eric Auer wrote:
...
struct dhdr FAR *IsDevice(const char FAR * fname)
has a problem here. But why does that only happen with DEVLOAD?
...
I hope there are still some readers on the kernel list and we
can move the further discussion to that list. A fix should be
quite straightforward: 1. .
Eric Auer wrote:
...
So your kernel is still not immune to the problem entirely - it still
somehow uses names of block device drivers even though those names
are optional and not even related to file name processing at all.
I will have to check and see if there are other references in the
Салям!
1-Июл-2005 18:17 [EMAIL PROTECTED] (Steve Calfee) wrote to
freedos-kernel@lists.sourceforge.net:
SC Hi I found a bug. We discussed it on alt.os.free-dos and
for dos files, if it finds it it uses fdconfig.sys. Apparently, if it
does not find the dos file it uses neither config.sys or
Before invoking build.bat, at the command prompt does directly invoking the
Borland tools work? ie does tcc, make, and tlink all execute or give you bad
command or filename error? If not, then your path is not setup correctly,
please add it (eg set PATH=c:\tc101;%PATH%).
Also, is the kernel
Hi,
tom ehlert escribió:
Hello Eric,
While we are at it, I would suggest a new category not planned at all
unless you tell us why it is useful or alternatively send us patches
for the list: http://fdos.org/ripcord/fdos_1_0/official/post.htm
Bad idea: I unsupport this. If you don't
Hi!
12--2005 05:03 [EMAIL PROTECTED] (Eric Auer) wrote to
freedos-kernel@lists.sourceforge.net:
EA DOS3.x+ 32bit sector number calls) and 2048 byte (raw sector size
EA on CD-ROM and maybe on magneto-optical drives) cases.
AFAIK, CD-ROM sector is 2352 bytes.
EA - To support bigger sectors,
Hello Eric,
While we are at it, I would suggest a new category not planned at all
unless you tell us why it is useful or alternatively send us patches
for the list: http://fdos.org/ripcord/fdos_1_0/official/post.htm
Candidates are: drivparm / driver sys / 3rd floppy support (kernel, sys...),
Hi!
13--2005 15:38 [EMAIL PROTECTED] (Eric Auer) wrote to
freedos-kernel@lists.sourceforge.net:
The more so, does anyone
contains resources (devices), where non-standard sectors support may be
EA YES, big question!
Main question!
Hello Eric,
Comments about useful sector sizes would be welcome:
Smaller (64, 128, 256), normal 512, Bigger (1024, 2048, others).
512.
Thanks for your comments! Trying to wake up the kernel list a bit :-)).
add code to support dynamic disks.
Tom
!
24--2005 16:02 [EMAIL PROTECTED] (Eric Auer) wrote to
freedos-kernel@lists.sourceforge.net:
(Other questions already answered by Bart).
EA - there are I186 and I386 defines which are only used in inthndlr.c
EA and main.c, but I have the feeling that you get better consistency
EA by
Abrahan Sanjuas schreef:
Is this feature missing on FreeDOS?
if BIOS has support, DOS supports it.
you might need the UDMA2.SYS driver for really large harddisks though.
Bernd
---
SF.Net email is sponsored by: Tell us your software development
On Sun, 24 Apr 2005, Eric Auer wrote:
Things that I found:
- there is an I86 define which is triggered for most (all?) known
compilers and which activates some Turbo C / ... style syntax
in some places. See portab.h and grep for I86 in kernel/*. and
tell me WHY we have I86 at all.
Jeffrey Chao schreef:
I use sys config kernel.sys bootharddiskseconds=5 to configure the
freedos kernel.
Then I use this freedos as floppy image to burn a bootable CD.
Then:
what kind of bootloader is used on the cdrom, or what type of emulation
does the cdrom use for diskette?
Config:
IDE
@lists.sourceforge.net
Subject: Re: [Freedos-kernel] kernel question
Date: Fri, 15 Apr 2005 08:05:53 +0200
Jeffrey Chao schreef:
I use sys config kernel.sys bootharddiskseconds=5 to configure the
freedos kernel.
Then I use this freedos as floppy image to burn a bootable CD.
Then:
what kind of bootloader
Oops ... should have checked that more closely before posting. Eric is
not the maintainer, of course. I've moved Eric's 1.02f into a subdir on
ibiblio, and I'll try to reach Raster to see if this can become an
official release of 1.02f.
-jh
Jim Hall wrote:
Eric,
I've mirrored your DELTREE
Hello Geraldo,
is possible to implement a virtualfilesystem layer on
freedos kernel?
it has already: the network redirector interface.
what do you think about create a hardware abstraction layer
on freedos kernel?
it is interesting to make freedos portable to others
architectures
it has
Hi!
7--2005 04:58 [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote to
freedos-kernel@lists.sourceforge.net:
jo I assume you are pointing out the use of hiword loword versus what I used
jo I did this for two reasons, the 1st is that those macros are not in the
jo stable kernel's portab.h, so using
Hi!
16--2005 18:56 I wrote to freedos-kernel@lists.sourceforge.net:
AVB if (mode != LARGEST (mode ALLOC_HIGH_LOW)
AVB instead
AVB if ((mode != LARGEST) (mode FIRST_FIT_U)
And see the difference: this code checks for HIGH_LOW strategy, but
original source reuses FIRST_FIT_U name, thus
Does this fix the DOSLFN problem reported here?
http://www.geocities.com/jadoxa/doslfn/index.html
-
FreeDOS has a problem with extended DPBs, which causes problems with
XMSDSK (DOSLFN thinks the RAMdisk is FAT32). It also does not support
the Set Extended Error function, which causes
Arkady V.Belousov wrote:
Hi!
17--2005 18:34 [EMAIL PROTECTED] (Kenneth Davis) wrote to
[EMAIL PROTECTED]:
tc debug build fix
+++ task.c17 Jan 2005 18:34:10 - 1.44.2.5
-#if DEBUG
+#ifdef DEBUG
__O\_/_\_/O__
#if TST
# error
Hi Bart (are you around?)
Thanks this worked fine (it took some time to test)
Alain
PS: you are getting good at reading minds ;-)
Bart Oldeman escreveu:
On Thu, 6 Jan 2005, Alain wrote:
Peter Fedorow escreveu:
OmmitIfOptimizeSize break ();
Has anyone managed to make this construct qork with
Hi!
19--2005 15:06 [EMAIL PROTECTED] (Kenneth J. Davis) wrote to
freedos-kernel@lists.sourceforge.net:
+++ task.c17 Jan 2005 18:34:10 - 1.44.2.5
-#if DEBUG
+#ifdef DEBUG
Fix:
#if TST+0
---^^
KJD I'm confused.
KJD How does #ifdef DEBUG (the new code)
Oops... :( Sorry, I'm
Hi!
6--2005 23:47 [EMAIL PROTECTED] (Peter Fedorow) wrote to
freedos-kernel@lists.sourceforge.net:
OmmitIfOptimizeSize break ();
Very hard to justify such macros, then you may as well use a comment, the
potentially nasty fallthrough would still be there in the embedded case.
PF A macro
Hi!
6--2005 15:11 [EMAIL PROTECTED] (Eric Auer) wrote to
freedos-kernel@lists.sourceforge.net:
EA If you REALLY want to change the FreeDOS kernel in an impressive way,
EA then remove that far f_nodes. This will improve compatibility, size,
EA and (maybe not at once, but it still) stability.
Thanks all for the information.
As everyone probably already knows, I have a similar background to
Jeremy, with similar constraints. Here at HP, I now work on Linux
clusters and we've been delivering products at an unprecedented rate.
The cost is employee free time, as I typically put in 60+
Hello Alain,
Tuesday, January 11, 2005, 1:24:48 PM, you wrote:
Arkady V.Belousov escreveu:
Hi!
4--2005 19:05 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
Fix divide error message text
+++ entry.asm 4 Jan 2005 19:05:08 - 1.27.2.2
-; print a message
Hi Tom,
Arkady V.Belousov escreveu:
Hi!
4--2005 19:05 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
Fix divide error message text
+++ entry.asm 4 Jan 2005 19:05:08 - 1.27.2.2
-; print a message 'Interrupt divide by zero'
+; print a message 'Interrupt divide error'
Arkady V.Belousov wrote:
Hi!
31--2004 21:37 [EMAIL PROTECTED] (Kenneth Davis) wrote to
[EMAIL PROTECTED]:
use NT OW binaries on NT, add access to more options from build cmd line
+++ defaults.bat 31 Dec 2004 21:37:51 - 1.1.2.6
+set BINPATH=%BASE%\bin
+if %COMPILER% == TC set
Hi!
11--2005 12:19 [EMAIL PROTECTED] (Pat Villani) wrote to
freedos-kernel@lists.sourceforge.net:
PV With all the unstable versions and private branches going around,
1. official 2035.
2. tom's stable fork (not very known).
3. Mine/Lucho unstable fork.
4. Kenneth tree, which is compomise
While I can reproduce this bug with the indicated kernel revision, it
does not
appear to be a current problem. Can anyone reproduce with the current
kernel? Did anyone already fix this or are we possibly still corrupting
memory, just a different location now?
Thanks,
Jeremy
...
version 1.1.35w
Kenneth J. Davis wrote:
Jim Hall wrote:
I'm forwarding this for Wengier. Since the current FreeDOS kernel
seems incompatible with this version of GRUB for DOS, I'm not sure if
I should post a note about it on the FreeDOS web site (I'm concerned
that too many avid Linux/Windows/FreeDOS
Hi!
5--2005 22:59 [EMAIL PROTECTED] (tom ehlert) wrote to Eric Auer
freedos-kernel@lists.sourceforge.net:
te and while I agree completely with what he wrote, IMO he slightly
te missed the point (and you -eric- miss it completely)
The whole point is that if you remove the break; completely, then
Hi Tom,
the whole point is that in a shared programming effort (as the freedos
kernel still should be) it's a waste of resources to change ANYTHING
without a certain payback.
Lucho's payback is clear. He compiles with Borland C and compresses the
result, so that the *compressed* kernel fits
On Thu, 6 Jan 2005, Alain wrote:
Peter Fedorow escreveu:
OmmitIfOptimizeSize break ();
Has anyone managed to make this construct qork with OpenWatcom?
We (me and Andreas) have run across this issue for debug macros and the
/##/ construct aparently does not work. We would
That's really bad practice. The reason that it's there is so if, by
reason of a bug or hardware failure of any sort, return_user() does
really return, you will have bug that will be a nightmare to find. For
the savings of less than 10 bytes, it's not worth the risk.
Pat
Arkady V.Belousov
Hi!
5--2005 08:30 [EMAIL PROTECTED] (Pat Villani) wrote to
freedos-kernel@lists.sourceforge.net:
+++ inthndlr.c31 Dec 2004 12:46:21 - 1.87.2.13
return_user();
- break;
I think, for readability purposes (to make understanding by new
developers easier) `break'
Hi Arkady,
The - in the diff says that the break is removed entirely. Did you
actually mean this, given your reply?
I think you do save 2 or 3 bytes per break, depending on the compiler.
However, I can relate to you an amusing experience. At one time, I did
some consulting for Bell Labs. A
Hi!
5--2005 09:19 [EMAIL PROTECTED] (Pat Villani) wrote to
freedos-kernel@lists.sourceforge.net:
PV The - in the diff says that the break is removed entirely. Did you
PV actually mean this, given your reply?
Yes. Break is removed, but later some new developer may wonder, why
there are no
Eric Auer schreef:
PS: Which kernels contain the DOSLFN compatibility patch (improved
xBPB/DPB initialization and set extended error code implemented),
only the development kernels at www.fdos.org/kernel, I think. Jeremy has
been active lately. Only thing missing by default is that IF a
Hello Eric,
Hi guys, interesting anecdote from Pat, but:
yes, it was interesting to see Pat watching this list at all.
and while I agree completely with what he wrote, IMO he slightly
missed the point (and you -eric- miss it completely)
The whole point is that if you remove the break;
Bernd Blaauw wrote:
Jeremy, the -dev kernel is BROKEN.
Try booting, and then SET FOO=BAR
...
This is fixed in current cvs. The problem was that the
DOS int21h function 4A, resize block, is called by
FreeCom to resize its initial environment to size
requested by the /E: option. For a brief
Hi!
30--2004 00:35 Arkady V.Belousov wrote to
freedos-kernel@lists.sourceforge.net:
Remove hack in Int 21h AH=38h, revert bad change in _CmdInstall
+++ inthndlr.c29 Dec 2004 19:27:31 - 1.87.2.11
- rc = DosGetCountryInformation(cntry, FP_DS_DX);
- if (rc =
Yes, I saw it after looking at the updated shsucdx, and
Lucho has already committed it to the development branch.
It will make it into the stable branch on my next merge
from dev to stable (which probably won't be until after
Christmas as I'm visiting my folks and won't have access
to my
Hi!
23--2004 02:04 Arkady V.Belousov wrote to
freedos-kernel@lists.sourceforge.net:
AVB Ok. First, call presence/missing doesn't affect calls throug
AVB makefile, call affects execution only througb batch files. Second, you
AVB may just remove check on Close window on program exit option.
On Tue, 30 Nov 2004 13:34:26 +0100 (MET), Eric Auer [EMAIL PROTECTED] wrote:
Hi, you are not the first one who is planning FreeDOS ports for embedded x86:
http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=incoming/277
This FAQ entry contains a detailled description of the needed
On Tue, 30 Nov 2004 13:44:33 +0300 (MSK), Arkady V.Belousov
[EMAIL PROTECTED] wrote:
Hi!
30--2004 02:31 [EMAIL PROTECTED] (9000 VAX) wrote to
[EMAIL PROTECTED]:
9V I am developing a hobby project where freedos kernel might be a nice
9V fit. There are CPU (80188), memory (256K, 512K, or
On Tue, 30 Nov 2004 13:34:26 +0100 (MET), Eric Auer [EMAIL PROTECTED] wrote:
Hi, you are not the first one who is planning FreeDOS ports for embedded x86:
http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=incoming/277
This FAQ entry contains a detailled description of the needed
On Thu, 18 Nov 2004, Arkady V.Belousov wrote:
Of course, qsort() if very fast algo (except some specific cases, when
it is O(N^2)), but why to do _any_ extra action, when unnecessary? :)
Especially, I suggest, (most) linkers do own sorting anyway?
I think even bubble sort would be fast
Hi!
20--2004 18:54 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
Hm. I think for simplicity and safety, exeflat should itself move
relocation table from executable's header inside executable itself, so that
it may be reused by MoveKernel(). This allows to eliminate manual
On Sat, 20 Nov 2004, Arkady V.Belousov wrote:
Yes, and then now may be reduced code duplication in asmsupt.asm (which
generated both for transient and resident portion).
only for Borland C. For Watcom they are not duplicated (only one CS:
there). And anyway it's only a small amount of
On Thu, 18 Nov 2004, Arkady V.Belousov wrote:
Small optimization: because BC doesn't knows, that exit() doesn't
returns, better to insert explicit return 0; after exit() or return error
code through return (remaining error handling for main()). For BC, this
allows to join common tails.
Hi!
18--2004 21:21 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
Small optimization: because BC doesn't knows, that exit() doesn't
BO I don't think optimizing exeflat.exe's size is very important though ;)
Sure. :) But why not make more optimal code from scratch in any
Hello Arkady,
Small optimization: because BC doesn't knows, that exit() doesn't
BO I don't think optimizing exeflat.exe's size is very important though ;)
Sure. :) But why not make more optimal code from scratch in any case,
without thinking will this code often used?
And why not
Hi!
18--2004 11:24 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov
[EMAIL PROTECTED]:
te And why not leave *existing* code as is - without wasting mental and
te ethernet bandwidth on it ?
This is not (yet) existing, this is _new_ code.
Especially, I suggest, (most) linkers do
Hi!
29--2004 17:36 [EMAIL PROTECTED] (tom ehlert) wrote to Eric Auer
[EMAIL PROTECTED]:
Hi, Steve reports that while things were fine in kernels
2030 ... 2033 (both with and without FAT32 support), kernel
2034 WITH FAT32 support and all 2035 kernels fail to read
the (fd) config sys file when
Hi Bart,
good to see you alive and around :)
http://freedos.sourceforge.net/kernel/exeflat.c
(the file is smaller than the diff would be)
there are probably a couple of changes to makefiles batches ?
To use it you need to change the makefile to remove the explicit UPX call:
this call is
Hi Tom,
http://freedos.sourceforge.net/kernel/exeflat.c
(the file is smaller than the diff would be)
there are probably a couple of changes to makefiles
batches ?
just remove that upx call in makefile.
To use it you need to change the makefile to remove the
explicit UPX call: this
Hi!
16--2004 11:13 [EMAIL PROTECTED] (Fab) wrote to
[EMAIL PROTECTED]:
F I'm trying to use a compact flash under FreeDos as removable media.
F The problem is that the compact flash *must* be present into the card reader
F (interfaced onto the IDE bus) otherwise the BIOS POST do not recognize the
Hi!
9--2004 21:14 [EMAIL PROTECTED] (Karthigan Srinivasan) wrote to
[EMAIL PROTECTED]:
KS me with this question. Based on the kernel makefiles I wrote a simple C
KS and asm file and tried linking them.
There are no reasons to do this, because kernel memory model very
specific.
KS It warns
ADE If so, where can I get it?
AFAIR, www.delorie.com?
For the OP, the DOS version is http://www.delorie.com/djgpp/
-jh
--
_
I'm sorry my president's an idiot. I didn't vote for him.
Hi!
9--2004 21:14 [EMAIL PROTECTED] (Karthigan Srinivasan) wrote to
[EMAIL PROTECTED]:
KS me with this question. Based on the kernel makefiles I wrote a simple C
KS and asm file and tried linking them.
There are no reasons to do this, because kernel memory model very
specific.
KS It warns
Hi there,
The basic reference would be the original book by Pat Villani.
There is the little problem that the kernel has grown too much ever since. Time
ago I had been reading the kernel sources, as much as to get an idea on how it
works.
I planned to create some block diagram, but didn't
Hi!
10--2004 15:47 [EMAIL PROTECTED] (Allen D. Evans) wrote to
[EMAIL PROTECTED]:
ADE I enjoy frustration and would like to compile my own version of FreeDOS.
ADE Does a DOS/Windows have a GCC compiler?
Yes. There is a Win32 implementations of GCC and there is DOS version
of GCC (DJGPP).
Karthigan Srinivasan wrote:
...
am kind of lost. Is there any documentation of on
the kernel source. I am new to OS programming and
...
The only documentation that I am aware of is:
The FreeDOS Kernel book by Pat Villani, the comments
in the source, the Topica Sourceforge fd-kernel archives,
and
Hi!
6--2004 16:13 [EMAIL PROTECTED] (tom ehlert) wrote to
[EMAIL PROTECTED]:
te From: Jose Antonio Senna
te ===8==Original message text===
te Excuse me for sending this directly to you, but I am still unable to post
te on Freedos lists.
te I do not know who (if anyone)
On Sat, 6 Nov 2004, tom ehlert wrote:
However,FreeDOS hooks INT 13
No, if anything hooks INT 13 it could be LBACACHE but the kernel does not
(it should but for different reasons -- see int2f/ah=13 in RBIL).
how are these disks/BIOS variants detected ?
I have a faint memory of these
Hi!
7--2004 09:24 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
BO My 386 SX only had 80 MB hard disk space, which was far below the
BO first problematic barrier of 1024*16*63*512=512MB
1024*16*63*512=504Mb (or 528 Mb, as this counted by disk
manufacturers).
The simple fact is that the f_nodes structure is not needed at all.
Before I left the group several years ago, I was planning to rewrite the
kernel specifically to eliminate f_nodes and move to SFT. The reason
was precisely the incompatibility between this kernel and other programs
such as
Hi Eric,
I don't know what an f_node is, but you have received 4 replies from:
- James (former kernel maintainer)
- Bart (former kernel maintainer)
- Tom (former kernel maintainer)
- Pat (former kernel maintainer and original kernel author)
I just wanted to add myself :-))
Ciao
P.S.: If you
It's the original data structure used for file systems. It was designed
originally as a structure that contained a semaphore, file system type
identifier, and a union for file system data. It was simplified for the
original DOS-C/FreeDOS kernel, and changes have been made by myself and
the work before Eric sets about to it.
Aitor
- Mensaje Original -
Remitente: Pat Villani [EMAIL PROTECTED]
Destinatario: [EMAIL PROTECTED]
Fecha: Martes, Noviembre 2, 2004 3:00pm
Asunto: Re: [Freedos-kernel] unused SFT fields - f_nodes not needed???
The simple fact
Roberto Mariottini wrote:
Hi Eric,
I don't know what an f_node is, but you have received 4 replies from:
John Price (former kernel maintainer)
- James (former kernel maintainer)
- Bart (former kernel maintainer)
- Tom (former kernel maintainer)
- Pat (former kernel maintainer and original
On Tue, 2 Nov 2004 [EMAIL PROTECTED] wrote:
So there is the problem to estimate the size of the code:
- changing references to f_nodes from near to far (thus with a segment prefix)
about 1300 bytes. It's not just segment prefixes; lots of pointers get
passed around. They're really quite
Hi,
Eric Auer wrote:
Hi, I tried to check SFT compatibility of FreeDOS, quick conclusion:
sft_dcb is never accessed
sft_stclust is never accessed
sft_relclust is never accessed
sft_cuclust is never accessed
sft_dirdlust (sic!) is never accessed
sft_diridx is never accessed
sft_bshare is never
Hi Eric,
Is that correct? I think SFT-messing programs like Windoze will not be
happy in particular about all those uninitialized cluster values, the
missing DCB pointer, and missing dir entry info. The share / ifs stuff
is probably less interesting or set by SHARE / IFSdrivers directly,
Hello Eric,
Hi, Steve reports that while things were fine in kernels
2030 ... 2033 (both with and without FAT32 support), kernel
2034 WITH FAT32 support and all 2035 kernels fail to read
the (fd) config sys file when booting from floppy.
*ALL* kernels 2023..2035BTom boot from 1.44 floppy,
Hello Eric,
Hi, I exchanged some mails with Udo from DR DOS improvement project,
and the conclusion might be that FreeDOS is not missing much for 386Enh
compatibility - it only has one thing too much: fnodes.
From what follows, it real seems to be easy to make FreeDOS Win3.1
compatible.
So
On Mon, 11 Oct 2004, Eric Auer wrote:
http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=incoming/321
tells: If not ALL buffers fit into HMA, then ALL buffers will be in
low DOS memory. How hard would it be to put MOST buffers in HMA and
only the REST in low DOS memory, if many BUFFERS
Hi Jeffrey,
actually the kernel tries to finish CD harddisk emulation
before booting from HD (main.c, EmulatedDriveStatus)
unfortunately this doesn't seem to work (in your case, with your CD
burning software,...)
tom
---
This SF.net email
Jeffrey Chao schreef:
After booting into Windows, I can see there are two floppy drives in
Windows Explorer,
but I just have one floppy drive connected. Does anyone ever faced the
same issue as me?
A: is the emulated floppy drive (the floppy image and/or diskette you
provided for bootable
Hi!
22--2004 11:11 Arkady V.Belousov wrote to
[EMAIL PROTECTED]:
AVB I may suggest next patch:
Sorry, forget about undocumented COMMAND:
__O\_/_\_/O__
diff -ruNp old/config.c new/config.c
--- old/config.c2004-04-14
Eric Auer wrote:
Hi!
If it is broke in stable and fixed in dev, then it should
be fixed in head soon. Please people, the kernels are not
Lucho/Arkady vs Tom/..., they are stable and development (unstable).
Well I can only give people the Lucho or the SF homepage URL if
they want a kernel
Hello Eric,
- Tom has added only the best few lines of the Lucho / Arkady patches,
those which OBVIOUSLY fix bugs, but will have missed several bugfixes
which were hidden between optimizations
that might have happened.
But for sure I missed some bew bugs hidden between optimizations.
-
Eric Auer wrote:
Hi, after a while we found that only the Lucho / Arkady kernel
has working VERSION=, ...
If it is broke in stable and fixed in dev, then it should
be fixed in head soon. Please people, the kernels are not
Lucho/Arkady vs Tom/..., they are stable and development (unstable).
...
401 - 500 of 1070 matches
Mail list logo
