Mail Archives: djgpp/2011/08/31/15:45:05
Hi,
On Aug 31, 2:17 pm, Juan Manuel Guerrero <juan DOT guerr DOT DOT DOT AT gmx DOT de> wrote:
> Am Mittwoch, 31. August 2011 schrieb Eli Zaretskii:
>
> > > From: Juan Manuel Guerrero <juan DOT guerr DOT DOT DOT AT gmx DOT de>
> > > Date: Wed, 31 Aug 2011 00:27:21 +0200
>
> > > cc1.exe: c:/djgpp-2.04/bin/../lib/gcc/djgpp/3.44/djgpp.ver: Value too large (EOVERFLOW)
> > > 1.c:1:19: c:/djgpp-2.04/include/stdio.h: Value too large (EOVERFLOW)
>
> > Can you find out where did this error message come from? Which system
> > call or library function emits EOVERFLOW?
>
> The functions generating EOVERFLOW are filelength() and lfilelength(). Both of
> them usefunction 0x7A46 to get the file size if LFN support is available. But I
> assume that neither MSDOS nor DOSLFN provide the required function. May we
> need to disind a better to certainly identify the OS used.
I don't have easy access to MS-DOS 6.22 these days (old 486 is
disconnected, too painful to setup right now, half dead anyways), but
I vaguely remember seeing similar issues.
You could try StarLFN instead, it should work, but no promises how
well. In particular, I can't remember exactly, but you may or may not
have to make the LONGNAME.DAT file not be +H (hidden), at least on
FreeDOS, not sure about MS-DOS. (It also supports direct VFAT access a
la DOSLFN, but I usually avoid that.)
http://sta.c64.org/starlfn.html
starlfn /i
...
starlfn /u
P.S. I didn't write it, obviously, but at one time I did get the crazy
idea to rebuild it with JWasm for 8086, and esp. strip out all the
(unneeded, patented) VFAT crud. Never got around to it, of course.
Still would be worth doing, IMHO. (And it's not hard, just tedious.)
- Raw text -