libusb-win32-devel

Re: [Libusb-win32-devel] using libusb filter without installing it

[Stephan M. <ste...@we...>]

> hi folks
> i tried to use the dll in a test app without installing it with the filter installer
> 
> i've no compiling or linking errors, my app find usb hosts but no devices attached (yes, i've plugged them :) 
> 
>  if i install the filter driver and i try again all works
> 
> is there a way to avoid installer?
> 

No, you have to install the driver, either as a filter or as a normal device driver. 
Otherwise the DLL won't work.

> thanks and congratulations for the project
> Marco
>  


______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

[Libusb-win32-devel] x64 driver

[Matt M. <ml...@ay...>]

This may be a dumb question since the name of the project is libusb-win*32*. 
Does libusb have support for Windows XP x64?

Thanks,
Matt

[Libusb-win32-devel] using libusb filter without installing it

[Marco F. <fab...@gm...>]

hi folks
i tried to use the dll in a test app without installing it with the filter
installer

i've no compiling or linking errors, my app find usb hosts but no devices
attached (yes, i've plugged them :)

if i install the filter driver and i try again all works

is there a way to avoid installer?

thanks and congratulations for the project
Marco

[Libusb-win32-devel] Looking Digital Music MP3 and MP4 Player ReSeller

[Stephen Y.K. Lee<sa...@ei...>]

Dear Sir / Madam

I would like to introduce myself as Stephen YK Lee working in GoodsWell Limited which specializes
in MP3, MP4, HD Player.

You will be interested to hear that our EiONE MP3, MP4 and HD MP4 Player, which is selling very strongly
on the home market.

Because of its success in this country, we thought there might be sales potential abroad, and we would
welcome your advice as to whether, in your opinion, there is a market in your district.

If you were interested in our EiONE MP3, MP4 and HD MP4 Player or inspect the full range of our products.
please visit our web site or contact me.

Stephen Y.K. Lee
Sales Manager

E-Mail:
st...@ei...

Messenger ID:
Skype: goodswell
Yahoo: stephen_mail2002
MSN: st...@go...

Hong Kong Office:
Tel: +852 2139-5781
Fax: +852 2139-5782

Factory in China:
Tel: +86 755 61601071
Fax: +86 755 61601072

GoodsWell Limited (EiONE Digital)
E-mail: st...@ei...

































NEVER SEND SPAM. IT IS BAD.

[Libusb-win32-devel] (no subject)

[krivoshein <kri...@sh...>]

confirm 345291

 

RE: [Libusb-win32-devel] will this be libusb-win32's death?

[Stephan M. <Ste...@ia...>]

Using UMDF could be an option if it will provide the necessary features,
but since it's not released yet, I don't know if it will actually be=20
useful.

Stephan


> I thought that UMDF would sort this out for Vista? Couldn't win32-libusb
> use a user mode interface to USB to implement the library?
>=20
> Dan.
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log=20
files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=103432&bid#0486&dat=121642
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] will this be libusb-win32's death?

[Andy G. <an...@wa...>]

IC-...@t-... wrote:

Hi Juergen -

> So far as I understand the chapter "How to Disable Signature
Enforcement during
> Development" is that you need to press all times F8, use a kernel
debugger or
> have a special release of bcdedit to disable signing enforcement.

Sure, but one can also just sign all builds of the driver and use it on
a normal, signed-only, OS.

>>Why should one care any more if a signed driver you were developing
>>escapes into the wild than if the same unsigned driver escaped?  Is

> If an unsigned driver "escapes", it wouldn't be executed by Vista.
> But an signed driver would be usable as driver.

Yes, agreed.  What I meant was, why should a company developing drivers
care more if a signed vista driver 'escapes' than they should if an
unsigned XP driver 'escapes'.

Perhaps Adam Megacz had an answer, the unspoken reason is that if MSFT
do not like what your driver does, they will blacklist your signing cert
and so disable you from the Windows market :-/

-Andy

Re: [Libusb-win32-devel] will this be libusb-win32's death?

[<IC-...@t-...>]

