Message-Id: <1.5.4.32.19961020202847.00672960@mv.mv.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 20 Oct 1996 16:28:47 -0400 To: Eli Zaretskii From: Howard Kaikow Subject: Re: HK: v 2.1 Cc: Howard Kaikow , djgpp AT delorie DOT com At 06:11 PM 10/20/96 +0200, Eli Zaretskii wrote: > >On Sun, 20 Oct 1996, Howard Kaikow wrote: > >> However, I did notice one more thing. Before I changed te option to -O2 from >> -O3 I did a >> >> rename *.exe *.exe0 >> >> However, the .exe0 got overwritten by the new .exe files. So I guess that >> the loader (or something) does not honor LFN = y. > >Are you sure that ``something'' isn't Windows 95 itself? There is a >nasty bug in Windows 95 RenameFile function whereby sometimes the long >filename changes, but the short 8+3 filename does not! Therefore, as far >as Windows 95 is concerned, the file was effectively not renamed. This >only happens for certain filenames, but maybe *.exe0 is just one of these >names? Please try renaming the files again and compare the short 8+3 >filenames before and after the rename. I did before and I just did it again. PSBOOK EXE 96,897 10-20-96 11:21a psbook.exe0 PSSELECT EXE 98,204 10-20-96 11:22a psselect.exe0 PSTOPS EXE 106,933 10-20-96 11:22a pstops.exe0 PSNUP EXE 108,399 10-20-96 11:22a psnup.exe0 PSRESIZE EXE 106,035 10-20-96 11:22a psresize.exe0 EPSFFIT EXE 101,321 10-20-96 11:21a epsffit.exe0 6 file(s) 617,789 bytes >Anyway, since the filenames that the compiler generates in your case are >well within 8+3 DOS limits, I think this problem cannot be in any way >connected with LFN support in DJGPP v2.01. The problem is that it is overwriting the .exe0 files as if they were .exe. That is an LFN problem in 2.01. For example: 1. Make a text file, x.abc0 2. open the file with Edit x.abc0 3. While in Edit, do a FileSaveAs with the name x.abc 4. Exit Edit Both x.abc0 and x.abc exist, so it is not a Win 95 problem.