Hi!
18--2004 16:50 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:
EA Jeremy, please create a list of improvements / changes between 2035
EA and newest CVS kernel, and a way to download all patches separately
EA (or in one big tgz/zip), along with short descriptions of them.
All
Hi!
18--2004 20:32 [EMAIL PROTECTED] (tom ehlert) wrote to Eric Auer
[EMAIL PROTECTED]:
- Lucho / Arkady produced a big amount of patches which mainly contain
optimizations (hopefully not too compiler specific), but also important
bugfixes,
te which ones ?
See the subject for one
Hi!
19--2004 02:34 Arkady V.Belousov wrote to
[EMAIL PROTECTED]:
- Lucho / Arkady produced a big amount of patches which mainly contain
optimizations (hopefully not too compiler specific), but also important
bugfixes,
te which ones ?
AVB See the subject for one fixed bug.
I
Hi!
15--2004 03:44 [EMAIL PROTECTED] (Bernd Blaauw) wrote to All:
BB Bart, do you see the unnamed program, eating 48KB (probably just a
BB viewing problem)?
BB CTMOUSE 3,328(3K) 0(0K) 3,328(3K)
BB 48,704 (48K) 0(0K) 48,704 (48K)
Arkady V.Belousov wrote:
BB Bart, do you see the unnamed program, eating 48KB (probably just a
BB viewing problem)?
BB CTMOUSE 3,328(3K) 0(0K) 3,328(3K)
BB 48,704 (48K) 0(0K) 48,704 (48K)
BB Free 623,024 (608K)622,880
Hi!
15--2004 12:04 [EMAIL PROTECTED] (Bernd Blaauw) wrote to
[EMAIL PROTECTED]:
BB CTMOUSE 3,328(3K) 0(0K) 3,328(3K)
BB 48,704 (48K) 0(0K) 48,704 (48K)
BB Free 623,024 (608K)622,880 (608K)144(0K)
Hi,
Bernd Blaauw escribió:
Bernd Blaauw wrote:
Hello all,
I've put online a new bootdisk with which I, and you, can easily
experiment. Download it from:
http://fdos.org/ripcord/beta9-final/test/testing.zip [274KB, 1.44MB
unzipped]
OK, just uploaded a new version, now includes fixed autoexec.bat
Hi,
Bernd Blaauw escribió:
2) DISPLAY loads low (see MEM /C /P), while plenty of (UMB)memory is
available, and being the FIRST driver loaded. very strange!
3) DISPLAY loads high and ATAPICDD/CDRCACHE load low, if removing the
REM from MEM /C in the beginning of autoexec.bat
You are using
Bart Oldeman escribió:
On Wed, 15 Sep 2004, Bernd Blaauw wrote:
Bernd Blaauw wrote:
Hello all,
I've put online a new bootdisk with which I, and you, can easily
experiment. Download it from:
http://fdos.org/ripcord/beta9-final/test/testing.zip [274KB, 1.44MB
unzipped]
OK, just
alright, MEM display is a MEM bug as Bart indicated,
Lucho fixed, as final public developers's work for his part, the
'remainig' - 'remaining' cosmetic bug.
now only this strange bug of why DISPLAY loads high if MEM is first run,
and loads low (and atapicdd/cdrcache load high instead) if MEM
Hi!
15--2004 13:45 [EMAIL PROTECTED] (Aitor Santamara Merino) wrote to
[EMAIL PROTECTED]:
2) DISPLAY loads low (see MEM /C /P), while plenty of (UMB)memory is
available, and being the FIRST driver loaded. very strange!
3) DISPLAY loads high and ATAPICDD/CDRCACHE load low, if removing the
REM
Bernd Blaauw escribió:
no idea if the DISPLAY binary has been UPX'd, and if that has any affect.
UPX first, COM2EXE next, produces smallest size.
I'm still confused by syntax for DISPLAY/MODE/KEYB.., so it's good to
have working examples at hand.
I think what you are using is ok. It's equal than
Hi,
Eric Auer escribió:
About DISPLAY:
UPX first, COM2EXE next, produces smallest size.
bad idea. COM2EXE cannot detect de-UPX-ed size! So the exe header
will tell how much space the compressed COM needs. But the whole idea
of using COM2EXE was to let DOS know the de-UPX-ed size
Aitor wrote:
By the way, does anyone know how to mount a drive or
directory as a drive for VMWARE? (something like DOSEMU's
lredir).
I never had VMWARE myself (why spend US $189 when you don't
need to?) but from what I've read about it has a virtual
network card so you could use a SMB client
Hi!
15--2004 19:31 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:
EA About DISPLAY:
UPX first, COM2EXE next, produces smallest size.
EA bad idea. COM2EXE cannot detect de-UPX-ed size! So the exe header
This is unimportnat, because (my) COM2EXE doesn't detects size at
all. It
Hi!
16--2004 01:19 [EMAIL PROTECTED] (Aitor Santamara Merino) wrote to
[EMAIL PROTECTED]:
bad idea. COM2EXE cannot detect de-UPX-ed size! So the exe header
will tell how much space the compressed COM needs. But the whole idea
of using COM2EXE was to let DOS know the de-UPX-ed size explicitly:
I wonder about those creation time set removals. It looks like your
I will consider reverting it, but a config.sys option is overkill.
Yes, it is. It'll be difficult to revert it as it leaded to numerous other
optimisations. Besides, I already explained why I removed it. Why add back
an useless
BTW, Lucho, if you wish, I may prepare for you macroses in TASM to ease
writing more readable and safer country.asm. Probably, someone then may
translate these macro to NASM?
Such translation will be very difficult if not impossible because NASM is
too incompatible :-( So, don't bother with it.
Hi,
Luchezar Georgiev escribi:
I wonder about those creation time set removals. It looks like your
I will consider reverting it, but a config.sys option is overkill.
Yes, it is. It'll be difficult to revert it as it leaded to numerous
other optimisations. Besides, I already explained why I
Hola Eduardo,
Not really. In the worst case, only the 4 bytes for the empty DBCS table
will be unused. The idea is to overwrite the hardcoded tables for
CTYINFO, UCASE, FCHAR, and COLLATE and allocate new memory (if needed)
for FUCASE, LCASE and DBCS _only_.
What about a combination of your (1)
On Mon, 13 Sep 2004, Luchezar Georgiev wrote:
Bart wrote:
I wonder about those creation time set removals. It looks like your
removing a useful feature here. Sure a reason given is MSDOS 7.10
doesn't do this. Well, I say, who cares about this specific DOS,
Isn't *this* specific OS what
The question is: does anyone know what does MS-DOS do?
What now unstable FreeDOS does - ZERO creation time/date and access date
on each directory entry write. Verified.
---
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
#include fcntl.h
#include io.h
#include dos.h
int main(void)
{
int fd = open(fool.dat, O_WRONLY|O_CREAT|O_TRUNC);
write(fd, hello, 5);
close(fd);
sleep(2);
fd = open(fool.dat, O_WRONLY);
write(fd, hello bye, 9);
close(fd);
return 0;
}
Thanks, Bart. Seems that as I already have
On Tue, 14 Sep 2004, Luchezar Georgiev wrote:
#include fcntl.h
#include io.h
#include dos.h
int main(void)
{
int fd = open(fool.dat, O_WRONLY|O_CREAT|O_TRUNC);
write(fd, hello, 5);
close(fd);
sleep(2);
fd = open(fool.dat, O_WRONLY);
write(fd, hello bye, 9);
Lucho, you introduce change in interface. _Such_ actions necessarily
_must_ be discussed and approved.
By whom? By the Boss? Who is the Boss? Arkady?
Hi Lucho, don't feel hurt, he is just sayint what we yelled at him so
many times :) The boss is ... gess who? the comunity, represented in
this
Alain escribió:
Lucho, you introduce change in interface. _Such_ actions necessarily
_must_ be discussed and approved.
By whom? By the Boss? Who is the Boss? Arkady?
Hi Lucho, don't feel hurt, he is just sayint what we yelled at him so
many times :) The boss is ... gess who? the comunity,
Hi!
13--2004 04:19 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:
EA how to use it that way ;-). In addition, the MS-ish interface allows
EA revert to real version number by passing a value of zero. The extra
RBIL doesn't says this.
EA few bytes are really VERY few bytes and
Hi!
12--2004 14:30 [EMAIL PROTECTED] (tom ehlert) wrote to Luchezar Georgiev
[EMAIL PROTECTED]:
Only 0 and 80 are used by MS-DOS. All other values are FreeDOS extensions ;-)
te are you SURE ?
How strange. B-\ I receive this letter two minutes back, whereas I
answer yesterday to Lucho's
Hi!
12--2004 14:28 [EMAIL PROTECTED] (tom ehlert) wrote to Luchezar Georgiev
[EMAIL PROTECTED]:
and removes (parts? of) tom's patch.
As you wrote youself, it's better to have the whole patch than parts of
it. And even better is to solve entirely the problem which this kludge
solves
In addition, the MS-ish interface allows revert to real version
number by passing a value of zero.
RBIL doesn't says this.
It does say this. D-2F122F says: DX = DOS version number (h = return
true DOS version). RBIL also says this is supported by Matthias Paul's
FREEVER.COM. Do you see now
Although I dislike the idea of patching the bootsector, choice 2 does
seem most compatible and is slightly smaller boot code (as the logic is
moved to sys).
I agree and prefer method 2 too. The distance between this new patched
boot sector offset and the existing boot segment offset seems
Hello Luchezar,
Do you mean
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01070.html
yes
(It doesn't contain other comments but those in the patch.) If you
confirm, I can apply it.
yes.
it happens if a int24 handler returns to itself directly, instead of the
'normal' way to return to
Hallo Bart,
merge in some changes from UNSTABLE
If Bart doesn't like some changes, I don't mind if they're not merged them
into stable ;-)
I wonder about those creation time set removals. It looks like your
removing a useful feature here. Sure a reason given is MSDOS 7.10
doesn't do this.
Eduardo, couldn't we divide the work between ourselves? If you do the
changes in nls_hc.asm for the third option you offered (make enough room),
I will add the necessary code in config.c ;-)
---
This SF.Net email is sponsored by: YOU BE THE
Do you mean
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01070.html
yes
(It doesn't contain other comments but those in the patch.) If you
confirm, I can apply it.
yes.
Just applied and committed (and updated binary on my site ;-)
---
This
Hello,
Award BIOS dated 1999 for Intel i810, and the original IBM PC/AT BIOS
don't seem to pass anything in DL on Int 19h. How did I verify it? For
those who can't guess, let this be my little secret ;-G
(Table 00653)
Values Bootstrap loader is called with (IBM BIOS):
CS:IP = h:7C00h
DH =
Hi!
13--2004 12:04 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
In addition, the MS-ish interface allows revert to real version
number by passing a value of zero.
RBIL doesn't says this.
LG It does say this. D-2F122F says: DX = DOS version number (h = return
LG true
The BIOS Boot specification warns that only 0 and 80h can be [...]
[...] interesting enough... Nevertheless, trying it gives me 404...
Moved -
http://www.phoenix.com/NR/rdonlyres/56E38DE2-3E6F-4743-835F-B4A53726ABED/0/specsbbs101.pdf
---
This
Hi!
13--2004 12:48 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
My AwardBIOS here for example does have such a feature. However, when I
look at the boot record of my second hard drive, I see again boot drive
= 80.
Do you try to boot from second drive with this boot
El lun, 13-09-2004 a las 12:36, Luchezar Georgiev escribió:
Eduardo, couldn't we divide the work between ourselves? If you do the
changes in nls_hc.asm for the third option you offered (make enough room),
I will add the necessary code in config.c ;-)
Hi Lucho,
I don't mind adding the
Ie., second disk was enumerated as 80h (and, for example, partitions
from it was labeled earlier, than from first disk)?
Yes, exactly.
This warning may be only because authors of tose spec may know about
existance of buggy BIOSes.
No, they state several times that ONLY 0 AND 80 may be boot
Hola Eduardo,
I don't mind adding the changes to nls_hc.asm, but I'm not sure that I
like that option.
Neither do I like it very much, but (1) and (3) are most straightforward
and easiest to implement.
In a private mail, Eric suggested a fourth option: Check if there is
enough room for loading
Hi!
13--2004 19:55 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
This warning may be only because authors of tose spec may know about
existance of buggy BIOSes.
LG No, they state several times that ONLY 0 AND 80 may be boot drives.
Ok. What about boot managers?
No,
El lun, 13-09-2004 a las 19:19, Luchezar Georgiev escribió:
In a private mail, Eric suggested a fourth option: Check if there is
enough room for loading the package and, if not, allocate extra memory
only for the additional tables.
This will keep the kernel size unchanged and optimze
No, they state several times that ONLY 0 AND 80 may be boot drives.
Ok. What about boot managers?
The option mentioned below is for boot managers too.
For this, an option of SYS will revert back to DL = boot drive
Hm. Your arguments sounds reasonable. But I continue to _feel_, that
using BIOS
Hi!
12--2004 14:08 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
I don't understand this. SYS writes 0/FF only into its own images,
builtin into SYS executables. And, if _after_ SYS someone will change
boot loader, then 0/FF value also will be replaced. Where is trouble?
Hi!
BTW, Lucho, if you wish, I may prepare for you macroses in TASM to ease
writing more readable and safer country.asm. Probably, someone then may
translate these macro to NASM?
---
This SF.Net email is sponsored by: YOU BE THE JUDGE.
Hi!
12--2004 14:23 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
* There is no room for the LCASE table, so it won't be possible to load
the ru/866 pair.
BTW, in contary to RBIL (which says that INT21/6503 is present only in
DOS 6.2+ COUNTRY.SYS and supports only
Hi!
12--2004 13:54 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
Show this, please.
LG See it in the CVS, along with the nice additions of Eduardo.
CVS isn't accesible for me.
Let me ask reverse question: why you add this _another FreeDOS specific
function, which
Hi,
Luchezar Georgiev escribi:
I still think that half a kilobyte isn't a big price to pay, PROVIDED
THAT SOMEONE WILL REALLY USE THE DOUBLE-BYTE TABLES. As far as I know,
there are complete Chinese, Korean and Japanese packages that install
their own font, NLS and keyboard support, and most
Hi!
15--2004 21:59 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
BO BC isn't a target for freedos optimizations; there's one and only one
BO target to optimize for : WATCOM.
BO so BC specific optimization is a waste of time (ours and yours)
BO This just being tom's opinion but
Hi!
15--2004 20:24 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
- lr.BH = OEM_ID;
- lr.CH = REVISION_MAJOR; /* JPP */
- lr.CL = REVISION_MINOR;
- lr.BL = REVISION_SEQ;
+ lr.BX = (OEM_ID 8) | REVISION_SEQ;
+ lr.CX = 0; /* serial number must
Hi!
10--2004 20:05 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
LG brain-dead BIOSes if the boot drive is A: (but not if it's C:), the FF
LG value written to by SYS causes a compatibility problem. What happens if
LG someone decides to overwrite our boot sector later with a
I don't understand this. SYS writes 0/FF only into its own images,
builtin into SYS executables. And, if _after_ SYS someone will change
boot loader, then 0/FF value also will be replaced. Where is trouble?
The trouble is that most SYSes don't bother to set this value - they just
copy the whole
Hello Luchezar,
D:==second disk? Second disk is a 81h value.
Only 0 and 80 are used by MS-DOS. All other values are FreeDOS
extensions ;-)
are you SURE ?
I remember a BIOS that had the option to boot from 2'nd drive.
this only makes sense if DOS then boots from 0x81.
tom
Hello Luchezar,
and removes (parts? of) tom's patch.
As you wrote youself, it's better to have the whole patch than parts of
it. And even better is to solve entirely the problem which this kludge
solves partially. But we don't know the problem :-(
at least I know the problem - and
Hi!
12--2004 14:28 Arkady V.Belousov wrote to
[EMAIL PROTECTED]:
And what about INT2F/122F?
LG Although only MS-DOS 4.0 had it, I won't remove it
AVB Let me ask reverse question: why you add this _another FreeDOS
AVB specific
AVB function, which duplicates another specific function_,
Hallo Eric,
we already do have 622k low DOS RAM free in a quite straightforward
configuration (in DOSEMU, where HIMEM / EMM386 take almost no memory,
even 627k), and I never met any program which really needed more than
590k, so this is only about bragging.
Exactly. I have 629 KB free in
Hallo,
Therefore I vote for a SYS option which lets you decide whether or not
the 0x80 in the boot sector will be used. The DEFAULT should be, in my
opinion, to accept the value from the boot manager / MBR / BIOS for
harddisks. For floppy, 0 will be in the boot sector, and the DEFAULT
should
unsigned char check_handle_break(struct dhdr FAR **pdev)
{
- unsigned char c;
+ unsigned char c = 0;
if (ctrl_break_pressed() ||
(c = (unsigned char)ndread(syscon)) == CTL_C
||
*pdev != syscon (c = (unsigned char)ndread(pdev))== CTL_C)
{
Hello,
I uploaded the wrong patch to my page. I have updated it now, so please
download it again from the same location:
http://perso.wanadoo.es/samelborp/country.zip
Sorry for the inconvenience.
Eduardo.
---
This SF.Net email is sponsored
Arkady V.Belousov escreveu:
Hi!
7--2004 19:17 [EMAIL PROTECTED] (Kenneth Davis) wrote to
[EMAIL PROTECTED]:
KD Update of /cvsroot/freedos/kernel/boot
KD In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28417/boot
Third (or 5th?) times of asking (without answer): where and how
download
Hi again, Justin!
In FreeDOS 2035a, NSSI crashed.
In the newest unstable kernel, NSSI works excellent!
Get NSSI at http://www.navsoft.cz
Thanks for the information! Unfortunately if UDMA or CD-ROM driver is
loaded, it hangs at the checking memory for viruses stage under the
unstable CVS kernel.
If I right remember, Lucho's patch affect os_major and os_minor.
No, it affects os_setver_m??or.
---
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who
Hello Luchezar,
In FreeDOS 2035a, NSSI crashed.
In the newest unstable kernel, NSSI works excellent!
Get NSSI at http://www.navsoft.cz
Thanks for the information! Unfortunately if UDMA or CD-ROM driver is
loaded, it hangs at the checking memory for viruses stage under the
unstable CVS
#pragma aux default parm [ax dx cx] modify [ax dx es fs]
Thanks, Eduardo - Jeremy already noted these errors on CPU 386 this and
today I fixed it in the CVS by applying it only for an 80386. The pragma
was suggested by Bart. I don't understand how it works but it does
decrease kernel size
Hi!
8--2004 19:32 [EMAIL PROTECTED] (Kenneth J. Davis) wrote to
[EMAIL PROTECTED]:
Third (or 5th?) times of asking (without answer): where and how
download latest (unstable) kernel sources? And, as I understand, there is
KJD If sourceforge has cron working, tarballs are there still,
In FreeDOS 2035a, NSSI crashed.
as it works for me (a different 2035a), could you
give some details (like config.sys).
in particular: does it crash with an empty config.sys ?
tom
In the newest unstable kernel, NSSI works excellent!
Get NSSI at http://www.navsoft.cz
Interon
and AUTOEXEC.BAT, NSSI worked fine under FreeDOS
2035a.
- Original Message -
From: tom ehlert [EMAIL PROTECTED]
To: The Somertons [EMAIL PROTECTED]
Sent: Wednesday, September 08, 2004 6:39 AM
Subject: Re: [Freedos-kernel] NSSI Works!!!
In FreeDOS 2035a, NSSI crashed.
as it works for me
Bom dia, Alain!
Now the kernel no longer removes or renames the current directory of
the drive for which this is requested.
This says that it does not do what is requested... Could you please
rewrite or explain it?
MS-DOS never removes or renames the current directory of the drive for
which
CVS already updated. Binary at
And question again: how to download this lates image?
http://linux.tu-varna.acad.bg/~lig/freedos/kernel/KERNEL.SYS
http://linux.tu-varna.acad.bg/~lig/freedos/kernel/SYS.COM
The boot code in SYS now has the DMA 64K boundary cross bug fix (thanks,
Jeremy! :)
Hi!
5--2004 12:37 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
LG MS-DOS behaviour changes regarding creation/access stamps etc. Sources in
LG CVS already updated. Binary at
And question again: how to download this lates image?
Hi!
3--2004 06:00 [EMAIL PROTECTED] (Kenneth J. Davis) wrote to
[EMAIL PROTECTED]:
+++ wlinker.bat 2 Sep 2004 20:22:05 - 1.3.2.2
-%BASE%\binw\ms2wlink %1 %2 %3 %4 %5 %6 %7 %8 %9kernel.lnk
+%BASE%\binw\ms2wlink %1 %2 %3 %4 %5 %6 %7 %8 %9 kernel.lnk
Please, explain this.
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 %9kernel.lnk
+%BASE%\binw\ms2wlink %1 %2 %3 %4 %5 %6 %7 %8 %9
+%BASE%\binw\ms2wlink %1 %2 %3 %4 %5 %6 %7 %8 %9 kernel.lnk
If you have a better fix, I will gladly change it.
Microsoft LINK accepts a trailing colon (;) after the last meaningful
argument instead of commas. Perhaps this would work for MS2WLINK too? Like
this:
+%BASE%\binw\ms2wlink %1 %2
Microsoft LINK accepts a trailing colon (;) after the last meaningful
argument instead of commas
Sorry about my bad English. The dictionary says that the ; sign is
called semicolon, not colon!
---
This SF.Net email is sponsored by BEA Weblogic
Eric, why don't you fill in a Bugzilla entry with this problem?
Lucho
Tue, 31 Aug 2004 18:53:29 +0200 (MEST), Eric Auer [EMAIL PROTECTED]:
Hi all, please check:
http://www.coli.uni-sb.de/~eric/comdrive-analysis.txt.gz
... and tell me how to make (either by fixing FreeDOS or comdrive or
both) this
it doesn't compile.
Sorry - it turned out that my patches were against a mixture of stable and
unstable branch! Now I got the real unstable CVS sources, cleaned up mine,
and the resulting patch became larger, because it contains some Arkady
changes not in unstable CVS yet. Just uploaded it on
...
P.S. After sending the above message, I got the following auto-reply:
Your mail to 'Freedos-kernel' with the subject
Updated unstable kernel patches and binary
Is being held until the list moderator can review it for approval.
The reason it is being held:
Message body is too big: 76015
Mon, 23 Aug 2004 00:00:30 +1200 (NZST), Bart Oldeman
[EMAIL PROTECTED]:
63978 bytes!!! HOORAY!!! ;-) ;-) ;-)
Still strange. I get 64266, doesn't matter whether it's OW 1.2 or 1.3.
Strange indeed.
#if !defined(FORSYS)
#pragma aux default parm [ax dx cx] modify [ax dx es fs]
#endif
in portab.h
On Mon, 23 Aug 2004, Luchezar Georgiev wrote:
What do you mean by the 386 options? I do use the -3 option as well as
-zff -zgf options.
Yes that's what I meant. What are the errors dsk.c gives you?
That's the only weak point indeed. They didn't seem to fix the bug I
reported (bug 407)
Ciao, Eduardo,
We strive for MS-DOS compatibility, and MS-DOS, PC-DOS, PTS-DOS, OS/2,
Windows 9x and Windows NT all use the same format that is so well
described in the RBIL tables 2619-2622. So I chose that.
IMHO, the COUNTRY.SYS format does not affect compatibility, as the
information is
Hallo Bart,
Yes that's what I meant. What are the errors dsk.c gives you?
None! :-O Don't know why, but now when I edited the UTILS\MAKEFILE to
define EXEFLAT for EXEFLAT.C so that the pragma doesn't affect it,
OpenWatcom 1.3 *successfully* built the kernel and the size is... guess
what -
Lucho, whatever you do. Please leave that copyright message in. You made
a proposal to change it. Then just removed it. Which is worse.
The justice finally caught the criminal! I didn't remove it, I had just
*moved* it to AUTOEXEC.BAT where it can be enjoyed in its full glory for
as long as you
Bom dia, Alain!
I believe that being hated as much as a certain man is a matter of
behaviour.
I always use this analogy: Oracle's product are very expensive, but
their custumers are content and Oracle is not hated at all.
M$ make we feel bad, not because they charge, but because they force us
Luchezar Georgiev schreef:
Lucho, whatever you do. Please leave that copyright message in. You
made a proposal to change it. Then just removed it. Which is worse.
The justice finally caught the criminal! I didn't remove it, I had
just *moved* it to AUTOEXEC.BAT where it can be enjoyed in its
Hi,
I just have to say: many thanks for your reply.
Bart Oldeman escribió:
(5) By the way, strangely enough I don't happen to see 123 - Initdisk
anymore, due most probably to the \r before the kernel compatibility.
Now I was just wondering who prints FreeDOS kernel version 1.1.35
(Build 2035) [May
tom ehlert escribió:
Hello Aitor,
I have started watching kernel source files, and trying to understand
its logic by reading sources.
good luck ;)
Thanks as well! (and for reply).
Aitor
---
SF.Net email is sponsored by
Hi!
22--2004 22:39 [EMAIL PROTECTED] (Alain) wrote to
[EMAIL PROTECTED]:
PS: Currently I improve (cure) my nose, so I again delay my answer around a
week.
A Can someone translate that from Russian :)
Don't worry, personal medical issues, which are now solved. Russian
proverb: troubles
Hi!
22--2004 15:25 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
LG I noticed that I often get CHKDSK/SCANDISK errors that my FAT32 freespace
LG count is incorrect. This happens when I write new files onto my disk, e.g.
LG free space decreases.
I get same under MS-DOS
Hi!
23--2004 20:08 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
(1) why are there STRINGS.C and MISC.C, apparently with the same
functionality and same routines in the same programming language?
BO They are just there for reference now.
BO there in case somebody wants to play
Now I discovered this using DISKEDIT. It's a double word at offset 488
(1E8h) of the second sector of the FAT32 boot record (which consists of
three sectors, not one as for FAT12 and FAT16). But actually this is
described in
http://www.microsoft.com/hwdev/download/hardware/fatgen103.pdf
It's
It's declared in hdr/xstructs.h as xdpbforformat.setdpbcounts.nfreeclst
but I don't see it updated anywhere! I suppose that this should be done
at the end of kernel/fattab.c:link_fat() along with the update of the
dpbp-dpb_xnfreeclst, but how to do it?
I was wrong. It's fsinfo.fi_nfreeclst and
(some) big corporations _do_ thefting. For example, Sony theft Walkman
idea (AFAIR, from Bulgarian inventor), Logitech was reject co-operation
with Russian developers, but then (quietly) reuse their ideas in own
mice. :(
I didn't know those things, and they only support my anti-corporate
About country sys: Do NOT copy it from another DOS.
It's NOT copied! See COUNTRY.ASM in
http://linux.tu-varna.acad.bg/~lig/freedos/kernel/CVSPATCH.TXT
---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R
Eric Auer escribió:
As far as I remember, we only have US and German country data around in
the kernel - but that might be because the other countries are similar to
either of both, and nobody missed explicit support for them yet??
Well, the uppercasing and lowercasing tables for codepage 850
On Sat, 21 Aug 2004, Luchezar Georgiev wrote:
Even after reducing kernel size with my latest patches I still get 65830
bytes. That's more than a kilobyte bigger! How can we explain that?
Well I can only try to narrow down by telling exactly what I did:
here we go:
download UNSTABLE cvs
cvs
Hallo Bart,
resolve rejects in exeflat.c :(
Sorry, my fault. Just fixed that and uploaded a new CVSPATCH.TXT,
including a SYS fix - OpenWatcom 1.3 now complains about missing return
type of fat32readwrite so I addeed an int at both places.
I've uploaded it to
63978 bytes!!! HOORAY!!! ;-) ;-) ;-)
I'm looking forward to say Goodbye, Borland! Welcome, Watcom! ;-)
Sadly, I can't do this yet - UPX compressed it to 41604 bytes as COM and
41614 bytes as EXE. aPack - to 42071 bytes as COM. In contrast, the
cowardly Borland 4.0 FAT32/80386 aPacked
UPX compressed it to 41604 bytes as COM and 41614 bytes as EXE.
I mean as SYS, not as EXE. I just changed the first 4 bytes to FF to fake
it.
---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for
501 - 600 of 1070 matches
Mail list logo
