X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient:	djgpp-workers AT delorie DOT com
Subject:	Re: DJGPP on NTF with SFN creating disabled [was : gcc-8.1.0 packages
	for testing]
To:	djgpp-workers AT delorie DOT com
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>
From:	"Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp-workers AT delorie DOT com]" <djgpp-workers AT delorie DOT com>
Message-ID:	<df616b96-646c-788b-3177-87de740f03ae@iki.fi>
Date:	Sat, 5 May 2018 17:04:55 +0300
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
	Thunderbird/52.7.0
MIME-Version:	1.0
In-Reply-To:	<5AED9B44.90000@gmx.de>
X-MIME-Autoconverted:	from Quoted-Printable to 8bit by delorie.com id w45E4x3b031019
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv 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

- Raw text -