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 - Lars

Pages: 1 ... 75 76 [77] 78 79 ... 82
1141
Applications / Re: cups and usb printers
« on: December 08, 2016, 05:45:25 pm »
rebuilt libusb10.dll is at http://smedley.id.au/tmp/libusb-20161207.zip

This is built against the latest usbcalls toolkit from http://trac.netlabs.org/usb

Note I haven't tested this, I have no time today.

Cheers,

Paul

Hi Paul,

now that we know that this Version of libusb10.dll works just fine, are you also going to put it in the AN rpm repo ?
I just don't want that piece of SW getting lost ...

Lars

1142
Programming / Re: os4: KEE update notification
« on: December 07, 2016, 08:24:02 pm »

If the kernel does not need to be updated and all problems can be solved through PSD, why the same IBM released the updated kernels, with each new fixpack and each new version of the OS? Moreover, remember amount of test kernels on testcase? Probably architectural problems can not be solved with the external driver.

Remember that Warp V4 and later w kernels didn't use a PSD.

Then you will be delighted to hear that since about 14.104 or so the W4 kernels can also load a PSD !
You can try out (and switch to native FPU exception handling):

http://hobbes.nmsu.edu/download/pub/os2/system/drivers/misc/os2pcat3.wpi

It's a PSD that I have written to fix some prob with the W4 kernel and to switch over using native FPU exception reporting (instead of going via IRQ13 on the external interrupt controller). It was meant as a personal learning excercise.
It also comes with full source code (well there is not much ...).

Lars

1143
Programming / Re: os4: KEE update notification
« on: December 07, 2016, 08:03:17 am »
Good question why IBM did not follow. I guess they broke their own concept.
The kernel should be as lean as possible.
All platform specific stuff should be in the PSD. It already contains the specific code for "end of interrupt", setting interrupt status and in-service registers, sending inter-processor interrupts and a few more. Therefore it is the ideal place to put such code and as I said it has already been done.

1144
Programming / Re: os4: KEE update notification
« on: December 07, 2016, 06:27:43 am »
1) what happens if you want to install eCS/AN inside VirtualBox where eCS/AN is the host system ?

2) ACPI as such has no relation to it, yes. But a PSD is a good place to put additional platform functionality to leave the kernel unchanged.
There is even a function PSD_APP_COMM in the PSD that could exactly meet this purpose (in was originally intended to be used for Ring-3 apps but that was never/is no more implemented). By the way: Pasha had originally implemented those functions in ACPI.PSD.

Lars

1145
Applications / Re: cups and usb printers
« on: December 06, 2016, 06:54:53 pm »
Some ordinals of new functions overlay ordinals of old functions (most notably ordinal 4 that now offers a function that did not exist before).
I can only say that I had to relink cameraderie with an updated import libary for usbcalls.dll.

To make it more clear, there the library from: http://en.ecomstation.ru/projects/usbtools/download/usbcalls-20060807.zip
Code: [Select]
Library:                        usbcalls
Description:                    USB Interface DLL - (c) Froloff&Son 2006

Module type:                    Dynamic link library
                                Per-process initialization
                                Per-process termination
Number of memory pages:         00000002 (2)
Initial CS:EIP:                 object 1 offset 00000000
Initial SS:ESP:                 object 0 offset 00000000
Automatic data object:          2
And "exehdr usbcalls.dll | find " 4"" results in:
Code: [Select]
   4    1  000011e6  UsbIsoStart        exported, shared data
