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 ... 8 9 [10] 11 12 ... 14
Events / Re: Any questions for Warpstock 2016 ??
« on: October 26, 2016, 10:24:30 am »
... and none of the additional SW needed is likely to be available under OS/2.

Events / Re: Any questions for Warpstock 2016 ??
« on: October 23, 2016, 01:02:26 am »
@Lars: does the USBAUDIO.SYS support USB microphones? My USB webcam has one built in - would be a step closer to having some kind of streaming video/sound capability using USB devices.

Let me put it this way: it should already. If it does not for your case then there is room for improvement. It depends on the sample rate. USB devices only have have a reduced number of sample rates they support. Normally they are smart enough to support 44.1 kHz (CD-ROM sample rate) and/or 48 kHz (the sample rate for professional equipment). Everything else would need to be supported by sample rate conversion in SW.

Events / Re: Any questions for Warpstock 2016 ??
« on: October 22, 2016, 12:47:49 am »
Is there any interest in updating USBAUDIO.SYS ? Right now I updated volume control so that master volume and application specific volume setting will both work. It's enough to have volume control (via master volume control) when playing audio CDs or playing system sound (via master volume control and application volume control via the specific system volume setting).
But there still is enough other stuff to do.

Applications / Re: anpm question problem DUMPPROC / PROCDUMP
« on: September 30, 2016, 01:34:29 pm »
The easiest is to delete or backup the "usr" and "etc" subdirectories.
I seem to remember that if you then run ANPM it will ask you if you want to download and install the YUM/RPM base package. Answer with yes and your "usr" and "etc" subdirectories will be properly recreated.
Once that is done, rerun ANPM and follow all of the instructions in the link that Doug has already posted and start updating all the packages that show up as outdated (there will be quite a lot).
The nice thing is that once you have all that done, you will not have any problems with ANPM in the future.

Your problem is due to some hosed python installation. I had the very same problem and I fixed it the way I stated above.

Setup & Installation / Re: eCS install problems on a recent mainboard
« on: August 25, 2016, 06:40:57 pm »
1) make sure it's set to AHCI in BIOS
2) use OS2AHCI.ADD (of course)
3) try the /!R for OS2AHCI.ADD. I already had to specify this switch on installation. It prevents reset of the SATA ports on system start.

For OS2AHCI.ADD you can also try /F and /N switches. These switches should improve performance (enable command queuing, force usage of disk HW cache).


Programming / Re: Compiling PM app on 2016.
« on: August 16, 2016, 05:43:59 pm »
In this case it will not work as Martin is not compiling C++ code but rather C code.

Programming / Re: Compiling PM app on 2016.
« on: August 14, 2016, 08:51:26 pm »
Hmm, seems that min and max macros are defined in the toolkits stdlib.h but not in the kLIBC stdlib.h. Not sure about the best way to use the toolkits stdlib.h so simplest to add the macro.

Should I open a ticket for stdlib.h to be updated on the KLIBC project? Does it makes sense?


No it makes no sense as "min" and "max" macros are not ANSI compliant and therefore not required.
In reality, most compiler's header files supply these macros as they are used so often. But ANSI does not define them ...


Applications / Re: Os/2 and Midi
« on: August 14, 2016, 12:16:33 pm »
If you are not after playing MIDI files but rather after interfacing with a MIDI device I think this is what the MIDI.SYS driver is for.
However you will not get by without additional programming effort. MIDI.SYS offers a generic interface to client drivers (which have to be written) in order to read or write MIDI data. The client driver in turn interfaces with an application (usually via some freely definable IOCTL interface I would suppose).
You will find the MIDI.SYS driver interface (IDC) (badly and insufficiently) documented in the DDK in the "MMPM/2 Device Driver Reference" document under the chapter "Real-Time MIDI Subsystem" (the MIDI.SYS driver IS the RTMIDI support that chapter talks about).
The odd thing is that MIDI.SYS driver is not necessarily installed on your system and you might also need to add it to config.sys. You would find it in the \MMOS2\MMPLAYER subdirectory (at least on an eComStation installation).


