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 ... 28
1
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.


Lars

2
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.

3
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.

4
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.

5
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)

6
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.

7
This also centers around Linux but nothing else.

8
Here it is an interesting article:

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

Quote
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.

References
- https://techcrunch.com/2019/08/28/microsoft-wants-to-bring-exfat-to-the-linux-kernel/
- https://venturebeat.com/2019/08/28/microsoft-wants-its-exfat-file-system-in-the-linux-kernel/
- https://docs.microsoft.com/en-us/windows/win32/fileio/exfat-specification

So how is this to be interpreted:
https://venturebeat.com/2019/08/28/microsoft-wants-its-exfat-file-system-in-the-linux-kernel/

</quote>
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.”
<quote>

9
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.

10
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 !

Lars

11
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 ?

12
Applications / Firefox 45.9.0 can no longer play Youtube movies ?
« on: September 20, 2019, 08:09:16 am »
I can no longer get Firefox 45.9.0 to play Youtube movies. It used to work in the past but I cannot remember when that would no longer work.
Is this a known problem ? And is there a solution ?

13
Multimedia / Re: Cannot play midi files
« on: September 20, 2019, 08:07:09 am »
As an alternative I see sound card drivers on Lenovo's site for the T42 but I cannot install them as it's a self-extracting executable that goes onto a floppy drive. Any tips on how to obtain those files as I don't have a floppy drive?

You can install a "virtual floppy". It's essentially a RAM disk that looks to the OS as if it were a floppy:
http://hobbes.nmsu.edu/download/pub/os2/system/drivers/filesys/vfdisk60.zip

14
Applications / Re: About bldlevel
« on: September 14, 2019, 09:16:00 am »
Be careful with various versions, because original bldlevel has a limit on searching string in a file.

Not sure about the exact limit, but looks like only first 500 or 512kb of file is scanned. Signature placed after this position is just "invisible".
...which would explain why IBM linkers place this string into the resident name table ...

15
Applications / Re: About bldlevel
« on: September 06, 2019, 09:16:19 am »
Hi Martin

If you have a copy of USbcfg installed then you should also have a copy of GETDESC.DLL which USBcfg uses to extract buildlevel information. However, this DLL is built to work with Pascal coding so would probably need a bit of reworking to work with "c" code.

The DLL was put together by Lars, of USB drivers fame, so you could ask him if he could build a "c" version.


Later Edit: The zip file Lars sent me contains source (cpp, def files) and makefile so you could probably modify it yourself. Let me know if you want a copy.


Regards

Pete

Err,  I have to admit that in the end, GETDESC.DLL also uses a direct call to "bldlevel.exe" to extract the description info. The DLL just pipes the output into a memory buffer, extracts the description string and passes it back into the string buffer provided by the caller.

The reason for this: Initially (on my first attempt) I determined that the description would end up (for the compiler and linker toolset that I used) in the resident name table of the DLL (that's a place in the DLL file that serves a special purpose).  I was done and everything was fine. Unfortunately, another compiler and linker toolset would NOT place the description info into the resident name table but "somewhere else" into the file.
In short: there was no common way to determine this info and therefore I used bldlevel.exe which just scans the complete file for the description string template.

Pages: [1] 2 3 ... 28