Nabble - FreeDOS

Re: NOT PUBLIC DOMAIN (was Re: Possible size optimizations, kernel build 2039 bug in tracker)

2009-11-28T05:28:56Z

Thank you. I will follow through on that.

Pat

On Sat, Nov 28, 2009 at 8:26 AM, Eric Auer <e.auer@...> wrote:

Hi Pat,

> Allow me to make this perfectly clear: the FreeDOS kernel
> *IS NOT PUBLIC DOMAIN* and will never be.
> Please do not spread such rumors.

I do not see such rumors but...

>> OFFTOPIC: JaguiD (Java with GUI for DOS) might be worth testing;
>> the Ikon GUI, offered commercially this fall as an OS with some
>> (unspecified) FreeDOS kernel, is now public domain/unmaintained
>> --it should work with FreeDOS.

Well only the GUI is public domain, but if their download
still contains "some unspecified FreeDOS kernel" then you
could ask them to make licensing clear on their page and
in their download. If you sense a GPL violation, you can
ask Shane for advice, he is an expert for handling that.

Eric

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-kernel mailing list
Freedos-kernel@...
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-kernel mailing list
Freedos-kernel@...
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

From forum: FreeDOS - Kernel

Re: NOT PUBLIC DOMAIN (was Re: Possible size optimizations, kernel build 2039 bug in tracker)

2009-11-28T05:26:17Z

Hi Pat,

> Allow me to make this perfectly clear: the FreeDOS kernel
> *IS NOT PUBLIC DOMAIN* and will never be.
> Please do not spread such rumors.

I do not see such rumors but...

>> OFFTOPIC: JaguiD (Java with GUI for DOS) might be worth testing;
>> the Ikon GUI, offered commercially this fall as an OS with some
>> (unspecified) FreeDOS kernel, is now public domain/unmaintained
>> --it should work with FreeDOS.

Well only the GUI is public domain, but if their download
still contains "some unspecified FreeDOS kernel" then you
could ask them to make licensing clear on their page and
in their download. If you sense a GPL violation, you can
ask Shane for advice, he is an expert for handling that.

Eric

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-kernel mailing list
Freedos-kernel@...
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

From forum: FreeDOS - Kernel

NOT PUBLIC DOMAIN (was Re: Possible size optimizations, kernel build 2039 bug in tracker)

2009-11-28T05:19:04Z

Allow me to make this perfectly clear: the FreeDOS kernel * IS NOT PUBLIC DOMAIN* and will never be. Please do not spread such rumors.

Just to make mys elf perfectly clear, the FreeDOS kernel *IS NOT PUBLIC DOMAIN*. In fact, unless a package has documentation that says it is public domain, make no assumptions of its copyright. Any package in FreeDOS, unless so deemed by its author, *IS NOT PUBLIC DOMAIN*.

Pat

On Fri, Nov 27, 2009 at 11:33 PM, <ibid_ag@...> wrote:

