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 ... 74 75 [76] 77 78 ... 82
Multimedia / Re: USB Audio
« on: March 01, 2017, 10:29:48 am »
Hi David,

that is obviously possible but not a good solution in general. We need a sound subsystem that is able to deal with different sound formats and also with different sample rates. You don't want the user to convert his sound files to the very few formats that OS/2 and the Audio HW understand.
The MMIO mechanism deals with the conversion between different sound formats (say: MPG to WAV), therefore that is already covered.
In addition, we also need to deal with different sample rates which is not yet covered.

Multimedia / Re: USB Audio
« on: February 28, 2017, 03:08:50 pm »
I also tried some cheapo chinese USB Audio stick (which broke after about 2 weeks of use).
In general any USB Audio device should work but manufacturers are free to support dedicated sample rates.
They will almost always support 44.1 kHz Stereo because it is so common, then the good stuff will also support 48 kHz Stereo (the Terratec Aureon does) because that is the sample rate for professional sound equipment (as far as I know).

What they will normally not support is the 22,05 kHz and 11,025 kHz sound files that OS/2 comes with. For that a sample rate converter (in SW) would be needed and "fitted" into OS/2 MMPM subsystem (I think that is possible but it is work and the data amount would double or quadruple respectively and I don't know how to increase a sound buffer in size).

That's also the reason why those OS/2 Sound files sound so funny if you play them ...

Multimedia / Re: USB Audio
« on: February 26, 2017, 10:17:40 pm »
I myself am testing with a Terratec Aureon Dual USB.
To make it short: for certain technical reasons only 44.1 kHz sampling rate will do.

Setup & Installation / Re: Question about OS/2 3.5 floppy image files
« on: February 25, 2017, 07:15:24 am »
It's the XDF floppy format. It allows more data on a 3.5 inch floppy. OS/2 comes with a filter driver XDFFLOPPY.FLT that is able to access these floppy disks. You should try and get a CD-ROM version of Warp 4 instead of using floppies ...

By the way: OS/2 has a tool to create 3.5 inch XDF floppies from the floppy images (image.exe or savedskf.exe should do).

Another issue: XDF formatted floppy disks CANNOT be read when inserted into a USB floppy drive. Only legacy/built-in floppy drives will do.

Programming / Re: Open watcom lib question
« on: February 20, 2017, 04:14:54 am »
For static libraries, wlib should be able to give you a listing of the OBJ files contained in the library plus the names of the routines contained in those OBJ files. That should give enough of a clue.

Storage / Re: Possible causes of TRAP000e in OS2LVM?
« on: February 17, 2017, 10:21:13 pm »
A "compatibility" volume cannot span drives.

Storage / Re: Possible causes of TRAP000e in OS2LVM?
« on: February 17, 2017, 04:11:36 pm »
I suppose that Partition type 0x7 is "compatibility Volume" and Partition type 0x35 is "LVM volume".
This is only relevant for JFS as only JFS can be either "compatibility" or "LVM" volume (everything else needs to be "compatibility"):

A "compatibility" and also a "LVM" JFS volume has a DLAT sector as the last sector of the first track of a partition. It saves stuff like disk Name, Partition Name and volume Name and drive letter.

In addition , a "LVM" JFS volume also has a "LVM signature area (BBR)" right inside the JFS Partition that contains "DriveLink" and "BadBlock" Information. Obviously, the DriveLink info is needed if an "LVM" volume spans multiple partitions, possibly across multiple physical drives. It will allow LVM to figure out what partitions on what drives belong to that one JFS volume.
"BadBlock" adds additional functionality to remember which sector/block was broken so that the filesystem can avoid using that sector/block. I don't think that is too valuable as modern hard disks do a bad sector remapping in HW, completely transparent to any SW.
Thinking about the fact that the DLAT sector saves the drive letter, I would say there is some cross-dependency between the BBR and the DLAT sector (the DLAT sector needs to list the very same drive letter for all partitions belonging to the same volume).

Taken from here:

That said I'd suspect that there is some problem with the BBR and/or the dependency to the DLAT sector.
Why are you using "LVM" volumes anyway ? They cannot be booted from and they have no added benefit unless you intend to span a volume across multiple partitions/drives. With today's large disks (and "home user" requirements) I cannot see why you would want to do that.

Applications / Re: Blue Lion Beta testing...
« on: February 11, 2017, 02:07:00 pm »
I am not surprised that a USB floppy drive did not work. USBMSD. ADD
 version 10.162,latest version from IBM is not working well. As a test you can download my latest usbdrv215. zip from I have tested with a Mitsumi floppy drive.
Of course that will not help you with your boot CD.

Hardware / Re: USB drivers 10.215 are in the works - done
« on: February 09, 2017, 09:09:37 am »
As usual find on Hobbes:

currently in the incoming directory /pub/incoming, moving to /pub/os2/system/drivers/misc.
Please read the enclosed readusb.txt for the changes. All changes are related to USBMSD.ADD.
I tried to improve peaceful coexistence of Windows,DFSee and OS/2.


Hardware / USB drivers 10.215 are in the works
« on: February 02, 2017, 09:22:16 pm »
I had to do numerous fixes to USBMSD.ADD regarding geometry computation in order to make it more compatible to Windows and DFSee. I also had to add recomputation of geometry in case the media is ejected and exchanged but the device stays attached (example: SD card reader).
This required substantial changes. Unfortunately 10.214 is suffering from some major problems and I suggest to roll back to say 10.210 and wait for the next version :-)


