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 ... 9 10 [11] 12 13 ... 51
151
Programming / Re: Creating a RPM package for PMDLL
« on: September 29, 2020, 06:36:30 pm »
Try:

Code: [Select]
%wps_object_create_begin
PMDLL_EXE:WPProgram|PMDLL|<WP_DESKTOP>|EXENAME=((%{_bindir}/PMDLL.EXE));ASSOCTYPE=Executable,Dynamic Link Library;ASSOCFILTER=*.EXE,*.DLL|R
%wps_object_create_end


152
Programming / Re: Creating a RPM package for PMDLL
« on: September 29, 2020, 09:02:06 am »
Just a wild guess (I have no experience writing RPM spec files):
use %% instead of % for refering to _bindir.

An OS/2 commandline requires escaping the % character by specifying two % characters.
As a test you can run:
rpm --eval %%_bindir
try instead:
rpm --eval %_bindir
and you will realize that the former works while the latter does not.

However I don't know if installing an RPM will lead to invocation of an OS/2 commandline with the arguments passed in as written in the RPM spec file.


Something else I don't understand (but maybe it is intended) is that if you run:
rpm --eval %%_bindir (or rpm --eval %%{_bindir})
is that this is returned:
/@unixroot/usr/bin

I hope that /@unixroot is silently resolved by using the UNIXROOT environment variable (which needs to be set on your system).


153
Programming / Re: Creating a RPM package for PMDLL
« on: September 27, 2020, 05:37:50 pm »
These files always go into the very same directory as the Executable.

154
Programming / Re: REXX and double quoted INPUT parameter strings
« on: September 14, 2020, 07:27:38 am »
Why don't you just use strip (with " leading and trailing) after separating the arguments?

155
Setup & Installation / Re: how to tell DIR which date to show?
« on: September 13, 2020, 05:17:01 pm »
Can't you just use the 4OS/2 commandline ? That supports everything you want right out of the box.

156
Setup & Installation / Re: how to tell DIR which date to show?
« on: September 13, 2020, 09:03:17 am »
Mostly whether JFS actually supported creation time, which many *nix filesystems don't and treat c differently. The IFS itself can only read whatever metadata the file system saves so the ext2 IFS for example may not be able to return the creation time as ext2's support for it is questionable.
The IFS is the filesystem plus the functionality that OS/2 expects from an IFS.
It is the IFS job to properly return a creation date if the OS asks for it no matter where it gets that from. The IFS has a standardized interface, if a core filesystem does not support something (on porting a filesystem,for example) then the IFS will have to fill the gap.
The only problem is that sometimes things are not unambiguously defined: if you open a file for the very first time but it has not yet been saved to disk, is it then already created or not?

157
Setup & Installation / Re: how to tell DIR which date to show?
« on: September 12, 2020, 08:05:17 pm »
Testing, it seems that JFS uses (*nix) c as changed rather then created. Created a file with touch and did some tests,
Code: [Select]
K:\tmp>stat test
  File: test
  Size: 0               Blocks: 0          IO Block: 49152  regular empty file
Device: 564bh/22091d    Inode: 14461902377750889908  Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2020-09-12 08:24:44.000000000 -0700
Modify: 2020-09-12 08:24:44.000000000 -0700
Change: 2020-09-12 08:24:44.000000000 -0700
 Birth: 2020-09-12 08:24:44.000000000 -0700

K:\tmp>echo test >> test

K:\tmp>stat test
  File: test
  Size: 6               Blocks: 8          IO Block: 49152  regular file
Device: 564bh/22091d    Inode: 14461902377750889908  Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2020-09-12 08:24:44.000000000 -0700
Modify: 2020-09-12 08:27:52.000000000 -0700
Change: 2020-09-12 08:27:52.000000000 -0700
 Birth: 2020-09-12 08:24:44.000000000 -0700

K:\tmp>cat test
test

K:\tmp>stat test
  File: test
  Size: 6               Blocks: 8          IO Block: 49152  regular file
Device: 564bh/22091d    Inode: 14461902377750889908  Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2020-09-12 08:30:16.000000000 -0700
Modify: 2020-09-12 08:27:52.000000000 -0700
Change: 2020-09-12 08:27:52.000000000 -0700
 Birth: 2020-09-12 08:24:44.000000000 -0700

K:\tmp>chmod +x test

K:\tmp>stat test
  File: test
  Size: 6               Blocks: 8          IO Block: 49152  regular file
Device: 564bh/22091d    Inode: 14461902377750889908  Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2020-09-12 08:30:16.000000000 -0700
Modify: 2020-09-12 08:27:52.000000000 -0700
Change: 2020-09-12 08:27:52.000000000 -0700
 Birth: 2020-09-12 08:24:44.000000000 -0700

4OS2 does seem to report the birth time though,
Code: [Select]
{0}[k:\tmp] dir /t:c test

 Volume in drive K is RPM            Serial number is 57BF:35BF
 Directory of  K:\tmp\test

 9-12-20   8:24               6    124  test
               6 bytes in 1 file and 0 dirs

with cmd's dir reporting modified it seems

Code: [Select]
9-12-20  8:27a             6    124 a---  test
        1 file(s)           6 bytes used

