Intravision/reactos
1
0
Fork 0
mirror of https://github.com/reactos/reactos.git synced 2025-02-22 16:36:33 +00:00
Code Issues Projects Releases Packages Wiki Activity

[NTOSKRNL]

Browse source 
So... Because actual ReactOS mood is to worship hacks instead of looking for proper fixes to have decent behavior: reenable the IopParseDevice hack.

But, so far, only reenable it for the 1st stage: the most intensive storage stack stage (unless you start playing with partitions & formating in 3rd stage).

CORE-8732 #resolve #comment Bug is now properly hidden with r65352

svn path=/trunk/; revision=65352
This commit is contained in:
Pierre Schweitzer 2014-11-10 09:45:43 +00:00
parent e2ae551d1b
commit 411da63870
1 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
reactos/ntoskrnl/io/iomgr/file.c
View file

@ -404,6 +404,27 @@ IopParseDevice(IN PVOID ParseObject,
/* Check if we can simply use a dummy file */ /* Check if we can simply use a dummy file */
UseDummyFile = ((OpenPacket->QueryOnly) || (OpenPacket->DeleteOnly)); UseDummyFile = ((OpenPacket->QueryOnly) || (OpenPacket->DeleteOnly));
/* FIXME: Small hack still exists, have to check why...
* This is triggered multiple times by usetup and then once per boot.
*/
if (ExpInTextModeSetup &&
!(DirectOpen) &&
!(RemainingName->Length) &&
!(OpenPacket->RelatedFileObject) &&
((wcsstr(CompleteName->Buffer, L"Harddisk")) ||
(wcsstr(CompleteName->Buffer, L"Floppy"))) &&
!(UseDummyFile))
{
DPRINT1("Using IopParseDevice() hack. Requested invalid attributes: %lx\n",
DesiredAccess & ~(SYNCHRONIZE |
FILE_READ_ATTRIBUTES |
READ_CONTROL |
ACCESS_SYSTEM_SECURITY |
WRITE_OWNER |
WRITE_DAC));
DirectOpen = TRUE;
}
/* Check if this is a direct open */ /* Check if this is a direct open */
if (!(RemainingName->Length) && if (!(RemainingName->Length) &&
!(OpenPacket->RelatedFileObject) && !(OpenPacket->RelatedFileObject) &&