Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Wim Brul

Pages: 1 ... 11 12 [13] 14 15 ... 20
181
Multimedia / Re: USB Audio
« on: March 13, 2017, 11:51:12 am »
Hallo Roberto,

Quote
The question, Is it normal for the device list to show me the internal devices?
And I ask this because I only have two accessories connected. One wifi mouse, and relay board2303.
When I show the other two internal usb, if I pulse the wifi on / off one of them disappears and appears.

It is normal that both the internal and external connected devices are shown in the device list.
It is possible on some systems  that the bios allows you to enable/disable internal connected devices.
There are devices that disappear/ reappear as part of their device specific initialization sequence.

The 03F0:231D device - Broadcom Corp HP Integrated Module - is one of those device that first appears as one type of device and later on (after disappear/reappear) shows op as a different type of device.

The 138A:0007 device - is your Fingerprint Reader.

Regards

182
Multimedia / Re: USB Audio
« on: March 12, 2017, 05:01:08 pm »
For proper result you MUST have DEVICE=C:\OS2\BOOT\USBRESMG.SYS in your CONFIG.SYS file. If you REM it out then you get RC=0x1B58.
I ran your script over here and I get USBCALLS 14.210  and USBRESMG 14.210 which is correct for with my latest set.

183
Multimedia / Re: USB Audio
« on: March 09, 2017, 12:37:59 pm »
Quote
About drop outs in Firefox: maybe that cannot fully be avoided. It might happen on high interrupt load. Isochronous transfer will lead to a fairly steady interrupt load. If something else is busy in the system (hard disk etc.) that might lead to a delay in interrupt processing.

Most likely the drop outs of sound in firefox occur when the sample rate is too low to be handled in time. It probably occurred when the sound was playing too fast. The usb audio driver goes into a kind of overdrive to spit out the 16 bit stereo sound samples at a rate of 44.1 kHz. whereas the application produces say 8 bit mono sound at 8 kHz. hence lack of samples occur  i.e. drop out of sound. Moreover the overdrive operation results in an interrupt load that is in this case 2*2*44100/8000 i.e. 22 times so high. I am having sound dropouts when I play the macaw.avi file which produces 8 bit mono sound at 22.050 kHz.

Wim

184
Multimedia / Re: USB Audio
« on: March 04, 2017, 06:25:52 pm »
Nice Neil,

I wonder if you would need the following to ensure stereo output:
Code: [Select]
'sox' wav.i '-b 16' outputFile 'channels 2 rate -s -a 44100 dither -s'

Wim

185
Multimedia / Re: USB Audio
« on: March 03, 2017, 03:57:45 pm »
Hi Neil,

I bought a Trond USB Audio Adapter, and it works just as Lars said. There is good sound, except for System Sounds.

You might try and convert the system sounds yourself with the IBM Wave Doctor application that I think is part of the IBM Multimedia Presentation Manager Toolkit/2.
\ MMOS2\MMTOOLKT\ NEATSTUF\WVDOC\WVDOC.EXE

Wim

186
Applications / Re: Can I use a usb port as a com-port?
« on: January 28, 2017, 08:41:05 pm »
Since it has a Prolific 067B:2303 USB-Serial Controller, I agree with Ivan that USBCOM.SYS has to be used.

187
Applications / Re: Can I use a usb port as a com-port?
« on: January 28, 2017, 02:59:50 pm »
Quote
The case is that I wanted to use a circuit board with 8 relays that has a usb connection.

Since it has a usb connection, I would plug it into a usb port and control it through the usbcalls rexx interface functions.

Which circuit board is it? What documenmtation do you have?

188
Web applications / Re: What are we mising to run "Jitsi" on the Browser ?
« on: January 07, 2017, 03:38:55 pm »
Hi Martin,
The way to go is via the generic usbcalls interface. My specific usbecd.sys driver should not be used. 
Just curious, when you say "usbecd.sys driver should not be used" do you mean that it should not be called directly by an application? or that is should not be used at all?
No and No. This is what I meant: To access webcams from an application like firefox you should not use my usbecd.sys driver. There are 2 reasons for that. First of all you would need a very specific device driver statement in config.sys for the particular webcam that a user wants to use. Plugging in a different webcam would require config.sys to be changed. And secondly usbecd.sys has by design insufficient isochronous buffering capability to sustain high speed and high bandwidth operation especially on larger image sizes.

189
Web applications / Re: What are we mising to run "Jitsi" on the Browser ?
« on: January 05, 2017, 07:56:42 pm »
Hi Martin,

Quote
Outside Firefox I think we also miss a way to connect Wim Brul's USBECD (webcam driver) to firefox.

The way to go is via the generic usbcalls interface. My specific usbecd.sys driver should not be used. The current OS/2 port of libusb needs to be enhanced to include support for isochronous transfers.

Perhaps an implementation based on Webcamd - a FreeBSD userspace Linux Kernal Drive framework could be used? Webcamd is a small daemon that enables about 1500 different USB based webcam, DVB and remote control USB devices under the FreeBSD-8.0 and later operating system. The webcam daemon is basically an application which is a port of Video4Linux USB drivers into userspace on FreeBSD. The daemon currently depends on libc, pthreads, libusb and libcuse4bsd.