For the latest usbcalls.dll (in this case my build, but David's is exactly the same):
Code: [Select]
Library:                        USBCALLS
Description:                    @#Lars Erdmann:10.211#@##1## 14 Nov 2016 22:30:23     Laptop    ::::::@@USBCALLS DLL for OS/2 (c) 2015 Lars Erdmann

Module type:                    Dynamic link library
                                Per-process initialization
                                Per-process termination
                                NO internal fixups in executable image
Number of memory pages:         00000008 (8)
Initial CS:EIP:                 object 1 offset 00003876
Initial SS:ESP:                 object 0 offset 00000000
Automatic data object:          2
And "exehdr usbcalls.dll | find " 4"" results in:
Code: [Select]
   4    1  0000101e  UsbQueryDeviceInfo exported
where "UsbQueryDeviceInfo" is a function that is completely new and never existed in the old DLL.

To crosscheck with Wim's DLL:
Code: [Select]
Library:                        USBCALLS
Description:                    @#W.M.Brul:14.20150630#@USBCALLS

Module type:                    Dynamic link library
                                Per-process initialization
                                Per-process termination
Number of memory pages:         0000000c (12)
Initial CS:EIP:                 object 1 offset 00000000
Initial SS:ESP:                 object 0 offset 00000000
Automatic data object:          2
and "exehdr.exe usbcalls.dll | find " 4" results in:
Code: [Select]
   4    1  000025e2  UsbQueryDeviceInfo exported
I can say that David's, Wim's and my version of USBCALLS.DLL are exactly the same from a binary interface point of view (and also otherwise).

In short: sticking to one and the same ordinal of "4" for two different functions broke the binary compatibility between the DLL from Froloff (2006) and the new version.


Lars



1146
Programming / Re: os4: KEE update notification
« on: December 06, 2016, 01:33:17 pm »
So you are looking for a community that splits up even more than it is today ?
That will be the moment in time when I will finally pull the plug on OS/2.

If you cannot install a standard eCS or AN Installation inside a virtual machine then that's it for me.
That's not frustration. That's common sense.

Ok, here is something constructive: don't put these routines in the kernel, put it in ACPI.PSD and ACPI.SYS (the ACPI driver from the OS4 team) respectively.
Then have the 2 parties agree on a common Interface.

1147
Programming / Re: os4: KEE update notification
« on: December 05, 2016, 10:28:41 pm »
No it's not useful as it leaves everybody outside that wants to continue to use the original kernel.

1148
Applications / Re: cups and usb printers
« on: December 05, 2016, 10:23:23 pm »
Hi All

Sorry to have brought the usbcalls.dll problem into the light. However, I suspect other changes within the Arca Noae USB driver package will need to be investigated as even when using the old usbcalls.dll/usbresmg.sys printing fails with "Unable to send data to printer".

Regards

Pete

What you say makes no sense to me. The USBCALLS.DLL was changed for exactly the reason to fix transfer problems (at least that's what I remember). Unless we cannot get the new USBCALLS.DLL/USBRESMG.SYS to cooperate with TAME / libusb.dll / "you name it" we will never know if all problems will not vanish into thin air.

1149
Applications / Re: cups and usb printers
« on: December 05, 2016, 04:36:57 pm »
That explains why TAME no longer works with our USB scanners unless we use the old USBCALLS.DLL.

Could you post the updated CAMERA.EXE because I was wondering why I now had to take the card out of my camera to download files.

Also could I ask for those that changed USBCALLS.DLL to do something about updating all the programs that rely on it to work or at least provide something that will allow those programs to work.

1) about TAME: let's hope it also uses libusb.dll in which case it will be fixed when libusb.dll is fixed.
2) about camera.exe: if I find the time, yes. The prob is it is not my package and contains some files with Copyright David Azariewicz (I mean the source package).
3) about the rest: You must be kidding. I propose to ask for a specific application and then let's find the guy who wrote it originally. For my "OS/2 HWManager WPS replacement class" I can say it uses the up to date USBCALLS.DLL ...


Lars


1150
Applications / Re: cups and usb printers
« on: December 05, 2016, 04:31:39 pm »
Hi Lars and Pete,

