--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
While changing laptops, I installed the latest Win32
self-installing Gforth 0.6.2, and my programs promptly stopped loading,
giving file I/O errors. (Under Win XP Pro). As I've used the previous
0.6.2 self-install with no problems, I had it on my old drive, and when
I replaced the new cygwin1.dll (1,114K, 2004-08-01) with the old one
(949K, 2003-08-30), everything was fine again. The symptom is that
INCLUDED cannot load any file that has directory specifiers in the name.
If I say S" test1.f" INCLUDED, and the file is in the current
directory, it works, but if the command is
S" /elko/work/forth/new-oof/test1.f" INCLUDED, it fails. (It fails with
both dir separators, / and \, while INCLUDE works with the DOS standard
\ separator only).
Is there a significant reason to use the new cygwin1.dll as opposed
to the old one? I don't see anything wrong with the old one so far, but
maybe there's some hidden issue?
- [gforth] Broken cygwin1.dll? Elko Tchernev
- Re: [gforth] Broken cygwin1.dll? Anton Ertl
- Re: [gforth] Broken cygwin1.dll? Elko Tchernev
- Re: [gforth] Broken cygwin1.dll? Anton Ertl
- Re: [gforth] Broken cygwin1.dll? M. Edward (Ed) Borasky
