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] 2 3 ... 12
1
Multimedia / Re: Use of webcam
« on: Today at 12:53:02 pm »
One additional note:
Wim can confirm or not but I would believe that uvcview.exe/uvcscope.exe uses USBCALLS/USBRESMG to do its thing.
Therefore,the problem could also be located in those components.
Taken the fact that Rich reported that USB audio works ok with the AN 32-bit stack, I consider these 2 a likely source of the problem.

Yes, uvcview.exe/uvcscope.exe are using USBCALLS/USBRESMG to do their thing. The only difference is that uvcscope.exe has a microscope selection parameter.

I have a Lenovo Thinkpad T540p with two bootable ArcaOS volumes. One has USB 11.17, and runs websee UVCView.exe perfectly. The second has USB 12.05 and  UVCView terminates with an error: [0000FF14] Obtain thread error!

This confirms that the problem is somewhere within the ArcaNoae 12.x USB driver set.

2
Multimedia / Re: Use of webcam
« on: May 24, 2020, 09:55:34 pm »
The program gets this FF14 error when it tries to allocate resources for isochronous transfers.
Like Lars already said: isochronous transfers are not yet supported by the ArcaOS 12.x USB drivers.
Try and use the ArcaOS 11.17 drivers instead. Or use the latest Lars Erdmann USB driver set.

Ok, thanks i'll give it a try

Did you try and use your webcam with the ArcaOS 11.17 drivers? Did it work with these?
Did you try and use your webcam with the Lars Erdmann 10.234 drivers? Did it work with these? 

Hi    Wim,

According Andy's update,  isochronous is supported.
How to make it work please using  AN latest build ?
Thanks

Regards
Rémy

When the answers to my 4 questions above are yes then it is time to use ArcaNoae's Mantis to report the problem.   

3
Multimedia / Re: Use of webcam
« on: May 20, 2020, 05:24:20 pm »
The program gets this FF14 error when it tries to allocate resources for isochronous transfers.
Like Lars already said: isochronous transfers are not yet supported by the ArcaOS 12.x USB drivers.
Try and use the ArcaOS 11.17 drivers instead. Or use the latest Lars Erdmann USB driver set.

4
Multimedia / Re: Use of webcam
« on: May 20, 2020, 02:57:49 pm »
Hi Remy,

Go to https://home.hccnet.nl/w.m.brul/usbvideo/index.html and select your webcam, or equivalent, then select the necessary program.

Not sure about sound as I don't have it on my main computer.

Hi Ivan,

I already was there but nothing works.
My system is SMP  -   USBEHCD.SYS  (ArcaOS latest level)
The  webcam is a 720p 30fps - defined as USBECD.SYS /D:046D:0825:0010

Regards
Rémy

Hi Remy,

The URL given by Ivan points to my "USB Webcam Tests" web page, which is beta test software, not to be used anymore.
So remove the usbecd.sys line you added in config.sys for your webcam and use my "UVC Microscope Viewer" instead.

Regards, Wim.


5
Hardware / Re: Report: ArcaOS on Panasonic Toughbook CF-M34 MK1
« on: May 14, 2020, 07:28:28 pm »
Everything working now.. but this notebook also comes with touch screen ... next task will be to get that working, too.
Have a look at my "Digitizer Support" web page. Support is a 3 step process: Access COM device, Develop REXX script, Send Mouse events.
It seems to me that your Panasonic Toughbook touch screen has been connected to com port 2 using a gunze AHL-71N Touch Panel Controller.
Try and run "comraw 2 9600" to get raw input data at 9600 baud into the 9600.raw file. Touch the screen for actual input. Use Ctrl+C to stop.

6
Unfortunately I wasn't able to get any further than this despite following Lars' advice on installing his driver kit and doing my best to make sure config.sys was up to date. I'm currently backing up my system and once that is complete I may do a fresh reinstall and try following the steps on a clean slate - I'm sincerely hoping that may yield better results than what we've been facing so far.

I have also once again attached a copy of my config file for anyone who is interested.
I looked into your config.txt file and after the "REM [END USB section" line it contains duplicate "BASEDEV=USBD.SYS" etc. statements. Take your time to scrutinize.

7
I have prepared Yoga12-20200422.zip containing two rexx scripts for you to try out:

1. Run ofinger.cmd in a command window to obtain and show raw finger events. Touch the screen with your finger to see if that works.

2. Run ostylus.cmd in a command window to obtain and show raw stylus events. Touch the screen with your stylus to see if that works.

8
Quote
I apologize for not attaching this beforehand, I've uploaded it with this post. From inspecting the file myself I see it is putting out a picture, the UVCVIEW program itself just doesn't display it.
No need to apologize. I am glad it is now available so I may improve my mjpg decoder once I find the time and feel like it.

Quote
And then loops on this:
Code: [Select]
stylus configuration
 stylus configuration
[0000001D]
The program is retrying because usbecd.sys reports an i/o error. Please report which USB driver set you are using. Try and use the Lars Erdmann USB driver set.

