This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
- From: Samuel Thibault <samuel dot thibault at labri dot fr>
- To: cygwin at cygwin dot com, cygwin-apps at cygwin dot com, Ton van Overbeek <ton at v-overbeek dot nl>
- Date: Mon, 26 Mar 2007 22:44:38 +0200
- Subject: Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
- References: <20070324151544.GA3541@interface.famille.thibault.fr> <20070324200659.X11058-100000@xs2.xs4all.nl> <20070324192106.GE3541@interface.famille.thibault.fr> <20070326084251.GA21641@calimero.vinschen.de>
Hi,
Corinna Vinschen, le Mon 26 Mar 2007 10:42:51 +0200, a écrit :
> On Mar 24 20:21, Samuel Thibault wrote:
> > > > Actually, I'm wondering: instead of trying to make libusb0.sys work
> > > > from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in
> > > > libusb-install, to just copy it into c:\windows\system32\drivers\ and
> > > > then use the usual libusb-win32 filter setup? That works fine and
> > > > actually makes the patch simpler...
> > >
> > > I am pretty sure that would solve the problem.
> >
> > Yes it does, but the question to cygwin developers is: is it ok
> > packaging-wise?
>
> If it helps to work better, it should be ok in this case.
It will help a lot yes. What is the best way to get the
C:\windows\system32\drivers directory ? %systemroot%\system32\drivers,
%windir%\system32\drivers or something else ?
Samuel