Hi. I am requesting that everyone with a little spare time and a PCI
network card that works with a clearly redistributable packet driver
(in the licence, like a crynwr packet driver), to email me their
PCIsleep output and either tell me what driver it works with if it is
in the crynwr packet driv
There is a major release blocker where if "/1"=="/1" echo yes fails
with an invalid switch, where it worked in 0.83. This is very
important to many batch files, and reduces the compatibility with
manny things. This should really be fixed before 0.84 gets released.
--
Eric Auer escreveu:
But again, the problem only shows up if you use 386 optimizations
in the kernel. You can also reduce the fortification cost by telling
OpenWatcom "this function is known to trash those registers" instead
of adding extra code to save all registers all the time (even at
place
Hi...
> Except he didn't find out saving registers would fix things. He dug into
> it, got some debugging information and then flatly decided _without_
> verification that register usage definitely _was_ the problem...
So I gave exact information on how this could be tested, and Jeremy, who
a
At 05:47 PM 7/25/2005 -0300, Alain wrote:
Hi Michael, Eric, Arcady and Jeremy,
I have just read all this thread at once. It sounds just like a big quiproquo.
1) Eric pinpointed one problem to a register modification
2) He found out that new compile options could solve it, temporaryly only
mea
Hi Alain,
> 1) Eric pinpointed one problem to a register modification
Yes. EMM386 modifies registers that do not even exist on 8086,
and it does so only during EMM386 initialization. As the MS DOS
kernel is 100% 8086 compatible, it does not hurt there.
> 2) He found out that new compile options
Hi Bernd,
I use that dummy aproach too, but I use the *previous8 environment for
small utility programs that return stuff in environment variables. And
yes, they free the dummy variables to get space.
Alain
Bernd Blaauw escreveu:
So, what's the best way to find the master environment loca
Is there eny FreeDOS specific way of finding the previous environment
and the master environment?
I used this a lot and I had to convert a lot of batch files :(
Alain
Eric Auer escreveu:
Hi, yes FreeCOM does not support int 2e (for non-programmers:
int 2e is "send a command to the master com
Alain schreef:
I would like LH to be Accepted(!) by FreeCOM, even if functionality
behind this command has been disabled.
???
It is working here! Is this new?
it's disabled for the 8086+ XMS-swapping version of Freecom 0.84PRE.
Otherwise FreeCOM wouldn't compile.
Bernd
--
Bernd Blaauw escreveu:
I would like LH to be Accepted(!) by FreeCOM, even if functionality
behind this command has been disabled.
???
It is working here! Is this new?
Alain
---
SF.Net email is sponsored by: Discover Easy Linux Migration
tom ehlert escreveu:
IMO, scince FS, GS, and the high parts of EAX,... aren't used by MSDOS
as well, drivers can get away when they destroy these resisters,
so it's a good idea to save them as well.
This gets complicated when Kernel is 386 optimized. MS-DOS never
modified this because it is
Hi Michael, Eric, Arcady and Jeremy,
I have just read all this thread at once. It sounds just like a big
quiproquo.
1) Eric pinpointed one problem to a register modification
2) He found out that new compile options could solve it, temporaryly
only meant it as a test. It is *not* clear at all
Alain schreef:
I agree with this, and if simplicity in the number of versions
available is an issue, have 386+ and 8088 versions (being 286+
optimized is ok whenever possible, and whenever the differences
between the 286-optimized and 386-optimized versions are small.
Furthermore, this is somet
same
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.
I vote with Aitor on this issue
Alain
I agree with this, and if simplicity in the number of versions available
is an issue, have 386+ and 8088 versions (being 286+ optimized is ok
whenever possible, and whenever the differences between the
286-optimized and 386-optimized versions are small.
F
Alex Buell schreef:
On Mon, 25 Jul 2005, Eric Auer wrote:
Apart from, of course, detecting the master environment location in
RAM and tweaking the contents there in place.
So, what's the best way to find the master environment location then?
what are you planning to do with it then?
if yo
Hi Jeremy,
I tested your new FreeCOM with /LFN and it works great. Bu I have one
suggestion:
For an end-user, it is very strange not to have all files in the right
side, just the ones with LFN. It is ok for us devellopers, but they tend
to get confused with it. So, I would appreciate very mu
Johnson Lam escreveu:
Hi Arkady,
PS: Next time, don't use "Program Files" directory, when install dumb
programs like from Adobe.
I love your comment.
I love that too ;-)
In my case it is a user supplied machine with an old, heaven knows how,
instalation...
Cheers,
Alain
---
Alex Buell schreef:
I do wonder if FreeDOS Kernel build 2034b will work with MS-DOS 6.22
COMMAND.COM...
FreeDOS kernel has a VERSION= statement for config.sys.
I don't know if it's executed before or after loading the shell.
MS COMMAND.COM from win98 runs on freedos fat32-enabled kernel, which
Hi, yes FreeCOM does not support int 2e (for non-programmers:
int 2e is "send a command to the master command.com instance
in RAM") yet, so you cannot change the master environment in
any other way than creating a batch file and running that
from the prompt of the master shell for now.
Apart from
Hi, as Blair (also) wants a shorter beep in FreeCOM, I suggest
to do the following:
- edit beep_l.c and beep_n.c and remove the sound() / delay() / nosound()
and replace them by "printf("\b");" or similar. A more sophisticated
solution would involve an option to the BEEP command of FreeCOM
At 02:58 PM 7/25/2005 +0200, Eric wrote:
Hi, while the XMS spec is not specific about the internal version
number of himem, RBIL is:
Call the XMS driver "Get XMS version number" function with:
AH = 00h
Return: AX = XMS version (in BCD, AH=major, AL=minor)
BX = internal revision
Blair Campbell schreef:
I would like to see a shorter beep when autocompleting filenames, as
the beep is too long and actually causes it to be faster sometimes to
type the filename out.
I would like LH to be Accepted(!) by FreeCOM, even if functionality
behind this command has been disabled. t
I would like to see a shorter beep when autocompleting filenames, as
the beep is too long and actually causes it to be faster sometimes to
type the filename out.
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM
Eric Auer schreef:
Well it worked for me, but I tested by typing LABEL C: enter
and then typing the label when prompted. Maybe FreeCOM
compressed the spaces on the LABEL command line, you should
try LABEL C: "TEST TEST" of similar... Anyway, my test result
is that VOL displays the label with the
Hello Eric,
>> works under FreeDOS at least, under NTFS still fails.
> That can be a problem with your NTFS driver,
AFAIK, that's a problem with the network redirector which can't return
more them 4GB total/free size
tom
---
SF.Net email is
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 are) exac
Hi Bernd,
> > 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
Well it worked for me, but I tested by typing LABEL C: enter
and then typing the label when prompted. Maybe FreeCOM
compressed the spaces
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
fix: VOL: syntax error if extra whitespace after drive {KJD}
add: CDD: if given path to a valid filename, ignore filename portio
On Mon, 25 Jul 2005 16:40:15 +0200, you wrote:
Hi Aitor,
>> Please calm down both and return to normal work on FreeDOS!
Eric recently talk too much, now seems back to work.
We're all hoping to improve FreeDOS, but can't push too much, poor
guys like Jack Ellis need to find a job, he's 60 years
Hi... some new thoughts on the "EMM386 trashes 386-specific registers
(and only such!) during init (but not during other activities)" problem:
MS DOS _kernel_ was plain 8086 compatible, so even though you were
supposed to preserve ALL registers, you could trash all THOSE registers
which MS DOS wou
It seems I was a bit late with my reply to Eric. Needless to say I agree
with Robert.
Aitor
Robert Riebisch escribió:
Joe Cosentino wrote:
You are an asshole.
Did you notice Eric's "Hope for ... peace on the list"? I think, that Eric
is *not* an asshole. He already did a lot for FreeDOS (
I dislike the style of this kind of letters, specially when directed to
Bernd and Jeremy, who appart from others (like Michael or yourself, also
testers like Alain, and many more) are working quite actively to get the
project alive.
Eric Auer escribió:
>>What stops you from collecting those fi
Hi,
Eric Auer escribió:
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.
This sucks. Release an update. You have had the binary for months.
How unpolite!.
Hi,
Michael Devore escribió:
MEMCHECK checks for illegal INT 15h function 87h memory transfers
to/from the real RAM address range -- the CHECK and MEM parts of the
MEMCHECK option -- and dynamically builds and sets two scratch page
tables to allow the access to occur if it is outside of normal
Hi, while the XMS spec is not specific about the internal version
number of himem, RBIL is:
Call the XMS driver "Get XMS version number" function with:
AH = 00h
Return: AX = XMS version (in BCD, AH=major, AL=minor)
BX = internal revision number (in BCD for HIMEM.SYS)
DX =
Hello Kenneth,
>> 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 The I
On Sun, 24 Jul 2005 03:22:32 +0200, you wrote:
Hi,
>It could be that the, say, three versions are bundled together within an
>executable, and by means of some trick, the correct version is unpacked
>and run, but note that the executable version would grow a bit.
>Perhaps Eric can come up with o
tOn Sun, 24 Jul 2005 03:18:45 +0200, you wrote:
Hi,
>> But sadly, FreeDOS still not v1.0, that means it's still have some
>> kind of bugs.
>which is cause, which is consequence? ;-)
Chicken and Eggs :-)
Better to say this way: If FreeDOS are DONE, no more MS-DOS!
>I agree with this, and if sim
39 matches
Mail list logo
