X-Spam-Check-By: sourceware.org Message-ID: <46C38C51.4377EB05@dessent.net> Date: Wed, 15 Aug 2007 16:29:21 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Bug Report: ioperm.sys on Windows Server 2003 x64 References: <.84 DOT 74 DOT 50 DOT 189 DOT 1187218911 DOT squirrel AT www DOT adenet DOT biz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 adombi AT adenet DOT biz wrote: > \??\C:\cygwin\bin\ioperm.sys has been blocked from loading due to incompatibility > with this system. Please contact your software vendor for a compatible version of > the driver. Yes, there's no way a 32 bit driver should work in a 64 bit OS. > Suggestion: Since ioperm.sys seems to be a kernel mode > driver, it needs explicit support for native 64Bit mode. > Can you compile this driver in x64 mode? > (E.g. name it iopermX64.sys) There are two problems here. One is that the driver needs to be ported, i.e. there is more to it than just recompiling. Two is that there is no Free 64 bit compiler. The free MS Visual Studio Express is 32 bit only and gcc has not been ported to 64 bit Windows. (There is an x86_64-pc-mingw32 port that is a work in progress but it's still in the early stages and not released yet.) So I'm not sure if the ioperm maintainer (or the Cygwin project, for that matter) would be comfortable releasing a binary package that requires an expensive proprietary toolchain to rebuild. Brian -- 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/