Hello all,
1. I saw a bug in the tracker
(http://sourceforge.net/tracker/index.php?func=detail&aid=2901916&group_id=5109&atid=105109)
regarding creation of cross-linked files on FAT32; this bug is new in
2039/not present in 2038.
Seems to be very serious, but perhaps rare.

2. Size optimizations again
Could nonls be re-enabled, since 2039 OW/UPX kernels seem to be about 2-4
kb larger than 2038.?

Also, could the "LFN helper api" be commented out of the default build?
The code in question is not current (reserves 3 fnodes, when only 2 are
presently in use), and it is only a backend for an unwritten TSR.

Would anyone be interested seeing the no-hd patches (and related
stuff) merged into the tree as a build option (eg "build fat16 nohd")?
For what it's worth, this sounds like CD and _perhaps_ USB drivers would
work, but not native USB boot (emulates HD), flash chips, or any bios
drivers that don't use a floppy or floppy emulation. But we have two
people who use it...Are there any more?

Thanks,
Ibidem

PS-
I looked up the Linux VFAT patent-avoidance patch (hack), and it seems to
be less critical than I thought: It is a patch that enables a build
configuration option (not identified). If the Linux kernel config does
not show this option, it was not applied; if it shows the hack as not
enabled, the code was not used.

OFFTOPIC: JaguiD (Java with GUI for DOS) might be worth testing;
the Ikon GUI, offered commercially this fall as an OS with some
(unspecified) FreeDOS kernel, is now public domain/unmaintained--it should
work with FreeDOS.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-kernel mailing list
Freedos-kernel@...
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

From forum: FreeDOS - Kernel

Re: Possible size optimizations, kernel build 2039 bug in tracker

2009-11-28T01:32:12Z

> I saw a bug in the tracker
> http://sourceforge.net/tracker/index.php?func=detail&aid=2901916&group_id=5109&atid=105109
> regarding creation of cross-linked files on FAT32; this bug is new in
2039/not present in 2038.
> Seems to be very serious, but perhaps rare.

YES it is, I discovered one more corrupt file on my disk. Someone can
look into this please ???

> 2. Size optimizations again

The must-fix for 2040 is the cross-link BUG, not size :-(

> I looked up the Linux VFAT patent-avoidance patch (hack),
> and it seems to be less critical than I thought:

Ugly hack :-(

See: http://www.bttr-software.de/forum/forum_entry.php?id=6919

--
~~~ wow ~~~

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-kernel mailing list
Freedos-kernel@...
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

From forum: FreeDOS - Kernel

Possible size optimizations, kernel build 2039 bug in tracker

2009-11-27T20:33:35Z

Hello all,
1. I saw a bug in the tracker
(http://sourceforge.net/tracker/index.php?func=detail&aid=2901916&group_id=5109&atid=105109)
regarding creation of cross-linked files on FAT32; this bug is new in
2039/not present in 2038.
Seems to be very serious, but perhaps rare.

2. Size optimizations again
Could nonls be re-enabled, since 2039 OW/UPX kernels seem to be about 2-4
kb larger than 2038.?

Also, could the "LFN helper api" be commented out of the default build?
The code in question is not current (reserves 3 fnodes, when only 2 are
presently in use), and it is only a backend for an unwritten TSR.

Would anyone be interested seeing the no-hd patches (and related
stuff) merged into the tree as a build option (eg "build fat16 nohd")?
For what it's worth, this sounds like CD and _perhaps_ USB drivers would
work, but not native USB boot (emulates HD), flash chips, or any bios
drivers that don't use a floppy or floppy emulation. But we have two
people who use it...Are there any more?

Thanks,
Ibidem

PS-
I looked up the Linux VFAT patent-avoidance patch (hack), and it seems to
be less critical than I thought: It is a patch that enables a build
configuration option (not identified). If the Linux kernel config does
not show this option, it was not applied; if it shows the hack as not
enabled, the code was not used.

OFFTOPIC: JaguiD (Java with GUI for DOS) might be worth testing;
the Ikon GUI, offered commercially this fall as an OS with some
(unspecified) FreeDOS kernel, is now public domain/unmaintained--it should
work with FreeDOS.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-kernel mailing list
Freedos-kernel@...
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

From forum: FreeDOS - Kernel

DISPLAY problem

2009-11-27T11:20:07Z

I just run some tests and fount the problem with DISPLAY...

Older version 0.11 could be loaded with
DISPLAY CON=(VGA,,1)

but new version 0.13b only accepts Ega:
DISPLAY CON=(EGA,,1)

I consider this a BUG because it will disrrupt existing instalations.
Can this be fixed? Please?

Is Aitor around? it's been a while since I heard news...

Alain

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-devel mailing list
Freedos-devel@...
https://lists.sourceforge.net/lists/listinfo/freedos-devel

From forum: FreeDOS - Dev

Re: New Distro: checking everything

2009-11-27T07:03:07Z

I used yesterday JEMMEX 7.52 it this way:

Config.sys:
device=c:\dos\jemmex.exe NOEMS X=TEST

Autoexec.bat:
XMSDSK 40000 v: /C2 /T /Y

And XMSDSK just crashes and the system halts... only phisical reset works

The only thing that I have to say is that this is a "just a little
problematic MB". I have some others that I classify as "very problematic
B" from ASUS, but I don't have one around.

Alain

Christian Masloch escreveu:

> Hi Alain,
>
>> JEMMEX crashes XMSDSK, so it could crash other programs and I did no
>> further test.
>
> I often use both together without issues. Maybe you could report the bug
> that you experience? When did you test JemmEx?
>
> Regards,
> Christian
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-devel mailing list
Freedos-devel@...
https://lists.sourceforge.net/lists/listinfo/freedos-devel

From forum: FreeDOS - Dev

Re: New Distro: checking everything

2009-11-27T06:54:10Z

Ah, I forgot to report of one...

SUBST is working fine, all past problems seem to have been fixed.

Alain

Alain Mouette escreveu:

> Hi all,
>
> I am making a new version of my mini FreeDOS distro, so I put togheter
> all latest versions. Here is What I Get:
>
> KERNEL svn1500 is plain *marvelous*. When my program crashes (with many
> database files open) it no longer looses anything, I only get a few lost
> clusters. (this did not happen with svn1475)
>
> SHSURDR (fdrv-3) is very good. In fact it is the only RAMDISK that gives
> me 40Mb of RamDisk flawlessly (so far)
>
> EMM386+HIMEM from Tom Ehlet (iirc with Michael Devore) is still
> the-best. But only version 2.26
>
> JEMMEX crashes XMSDSK, so it could crash other programs and I did no
> further test.
>
> DISPLAY v013b doesn't even load. I had to go back to 0.11 which works
> fine. Because of that I had to use an older MODE 30nov2004 because new
> mode does not recognize old display.
>
> KEYB 2.00 does not accept a special BR.KL that H.Peron adapted for me. I
> had to go back to 2.0(pre2)
>
> LABEL is fine, I just found the new version ...
>
> EVERYTHING ELSE IS WORKING JUST FINE :) :) :) :) :) :) :) :) :) :) :)
>
> I will report any further develpment...
>
> My personal phylosophy about this distro was already discussed here. It
> was debated and considered wrong... So I will ot discuss it any more, it
> is just for me and my dear users.
>
> Thanks to all,
> Alain
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Freedos-devel mailing list
> Freedos-devel@...
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-devel mailing list
Freedos-devel@...
https://lists.sourceforge.net/lists/listinfo/freedos-devel

