> Emacs (freemacs) definitely does NOT support files
> larger than 64k. I don't know about the others.
Well Emacs has a Unix version which has a DOS port,
same for VI / VIM :-) You can get the DOS port here:
(the parent directory has even more DOS apps and v2misc/cwsdpmi)
Most of the readme is about compiling it, but you can
of course download a precompiled version. You will need
CWSDPMI (delorie.com), HDPMI (japheth.de) or a similar
DOS extender to make the 32bit DOS EMACS work :-).
http://www.vim.org/download.php#pc tells that you should only
use the 16bit version if you are desparate (missing features,
quickly runs out of memory) and that the 32bit version needs
DPMI and has all the big features. Interestingly, to get long
file names in Win2k/NT/XP, you need a special Win32 version
as the DOS 32bit version only does DOS long file names...
only has the sources but Rugxulo at least has a bat to compile
it without having to install a big pile of autoconf and make
tools first :-p. See: http://rugxulo.googlepages.com/
and there http://rugxulo.googlepages.com/edlin-dl.txt ...
I tried an old EDLIN 2.8 which seems to be a 16bit DOS app
and with 626k DOS RAM free it was able to open a file made
using "head -c168k < intlist.txt > file.txt" (173 kBytes,
3882 lines). With 507 kB free (Quarterdeck Manifest / MFT
loaded, now freeware :-)) the EDLIN limit was 134 kBytes.
That would mean that 16 bit EDLIN for FreeDOS needs exactly
3 bytes of RAM for each byte of text you want to edit, maybe
more if you actually edit the text instead of only open it.
Plus it needs roughly 100-110 kB or so of general overhead.
Because of various overhead, FreeDOS EDIT seems to have a
limit of about 62 kB per file (crashes if tab expansion on
open makes the file go above that). With 626 kB DOS RAM
free, the most that I could squeeze out of EDIT 0.7d was
opening 4 files of 62 kBytes each and 1 file of 32 kBytes,
giving me a combined 280 kBytes to edit simultaneously.
Editing only 1 tiny file already takes 199 kB of general
overhead according to MFT so I would say that EDIT takes
on average ( 626-199 ) / 280 = 1.5 bytes of RAM for each
byte you want to edit. This is because it does internally
use sparse data structures such as escapes embedded into
the in-RAM copy of the text and only 1 copy of the text.
Other nice things linked from the Rugxulo Googlepage:
http://laaca-mirror.ic.cz/ - Blocek editor (uses 32bit Freepascal)
(has fresh clamav clamscan DOS binaries and other goodies, too)
www.freebasic.net/ - did you already get the recent update of this
32bit BASIC with a "QBASIC dialect mode"? :-) Active forum, too!
http://ndn.muxe.com/beta/ NDN file manager with editor etc etc :-)
(yet another list, by Rugxulo, of editors for DOS :-) JED maybe?)
(Freemacs indeed is 16bit only, written in Assembly language)
Unrelated nice thing: A combined UDMA/SATA/IDE/ATAPI/CD/DVD/disk driver:
http://www.freebasic.net/forum/viewtopic.php?t=6449 says between
the lines that Blocek indeed has no small text file size limit
and that djgpp RHIDE is yet another possibility to edit things.
Page 2 of the thread also lists editors *written* in FreeBASIC.
> > www.freedos.org/cgi-bin/lsm.cgi?mode=dir&dir=edit
> > Blocek, Emacs, Fed, OS+ Editor, TDE, SETEdit, VIM, Edlin...
> > I believe 32bit versions of Blocek, Vim, Emacs, Edlin do
> > support files above 64 kB. TDE and SETEdit definitely do,
> > but maybe are a bit big to install. TDE also has a bit of
> > an odd menu system if you have a non-US keyboard. Please
> > try and report which editors you like and which not :-).
> > Classic FreeDOS EDIT supports max 64 kB per file but you
> > can edit several files at the same time with it... :-).
> >> Necromancer Dos Navigator (NDN)
> >> For me, this has been one of the best application ever created!
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Freedos-user mailing list