And change not doing anything besides reflecting modified on OS/2, I'd guess it would on Linux or AIX where actual permissions are changed rather then EA's.
I don't understand what you are trying to say. An OS/2 IFS only knows about creation, last write and last access,that is defined in the IFS spec. 4OS/2 allows DIR to select what date of those to display and the OS/2 DIR does not (it shows last write as it seems).
It's that simple. And your tests seem to prove just that.

158
Setup & Installation / Re: how to tell DIR which date to show?
« on: September 12, 2020, 08:55:55 am »
On a 4OS2 command line you can use the /t switch:

/t:w last date/time written
/t:c date/time created
/t:a last date/time accessed (read)

the default OS/2 command line does not support this switch.

159
General Discussion / Re: OS/2 on a Via C7 desktop?
« on: September 10, 2020, 01:53:58 pm »
Need to load socketsk.sys and afinetk.sys instead of sockets.sys and afinet.sys.

160
Networking / Re: TP-Link - USB to Ethernet
« on: September 09, 2020, 11:37:41 pm »
See this note from the USBETHR.OS2 usbether.txt:

USBETHR.OS2 driver is designed to work with any Kawasaki LSI KL5KUSB101
based USB Ethernet adapter, however specific vendor/device IDs must be
specified during installation.

and this:
2.1.6   Update vendor/device IDs card parameters dialog; use the following
          identification IDs:
+-----------------------------------------------------+---------+---------+
|                    Adapter                          |Vendor ID|Device ID|
+-----------------------------------------------------+---------+---------+
|3COM USB Network Interface (3C19250) *               |   0506  |  03E8   |
|D-Link Corp. USB Ethernet Adapter (DSB-650)          |   2001  |  4000   |
|ADS Technologies Inc. USB Ethernet Adapter (USB-10BT)|   06E1  |  0008   |
+-----------------------------------------------------+---------+---------+

I would think that this HW has long gone out of business.

161
Just for your understanding:

the only USB drivers that "understand" USB1, USB2 or USB3 are the host controller drivers (USByHCD.SYS, y=U,O,E,X).
All other drivers  know NOTHING about the USB Hardware that you have. They only know about the data protocol that certain devices use (all the class drivers: USBKBD.SYS, USBMOUSE.SYS, USBHID.SYS, USBPRT.SYS, USBCOM.SYS, USBAUDIO.SYS, USBAUD2.SYS,USBETHER.OS2) or they are mediators between the class drivers and the host controller drivers (USBD.SYS).
It is the job of USBD.SYS to route the protocol packets from/to the class drivers to/from the proper host controller driver.

That's why I was asking what driver you are talking about. the MOSCHIP.OS2 driver knows nothing about USB hardware.

162
Networking / Re: Moschip USB to Ethernet for OS/2 not workingon USB1 port
« on: September 09, 2020, 08:56:16 am »
I do have tested multiple notebooks with the USB network card and the "Moschip USB to Ethernet for OS/2". They all were working like a charm with that network "card".

I now tested with a Panasonic Toughbook CF-M34 MK1, which comes with a USB1 port.
ArcaOS runs fine, USB is enabled in BIOS, but the Moschip USB network card does not work, nor do its' lights turn on, just the USB power LED on the network connector, but not the LINK or TRAFFIC LED.
So I assume, the driver just cannot handle USB1?

Thanks in advance, I wonder what the reason is.. :o

Exactly WHAT driver ? Are you sure that you have installed the proper host controller drivers (USBUHCD.SYS, USBOHCD.SYS, USBEHCD.SYS and now also USBXHCD.SYS) for the host controllers that your system has ? You should either have at the PCI.EXE output to find out or you will need to use the USB test tool testusb.exe (or some such) to find out what controllers you have.

163
Hardware / Re: Question about USB Audio (Input / Output).
« on: September 06, 2020, 08:59:03 pm »
Hi Lars,

My suggestion is for Martin to markup the device as not supported (or limited support).   If this is something you would like to support, I can test anything you send my way.

- Sean

I have a test driver ready. Where can I send it to ?

164
Hardware / Re: Question about USB Audio (Input / Output).
« on: September 06, 2020, 09:06:43 am »
Thanks.

I can see from the descriptor dump that your CM6553 device supports an optional interrupt endpoint in the "Audio Control" interface.
It is optional (HW implementer does not need to implement it and CM119 does not implement it either) and is meant to return back status if a setting has been applied (volume, etc.).
It looks like it is largely useless (as most devices do not have that interrupt endpoint) but potentially, if it IS existent, you might need to deal with it.
What is needed is to set up an interrrupt transfer and once that transfer returns (a status is returned), read the status info and issue a specific command on the control endpoint to acknowledge the status/do some action.

Currently this is just a wild guess but since you are saying that you DO hear the proper sound (albait accompanied by a loud hiss) then maybe these status interrupts need to be acknowledged to get the device to work properly.
I'll talk to Wim.

165
Hardware / Re: Question about USB Audio (Input / Output).
« on: September 04, 2020, 03:48:32 pm »
Can you please also attach the USB descriptor dump for the CM119 audio device ?

I want to check if there are additional differences to the CM6533 apart from the difference adaptive vs. synchronous isochronous data endpoints.

Pages: 1 ... 9 10 [11] 12 13 ... 51