The USBCALLS.DLL interface has changed (I cannot remember why, I didn't change it, I just "followed the crowd" with my USB driver set). Whatever EXE or DLL uses it (presumably libusb.dll) will need to be relinked against an updated import library for USBCALLS.DLL. I have the feeling that this has not yet happened.
The interface has changed massively and depending on what functions were used, the calling application/dll might also need to be modified (relinking might not be sufficient in this case).
You will be able to see the changes by running "exehdr /V usbcalls.dll" (exehdr.exe comes with the OS/2 toolkit) and comparing the "Exports" section of the 2 DLLs.
Maybe Paul Smedley is reading this ...

By the way: the same holds true for some apps making use of USBCALLS.DLL. After rebuilding "CAMERA.EXE" (show files from smartphones employing PTP protocol, from Rich Walsh) with an updated import library, it now also works.

So sounds like I need to rebuild libusb against the latest usbcalls? Where do I get the latest usbcalls.lib? From the Arca Noae driver package?

Cheers,

Paul

Hi Paul. David Azariewicz should be able to provide it (I think in the USB toolkit which I think is part of the AN 11.14 USB Driver package). Alternatively it's very simple to create an Import lib on your own if you have an IBM Compiler (VAC):
run "implib.exe usbcalls.dll" on the new USBCALLS.DLL and it will create an appropriate Import library usbcalls.lib (or look "implib -?" for help).

Lars

1151
Applications / Re: cups and usb printers
« on: December 05, 2016, 06:56:02 am »
The USBCALLS.DLL interface has changed (I cannot remember why, I didn't change it, I just "followed the crowd" with my USB driver set). Whatever EXE or DLL uses it (presumably libusb.dll) will need to be relinked against an updated import library for USBCALLS.DLL. I have the feeling that this has not yet happened.
The interface has changed massively and depending on what functions were used, the calling application/dll might also need to be modified (relinking might not be sufficient in this case).
You will be able to see the changes by running "exehdr /V usbcalls.dll" (exehdr.exe comes with the OS/2 toolkit) and comparing the "Exports" section of the 2 DLLs.
Maybe Paul Smedley is reading this ...

By the way: the same holds true for some apps making use of USBCALLS.DLL. After rebuilding "CAMERA.EXE" (show files from smartphones employing PTP protocol, from Rich Walsh) with an updated import library, it now also works.

Lars

1152
Events / Re: Any questions for Warpstock 2016 ??
« on: October 26, 2016, 10:24:30 am »
... and none of the additional SW needed is likely to be available under OS/2.

1153
Events / Re: Any questions for Warpstock 2016 ??
« on: October 23, 2016, 01:02:26 am »
@Lars: does the USBAUDIO.SYS support USB microphones? My USB webcam has one built in - would be a step closer to having some kind of streaming video/sound capability using USB devices.

Let me put it this way: it should already. If it does not for your case then there is room for improvement. It depends on the sample rate. USB devices only have have a reduced number of sample rates they support. Normally they are smart enough to support 44.1 kHz (CD-ROM sample rate) and/or 48 kHz (the sample rate for professional equipment). Everything else would need to be supported by sample rate conversion in SW.

1154
Events / Re: Any questions for Warpstock 2016 ??
« on: October 22, 2016, 12:47:49 am »
Is there any interest in updating USBAUDIO.SYS ? Right now I updated volume control so that master volume and application specific volume setting will both work. It's enough to have volume control (via master volume control) when playing audio CDs or playing system sound (via master volume control and application volume control via the specific system volume setting).
But there still is enough other stuff to do.

1155
Applications / Re: anpm question problem DUMPPROC / PROCDUMP
« on: September 30, 2016, 01:34:29 pm »
The easiest is to delete or backup the "usr" and "etc" subdirectories.
I seem to remember that if you then run ANPM it will ask you if you want to download and install the YUM/RPM base package. Answer with yes and your "usr" and "etc" subdirectories will be properly recreated.
Once that is done, rerun ANPM and follow all of the instructions in the link that Doug has already posted and start updating all the packages that show up as outdated (there will be quite a lot).
The nice thing is that once you have all that done, you will not have any problems with ANPM in the future.

Your problem is due to some hosed python installation. I had the very same problem and I fixed it the way I stated above.

Pages: 1 ... 75 76 [77] 78 79 ... 82