Programming / Re: Compiling PM app on 2016.
« on: July 30, 2016, 07:29:36 pm »
1) use ANPM to install these packages: gcc, gcc-wlink, gcc-wrc. Alternatively you can run "yum install gcc gcc-wlink gcc-wrc" from a commandline.

2) Make sure these lines are in config.sys or add them if they are not. Fix the drive letter to your system and make sure you have the OS/2 toolkit installed (the below setup will use the OS/2 toolkit for all headers instead of what comes in usr/include. The reason is that what comes in usr/include is not complete with regard to what the toolkit offers):

3) this is how you then compile a file:
gcc -c -Wall

4) this is how you link together multiple files (and create a map file) and link to libs lib1 and lib2
gcc -Zmap -o myexe.exe lib1 lib2 foo1.o foo2.o

There are variations to the compiler flags: add -O if you want optimization or -g if you want to debug etc.
You should just know that what is set in GCCOPT appends to what you specify as switches to gcc.exe.
I did it this way because there are things that you always would need to set, for example the -Zomf switch
(for the compilation as well as for the linking stage).

5) change your makefile so that it uses the switches for compiling and linking as given above.

6) instead of using nmake.exe you could also use make:
use ANPM and install kbuild-make or run "yum install kbuild-make" from the commandline
However that means you will need to change the makefile syntax and structure to what make accepts. I recommend some book.
The documentation of nmake.exe however is available in the OS/2 toolkit.

One last thing: the above setup will allow you to source code debug executables built with gcc to operate under the VAC debugger or various other debuggers that use the HLL debug format. This is the standard debug format that any of IBM's debuggers use (VAC debugger, SD386, ICAT, etc.). I would hope that even the Watcom debugger can debug this format but I haven't tried and I am not sure.


Applications / Re: Yum error! "Python strikes again"!
« on: July 19, 2016, 02:34:54 pm »
1) rename the \etc directory to say \etc_xxx
2) rename the \usr directory to say \usr_xxx
3) reboot and hope for the best
4) rerun ANPM, it should now ask you if it should install yum/rpm (because it now can no longer find it because of 1) and 2) ), answer with yes and wait until it is done
5) reboot, if everything went well you will now have a new \etc and \usr directory and you can then delete \etc_xxx and \usr_xxx. You will need to run ANPM to update a whole bunch of packages because the prebundle installed at 4) contains outdated versions of a number of packages.

Utilities / Re: IRQ Monitor
« on: June 25, 2016, 12:25:55 pm »
May I throw in that with USB drivers 10.205 and 10.206 I have also reworked the USBMSD.ADD data transmission code. I hope it has helped performance while at the same time it should reduce IRQ load.

Hardware / USB drivers 10.206 released
« on: June 22, 2016, 10:35:02 am »
Sorry but since it's kind of urgent: I had to do yet another critical fix to USBMSD.ADD in order to prevent data loss and/or an endless cycle in trying to write/read data under specific circumstances.
Get the latest 10.206 from Hobbes as usual. Contained file "readusb.txt" lists the changes (as usual).

Hardware / USB drivers 10.205 released
« on: June 14, 2016, 09:26:31 pm »

I hope to have fixed the problems with USBMSD.ADD that existed up to and including 10.204.
Just try out and report back.
Available, as always, on Hobbes (, currently in "incoming" directory.

This is difficult to say:
The DDK code that we have available is not up to date. Things might have been fixed in 10.162 that are broken in the DDK code (in short: I can never trust the DDK code).
Additionally even a large file can be transferred in small chunks.
The error case is very specific.
I am on my way of getting the issue fixed. Needs more testing.

It rather depends on what bulk amounts of data you copy. I have observed this when using the WPS to copy back a whole stick's contents. In that case, the WPS (or rather, the underlying copy mechanism) tries to optimize copy speed by combining copy operations into one several large data movement operations. When that happens the driver can fail and I think this is also true for 10.162.
It occured to me when I ran a program (dskxtrt.exe) to view a fixpak file's contents on a USB stick and for one file the CRC would fail but not for the others. I suspect that in the past I had copied this file to the hard disk and now back onto the USB stick and this file has been corrupted already in the past. I cannot remember if at that time I had 10.162 in use.


Pages: 1 ... 8 9 [10] 11 12 ... 14