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 ... 29
Applications / Re: Timidity MCD install (Minstaller).
« on: October 21, 2019, 05:56:21 pm »
Hi All

A possible ini file entry is:-

    Application                                    Key
   PM_Workplace:IplLoad         MMMIDI

Not sure if this line in config.sys is relevant - change the "?" for appropriate drive letter




1) Thanks, yes, that is exactly the registry key that I meant.
2) I don't think MIDI.SYS is necessary to play MIDI files. MIDI files are played either directly through audio HW (if it supports that which these days most audio HW does not) or by creating,parameterizing and concatenating PCM sound fragments (that's what Timidity does in SW). I think MIDI.SYS is only necessary to control a device that can be controlled via MIDI commands such as a keyboard with MIDI input.

Applications / Re: Timidity MCD install (Minstaller).
« on: October 21, 2019, 06:44:42 am »
It's possible that these classes cannot be deregistered in the normal way. It is possible that they are always preloaded via some OS2SYS.INI or OS2.INI key, I forgot which one that was.

Applications / Re: Timidity MCD install (Minstaller).
« on: October 18, 2019, 04:19:16 pm »
I am not in front of my PC but if you have XWorkplace installed you can then use the WPS class browser to show all WPS classes. You will then be able to guess from the WPS class name what is the WPDataFile derived WPS class that handles MIDI files. It should be called "MMMIDI" or something like that. If you found it you can right click on that WPS class and choose "deregister" and it will no longer be registered. You can then restart the WPS. What you should do is to note down the DLL that implements the WPS class and also the WPS class name. You can then reregister the WPS class in case you want to do that.

Applications / Re: Timidity MCD install (Minstaller).
« on: October 18, 2019, 11:15:42 am »
This is exactly the problem I explained already: the WPS class that handles MIDI files uses the MMPM API to play the midi file.
And this API requires an MCD implementation of timidity. The only thing you can do is to deregister the WPS class that handles MIDI files, in which case a midi file will be an "ordinary" file of unknown content . But then, you will also lose the WPS icon representation of the midi file.

Internet / Re: PMMail and EARLYMEMINIT=TRUE problem?
« on: October 14, 2019, 03:53:49 pm »
There is an unfortunate twist with EARLYMEMINIT=TRUE.

There is a dynamic memory allocation DevHelper called "VMAlloc" that is to be used by kernel/driver SW. There exists a flag called "VMDHA_USEHIGHMEM" that does exactly what EARLYMEMINIT = TRUE is supposed to do: it allows to allocate memory above the 16 MByte physical address boundary on driver init (and only on driver init). For some reason I don't know, a call to VMAlloc with flag "VMDHA_USEHIGHMEM" will FAIL if "EARLYMEMINIT=TRUE" is specified.
But if you do not specify flag "VMDHA_USEHIGHMEM" along with "EARLYMEMINIT=TRUE" , then the allocation will be successful and will use memory > 16 MB address boundary.
The only solution to ensure that (on driver init) you can allocate memory above the 16 MBYTE physical address boundary is to try to allocate with "VMDHA_USEHIGHMEM" flag and if that fails to retry without this flag. That way, you will succeed one way or the other (unless you have too little memory in general).

Therefore, I suspect that all those drivers that fail with "EARLYMEMINIT=TRUE" set in config.sys try to dynamically allocate memory on driver init with "VMDHA_USEHIGHMEM" flag set and would likely work OK if the binary were patched to NOT set the VMDHA_USEHIGHMEM flag.


Internet / Re: PMMail and EARLYMEMINIT=TRUE problem?
« on: October 11, 2019, 11:27:25 pm »
I had a look at the QSINIT SDK code: there is a "mode" to start the HD4DISK.ADD with the /i parameter. In that case, no disk will show up but instead, the memory allocated for the RAM disk will be accessible as ordinary memory via IOCTL calls (you can read from and write to it).
However that will only allow one app to use that memory at a time, it can only read/write in blocks of 512 bytes and of course you will have no RAM disk. I guess that is not a good solution to the problem.

Hardware / Re: UNIAUD Update: Thinkpad X250 - The Perfect ArcaOS Laptop
« on: October 07, 2019, 07:20:10 am »
Have you run "unimix -list" to see what controls your audio device has ? Maybe you will find a switch that you need to turn on to have audio play via the built in speakers. The control names are fairly self explanatory.

Applications / Re: Timidity MCD install (Minstaller).
« on: October 07, 2019, 07:17:02 am »
Hi David,

yes, there are applications that can play MIDI just fine. The only advantage of a MCD implementation is that it better integrates in the WPS and the MMPM environment as you can use the MMPM API to control the "MIDI device". For example, that makes it available to any application that uses the generic/well defined MMPM API to play a MIDI file instead of calling an app directly. Additionally, the WPS will play a MIDI file on a double click because underneath, the WPS class that manages MIDI files uses the MMPM API to play the MIDI file.

Applications / Re: Timidity MCD install (Minstaller).
« on: October 06, 2019, 07:07:16 pm »
No, timidity MCD source Code is Not helpful.
It's completely Broken and IT cannot handle multiple instances (I did already Look at it)

Applications / Re: Timidity MCD install (Minstaller).
« on: October 06, 2019, 10:14:08 am »
Timidity MCD is broken. I was thinking about writing a new one that just invokes timidity.exe under the hoods but I never found the time to do it.
What does work is to associate .MID files with timidity.exe but that does not give you the "double click and play" functionality.

This also centers around Linux but nothing else.

Here it is an interesting article:

Today, however, Microsoft announced that it is supporting the addition of exFAT to the Linux kernel and publishing the technical specifications for exFAT.

In addition to wanting it to become part of the Linux kernel, Microsoft also says that it hopes that the exFAT specs will become part of the Open Invention Network’s  Linux definition.

If this is actually true and not a trick, it may solve our issue on why the FAT32 project got forked by Arca Noae. Since the FAT32 project (Netlabs / Valerius) included exFAT support, AN didn't want any reference to it because of the risk on getting sue by Microsoft.  Now it may change, let's see how things evolve on this subject.


So how is this to be interpreted:

To be clear, Microsoft isn’t open-sourcing exFAT — but it is making sure anyone building with Linux can use it. “It’s important to us that the Linux community can make use of exFAT included in the Linux kernel with confidence.”

Hardware / USBDRV 10.230 - fixes for USBCALLS + USBRESMG
« on: September 24, 2019, 08:49:10 am »
I had to reissue the USB drivers as I was pointed to some annoying bugs when using USBCALLS + USBRESMG. There are quite a few applications that rely on the correct working of USBCALLS+USBRESMG (like for example "lsusb.exe" to show device info) so I thought it to be a good idea to fix it immediately.
I hope to thave these problems fixed now.

Applications / Re: Firefox 45.9.0 can no longer play Youtube movies ?
« on: September 20, 2019, 06:04:02 pm »
1) I did have FFMPEG installed
2) I now did a "Refresh Firefox" and that has fixed the problem.

Many thanks for your help !


Applications / Re: Firefox 45.9.0 can no longer play Youtube movies ?
« on: September 20, 2019, 12:37:32 pm »
Maybe I screwed something up about the configuration ("about:config"). Is there a way to reset the configuration to some "safe default" or do I need to create a new profile ?

Pages: [1] 2 3 ... 29