Subject: [Freedos-devel] FreeDOS ODIN 0.6
http://fd-odin.dosius.com
disk image and source zips.
This is basically just the beta slimmed down. Haven't had a lot of time
to work on it beyond that. (Busy waiting for the next ep of live-action
Sailor Moon to go up on torrent) ^^;
-uso.
An executable compressor is no different than a compiler/linker.
The exe compressor is a major component of the OS (at least
for the purposes of FreeDOS) just like a compiler/linker.
The major comonents do not have to provide source (it is the
only source exemption in the GPL). Thus the source to
From: tom ehlert [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [Freedos-devel] Executable compression
SK special exception, the source code distributed need not include
SK anything that is normally distributed (in either source or binary
SK form) with the major components (compiler,
Hi, I noticed that I have not yet enabled the MODE LPTn COLS=...
feature. Reason: Nobody tested / suggested ESC sequences for
10cpi (80 column) / 15cpi (132 column) printing yet. So please test
the sequences below, which are Google-educated guesses:
ESC P
10 cpi printing. Could also be reached
Hi, to answer your question:
DOS\HELP - all help files
This contains only files which are called project.*, like
project or project.cn or project.es or project.htm ...
Actually the CURRENT way is even simpler:
DOS\HELP\ contains files which are called project. So for example
the
..
I keep my binary files inside BIN of PGnnn.ZIP now, it
looks like I ought to drop the BIN directory to align
with your idea, give me a 'yes' please.
Eric.
BAHCL
Not if you are only doing it for distribution package
reasons, otherwise go ahead. While I encourage all
maintainers to
Hi!
DOS- all exe/com/sys files
DOS\APPINFO- lsm files
DOS\DOC\project- documentation for 'project'
DOS\HELP - all help files
DOS\NLS- national language support files
DOS\SOURCE\project - source code for 'project'
Sounds okay BUT
..
DOS- all exe/com/sys files
DOS\APPINFO- lsm files
DOS\DOC\project- documentation for 'project'
DOS\HELP - all help files
DOS\NLS- national language support files
DOS\SOURCE\project - source code for 'project'
Note that the install
..
Otherwise, I agree with Arkady. No need to have 50 files called COPYING with equal
contents ;-)
..
We don't (well not really).
Within the distribution there is a package called GPLv2,
which contains nothing but the GPL license which is installed
to the base dirctory (e.g. C:\DOS\COPYING ).
Hi,
This brings a very important question: If I create an image with
FreeDOS's disckcopy, can I write it back with rawrite? Are they compatible?
Alain
As long as you don't use compressed images, images that add
a header (such as an executable stub to write the image to
floppy), then all
I have slightly modified smart boot manager 3.7-1 to work as a comboot file
with syslinux. Once added to syslinux menu, one can boot to syslinux and
chain boot sbm, which can then boot a CD-ROM :-) and use
Bart's el-torrito CD-ROM driver. I use SBM on my 486 (which lacks
el-torrito support in
..
Please take a look and comment, try my best to improve.
http://johnson.tmfc.net/freedos
P.S. The most headache is the geographic location.
Rgds,
Johnson.
Minor correction, I'm from North Carolina not Florida.
Jeremy
:-)
---
SF.Net is
This is very cool!
Is it stable enough for me to update my weekly built
boot disks with or should I wait a while longer?
Thanks,
Jeremy
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel
Michael Devore wrote:
...
I'll make a bugfixed EMM386 available soon.
cool! Thank you for your all your work debugging these problems!
Jeremy
(While I appreciate all the hard work of all the FreeDOS devs,
I generally try to avoid bugging the list with constant thanks;
this just makes me really
Bernd Blaauw wrote:
Eric, other people,
the HTMLHELP problem I'm experiencing is the following:
HTMLHELP crashes if called twice and HIMEM is loaded.
At least it loads for you, on my test computer, choosing
option one (with himem) locks my computer (have to press
the reset button or power off/on)
Diego Iastrubni wrote:
, 14 2004, 21:30,gsan92:
Using FreeCOM in Wine
...
If you must use FreeDOS under linux, please check doesemu or dosbox.
Bernd Blaauw wrote:
Michael Devore schreef:
Since bug #1826 re: Solitarie Suite was flagged in subject as fixed in
pre-release development version, can someone, such as Eric Auer,
verify that it still works in latest official FreeDOS and mark the bug
as FIXED or if not, why not? I would, but
tom ehlert wrote:
...
so I want to propose a new project (and any serious project should
...
this is a collection of almost trivial batches with a known/expected
outcome.
...
but the people working on the kernel/command.com would have some means
to verify, that a new version doesn't break old
Aitor Santamaría Merino wrote:
I can't answer anything emm386 specific, but maybe this'll help a little
until Michael/Tom/? answers.
Hi there,
I have started reading EMM386.ASM (not the latest hot version, but the
...
(2) What is the meaning of this structure? How much memory does it
weight
...
It was more interesting to have ATAPICDD in NASM, but I am not sure if
the port has the same maturity as the original MASM/TASM version. At least
it helps to test patches for ATAPICDD that it can be compiled with free
compilers / assemblers. But you still need spare time for that :-(.
...
Aitor Santamaría Merino wrote:
...
actually current ATAPICDD, which is now split into cdrom.sys
ataspi.sys to separate the CD code from the IDE/ATAPI code uses
FASM.
Could you extend a little bit on this?
ATASPI for the ATAPI/ASPI layer and CDROM over it (which means I need to
load two drivers,
David O'Shea wrote:
...
What I'd suggest is you use a binary search tree (with the key
being the filename of course); the trick being that you just use up
all the RAM available to build the tree, and if you run out before you
finish reading the descript.ion file, you remember the file
Alain wrote:
...
space and two copies of: boot sector, second stage boot sector (used
if the boot loader is bigger than 512 bytes) and filesystem info
(statistics...) sector. So 6 sectors of the first 32 sectors of the
partition contain all that stuff. Usually sectors 0, 1, 2, 6, 7, 8.
Alain wrote:
Eric wrote:
FAT32 has usually 32 reserved sectors where FAT16 has only one, the
boot sector. In those 32 reserved sectors, you have a lot of free
space and two copies of: boot sector, second stage boot sector (used
...
I copied Sector 0 to sector 6 and now fosfsck doen't not
What I usually do is old fashioned printfs [or in this case calling BIOS
print a character or a print # routine based on this, if I need to see
values], disabling a chunk of later code if necessary for the code
space. However, if you can live with GPL'd code, you may want to use
our FreeDOS
Alain wrote:
during my tests, I tried FDXMS and FDXXMS 0.93 strawberries
I get this message:
VDISK has been detected. Driver won be installed.
Nothing is installed, it must be some BIOS thing. The machine is a
PcChips with SiS742 chip, Semprom 2.2GHz.
In the docs I found no option to
Alex Buell wrote:
On Fri, 17 Jun 2005, Jim Hall wrote:
:-)
...
Yes, but that's out of date.
The source on darklogic.org is reasonably close to any released version,
as only 0.2.x alpha versions have ever been released (due to too many
projects and not enough time on my part). Yes I
Have you had a chance to put it into cvs yet?
not yet, my cable [hence internet connection] went out (and back, and
out, ...) last weekend, so I was planning to do it this weekend. check
fdos project on sourceforge.
I'm also putting the 0.2.14 source up on darklogic, it is the latest in
the
...
either it's a bug - or it's not
if it's a bug, I (speaking generally) might even find it worth fixing
...
tom
This whole discussion is both interesting and amusing (as are many
discussions here...:- )
If you guys do find the cause of the slowdown, and it is fixable, and it
is a
Alex Buell wrote:
On Tue, 5 Jul 2005, Bernd Blaauw wrote:
Owen Rudge schreef:
I'm having a go at porting FreeCOM to WATCOM. But before I do that
Have fun!
I'm trying to get it to build with TC 1.01, without much joy.
There seems to be something wrong with SUPPL.TGZ, as UNTAR.EXE
As our FreeCom maintainer is MIA, I have committed my small patchset to
FreeCom cvs (HEAD). This means a fresh cvs checkout should now compile
(after seting up compiler and config.h options). Given the changes, I
may also make a new release once I figure out what the proper version
should
...
FYI, the only changes I have planned is the enhancement for CDD to
support path ignoring any filename portion (as requested). Any patches
...
This is now implemented in cvs.
I have added support for CDD path/filename, where the filename portion
is stripped (ignored) if and only if this
I have updated my daily FreeCom builds so there are now two sets.
The cmdxms* files are same as before, 186+ xms-swap nearly all features.
Added cmd8086* files, 8086+ kernel-swap some features disabled.
Note: I switched it so the cmdxms builds have loadfix loadhi, and
these are disabled in the
Eric Auer wrote:
Hi Bernd,
I'll respond to Bernd's mail in a minute.
Jeremy, can you reduce the number of files which are downloadable?
I guess the non-XMS build is most universal, despite the high memory
consumption then.
The non-XMS build is really only useful if you cannot provide
Bernd Blaauw wrote:
Kenneth J. Davis schreef:
I have updated my daily FreeCom builds so there are now two sets.
The cmdxms* files are same as before, 186+ xms-swap nearly all features.
Added cmd8086* files, 8086+ kernel-swap some features disabled.
Jeremy, can you reduce the number
As bugzilla is still down (not that this is really there or should be) I
would like to open a discussion. I make no assertion that I will
implement any of these, but I'm curious and just may.
What features in command.com would people like to see implemented?
Please provide reference to full
1) 8086 command.com, works with CALL /S and KSSF, no loadhi/loadfix
2) 186+ xmsswap.com, including loadfix
3) 8086 xmsswap, with some disabled features as it would otherwise be
too big.
I would prefer option 3 as most optimal, but depends on what you
explicitly disabled :)
Bernd
Eric
Kenneth J. Davis wrote:
...
I disable only ALIAS support, command /Z support, dir with 4DOS
descript.ion support, loadhi, and loadfix. I'm checking now to see if
the xms-swap version builds for 8086 with these same options disabled.
...
ok, 8086 xms-swap seems to work/build with just
When using EMM386 there is a problem with help where help either
reboots or gives an error and locks-up the machine...
...
this is an old problem, and fixed, but no binary released.
...
Jeremy posted a fixed binary once, and sources, but I can't find it on
the mailinglists, and also not on
Please test, assuming no major issues pop up in the next few days, this
weekend I will be making a new official FreeCom release.
For those with a 186 or better please use
http://www.fdos.org/kernel/cmdxms.HEAD.zip (English only)
http://www.fdos.org/kernel/cmdxms.HEAD.NLS.zip (other
Alain wrote:
...
Ok, but and this remark that in in that page? Has it been fixed? It does
look strange because it is about build 2034 but tha page is dated 1
March, 2005.
FreeDOS has a problem with extended DPBs, which causes problems with
...
current kernels should be fine
Michael Devore wrote:
At 06:53 AM 7/24/2005 +0200, Eric Auer wrote:
So for a quick check, you can remove the -zff and -zgf from our
kernel makefile to see if that makes the kernel EMM386 2.04 immune.
Tests done with FreeDOS devel kernel, 386-optimized, from
http://fdos.org/kernel/ (which is
Eric Auer wrote:
...
I agree that device drivers should not modify any register when you call
them, but I admit that I do not remember WHERE I have read that device
drivers MUST not modify any registers. In particular, fixing EMM386 would
...
Well PC-DOS tech reference states regarding the
Bernd Blaauw wrote:
Kenneth J. Davis schreef:
fix: DIR/VOL: bug#1809, volume label missing spaces {KJD}
did you verify? VOL still seems to compress spaces in label
LABEL C: TEST TEST
it works for my test cases. please provide (use quotes or something so i
can tell where spaces
I have a request regarding this thread.
Please be clarify when to strip spaces, during command line argument
processing, which I believe it does or during the prompt if not
specified on command line, which I believe it doesn't. (Mind you I
didn't verify, but you get the idea.)
Thanks,
Blair Campbell wrote:
I'm REALLY sorry for all of the trouble I've caused. I just found out
that the user must have installed the 386-optimized kernel (which
needs to get removed from my distro), and that's what's been causing
the crashes.
Once more I'm REALLY sorry and I'll try to remember
K. Alekhine wrote:
Hi and thanks for the replies!
I forgot to ask in my last email
if you think any of these titles would be useful for
me;
Depends, do you want to work on the kernel or the other
programs. The first one is definitely a good read to get
an introduction to the kernel.
I'm reading through some of my older books (partly in my quest for
information about MS DOS internals and partly curiosity), and there are
some references to look at the win 3.x ddk. As this is no longer
available directly (as best I can tell it cost money at the time, so I'm
pretty sure I
Alain wrote:
Hi,
I am just starting to prepare for compiling FreeCOM. should I stick to
docs\compile.txt or is there any other explanation?
Alain
It should be fine. If you build on Windows be sure to use the win
version of nasm, and every so often the build may fail in the middle (I
maybe I was not clear, a mini suppl library is now included so you do
not have to do anything regarding it. Do not create the skip file, do
not try to download it, just ignore any mention of it existing.
(The docs still explain it because you can still use the full suppl
library and everything
regarding the descript.ion thing not working, are you sure it was
compiled in or was that why you were building? (not sure why you were
trying to build in large model though, see Tom's remarks, basically not
going to work, even if you manage to get an executable)
...
I think Jeremy's
Ladislav Lacina wrote:
OK, I will look at it.
Few months ago I wrote a small utility for SB Live! cards to enable CD
playing without Soundblaster emulation drivers. Might be useful for
someone...
http://www.laaca.borec.cz/soubory/livecd.zip
nice!
could you provide license/redistribution
Jim Hall wrote:
Webmasters will want to do a refresh of their FreeDOS.org web site
mirror. I just made a change to the css that will make your front page
look weird _unless_ you refresh.
I've also removed the FreeDOS News Bits section with a FreeDOS
Pressroom section. All the News Bits
Andreas Bollhalder wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
I use FreeDOS in the QEMU emulator for running my DOS applications under
Windows XP. Today, I testet the developer kernels.
1. The kernels compiled with OpenWatcom won't boot. They stop with the
following message:
Arkady V.Belousov wrote:
Hi!
27-Ноя-2005 12:58 [EMAIL PROTECTED] (Andreas Bollhalder) wrote to
freedos-devel@lists.sourceforge.net:
AB Something stranges happens here.
AB BUFFERSHIGH=29 - 615kB conventional and 150kB upper memory free
AB BUFFERSHIGH=30 - 599kB conventional and 150kB upper
tom ehlert wrote:
Hello Kenneth,
With several of my changes/additions the size of the
kernel has grown
just a few cents:
a) are human beings like me supposed to locate kernel sources ?
how about a link where one can download it without knowing where it
is ?
they are in the same
tom ehlert wrote:
...
I wrote that after spending a couple of successless minutes to locate
the kernel (or freecom) source, starting from www.freedos.org
just try software-base-kernel-kernel.lsm and you are either on a
dead link or on the same page again :(
www.fdos.org/kernel/
I know
Kenneth J. Davis wrote:
...
I may make patch sets or test binaries available at
http://www.fdos.org/kernel/test/ (or for short descriptions use
http://www.fdos.org/AuoIndex/index?dir=kernel/test/ )
:-)
Jeremy
sorry the above url should have a 't' in it, the correct one is:
http
Ladislav Lacina wrote:
Hi!
I would like to know whether is there any diference between MSDOS and
FreeDOS behavior in TSR programs. Can I in TSRs call the same subset of DOS
funkcions like in MSDOS? Or more or less?
Can I read and write files from my TSRs?
The behaviour _should_ match MS-DOS
Aitor Santamaría Merino wrote:
Hi there,
Continuing the bugzilla report, the following are reported as wishes,
that is, to enhance the present functionality. They are mostly not
included in the TODO list, but I will include them in the post-list
(that I am going to renew). I simply list
Aitor Santamaría Merino wrote:
Hi there,
I have been listing and analyzing the bugzilla bug list, or at least,
until bug 1916, and I'd like to share this information with you. I have
grouped the bugs, and will expose them in three mails.
In this first mail I'd like to write about two
tom ehlert wrote:
...
and the kernel aspect is a work in progress
such as FDBACKUP is work in progress ?
if a bug is known scince 2 years, and noone worked on this
don't call it 'work in progress', call it 'noone cares' or DIY
instead
Tom
no, I mean I have a cvs tree on my laptop that
Michael Devore wrote:
...
Okay, that was painful. The ATAPICD assembly code is already a we1ird
amalgam of NASM and MASM/TASM code. Plus it appears to improperly use
I agree it is painful
EQUates globally that can be IFDEF'ed out of sight, and has a few other
quirks.
:-) how do you
David O'Shea wrote:
...
No. FreeDOS doesn't splits HMA to blocks with headers, similar to MCB
in conventional memory.
Could we maybe store a char or word in HMA which is at a standardized
location which we can read if we know we're running FreeDOS? I'm not sure
what MS-DOS does in this
Due to spamming I have password protected several pages on
wiki.fdos.org, if you need to edit any of these pages just send me an
email and I'll send you back the password. I hate to do this, but
someone keeps overwriting pages with junk. If it continues I may have
to update pmwiki and
Michael Devore wrote:
Not sure if it's already been noticed, but the wiki at
http://wiki.fdos.org has been pretty heavily spammed with Cialis crap,
several pages completely replaced.
Unfortunately they keep doing it which means I am going to have to setup
the wiki so people have to
On Sun, January 8, 2006 10:02 pm, Blair Campbell wrote:
Since XCDROM has been released and has proven to be relatively stable
and featureful, I think it is a good idea to replace atapicdd with it
in the 1.0 todo list. Also, does everyone agree that ASPI and El
...
Sounds good to me.
Jeremy
On Tue, January 10, 2006 7:57 pm, Johnson Lam wrote:
On Wed, 11 Jan 2006 01:18:25 -0200, you wrote:
Hi,
It not a good thing to ban IPs. Most people now use dynamic IPs, that
means that I can get of of a pool of 1 million IPs. If you ban some of
these IPs, one day I could be luky to get that
This feature (as it is implemented in pmwiki) is enabled on wiki.fdos.org.
Jeremy
On Tue, January 10, 2006 1:30 pm, Alain wrote:
Eric sent this, I think it is a good idea too, so I am copying to the
list :)
Not sure, we might already have that, but: Some Wiki
systems have the function URLs
What brand is the USB stick? and the BIOS you're booting from?
The usb stick is being treated as a hard drive, including a fake mbr
(with partitions), correct?
I see FAT16 versus FAT32 makes a minor difference, but not much.
If possible, would you send to me (depending on size and how much
Mark Bailey wrote:
Good day, all:
If doing a DIR A: on a floppy disk with no visible files,
or a hard disk partition with no files, the DIR command does
not print the line showing the number of bytes free.
This appears to be intended in the routine dir_print_body
from the file dir.c.
Note
Michael Devore wrote:
At 08:49 PM 2/22/2006 -0500, Mark Bailey wrote:
...
I'm going to try to muster sufficient time and brainpower to look the
offending partition-related source code over Thursday or Friday.
Subject to actual work and real-life interruptions, of course.
Anybody else
Miguel wrote:
My testing reveals that interrupt vectors 76h and 77h are also being
overwritten/hooked by FreeDOS ... or at least someone.
Running under VMware ...
At PXE boot time they are pointing relatively high in memory (EBEB:2D72)
By the time FreeDOS is running they are pointing at
Blair Campbell wrote:
But the question is: Will anyone help me test it :-) (Preferrably
both versions)
Also note that chdir, rmdir, and mkdir support LFNs properly, and DIR
/LFN will print long filenames for all files with lfn entries, just as
MS-DOS 7's command.com does.
...
So what LFN
FYI the sources for the GUI installer (as provided to me originally) can
be found here:
http://www.fdos.org/install/GUI_INST.RAR
not 100% sure if its the latest one as I have a few variants on my hard
drive as well, but should be close enough if you are just going to be
reading and not
Aitor Santamari'a wrote:
Hi Jim,
It wasn't me (I couldn't determine the cause why I couldn't connect to
Michael's site), but I'm glad that they're there!
So merit goes to someone else...
Thanks for those that sent the files!
Aitor
:-)
Hello all,
I am slowly working on updating my fdos.org site; to that end I have
finally re-enabled my kernel builds.
However, unlike past builds, the kernels found are now (or at least
should, I'm still testing) only be updated if the SVN source is
updated. I have it checking several times a day
On Tue, Jun 23, 2009 at 8:47 AM, Bart
Oldemanbartolde...@users.sourceforge.net wrote:
2009/6/23 Tom Ehlert t...@drivesnapshot.de
one thing, though: there MUST be the possibility to keep the dates of
the source files to the last change, not the last checkout.
with all files having a date of
On Sat, Aug 21, 2010 at 12:44 AM, Pat Villani p...@freedos.org wrote:
Folks,
I'm thinking it would be a good idea to standardize on one C/C++ compiler
for the project. I'm looking at the Open Watcom compiler and would like
your opinion. Reason for this suggestion is that it is the only real
On May 28, 2011 4:44 AM, Bernd Blaauw bbla...@home.nl wrote:
Op 28-5-2011 4:57, perditi...@gmail.com schreef:
A work in progress for testing is available at
http://www.fdos.info/kernel/latest/
The KERNEL.SYS file.
I'll try it out over the weekend, thank you :)
append initrd=FDBOOT.IMG
That kernel is not upx'd as I haven't yet installed it. (I will post a new
compressed kernel this weekend, I'm going to see about compiling on Linux,
if so my fdos site will be setup to check build daily - part of my work
for easy custom downloads)
Jeremy
On Jul 15, 2011 7:41 AM, Eric Auer e.a...@jpberlin.de wrote:
Hi Eduardo,
inthndlr.c int2F_12_handler should implement this...
So in short, I do not know what broke int 2f.122b and 122d
or whether it was removed deliberately. The changelog says:
Definitely, they are not implemented.
On Jul 15, 2011 12:31 PM, Travis Siegel tsie...@softcon.com wrote:
On Jul 10, 2011, at 9:20 AM, Rugxulo wrote:
You know what can edit arbitrary-sized files? sed !!! (My favorite!)
Maybe that should be included in FreeDOS 1.1 by default! ;-))
Hmm, speaking of including things in
On Aug 3, 2011 5:27 PM, c...@bttr-software.de wrote:
... Now, when I load DOSUSB and then devload usbdisk.sys the
block device driver usbdisk.sys will get the drive letter F: from
FreeDOS. Apparently it does not supply the next drive letter which
would be G:. I can then access the flash
On Sun, Jul 31, 2011 at 10:58 AM, Bernd Blaauw bbla...@home.nl wrote:
Op 31-7-2011 16:48, Bernd Blaauw schreef:
Op 31-7-2011 16:36, Tom Ehlert schreef:
Bernd,
assign a fix (W:) drive letter to the CD drive;
Tom
Experimented a little bit more: TDSK takes first driveletter after what
Please test lastest version of devload - version 3.24 available for
the time being at
http://www.fdos.org/kernel/testing/devload-3.24.zip
For changes since 3.23 see
http://fdos.svn.sourceforge.net/viewvc/fdos/trunk/source/BASE/devload/devload.asm?r1=133r2=138
Basically this adds the /Dx option
On Aug 4, 2011 9:08 PM, Bernd Blaauw bbla...@home.nl wrote:
Op 5-8-2011 2:53, Kenneth J. Davis schreef:
letter used (0 based, so A=0 and Z=25, note that I only tested C: or
higher) and 255 on error.
What if the driver being loaded doesn't assign a driveletter?
DEVLOAD UIDE.SYS /D:FDCD0001
On Aug 4, 2011 9:13 PM, c...@bttr-software.de wrote:
Additionally, I had thought the later check would be
sufficient for the LASTDRIVE check, but upon review I see it was not,
so implemented explicit check if we reached last drive [currently only
tested with default lastdrive = Z].
Your
Work in progress
see
http://fdos.svn.sourceforge.net/viewvc/fdos/trunk/source/BASE/devload/devload.asm?r1=138r2=139
or download
http://www.fdos.org/kernel/testing/devload.com
I will work on releasing 3.25 tonight or tomorrow after I get feedback
on the error levels to use and hopefully some
On Aug 5, 2011 3:34 PM, Bernd Blaauw bbla...@home.nl wrote:
Op 5-8-2011 13:45, Kenneth J. Davis schreef:
Work in progress
see
http://fdos.svn.sourceforge.net/viewvc/fdos/trunk/source/BASE/devload/devload.asm?r1=138r2=139
or download
http://www.fdos.org/kernel/testing/devload.com
Hopefully last update for a while. :-)
changes
http://fdos.svn.sourceforge.net/viewvc/fdos/trunk/source/BASE/devload/devload.asm?r1=137r2=141
download
http://www.fdos.org/kernel/testing/devload-3.25.zip
This fixes a few issues from previous 3.24 release:
- if initial CDS entry is invalid
On Aug 8, 2011 5:13 PM, Bernd Blaauw bbla...@home.nl wrote:
Op 8-8-2011 22:31, Rugxulo schreef:
No, I don't think it's been fixed since even SourceForge's Files area
still only has 0.82pl3 Besides, who's the maintainer these days?
(Bart? Doubt it, he's always busy.) I haven't heard
On Fri, Aug 5, 2011 at 7:45 AM, Kenneth J. Davis jere...@fdos.org wrote:
Work in progress
...
As a side note, on my netbook using similar VirtualBox setup I have
found that I can only use devload without any memory managers -
something related to no UMBs so I need to see if it is a devload
...
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,
On Sat, Jul 13, 2013 at 4:14 PM, Bertho Grandpied y31415926...@yahoo.frwrote:
Said Tom Ehlert te@dr.. - 2013-07-13 17:31 :
I can reproduce the bug; reason so far not found
Do you mean, not identified in the source, or what ?
it would be helpful for the uninitiated if you could share
On Jul 19, 2013 12:31 PM, Bertho Grandpied y31415926...@yahoo.fr wrote:
Hi Jeremy !
I'm glad someone (you) is / are fixing this issue. I have made a driver
which fixes it
successfully in conjunction with the flawed kernels, and I was wondering
whether I should have
to bundle that
96 matches
Mail list logo