Perhaps one or more of the Webcam programs working with webcamd in FreeBSD could be ported?

 

190
Applications / Re: cups and usb printers
« on: December 09, 2016, 12:35:44 pm »
Hi Pete,

Hi Wim

I believe I was using this package ftp://ftp.netlabs.org/pub/ecups/install/libusbdll10.wpi - original link on http://trac.netlabs.org/ecups/wiki/CupsPort - which contains:-

25-05-13  6:20p        45,790    230 a---  libusb10.dll

The version listed in the wpi file is 1.0.16.1

Same date as the version in libusb-1.0.16-rc6-20130525.zip but different time. Is the file size different?


Regards

Pete

Thanks for reporting back. I compared both files. Their size and binary content are the same. Only the time appears to be different.

Regards,

Wim

191
Applications / Re: cups and usb printers
« on: December 08, 2016, 12:32:24 pm »
Hi Pete,

Happy to report that the new libusb10.dll seems to have done the trick and my usb printer has just churned out the cups test page.

Great - I'll work on getting an updated libusb10.dll added to my site. I'll probably need to add a disclaimer around usbresmg.sys/usbcalls.dll dates around which build should be used....

Cheers,

Paul

Hallo Paul and Pete,

I installed this new libusb10.dll on my laptop and it works as well for me as the one that I had before. The only difference that I noted is that the new one has debug logging enabled whereas the older one has not. I do not have a usb printer, but I can scan with my CanoScan LIDE 210 scanner and lsusb.exe works too.

LIBUSB10.DLL - 25-05-2013 11:20:28 <- libusb-1.0.16-rc6-20130525.zip
LIBUSB10.DLL - 07-12-2016 09:49:08 <- libusb-20161207.zip

This makes me wonder what version Pete had on his system and where it came from.

Regards,

Wim         

192
Applications / Re: cups and usb printers
« on: December 06, 2016, 05:18:52 pm »
Since October 2013 I have been working on the implementation of isochronous transfers in USB Resource Manager. I have produced (beta test) matched sets of usbcalls.dll and usbresmg.sys that are backwards compatible. I have removed old code both in usbresmg.sys and usbcalls.dll for functions that were never properly supported. Existing synchronous transfer functions work well again and I have implemented these as asynchronous too. I have added code for the new asynchronous isochronous transfer functions. All of my changes have found their way into the Arca Noae and Lars Erdmann usb driver sets. 

There is no need for existing applications to be relinked. During regression testing both PtPro110 and Camera15 did not find an attached ptp camera. Both programs were updated to increase their UsbQueryDeviceReport report buffer size from 1024 to 4096 bytes. This was necessary to cater for usb devices with large compound descriptors. Otherwise no ptp camera would be found at all when such a device was present. In addition PtPro110 was updated to have its CloseSession routine not passing 1 parameter which it shouldn't.  The updated applications ptpro111.zip and camera153.zip are available on hobbes. 




193
Storage / Re: MTP plugin for Netdrive?
« on: October 27, 2016, 12:17:21 pm »
I looked into detect.log and I see starting on line 1883 :

Code: [Select]
libusb: 2.459000 debug [libusb_open] open 1.2
libusb: 2.459000 debug [os2_open] unable to open device - id= 22b8/2e82  rc= ff0c
libusb: 2.459000 debug [os2_open] open: rc = ff0c, fd -1
libusb: 2.459000 debug [os2_open] open, set device configuration: rc = ff37, fd -1

FF0C= ERROR_I24_GEN_FAILURE. The open fails because it has already been opened before.
FF37= ERROR_DEV_NOT_EXIST. The set configuration fails because of the invalid fd (-1) value.
I suspect that it would have worked with the  fd value (35651590) of the outstanding open.

I wonder about the event reported in line 43:

Code: [Select]
libusb_detach_kernel_driver() failed, continuing anyway...: Error 0

May be thIs is causing the problem? 

194
Applications / Re: Problems with Tame
« on: October 01, 2016, 09:29:12 pm »
I now successfully :) scanned using Tame/2. Only libusb-1.0.16-rc6-20130525.zip and scanimage-20130525.zip are required.

1). I copied LIBUSB10.DLL into D:\ECS\DLL and 2). I copied SCANIMAGE.EXE into D:\PROGRAMS\TAME

Ivan, for you these 2 steps are sufficient since Tame/2 already knows your scanner.

3). I added my scanner to D:\PROGRAMS\TAME\CONF\GENESYS.CONF

Code: [Select]
#Canon LiDE 210
usb 0x04a9 0x190a

I needed to select Canon LiDE60 from the list of supported scanners.

195
Applications / Re: Problems with Tame
« on: October 01, 2016, 06:29:59 pm »
Do those work if plugged into the Tame install or do you use something else to scan with?
I must say that I did not use the Tame/2 install nor do I use Tame/2 to scan with my Canon CanoScan LIDE210 scanner. This scanner is not available in the list of scanners shown by Tame/2. My Tame/2 installation came with eComStation 2.0 and could be too old. I don't know. I use scanimage.exe directly. I did not yet send Paul Smedley the 'device.txt' file for my scanner.

Pages: 1 ... 11 12 [13] 14 15 ... 20