X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: 1.7.0 CVS mmap failure Date: Mon, 15 Jan 2007 14:47:58 -0000 Message-ID: <024601c738b4$26412220$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <45AB899F.8090802@innobec.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 15 January 2007 14:03, Pierre Baillargeon wrote: > About the reason why the last 64K just before 2GB can't be used in > Windows, I'll refer you to this post in The Old New Thing blog by > Raymond Chen, who regularly discusses such obscure compatibility issues. > > See http://blogs.msdn.com/oldnewthing/archive/2003/10/08/55239.aspx. > > (Short answer: it has to do with address fixup when loading executable > image and the influence of the alpha processor on the design.) Presumably you got that link from the post about six posts back in this thread where it was first mentioned...? ;) http://cygwin.com/acronyms#YSHFRTT! cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/