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] 2 3 ... 90
1
The audio control interface header says bcdADC = 1 so it's a class 1 device. You will need USBAUDIO.SYS.
If you post the complete MMPM2.INI I would be able to say if the install is complete. As I mentioned, not only the drivers need to be installed.
And as Rich said, you should use the "enhanced" package.
If you can hear sound at all, you should check if setting the volume works (it should). If the sound stops playing prematurely, try with a USB 2.x only port (a port connector not colored in blue) if you can find that on this PC or another. If that works without a problem, then I suspect that USB isochronous transfers do not work properly with USB 3.0 (USBXHCD.SYS).
The iso endpoint is of type "adaptive". I don't know if that's what my USB audio device uses. Ill need to check. Maybe that type needs special treatment not yet implemented.
By the way, UNIAUD and the on-board sound support have nothing to do with/no impact when using that soundbar. The audio HW is all contained in that soundbar. The audio HW itself only supports a sample rate of 48 kHz but USBAUDIO.SYS contains rate conversion to/from quite a few other standard sample rates.

2
plus, if you want, post your MMPM2.INI file.
By the way, did you regularly install the sound drivers (not just copying the driver file)? The package that I provided also installs a replacement for AUDIOIF.DLL (called USBAUDIF.DLL) and an SPI update that is matched to USBAUDIF.DLL.
Your MMPM2.INI will tell.

3
If you have lsusb.exe installed, have it dump the descriptor info (with the audio device inserted of course). That will allow to check if it is a class 1 or class 2 device.

4
Hi Rich

Hmmmm.... What "USB Adapter Wave" page? - I suspect that page only appears if a USB Audio Device is installed.


Regards

Pete

No, it appears if the USB Audio Driver is properly installed (including the necessary updates to MMPM2.INI). The MMOS2 subsystem has no way of knowing if a USB audio device is inserted or not.
But you need to activate a certain sound driver (UNIAUD or USBAUD) in order to support streaming of data to/from the devices that are attached to that driver.

5
Programming / Re: [GCC] Unable to define getMemorySize()
« on: September 30, 2024, 01:57:45 pm »
Last update: yes, getrusage is available in our libc. Compiling it - will test this binary asap and - if it works as I expect - it's going to HobbesArchive.
Mentore

Seems like our getrusage does not return any memory size information, only use of time ("ru_utime", "ru_stime").
I suspect this is not what you are looking for.
As to memory: Rich Walsh has elaborated somewhere in this forum about what the various memory sizes mean and how they play together:

https://www.os2world.com/forum/index.php/topic,3445.msg41758.html#msg41758

It would be nice if we could get that added to "getrusage".

6
Programming / Re: [GCC] Unable to define getMemorySize()
« on: September 27, 2024, 09:44:10 am »
Looks like you will have to write an OS/2 get_avail_mem_size.

Oh, that may be actual fun :) guess I'll give it a go asap.
Mentore
libc has that implemented since long. see https://github.com/bitwiseworks/libc/commit/1ee2ad15bb9db8f0a327ec6a3cf6c216d2004b8c

The libc implementation returns size in pages whereas in this case it is supposed to be returned in bytes. But of course that is easy enough to take into account.

7
Programming / Re: [GCC] Unable to define getMemorySize()
« on: September 26, 2024, 04:01:19 pm »
#if defined(_WIN32)
#undef BOOLEAN
#include <windows.h>

#elif defined(__unix__) || defined(__unix) || defined(unix) || (defined(__APPLE__) && defined(__MACH__))
#include <unistd.h>
#include <sys/types.h>
#include <sys/param.h>
#if defined(BSD) && defined(HAVE_SYS_SYSCTL_H)
#include <sys/sysctl.h>
#endif
#if defined(__APPLE__) && defined(__MACH__)
#import <mach/mach.h>
#import <mach/mach_host.h>
#endif
#elif defined(__OS2__)
#define INCL_BASE
#include <os2.h>
#else
#error "Unable to define getMemorySize( ) for an unknown OS."
#endif

