Messages

1

Multimedia / Re: Can aswitch.exe be used for always connected/attached usb speakers?

« on: October 07, 2024, 05:09:53 am »

I notice that the USB interface descriptor for the speaker specifies a 48000 sample rate but under [WMBWAVEUSB01], it's configured for 44100:
 PARMSTRING=FORMAT=1,SAMPRATE=44100,BPS=16,CHANNELS=2,DIRECTION=PLAY

You may want to try changing SAMPRATE to 48000. After doing so, do NOT open MMSetup (stpm.exe) before you reboot - it always rewrites MMPM2.INI with the values currently in memory, wiping out any manual changes.

2

Multimedia / Re: Can aswitch.exe be used for always connected/attached usb speakers?

« on: October 03, 2024, 10:00:00 pm »

As the driver level could be the problem, I updated to 12.16 (was using AN 12.14)
Following a reboot there was still no sound

I also downloaded USBAUDIO-12.16.exe which unpackaged itself into \MMOS2\INSTALL\usbaudio but did not install any files anywhere. I replaced the usbaudio.sys/sym files in \mmos2 with the files from \MMOS2\INSTALL\usbaudio and rebooted.

'USBAUDIO-12.16.exe' is the old IBM driver that lacks Lars' additional features. Do not intall it. Also, *.sym exist solely to make debug reports more intelligible. They are completely passive (and generally unused), so copying in the wrong ones isn't helping anything.

The Desktop Startup sound almost played - started but cut off about 66% of the way through.

So, you rebooted and got no sound, then did something that had no effect and rebooted. Voila, sound! Are you sure you didn't do anything else?

Do I need to "clean up" the mmos2 setup?

Messing-around when you don't know the correct configuration is seldom helpful.

I have the files from the Enhanced USB audio packages installed although I am not using the drivers from the package.

What does this mean? If the Enhanced USB audio packages are installed, how can you not be using its drivers?

At this point, I can only think of two possibilities:

* unlikely: maybe this is a USB Audio v2 device. With no audio streams open, set "UAC2 Adapter Wave" as the default in MM Setup, close it, then play a sound. If this fails, go back to "USB Adapter Wave".

* likely: perhaps there are still problems with xHCI isochronous transfers. File a bug report.

3

Multimedia / Re: Can aswitch.exe be used for always connected/attached usb speakers?

« on: October 02, 2024, 08:39:33 pm »

I may have found the cause of no sound with this usb soundbar.
I'm guessing but think the following applies:-

Too much speculation...

