X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f X-Recipient: djgpp-workers AT delorie DOT com Message-ID: <5AEF5D3A.2030409@gmx.de> Date: Sun, 06 May 2018 21:53:30 +0200 From: "Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp-workers AT delorie DOT com]" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.13) Gecko/20101206 SUSE/3.1.7 Thunderbird/3.1.7 MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com Subject: Re: DJGPP on NTF with SFN creating disabled [was : gcc-8.1.0 packages for testing] References: <0244cff9-6176-8aec-bbc2-6fc49602c295 AT iki DOT fi> <558b5ff2-71df-e556-a874-7acbb264c84a AT iki DOT fi> <5AED9B44 DOT 90000 AT gmx DOT de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:Pto7Ci40ealpfVo18fL4t3W6YgCXJFnYDH1hUDHZDsf5Y2yJTeE h1Y6jTgxBF3aaFiWm8kG5mwx/enTKklSIbag2I/d1K8uU5Tez8gAOODhUVrK2vbDUD8u+lL 1Zo1qgXNZhoe7VdOPdeEOA5D+6uUbsSXvaiBdbz/saW3WdaYYdbBaCgiQRDPUC8CBpovT+t Qr7xokPtEm8fXvBxwJAKg== X-UI-Out-Filterresults: notjunk:1;V01:K0:TYVBZUXbBSA=:ZzmSQehz7Tawrh+HKgM6Zs IXcla4ieohdKJjLABnZVU89uF9zMH6XdJNxh6/mkGuje0YjWfoyw73Y40MSz9mEXtMMgwdmXg v4tAzZ1SErfEJs7Gl3TpoiAZ17lAP/z6VAVBtmGCgZ3aWPOg1lCKA/C3/4QAAzGC8g7yrG0Rp XulCQQa9oalAHLq0mk+8OBvCcTkxlysiYA5LvWE4U4F1IQX9Yyod7zlDQWlVlZ3SsYHGG6xAl w7jDagZ+0O8cslgF4mFbdMj43EN3CpVHJxBHg0aM0VH7QL4uLy9RQ6Scnv6LnygdODEGpVKSX MwCWTvMnPTBDGHEjfOxFR7ZC0r6Ax8bzyfczXUZvTmk7hJAgeaiDjZSYYhQFjG0vET1sWk1fv RxgcKFM2jQl7oMMMKUuE9gcRtbquz5U5jV37RrgEmGpfBTWBpMcT4N8xN8TiHYDxUu4Q0UNaA 1NjM3fju/6/5eL3bL7mT1ZHIoAEHzRb+RRupovPF5IGXpNKL/rnOYru8x5agyHpFo+laced7n 1KuF0pXL5iOe2jd7o/na5c2u6vvHAmgmv8PJl/+ssoqq/G5x58l39FzP30QPULDaa3hab7+pV VI39ypARDgr7BR19cE4hDQ2vgs9h3szdia6rFo/h9aeybqIM4OnE8OEF42m5Zl2Y8yBxhwvgZ 6qnCszMboxvY0EdSAbIaRvLIVM3ntOMW4WdwB9fNO5KbNMZbzqEZXWLCA9mdaYLLdKh7Up50l UdNntusWNB1XBI8aYxAo8iu/Vz6/QM//W2gWf/PguVQXPebwCzpeRKmVeOeWSrqUQwyKX1Q6Z xGMlqlI Reply-To: djgpp-workers AT delorie DOT com Am 05.05.2018 16:04, schrieb Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp-workers AT delorie DOT com]: > On 05/05/2018 02:53 PM, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp-workers AT delorie DOT com] wrote: >> Am 04.05.2018 20:28, schrieb Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp-workers AT delorie DOT com]: >>> On 05/03/2018 06:20 AM, Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp-workers AT delorie DOT com] wrote: >>>> gcc-8.1.0 packages (both DJGPP native compiler and cross-compiler RPMs) are available for testing at >>>> >>>> >>>> http://ap1.pp.fi/djgpp/gcc/8.1.0/ >>>> >>>> http://ap1.pp.fi/djgpp/gcc/gcc-version-index.html >> [snip] >>> Possible additional change, which I would like to see in: support of NTFS when SFN creating is disabled by Windows registry setting. Currently attempting open file which has only LFN but not SFN fails with EACCES. I myself do not have all required environments for testing such changes >> >> If it is really required I can check the behaviour on MSDOS-6.22, Win98SE, Win2KSP5 >> and WinXPSP3, But I need some test code that is supposed to fail. >> >> > It is easy to test with any simple test program that tries to open file with LFN preasent and SFN missing. > > 1) disable SFN creating according to Microsoft instructions and reboot. It will not affect any already existing file for which SFN is already present > (https://support.microsoft.com/en-us/help/121007/how-to-disable-8-3-file-name-creation-on-ntfs-partitions) > 2) create some file lite test.file.1 (you can even do it with DJGPP tools as creating file works) > 3) reenable SFN creating in registry and reboot to prevent problems with files created later > > After that You have a test file with missing SFN (one can try 'LFN=N ls -l' to verify that SFN is missing. > 'cat test.file.1' is after that expected to fail. For debugging plain opening file for reading is sufficient for testing. > > Andris OK, I was able to reproduce this for Win2K and WinXP when they read/write on NTFS formated partitions. Have you already designed any fix for this issue? Is there any fix conceivable for this issue when only long filenames have been created? IIRC on FAT file systems the short file name is created first and then the long file name is assigned to it. A long file name without a short filename does not exist, or am I missing something? Regards, Juan M. Guerrero