Hardware / Re: USB drivers 10.213 released
« on: December 25, 2016, 02:04:54 pm »
Sorry but all of what you describe has nothing or very little to do with the USB drivers.

1) first you screwed up your system by removing MULTIPT.EXE where you don't know what that file is good for. Suffice it to say that it is loaded by some WPS class, very likely WPMouse, and therefore it's certainly a very bad idea to just kill it or remove it because you don't know what the affected WPS class will do if that daemon executable is not running.

2) then you fumbled around with your WIFI and think it has some repercussion on the system even though you didn't even install a driver for that device. The only thing that could go wrong is that your WIFI HW is issuing spurious interrupts and if no driver handles that (of course no driver will do as there is no WIFI driver to specifically handle that interrupt) OS/2 will eventually shut down the interrupt for good and any device using the same (shared) interrupt would cease working. Then the only advice can be to turn off WIFI for good. And you know that you have crappy HW.

3) you say that all of a sudden you can select the XView menu entry. However, USBMOUSE.SYS only knows about mouse clicks and mouse pointer position info. It does not give a bit or care on what you click on.

From all those weird issues you have I would think that your OS2.INI and OS2SYS.INI are completely screwed up and need a cleanup. You will never solve this problem by mucking around with drivers, no matter what drivers you use.
Another likely culprit is your legacy mouse driver which is either AMOUSE.SYS or MOUSE.SYS. I suggest you (re)install the latest AMOUSE (if you have an ArcaNoae subscription). That's because USBMOUSE.SYS needs a legacy mouse driver to interact with. In the end, it's the legacy mouse driver that reports mouse clicks and pointer position to the operating system.


Hardware / USB drivers 10.213 released
« on: December 22, 2016, 07:11:20 pm »
Please skip versions 10.211 and 10.212. All changes in "readusb.txt", as usual.
Find on Hobbes.

Setup & Installation / Re: Help installing old software
« on: December 17, 2016, 08:19:47 pm »
Here are some notes I have written for myself for installation of VAC 3.6.5. I am sure that you can "translate" this info to your specific installation needs. The idea is to not only use the CID response file but also dynamically update the installation path(s). The drive and path variables "InstDrv1","InstDrv2","InstDir1","InstDir2" are specific to the base response file. You will need to find these variables for your specific product:

C.  Invoking installation directly through an installation object
    I have reworked and modified PORTAPAK.RSP (on your VAC 3.6.5 installation CD-ROM) so that it can also be used
    to create an installation object.
    You create an installation object via CLIFI.EXE (it is installed on every OS/2 machine) once you have burned a new
    CD-ROM from the original CD-ROM and these patches.

    For what follows, assume this:
    a.) your CD-ROM is drive V:
    b.) you want VAC 3.6.5 installed to drive D: and directory IBMC365
    c.) you want the OS/2 toolkit installed to drive E: and directory TOOLKIT

    echo /O:ROOT >parms.txt
    echo /SET:InstDrv1=D: >> parms.txt
    echo /SET:InstDrv2=E: >> parms.txt
    echo /SET:InstDir1=IBMC365 >> parms.txt
    echo /SET:InstDir2=TOOLKIT >> parms.txt
    echo /SET:PackagedFromPath=V:\COMPILER >> parms.txt
    echo /SET:ImageMediaPath=V:\COMPILER >>parms.txt
    echo /R:V:\COMPILER\PORTAPAK.RSP >>parms.txt
    echo /S:V:\COMPILER >>parms.txt

    clifi.exe /A:B /F:"<WP_DESKTOP>" /PARMS:parms.txt

    The installation object is created on your desktop. If you open it you can select/deselect the individual features to
    install. After installation you can either delete the object or keep it around somewhere if you want to install later on.
    During installation, you are asked to specify the "Source Media": just reenter the path: V:\COMPILER

Setup & Installation / Re: Help installing old software
« on: December 17, 2016, 02:57:29 pm »
Part 1:
Part 2:

I have successfully installed IBM VAC 3.65 and VAC 4.00 with these instructions without use of Netscape.


Applications / Re: cups and usb printers
« on: December 09, 2016, 12:49:15 am »
Thanks !

Pages: 1 ... 74 75 [76] 77 78 ... 82