'usbaudio.sys' supports the USB Audio Standard v1.0 which is implemented by nearly all USB audio devices. 'usbaud2.sys' supports the USB Audio Standard v2.0 and is only implemented by a few newer, high-end devices. The standard operates independently of the transport, so whether you have USB2 or USB3 is irrelevant. (Also, it's highly unlikely you have a "USB3-only" system. Rather, you only have xHCI controllers which typically support both USB2 and USB3.)

Since the datasheet for the soundbar makes no mention of which standard it uses (and it connects to your USB ports using a USB-A connector), it's almost certainly a USB Audio v1.0 device.

Some of the more likely causes of the problem are:
* some machines have USB3-only ports as well as USB2/3 ports: maybe your device is plugged into the wrong one.
* your USB stack is back-level: IIRC, AN's drivers had problems (now fixed) with isochronous connections which are used for audio.
* you have garden-variety settings issues in uniaud: use PMUnimix to set all available input volumes to max
* perhaps your driver installation failed (though I doubt it): confirm both driver lines appear in config.sys and aren't duplicated; open 'mmpm2.ini' and confirm you have sections for "WMBWAVEUSB01" and "WMBWAVE2USB01".

FWIW... I have an xHCI-only system and it all WFM.

4

Multimedia / Re: Can aswitch.exe be used for always connected/attached usb speakers?

« on: September 30, 2024, 11:55:23 pm »

> you need to install the USB audio driver using Minstall.

Easier:
- mount your AOS ISO
- open 'Programs\Multimedia\Multimedia Installer'
- click on "Audio Drivers on your ArcaOS DVD/ISO"
- on the dropdown list that appears, install both:
  * Enhanced USB Audio - device support
  * Enhanced USB Audio - sample rate support
  (these are from Lars' USB Audio package)

Bonus: this will also clean 'mmpm2.ini' after installation is done.

For those who want to do a cleanup without actually installing anything, select a sound driver you DO NOT have installed, then press "Install/Remove". On the next popup screen select "Remove", then OK.  It won't complain if the driver can't be found and will proceed to do cleanup, then tell you it's done.

5

Multimedia / Re: Can aswitch.exe be used for always connected/attached usb speakers?

« on: September 30, 2024, 12:57:24 am »

Will aswitch.exe recognise already attached usb speakers at boot and do it's thing to output audio via usb

It _should_ work as described, but...

If the soundbar is the only speaker you'll ever use, why not open 'Multimedia Setup' to the "USB Adapter Wave" page and make that the default audio device? If this is AOS 5.0.3(?) or later, this will work as expected. On eCS, MCP, etc, the checkbox is broken so 'aswitch.exe' is needed.

6

Setup & Installation / Re: How to get rid of the second boot menue?

« on: September 07, 2024, 03:05:14 am »

Are you using an old or prerelease version of the UEFI ArcaOS boot loader? That menu is part of the loader, but it's been disabled by default in all GA releases.

If there's more than one bootable partition, and the user hasn't specified the one to use (via the commandline), how else is 'os2ldr.efi' supposed to know which one to boot? The partition menu is required for proper operation.

In any case, having it available (e.g. via the "*" menu entry in ANLauncher) allows the user to select a partition that may not be on his bootmanager's menu.

7

Applications / Re: Unzip Version 6.0 hangs when booting to a commandline

« on: August 05, 2024, 04:50:28 pm »

Attached is a standalone version of 'unzip.exe' v6.0 compiled with VACPP 3.65. I have only done minimal testing on this.

Also attached is a diff of the changes. Most of the compile errors came from "#include <ctype.h>" being mispositioned in 'os2cfg.h'; moving it up in the file fixed them. I also added a "vac" target to 'makefile.os2'. It's set up for VAC 3.65 but should(?) work with 3.08.

8

Setup & Installation / Re: ArcaOS 5.1

« on: July 30, 2024, 07:44:22 am »

Just in case the manual says "In addition, it is not possible to upgrade from a traditional BIOS installation to a UEFI installation."

You should't believe everything you read. Months ago, I posted a package to convert from BIOS to UEFI. The process is trivial and fully license-compliant. If you need it, do a search of this forum.

9

Applications / Re: Archive tool problem

« on: May 14, 2024, 06:35:03 pm »

Reinstalling any WPI that was included with AOS is really easy:

* mount the ArcaOS ISO file (doubleclick on it) or load the DVD you burned
* navigate to x:\CID\SERVER\ARCAPKG
* find the WPI you need and doubleclick on it
* ...done

Pretty much anything you'd want to (re)install can be found in one of the subdirectories of \CID\SERVER.

10

Programming / Re: ClassiCube porting thread

« on: May 07, 2024, 09:25:58 pm »

2) "args->filters" is effectively a PAPSZ pointer, that is, a pointer to an array of pointers where the last pointer in the variable array is a NULL pointer

This is not correct. There is absolutely no indication anywhere in the *OS/2* docs that that 'fileDialog.szFullFile' is anything other than a simple string. If you wanted to filter based on multiple extensions, you do it like this: "*.exe;*.cmd" using a semicolon, not a null, to separate the filters.

Regardless, the most appropriate way to determine whether this is the source of the problem (and I doubt it is) is to make the assignment as simple as possible:  strcpy(fileDialog.szFullFile, "*.*");

see the example code for the Windows implementation

Not helpful.

11

Applications / Re: XWP v1.0.16

« on: April 29, 2024, 06:34:16 pm »

I would like to just stick to the menu selection which would simply show that BLDLEVEL info in it's own pop-up

Why wait for someone to implement a feature that you can have _now_?

Open Properties for \os2\bldlevel.exe, and on the 'Session' page uncheck "Close window on exit". Then on the 'Association' page, add "*.DLL" and "*.EXE". Done! When you need this info, select 'Open as', then 'bldlevel.exe'.

FWIW... on my system, any info I may need about a binary is immediately at hand because I have associated 6 different utils with *.exe and *.dll. Some of these associations are program objects while others point at the exe itself:
unlock.exe
exehdr.exe
exeinfo.exe
pmdll.exe
hexedit2.exe
bldlevel.exe

Warning: you can *not* copy/paste from a VIO window whose app has terminated - it's instant death. If you need this ability, associate a simple .cmd file like this and leave "Close window on exit" checked:

-----bldlvl.cmd-----
@bldlevel %1
@pause
------------------------

12

Applications / Re: LarsenCommander - new test version

« on: April 23, 2024, 12:18:14 am »

there are 5 entries [...] and you map them to your categories.

FWIW... you're not limited to just the 3 default fonts. Rather, you can use these entries as guidelines for setting the correct size of your preferred typeface. For example, if lcmd uses 'Helv' somewhere, you can get the entry for the category (say, "menu") but only pay attention to the size (use 'atol(...)). If 'Helv' has that point size, use it. Otherwise, go up or down at point _or_ substitute WarpSans (non-bold).

