From 0ce19565ede0c20d5310d59b6f4a6ad7e679d1d6 Mon Sep 17 00:00:00 2001
From: Thomas Faber <thomas.faber@reactos.org>
Date: Sat, 2 Feb 2013 13:27:49 +0000
Subject: [PATCH] [NTOSKRNL:MM] - Ignore the unsupported MEM_TOP_DOWN flag
 instead of failing NtAllocateVirtualMemory CORE-6392 CORE-6805 #comment
 MEM_TOP_DOWN should be sufficiently fixed in r58266, and setup now starts.
 Please confirm.

svn path=/trunk/; revision=58266
---
 reactos/ntoskrnl/mm/ARM3/virtual.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/reactos/ntoskrnl/mm/ARM3/virtual.c b/reactos/ntoskrnl/mm/ARM3/virtual.c
index 3d3b4a1f25d..55562cc7134 100644
--- a/reactos/ntoskrnl/mm/ARM3/virtual.c
+++ b/reactos/ntoskrnl/mm/ARM3/virtual.c
@@ -3856,8 +3856,7 @@ NtAllocateVirtualMemory(IN HANDLE ProcessHandle,
     if ((AllocationType & MEM_TOP_DOWN) == MEM_TOP_DOWN)
     {
         DPRINT1("MEM_TOP_DOWN not supported\n");
-        Status = STATUS_INVALID_PARAMETER;
-        goto FailPathNoLock;
+        AllocationType &= ~MEM_TOP_DOWN;
     }
     if ((AllocationType & MEM_RESET) == MEM_RESET)
     {