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 ... 8 9 [10] 11 12 ... 16
136
Hardware / UVC Webcam Support for OS/2 in an SMP environment
« on: September 28, 2016, 08:19:11 pm »
Stichting Voice International has donated me a refurbished DELL LATITUDE E6500 laptop which enables me to develop and test my OS/2 software in an SMP environment.

I have been busy the last couple of months trying to solve the webcam timeout issue when running on an SMP system. I had to make a small change in the usbehcd.sys device driver. I modified Lars' latest source code i.e. the source code of his 10.207 USBEHCD.SYS device driver as he maintains it in the Netlabs USB repository. Moreover I had to modify my webcam programs to avoid a trap in usbehcd.sys upon exiting these. Now I am able to run the laptop internal webcam as well as the Logitech C250 webcam while running eComStation 2.0 with 2 CPU's active and I did not encounter any timeout nor traps anymore.

Several German people as to Webcam and Mehrkernprozessoren - Wim Bruls Treiber) have already been busy testing with good results too. Therefore I have updated my UVC Webcam Support web page with WebSee11.zip and WebSee11s.zip and I have put these now open source products on hobbes too. I have attached uvcsmp1.zip containing my 13.20160904 USBEHCD.SYS device driver with installation instructions  for any volunteers to try and test on their systems.

137
Programming / Re: The OS/2 API Project at EDM/2
« on: July 03, 2016, 10:44:22 pm »
Wim, can you let me know how to inspect the .LIB files?  Any tools? I really do now know anything about those files. How do you see it's internals?

Hi Martin,

With the IBM Library Manager you can a.o. create a cross-reference listing file from a library file.

A cross-reference listing file contains two lists. The first is an alphabetic listing of all public symbols in the library. The name of the module, the symbol name refers to, comes after that symbol name.

The second list is an alphabetic list of the modules in the library. Under each module name is an alphabetic listing of the public symbols the module refers to.

Code: [Select]
lib.exe os2386.lib,os2386.lst;

You may find lib.exe in the ddk. It is not present in os2tk45. An alternative is the Microsoft Library Manager contained in c7os2.zip on hobbes.

Regards

138
Programming / Re: The OS/2 API Project at EDM/2
« on: July 03, 2016, 12:07:32 pm »
Quote
Issue 2) The second issue is that there functions on CP1.INF that are also on the legacy (prcp.INF), but the CP1 function is not specified correctly. Which it also means that those CP1 functions have not been implemented, and only the legacy documentation should apply. right?
Yes. CP1.INF contains tentative documentation of 32 bit functions intended to replace those16 bit legacy functions.
Quote
If you call VIOSCROLLUP but sending ULONG parameters (like CP1 says) will it not work?
That will not work.
Quote
Is there a way to confirm that CP1's VIOSCROLLUP (the new one) does not exists at all? Or what I posted is enough evidence? I'm not sure about it.
For me that is enough evidence. I also inspected os2386.lib and those tentative functions are absent  whereas those legacy functions are present.
Quote
If it does not work, that would mean to me that I also need to document the legacy functions, and also put some warning on it that even that there is a "non-legacy function" you still need to use the legacy one because the newer one does not work. Does it makes sense?
Only the 16 bit legacy functions need to be documented. I would omit that tentative documentation completely because it would only lead to confusion.

139
Programming / Re: The OS/2 API Project at EDM/2
« on: June 24, 2016, 05:47:26 pm »
Hi Martin,

When I look into \TOOLKIT\OS2TK45\H\BSESUB.H then I see that e.g. VioScrollUp is in reality supported by VIO16SCROLLUP and that the argument list described in cp1.inf is in fact incorrect since the argument list described in prcp.inf applies. I checked several other Kbd, Mou and Vio functions and these all appear to be supported the same way i.e. their argument list in cp1.inf is incorrect. Consequently all Kbd, Mou and Vio functions need to be marked as ** Not implemented *.

Regards


140
Programming / Re: The OS/2 API Project at EDM/2
« on: June 24, 2016, 11:57:05 am »
I want to check the headers of the OS/2 Toolkit 4.5 and see if I can understand those and try to make a quick list (on other page of the wiki) on which functions may be available on the CP1 documentation, but missing on the headers.

Since I see that all the headers on toolkit are on /H directory and I only want to focus on the CPI components for the moment, which are the .H files that I should be looking at? Does this question makes sense ?

The main include is OS2.H which leads you to BSE.H which in turn leads you to BSEDOS.H (for Dos functions) and BSESUB.H (for Kbd, Mou and Vio functions).

141
Programming / Re: The OS/2 API Project at EDM/2
« on: June 23, 2016, 12:28:25 am »
Quote
Hi Wim. I'm sorry if I'm slow on this subject and if it is necessary to repeat something to me. I'm not sure if I'm asking the right thing.

Well, Martin, I am not fast either and it is hard to understand when the official ibm documentation is not in line with the toolkit header and library files.

Quote
What about "VioScrollDown"?  From what I understand "VioScrollDown" is the one that should be used and "VioScrollDn" is legacy. I guess they both do a similar thing. So it will mean (in my limited knowledge) that somebody doing some new development with CPI should avoid using "VioScrollDn" and use "VioScrollDow" instead. Am I right?

Although VioScrollDown appears in cp1.inf it is not present in the header and library files. The developer cannot use it. The developer may only use VioScrollDn since that is the one that is present in the header and library files. I am not sure whether or not the term "legacy" applies. One could argue that a contemporary programmer would produce Presentation Manager type programs only. In that case It would be regarded as "legacy".

