Hi Arkady!
I think it is at most a very small bug if the boot sector falls off the end
of the root directory if it has no entry which starts with 00 at the end.
As long as the KERNEL does not have such a bug... (checks for end-of-chain
in FAT32 or root dir size in FAT1x case before trying to use
Hi, about the DOS uses 'int' 0x25/0x26 as CALL FAR, so you have to POPF
when you call it through INT thread:
Several compilers TRANSPARENTLY handle this. I think DJGPP is among them.
If you try to use the 25/26 ones through int, it will automatically
use DJGPP. Borland Turbo C has the absread()
Hi Arkady!
EA use DJGPP. Borland Turbo C has the absread() and abswrite() functions to
EA do the access -
Firstly, these functions present only in BC (and TC?). Secondly, I
already quote RBIL, which says, that BC' absread()/abswrite() (which detects
size of partition through INT21/1C)
Hi, now that Arkady has shown us that BC auto-selects absread style
for 32 MB / 32 MB, while TC does not: I have to conclude that
compiling my UNDELETE will only work in Turbo C, not in Borland C.
Because UNDELETE manually creates a 32 MB style access structure,
assuming that absread() is not
Hi Arkady, for FAT32 drives, WinDOS returns on int 21.32 (get BPB),
when you use it as get default BPB, that:
- root dir size would be 512 entries
- FAT1x size would be as FAT32 size
- ...
- so you have to notice aha, FAT so big that it must be FAT32 and
use the FAT32 call then. Or even better,
Hi, here the thing again inline for easier discussion (result file
from previous mail):
Default BPB for drive X: according to Bootfix 1.1 by Arkady:
512 by/sec, 4 sec/clust, 1 boot sector, 188 sec/fat, 2 FATs,
0 / 195016 sectors, 0x.f744 hidden sectors (this is the
partition position, looks
Hi, I think we should be able to boot from ZIP FAT32 if BIOS can boot
from it as a normal int 13h device. After all, default BPB = FAT16 while
actual BPB = FAT32 does NOT mean that FAT32 is generally broken. It only
means that the partition table is wrong and marks the partition as FAT16.
Hi, about add_far() pointer normalization: I think it would be
better to normalize earlier. If you have a pointer, you normally
have a pointer to a STRUCTURE. If the end of the structure ends
up with an offset 0x then having the POINTER normalized is
not enough. So how do you check the SIZE
Hi, in the FAQ, somebody claims that file handle 4 should default to PRN:
http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=incoming/224
Any idea why this would work at all? And why it works in MS but not in
FreeDOS? Used language is C.
Eric.
Hi, I would like to spread some fear, uncertainity and distrust
about EBDA movement!
For explanation, in 2032+ kernels, this is enabled by default.
You can suppress it with SWITCHES=/E in your config sys file.
Some time ago, I noticed that UPX would sometimes create broken,
truncated,
Hi Bernd,
I am not doing anything to the To: field... Whatever:
still not clear if CALLVER can be implemented into FreeCOM:
CALL /V:x.yz program /options
Should not be hard to do, I think. But would be a bit off topic.
CALLVER requires FreeCOM anyway, instead of patching MSDOS version
Hi Arkady,
why did you only mention in THIS mail what the MEANING of your patches
is? You normally send a mail with subject like patch: filename.c and
then there is ONLY the patch, zero explanation of any kind, nobody except
you will know what you are trying to tell us and why your patch is
Arkady,
you really never learn it, do you?
You optimized less than 0x10 bytes but you sent a diff of probably
far more than 100 lines. Most changes involve removing comments, changing
indendation, replacing code like foo = bar; if (foo == ...) by
code like if ((foo = bar) == ...) which is less
Hi, while we have no real kernel maintainer right now (I assume Jeremy
can at most find enough time to upload patches submitted by others, not
for doing coding / testing himself), I think it would be good to review
some old bugs before we move on to do new optimizations. Of course now
that Arkady
Hi Justin, thanks for your help offer!
Win 3.11 can only run in 386 multitasked mode, which requires extra
kernel support e.g. in the int 13 handler and in some int 2f functions
for managing the int 13 handler and related. So it is no surprise
that Win 3.11 does not run. HOWEVER, it would be
Hi Arkady!
EA * 698 floppy change / floppy DMA boundary check should be moved from
EA int 25/26 to the int 13 handler.
Hm. Probably I not very understand this request, but FreeDOS does all
DMA checks in dsk.c:LBA_Transfer().
Moving the check to int 13 means that DOS programs which
Hi Arkady!
The bug submitter for clear high parts of 32 bit registers on exec
claims to have experienced actual problems because of one program leaving
values in registers and another program assuming those parts to be 0.
However, he does not tell anything about which program is affected.
If it
Hi, forwarding a comment by Lawrence, maybe interesting???
Well, it happened in an older version of the GRDB
debugger. It has since been fixed.
By the way, I don't have time to investigate this now,
but while I have your attention, I noticed that when
the BIOS allocates an XBDA at
Hi Arkady!
(Clear high parts of 32bit regs...)
How this relates to DOS?
MS DOS basically had no 386 stuff at all (except EMM386). In FreeDOS,
however, people run 386 aware programs more often. Those leave non-zero
values in 32 bit registers when they exit, and the next program which you
Hi Aitor, Alain,
please ask Lawrence first if the MS DOS kernel clears the 32 bit
registers. I bet that it does NOT.
This is not related to is the program which breaks unimportant.
Arkady (hey, 3rd person with A..-name) told that this is a feature
wish and not a bug report and I think he is
Hi, I think idleness percentage is easier to understand for users than
time of using HLT versus total FDAPM loaded time
in general :-). Displaying TOTAL time is a bit complicated in NASM but would
be a nice extra (uptime display).
Only with the resident module you have an idleness percentage -
Hi Tom, Arkady,
- screen now cleared (white on black)
well - I IMPLEMENTED THE CONFIG MENU'S FIRTS TIME.
AND I ABSOLUTELY HATE IT IF OTHER ASSHOLES COMPLETELY CHANGE THE
BEHAVIOUR INTO A WIN95 GUI LIKE BEHAVIOUR.
Pretty asshole-style behaviour to insult each other on the list, mister!
Hi, using FREETEST and WHICHFAT and FORMAT, I found some wrong
kernel behaviour... Test setup: F: drive is 32.x MB diskimage
drive in DOSEMU. Kernel 2035-32, FreeCOM 0.82pl3 ... The other
tools can be found on my homepage.
Test:
debug (a recent version with FAT32 support, F: is FAT32!)
-lcs:100
Hi Arkady, Lucho,
nice cooperation if you ask me. Arkady writes the patches and Lucho,
hopefully, publishes:
- patches
- patched sources
- precompiled binaries
I think all three categories are needed. Patches, if people want to
merge them into the main branch (main? Tom? Confused...) eventually.
Hi Norm,
1. Is it possible to port FreeDOS to work on a journaling file system
like Reiser, Ext2/3, JFS, etc; ?
Not useful, sorry. Those high end file systems are not good for a 16 bit
kernel. You can use the DOS LTOOLS to copy data to and from ext2fs under
DOS, exactly as using MTOOLS
Hi, I still disagree...
I've taken a keen interest in embedded
technology over the past few months. I have some ideas that I have been
investigating over that period of time, what I have come to conclude
thus far is that Linux/Unix, while a perfect choice for multiuser
systems, is not
Hi Arkady, please UNFIX the environment then!
Seems to be a very bad idea that people get throw out of FreeDOS
after updating to your kernel just because they forgot to update FreeCOM
as well!
You could add a temporary
SWITCHES=/P
flag which would mean improve environment size - might be
Hi all, Arkady:
PLEASE do make FreeDOS 2035a behave as wrong as 2035, because
people will want to compare 2035a to 2035, and if things happen like
- you cannot format unformatted drives (disk access flag broken)
- stable version of FreeCOM (0.82pl3, as opposed to 0.82pl3xyz testing)
crashes
Hi, even though you now have an (0.82pl3w? Testing, unstable!)
FreeCOM, you STILL should waste those FEW BYTES in the environment
to maintain FreeCOM compatibility!
There is TRANSLATED FreeCOM, STABLE FreeCOM, DEBUGGING FreeCOM,
NON XMS SWAP FreeCOM, and possibly many other reasons why people
Hi, sorry, I swapped \0\0c:\\freecom.com with \0c:\\freecom.com then...
Anyway, if you waste 3 bytes to do:
A=B\0\0c:\\freecom.com\0
instead of
\0\0c:\\freecom.com\0
... then everybody will be happy!
By the way, FDAPM is looking for COMSPEC to know if it is run from
INSTALL. This should be
Hi, I took the effort to grep through the whole 2035 kernel sources,
to find divisions and modulo calculations. Some results:
* division/modulo macro should have an if x/512 then ... shortcut,
especially for older CPUs where division is slow. We often divide
by sector size, but without
Hi! I mean:
+ jcxz%%div3216 ; cx=0 - divisor 2^16
[ALL this code is NEVER reached in KERNEL now]
[So you can add some panic here, e.g. deliberately divide by zero...]
[...and then you have only he following left:]
+%%div3216:
+ cmp dx,bx ; xh y ?
+
Hi, I reduced the 500 line mail to 140 lines now... enjoy. Eric.
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
Hi, I reduced the 500 line mail to 140 lines now... enjoy. Eric.
lfn_inode: l_diroff offset could be an UWORD slot number, smaller
dmatch dm_size is LONG but should be ULONG
and dm_flags is not currently used. Note that the offsets in the
structure are fixed, so dm_flags is to be replaced
DosGetFree (FatGetDrvData int 21.1c/21.36) can crash, maybe because of
a NULL navc pointer.
If so, please submit some code to make the kernel crash.
if not, shut up.
I did. Read and shut up:
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/format/format-0.91r.txt
Maybe
Hi Arkady! Your patch is MUCH too long.
This is my (first) try to bugfix wrong INT21/1B, INT21/1C and INT21/36.
Sorry, tom, but there more than 1-2 lines of diff, and I doubt that this
diff may be (noticeably) reduced.
- bugfix: DosGetFree(): *navc was accessed (read and write) without
Hi all,
could you file the list of problems which are mentioned in this
thread as Bugzilla entries? I believe some RTM did work - and
Lucho found a very small binary patch to fix 32RTM - so Lucho,
please try to remember what you patched and why, thanks. This
might also be related to the used XMS
Hi, as suggested by Michael, I tried 386SWAT and would like to
recommend it for those who have no SoftICE at hand... some hints:
- 386SWAT loads as a device driver (quite small in DOS RAM)
- it debugs everything, including Win kernels / protected mode / ...
- it detects if you have 2 PCI/AGP VGA
Hi Lucho, Tom, ...,
TOM and so I won't touch the arkady branch with a 3 meter long stick.
L You already wrote this, but (1) I'd prefer the innocent presumption, to
the guilty presumption towards him, and (2) I think that accusing him
when he's absent to defend himself is not ethical.
In
Hi, I am having with the load saved game function of a jump and run game...
The game modifies the timer speed, hooks int 8, 9, 60, 61, 23 and 24,
calls functions (ax) 0..6 of int 60 (int 61 is used quite a lot but does
not seem to have function number in ax properties), uses functions 0 and 1
of
Hi Michael,
An unanswered question is are you able to successfully install Windows 3.1
itself over FreeDOS? Attempting to do so here aborts the install while it
is within the initial stages of running Windows after preliminary DOS file
copies on disk 1 and 2. There is a fatal general
Hi!
the code patterns which Windows 3.1 looks for that Eric
mentions will NEVER be there, nor should they be there, of course.
This depends a lot on WHY the patterns are searched / patched by
Win3.1 ... For example the mov ...,dx might be to make something
partially relocateable or to trap /
Hi, indeed an interesting problem... 32RTM fails to initialize CX
(number of words to copy from stack) before a DPMI call, and instead,
the CX of int 21.30 (get version) is used. So we need a version other
than 1.1.35 (major, minor, seq):
- lr.CH = REVISION_MAJOR; /* JPP */
- lr.CL
Hi Tom, Lucho,
INT 2F U - DOS 4.x internal - SET DOS VERSION NUMBER TO RETURN
AX = 122Fh
DX = DOS version number (h = return true DOS version)
note the 'internal', 'true version', and '4.x' ( not 4+ )
I'd recommend to implement setver in a reasonable fashion :((
I think
Hi, I have been thinking about an extra tool for LBAcache:
hook int 25/26 (or the FAT32 equivalent int 21.7xxx function, or all),
for ONE drive. That drive must not use int 13 BIOS disk access.
For all calls, call int 13 LBA functions, using the linear sector number
from the call and a fixed
About country sys: Do NOT copy it from another DOS. Our font (CPI) and
keyboard (KL/KEY/KC/whatever) packages show that we can do much better if
we collect the information ourselves, for the languages which are used by
FreeDOS people. I might even put up an online form like fill in: your
country
Hi Lucho!
Now our SYS stores 0 if the drive is A: or B: and FF in all other cases.
Then the boot sectors check if this value is FF and if so, use DL from
BIOS, else use the drive number from the boot sector.
...
someone decides to overwrite our boot sector later with a boot sector from
Hi, after PTS-DOS, the DR-DOS enhancement people have added an
option to put more data structures of DOS into UMB (I guess this
time we are talking about LoL / SDA). That way they get 626k of
640k low DOS RAM free after loading HIMEM/EMM386.
If you want to keep up with the game, we could add
Hi Jeremy, I vote for 2)
- use 0 or 80 only in the boot sector (or really any value the
user wants, but default to 0 or 80)
- the boot sector code has at a fixed location
useBIOSorNotFixedLocation:
mov [drive], dl
- SYS is then responsible for determining if BIOS
Hi, CALLVER is
http://www.coli.uni-sb.de/~eric/stuff/soft/specials/callver.zip
... and it does not support int 2f.122f nor int 21.33fc YET. If
the kernel has it, CALLVER will offer some set version to ...
until the next change functionality in a later version.
FREEVER source code got lost in
Hi Bernd and all,
I finally got internet again, so after spending this afternoon reading
about 300 emails I'm back again.
I noticed that :-).
DEVLOAD /H /Q ATAPICDD.SYS /D:FDCD0001
DEVLOAD /H /Q CDRCACHE.SYS FDCD0001 CDRCACH1 5
Oh boy... I still suggest using DEVICE, not DEVLOAD. The
Hi, after a while we found that only the Lucho / Arkady kernel
has working VERSION=, which reminds me that we have too many versions:
- outdated 2035
- Jeremy has added an unknown amount of patches to CVS HEAD 2035a, but
I have no idea if / how well those patches got reviewed and which bugs
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 BINARY. If I
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.
- DR DOS does not support int 2f.1603, so there is no ADDITIONAL instance data
- DR DOS supports
Hi Jeffrey, I think I can explain your symptoms...
Your bootable CD probably contains a boot floppy image. The BIOS
uses this image to simulate an extra floppy drive. You can check
the contents of the A: and B: drives to verify this. To avoid the
effect, create a bootable CD with help of
Hi!
te My computer BIOS INT 13 is able to access up to 4096 cylinders
te in a hard disk.
te by using bits 6 -7 of DH in INT 13 requests as bits 10-11 of cylinder
te number.
I remember having a 386 (NeAT mainboard) which had this kind of BIOS
feature. It means you can have 4k cylinders but
Hi, you do NOT have to write code to handle FAT filesystem.
You only have to EITHER convince the BIOS to access your CF disk
OR write some (relatively simple) code which can read and write
single sectors on the CF disk by accessing the IDE controller
directly.
The REST will be done by the
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 BIOS services
for the kernel. You can remove some of them by modifying the kernel a
Hi, I found that FORMAT and SYS need support for function
int 21.440d.0860 (for FAT32: int 21.440d.4860) to find out
the BPB contents. This function is not supported by ASPIDISK
when you use USBASPI4, and it is not supported by some RAMDISK
drivers. Other drives can be affected as well, maybe
Hi, I found out that SYS does not need the get default BPB call,
it just uses it as optional data source to adjust the BPB of the
already existing boot sector. However, FORMAT does need the default
BPB when formatting a not-yet-formatted disk.
The FORMAT problem with my USB flash memory stick,
Hi, Mohammed Sayed found out that kernel 2035a has a bug with
DELTREE - it does not allow it to delete directories. However,
RMDIR does work. With kernel 2035, everything works, so this
is a 2035a-specific bug. Confirmed by own testing in DOSEMU...
Hi, Lucho pointed out that DELTREE got error 5 because it had
code which does if OEM ID is 0FDh and CX is 0 or -1, then
explicitly exclude the DIR attribute when resetting file attribs
in preparation of deletion. This code is triggered by 2035a as
it sets CX to 0, which is needed by 32RTM DOS
Hi, I found that http://fdos.org/kernel/ 386-optimized kernels,
at least the CVS stable FAT32 one, crash iff you load EMM386,
after the EMM386 frame at display and before the next load Y/N
display of the kernel in F8 mode. Maybe you can have a look at
kernel.HEAD sources from the same homepage
Hi Arkady,
AFAIK, CD-ROM sector is 2352 bytes.
That would be the raw (cdda) sector size. For data (iso9660...) CD-ROM,
the useable sector size is 2048 bytes, rest is CRC/ECC overhead.
Eric, I suggest, non-standard sector size is not the hottest issue
(and, probably, will never be
Hi, as the KERNEL.dbgdev from fdos.org/kernel works for me in
DOSEmu, I could do some DEVLOAD CD .. problem debugging:
Unfortunately the debug output is very verbose and multi-line, so
I replaced media_check: no change by MC:ok and replaced
get_near_f_node and got near fnode by getfnode and got:
Hi Jeremy, that was quick...
quite straightforward: 1. . .. \ are all no device names and
2. dhp-dh_attr should be tested for ATTR_CHAR before comparing
the IsDevice input to dhp-dh_name.
Eric, I have uploaded a test kernel [stable branch] for you to try.
Hi, I think you can indeed introduce a compile time option like the DOSEMU
one (which makes put_console send output to int e6 function 13) to get
output to Bochs / QEmu specific interfaces. On the other hand, you can
just use DOSEMU :-).
I really recommend to use Bochs and the built-in debugger
Hi, Jeremy is right, FreeDOS boots in seconds, so it is best
to just reboot. Dynamic drive letter assignment is not what
DOS programs are used to cope with.
HOWEVER, useful aspects of re-read partitions would be:
- you can scan a PCMCIA disk after initializing the disk controller
- you can
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, you are free to
Hi Bernd,
I did not invent quickboot, fdapm hotboot just calls int 19
(load boot sector and run it). To make that work in real life,
you would have to have all interrupt vectors DOS free at the
moment, or at least some int 19 handler would have to be hooked
by everything which hooks boot-relavant
Hi, question about the kernel used in beta9sr2: When you boot
from beta9sr2 CD, a MEMDISK will simulate the A: drive, so
your normal drive would become B:. However, on computers without
actual diskette drive, FreeDOS seems to get stuck in some error
condition. Did the is DJ mechanism needed?
Hi, the short answer is: YES.
You can run FreeDOS on 8086.
is it possible that freeDOS work on an embedded system without BIOS?
The answer for that is longer. Searching for embed on
http://fd-doc.sourceforge.net/faq/cgi-bin/search.cgi
will point you to:
Hi, please assign version numbers 2036 and 2037 to the
last daily build CVS kernel stable and unstable versions...
That will make it a lot easier to refer to versions e.g.
in bugzilla. And people will be able to use VER to get a
hint of what version they are using :-). We have been
sitting with
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
Please make the XMS SWAP 186+ FreeCOM the one which is linked
at the Stable Kernel
Hi Bernd,
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
The core problem is that 2035w is not a version. It is the label
for the daily compile
Hi,
as Jeremy seems to be missing in action, could you tell me
who else can modify the fdos.org/kernel page?
I just downloaded the daily builds of several FreeCOM and
FreeDOS kernel packages and found several problems with
the web page, you could say.
1. kernel HEAD is featuring daily builds,
Hi,
I was wrong about item 2 of my mail: The link
http://fdos.org/kernel/command.com leads to a
classic FreeCOM 0.82pl3, build date 12/2003,
file date 1/2005, which uses XMS SWAP, supports
LOADHIGH but does not support LOADFIX... So:
The file is older than I thought but at least
it does support
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
Hi all,
I have a problem with FreeDOS unstable / Win386/WfW311 kernel,
the kernel which calls itself 2037 by now:
FreeDOS kernel version 1.1.37w (Build 2037w-UNSTABLE, Jun 29 2006)
(by the way, the 1.0 pre ISO of FreeDOS has a buggy FreeCOM LFN
thing, so either set LFN=N or update to the FreeCOM
Hi all, I found that the INSTALL(HIGH) of the winkernel
(2037 unstable with Win386 patches) is broken. It works
with kernel 2036. The test case is loading LBACACHE,
size 15000, with TUNS option (which allocates an extra
memory block in low memory when the cache itself is in
UMB). An interesting
Hi all,
Laaca writes that FreePascal works fine in FreeDOS 2036,
our stable kernel version. So far so good. 2036 rocks.
But FreePascal shows abnormal behaviour in FreeDOS
unstable / testing kernel version 2037. So if any
of you wants to figure out what is going wrong...
would be really nice.
Hi all,
I would like to draw attention to the fact that FreeDOS is
even still missing a few MS DOS 3.3x functions. So function
43ff (create directory / rename file, allowing path/file
names up to 128 rather than 67 bytes, allowing deeper nested
directories) should IMHO wait until the other stuff
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
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 all
... and happy new year :-)
I took some time to compare the current CVS stable / HEAD
kernel FreeDOS 2036 to the extra stable 2035c kernel
which is used by Tom. The latter is generally a bit older,
but also features some patches which have not yet found
their way into 2036. There are also
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 Frank,
you wrote that the Online Bible for DOS, which one
can download at http://www.onlinebible.net/dosolb.html
does not work in FreeDOS.
After some messing with dosemu and the built-in debugger
and interrupt trace functions of it, I figured out that
your problem is in DOS INT 21 function
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
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 /
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 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 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
Hi Bart, Arkady, other kernel people,
what do you think about the following problem:
We only have ONE scr_pos variable in the SDA but
several functions use it for several char devices
as far as I can tell. So tabstop calculation will
probably go wrong when you mix accesses to, say,
CON and AUX.
Hi Rugxulo, Robert, kernel people,
I finally figured out svn at home, so I updated three areas
of the stable branch of the FreeDOS kernel in svn. Actually
only UNSTABLE is a branch, stable is the default. Anyway.
The three changes vary a lot in complexity. Fixing language
glitches was easy. The
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.
Hi Bernd,
I have tested the new kernel a bit in Bochs already.
Sample kernel binary: www.coli.uni-saarland.de/~eric/ke2007jul21.zip
same filename yet updated release?
Yes, it was still 21jul :-). Updated kernel, kept kernel2.
Something else: Rugxulo tested the executable-unpacker IUP
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
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 all,
For the next file release of FreeCOM 0.84xyz and
kernel 2038 / sys, I would be happy if somebody
could figure out and fix the following problems:
- SUBST somehow breaks getcwd / chdir in the kernel??
- when you write a char dev, the kernel tries to read
it to detect ctrl-break,
1 - 100 of 186 matches
Mail list logo