>From: Andy Green <an...@wa...>
>
>IC-...@t-... wrote:
>
>> after reading=20
>>=20
http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599ba=
c8184
>> a/x64KMSigning.doc
>> it becomes clear: You need a special release of Vista/Longhorn or a kern=
el=20
>> debugger installed for development.
>
>Hi Juergen -
>
>It does not seem to say that... it seems to me to say that you can
>indeed integrate the signing action into your makefile and sign
>everything if you are willing to sacrefice "security best practices":
>
[..]
>Tip: Rather than signing drivers throughout the development process,
>developers can disable signing enforcement as described in =93How to
>Disable Signature Enforcement during Development=94 later in this paper.
>There is always some risk that software under development could end up
>in the public realm. If the software is signed with a PIC, it could
>misrepresent the company to whom the PIC belongs.

So far as I understand the chapter "How to Disable Signature Enforcement du=
ring=20
Development" is that you need to press all times F8, use a kernel debugger =
or=20
have a special release of bcdedit to disable signing enforcement.

>
>After functional testing for a milestone is complete, the development
>team should sign the kernel-mode software module with the PIC, load the
>driver on a system that has signing enforcement enabled (such as a
>system without a kernel debugger attached), and verify that the module
>behaves as expected. For both =93test=94 and =93release=94 signing, the
>development team should follow best practices for key management, as
>described in =93How to Safeguard Code Signing Keys=94 later in this paper.
>
>... ''
>
>This is only recommendation in the paper that you use a system with
>signing enforcement disabled for development.  It's arguably better to
>test the thing on a system that is as realistic as possible compared to
>the end user systems...
>
>Why should one care any more if a signed driver you were developing
>escapes into the wild than if the same unsigned driver escaped?  Is
>there a liability issue or is it understood that everyone developing for
>Windows is in favour of the secure path driver stuff and it would be
>terrible if it was broken?  If that is the problem, people working on
>drivers outside of the secure path crap need have no fear it seems to me..=
.

If an unsigned driver "escapes", it wouldn't be executed by Vista.
But an signed driver would be usable as driver.


Greetings
=09Juergen

[Libusb-win32-devel] Re: will this be libusb-win32's death?

[Adam M. <me...@cs...>]

Andy Green <an...@wa...> writes:
> Is this scenario not a possible solution: a FOSS-friendly company will
> be given, or will develop a driver-loading driver.  Sort of like
> ndiswrapper but all native to Win64.  The company will sign a binary of
> their driver-loading driver and make it public domain.  Everyone who
> wants to ship unsigned drivers will bundle the signed driver-loading
> driver to get their driver loaded in two steps.

And the very next Windows Update will include said FOSS-friendly-company's
certificate on the new a Certificate Revocation List.

When Verisign accidentally issued a codesigning certificate with
Microsoft's name on it to somebody who wasn't Microsoft, this is how
they handled it.

  - a

-- 
PGP/GPG: 5C9F F366 C9CF 2145 E770  B1B8 EFB1 462D A146 C380

Re: [Libusb-win32-devel] will this be libusb-win32's death?

[Andy G. <an...@wa...>]

IC-...@t-... wrote:

> after reading=20
> http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d5=
99bac8184
> a/x64KMSigning.doc
> it becomes clear: You need a special release of Vista/Longhorn or a ker=
nel=20
> debugger installed for development.

Hi Juergen -

It does not seem to say that... it seems to me to say that you can
indeed integrate the signing action into your makefile and sign
everything if you are willing to sacrefice "security best practices":

''...
Best Practices for Code Signing through Development, Test, and Release
When a driver package is publicly released=97whether it is a beta or fina=
l
version=97it must be digitally signed. However, signing with a PIC should=

take place only near the end of the development process for that
milestone, for the following reasons:
If packages are signed after each iterative build, then the best
practices for protecting the code signing keys can become tedious and
expensive.
Tip: Rather than signing drivers throughout the development process,
developers can disable signing enforcement as described in =93How to
Disable Signature Enforcement during Development=94 later in this paper.
There is always some risk that software under development could end up
in the public realm. If the software is signed with a PIC, it could
misrepresent the company to whom the PIC belongs.

