Hi again, we are getting closer :-)

Mozilla is a bit huge, but did you try Arachne to surf the web with DOS?
For text editing, I recommend TDE (32bit) and TED (16bit) for DOS, and
joe (because it feels a bit like WordStar and the Borland programming
editors, and is quite powerful) for Linux. For "that really focussed
feeling", I sometimes run joe in text mode (100x37 in my case). But when
I am logged in on the GUI, I love it to have several windows at a time:
one or two "joe", some "less" for the manuals (intlist, for example :-)),
up to two DOS windows (for compiling and running, therefore two), and a
Netscape, Mozilla, Sylpheed or shell window for my mail. I do not know
much about Dexter, but TDE and TED are both free, at least ;-).

There are zillions of Norton Commander clones both for DOS and Linux, but
I usually do not use any of them...

Sure, viruses and internet worms work with all OSes. In DOS, a virus can
easily infect the whole computer. In Linux, you have more server-infecting
worms than file-infecting viruses: People run too many servers without
keeping track of updates with Linux - Windows and Dos just offer very few
servers, so the issue is more focused (Outlook worms, IIS worms, Office and
program viruses). There is one reason why DOS web browsers are a bit safe:
No DOS virus ever expected the victim PC to be networked ;-) (well, hardly
and, I guess - given 70.000 different MS DOS/Win/Office virusses, you never
know...). Here, multiuser helps you to limit the damage. If your system runs
from a readonly media or is recreated in a ramdisk on each reboot, cleaning
is as easy as rebooting, no matter what OS you have. By the way, with VFAT
partitions for your data and the system software mounted readonly, you get
pretty close to the "hit reset at any time, no problem" with Linux (but there
are /etc and /var and maybe others that -I- would consider to be better on a
"real" filesystem than on a VFAT partition, while those have to be writeable).

When I kill an app in Linux, its memory is definitely released. But when I
kill something with mark/release in DOS, I still have to be extra careful
not to have some bent interrupt vectors left behind dangling in the void.
I think it is hard to compare FF and FIND, but once your metadata is in the
cache, both are pretty fast ;-).
Waitasec? How about pressing ctrl-s (stop scrolling) and ctrl-q (continue)?
Or run "sleep 5s" to wait 5 secs?
The boot messages end up in a file in Linux - they are too long for just a
few hits of the printscreen button. But I have to admit that the button
style is nice, too (I prefer to use THAT button as sysrq button for some
emergency tricks - something in between control-alt-delete and the cold
reset button that systems often miss nowadays - as if Windows would never
crash anymore...).

Dos is definitely an artistic medium. And ANSI-ASCII arts and b/w film are
indeed cult :-). By the way, I have some problem with "the Matrix" and
Dosemu: As the "cyclic RTC interrupt" is not yet simulated in Dosemu, the
"paska" intro (4k category, www.assembly.org 1999) freezes in Dosemu. You
can replace the RTC timeline by something else to make the intro run, but
having a better RTC simulation would be even better...:

http://www.coli.uni-sb.de/~eric/stuff/dos-ega/ dosemu/paska.zip
(the whole dos-ega tree contains things that are hard for Dosemu 1.1.3.7...)

Eric

PS: While DOS is nice to "count your electrons" in case of trouble, the
Linux "rescue disks" (floppy or CD) are also quite helpful. Much better
than having to install Windows to figure things out ;-).

----------
list options/archives/etc.: http://www.topica.com/lists/fd-dev
unsubscribe: send blank email to: [EMAIL PROTECTED]

==^================================================================
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2
Or send an email to: [EMAIL PROTECTED]

T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================

Reply via email to