Hi Michael,
>> There are new EMM386 2.11 troubles: Jazz Jackrabbit
>> crashes (returns to DOS) with either a page fault or
>> a GPF as soon as you use the NOEMS option of EMM386
>> now. Lemmings 3d needs a page frame anyway, so it
>> "cannot find EMS" if you use the NOEMS option...
>> The Stargun
> Also the call to INT67/3F was also commented out just temporarily
> and reactivated later. It's a feature!!! :)
As this means "you temporarily locked the real and virtual A20
to on", and as you call it a "feature", I have two comments...
1. toggling the virtual A20 by remapping a few pages is
Hi BAHCL,
> FreeDOS mailing list has never been the friendly place to me dispise its
> noble goal that win my admiration. Conflicts among members over minor
You could have found a more positive opening for your mail ;-)
> issues are not uncommon, insulting words like fool, idiot, stupid are
> j
Hi Michael!
Very nice analysis :-).
I hope you also like my kernel patch for it...
> While testing out a users bug report, I found a terribly obscure difference
> between the way MS-DOS kernel works and FreeDOS kernel works. It shouldn't
> matter, but it does to QuickBASIC 4.x applications, at
Hi!
Try www.bootdisk.com. ...
>>> Is that legal?
>> Nope.
> So FreeDOS 1.0 will be buggy software,
> created using illegal software.
I would not say so. Michael compared MS DOS behaviour to
FreeDOS behaviour to find a bug. To ensure compatibility
(interoperability), even limited reverse e
Hi!
>> --- kernel/memmgr.old 2006-08-18 10:22:33.0 +0200
>> +++ kernel/memmgr.c 2006-08-18 10:22:33.0 +0200
>> @@ -66,7 +66,12 @@
>> /* join both MCBs */
>> p->m_type = q->m_type; /* possibly the next MCB is the last one
>> */
>> p->m_size += q->m_size
> A:\>if not errorlevel 4 getargs > temp.bat [Yes=ENTER, No=ESC] ?
> # I needed to press ENTER twice on the line above
Yes, because the echo-ed command itself is also sent to temp.bat...
Redirection combined with single-stepping has a bug.
> A:\>A:\>getargs [Yes=ENTER, No=ESC] ? [Yes=ENTER, No
Hi Blair, I did not check the updated htmlhelp (could some
more documentation-oriented people have a look?), but I did
test your new iso :-). As said in my earlier mail, most of
the new changes are very nice, thanks :-). The install now
works without any real problems - APART FROM the fact that
is
Hi Joris,
as far as I know, Blair now included mem 1.9a3 on the ISO...
> I just tested MEM.EXE 1.9a3 and it has the same issue as MEM 1.9a2.
Yes. The cpu check should be fixed. Could you provide a patch
or even a patched version? The maintainer seems to be missing
in action. Mail me off-list if
Hi all,
I uploaded a new MEM 1.10 to SourceForge, based on 1.9a3:
http://freedos.sourceforge.net/mem/mem110.zip
(Dutch, Spanish and Italian translation not updated yet)
* applied a patch from Joris van Rantwijk to fix the 386 detection:
the old version 1.9a3 failed to recognize 8086
Hi Imre, you are right, actually several files
contained Linux style line endings. Probably
somebody used a Linux cvs client to download
them and forgot to convert the line endings
back to CRLF. By the way, when you upload things
to cvs with a Linux client, you also have to
convert to Linux style
Hi all,
uploaded to http://www.freedos.org/mem/ you can now
find mem111.zip :-)... Unfortunately I lost parts of
the mem 1.10 sources in the course of creating 1.11,
so if you still have a copy, we could upload that
to freedos.org again. I have recreated the lost part
based on 1.9a3, hopefully no
Hi Tom,
as you asked on the list, I will reply on the list as well:
snip
> patch --help
Usage: patch [OPTION]... [ORIGFILE [PATCHFILE]]
Input options:
-p NUM --strip=NUM Strip NUM leading components from file names.
-F LINES --fuzz LINES Set the fuzz factor to LINES for ine
Hi all,
Blair pointed me to the fact that "source" packages
are not supposed to contain docs, according to our
specs. I object that recommendation. In my opinion,
"source" packages should contain everything outside
the bin directory, and "binary" packages should
contain everything outside the sou
Hi!
> Let me disagree. "Source package" should contain only sources and other
> files, which not need for program' user (not developer). "Binary package"
> shouldn't contain these files. For example, doc/emm386/build.txt should be
> present only in sources package, but it not need in binary p
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. Bec
Hi all,
after more than a year without updates, I uploaded a new
version of LBACACHE (includes TICKLE). This semi-critical
update fixes a hang which could happen with FDAPM. Thanks
to Arkady for explaining the bug background and solution.
You can get the updated version at:
http://www.coli.uni-
Hi Imre,
nobody would complain if DEFRAG needed a 386 and XMS
to do defragging on FAT32... Ever seen a FAT32 drive
in a PC-XT...? And about Wine for DOS: Okay, with
HXRT, you can even run some Windows programs in DOS,
but if you have reasonably new hardware, you can
equally well use ReactOS or Li
Hoi Imre,
you cannot do decent checking in 100 lines. dosfsck
is 4600 lines long as well... And it checks for many
aspects of filesystem consistency.
Only 15pc of that are for the lowlevel disk access:
dosfsck without DOS support is still 4000 lines long.
Maybe the reactos chkdsk just ask the k
Hi Aitor (and hi Blair !)
> I am trying to download the kernel binary, and I find the ibiblio
> stuff a bit confusing, even if I read the list regularly (so figure
> out for those that don't :)). Here we go: I click to
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/kernel/
> and th
Hi Imre,
> Well I think what we are realy missing is a good BASIC compiler.
> Something like QuickBASIC. Free BASIC has something like that but
> that works only in 32 bit.
As http://www.freebasic.net/index.php/about?section=diff
shows, FreeBASIC is very close to QuickBASIC already. And
386+ PCs
Hi!
On Mon, 18 Sep 2006, Ladislav Lacina wrote:
> I found in internet source files of Turbo pascal 6.0
> If is someone interrested in it write me to mail.
Ladislav, as you have been told a few days ago about
those two abandonware Basic compilers: Do NOT announce
legally questionable files here!
Hi!
On Mon, 18 Sep 2006, Frederic Logghe wrote:
> Since several years, I'm using Turbo C on MS-DOS. Last week, my PC crashed
> and I'm now planning to use FreeDOS. I just wonder if anyone has positive
> experiences running Turbo C on FreeDOS?
As Uso said:
> Turbo C++ 1.01: No problems whatsoev
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 all,
I created an initial version of a FreeDOS 1.0 install
howto, including a list of known problems and workarounds.
The text is partially based on the FreeDOS beta install
howto. Because the SF Wiki can be slow, I created a static
copy on my homepage:
http://www.coli.uni-saarland.de/~eric/F
Hi all,
>> Which first, 8086 or 80386. If the program don't need to mess with
>> memory, why not keep it 8086 based?
>
> Fully ACK! As PM apps tend to be much larger than their 8086 counterpart,
> FreeDOS would waste a lot of memory without a benefit.
I would like to add that IMHO it is a bad mo
> I'm looking from a marketing perspective. ISOLINUX throws Linux out there to
Isolinux does not contain any Linux at all.
> the enduser even though the result is FreeDOS on the machine. I think that a
> FreeDOS install CD should boot with FreeDOS, if the hardware is capable,
> jump into a 256 c
> Well, the secret to the read only image would be to create a ram disk and
> set temp there, copy a few files. Microsoft uses RAMDISK. This would allow
> the creation of temporary files as well as provide a storage for frequently
> accessed DOS commands, since CD is slower than RAM. I did some se
> I don't see a purpose in circumventing ISOLinux, and I don't see any
> future distribution not using ISOLinux.
>> Well, I played a little more with the boot CD, I have a rescue image that it
>> boots from, using SHSU ramdisk to load a FDBOOT.IMG and set that image so
>> there is TEMP space...
Hi Bernd,
> Guys, where's the best place to put some feedback on the 1.0 ISO? tiny
> bugreports and tiny enhancement ideas as well to an otherwise great
> distro already.
> * Bugzilla?
for real bugs ;-)
> * Tech Wiki?
> * Install Wiki?
you can add a note about misbehaving 1.0 things to the
ht
> You know, a small piece of code could be written to simply read the
> partition table and check for FAT/FAT32 partitions instead of the
> whole %comspec% /f thing...
The answer to this is two-fold...
First, things are not that simple. You can get drives
from various sources, and it can be comp
Hi Bart,
> First of all, I couldn't find a "kernelx.zip" package.
http://www.coli.uni-saarland.de/~eric/stuff/soft/by-others/
has kernel2036-binary.zip and kernel2036-source.zip :-)
For unstable 2037, you will have to ask Blair. But the ISO
contains the various kernel binaries in unpackaged
Hi Jim,
> E! I'd rather not go back to "beta9 SP2" etc naming scheme...
Right. I have a related question: Tom gave me a copy of his
2035-Tom kernel sources, and I included a 2037-findfirst fix
in the 2036 kernel. I might find some more useful fixes in
2035-Tom and 2037, and then I guess "20
>> Looks like this change wasn't tested.
> It looks like Eric has magic powers to produce .zip files anyway!
actually i do not use makefiles or batchfiles to create zip files.
but i have a question about the cvs kernels: which branch are you
working on? 2037 unstable or 2036 head? do you ha
Hi all, Caesar repeatedly asked me to recommend a few
useful programs for our distro. I agree that those
programs are useful and have a suitable license as well:
First, a MCGA (320x200, 256 colors) paint program:
http://www.geocities.com/yotam_madem_software/ writes
"Y.M.S Software is written in
Hi Arkady, Bart,
> This is what stops me currently from dealing with kernel, because there
> is no management centralization. Eric, do you support/control your kernel
> edition? What about Kenneth' edition? Who control and support CVS?
You can assume that I am the only maintainer of kernel 2036,
Hi Bernd!
...and happy birthyesterday ;-)
> Ladislav Lacina schreef:
>> Today I found this utility. Is it interresting for our community?...
>> http://www.phatcode.net/projects.php?id=102
[Robert commented:]
[Yes, it looks interesting, but it is freeware `only'. Not open source.]
> utility loo
Hi Blair, Markku,
there is a simple solution for your problem:
Add the games to the DOS GAMES distro on
bootablecd.de :-) That distro contains both
open and closed source games. The "normal"
FreeDOS distro focuses more on non-game
categories anyway. By the way, yesterday we
found out that the SEAL
Hi Ladislav,
> Japheth mentioned this page in DR-DOS discussion. Is there some
> interresting for FreeDOS too? http://www.deskwork.de/INFOS/DOS.HTM
Deskwork is a shareware GUI in StarTrek NextGeneration design. It can
work both in text mode and graphics mode, and it can invoke Win3 /
WfW3.11 app
Hi all, there are new mails on the -kernel list:
In two mail, I compare the "extra stable 2035c"
kernel from Tom to the current 2036 CVS HEAD stable
kernel, in the hope that both kernels can be merged
again in the near future: That way, Tom will have a
stable CVS kernel to use, and the CVS version
Hi, to re-post a recent mail of myself: There IS floppy FreeDOS!
It is based on FreeDOS 1.0 :-). However, it's been waiting for
some clean up work for a while - you have to download THREE
files to get the best versions of all parts, while it
would be much better to have ONE combined download. May
Hi Jean, I did not know that .aero domain names exist ;-).
> The intent here is not to run FreeDOS programs, but rather use FreeDOS
> as an operating system for an embedded platform. The "BIOS" we use is
> custom made. We actually call it the bootloader...
> We use it to load the OS from PROM to
Hi, you should have a look at how NWDSK does the
network card detection and driver loading :-).
One FreeDOS way to do it would be to use PCISLEEP
to list all PCI devices of the "network" category
and use the new SET /E (or so) feature to put the
first output line of PCISLEEP into an environment
v
Hi Ladislav,
> It seems that FreeDOS project is in another crisis now. There is nobody
> who develops kernel (compatibility with MS-DOS is still not perfect), we
> still lack some disk utilities for FAT32 and so on.
Well I do develop 2036, but nobody said there was a MS DOS compat issue.
Similar
Hi Florian,
> Please remove from freedos.org:
> >To run old DOS games (like DOOM, etc.)
> >To run old business software that only supports DOS
> The word "old" is very bad!
No it is not. FreeDOS is one of very few ways to run
CLASSIC software which no longer runs properly in DOS
windows of Windo
Hi Ladislav,
Please provide more details about the MGL problems.
What exactly do you do, what exactly goes wrong?
Will it work on generic hardware? Does it work okay
in EDR DOS or MS DOS 6 for example?
> ftp://ftp.scitechsoft.com/devel/demos/dos
> Japheth also reported problems with restoring i
Hi Ladislav,
> These demos work perfectly under MS-DOS. I can't test it under EDR-DOS
> In FreeDOS I get the message "Graphics driver wasn't loaded."
Well it worked for me, see the detailled explanations below.
> > > ftp://ftp.scitechsoft.com/devel/demos/dos
I got the "mglgears" thing, which s
Hi Jim,
> They hadn't paid attentions to the messages telling them they were
> about to format their hard drive, or they didn't realize what "format"
> meant, or they sort of assumed FreeDOS would somehow be smart enough
> _not_ to wipe their Windows partition. They wanted to know what I was
> g
Hi, partially agreed... Yet I think we can and should
keep several good compilers in the distro. The confusing
points of the distro are more that you have to dig through
long lists of packets and stuff. It would be nice to have
an option like "install everything which works without
network connect
Hi Ladislav,
> Is practicaly possible to compile on demand?
> I mean that on the instalation CD would be all source codes for key parts
> of FreeDOS and C compiler and all necesary things for compiling.
No, that could be a waste of space and time. The sources are often
bigger than the compiled v
Hi Tony,
> I was bored so I tried FreeDOS 1.0 and WfW 3.11.
We have a special version of kernel 2037 for that,
as Windows for Workgroups and the "386 Enhanced"
Mode of normal Windows 3 has to wrap lots of magic
around the DOS kernel to make it "multitask". So
only the special kernel will probabl
Hi Tony, Flox,
indeed I do not understand what the problem should be here...
if you have "sound drivers", then they will work with any DOS,
including FreeDOS. However, C-Media chips work really bad in
DOS in general. Old ForteMedia chips usually work better, but
even those still do not work in DO
Hi, well, honestly,
I think the most "in style" way to have an API for FDRC would
be to have a way to send strings like "4+sqrt(2)" to the
calculator and receive a string with the result. Maybe with
some extra functions like "round(2, 4+sqrt(2))" which would
return "5.41" and "hex(42)" (returns "
Hi Enrico,
for porting the FreeDOS implementation of FAT to another
operating systems, you should simplify many things. In
particular, each disk access goes through several layers,
basically because this is what MS DOS does as well and
we have to be compatible to drivers written for MS DOS.
> C
Hi Enrico, Bart,
> > The starting point of my port should be the following set of functions:
> > "DosOpen()", "DosClose(), "DosRead", "DosWrite",...
Those are how the kernel implements the basic int21 functions.
The int21 handler is only a thin wrapper in this area.
> > And not the following se
Hi Enrico,
> I can't find in the source code the place where "fnode[2]" and "fnode_fd[2]"
> are allocated:
>
> GLOBAL struct f_node fnode[2];
> GLOBAL int fnode_fd[2];
>
> The above two lines come from "globals.h"
The trick is that inthndlr.c defines MAIN, and "GLOBAL"
is only "external" if MAI
Hi Enrico,
> What I need to know to proceed, is how you guys configure FreeDOS at
> compile time. In particular, I need to assign an initial value to
> variables like: "f_nodes_cnt", or structures like "buffers" list...
That is not a compile time thing. Most of those variables are in
kernel.asm
Hi, I looked into your problem description now...
The "condition is always true" cases are intentionally,
but maybe I should remove the "if (TRUE)" to make that
clear... Actually I had assumed that you only get a
warning when you have "if (some always true expression)"
and not when you use the "o
Hi Enrico,
> In principle, I would like FFS to be able to handle
> pathnames longer than 67 and possibly read Unicode filenames.
But then it would not be compatible to FAT. If you want to
have long unicode file names, then you have to implement
exactly that - LFN. Look at doslfn. But watch out,
Hi, this sounds like a wrong error message.
Having more than 64k heads or sectors-per-track is just
a sign of implausible extended geometries. The real limit
tested for is 2 Terabyte (more than 4 G total sectors)...
However, maybe the fallback is to use CHS if the LBA data
is implausible - then y
Hi Enrico,
> I read carefully the following document about CHS and LBA...
> http://www.ata-atapi.com/hiwchs.htm
> My guess...
> My guess 2...
> My guess 3...
There is really no need to guess here ;-).
Just read the rest of the code of
STATIC int LBA_Get_Drive_Parameters(
int drive, struct D
Hi all,
when looking into a bug report about a funny character
device driver which is "writeonly", I found something
problematic in our FreeDOS kernel sources. For more
details, check the snippets of FreeDOS 2036 below, or:
http://freedos.cvs.sourceforge.net/freedos/kernel/kernel/chario.c?revisi
Hi Enrico,
> 1. How does FreeDOS to detect and read a LFN entry?
It does not
> 2. How FreeDOS writes a LFN entry?
It does not
Both functions are implemented in driver TSRs like DOSLFN, which
split long Unicode file names into short UTF-16 fragments which
are stored in special "invalid" dire
Hi Enrico,
> Microsoft created ad-hoc functions to deal with UNICODE filenames
> ... Linux allows the caller of fopen() to inject UTF8 names
There is really no need to inject or trick anything here. Just
implement the PROPER long file name functions int 21.71nn...
http://www.ctyme.com/intr/rb-3
Hi Enrico,
> I noticed that in this version of FreeDOS, the function:
> Upmem (unsigned char* str, unsigned int len)
> is missing and the filesystem seems case sensitive.
> I indeed can't open an existing file, named "foo.txt", when I call:
> dos_open ("Foo.txt,..,..);
Interesting. There are
Hi Enrico,
> there are no "toupper" or similar function calls from dos_open()
> down to exechr().
This is because the case (in) sensitivity handling happens in
DosOpenSft which in turn calls dos_open. So dos_open is one
step too "lowlevel" to be case insensitive. Other functions
seem to call tru
Hi Enrico,
> The function works if I rewrite get_f_node() in the following way:
...
> for(i = 0; i < NFILES; i++)
...
> if(f_nodes[i].f_count == 0)
...
> return &f_nodes[i];
...
> This was the implementation present in the source tree four years ago.
The difference in the c
Hi Ladislav,
> Is possible to call a software interrupt from hardware interrupt? I
> want to call INT33h/AX=3 from INT 1Ch handler. And this all works in
> protected mode. I tried to call INT33h through DPMI service 31h but
> it crashed. Is it possible at all?
Yes, sure, but you must avoid calli
Hi Tony,
> If I remember correctly, the mouse comes in on Int 15h (if PS/2)
No int15 is the BIOS based driver... The data comes in via an IRQ
handler. Some mouse drivers use int15, others use their own IRQ
handler... To reduce the number of context switches, you can make
your own IRQ handler whi
Hi Alain,
> > thanks for hunting the SUBST bug! Look at bugzilla,
> > it should be a known bug.
> Which bugzilla? I'd appreciate if you sent me a link ;-)
www.freedos.org/bugzilla/cgi-bin/buglist.cgi?bug_status=__open__
www.freedos.org/bugzilla/cgi-bin/show_bug.cgi?id=1862
> Let me explain: som
Hi Alain,
> I am not sure which version I have, it is the one I translated an then
> lost the sources (when I was robbed). I will test with a later one.
> Where should I get the latest (binary) from?
I still suggest to extract the translation from your binary...
Kernel and FreeCOM command.com d
Alain,
> Can anyone tell me where to fing "Bart's Network Boot Disk"???
Very simple: www.google.de/search?q=bart+network+boot+disk -->
Bart's www.nu2.nu/bootdisk/network/ :-p.
Another nice disk is www.veder.com/nwdsk/ netware boot disk
Eric
---
Hi Alain,
> That is why I asked... there is nothing more there to download...
> Thanks to M$ lawyers
Hmmm? Does http://www.nu2.nu/bootdisk/network/makedisk/ and
http://www.nu2.nu/bootdisk/network/makedisk-old/ not have
all the files that you need to make such a boot disk? See
also http://www.nu2
Hi Alain,
> What I need are the latest drivers for network cards
http://www.crynwr.com/
> There is another thing: that machine has a working NIC from nVidea, but
> there is no PCI device in group 0x0200, apparently it is part of another
> chip and I will need to guess which one to use in my aut
Hi Ladislav,
> Hello all, I wrote small and simple program which can detect
> any device attached to parallel port.
> (It displays parallel port Plug and play device info)
> Maybe it isn't so useful for end users but may help to programmers.
> URL: http://www.laaca-mirror.ic.cz/lpttest.zip
I wou
Hi Jim, I think I use a reduced local install. My .xinitrc says:
mkfontdir $HOME/.dosemu
xset fp+ $HOME/.dosemu
... where ~/.dosemu contains my copy of vga.pcf.gz ...
(no fonts.* and no other *.pcf* files there)
> In the /share/dosemu/Xfonts directory, you should find several
> pcf.gz font
Hi all,
> I added help screen, possibility to scan other LPT ports and a little
> modyfied delay routine. For help screen write lpttest /? link:
> http://www.laaca-mirror.ic.cz/lpttest.zip
(compiles with TASM and TLINK)
I have thrown Michael Devore's NoMySo Perl script at the source
and made a N
Hi Ladislav,
> > You _need_ to include a copy of the GNU GPL with a copy of your
> > program. I don't see one here. This file is usually named COPYING.
> But it has no sense. LPTtest is supposed to be a part of FreeDOS and
> FreeDOS itself has own copy of COPYING. Why should every small binary
>
Hi Ladislav,
> Wow! It is a touch of master!
Thanks, but a real master would have fixed the "out base,4 only if"
problem before uploading ;-).
> Despite I prefer TASM conventions your code is much cleaner...
Yeah I made sure that all commands are indented by 1 tab and all
comments are indented
Hi all,
I did some experiments with ieee1284 plug and play
handshaking, based on the docs on fapo.com ... Yes
I know that Public Domain means "everybody can do
everything with it, including removing any mention
of me as the author". Anyway. Here is what I found:
Default data, control, status in
Hi all,
I have been busy with bug 1840:
www.freedos.org/bugzilla/cgi-bin/show_bug.cgi?id=1840
"sys a: b: requires numerous disk swaps with single floppy system"
SYS 3.2 needed at least 15 disk changes to copy kernel and
shell and write a boot sector if you had a system with only
one diskette dr
Hi Bernd,
> As Eric Auer released a "bugzilla SYS 3.3" which starts confusing as
> unofficial 3.x versions already exist,
I agree that the "unstable kernel" SYS (which is also in the
subversion system, but in a separate branch) should have a
version number which i
Hi Tom, thanks for the hints!
> TURBO C/FAT32:
> you mentioned 'linker complains: TGROUP exceeds 64KB' somewhere.
>
> TGROUP is *all* code called near and is a fundamental limit of small
> memory modell. If that's the problem, you got a real problem, as the
> kernels memory model is a bit complic
Hi Bart!
> > - SYS OpenWatcom farmalloc
> I see you worked around that now in SVN. But I wonder, since you use
> allocmem() already for Turbo C, why not also use _dos_allocmem()
Feel free to add this, as long as it does actually work :-)
While you are at it, you may want to remove the "shrink to
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, which
Hi Bernd,
> > I notice you forgot the --8086 when running UPX!
> > You could also use --ultra-brute instead of --best but that
> > is slower and it is UPX 2.0 incompatible so it should be the
> > non-default option if you ask me.
> Be carefull with UPX 3.01, their forums mention the switches ha
Hi Tom,
> > - FreeCOM stops to run external commands sometimes
> > (internal commands keep working)
> is that a (newly introduced ? ) kernel or Freecom bug ?
This is a FreeCOM 0.84 bug, one of the reasons why I still
prefer 0.82pl3 as more stable FreeCOM where no LFN are used.
> > old bug but
Hi Bart,
thanks for making SYS more elegant again and for re-introducing
the file timestamp copy function :-). Having separate readfile
and writefile makes the diff longer but the code cleaner :-).
About the exeflat thing: Makes the makefile simpler but makes
crosscompiling harder, if anybody wa
Hi FreeCOM experts,
could somebody modify the context memory display to make it
a bit more correct? Problem is that it has many translations
which will need adjustment, but even that should be possible
without speaking the languages :-) Thanks in advance!
The command in question is called MEMORY
Hi, update: According to SVN, the relevant areas of
FreeCOM have not changed between 0.82 and 0.84, maybe
the "0.84 shows last dir cache info in the line which
claims to be about dirstack, and shows all-0 values in
the line about last dir cache" problem is because some
context memory info data str
Hi Imre,
> Does anybody know what the status is of long file name support in
> freecom. There is absolutely a compile time option you can use,
> but does it work (well)?
FreeCOM 0.84 arguably has far too many changes with far too little
review (compared to 0.82pl3) but those changes do mean tha
Hi XO,
> I plan to buy OLPC XO laptops from One Laptop Per Child project.
> 1. There is no standard BIOS on the laptop.
> 2. There is no VGA/EGA/CGA display mode on the built-in display
> Is it possible to port FreeDOS to this new AMD Geode laptop?
I think the OLPC will run on Linux. And on Linu
Hi Robert, XO user, others,
> > sort of graphical layer since there is no (S)VGA standard
> > implementedin fact, the graphical controller is embedded in the
> > Geode chip and i'm not sure if it implements some standard at all
> Why not read the Geode LX data book at
> www.amd.com/us-en/Con
Hi Japheth,
(changing subj from "Some FreeDOS kernel bugs reported by
Jack R. Ellis" and moving the issue to freedos-kernel...)
> ... just reported a bug/issue found in the FreeDOS kernel:
> http://www.bttr-software.de/forum/...
I guess a few people will have bad mood after reading this,
so it
Hi everybody,
my current homepage is about to expire, so I am looking for
a new place to store my stuff. The page is less than 100 MB,
of which maybe 1/4 DOS and 1/4 pics. Hosting the DOS stuff
has priority, but I would like to have a bit of space for
my personal homepage as well. The page should
Hi Pat, nice to hear from you :-)
> If you folks were to extend the DOS API, in which direction would you
> take it? Would you go with POSIX/UNIX/Linux, win32 or simply provide
> the same API with extensions for modern functionality and platforms?
Well OS/2 once was a pretty nice and straightfo
Hi Paul,
> SMB/CIFS client would be very nice, it would be nice if it also
> provided some sort of standard TCP/IP implementation as well ...
The other way round - you need TCP/IP to have a network file system
client like SMB/CIFS. And because a client like Samba would be TSR,
you are right that
Hi Pat,
> 3. A built-in network TCP/IP stack.
I would not build it into the kernel, but making Wattcp sort of
modular, with a resident part, would be useful. For example it
would avoid the "do DHCP handshake again for each app" thing.
> real mode execution on ia32 and x86_64, and emulation on o
Hi Johnson,
> IMO, a smaller, solid and flexable kernel is highest priority.
Our kernel is only ca 40 kilobytes on disk, which is quite small.
> Kernel grows bigger each release, but the compatibility with MS-DOS
> still not finished, the syntax in CONFIG SYS still have a big diff
Agreed, the
Hi everybody,
Tom just said in the "A Poll of sorts" thread on -devel:
> just kick out the useless 2037 kernel
> (merge any useful stuff into 2038); that's it
Unfortunately, 2037 has an immense amount of changes
and is based on 2035a. Still it would be interesting
if people could mention some e
801 - 900 of 1242 matches
Mail list logo