Do all this during init and save the results so you don't have to duplicate a lot of code. (Note: the default values in 'os2.ini' will never change during a session - they're only updated during shutdown - so there's no need to check for  new values.)

13

Applications / Re: LarsenCommander - new test version

« on: April 22, 2024, 10:29:43 pm »

I would like to have something that saves me some time grabbing by default font size (as XWP shows as default), but I understand that it is not easy to implement for each component described in the Font settings of lcmd.

It shouldn't be particularly hard: there are 5 entries under 'os2.ini->PM_SystemFonts'  [see below] and you map them to your categories. For example, 'PM_SystemFonts->Menus' maps to lcmd's 'AppWin.MenuBar' and its other menu settings.

DefaultFont: System Proportional - if this entry is missing/empty, assume 10 point SysPro

IconText:  WarpSans - this is mislabelled, it should be "Folder text" since it also is used for Details view
WindowText: WarpSans - standard dialog text

Menus: WarpSans Bold - both menubars and popups
WindowTitles:  WarpSans Bold

The key to using defaults while still allowing customization is *never* save the default value. That way you don't get stuck with a value that _used_ to be the default but isn't any longer.

14

Games / Re: Minecraft

« on: April 11, 2024, 07:52:17 pm »

How would I change the default browser settings?

You don't need a third-party app. Open any URL object's Properties to the 'Browser' tab, fill in the details, then press the 'Set Default' button below.The info ends up in os2.ini->WPURLDEFAULTSETTINGS->DefaultBrowserExe and ->DefaultWorkingDir.

perhaps DosStartSession() would be better to use.

If this is linked as a PM app or gets morphed into one, use WinStartApp() - much easier.

15

Applications / Re: XWP v1.0.16

« on: April 09, 2024, 07:19:40 pm »

XWP full does not enable by default the "Enable global object hotkeys".

I made the mistake of assuming it did, and that the settings on the Icon page would be disabled if the feature were disabled - neither of which was true. I've now fixed both.

In doing so, I found a bigger issue: XWP-Full starts with fewer features enabled than XWP-Lite/ANXWP. Since nothing in Lite is risky/experimental/controversial, I can't see any reason why Full shouldn't default to the same feature set as Lite. In the next version (1.0.17), it will. All the checkboxes will remain, only the ones that are checked by default will change.

BTW... this only affects new installations - upgrades will use your existing settings and shouldn't change anything.