From forum: FreeDOS - Dev

Re: New Distro: checking everything

2009-11-27T04:52:30Z

Hi Alain,

> JEMMEX crashes XMSDSK, so it could crash other programs and I did no
> further test.

I often use both together without issues. Maybe you could report the bug
that you experience? When did you test JemmEx?

Regards,
Christian

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-devel mailing list
Freedos-devel@...
https://lists.sourceforge.net/lists/listinfo/freedos-devel

From forum: FreeDOS - Dev

New Distro: checking everything

2009-11-26T17:44:46Z

Hi all,

I am making a new version of my mini FreeDOS distro, so I put togheter
all latest versions. Here is What I Get:

KERNEL svn1500 is plain *marvelous*. When my program crashes (with many
database files open) it no longer looses anything, I only get a few lost
clusters. (this did not happen with svn1475)

SHSURDR (fdrv-3) is very good. In fact it is the only RAMDISK that gives
me 40Mb of RamDisk flawlessly (so far)

EMM386+HIMEM from Tom Ehlet (iirc with Michael Devore) is still
the-best. But only version 2.26

JEMMEX crashes XMSDSK, so it could crash other programs and I did no
further test.

DISPLAY v013b doesn't even load. I had to go back to 0.11 which works
fine. Because of that I had to use an older MODE 30nov2004 because new
mode does not recognize old display.

