On Mon, Mar 5, 2012 at 2:13 AM, dos386 wrote:
...
>
> Minor SYS BUG (see shot): it fails to find KERNEL.SYS despite it's
> in there (it has "R" attribute). Suggestion for improvement:
>
> - read and report KERNEL.SYS attribs and size
> - if "R" then write "can't modify because read-only"
> - IF ((
On Tue, Feb 7, 2012 at 9:51 AM, Tom Ehlert wrote:
> Dear PerditionC,
>
> UBYTE DiskTransferBuffer[MAX_SEC_SIZE];
>
> wastes 3,5 KB low memory for *everybody*, not only when it's needed.
> regarding how much time we have spend until we had 64 byte free
> I think this is a bad idea
please s
On Sun, Feb 5, 2012 at 4:07 PM, C. Masloch wrote:
> Hello devs, especially Jeremy,
>
> I reviewed your recent commit 1702 to build 2041 regarding sector sizes
> larger than 512. Here are my thoughts and suggestions.
>
> - First, dsk.h defines the maximum sector size (MAX_SEC_SIZE) as 2048 (as
> th
...
> > 3. All the machines I have tried so far report the CHS vs LBA computed
> > mismatch warnings. Considering that first time FreeDOS users might be
> > put off because of these benign warnings, I would very much like to
> > avoid them.
>
> There's a list of warnings indeed. A big one at that,
And Bart is too quick, he already adjusted the watcom.mak so it just works. :-)
Thank you,
Jeremy
--
5 Ways to Improve & Secure Unified Communications
Unified Communications promises greater efficiencies for business. UC
On Jul 20, 2011 1:37 PM, "Bernd Blaauw" wrote:
>
> Op 20-7-2011 3:50, Bart Oldeman schreef:
> > It's probably best to make things explicit (unless the goal is a true
> > Win32->DOS cross-compile), using DOS16 utilities, by changing the last
> > part of mkfiles\watcom.mak to:
> >
> > CFLAGS1 = -os-
On Sat, Jun 25, 2011 at 4:40 PM, Bernd Blaauw wrote:
> Op 25-6-2011 16:06, Kenneth J. Davis schreef:
>> Hello all.
>>
...
> Are there any verified/stable working compiled versions available of the
> following?
> * COMMAND (there's an openwatcom CVS/SVN version som
I am working on updating my site as I move files to my new host.
www.fdos.org/kernel is updated. But I only have a little bit of time that I
split among development & website updates.
--
All of the data generated in your I
Hello all.
Kernel 2040 has been tagged and should be made available on
Sourceforge file releases within next few days.
Also available for download at fdos.org:
installer compatible form - http://www.fdos.org/kernel/package/
same as sf releases - http://www.fdos.org/kernel/release/LATEST/
Note: t
Thanks, I will fix it tonight. Originally I had it as inline asm and messed
up when I moved it to the external file. I need to fix the conditional as
well as I think the and is always compiled on 386 builds. Yes I plan post
2040 to add the CPU check and then update config.c to check this so avoi
On Sat, Apr 9, 2011 at 6:56 PM, Eric Auer wrote:
>
> Hi Pat, kernel gurus Jeremy and Bart,
>
>> You can release it [an updated kernel], but I want to put
>> it together with other updates and finally generate v1.1.
>
> You mean a FreeDOS 1.1 BASE ISO image? That would be nice,
> but you can of cou
On Fri, Nov 13, 2009 at 3:14 PM, wrote:
> Hello everyone,
> First, I have a bug report against the 1497 fdos.org build of sys
> (OW386/FAT32/UPX)--
> if I specify a file to write the bootsector to (sys c: large.bin, with or
> without /BOOTONLY or /BOTH), sys crashes with "Invalid opcode at 00AB
>
On Wed, Jul 29, 2009 at 5:06 PM, Eric Auer wrote:
>
> Hi Bart,
>
...
>> * New SYS, merged from unstable branch.
>
> I hope it still uses the much faster cached copying :-)
> Could you add a small but useful option to force either
> CHS or LBA mode boot sectors, in particular for FAT32?
...
I did m
Assuming no objections, I will tag and make available kernel 2039
sometime at the end of this week. So if there are objections, please
speak up! but include exactly what you feel needs to be done before
the new release [that can not wait for a future release].
Thank you,
Jeremy
-
On Mon, Jul 27, 2009 at 10:44 PM, wrote:
...
> In the discussion I refer to, relicensing was mentioned. I am curious who
> should be contacted for such requests, or if relicensing would be allowed,
> etc.
> The kernel source says "Portions copyright Patrick J. Villani."
> Would that mean that Pat
On Sat, Jul 18, 2009 at 10:37 AM, Bart
Oldeman wrote:
> Jeremy,
>
> I was wondering what your reasoning is for changing
It has to deal with debugging the kernel, especially during
initialization. I choose this method as the kernel does not usually
have many strings it prints except when built wit
I was just checking my email and about to work on an issue with the
usb stack from Bret Johnson. Does this change effect/fix the issues
with this (from the description it looks like it does - as the problem
was described as FAT32 specific issue with the kernel and related to
the buildbpb call) or
On Sun, Jul 5, 2009 at 8:09 AM, Christian Masloch wrote:
>>> - uses an interface on Int2F which probably isn't as good as an internal
>>> hook. (MS-DOS uses a number of hooks partly documented in RBIL, I use
>>> one
>>
>> You mean table 01636, format of share exe hooks?
>
> It doesn't matter, but p
On Tue, Jun 30, 2009 at 10:52 PM, Bart
Oldeman wrote:
> 2009/6/30 :
>> I've been trying to patch 2039-svn with Christian's fix, while working
>> under a TC 186/FAT32/"Win" kernel (built myself), and I have found the
>> following:
>
> what does "Win" here mean?
>
...
Win doesn't do anything. I w
On Fri, Jun 5, 2009 at 2:05 PM, Eric Auer wrote:
>
> Hi Bernd, Tom, Bart, others,
>
...
>> WfW support will probably never come; WfW was tighly coupled to the
>> kernel (at least according to Schulman et. al., WfW is MUCH more then
>> just a flavour of Windows 3.11)
>
> What is Schulman et al? I wo
On Mon, May 18, 2009 at 6:32 PM, Pat Villani wrote:
> If half as much effort went into the code that has gone into this
> thread, we'd have rewritten the kernel several times over.
>
> Since I'm wrong about the kernel(?), let me put it to you this way. I
wrong?
> want to put out a new release,
On Mon, May 18, 2009 at 3:49 PM, Tom Ehlert wrote:
>>> It won't help FreeDOS of course because it still uses fnodes for these
>>> things instead of SFTs.
>
>> Those are ancient relics that should be done away with. There is no
>> need for them anymore. I'd like to put that high on the priority l
Kernel 2038 tagged and available at http://www.fdos.org/kernel/latest/
Someone with access, please upload to ibiblio and release on SF.
Please test and report any new issues to the mailing list.
Depending on any reported issues, 2039 scheduled to be released in
about a month. Comments about new
On Fri, May 15, 2009 at 12:07 AM, Bart Oldeman
wrote:
> Hi,
>
> there's a problem with the recent FCB fix -- I was a little suspect
> seeing the change.
> After testing with the old GEM, it seems the problem is in FCBOpen: it
> initializes too much, see also
> http://www.drdos.com/dosdoc/sysprog/c
On Thu, May 14, 2009 at 12:38 PM, Eric Auer wrote:
>
> Hi Christian,
>
> The main bug/feature that I plan to work on is FAT+ support,
...
> You misunderstand me :-) Of course we should support files of 2-4 GB
> size in the STABLE kernel very soon! Just do not support ABOVE 4 GB
There are no l
On Tue, May 12, 2009 at 10:20 AM, Pat Villani wrote:
> Hi Folks,
>
> It's been a while, and I have to admit I haven't been keeping up on
> developments. Would the folks who have been working n the kernel,
> officially or unofficially, get in touch with me and let me know what
> you've been up to?
Below is the important part (either my SVN client or OW's text editor
seems to do some tab/space conversion)
based on the patch Eric posted based on RayeR's changes.
I changed where the +1 to cylinders was done and I want some comments
because I'm trying to make sure the code is consistent.
The p
On Thu, May 7, 2009 at 2:57 PM, Christian Masloch wrote:
> Hi,
>
> I just looked at the recent SVN commits to fix that CALL 5 stuff. The new
> commentary about it contains some errors. I'm appending the things I would
> improve about it. It's not meant to annoy you, although I imagine it
> could.
On Tue, May 5, 2009 at 5:24 PM, Eric Auer wrote:
>
> Jeremy,
>
>>> I could not find any LOAD*.* file in the zip, though... Maybe
>>> this whole experiment is something different than IBID meant?
>
>> See http://www.seasip.info/Gem/gemxm.html (I'm not sure if its the
>> same/newer/older than the
On Tue, May 5, 2009 at 2:10 PM, Eric Auer wrote:
>
> Hi Jeremy, Bart, IBID,
>
...
> I could not find any LOAD*.* file in the zip, though... Maybe
> this whole experiment is something different than IBID meant?
>
> Eric
See http://www.seasip.info/Gem/gemxm.html (I'm not sure if its the
same/newe
On Mon, May 4, 2009 at 9:35 PM, Eric Auer wrote:
> Hi ibid_ag at lavabit com,
>
>> I tried 2038rc1svn out _briefly_. It works about the same as prior builds
>> (runs edit, mem, command, gem; loads ctmouse, gcdrom, himemx,jemm386,
>> shsucdx; still does not run GEM/XM).
thanks, that sounds about
On Mon, May 4, 2009 at 6:26 PM, wrote:
> Hello,
> I've tried running GEM/XM under freedos kernels 2035b, 2036, 2037, and
> "Christian" experimental build (later renamed 2038pre). Official
> documentation says it will not work due to using FCBs to read the driver
> loading file, 'ASSIGN.SYS'. GE
I am still reviewing and testing the pending patches... but progressing. :-)
Does the non-UPX'ed kernel boot for anyone else? I spent most of this
evening tracking down why my kernel didn't boot (that is testing my
new setup so I wasn't sure if it was my host OS/compiler (I'm already
using ms2wl
On Fri, May 1, 2009 at 4:01 AM, Eric Auer wrote:
>
> Hi Bart,
>
> thanks for making the patch much shorter, very "commitable" now :-)
>
> Why did our old code do that complex "put bp at [bp+2]" thing? And
don't know
> what does the "cpm_error jump decision now inverted" patch mean?
skips the call
On Thu, Apr 30, 2009 at 8:18 PM, Bart Oldeman
wrote:
...
> This is a minimal fix for the kernel:
>
> --- entry.asm (révision 1371)
> +++ entry.asm (copie de travail)
...
> This bug has been there since the DOS-C days by the way!
>
> Bart
Thank you!
Patch committed along with some comments to
free time at last...
On Wed, Apr 29, 2009 at 8:49 PM, Eric Auer wrote:
>
> Hi Bart, admins, others,
>
>>> Would you like to have access again? Should be no problem :-)
>
>> Sure!
>
> Apparently only Aitor, Jim and Pat can give you SVN write
> access but I think that would be a *very* nice idea...
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 su
Eric Auer wrote:
...
> About Windows compatibility: Win 3.1 "WIN /S" works
> fine with kernel 2036 and older already, and "WIN /3"
> just returns to the prompt without further messages,
> even with the "winkernel". Maybe the patches only help
> with Windows for Workgroups 3.11?
>
...
It works fo
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% comp
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 conf
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 ch
[dev kernel, will check stable shortly]
It was brought to my attention by Eric that in config.sys read() returns
an unsigned count or 0x on error but we were checking as though it
returned a signed value (-1 or less than requested count). I committed
the change that makes these tests check
Just wanted to let everyone know I haven't completely dropped off the face
of the Earth, but my moving is taking me longer than anticipated, so I
still don't have my computers yet. Once I'm back operational I'll finish
my merge work and release a new stable kernel and see read the rest of
this req
飘似沙鸥 飘 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
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 problems?
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
--
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 i
would anyone object if after merging current changes into stable I
modified the comments in the dev branch so I could run a tool like
naturaldocs on the kernel and get useful output (www.naturaldocs.org).
Alternatively anyone know of any similar tool that would be better?
Nothing urgent, nor n
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 ; f
Arkady V.Belousov wrote:
Hi!
20-Ноя-2005 16:39 [EMAIL PROTECTED] (Kenneth Davis) wrote to
[EMAIL PROTECTED]:
+++ prf.c 20 Nov 2005 16:39:14 - 1.31.2.4
@@ -123,17 +123,17 @@
+STATIC void do_printf(const char FAR *, va_list);
+VOID VA_CDECL printf(const char FAR * fmt, ...);
---
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 the parameters can use either segment
interchange
The following may need to be added to your makefile for the debug
printfs to actually work, it tells OW that SS!=DS
This needs to be added to the watcom specific makefile, but as a special
flag so I didn't have time to do it yet.
Index: kernel/makefile
For some projects I would like to work on I need to modify the kernel to
not overwrite certain sections of memory at startup. My problem is that
these items are put in memory before the kernel is loaded so I can not
just allocate the memory using DOS calls (since no MCB chain exists yet).
The
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 (OemH
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 (e
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 resources
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 occup
Bernd Blaauw wrote:
Diego Rodriguez schreef:
Hi
There is a problem with COUNTRY and the Spanish code in CONFIG.C
The correct code is *34* not 33, wich is the French one (actually the
settings are the same).
should be fixed in nightly stable releases
cstarter wrote:
>
> Now ,I have known what you said .But when we assemly the code , and
> write the binary file to the floppy ,The 1st sector will be overwritten.
> Then BPB is destroyed .
> Thanks for you reply .
If you directly write it yes, but it is not meant to be used that way.
You need t
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 fat
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 ke
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. .
Arkady V.Belousov wrote:
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 k
Any of you watching cvs commits will see I just commited some
code to the dev branch to aid in win 3.x support when WIN31SUPPORT
is defined. When this is not defined there is minimal changes to the
kernel, however and this is my primary question it does restructure
some variables marked 'FreeDOS s
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
# err
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" s
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
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 multi-boot users would try to use
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 multi-boot users would try to use
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 moment
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,
an
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 BINARY.
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).
... wh
Bart Oldeman wrote:
On Sun, 12 Sep 2004, Kenneth Davis wrote:
merge in some changes from UNSTABLE
I wonder about those creation time set removals. It looks like your
...
Maybe it should be a config.sys option if it did hurt in certain
I will consider reverting it, but a config.sys option is overk
So the options are:
1) current
- use 0xFF in BPB.drive to indicate to boot code to use BIOS provided
drive in DL, otherwise use value in BPB.drive
- the boot sector code can be anywhere and is similar to:
cmp [BPB.drive], 0xFF
jmp dont_use_bios
mov [BPB.drive], dl
don
Arkady V.Belousov wrote:
... (I'm reading his question from the archive, never getting it myself) ...
http://freedos.sourceforge.net/kernel.UNSTABLE.tgz
will be http://freedos.sourceforge.net/kernel/kernel.UNSTABLE.tgz
and updated regulary once sourceforge reenables cronjobs,
currently it and /kern
Arkady V.Belousov wrote:
Third (or 5th?) times of asking (without answer): where and how
download latest (unstable) kernel sources? And, as I understand, there is
If sourceforge has cron working, tarballs are there still, additionally:
http://www.fdos.org/kernel/kernel.HEAD.zip for stable
The Somertons wrote:
Hi folks,
That "unstable" kernel and command.com, is it a smart idea to use it for
normal use (just my room playing games, no serious business stuff) for
testing purposes?
Thanks,
Interon
It should be fine to use for games and such, especially if you are
willing to submit bu
Arkady V.Belousov wrote:
Hi!
Log Message:
easier change of kernel load segment, remove need of keypress when linking
+++ wlinker.bat 2 Sep 2004 20:22:05 - 1.3.2.2
-%BASE%\binw\ms2wlink %1 %2 %3 %4 %5 %6 %7 %8 %9>kernel.lnk
+%BASE%\binw\ms2wlink %1 %2 %3 %4 %5 %6 %7 %8 %9 >kerne
Luchezar Georgiev wrote:
Hallo Bart,
...
#define BUILD "2035a"
#define SUB_BUILD "-UNSTABLE"
oops, I see it should be BUILD 2035 with SUB_BUILD a-UNSTABLE
I don't know why some people started calling 2035a-UNSTABLE plain
2035a... perhaps just too lazy to type "-UNSTABLE". But it re
Arkady V.Belousov wrote:
Hi!
25-Июл-2004 09:55 [EMAIL PROTECTED] (Kenneth Davis) wrote to
[EMAIL PROTECTED]:
KD> +++ autoexec.bat25 Jul 2004 09:55:56 - 1.6.2.1
KD> @@ -1,3 +1,3 @@
...
Hm. What here changed? Why diff shows all lines as changed?
This is largely a cvs issue regarding
There recently has been discussion of the kernel,
of the upcoming FreeDOS 1.0 release, and of changes
which should or should not be accepted.
As acting kernel maintainer, this is how I am trying
to ensure stability while making progress and trying
not to 'upset the talent' as it were.
As I said in
James Tabor wrote:
Hi,
I see allot of patches from Arkady. If I had more time I could check
them out and start committing to the CVS. But! So many patches!
Yes there are! :-)
Which is why I created a development branch, where I can more
quickly apply patches that may (or may not) need more testing
Alain wrote:
Can someone send me a compiled version with debugging? Pleeease...
Either 2035 or 2035a or both ;-)
You can find builds of the cvs stable (still pretty much
kernel 2035) and cvs dev branch (much of Arkady's & Lucho's changes),
both with or without extra debug (-DDEBUG) information on
f
Arkady V.Belousov wrote:
Why? Also, I see, you miss my fix for previous records in history.txt
(was published here).
Because I have not had time to review the patches that the changes refer
to, and I do not wish to make any adjustments to prior changelog until
I am certain of what the change r
...
I may send you my edition of config.c (private, I suggest?), but it not
the last edition (I continue to work on it).
please do
...
and add own comments. For example:
KJD> yes, I viewed yours, the original, RBIL, and the code and selected
KJD> the one that seemed the most clear, being more
Arkady V.Belousov wrote:
Hi!
18-Июн-2004 03:12 [EMAIL PROTECTED] (Kenneth J. Davis) wrote to
[EMAIL PROTECTED]:
KJD> I have gone through Arkady's floppy patchset (is there a 5 of 5?).
There was 4 of 5. Last patch I omit, because it was cosmetic. Ot the
other side, you may get
I have gone through Arkady's floppy patchset (is there a 5 of 5?).
This weekend I intend to finish processing his dsk.c patchset
(which includes Lucho's rewording patch), and once a patch is
provided I will work on the config processing. I'll commit the
history.txt update once I finish the dsk.c w
Arkady V.Belousov escreveu:
Hi!
Well, looks like Bart is gone. Who now will manage the kernel
(reconcile patches, update CVS, release intermediate snapshots)? For
example, my current todo contains at least 6 bugfixes for dsk.c, and 2
which
I don't know how to handle. Beside this, there optimi
On Sun, 04 Apr 2004 22:41:35 +0200 Bernd Blaauw <[EMAIL PROTECTED]> wrote:
...
BB> *Can there be a hint as to NASM use?
BB> I did this wrong.
BB> Bart's config.b has a line "set NASM=NASM16"
BB> I thought this pointed at a directory.. ofcourse compiling failed :)
BB> so please add a comment like "
>>> - /Odrive - use fixed drive number (in hex) in boot sector.
>MHT> If this switch is intended for compatibility with DR-DOS, drive number
>MHT> should be given in decimal. Support for hex with '0x' and/or '$' prefix
>MHT> can be a nice extension, though :-)
>
> Inconsistent: address in /L op
..
>
> BTW, who currently officialy mantain SYS?
>
..
The kernel maintainers. I'm just commenting as most
of your suggestions are regarding code based on a
patch I submitted a while back, though sys has had
many improvements since them.
Jeremy
---
>To: [EMAIL PROTECTED]
>From: "Arkady V.Belousov" <[EMAIL PROTECTED]>
>Subject: [Freedos-kernel] sys.c issues
>
>Hi!
>
>AIU=As I understand.
>
>>int main(int argc, char **argv)
>> if (argc > 1 && memicmp(argv[1], "CONFIG", 6) == 0)
>>else if (memicmp(argp, "BOOTONLY", 8) == 0 && !bootonly)
>>
Please change the two lines in sys.c that use (int *) to use (UWORD *) or
similar. I overlooked this when compiling with MS VC 6 and causes the
resulting floppy to not be able to boot as the wrong location is written
to (as int == DWORD instead of WORD). And I'm likely to overlook it again
if I u
95 matches
Mail list logo
