Hi Ibid,
1470 builds and works fine (not much testing done though).
cd \ works again
Good...
HDPMI (HX 2.15 dpmi server) loads.
What was broken before?
Regarding the patch I saw mentioned, here's the thread:
I guess SHARE might be something to test w/ HX.
Japheth's documentation claims that SHARE is needed for pipes, Cygwin
requires pipes, and FD SHARE is too crippled to work.
If Japheth knows about a bug, he should explain what EXACTLY
is wrong so somebody has a chance to fix it...
I don't
Hi Christian,
I don't know what Japheth has to complain about it, but I know that
DOS-C's SHARE:
- is a C program that stays in memory without usage of any assembler code.
True. It might be interesting to rewrite it in pure Assembly, for size.
Increases memory usage much.
Already
- uses an interface on Int2F which probably isn't as good as an internal
hook. (MS-DOS uses a number of hooks partly documented in RBIL, I use
one
You mean table 01636, format of share exe hooks?
It doesn't matter, but probably yes. (I don't know the number, but it's
inside the Int21.52
- doesn't check whether it runs on the correct DOS version. It doesn't
..
I know about the OEM ID and the DOS-C release string which can be
retrieved by Int21.33FF. I don't see how SHARE could use that to
differentiate kernel releases. Does the string have a fixed format
specified anywhere?
2009/7/5 Christian Masloch c...@bttr-software.de:
Regarding the updating of SFTs opened for the same file (previous mail),
is that already in the kernel? If not, I want to add that point to your
list for SHARE.
Yes, that has been in the kernel since the initial implementation by
Ron Cemer. It
Additionally, I used copy con: to record some messages.
One interesting thing it says is
Truename CON: C:/CON
or some such thing.
Is this a bug, or standard behavior?
No bug, it's compatible to MS-DOS. If the input is a character device's
name without any directory information (but a
Hello,
2009/6/27 ibid...@lavabit.com:
The hardest part was to find a 16-bit NASM.
I have used TurboC because
1 I already have it,
2 OpenWatcom would take too long to download at~78 mb,
3 OW is too large for the 256 mb flash drive I have been booting from
Time ago, and if I remember
The kernel files are now mirrored to ibiblio:
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/kernel/2038/kernel2038-fat16-binary.zip
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/kernel/2038/kernel2038-fat32-binary.zip
Aitor Santamaría escreveu:
Time ago, and if I remember correctly, Arkady built a simple OW pack
having the basic OW for DOS, and being small enough, but probably this
is discontinued with the newer versions of OW, right?
It is not a matter of being discontinued. What he did was just simple:
2009/6/30 ibid...@lavabit.com:
I've been trying to patch 2039-svn with Christian's fix, while working
under a TC 186/FAT32/Win kernel (built myself), and I have found the
following:
what does Win here mean?
1. Code changed. In other words, the
if (!tsr)
line referred to seems to not
On Tue, Jun 30, 2009 at 10:52 PM, Bart
Oldemanbartolde...@users.sourceforge.net wrote:
2009/6/30 ibid...@lavabit.com:
I've been trying to patch 2039-svn with Christian's fix, while working
under a TC 186/FAT32/Win kernel (built myself), and I have found the
following:
what does Win here
Hello,
2009/6/14 Eric Auer e.a...@jpberlin.de:
Hi Aitor,
I support this idea, but that means that odd numbers (2039) would go
unstable.
Actually Bart already ported country sys support from unstable,
combining it with built-in country support. He is also working
on f-node free
Hi Aitor,
I support this idea, but that means that odd numbers (2039) would go unstable.
Actually Bart already ported country sys support from unstable,
combining it with built-in country support. He is also working
on f-node free operations in stable. This means that version
2039 will be the
I support this idea, but that means that odd numbers (2039) would go unstable.
I guess that on view on this FD 1.1 should have 2038 ( or 2040 if
there's such thing by the release time).
Aitor
2009/5/18 Bernd Blaauw bbla...@home.nl:
Eric Auer schreef:
Still no reason to add experimental things
Hi Bart,
well, at the time of setting up SVN I asked Jim if he could
set up sourceforge so the patches to go to the existing
freedos-cvs mailing list (where CVS commits were sent)
I do not know how many people read that list, but my suggestion
was more to talk about the code rather than
Hi Ibid,
mess ... with Win98 and FreeDOS (Freedos starts, Windows doesn't
You can dual-boot with Win98 and FreeDOS actually sharing the
same C: drive, using a suitable boot menu and file locations.
You should use only the Win98-DOS kernel for starting Win98.
UDF is popular for rewritable
Hi dos386!
Can you forward details about that dmidecode / bttr forum thing?
PS: I would like to quote IBID_AG
4. I would rather see more of the features from 2037 in stable
Ask IBID... country sys support is very useful for SOME languages,
but which other features of 2037 are really hot? :-)
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
* Windows 3.1x support
seriously: is ANYBODY using Windows 3.x ?
IMHO Windows 3.x is 100% obsolete, so why would anybody want windows
3.x support ?
WfW support in stable, these might be handy.
Windows for Workgroups , which is a flavor of Microsoft Windows 3.11
WfW support will probably
Hi Bernd, Tom, Bart, others,
* external Country.sys support (including MODE, DISPLAY, NLSFUNC etc)
Definitely useful. I hope it can be combined with compiled-in
2038 style basic support: Things like date/time/number format.
While only external country.sys adds sort/uppercase/lowercase
override
On Fri, Jun 5, 2009 at 2:05 PM, Eric Auere.a...@jpberlin.de wrote:
Hi Bernd, Tom, Bart, others,
...
WfW support will probably never come; WfW was tighly coupled to the
kernel (at least according to Schulman et. al., WfW is MUCH more then
just a flavour of Windows 3.11)
What is Schulman et
Hi Eric,
2007/9/19 Eric Auer e...@coli.uni-sb.de:
I tried to fix bug 1908: Our kernel used to need a fresh
dir entry for renaming, as it renamed by create new dir
entry for file, then mark old entry as deleted. My patch
tries to limit this to cases where you rename files or
directories
Folks,
I am not as up to date on the changes as you may be. I'm looking for
a volunteer (or volunteers) to update history.txt for 2038 and 2039.
When I get the updated files, I'll follow through and get them on the
web sites.
Pat
On Sun, May 31, 2009 at 9:05 AM, Eric Auer e.a...@jpberlin.de
Hi Bernd, Pat, Jeremy,
Pat, Jeremy: Please FIRST update history txt BEFORE we make
a sourceforge file release of kernel 2038. Thank you :-).
I just uploaded updated history.txt / readme.txt / contrib.txt
as subversion revision SVN r1412 for Pat :-). NOTE: Please ONLY
updated those 3 when
George Petculescu:
at http://sourceforge.net/projects/freedos/ use the menu Code.
The exact adress is http://sourceforge.net/scm/?type=svngroup_id=5109
Thanks for the information!
--
Register Now for Creativity and
Hi Bart :-)
Jim reinstated SVN write access so I committed a patch that I have
used internally in a not so clean fashion for a long time:
cross-compiling from Linux using Open Watcom. The reason why: well it
is more convenient and quicker (less than 2 vs. 20+ seconds here) to
cross-compile
Tested and didn't find anything eclatantly evil so far :-)
- It works mostly, see shot: http://img211.imageshack.us/img211/4611/ker2038.png
- my GetDiskFreeSpaceEx bug seems fixed
- history.txt neglects any development, oops Eric already pointed it, also,
the filename should be HISTORY.TXT
Does anyone have any information or Idea about this problem?
Would any of Jack's driver help?
Maybe __removing__ drivers and avoidable memory managers would be the
more promising approach ...
YES, a ramdisk (I use SRDISK) is a way to avoid the HD and possibly
bugged INT $13 support.
Also, a
Hi Eric,
Interesting :-) How does it work (in other words, what was the
trick to make it possible) and how do the config bat settings
work in this context? :-)
Can you be more specific? Did you look at the svn diff at all?
Bart
Hi Bart,
Can you be more specific? Did you look at the svn diff at all?
That is the point...
svn diff -r1386:1388
gives a diff of 14 kilobytes, 12 files modified,
46 lines changed, 170 lines added. Quite a lot.
Okay okay I can analyze the patch myself... :-( Some explanations
from the
2009/5/21 Eric Auer e.a...@jpberlin.de:
That is the point...
svn diff -r1386:1388
gives a diff of 14 kilobytes, 12 files modified,
46 lines changed, 170 lines added. Quite a lot.
Okay okay I can analyze the patch myself... :-( Some explanations
from the author would have saved some time
2009/5/21 Eric Auer e.a...@jpberlin.de:
Not really - I think it would be tricky to put the config
variables in something that all used MAKE versions can deal
with directly, as opposed to having both a BAT and a MAK?
There used to be (a long time ago) both a config.bat and a config.mak
(for
Hi Pat,
This sounds liuke a good strategy.
I would say 2038 as default, 2037 (including winkrnl) as option--unless
2039 shows up first (doesn't look likely). If 2039 gets something
worthwhile, 1.11 is an option.
I agree - same as in 1.0, the stable kernel is the
default and the unstable
Still no reason to add experimental things to stable now :-)
The solution is easy: Add it to the UNSTABLE fork
No. Because first, I don't develope DOS-C, and second, forking is bad and
makes merging changes back in harder. Since your opinion seems to be that
filesystem extensions can never
Indeed JAM only works on non-FAT32 kernels because of different
data structures...
Any other different structures besides the SFT?
JAM apparently needs the start cluster of
the compressed disk file so it can use lowlevel (int 25/26...?)
calls to access that file without causing reentrancy
Hi Jeremy,
Kernel 2038 tagged and available at http://www.fdos.org/kernel/latest/
Someone with access, please upload to ibiblio and release on SF.
Please update history.txt - it represents the state of 13 months ago...
While you are at it, could you update my email to mceric at
Actually MSDOS 7.10 already uses the SFT in a different way, but
undocumented by RBIL,
for both FAT16 and FAT32:
0BhWORDcontains the high word of the relative cluster number
at offset 19h
2BhDWORD contains the starting cluster number
35hDWORD contains the current cluster
Hi Christian,
I think that you are not being polite.
You are new here and you start by wanting to change everything. Why
don't you start by fixing a few bugs?
Alain
Christian Masloch escreveu:
Which app crashes from running on a FAT+ kernel? (Presuming you don't
even
have that large
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
2009/5/18 Christian Masloch c...@bttr-software.de:
Good work! I verified RBIL's statement that the word at 0Bh was not used
by checking it for files located on a FAT12 and FAT32 drives. It contained
a seemingly random value which lead me to the wrong assumption MS-DOS just
didn't properly
Eric Auer wrote:
Once 2038 is released I plan to continue reviewing any outstanding
patches and apply as appropriate. My top priority is bug fixes -
repeatable bugs will probably be fixed first :-) In no particular
True. One bug: MSCLIENT, but only in BASIC (without REDIR loaded)
It won't help FreeDOS of course because it still uses fnodes for these
things instead of SFTs.
Those are ancient relics that should be done away with. There is no
need for them anymore. I'd like to put that high on the priority list
for kernel development.
in theory you are right. in
Hi Eric,
Pat:
It won't help FreeDOS of course because it still uses fnodes for these
things instead of SFTs.
Those are ancient relics that should be done away with. There is no
need for them anymore. I'd like to put that high on the priority list
for kernel development.
Just to remind
2009/5/18 Tom Ehlert t...@drivesnapshot.de:
It won't help FreeDOS of course because it still uses fnodes for these
things instead of SFTs.
Those are ancient relics that should be done away with. There is no
need for them anymore. I'd like to put that high on the priority list
for kernel
Hi Bart,
[fnodes] are ancient relics that should be done away with. There is no
need for them anymore. I'd like to put that high on the priority list
for kernel development.
in theory you are right. in praxis fnodes are everywhere throughout
the file system (as you probably know), and
On Mon, May 18, 2009 at 3:49 PM, Tom Ehlert t...@drivesnapshot.de wrote:
It won't help FreeDOS of course because it still uses fnodes for these
things instead of SFTs.
Those are ancient relics that should be done away with. There is no
need for them anymore. I'd like to put that high on the
2009/5/18 Christian Masloch c...@bttr-software.de:
However I don't think I'll copy this strange behaviour (at least not by
default). As reported by Eric, it breaks programs like JAM (the point
is,
even on FAT12 and FAT16 disks) which look into the SFT to get the first
cluster of a (FAT12 or
It's all undocumented, of course :) You're distinguishing undocumented
undocumented from documented undocumented...
Nah, here I rather distinguished undocumented changes from MS-DOS 6 to 7
and the documented ones, which were like the config.txt user documentation
describing some of the
Hi Christian,
I don't want to change everything. The only extension I asked
for was to support FAT+, of course in the stable (or trunk) kernel
branch because unstable isn't developed by anyone currently and
developing it would proceed the forking of these branches.
Still no reason to
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
If half as much effort went into the code that has gone into this
thread, we'd have rewritten the kernel several times over.
Since I'm wrong about the kernel(?), let me put it to you this way. I
want to put out a new release, FreeDOS v1.1 and get a plan in place.
In 50 words or less, who is
On Mon, May 18, 2009 at 6:32 PM, Pat Villani p...@monmouth.com wrote:
If half as much effort went into the code that has gone into this
thread, we'd have rewritten the kernel several times over.
Since I'm wrong about the kernel(?), let me put it to you this way. I
wrong?
want to put out a
This sounds liuke a good strategy.
Pat
On Mon, May 18, 2009 at 8:07 PM, ibid...@lavabit.com wrote:
Hi Pat,
I would say 2038 as default, 2037 (including winkrnl) as option--unless
2039 shows up first (doesn't look likely). If 2039 gets something
worthwhile, 1.11 is an option.
Thank you,
I'll take care of it tomorrow.
Pat
On Sun, May 17, 2009 at 11:11 PM, Kenneth J. Davis jere...@fdos.org wrote:
Kernel 2038 tagged and available at http://www.fdos.org/kernel/latest/
Someone with access, please upload to ibiblio and release on SF.
Please test and report any new issues to the
2009/5/17 Bart Oldeman bartolde...@users.sourceforge.net:
0Bh WORD contains the high word of the relative cluster number
at offset 19h
2Bh DWORD contains the current cluster number
35h DWORD contains the starting cluster number
sorry, the last two are the other way around:
2Bh
2009/5/17 Christian Masloch c...@bttr-software.de:
Just in case you're talking about the extended SFT: I'll use a
FAT32-extended SFT (probably compatible to EDR-DOS's extensions for FAT32)
even without FAT+. Somewhere *at least the beginning cluster* of the file
has to be stored, and the
answer didn't work
--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables
unlimited royalty-free distribution of the report engine
for externally facing server
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
2009/5/15 Kenneth J. Davis jere...@fdos.org:
Thanks, saved me some time further examining it. Explains why 0 was
being passed in. Reviewing it further, I should have caught that. I
still haven't found any programs other than old GEM that use FCBs for
more than volume label, but its a bit
The main bug/feature that I plan to work on is FAT+ support,
the working with 4GB files goes along with this since it adds
support for 4+GB files.
Please keep this out of production kernels.
I agree - modifying FAT to support files 4 GB is asking
for trouble. Of course you can add it to
OK, let me chime in on this. Jim and I had several conversations on
topics like this before I took over. I want to share the current
thinking.
We, as a group, have made a significant impact on the open source
community and computing in general. This is something we need to keep
in mind as we
Hi Christian,
The main bug/feature that I plan to work on is FAT+ support,
the working with 4GB files goes along with this since it adds
support for 4+GB files.
Please keep this out of production kernels.
I agree - modifying FAT to support files 4 GB is asking
for trouble. Of course you
Hi Jeremy,
You misunderstand me :-) Of course we should support files of 2-4 GB
size in the STABLE kernel very soon! Just do not support ABOVE 4 GB
There are no longer multiple active branches, there is only trunk.
Trunk is stable, but there also is devel / unstable:
Nope, I'm not doing anything other than trying to gather enough
information with respect to project status to try to come up with a
road map and possibly plan release 1.1.
I have made *NO* decisions.
Pat
On Thu, May 14, 2009 at 4:26 PM, Eric Auer e.a...@jpberlin.de wrote:
Hi Jeremy,
***
:45 +0200
From: Christian Masloch c...@bttr-software.de
Subject: Re: [Freedos-kernel] Hello again
To: freedos-kernel@lists.sourceforge.net
Message-ID: op.utw4ajfez9d...@isor
Content-Type: text/plain; format=flowed; delsp=yes;
charset=iso-8859-15
The main bug/feature that I plan to work
Hi Abrahan,
Ex-FAT support instead of FAT+ or FAT32+??
This idea seems more good like FAT+ instead :-)
And how is the support for Windows 3.1 / 3.11?
While it is called FAT, exFAT seems to differ a lot
from FAT. Also, exFAT is heavily patented... Talking
about FAT+... I really wonder
Hi Tom, Jeremy,
The main bug/feature that I plan to work on is FAT+ support,
the working with 4GB files goes along with this since it adds
support for 4+GB files.
Please keep this out of production kernels.
I agree - modifying FAT to support files 4 GB is asking
for trouble. Of course you
It seems to me I've run FreeGEM/XM on FreeDOS before.
On Mon, May 4, 2009 at 3:42 PM, Kenneth J. Davis jere...@fdos.org wrote:
On Mon, May 4, 2009 at 6:26 PM, ibid...@lavabit.com wrote:
Hello,
I've tried running GEM/XM under freedos kernels 2035b, 2036, 2037, and
Christian experimental build
Hello:
1. The updated GEM/XM is what I run. It simply was hacked to autofail
on FCB errors.
2. I am unfamiliar with debugging, asm, programming, etc. I just know
some tools.
3. LOAD.ASM is part of the missing source for GEM/XM. It was lost
before release under the GPL.
4. It is indeed a branch
Hi Jeremy, Bart, IBID,
I tried 2038rc1svn out _briefly_. It works about the same as prior builds
(runs edit, mem, command, gem; loads ctmouse, gcdrom, himemx,jemm386,
shsucdx; still does not run GEM/XM).
...
OpenGEM variant of FreeGEM (http://gem.shaneland.co.uk/) provides the
GEM/XM
PS: Attempting to use SUBST to create a drive letter backed
by a directory in a dosemu magic drive creates a drive
which does not contain any files. I did not check why.
I assume DOSEMU's magic drives use the Int2F redirector interface to
provide their filesystem to the emulated DOS. SUBST
On Tue, May 5, 2009 at 2:10 PM, Eric Auer e.a...@jpberlin.de wrote:
Hi Jeremy, Bart, IBID,
...
I could not find any LOAD*.* file in the zip, though... Maybe
this whole experiment is something different than IBID meant?
Eric
See http://www.seasip.info/Gem/gemxm.html (I'm not sure if its
Kenneth J. Davis escreveu:
I am still reviewing and testing the pending patches... but progressing. :-)
I am very very glad of rearing this. I use FreeDOS for clients, and it
is performing better then MS-DOS 7.10... I ma not sure why, but I have
fewer database problems with FreeDOS :)
I am
On Mon, May 4, 2009 at 6:26 PM, ibid...@lavabit.com wrote:
Hello,
I've tried running GEM/XM under freedos kernels 2035b, 2036, 2037, and
Christian experimental build (later renamed 2038pre). Official
documentation says it will not work due to using FCBs to read the driver
loading file,
2009/2/17 Eric Auer e.a...@jpberlin.de:
/* clear the Init BSS area (what normally the RTL does */
memset(_ib_start, 0, _ib_end - _ib_start);
Maybe this broke when Bart tuned the memory model recently?
Remember for example JEMM386 int 19 fastboot compatible
storage of original
I am still reviewing and testing the pending patches... but progressing. :-)
Does the non-UPX'ed kernel boot for anyone else? I spent most of this
evening tracking down why my kernel didn't boot (that is testing my
new setup so I wasn't sure if it was my host OS/compiler (I'm already
using
Hi Bart,
thanks for making the patch much shorter, very commitable now :-)
Why did our old code do that complex put bp at [bp+2] thing? And
what does the cpm_error jump decision now inverted patch mean?
Eric
This is a minimal fix for [entry.asm]
...
-pushbp
On Fri, May 1, 2009 at 4:01 AM, Eric Auer e.a...@jpberlin.de wrote:
Hi Bart,
thanks for making the patch much shorter, very commitable now :-)
Why did our old code do that complex put bp at [bp+2] thing? And
don't know
what does the cpm_error jump decision now inverted patch mean?
skips
2009/5/1 Eric Auer e.a...@jpberlin.de:
Why did our old code do that complex put bp at [bp+2] thing?
I don't know; it is old code from Pat Villani. Perhaps it wanted to do an extra
pop bp from that place but bp was already set to sp so that would be
wrong too.
-pushbp
- Christian: entry.asm revamp to fix the CP/M call (review!)
http://sf.net/tracker/?func=3Ddetailaid=3D2421577group_id=3D5109atid=
=3D105109
anyone know of any CP/M like programs or applications to test these with?
There's some C library based on the CALL 5 but I never used it. My test
On Thu, Apr 30, 2009 at 8:18 PM, Bart Oldeman
bartolde...@users.sourceforge.net wrote:
...
This is a minimal fix for the kernel:
--- entry.asm (révision 1371)
+++ entry.asm (copie de travail)
...
This bug has been there since the DOS-C days by the way!
Bart
Thank you!
Patch committed
Hi Bart, admins, others,
Would you like to have access again? Should be no problem :-)
Sure!
Apparently only Aitor, Jim and Pat can give you SVN write
access but I think that would be a *very* nice idea... ;-).
I noticed Pat already uploaded your SYS OW 1.8 fix :-).
If you plan to patch
free time at last...
On Wed, Apr 29, 2009 at 8:49 PM, Eric Auer e.a...@jpberlin.de wrote:
Hi Bart, admins, others,
Would you like to have access again? Should be no problem :-)
Sure!
Apparently only Aitor, Jim and Pat can give you SVN write
access but I think that would be a *very* nice
Hi Eric,
2009/4/25 Eric Auer e.a...@jpberlin.de:
Would you like to have access again? Should be no problem :-)
Sure!
Question about the change in OpenWatcom headers which
now apparently want 32 bit arguments for 16 bit values,
which breaks not only SYS but also other DOS apps:
- why did
Hi Bart,
here's a patch to be able to compile SYS with OW 1.8. I've lost SVN
commit access...
Would you like to have access again? Should be no problem :-)
+#if defined(__WATCOMC__) __WATCOMC__ 1280
unsigned short date, time;
+#else
+ unsigned date, time;
+#endif
Question about
Hi Christian,
If you're waiting for further improvements to 2038 before you release
2038, then you're doing this wrong. [...] I'd strongly recommend
making 2038 available, and putting the few pending improvements in
2039.
The problem is that Eric holds back at least three necessary
Examples:
- handling of floppy before disk is inserted / unformatted partitions
- initdisk CHS geometry fix and BSS init fix from RayeR
- int 21.1c non-FAT / non-existing drive handling fix from Tom
If anyone wants to contribute to discussions about this patches he can do
now.
seems
Hi Christian,
- handling of floppy before disk is inserted / unformatted partitions
- initdisk CHS geometry fix and BSS init fix from RayeR
- int 21.1c non-FAT / non-existing drive handling fix from Tom
If anyone wants to contribute to discussions about this patches
he can do that now.
Simple: If you only use WIN /S then you can use the
stable 2036 or stable 2038 kernel. The latter is on
http://rugxulo.googlepages.com/ as binary snapshot.
There are a few pending improvements before 2038 can
be put on sourceforge file releases... The sources
already are on sourceforge in
Hi Roberto,
result of a quick test in dosemu: I used the install tool
to set sound to none for fm, speaker for voice and then
selected update to store settings. Now start,bat starts
some endless loop of animation. Running indark2 8 0 by
hand without the -d of the batch file lets me access a
menu
- int 21.1c should report invalid drives via AL (keep other regs?)
News here: DR-DOS modifies BX/CX/DX but not DS for inv drives.
/* Get Drive Data */
case 0x1c:
{
BYTE FAR *p;
if (p = FatGetDrvData(lr.DL, lr.AL,
Hi Hans,
The easy fix to this is use Watcom 1.2.
The current versions are 1.7 and 1.8 release candidate,
where and why would one download a years-old OW 1.2...?
I must say that the kernel compiled well with OW 1.3 of
2004, but I wonder whether newer versions work better.
I use latest version
Here is the IsShareInstalled patch which also does
not seem to be commited to SVN yet?? The goal is
to reduce the share install check call floods that
FreeDOS would normally cause. The side effect is
minimally later detection of share, should be fine.
Thanks for commenting :-)
Eric
diff -bur
Hi Tom,
here is one of two diffs for patches that I have not
commited to SVN because I was waiting for review...
Topic: Handle floppy type 6 and use DF_DISKCHANGE and
DF_NOACCESS as well as InitializeAllBPBs in a way which
should help disk tools to avoid confusion about FAT1x
versus FAT32.
One more thing Auer: Can you edit my other two posts and delete my surnames?
I use this mail with my friends but I don´t like very much that my surnames
appear in a public page.
In the last post I don´t wanted put with I always use X=test with
Jemmex; with EM386 ram highscan. and with Yes, I
I am still interested in a precompiled debug version.
Eric Auer schrieb:
continuing the topic on freedos-kernel instead of
freedos-user, maybe one of the kernel list readers
has a precompiled kernel for you or can compile a
kernel or several with debug options according to
your choice
From your description, it looks like there is a bug in pkzip. That is a
comercial product, so the answer is simple: BUY one and ask for support...
As to unzip, it is freeware, well supported, and in fact it is a port of
the Linux program. That is why it behaves more in a unix way, and has
Travis Siegel escreveu:
Not exactly.
This error does not occur in msdos or drdos, only freedos, Ergo,
freedos is at fault.
That's why I wanted to know if there was any way to track down the
error, so it could be fixed.
Then you are correct... I hope that you can help in fixing it :)
201 - 300 of 1070 matches
Mail list logo