Quote
On the latest cp1.inf I can only find "VioScrollDown" and not "VioScrollDn". I can only find "VioScrollDn" as legacy on prcp.inf.

Me too. Apparently 32 bit versions of the 16 bit legacy functions have been documented. Unfortunately these are not supported by the header and library files. Only the 16 bit legacy functions are in there. Therefore these are the only ones available to an application programmer.

Quote
For the moment I ignored the functions with "16" on it because someone suggest me that developers should use the function without it.  Like on "Dos32QueryCtryInfo" and "DosQueryCtryInfo" the developer should use (normally) "DosQueryCtryInfo" and for some exception sometimes they might call the 16 one. This is what I understood in short and in my limited knowledge of programming.

Right you are. You understand well. I only referred to VioScrollDn and Vio16ScrollDn to prove that in fact VioScrollDn is a 16 bit function.

Quote
But I'm always open for other suggestions. I think that it is important to document everything, and if something that is being documented is wrong and/or old, suggest on that same documentation what should be used instead.

Yes. Let's keep on trying when time permits.


142
Programming / Re: The OS/2 API Project at EDM/2
« on: June 22, 2016, 06:48:44 pm »
Hi Martin,

When I look into \TOOLKIT\OS2TK45\H\BSESUB.H then I see that e.g. VioScrollDn is in reality supported by VIO16SCROLLDN and that the argument list described in cp1.inf is in fact incorrect since the argument list described in prcp.inf applies. I checked several other Kbd, Mou and Vio functions and these all appear to be supported the same way i.e. their argument list in cp1.inf is incorrect. It seems to me that all Kbd, Mou and Vio functions must be categorized as 16 bit legacy.

Regards, Wim.

143
Programming / Re: Settings Notebook tutorial
« on: May 15, 2016, 04:43:14 pm »
Seen on Samuel Audet's Programming Page:
Quote
Notebook dialogs
So, what would you like to do with Notebook dialogs?

■  Easily load and manage pages
■  Making Help Manager useable

144
Hi Martin,

Quote
I'm still looking for someone to compile SCREEN01.SYS, TIMER0.SYS and TESTCFG.SYS from the IBM DDK. No matter if it is backlevel, it is just for the experiment.

I don't have the source code for these drivers, but writing my own testcfg.sys was possible.
I have attached a minimal replacement for testcfg.sys with free source code. It only supports:
Generic IOCtl Category 80h, Function 40h - Obtain a Copy of BIOS/Adapter Memory.

Regards,

Wim

145
Quote
Is it the same file (isapnp.sys and pnp.sys) that just need to be renamed?

Both isapnp.snp and pnp.sys need to be replaced by the very same pnp593ec.sys file.

The Hardware Manager under "ISA_Bus" will no longer show the "PnP Isolation/Detection Driver".
See the PnP Basics article on EDM/2 for more information about the PnP i/o ports.

146
Hi Martin,

I have attached a stub replacement for isapnp.snp and pnp.sys with free source code.

Code: [Select]
copy pnp593ec.sys c:\os2\boot\isapnp.snp
copy pnp593ec.sys c:\os2\boot\pnp.sys

Regards.

147
Quote
Just one thing to confirm, are the .rom of your files the fonts?

Yes . When you run vio593.cmd then it invokes vio593.exe which in turn will read the six cp*.rom files and write the resultant vio593ec.dcp file. The content of the cp*.rom files is used unchanged and the added header data defines these as the 8*8, 8*14, 9*14, 8*16, 9*16 fonts for code pages 437 and 850.

cp437cga.rom and cp850cga.rom contain 8*8 rom fonts (like from a cga adapter).
cp437ega.rom and cp850ega.rom contain 8*14 rom fonts (like from a ega adapter).
cp437vga.rom and cp850vga.rom contain 8*16 rom fonts (like from a vga adapter).

148
Hi Martin,

I have attached a replacement for viotbl.dcp with free source code. Supports code pages 437 and 850.
I used the Display Font Editer for OS/2 v0.02 (pmfoed002a.zip on hobbes) to edit the fonts.

Regards.

149
I will be also happy to know which of the files of this list can be easy replaced. Just to continue this experiment.

Hi Martin,

I have attached a replacement for country.sys with free source code. Supports Ecuador (country code 593 with code pages 850 and 437), Netherlands (country code 31 with code pages 850 and 437) and United States (country code 1 with code pages 850 and 437).

Regards.

150
Setup & Installation / Re: Thinkpad X250 & eCS
« on: March 01, 2016, 06:14:17 pm »
Hi Mike,

Quote
I have now tested both programs uvcscope & uvcview with the latest USB drivers from Lars (v10.202) and from AN (v11.13). In both environments both programs starts but  the video freezes after some seconds with the already posted error message. I couldn't repeat the three minutes run time for uvcview.

Thank you for your testing and reporting. It clearly shows that these webcam programs cannot run reliably in a multicore environment. Other people have run into the same problem with their webcams in such an environment. Unfortunately I cannot recreate that problem because I have only single cpu hardware to test with.

Quote
I guess I shall try a clean environment, but that is a little bit tricky for the X250 because I have to clone the OS using DFSee. If I have time I will give it another try and will stop for now testing the camera.

Don't spend more time on it since I really don't know how to solve the problem.

Best regards,
Wim.



Pages: 1 ... 8 9 [10] 11 12 ... 16