After functional testing for a milestone is complete, the development
team should sign the kernel-mode software module with the PIC, load the
driver on a system that has signing enforcement enabled (such as a
system without a kernel debugger attached), and verify that the module
behaves as expected. For both =93test=94 and =93release=94 signing, the
development team should follow best practices for key management, as
described in =93How to Safeguard Code Signing Keys=94 later in this paper=
=2E

=2E.. ''

This is only recommendation in the paper that you use a system with
signing enforcement disabled for development.  It's arguably better to
test the thing on a system that is as realistic as possible compared to
the end user systems...

Why should one care any more if a signed driver you were developing
escapes into the wild than if the same unsigned driver escaped?  Is
there a liability issue or is it understood that everyone developing for
Windows is in favour of the secure path driver stuff and it would be
terrible if it was broken?  If that is the problem, people working on
drivers outside of the secure path crap need have no fear it seems to me.=
=2E.

-Andy

Re: [Libusb-win32-devel] will this be libusb-win32's death?

[<IC-...@t-...>]

Hello

>From: Andy Green <an...@wa...>
>
>IC-...@t-... wrote:
>
>> doesn't it result in an hen and egg problem:
>> How should an driver be written and _tested_, if it must be signed to run;
>> but it needs to be written and tested to become signed?
>
>It at least can be done that you buy the cert from verisign, and then
>can sign driver versions as many times as you like with the cert without
>going back to verisign.  At least until your year is up and you must pay
>again.  It's not AIUI like the Windows Testing Qualification where you
>send the driver off and *they* sign it.
>
>So I assume there is no problem as you describe.

after reading 
http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184
a/x64KMSigning.doc
it becomes clear: You need a special release of Vista/Longhorn or a kernel 
debugger installed for development.


Greetings
	Juergen

Re: [Libusb-win32-devel] will this be libusb-win32's death?

[Andy G. <an...@wa...>]

IC-...@t-... wrote:

> doesn't it result in an hen and egg problem:
> How should an driver be written and _tested_, if it must be signed to run;
> but it needs to be written and tested to become signed?

It at least can be done that you buy the cert from verisign, and then
can sign driver versions as many times as you like with the cert without
going back to verisign.  At least until your year is up and you must pay
again.  It's not AIUI like the Windows Testing Qualification where you
send the driver off and *they* sign it.

So I assume there is no problem as you describe.

-Andy

Re: [Libusb-win32-devel] will this be libusb-win32's death?

[<IC-...@t-...>]

Hello,

>From: Stephan Meyer <ste...@we...>
>Date: Sun, 22 Jan 2006 18:13:26 +0100

>- no one will be able to build custom USB devices for in-house or private use
>anymore unless one pays MS and Verisign a lot of money just to get a custom
>driver signed and installed

doesn't it result in an hen and egg problem:
How should an driver be written and _tested_, if it must be signed to run;
but it needs to be written and tested to become signed?

So I guess, there must be somekind of developermode in which an unsigned driver
could run at Longhorn/Vista.


Greetings
	Juergen

RE: [Libusb-win32-devel] will this be libusb-win32's death?

[Dan E. <Dan...@ne...>]

Stephan Meyer wrote:
> I just found this article on Microsoft's web site:
>=20
> http://www.microsoft.com/whdc/system/platform/64bit/kmsigning.mspx
>=20
> Some discussion and further information about this issue can be found
> here:=20
>=20
> http://www.osronline.com/showThread.CFM?link=3D86311
>=20
> If Microsoft is actually implementing this "feature" in their
> upcoming Windows Vista release then:=20
>=20
> - all open source kernel projects, including libusb-win32, will die
> sooner or later=20
> - all open source and hobbyist projects utilizing these open source
> kernel projects will die=20
> - no one will be able to build custom USB devices for in-house or
> private use anymore unless one pays MS and Verisign a lot of money
> just to get a custom driver signed and installed =20
>=20
> Hopefully some large organization or government will sue Microsoft
> and stop this stupid nonsense.=20
>=20
> Any comments?