KEYB 2.00 does not accept a special BR.KL that H.Peron adapted for me. I
had to go back to 2.0(pre2)

LABEL is fine, I just found the new version ...

EVERYTHING ELSE IS WORKING JUST FINE :) :) :) :) :) :) :) :) :) :) :)

I will report any further develpment...

My personal phylosophy about this distro was already discussed here. It
was debated and considered wrong... So I will ot discuss it any more, it
is just for me and my dear users.

Thanks to all,
Alain

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-devel mailing list
Freedos-devel@...
https://lists.sourceforge.net/lists/listinfo/freedos-devel

From forum: FreeDOS - Dev

looking for LABEL latest version

2009-11-25T15:55:12Z

Hi,

I am looking for the newest LABEL version

=> on IBIBLIO there is a 122 version, dated 2000

=> I have a version 1.4b dated 2003 (I lost the original .zip)

Does anyone have any information?

thanks,
Alain

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-devel mailing list
Freedos-devel@...
https://lists.sourceforge.net/lists/listinfo/freedos-devel

From forum: FreeDOS - Dev

Re: suggestion - put kernel svn revision version number in sys config data

2009-11-24T07:05:00Z

Christian Masloch escreveu:

>> Alain mentioned that it is hard to keep an overview which
>> kernel file is which version, for example if you want to
>> report a problem or want to compare kernels. For that it
>> would be a great help to put for example the SVN release
>> number in there. SYS CONFIG can then be used to show it
>> for any kernel file without having to boot with the file.
>
> Any chance there will be a (21.33FF style) call to retrieve that number
> from the running kernel too? You can't be sure that the kernel file on C:
> or A: or wherever is the one actually running. (Assuming a standard
> system, the file still could have been updated to another kernel revision.)

Suggestion: it could be added to the Kernel Id string, like "SVN:1500".
Today it has prety useless information, mine just says "FreeDOS Kernel
version 0.0.35" (re-translation) which is not to be cross referenced
with anything.

It would be nice to have that string as plain text in the binary too!!

Alain

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-kernel mailing list
Freedos-kernel@...
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

From forum: FreeDOS - Kernel

Re: suggestion - put kernel svn revision version number in sys config data

2009-11-24T05:36:27Z

> Alain mentioned that it is hard to keep an overview which
> kernel file is which version, for example if you want to
> report a problem or want to compare kernels. For that it
> would be a great help to put for example the SVN release
> number in there. SYS CONFIG can then be used to show it
> for any kernel file without having to boot with the file.

Any chance there will be a (21.33FF style) call to retrieve that number
from the running kernel too? You can't be sure that the kernel file on C:
or A: or wherever is the one actually running. (Assuming a standard
system, the file still could have been updated to another kernel revision.)

Such a 21.33Fx call could also return the build number for convenience,
possibly with a special value such as 0 or -1 if it's no official build.

> The config would still be less than 16 bytes with version
> number in it. I think it would be a valuable small extra.
> Putting the SVN release number will only add a 16 bit int.

A 16-bit "int"errupt? Okay, I know what you mean and the kernel is
developed mostly in C anyway and sorry for that :/

Why is it important to fit the CONFIG area into 16 byte?

Regards,
Christian

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-kernel mailing list
Freedos-kernel@...
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

From forum: FreeDOS - Kernel

suggestion - put kernel svn revision version number in sys config data

2009-11-23T14:13:25Z

Hi all,

Alain mentioned that it is hard to keep an overview which
kernel file is which version, for example if you want to
report a problem or want to compare kernels. For that it
would be a great help to put for example the SVN release
number in there. SYS CONFIG can then be used to show it
for any kernel file without having to boot with the file.

Example: Current SVN version of the kernel is 1499 since
22 Aug 2009, or if you include SYS: 1500 since 13 Nov.

The latter calls itself version 3.6e by the way, but SYS
can easily show a version of itself, a kernel cannot :-).
The SYS update is for handling "SYS X: bootsect.bin" runs.

