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 ... 25
1
Storage / Re: changing USB volume letter
« on: June 18, 2019, 05:38:19 pm »
DFSee: "change LVM info" and then set '*' (without the '') as the drive letter. That equivalents to driveletter = None = the next available drive letter.

That is how I set up ALL my USB sticks and drives/partitions in order to avoid a driveletter conflict.

As to my USBMSD.ADD that can also mount "large floppy" formatted USB sticks: it also always sets the drive letter of the "fake" volume that it creates (for the 'large floppy' formatted USB stick) to '*' so that it will never conflict with any already used drive letters.

2
Multimedia / Re: Warp with 2 sound cards?
« on: June 06, 2019, 09:55:17 am »
Do you know any email address ?

3
Multimedia / Re: Warp with 2 sound cards?
« on: June 06, 2019, 09:05:16 am »
Lars,

With the current state of MMOS2, the fact that IBM essentially abandoned it around the time of Warp 3, I am not surprised that there are bugs.  I certainly would not put any fault in your driver or applet, in fact I applaud your efforts - I'm really impressed with how well your USB audio driver works.

The sad part - there was a time when MMOS2 was near the top of the game - I can recall when the only system that had better multimedia capabilities was the Amiga.  Unfortunately today it can be a challenge just to get a sound card to work.  But I can't say that I'm all that surprised.


Do you know the [Filters] sections in MMPM2.INI ? If you are a programmer or if you have any idea of how to USE these filters via the MCI interface API functions, I'd be more than glad if you would let me know. What I tried to achieve is to use these filters to convert ADPCM encoded WAV files to PCM WAV files (which is what the IMAADPCM and MSADPCM filter drivers most likely do) but I have no clue of how to "tie" a filter to the WAVE device so that filtering will actually take place. I planned to use that in the USBWAV DLL to make it completely transparent for users to open and play any WAV file, regardless of its internal compression type. I have managed to do that for u-law and a-law compressed WAVE files but I have not "wrapped" these as filters and am calling the registered CODEC procs directly (the a-law and u-law CODECS are also contained in USBWAV.DLL).

Unfortunately, that "filtering" stuff is not documented at all in the MMOS2 programming spec but the Toolkit header files clearly show that a filter is much like a device (it has an MCI DEVICE TYPE just analogous to a WAVE device). It's just not explained anywhere of how you open a filter "device" and "tie" it to a WAVE device.

When I look at the Windows API of what is left of the MCI API (yes, it still exists in Windows even if it is marked as deprecated ...) then I can see that they have removed tons of awkward to use MCI functions like, for example, the connector stuff that nobody ever really understood of how it is to be used. And of course, they also removed that "filter" stuff ...

Lars

4
Programming / Re: Compiling Tookit WPS applications
« on: June 04, 2019, 09:11:42 pm »
This WPS sample is so fucked up that you will have to use the old RC version 4.00 (find as RC16.EXE in the toolkit) instead of the newer version 5.00. That'll eliminate the RC errors you are seeing.
It's even more fucked up in that it links in the incorrect libraries. Once you fix that it still does not work all the way. It'll load but it will not display the properties dialog etc.

The best you can do is to rewrite the makefile. And then, to rewrite parts of the code ...



5
Multimedia / Re: Warp with 2 sound cards?
« on: June 03, 2019, 10:42:13 am »
I just tried the REXX interface: even though it claims to be able to specifically select a WAVE device in the form "Waveaudio01", "Waveaudio02", etc. that will not work. Instead it will effectively use the device that is specified as the "default" device via MMPM2.INI.

I guess that is due to a longstanding bug in Warp 4 and beyond where it is necessary to not only set the default WAVE but also the associated default AMPMIX device to have any sound for a specific audio device (in short: you have to set these as a pair).

But the REXX interface does not allow to specifically select an AMPMIX device.
Therefore, once you set the default AMPMIX device via MMPM2.INI, you are effectively also selecting the WAVE device.

My applet cannot work around this twisted design. It can also not be held responsible. The design is just broken.


Lars

6
Multimedia / Re: Warp with 2 sound cards?
« on: June 02, 2019, 10:28:24 am »
If an app or a REXX script does not explicitly specify a specific audio device then the default device is used. USB 10.227 now comes with an applet that hooks itself into the Multimedia Setup Objekt and that allows easy default device selection ( regardless if USB or not).
But if you want to select a specific device then the app needs some logic to query the available devices and to select from those. OS/2 provides the necessary API but an app has to use it.
For a REXX script, you need to open a specific device,see the REXX mm helpfile on how to do that and what schema the audio device names follow.
Yes it should still be possible.

7
Multimedia / Re: SYBA USB Stereo Sound Adapter: Good or bad?
« on: June 01, 2019, 10:06:56 pm »
No.
No time, no HW, no interest. And for the next 2 years (likely starting end of this year) I will be somewhere else. Which will likely coincede with the end of OS/2 for me.