9
Quote
Perhaps the mjpg decoding in uvcview.exe is not good enough. Click on "Testshot" to capture raw input data. Captured input data is written to the UVCVIEW.RAW file for later inspection. This could be of help in situations where the WebCam Viewer is working but the displayed picture stays black. Post your results. Try uvcview /u to watch yuyv video.

yuyv appears to fix the camera issue entirely, I'm happy to say the camera is now working perfectly. It's a shame I didn't try the /u flag beforehand as it's clearly there in the documentation

Nice. However, I really would like you to attach UVCVIEW.RAW created from the procedure outlined above (using uvcview without parameter) for me to inspect.

10
Quote
Rem out the "RUN=C:\OS2\BOOT\YOGA12.EXE" line in config.sys and reboot. In a command window use "C:\OS2\BOOT\YOGA12.EXE /v" to get debug ouput on stdout. Try and use your pen to see if it is working. Post your results.

The results are as follows:
Code: [Select]
opening finger
[00000003]
stopped.

Still no functionality I'm afraid.

Strange. Seems to me that in config.sys the $FINGER$ device driver statement is missing or still not correct. Please check again.


11
Quote
No such luck I'm afraid. I'm still not getting any response from the pen or from normal touch (I even ran an Ubuntu live disk to verify it's not a hardware issue, it's definitely operational).
Rem out the "RUN=C:\OS2\BOOT\YOGA12.EXE" line in config.sys and reboot. In a command window use "C:\OS2\BOOT\YOGA12.EXE /v" to get debug ouput on stdout. Try and use your pen to see if it is working. Post your results.

Quote
I'm glad to say I'm no longer getting any error messages, the webcam appears to function with the recording light turning on but I am still met with no video.
Perhaps the mjpg decoding in uvcview.exe is not good enough. Click on "Testshot" to capture raw input data. Captured input data is written to the UVCVIEW.RAW file for later inspection. This could be of help in situations where the WebCam Viewer is working but the displayed picture stays black. Post your results. Try uvcview /u to watch yuyv video.


12
As Lars wrote earlier the proper lines for pen and touch are:

Code: [Select]
DEVICE=C:\OS2\BOOT\USBECD.SYS /D:04F3:0254:1112 /N:$FINGER$ /S /V
DEVICE=C:\OS2\BOOT\USBECD.SYS /D:056A:00EC:0131 /N:$STYLUS$ /S /V

With these lines I expect the pen to work. I expect touch not to work because the program expects a different device.

The webcam program works with usbcalls.dll and usbresmg.sys and usbecd.sys should not be used for this device.

13
Hi Hakeem,
 
Quote
>Whilst trying to get the touch screen to function, I've been getting an error during boot stating that amouse.sys is not installed and therefore the line in CONFIG.SYS has been ignored. I am currently using the latest version of the Arca Noae driver. The hardware manager also tells me the driver has been installed however and appears to refer to amouse.sys for AUX_0 PS/2 and MOUSE_0 IBM
It seems to me that you added amouse.sys to your config.sys whereas you needed to modify the existing amouse.sys device driver statement.
Quote

>When trying to run UVCVIEW, I am getting the 0000FF14 Obtain Thread error. The webcam light turns on but I receive no picture.
The webcam uses isochronous transfers that are not yet supported by the ArcaOS 12.x USB drivers. Try and use the 11.17 drivers instead. Or use the latest Lars Erdmann USB driver set.

Wim

14
Programming / Re: Observing if a program uses vio calls
« on: March 01, 2020, 12:50:10 pm »
In the Borland C header, both parameters row and column are PUSHORT. So we have three different meanings. Anyway, the original 2 times PUSHORT definition works. I assume the are problems if values higher than 65536.

Meanwhile, the new mechanism for popping up VIO windows works! But I have found a program TED.EXE (very old minimalistic editor for editing config.sys on 3,5 inches discs) which is not recognized: It is a pure VIO program and when starting, it draws a menu on the bottom of the VIO window and then it awaits input on the topleft cursorposition (0,0). So my program thinks that there was no input. Are there other useful VioGet... calls where I can additionally query and compare other values than the cursor position? Perhaps comparing the whole screen buffer? (Which is not as big today as it was 20 years before...) I could write user settings for these additional queries.

Use VioReadCharStr to compare the whole screen buffer (I think 8192 chars max)  or use VioReadCellStr to compare the whole screen buffer including colors.

15
Programming / Re: Observing if a program uses vio calls
« on: March 01, 2020, 11:35:37 am »
From the IBM Toolkit 4.5 Control Program Guide and Reference
Quote
#define INCL_VIO
#include <os2.h>

PULONG     Row;        /*  Row return data. */
PUSHORT    Column;     /*  Column return data. */
HVIO       VioHandle;  /*  Presentation-space handle. */
APIRET     rc;         /*  Return code. */

rc = VioGetCurPos(Row, Column, VioHandle);

Yes, that info is there, but when you look into BSESUB.H you will see that only the 16 bit version has been defined in there.     

Pages: [1] 2 3 ... 12