[Freedos-user] Freedos Future

2006-07-22 Thread busch-co
Hi,

When reading the messages in developer mailing list, I'm wondering about where 
FreeDOS is moving.
The developers are only blaming each other whole time. There's no normal 
discussion possible.
If you say something wrong than I'll kick your ass off the mailing list!.
That's just kidding.
Why always discuss things off-list? Has the rest of the dos community no right 
to see what's going on in the development of the software they are using?

Even if Johnson told wrong facts in the field of programming, I must say that 
Michael Devore is the wrong man to judge this.
It's a fact that his himem and emm386 clones are absolutely useless in a 
productive environment.
There are too many bugs concerning different types of hardware and freedos very 
often crashes when using emm386.
Using Jack R. Ellis qhimem and Uwe Sieber's umbpci is the only way to use 
Freedos with UMBs on nearly all kinds of harware by always using the same 
settings.
It's o.k. to ask why Jack is not going to give his sources to the freedos 
community, but this is up to him. If he doesn't want other people to have a 
look at qhimem code than it is allright.
But his memory manager is without any doubt the better and more reliable 
product for everydays use even if there are some features missing.

The worst thing is that Michael doesn't care about bug reports from the dos 
users that have problems running things like doom.
But what does he say in his emm386 help file:
IF IT WORKS FOR YOU - FINE. IF IT DOESN'T - STOP USING, BUT DON'T COMPLAIN.

You're all talking about the upcoming 1.0 release. And I made my contribution 
to get rid of bugs.
But no one cares.
Since I discovered the bug introduced in command.com 0.84pre2 that redirection 
of ouput to a file isn't possible anymore I hear nothing.
I sent different floppy images to Blair and Eric to reproduce the bug but 
nothing happens.
Statement from Blair: I can't reproduce the bug by using qemu.
Statement from Eric: I won't open any images at the moment.
Was it this hard to say: Oh yes, you're right. I'm working on this. or is it 
Blair's last crusade to push Freedos to level 1.0 whatever will happen?

Did you ever try your own software without using an emulated environment like 
qemu which is still in beta state and additionally not able to reflect 
different hardware?

I know you have all spent a lot of your freetime at programming code for the 
freedos community and everyone using freedos won't forget.
But I think freedos development has come to an end. The euphoric mood of the 
last weeks about the upcoming 1.0 release is getting less and less as you can 
see by reading the postings on the list.

If the remaining developers still want to give release 1.0 a chance they should 
discuss things in a more better way.
Let's see where the project leads.

And if you are all angry now, you can kick my ass off the list.

Norbert.


Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren
ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT JETZT bei Arcor: günstig
und schnell mit DSL - das All-Inclusive-Paket für clevere Doppel-Sparer,
nur  44,85 €  inkl. DSL- und ISDN-Grundgebühr!
http://www.arcor.de/rd/emf-dsl-2

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Freedos Future

2006-07-22 Thread Michael Devore
As a matter for record, since it's been incorrectly reported twice now: 
FreeDOS, HIMEM, and EMM386 work fine with Doom.  It was one of the first 
tests of VCPI support and is often checked against as a baseline.  There 
are no known applications which fail under FreeDOS HIMEM or EMM386 with the 
FreeDOS kernel and which work with Microsoft or other version memory 
managers under the FreeDOS kernel.

The rest of the original post is even less accurate.  Unfortunately , I did 
expect off-list marshalling of  allies for further posts and personal 
attacks, which has come to pass.  It's a sad situation: no winners, we all 
lose from this behavior.

As promised, I won't respond further other than to clear up direct 
misstatements of fact that confuse FreeDOS users into believing something 
doesn't work when it does.


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Freedos Future

2006-07-22 Thread Eric Auer

Hi all,

my excuses for the length of this mail. I hope at least
Norbert and Blair will read all of it :-). The other
readers of the EMM386 2.11 thread might want to join ;-)