...
unsigned long long getAvailableMemorySize(void)
{
...
#elif defined(__OS2__)
unsigned long mem_got;
if (NO_ERROR == DosQuerySysInfo(QSV_TOTAVAILMEM,QSV_TOTAVAILMEM,&mem_got,sizeof(mem_got)))
{
    return (unsigned long long)mem_got;
}
return 0L;
...

8
If you want it or not does not matter: there will never be a 64-bit version of OS/2. Period.

9
Either David's suggestion or get

http://www.hobbesarchive.com/Home/Download?path=/Hobbes/pub/os2/system/drivers/mouse//IBM_Single_Mouse_10-163.zip

from hobbesarchive.com and install that (the install.exe is missing, just copy files manually or get an older version of single mouse from hobbesarchive)
and then try the "FORCEPS2PP" or "FORCEGENERIC" or "FORCEIM" parameters (without the quotes) on the mouse.sys commandline.



10
General Discussion / Re: How to use a multipartioned usb key ?
« on: August 26, 2024, 12:55:56 pm »
Here is another round-about way to make a JFS partition on an USB drive.  With this method, I am using the whole drive for the JFS.

Open DFSee.
Select Scripts in the menu
Select Make Fat32 Data USB disk
Select the drive and make a fat32 data disk.
Follow the prompts.
Eject USB drive and reinsert.

Now I use FM/2
Open FM/2
Right click on the FAT32 USB drive
Select Miscellaneous
Select Format Disk
Select JFS

I do the quick format.
Done.

I bought around 10 packages of 3- 32 GB USB drives at Target last year for around $5.00 for each package.  It was an after school clearance.  Formatted them With DFsee to FAT32.  Thus, it was easy for me to format JFS under FM/2  when I want.  I had already made them FAT32 with DFSee.  The drives were originally FAT32 when bought.  However, for ArcaOS to use the drives, DFSee had to be used to reformat them Fat32.  Being already done, it took little time to convert to JFS.

It would be nice for DFSee to have a script to make a JFS data disk.

DFSee does have an option to create a JFS data disk. But that fails often enough and the cause seems to be that a JFS format already has some expectations regarding how the Master Boot Record and/or the end of the first track (that is: sector 63) should look like.

11
Internet / Re: Dooble releases-Qt6
« on: August 23, 2024, 11:59:59 pm »
Thanks Dave - it's working well here!

 There is a long standing bug in Dooble on OS/2 where if you try to open an HTML file, it always says 'Your file couldn't be accessed' even though you just clicked on it. However, if that file is on your %UNIXROOT% drive (say C:), and you remove 'C:' from the address bar with that file name on it, the file is displayed. If it is not on the %UNIXROOT% drive, removing, say 'D:' does not help and can not be displayed.

 The implication is the code is using a Linux standard to find the file (no drive letters) so it works this way only on the %UNIXROOT% drive. But the Windows version of Dooble does use drive letters and it does work, so it seems there must be a code path available to use drive letters when displaying files if needed.

 Are you familiar with this? Has it been looked at in the past? The reason it is important to me is I would like to use Dooble to display e-mail messages from PMMail, but it doesn't work because PMMail is not on %UNIXROOT% so even removing the drive letter doesn't help in that case. Seems like there should be a straight forward solution to this, if the proper code was identified...

Regards,

I vaguely remember that Dmitry already had a fix in place that went into a test version of one of the Qt5 DLLs. I just cannot remember which one that was ...

Thanks for the tip.

There is: https://github.com/bitwiseworks/qtwebengine-chromium-os2/issues/50
&
https://github.com/bitwiseworks/qtwebengine-chromium-os2/commit/6d53f8735fc37460d217f6d641eae585960c1e53

This may have been applied by Dmitry after I created my diffs... I certainly don't have it in my branch...

Yep, that's the fix.

12
Internet / Re: Dooble releases-Qt6
« on: August 23, 2024, 11:55:46 pm »
I found it. It is an updated version of qt5webc.dll which is part of the QtWebEngine RPM.
With this updated version, Dooble is able to display local files, regardless on what drive they are located on.

Something like:
file:///E:/CONFIG.SYS
will display in the browser.

{0}[d:\usr\lib] dir qt5webc.dll*

 8.09.22  22.43     271.973.910      0  Qt5WebC.dll
25.09.21  19.47      92.191.016      0  Qt5WebC.dll.bak
 8.09.22  22.43     271.973.910      0  Qt5WebC.dll.new

13
Applications / Re: Cannot create archive
« on: August 23, 2024, 07:15:34 pm »
Turning it off and back on again did the trick. Thanks !

14
Internet / Re: Dooble releases-Qt6
« on: August 23, 2024, 04:46:18 pm »
Thanks Dave - it's working well here!

 There is a long standing bug in Dooble on OS/2 where if you try to open an HTML file, it always says 'Your file couldn't be accessed' even though you just clicked on it. However, if that file is on your %UNIXROOT% drive (say C:), and you remove 'C:' from the address bar with that file name on it, the file is displayed. If it is not on the %UNIXROOT% drive, removing, say 'D:' does not help and can not be displayed.

 The implication is the code is using a Linux standard to find the file (no drive letters) so it works this way only on the %UNIXROOT% drive. But the Windows version of Dooble does use drive letters and it does work, so it seems there must be a code path available to use drive letters when displaying files if needed.

 Are you familiar with this? Has it been looked at in the past? The reason it is important to me is I would like to use Dooble to display e-mail messages from PMMail, but it doesn't work because PMMail is not on %UNIXROOT% so even removing the drive letter doesn't help in that case. Seems like there should be a straight forward solution to this, if the proper code was identified...

Regards,

I vaguely remember that Dmitry already had a fix in place that went into a test version of one of the Qt5 DLLs. I just cannot remember which one that was ...

15
Applications / Re: Cannot create archive
« on: August 23, 2024, 04:43:27 pm »
I don't have a space problem. However, unchecking and rechecking "Archive Desktop" might do. I'll give it a try.

Pages: [1] 2 3 ... 90