I thought that UMDF would sort this out for Vista? Couldn't win32-libusb
use a user mode interface to USB to implement the library?

Dan.

Re: [Libusb-win32-devel] will this be libusb-win32's death?

[Andy G. <an...@wa...>]

Stephan Meyer wrote:
> I just found this article on Microsoft's web site:
> 
> http://www.microsoft.com/whdc/system/platform/64bit/kmsigning.mspx
> 
> Some discussion and further information about this issue can be found here:
> 
> http://www.osronline.com/showThread.CFM?link=86311
> 
> If Microsoft is actually implementing this "feature" in their upcoming
> Windows Vista release then:
> 
> - all open source kernel projects, including libusb-win32, will die sooner
> or later

Hi Stephan -

I had some experience hacking the original Xbox which involves
cryptographic signing.

This problem may not so bad as it as first seems.

Is this scenario not a possible solution: a FOSS-friendly company will
be given, or will develop a driver-loading driver.  Sort of like
ndiswrapper but all native to Win64.  The company will sign a binary of
their driver-loading driver and make it public domain.  Everyone who
wants to ship unsigned drivers will bundle the signed driver-loading
driver to get their driver loaded in two steps.

-Andy

[Libusb-win32-devel] will this be libusb-win32's death?

[Stephan M. <ste...@we...>]

I just found this article on Microsoft's web site:

http://www.microsoft.com/whdc/system/platform/64bit/kmsigning.mspx

Some discussion and further information about this issue can be found here:

http://www.osronline.com/showThread.CFM?link=86311

If Microsoft is actually implementing this "feature" in their upcoming
Windows Vista release then:

- all open source kernel projects, including libusb-win32, will die sooner
or later
- all open source and hobbyist projects utilizing these open source kernel
projects will die
- no one will be able to build custom USB devices for in-house or private use
anymore unless one pays MS and Verisign a lot of money just to get a custom
driver signed and installed

Hopefully some large organization or government will sue Microsoft and
stop this stupid nonsense.

Any comments?

Stephan



__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsstarkeren E-Mail-Postfach!		
Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131

Re: [Libusb-win32-devel] Recognize the port and the bus where the device is connected

[Tecnico V. <te...@vi...>]

I resolved the problem installing the libusb-win32-filter 0.1.10.1 (not =
only the driver for my device).
Now the driver recognize all the devices connected to PC with the =
correct port and bus number.

  >> I'm using libusb-win32 to interface my software with some usb =
devices.=20
  >> The devices have the same serial number and I don't now how to=20
  >> discrimanate between them.=20
  >
  >Under Windows, if devices have a serial number, then this number MUST =

  >be unique, otherwise they won't install correctly.=20

  My devices use the DSP 5509 from TI configured to perform the boot =
from PC.
  I have no problem to install multiple devices.


  >> With the latest version of libusb can I recognize the port and the=20
  >> bus where the device is connected?=20
  >
  >The lastest version provides some information about bus topology but=20
  >this code will be removed in the future since it doesn't work =
properly.=20

  Yes, I see, the driver recognize the correct port but not the bus.
  I use the latest snapshoot, I have one device on bus2 and one device =
on bus 3 but the driver tell me all devices are connected on bus 1.
  There is a way to make it recognize the correct bus?

  Thanks,=20
  Valle Gianni.

Re: [Libusb-win32-devel] Recognize the port and the bus where the device is connected

[Tecnico V. <te...@vi...>]

>> I'm using libusb-win32 to interface my software with some usb =
devices.=20
>> The devices have the same serial number and I don't now how to=20
>> discrimanate between them.=20
>
>Under Windows, if devices have a serial number, then this number MUST=20
>be unique, otherwise they won't install correctly.=20

My devices use the DSP 5509 from TI configured to perform the boot from =
PC.
I have no problem to install multiple devices.


>> With the latest version of libusb can I recognize the port and the=20
>> bus where the device is connected?=20
>
>The lastest version provides some information about bus topology but=20
>this code will be removed in the future since it doesn't work properly. =


