Louis Santillan schreef op 5-5-2013 18:28:
Whoops, didn't realize that I replied to fd-user instead of kernel.
One other note, all kernels are slightly bigger withe options I set.
I guess it depends on what the compilers do:
[1] optimize for certain processor architecture(s)
[2] also keep
Op 19-2-2012 10:57, dos386 schreef:
(untested, just history.txt __IS__ updated this time)
but nobody annouced it :-D
It's a secret to everybody!
(hm, too much Zelda)
The pre-386/memdisk detection is a good thing, finally a unified kernel.
Right until someone does a append FD={INSTALL=FORMAT
Could someone please verify that a screen full of kernel warnings is
shown when running option 2 from the following bootdisk? :
[ http://www.reactos.org/bugzilla/attachment.cgi?id=7374 ].
A simple workaround I could do is commenting out the textline that gets
printed and recompile.
Cause of
Op 14-1-2012 19:48, Bertho Grandpied schreef:
It's been a few days and I'm surprised my first mail hasn't been acknowledged
in any way, let alone answered; strange, I've been part of various lists
before, usually 'newbies' are greeted rather than ignored altogether. So I'll
reiterate and
I'm happy to announce that the FreeDOS 1.1 distribution is finally
available, including sources to all packages. You'll notice it's quite
a basic version, lacking some features and programs that were present in
the 1.0 release. I'm planning on restoring functionality in the 1.2 release.
Op 18-12-2011 23:31, Pete Batard schreef:
1. I am the developer of Rufus [1], which is a DOS-bootable USB flash
drive creation utility for Windows. One of the versions of Rufus embeds
FreeDOS (kernel + freecom) for installation as the default DOS, in lieu
of the WinMe DOS that can be
I'm in a situation where I got Syslinux bootloader on an USB flash
drive. It loads the MEMDISK ramdisk module with a floppy image as
contents which is then executed (as drive A:).
I'd like to get into a situation where the USB flash disks doesn't get a
driveletter assigned by the kernel when it
Op 22-8-2011 0:47, Eric Auer schreef:
You can hook int 13 function 8 (get drive parameters) and make
sure that for dl = 80 or higher, it always returns carry set
and dl = 0 to pretend having no harddisks. Of course DOS does
a lot of work for you to parse partitions, so it is a bit odd
to
Op 22-8-2011 0:58, Bernd Blaauw schreef:
Then, again, Syslinux/memdisk documentation lists a nopassany
parameter to disable showing harddisk. Gotta test that next I guess :)
This works like a charm, however FreeDOS kernel happily lists about 50
lines with 'illegal partition table, drive nn
Op 20-7-2011 3:50, Bart Oldeman schreef:
It's probably best to make things explicit (unless the goal is a true
Win32-DOS cross-compile), using DOS16 utilities, by changing the last
part of mkfiles\watcom.mak to:
CFLAGS1 = -os-s-wx-bt=dos
# *Implicit Rules*
.obj.exe:
Op 14-7-2011 5:09, Marcos Favero Florence de Barros schreef:
I'm now using the 32-bit 2040 kernel, because none of these
errors has ever appeared under the previous 32-bit kernels, and
I'm hoping they will not appear under the new one either
[fingers crossed].
Any advice is
Op 15-7-2011 0:42, Eduardo Casino schreef:
Hi Bernd,
hello Eduardo, good to see you're around :)
Because it is harmless. Is it really necessary to treat that case in a
different manner than a successful installation? If it is, I'll look
into that, it is trivial to modify.
it's not really
Op 10-7-2011 13:11, Eric Auer schreef:
Hi dos386,
Ninja-ing thread here slightly:
Can kernel 2040 please be mirrored to Ibilio? Can't be found yet at
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/kernel/
Op 10-7-2011 3:10, dos386 schreef:
Anyone can please upload the __correct__ HISTORY.TXT file for
the 2040 kernel release on some place where it is easily discoverable ?
Both SF and fdos.org ?
http://sourceforge.net/projects/freedos/files/Kernel/2040/
It's history.txt inside the doc
Is it possible to have the FreeDOS kernel start with driveletter
assignment from specific interfaces, or are we stuck with what BIOS
offers us?
When booting from USB, I've got multiple options:
1) syslinux + memdisk + floppy image
2) syslinux + memdisk + ISO file
3) syslinux + chain.c32 +
Op 30-6-2011 1:29, Santiago Almenara schreef:
Thanks Eric!
I'll try 2040 instead of 2030.
Just for everyone's information, I'm still able to hit a double BAD FAT
INFO - Run CHKDSK error message from the kernel occasionally
The only situation in which I sometimes am able to trigger that, is
Op 25-6-2011 16:06, Kenneth J. Davis schreef:
Hello all.
Kernel 2040 has been tagged and should be made available on
Sourceforge file releases within next few days.
Nice to have an official updated kernel.
Also available for download at fdos.org:
installer compatible form -
Op 21-6-2011 4:24, perditi...@gmail.com schreef:
If there are no objections, then this week (tomorrow if I have time) I
plan to tag the kernel at 2040 and make release builds available.
By all means go ahead :)
I suppose it includes Bart's earlier fixes, your modifications for
Memdisk
dos386 schreef:
PS: I would like to quote IBID_AG
2. Congratulations on a great kernel/OS
4. I would rather see more of the features from 2037 in stable
List ???
* external Country.sys support (including MODE, DISPLAY, NLSFUNC etc)
* That FNODES stuff (Bart seems to be working
Eric Auer schreef:
Hi dos386!
Can you forward details about that dmidecode / bttr forum thing?
http://www.bttr-software.de/
http://www.bttr-software.de/forum/forum.php
software: http://www.bttr-software.de/misc/dmide29b.zip (I guess)
Nowadays a hardware diagnostics tool at boottime seems
Alain M. schreef:
I use regularly FreeDOS in users instalations with brand new, superfast
motherboards. The aplication is heavy Database usage and FreeDOS is
prerforming better then MS-DOS...
Great. Is switching kernel the only thing that's relevant or did you
switch any other components
Eric Auer schreef:
Still no reason to add experimental things to stable now :-)
The solution is easy: Add it to the UNSTABLE fork and, while
doing so, show that there are people who are interested in
new experiments with DOS! This will also draw more attention
to this branch and make it more
Eric Auer schreef:
Maybe we should have DVD playing software and a DVD-
compatible version of DOSCDROAST first... :-p. And
I repeat my earlier argument: Just split the bluray
image into a few files, very easy :-).
What's DOSCDROAST exactly?
So far I'm quite happy with Blair's port of
Eric Auer schreef:
Hi Bernd,
*your KERNEL.SYS in renewed archive works fine, nice job.
[ http://www.coli.uni-saarland.de/~eric/ke2007jul21.zip ]
*JEMMEX v5.64 can be compressed and works, can't see it listed in MEM /C
( MEM /C /N ) listing though, maybe it\s hiding under SYSTEM :)
(UMBs
Eric Auer schreef:
Hi Rugxulo, Robert, kernel people,
Hello Eric,
branch of the kernel? Rugxulo, KEYBUF should obsolete having a
keyboard extender around. Kernel people, IDLEHALT does not
obsolete FDAPM APMDOS but it gives you some energy-saving even
without FDAPM. I hope both can be used
Eric Auer schreef:
Please test :-)
You relying on me to test or does this new binary work for you in Bochs?
Sample kernel binary: www.coli.uni-saarland.de/~eric/ke2007jul21.zip
same filename yet updated release?
Bernd
David O'Shea schreef:
It says The UNSTABLE (aka development) branch is what I refer to as the
development kernel (kernels with w suffix). It looks like those kernels
actually have .dev or .dbgdev in them, right?
There doesn't seem to be a discussion of the naming convention for FreeCOM.
Bart Oldeman schreef:
To be fair I found Eric's email rather demanding. In general if you
want things to happen in the NEAR future you either have to do it
yourself or pay big bucks, not just pizza money. Certainly when the
kernel doesn't have a real maintainer (just an interim one who does
Eric Auer schreef:
Hi, yes, FreeCOM can handle changing drive letters. The PROBLEM
is that harddisk letters are handled by a kernel driver which
can only do one hole-free range of drive letters. So if you
could enable a new partition on the fly, all subsequent drive
letters would move. HOWEVER,
Abrahan Sanjuas schreef:
Is this feature missing on FreeDOS?
if BIOS has support, DOS supports it.
you might need the UDMA2.SYS driver for really large harddisks though.
Bernd
---
SF.Net email is sponsored by: Tell us your software development
Jeffrey Chao schreef:
I use sys config kernel.sys bootharddiskseconds=5 to configure the
freedos kernel.
Then I use this freedos as floppy image to burn a bootable CD.
Then:
what kind of bootloader is used on the cdrom, or what type of emulation
does the cdrom use for diskette?
Config:
IDE
Eric Auer schreef:
PS: Which kernels contain the DOSLFN compatibility patch (improved
xBPB/DPB initialization and set extended error code implemented),
only the development kernels at www.fdos.org/kernel, I think. Jeremy has
been active lately. Only thing missing by default is that IF a
Jeremy, the -dev kernel is BROKEN.
Try booting, and then SET FOO=BAR
I get 'environment full?' messages.
previous kernel was from December 3rd, 2004
putting that version back eliminates the problem.
btw: happy new year and best wishes, everybody!
see you all in 2005 :)
Bernd
Jeffrey Chao schreef:
After booting into Windows, I can see there are two floppy drives in
Windows Explorer,
but I just have one floppy drive connected. Does anyone ever faced the
same issue as me?
A: is the emulated floppy drive (the floppy image and/or diskette you
provided for bootable
Can somebody please fix the date for directory creation?
Bugzilla?
this is the unstable kernel, I used Lucho's latest binary.
I'll compile my own binary soon enough.
(if you're wondering: Freecom 0.82plAK-XMS, DIR C:\FDOS /OGN /Y)
problem is not in kernel 2035
Bernd
Volume in drive C is C_FREEDOS9
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
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
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 and
mounting. program
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
Lucho, impressive progress.
Though I don't use any COUNTRY/codepage/keyboard_layout things myself,
this can be quite usefull.
I can imagine Aitor being happy, for example.
He does a lot with these things.
Now only NLSFUNC is missing (in progress by Eduardo Casino)?
btw, no source for your
Bart Oldeman schreef:
I'm sorry but I simply don't have the time to go through all the other
patches. If they were reduced to just bug fixes I'll promise that I'll
have another look though -- I still monitor the mailing list every now and
then. Guys *any* project that wants to be close to a 1.0
Arkady V.Belousov schreef:
Hi!
19--2004 16:08 [EMAIL PROTECTED] (Bernd Blaauw) wrote to
[EMAIL PROTECTED]:
BB to work out his changes. At a given moment, he should probably issue a
BB code-freeze and then make stuff more readable/review-able
May you point, what in my code isn't readable
Arkady V.Belousov schreef:
PPS: About discussion of planned changes: how many times I wrote here? How
many times I get any answer? If I will wait answers for my proposals before
doing something, I will do nothing forever. :(
PPPS: Of course, I open for discussion anyway.
1) implement your code
tom ehlert schreef:
Hello Arkady,
where the hell are the sources for these changes ??
I wonder, too. CVS read/download access is nice.
Is it possible to fork the CVS kernel tree into an Arkady branch so he
can work on the kernel and at same time provide sources
(he doesn't have a website, and
Eduardo Casino schreef:
Hi!
Country code for Spain is 34, not 33.
Eduardo.
fixed in Arkady's version, and please check your clock - it's 23:15 here
and your message is dated 30-06-2004 00:21 or so.
one hour too much.
thanks for the patch though :)
Bernd
Alain schreef:
In my opinion this would be a _great_ improvement :)
Many times I had ro reboot (in MS-DOS) because the critical instruction
was executed ok and I didn't want to singlestep all the rest.
BUT, IMHO the key for that should not be Esc but something completely
different, like some
tom ehlert schreef:
- when tracing, Esc now turns off asks for following lines with ? and
assumes Y for all; F8 now behaves similar to Esc.
I disagree.
Esc turns of F8 'single stepping', nothing else.
so if pressed ESC, then everything except a command?=value is
auto-executed?
Arkady, define
Arkady V.Belousov wrote:
Hi!
Arkady, I'll try to compile your kernel tonight, as I experienced some
hardware upgrade glitches the last 2 days.
as someone asked (I lost about 35 emails) : Lucho's site is at:
http://linux.tu-varna.acad.bg/~lig/
it contains the Romdsk stuff and the UDMA DOS-driver.
Arkady V.Belousov schreef:
- 123? present and statement not from selected menu? Skip.
- ! present? Don't skip.
- ? present or single step? Ask.
Your proposal changes behavior: now it will look so:
- 123? present and statement not from selected menu? Skip.
- ? present? Ask.
- single step and not !
Eric and I have been working a few hours on a patch to correct the
ask-user-to-execute-config.sys-line algorythm.
essentially (config.c, line 806 I think):
/* !device= never ask / device?= always ask / device= ask if singleStep */
/* ! does override singleStep but not ?, so !device?= will
The Somertons schreef:
Justin
If I recall correctly, Interlnk never had FAT32 support, so I hope C: isn't FAT32.
as alternative to FD(X)XMS, we now use HIMEM.EXE , included in the EMM386 package.
ftp://ftp.devoresoftware.com/downloads/himem64.zip [22-04-2004]
is probably most recent.
Bernd
Bart Oldeman wrote:
On Sun, 9 May 2004, James Tabor wrote:
Hi Bart!
Bart Oldeman wrote:
Bart seems to be the only one with CVS access.
So, if no time, the CVS snapshots stay identical (because of no imports
to CVS), and people can start creating their own patches against this
CVS-release?
in
DOS=UMB is causing a lot of problems.
Unfortunately it's not possible to use UMBPCI (want to exclude EMM386 as a
cause..) on Bochs.
Bernd
set path=a:\freedos
LASTDRIVE=Z
BUFFERS=20
FILES=40
DOS=HIGH
DOS?=UMB
;DUMMY?=YES
set dircmd=/ogn
DEVICE=A:\DRIVER\HIMEM.EXE /VERBOSE
hi Bart,
Bochs has no PCI, so UMBPCI does not work.
any comments on the original message I posted?
do you want me to publish a Bochs zipfile including my FreeDOS
configuration,
so anyone can reproduce my encountered problems?
unlike VMware, Bochs is completely platform-independent
I'm kicking this back to kernel. No need to let it stay on devel-list
Arkady V.Belousov schreef:
Hi!
19--2004 15:13 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:
EA In bug 1759, he also suggests that No UMBs available warning (when you
EA use DEVICEHIGH) should be only displayed once
Bernd Blaauw schreef:
EMM386:
FDISK /REBOOT causes Invalid Opcode,
FDAPM WARMBOOT does the same
FDAPM COLDBOOT does reset the computer
FDAPM HOTBOOT works like good old QEMM: reboot to bootsequence immediately.
(not that it has that great effect, but OK..)
anything that can be done about
Arkady V.Belousov schreef:
Fine. For the future: show URL for complete diff patch on the main
page, previous time I don't found it (if it was present). Also, when planned
2034 release? May be I wait this release and download it completely (instead
patch), if it will be soon?
the idea is to
Erwin Veermans schreef:
Forbidden
You don't have permission to access /~lig/romdsk/romd-bin.rar
on this server.
What am I doing wrong, or should I send some cigars first ?
;-)
confirmed.
do you compile from source or always work with binaries like I did?
latest binary from Jeremy took a
Arkady V.Belousov schreef:
Hi!
4--2004 17:55 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov
[EMAIL PROTECTED]:
AVB I test batch and make files both under OW12 and BC31
te would be great if you ewoild
ewoild=perform?
would - 'if you would test them'
te test them with TV 2.01
each DEVICEHIGH in config.c causes a warning
[ http://www.freedos.org/bugs/bugzilla/show_bug.cgi?id=1759 ]
is the document for getting Openwatcom packages (in order to compile the kernel) still correct
(except OpenWatcom 1.0 - 1.2 then)?
http://www.freedos.org/freedos/news/newsitem/137.txt
idea
The current nightly-kernel may have reached a new landmark in the
quest for smaller conventinal-memory footprint but it lost ground in
usability and compatibility. My test-machines halt on various
arbitrary points telling me: more than two near fnodes requested at
the same time
if files=10 would
reason is speedup.
It's faster to read a single 360KB file into RAM and then run from
there, than to keep reading a diskette.
guess you had the bootdisk from prerelease 4, or the one below:
http://fdos.org/ripcord/beta9rc5/fdos1440.img
the real floppy contents is accessible as B:
are you the
it's the CDRcache driver which causes the cdrom disk resets, not SHSUCDX
itself.
option 2 should prevent it from loading, as no XMS driver is loaded.
Bernd
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial
63 matches
Mail list logo