You can get automated builds from fdos.org/kernel/ which
also has http://fdos.org/kernel/latest/ which is the most
recent SF.net file release, FreeDOS 2039, SVN 1494 if the
history.txt in there did not miss any :-). Looks good!

The config would still be less than 16 bytes with version
number in it. I think it would be a valuable small extra.
Putting the SVN release number will only add a 16 bit int.

Opinions? Comments?

Eric

PS: FD Changes since 1494: 1495 update history.txt itself,
1497 update LSM to have only placeholders instead of real
version/date and add BAT to fill in data, 1498 support
IBM int sharing for STACKS, 1499 adjust RAM layout build.

PPS: Sorry for my big silence in the last few months, I
should really make some time free to read more DOS mail!

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-kernel mailing list
Freedos-kernel@...
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

From forum: FreeDOS - Kernel

Bootable CD issue

2009-11-23T13:13:48Z

Hi All,

I used OEM CD-ROM discs that are on this link http://www.fdos.org/bootdisks/

Modifed as per my need, added my files and it worked.

But the issue was when I boot from USB CD-ROM, it boots but at the time of loading CD driver, it just hangs there.
It boots fine from normal CD -ROM.

Do you guys know what can be the issue?

Is it driver?

Thanks,
Arpit

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-devel mailing list
Freedos-devel@...
https://lists.sourceforge.net/lists/listinfo/freedos-devel

From forum: FreeDOS - Dev

Re: fdfullcd ISO, KINGSTON data traveler...sound drivers?

2009-11-23T10:05:36Z

Any idea which program gave the error95 message? I think it might be the
FORMAT or Fdisk program doing so, which means we'll need to figure out
how far your installation process got.
What you can do is manually run the FDISK program, create a "primary"
FAT16 (or FAT32) partition (instead of extended or logical partition),
set this created primary partition active, then reboot, then run FORMAT
C: and try the installation process again.
If that fails, also try running SYS C: right after the FORMAT step.
If fdisk/format/sys go right and the installation process afterwards
still goes wrong, please let us know. There's some tricky situations
sometimes.

Bernd

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-user mailing list
Freedos-user@...
https://lists.sourceforge.net/lists/listinfo/freedos-user

Nabble - FreeDOS

Re: NOT PUBLIC DOMAIN (was Re: Possible size optimizations, kernel build 2039 bug in tracker)

Re: NOT PUBLIC DOMAIN (was Re: Possible size optimizations, kernel build 2039 bug in tracker)

NOT PUBLIC DOMAIN (was Re: Possible size optimizations, kernel build 2039 bug in tracker)

Re: Possible size optimizations, kernel build 2039 bug in tracker

Possible size optimizations, kernel build 2039 bug in tracker

DISPLAY problem

Re: New Distro: checking everything

Re: New Distro: checking everything

Re: New Distro: checking everything

New Distro: checking everything

looking for LABEL latest version

Re: suggestion - put kernel svn revision version number in sys config data

Re: suggestion - put kernel svn revision version number in sys config data

suggestion - put kernel svn revision version number in sys config data

Bootable CD issue

Re: fdfullcd ISO, KINGSTON data traveler...sound drivers?

Re: Calling soundblaster driver from C

fdfullcd ISO, KINGSTON data traveler...sound drivers?

Re: Calling soundblaster driver from C

Fwd: DOSLFN discussion on FreeDOS user list

Re: Help with Ethernet/Wattcp

Re: Sys crashes when specifying file, kernel tree-screenshot

Calling soundblaster driver from C

Re: Help with Ethernet/Wattcp

Help with Ethernet/Wattcp

Re: DOSLFN and File Wizard

Re: DOSLFN and File Wizard

Re: DOSLFN and File Wizard

Re: 7-zip LZMA encoding is here

Re: website design

Re: Update,and info,problems

Re: Sys crashes when specifying file, kernel tree

Re: Sys crashes when specifying file, kernel tree

Sys crashes when specifying file, kernel tree

Re: website design