8
Multimedia / Re: SYBA USB Stereo Sound Adapter: Good or bad?
« on: June 01, 2019, 07:39:57 pm »
I beg to doubt that Doug's judgement is based on any measurable or even measured facts.
This is how the USB HW works: you prepare a transfer by setting up transfer desriptors that point to the data to transmit. Then you kick off the HW which does the transfer completely autonomously, without any SW intervention.
The only thing left is to handle the HW interrupt that is asserted when the transfer is completed (passing the transfer descriptor back to the system, setting up the next transfer etc.).
This basic mechanism is about the same with USB 3 where USB 3 does have additional means to speed up things because I seem to remember it allows to define concurrent transfers (multiple transfers running partly in parallel). Again, it is the HW that does all the transfer, the SW part is negilible.
I don't see how changing SW from 16-bit to 32-bit can make that much of an impact but I am an engineer and not a believer.

USBMSD on the other hand is crippled by the fact that larger blocks of data (like one or multiple disk sectors) typically occupy more than one memory page (a list of "scattered" data). And then it would be helpful if the host controller drivers would allow to pass this scatter list directly to the HC drivers as the transfer descriptor mechanism allows to do just that: set up a list of discontiguous memory blocks to transfer. But this is not currently supported and therefore my workaround was to copy those scattered blocks to a contiguous piece of memory and transfer that in one shot. This DOES show performance improvement because people have already measured the performance gain.


9
Multimedia / Re: SYBA USB Stereo Sound Adapter: Good or bad?
« on: May 31, 2019, 11:42:40 pm »
Rewriting the USB driver stack as (almost) 32-bit is a waste of time. The performance gain will be unnoticeable because all transfers are done by the USB Busmaster DMA Hardware anyway. There is still the drawback with USBMSD that scatter/gather lists cannot be passed to the HC drivers (and I implemented a workaround for this limitation on my USBMSD). The USB stack otherwise works fine the way it was.
But I don't really care anymore. It is useless to argue against these decisions.

10
Programming / Re: Compiling Tookit WPS applications
« on: May 31, 2019, 11:33:11 pm »
The makefile was written for either CSet or VAC 3.
But you are using VAC 3.65. You are on your own but it surely can be fixed. Also looks like your DPATH does not contain all necessary paths for the VAC 3.65 compiler/linker.

11
Multimedia / Re: SYBA USB Stereo Sound Adapter: Good or bad?
« on: May 29, 2019, 05:45:04 pm »
I fixed USBD.SYS with 10.227.
That might explain why it now works ...
In the past I have done a lot of fixes and changes to USBAUDIO.SYS. I have no idea what David has done to the corresponding AN driver.

12
Multimedia / Re: SYBA USB Stereo Sound Adapter: Good or bad?
« on: May 28, 2019, 05:41:54 pm »
I installed the USB Audio 223 on my laptop, where USB audio had worked before, and the SYBA adapter is working fine. It must be a USB Audio 1.0 compatible device.

If 10.227 does not work for you as a whole you can also install AN 11.17 and only install the USBAUDIO install package.

But something is stopping it from working on the desktop, a Lenovo M720s that has only USB 3.0 ports. I am using an add-in Startek USB 2.0 PCIe card to provide USB. This seems to work for booting from memory stick, and mouse and keyboard.

But for both USB Audio 223 and USB Audio 226, there is no sound. When I run play.cmd, it does not ever complete. I plan to get 227 and try it. I'll let you know if it works.

13
Multimedia / Re: SYBA USB Stereo Sound Adapter: Good or bad?
« on: May 24, 2019, 10:30:41 pm »
If you did install 10.227, make sure you also selected the SPI update and also the applet install.
Then, go to "Multimedia Setup" and select the default wave/ampmix device. You can switch back and forth. As soon as you have double clicked on an entry, that device will become the default device.

Lars

14
Multimedia / Re: SYBA USB Stereo Sound Adapter: Good or bad?
« on: May 24, 2019, 08:18:40 am »
Unfortunately the USBRes output is broken (the tool is broken).

My guess is that it is an USB audio standard 2.0 device in which case you will need the USB audio drivers from my USB package. There is a USBAUD2.SYS driver that will serve those devices.

15
Web applications / Re: Firefox and youtube
« on: April 15, 2019, 09:25:11 am »
Hi André, it is actually the symbol in the icon that is trademarked. The rules are here, https://www.mozilla.org/en-US/foundation/trademarks/distribution-policy/ which clearly states that we can't distribute the Firefox branded web browser.

Hi Dariusz, yes the icon is compiled into firefox.exe as a resource and can't be easily changed.

Normally you should be able to use resmgr (comes with eCS and also AN) and pull the resources from the exe.
Then, you can replace the icon and use "rc.exe" to readd the resources to the exe (the whole resources segment will be overwritten/replaced by rc.exe). But you might need to use LXLITE /X to uncompress the exe before pulling out the resources and after readding you need to use LXLITE to recompress the exe.

Pages: [1] 2 3 ... 25