For all the rest, the summary is: There is less poison in
the community than you think. HIMEM and EMM386 are better
than you think but improving them is a good thing. There
is a FreeCOM update available (newer than our ISO). The
list is quiet because Blair etc are processing 1.0 devel
things behind the scenes, but not behind the scenes to
keep the community from enjoying the development. QHIMEM
has some undocumented extra features. DOOM works with
HIMEM, too. The don't complain sentence in the EMM386
docs is years old and from Tom, not from Michael. Sorry
for the miscommunication about the FreeCOM / diskimage
issue, Norbert. Explicit and detailled bug reports are
better than blaming people for bugs in general.



Please stop reading here if you only want to get an
overview. Well, do not forget to browse the text below
a bit anyway, to find the new FreeCOM download URL ;-).




 When reading the messages in developer mailing list, I'm wondering about 
 where FreeDOS is moving. The developers are only blaming each other 
 whole time. There's no normal discussion possible...

This is not true. You just read the mailing list at the one moment
when a flamewar about qhimem was going on.

 Why always discuss things off-list? Has the rest of the dos 
 community no right to see what's going on in the development of the 
 software they are using?

Honestly, I think the rest of the dos community does not say
anything at all, not even off-list. For example nobody writes
mail about my cache, neither on-list nor off-list, probably
because the cache has been working well enough recently :-).
So it is not the case that we use the list only for flamewars
and discuss all improvements off-list :-). You should also
visit the IRC if you are interested in the latest distro news
and gossip ;-).

 Even if Johnson told wrong facts in the field of programming, I must say 
 that Michael Devore is the wrong man to judge this. It's a fact that his 
 himem and emm386 clones are absolutely useless in a productive 
 environment. There are too many bugs concerning different types of 
 hardware and freedos very often crashes when using emm386. Using Jack R. 
 Ellis qhimem and Uwe Sieber's umbpci is the only way to use Freedos with 
 UMBs on nearly all kinds of harware by always using the same settings.

Very harsh words about FreeDOS HIMEM / EMM386. I think I deleted
MS HIMEM and MS EMM386 a year ago because the FreeDOS versions
were actually BETTER than the MS DOS 6.xx ones for me! They have
smaller memory footprint and work better with modern hardware...
On some hardware, UMBPCI has better performance and/or stability
than EMM386. But for example on my test PC, UMBs created by UMBPCI
are slow memory, and loading CPU-intensive stuff like a cache to
that area makes the whole thing slow. UMBPCI also depends on having
exact knowledge about your particular mainboard chipset, while
EMM386 should work on all 386 and newer systems. Problems with
EMM386 are usually caused by incompatible BIOSes. You should test
if MS DOS EMM386 works with those BIOSes. If yes, please report.
If no, you cannot blame EMM386 - you are then simply stuck in a
situation where no protected mode based UMB providers work, and
where you have to revert to the real mode driver UMBPCI (which
cannot provide EMS, but most DOS programs do not need EMS...).

Later I installed the MS versions again for testing purposes with
Windows, but again found that Win3.1 works better with FD HIMEM :).

Notice that 386 enh mode of Win3.1 and WfW3.11 only works with
MS EMM386, but that all Win 3.x versions come with MS EMM386 on
the Win 3.x install diskettes anyway. The background is that the
heavy tweaks of 386 mode to make DOS true multitasking include
replacing the whole emm386 on the fly with a built-in driver
of the Windows kernel, which requires a complex interface called
GEMMIS. Nothing else apart from Windows uses GEMMIS, and because
of this, FreeDOS EMM386 does not include GEMMIS.

 [qhimem] is without any doubt the better and more reliable product
 for everydays use even if there are some features missing.

Did you try the FreeDOS memory managers in their newest versions?
Yes there were problems with EMM386 about VDS / SCSI / SATA in the
past, but at least HIMEM has been working fine for me for a long time.

The only advantage of QHIMEM is that it uses even less DOS memory.

As Jack does not reveal his sources, it is hard to tell which
other advantages ought to exist. I hear that he has allow an IRQ
window after every move of a few (2? 4? 8?) kilobytes of XMS, to
improve realtime handling, but I doubt that this is actually
relevant unless you have a gbit ethernet card on a 486...?

 The worst thing is that Michael doesn't care about bug reports from the 
 dos users that have problems running