Yes, I see, the driver recognize the correct port but not the bus.
I use the latest snapshoot, I have one device on bus2 and one device on =
bus 3 but the driver tell me all devices are connected on bus 1.
There is a way to make it recognize the correct bus?

Thanks,=20
 Valle Gianni.

[Libusb-win32-devel] libusb documentation / libusb-win32 compiler

[Mark B. <mc...@ec...>]

Just a quick suggestion/query regarding the libusb documentation... 
Would it be possible to make a single zip file, containing all the 
documentation, available for download? It would save having to download 
all the separate pages. Some of us are still in the dark ages and only 
have a dial-up connection ;-) Apologies if you already intend to do this 
for V1.0.

Also, with libusb-win32, I was originally using GCC from DJGPP 
(http://www.delorie.com/djgpp/), and couldn't even compile the 
testlibusb example - it was complaining about missing functions (eg. 
snprintf). I installed MSYS and MinGW and it worked first time. I don't 
know if it's worth putting a comment on the web page about other GCCs 
possibly not working? It's not that it's an older version either - DJGPP 
has GCC 4.0.1, while MinGW is only GCC 3.2.3.

Thanks for all the hard work - it certainly makes life easier for those 
of us who don't know exactly what we're doing with device drivers!

Mark.

Re: [Libusb-win32-devel] Recognize the port and the bus where the device is connected

[Stephan M. <Ste...@ia...>]

> Hi,
> 
> I'm using libusb-win32 to interface my software with some usb devices.
> The devices have the same serial number and I don't now how to 
> discrimanate between them.

Under Windows, if devices have a serial number, then this number MUST 
be unique, otherwise they won't install correctly.

> With the latest version of libusb can I recognize the port and the 
> bus where the device is connected?

The lastest version provides some information about bus topology but
this code will be removed in the future since it doesn't work properly.

Apart from that, even if you were able the retrieve the correct bus and 
port
number of your device you still can't keep the devices apart. 
Why? Because there is no way to correlate these numbers with your physical
hub or bus ports.

So the only way the distinguish between two identical devices are serial 
numbers.

Stephan


> 
> Thanks,
> Valle Gianni.

[Libusb-win32-devel] Recognize the port and the bus where the device is connected

[Tecnico V. <te...@vi...>]

Hi,

I'm using libusb-win32 to interface my software with some usb devices.
The devices have the same serial number and I don't now how to =
discrimanate between them.
With the latest version of libusb can I recognize the port and the bus =
where the device is connected?

Thanks,
Valle Gianni.

[Libusb-win32-devel] using libusb-win32 together with libftdi

[<mo...@te...>]

Has anyone tried to use libusb-win32 together with libftdi from intra2net?
(http://www.intra2net.com/de/produkte/opensource/ftdi/index.php).

I have the problem that, when I try to read data from the device via libftdi
based on libusb-win32, I only receive some single bytes with very high values
(between 248 and 255). Using the same software under Linux with libusb works
correctly.

Thanks for any suggestions.

------------------------------------------------------------
This mail was sent through TecO-Webmail: http://www.teco.edu

Re: [Libusb-win32-devel] USB printing

[Stephan M. <ste...@we...>]

> l=5Fi=5FReturn =3D usb=5Fcontrol=5Fmsg( l=5FUSBDev,  0x10100001B, 1, 0,  0, Data, 10=
, 2000 );  =20
> according to the USB print spec, and what I could make out from your met=
hod, with
> no avail (error code -22 - incorrect parameter)

Which programming language is this=3F C=3F
The second parameter looks suspicious. What's the type of it=3F Binary=3F=3F=3F

Also, use usb=5Fstrerror() to retrieve a more detailed error message.

Stephan


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=

Erweitern Sie FreeMail zu einem noch leistungsst=E4rkeren E-Mail-Postfach!	=09
Mehr Infos unter http://freemail.web.de/home/landingpad/=3Fmc=3D021131

Re: [Libusb-win32-devel] INF wizard crashes

[Stephan M. <ste...@we...>]

Yes, that's it. I never tried file names without the .inf suffix.
A fixed version is in the CVS.

Stephan

> 
> This has worked fine for me on Windows 2000 Pro, but just done a bit of 
> experimenting. Long file names are fine (the default is long). However, 
> it seems to crash if you remove the .inf extension or change the extension.
> 
> Mark.
> 
> 
> Brad Kingston wrote:
> 
> > I see the same problem under XP. The way I got it to work was to make 
> > sure I didn't change the filename of the .inf to be created (left it 
> > as your_file.inf when doing the save). It may not like filenames/paths 
> > that don't conform to 8.3 naming conventions.
> >
> > BK
> >
> >> From: Stephen Wenzler <ste...@ve...>
> >> Reply-To: lib...@li...
> >> To: lib...@li...
> >> Subject: [Libusb-win32-devel] INF wizard crashes
> >> Date: Tue, 20 Dec 2005 17:12:06 -0500
> >>
> >> Hello everybody, I'm having problems using INF wizard that comes with 
> >> libusb-win32-device-bin-0.1.10.1 package, once I chosen the device 
> >> that I want to create INF file, and after I am done and ready to save 
> >> the new .inf file, when I click on 'Save' button, suddenly, it just 
> >> crashed with error box appears telling me that the windows have to 
> >> shut it down and creates an error log so I am unable to use the 
> >> software to create .inf file, I'm running Windows 2000 professional 
> >> and could anyone help me fix the problem?
> >>
> >> Thanks!
> >>
> >> -- 
> >>
> >> WWW: http://www.boomspeed.com/stephenw4
> >> EMAIL: ste...@ve...
> >> AIM: S Wenzler
> >>
> >> **for sale**
> >> I have a bunch of items for sale on eBay, click this link below:
> >> http://tinyurl.com/7sxhe
> >>
> >>
> >>
> >> -------------------------------------------------------
> >> This SF.net email is sponsored by: Splunk Inc. Do you grep through 
> >> log files
> >> for problems?  Stop!  Download the new AJAX search engine that makes
> >> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> >> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> >> _______________________________________________
> >> Libusb-win32-devel mailing list
> >> Lib...@li...
> >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> >
> >
> > _________________________________________________________________
> > Express yourself instantly with MSN Messenger! Download today - it's 
> > FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> > files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> > _______________________________________________
> > Libusb-win32-devel mailing list
> > Lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

Re: [Libusb-win32-devel] INF wizard crashes

[Mark B. <mc...@ec...>]

This has worked fine for me on Windows 2000 Pro, but just done a bit of 
experimenting. Long file names are fine (the default is long). However, 
it seems to crash if you remove the .inf extension or change the extension.

Mark.


Brad Kingston wrote:

> I see the same problem under XP. The way I got it to work was to make 
> sure I didn't change the filename of the .inf to be created (left it 
> as your_file.inf when doing the save). It may not like filenames/paths 
> that don't conform to 8.3 naming conventions.
>
> BK
>
>> From: Stephen Wenzler <ste...@ve...>
>> Reply-To: lib...@li...
>> To: lib...@li...
>> Subject: [Libusb-win32-devel] INF wizard crashes
>> Date: Tue, 20 Dec 2005 17:12:06 -0500
>>
>> Hello everybody, I'm having problems using INF wizard that comes with 
>> libusb-win32-device-bin-0.1.10.1 package, once I chosen the device 
>> that I want to create INF file, and after I am done and ready to save 
>> the new .inf file, when I click on 'Save' button, suddenly, it just 
>> crashed with error box appears telling me that the windows have to 
>> shut it down and creates an error log so I am unable to use the 
>> software to create .inf file, I'm running Windows 2000 professional 
>> and could anyone help me fix the problem?
>>
>> Thanks!
>>
>> -- 
>>
>> WWW: http://www.boomspeed.com/stephenw4
>> EMAIL: ste...@ve...
>> AIM: S Wenzler
>>
>> **for sale**
>> I have a bunch of items for sale on eBay, click this link below:
>> http://tinyurl.com/7sxhe
>>
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc. Do you grep through 
>> log files
>> for problems?  Stop!  Download the new AJAX search engine that makes
>> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>> _______________________________________________
>> Libusb-win32-devel mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today - it's 
> FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel