I am trying to connect my usb webcam to my Transformer Prime. The webcam uses a generic Realtek chipset, which should be supported by the linux kernel. When I connect the webcam via usb I can see the device when executing the lsusb command in the terminal. I can also see that the file /dev/video0 is created after I plug in the webcam, but I cannot find an application that is able to display the stream from the webcam. Is is possible to open this stream using an app under Android?
The problem is probably more that apps like Skype don't expect this to happen and will not provide an option for the webcam and instead rely on the in-built ones.
You might be able to access /dev/video0 from within ubuntu/BT5 on the TFP. I doubt the video performance would be stellar though.
I now found a way to access the webcam. I found an eclipse project under this url: http://brain.cc.kogakuin.ac.jp/research/usb-e.html
The application works and displays the picture from my webcam, but before running the app I had to execute the command "chmod 777 /dev/video0" in the terminal and every time I reconnected the device again.
Thenetstriker said:
I now found a way to access the webcam. I found an eclipse project under this url: http://brain.cc.kogakuin.ac.jp/research/usb-e.html
The application works and displays the picture from my webcam, but before running the app I had to execute the command "chmod 777 /dev/video0" in the terminal and every time I reconnected the device again.
Click to expand...
Click to collapse
nice find
so do you know what app allows you to use those cameras?
or is his app the only once that works atm?
I too am trying to get this to work, I have downloaded and compiled the kogakuin app but how do I compile/load the v4l2_camera_v2.patch? and/or make the necessary kernel mods?
Please Help.
lil-devil said:
nice find
so do you know what app allows you to use those cameras?
or is his app the only once that works atm?
Click to expand...
Click to collapse
This app is the only one I found that works. But so far it works only on my Transformer Prime. On my Samsung Galaxy S2 (Cyanogenmod 9) it crashes the phone when using /dev/video0 and when using /dev/bus/usb/002/003 it just doesn't work. (Maybe I have to compile a custom kernel using the settings the developer describes on his BitBucket page, I will try this tonight)
pjames1972 said:
I too am trying to get this to work, I have downloaded and compiled the kogakuin app but how do I compile/load the v4l2_camera_v2.patch? and/or make the necessary kernel mods?
Please Help.
Click to expand...
Click to collapse
On my Transformer Prime the app just works, I did not make any modifications to the kernel. Just compile the app and upload it to your TF201 and it should work.
Thanks Thenetstriker,
I failed to mention that i am using Iconia A500 rooted stock 3.2 not the TF201.
Today I bought a UVC compliant webcam and I now have the kogakuin eclipse project working on my device.
have you tried putting "chmod 777 /dev/video0" in your ueventd.xxxx.rc script?
Paul
http://forum.xda-developers.com/showpost.php?p=22884164&postcount=3
Thenetstriker said:
This app is the only one I found that works. But so far it works only on my Transformer Prime. On my Samsung Galaxy S2 (Cyanogenmod 9) it crashes the phone when using /dev/video0 and when using /dev/bus/usb/002/003 it just doesn't work. (Maybe I have to compile a custom kernel using the settings the developer describes on his BitBucket page, I will try this tonight)
Click to expand...
Click to collapse
I tried to compile my own Kernel with video 4 linux enabled and the app still doesn't work on my Samsung Galaxy S2. But the device shows up on android. Using the app "USB Device Info" I was able to get the following information about my Logitech webcam USB interfaces, but I don't have the knowledge on how to communicate with USB devices over these interfaces. I think someone who has this knowledge could write an application using the USB Host feature from Android 4.0 to show the webcam picture even without root access.
Code:
Device Info
Device Path: /dev/bus/usb/002/002
Device Class: Miscellaneous (0xef)
Vendor ID: 046d
Vendor Name: Logitech, Inc.
Product ID: 07d2
Product Name: not in db
Interfaces
Interface #0
Class: Video Device (0xe)
Endpoint: #0
Address : 135 (10000111)
Number : 7
Direction : Inbound (0x80)
Type : Intrrupt (0x3)
Poll Interval : 8
Max Packet Size: 16
Attributes : 000000011
Interface #1
Class: Video Device (0xe)
Endpoints: none
Interface #2
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 192
Attributes : 0000000101
Interface #3
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 384
Attributes : 0000000101
Interface #4
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 512
Attributes : 0000000101
Interface #5
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 640
Attributes : 0000000101
Interface #6
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 800
Attributes : 0000000101
Interface #7
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 944
Attributes : 0000000101
Interface #8
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 2688
Attributes : 0000000101
Interface #9
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 2848
Attributes : 0000000101
Interface #10
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 3040
Attributes : 0000000101
Interface #11
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 4992
Attributes : 0000000101
Interface #12
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 5116
Attributes : 0000000101
Interface #13
Class: Audio Device (0x1)
Endpoints: none
Interface #14
Class: Audio Device (0x1)
Endpoints: none
Interface #15
Class: Audio Device (0x1)
Endpoint: #0
Address : 134 (10000110)
Number : 6
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 4
Max Packet Size: 68
Attributes : 0000000101
I've just found a video on YouTube which shows an "UVC Player" which seams to be able to access UVC compatible webcams, but the website that is mentioned on this thread is written in japanese and I didn't find any source code or a sample application:
http://www.youtube.com/watch?v=aieJMBFLEdA
http://www.infinitegra.co.jp/technology/rd_android_uvc1.htm
And another link here:Google crimsonwoods UVCCapture (Sorry not enough posts yet)
Have compiled just need to work out what to do with it
Thenetstriker said:
I now found a way to access the webcam. I found an eclipse project under this url: http://brain.cc.kogakuin.ac.jp/research/usb-e.html
The application works and displays the picture from my webcam, but before running the app I had to execute the command "chmod 777 /dev/video0" in the terminal and every time I reconnected the device again.
Click to expand...
Click to collapse
Are you rooted?
jazzcat007 said:
Are you rooted?
Click to expand...
Click to collapse
Yes, the device has to be rooted for this application, The Android API does not seam to support the isochronous USB interfaces, so no non rooted access possible at the moment.
Thenetstriker said:
Yes, the device has to be rooted for this application, The Android API does not seam to support the isochronous USB interfaces, so no non rooted access possible at the moment.
Click to expand...
Click to collapse
Check this out
someone has already created an app for it .. we just need to cook a new kernel for it
josh_m said:
Check this out
someone has already created an app for it .. we just need to cook a new kernel for it
Click to expand...
Click to collapse
Ok, where do I find this app?
this is a good find, what's the image quality like? is it substantially better than the front facing camera of the Prime?
http://forum.xda-developers.com/showpost.php?p=22884164&postcount=3
josh_m said:
http://forum.xda-developers.com/showpost.php?p=22884164&postcount=3
Click to expand...
Click to collapse
Has anyone tried the files in that link? The thread is for the Xoom, so would the "Development Overlay" and "Tiamat Kernel" work with the other tablets ( I have the Acer A500, but I realize this is a transformer thread) ?
tried to compile my own Kernel with video 4 linux enabled and the app still doesn't work on my Samsung Galaxy S2. But the device shows up on android. Using the app "USB Device Info" I was able to get the following information about my Logitech webcam USB interfaces, but I don't have the knowledge on how to communicate with USB devices over these interfaces. I think someone who has this knowledge could write an application using the USB Host feature from Android 4.0 to show the webcam picture even without root access.
Click to expand...
Click to collapse
Thenetstriker,
Your USB Device info looks OK to mine and it looks like the USB stub is being created OK but my first non UVC compliant cam did the same and it just did not work.
Make sure your device is listed in http://www.ideasonboard.org/uvc/, if not you may need to buy a new cam.
For some reason I have to occasionally reboot my A500 with the webcam inserted, unplug it, start the app and then reinsert the webcam to get mine to work.
Normally though, mine works if I start the app first before plugging in.
Paul,
Hello,
Currently i'm working on a personal project to integrate my GS3 into my car display and audio. Well this was easy with the help of a MHL or Allshare Cast Dongle.
My next goal was to install a 4 wire resistive touchscreen on my car display and use it as an external touchscreen control. I bought a 7" 4 wire resistive touchscreen with a USB module build around the CYPRESS CY7C63723C chip. I hooked up the touchscreen with OTG to test if there any initial reactions from my GS3, needless to say there wasn't any (no surprise there).
After a little digging around I came up with the conclusion that I need to create a custom "Input Device Configuration Files" for my touchscreen based on the following links
http://source.android.com/tech/input/touch-devices.html
http://source.android.com/tech/input/input-device-configuration-files.html
My initial question before I start plugging away with some codes is how would I name the files, the documents states "Input device configuration files are located by USB vendor, product (and optionally version) id or by input device name." How would I find the product ID or the input device name for the touchscreen? I'm sure this can be done thru terminal or something but I am new to android development so cut me a little slack here
Also if you know of any Input device configuration files dealing with touchscreen please post it.
After digging thru dmesg I found this:
<6>[ 626.370303] hub 1-0:1.0: USB hub found
<6>[ 626.370334] hub 1-0:1.0: 1 port detected
<6>[ 626.684205] usb 1-1: new low speed USB device number 2 using msm_hsusb_host
<6>[ 626.844071] usb 1-1: New USB device found, idVendor=0eef, idProduct=0001
<6>[ 626.844132] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6>[ 626.844254] usb 1-1: Product: USB TouchController
<6>[ 626.844284] usb 1-1: Manufacturer: eGalax Inc.
Thus meaning my Input device configuration files should be named
USB_TouchController.idc or 0eef_XXXX_0001_XXXX.idc right? Anyone?
Either I have the name of the file wrong or my code is wrong I can not get any reaction from my Galaxy S3
Code:
device.internal = 0
touch.deviceType = touchScreen
touch.orientationAware = 1
cursor.mode = navigation
cursor.orientationAware = 1
touch.size.calibration = area
touch.size.scale = 28
touch.size.bias = 0
touch.size.isSummed = 0
touch.toolSize.calibration = area
touch.toolSize.areaScale = 22
touch.toolSize.areaBias = 0
touch.toolSize.linearScale = 6
touch.toolSize.linearBias = 0
touch.toolSize.isSummed = 0
touch.pressure.calibration = amplitude
touch.pressure.scale = 0.0125
touch.orientation.calibration = vector
Can anyone help me
hi,
i want to do the same (sort off)
i want to make a padphone only for gs3.
:laugh:
keep up the work:good:
Thanks, still no progress on this can anyone help?
hechen said:
Thanks, still no progress on this can anyone help?
Click to expand...
Click to collapse
Hey mate, did you ever make any headway on this? I'm desperately trying to integrate ANY android device with GPS into my V36 skylines touch screen :'(
Im working on the same thing I got a 7inch touch kit with hdmi and 12v av trigger for reversing camera
The touch screen driver bord is cy7c63723c /e galaxy
Trying to run with android pc mk809iii
Should be a good carputer if I can get it to work
Any help would be good
1st I'm a noob, so be kind. After getting the 4.0.4 update pushed from Verizon, my Motorola Bionic has disappeared from adb radar. terminal command "adb devices" returns nothing under list of devices attached, when its usb connected. (I've updated my android sdks. to latest platform tools).
I have tried each of the 3 usb settings 4.0.4 offers (Mass Storage, Media Device(MTP) and Camera (PTP), with debugging both on and off. Still no joy. I have killed and started adb server and rebooted both the macbook pro and the bionic. BTW - the original android os it started with had a "Charge Only" mode, which was the usb connection type that adb connection had previously required, but that's gone from this 4.0.4 upgrade for some reason. I have searched numerous forums and threads, but haven't found anything that seems to specifically apply to what i'm encountering. Those forums that did have posts about adb not finding connected device, mostly suggested rebooting and updated sdks. A couple suggested editing some config files, but I couldn't locate those. Any and all suggestions/solutions will be gratefully attempted. Thanks in advance for your analysis.
I'm running osx lion 10.7.5 on a MacBook Pro. I can provide phone system info if necessary. I've copied below the info I've gathered about the usb port the device is connected to from USB Prober.
Using usb prober the device appears as "Composit device: "XT875" in the bus probe. Port Info shows as: 0x1018, not captive, external device, connected, enabled. Device Descriptor shows as: Descriptor Version Number: 0x0200
Device Class: 0 (Composite)
Device Subclass: 0
Device Protocol: 0
Device MaxPacketSize: 64
Device VendorID/ProductID: 0x22B8/0x4353 (Motorola MDS)
Device Version Number: 0x0216
Number of Configurations: 1
Manufacturer String: 2 "Motorola"
Product String: 3 "XT875"
Serial Number String: 4 "0A3BAA470C01100C"
Interfaces show as: Interface #0 - Vendor-specific .............................................. "MTP"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 255 (Vendor-specific)
Interface Subclass; 255 (Vendor-specific)
Interface Protocol: 0
Endpoint 0x81 - Bulk Input
Endpoint 0x02 - Bulk Output
Endpoint 0x82 - Interrupt Input
Interface #1 - Communications-Control .............................................. "Motorola Networking Interface"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 2 (Communications-Control)
Interface Subclass; 10
Interface Protocol: 1
Endpoint 0x83 - Bulk Input
Endpoint 0x03 - Bulk Output
Endpoint 0x04 - Interrupt Output
Device Qualifier Descriptor
Descriptor Version Number: 0x0200
Device Class 0 (Composite)
Device Subclass 0
Device Protocol 0
Device MaxPacketSize: 64
Number of Configurations: 1
bReserved: 0
Other Speed Configuration Descriptor
Length (and contents): 69
Number of Interfaces: 2
Configuration Value: 1
Attributes: 0xC0 (self-powered)
MaxPower: 500 ma
Interface #0 - Vendor-specific .............................................. "MTP"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 255 (Vendor-specific)
Interface Subclass; 255 (Vendor-specific)
Interface Protocol: 0
Endpoint 0x81 - Bulk Input
Endpoint 0x02 - Bulk Output
Endpoint 0x82 - Interrupt Input
Interface #1 - Communications-Control .............................................. "Motorola Networking Interface"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 2 (Communications-Control)
Interface Subclass; 10
Interface Protocol: 1
Endpoint 0x83 - Bulk Input
Endpoint 0x03 - Bulk Output
Endpoint 0x04 - Interrupt Output
Same issue
I am trying to root a Bionic running 4.0.4 and it is having the same issue with the ADB driver. Using the same computer and a rooted razr, the ADB drivers show up as soon as it is pluged in. Any help with this matter would be a big help.
Hi, I am having issues with a Huawei modem E173u-1 on my tablet Archos 101 g9 8gb
driver not found.
Can you help me, pls?
USB_ModeSwitch log from Wed Apr 09 17:50:44 PKT 2014
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HUAWEI
product HUAWEI Mobile
serial
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/12d1.14fe
! matched. Reading config data
devList 1:
config: TargetVendor set to 12d1
config: TargetProduct set to 1506
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 12d1 -p 14fe -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x14fe
TargetVendor= 0x12d1
TargetProduct= 0x1506
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 12d1:14fe
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Waiting for device file system (2 sec.) ...
Waiting for device file system (3 sec.) ...
Waiting for device file system (4 sec.) ...
Waiting for device file system (5 sec.) ...
Waiting for device file system (6 sec.) ...
Waiting for device file system (7 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 12d1:1506 (HUAWEI: HUAWEI Mobile)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /sbin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /lib/modules/usb_wwan.ko
Error: insmod: cannot insert '/lib/modules/usb_wwan.ko': Invalid module format (-1): Exec
format error
Loading main driver module "option"
Error: insmod: cannot insert '/lib/modules/option.ko': Invalid module format (-1): Exec
format error
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed
All done, exiting
please answer!!!
i'm solved the problem by replacing the nucleus
Hello guys,
I am trying to bring back to life a dead Vivo 1901 (V15) phone using SP Flash Tools v5.2036. The Firmware I am using comes in a file named, "Vivo_Y15_PD1901BF_MT6765_EX_A_1.12.4_11062019_(by_vivofirmware.com)",
which also provides MT6765 scatter file.
The auth file, scatter file and DA file that I am using for flashing is attached with this post. Upon selecting these files and flashing ( first tried with download only, then using format all + download, but results are same), I the following messages appear in the output of the tool.
Code:
$ sudo sh flash_tool.sh
[sudo] password for sarkar4540:
sysname:Linux
nodename:sarkar4540-X556UQK
release:5.4.0-49-generic
version:#53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020
machine:x86_64
domainame:(none)
cur_kernel_version = 5.4.0
QObject::moveToThread: Cannot move objects with a parent
support_dl_cert_to_storage: 0
Application asked to unregister timer 0xc00001b which is not registered in this thread. Fix application.
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
add@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/module/cdc_acm
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 0003
device pid = 0003
com portName is: /dev/ttyACM0
Total wait time = -1601887002.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Failed to Connect DA: STATUS_SHUTDOWN_CMD_EXCEPTION(-1073414142)
Disconnect!
BROM Exception! ( ERROR : STATUS_SHUTDOWN_CMD_EXCEPTION (-1073414142) , MSP ERROE CODE : 0x00.
[HINT]:
)((ConnectDA,../../../flashtool/Conn/Connection.cpp,149))
Following are the outputs of various commands in the system I am using.
Code:
$ uname -a
Linux sarkar4540-X556UQK 5.4.0-49-generic #53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Code:
$ dmesg
.
.
.
[ 324.046688] usb 1-2: new high-speed USB device number 5 using xhci_hcd
[ 324.195603] usb 1-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 324.195605] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 324.248243] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
[ 324.249509] usbcore: registered new interface driver cdc_acm
[ 324.249510] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 324.275093] usbcore: registered new interface driver usbserial_generic
[ 324.275106] usbserial: USB Serial support registered for generic
[ 324.300238] usbcore: registered new interface driver option
[ 324.300261] usbserial: USB Serial support registered for GSM modem (1-port)
I request you guys to please show me where to head. I shall always be grateful to you if you can help me out of this misery.
Regards,
A. Sarkar