Recent Posts

Pages: [1] 2 3 ... 10
1
General Discussion / Re: PMfax
« Last post by Andi B. on Today at 10:40:55 am »
I've it in that order and it works. I've used serial devices on this system since ages. Both the original ones (COM1: COM2: on the standard addresses with PSCOM) and USB converter devices. Mind the PL2303 device lines which are now remed out. I needed to load it 4 times to use the up to 4 attached USB converters. Since about a year the usbcom.sys (v12.13?) from Davids package work with my devices. And usbcom.sys is now loaded only once in contrast to the PL2303 driver.

Code: [Select]
DEVICE=M:\OS2\BOOT\PSCOM.SYS /F

.....
BASEDEV=USBD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBEHCD.SYS

BASEDEV=USBHID.SYS
BASEDEV=USBKBD.SYS
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM5 /Z
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM6 /Z
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM7 /Z
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM8 /Z
REM ! DEVICE=M:\OS2\BOOT\USBCOM.SYS
DEVICE=M:\OS2\BOOT\USBCOM.SYS /M:4 /N:COM6 /Z

When I attach one or more usb converters 'mode com6:' 'mode com7:' shows me the attached working devices. I need the /Z option cause I don't use CTS/RTS/DTR/DSR (?) handshake I guess. But with a real modem attached I think you should enable hardware handshake. Anyway as long as 'mode comx:' does not show the device working you don't need to play with any higher level program. Maybe it's necessary to attach a working modem to recognize the handshake lines for that. So maybe testing with /Z first.

Btw. when I played the last time with modems probably more then a decade ago I can't get my US Robotics 56k to work again after it was laying around for 10 years or so. The even older ELSA 33k on the other hand did work with PMFAX.
2
General Discussion / Re: PMfax
« Last post by Dave Yeo on Today at 04:05:28 am »
Ideally those basedev lines should precede the regular dev lines but the config.sys is parsed multiple times with the basedev lines parsed early, by  the mini-file system, so the result is a slightly slower boot.
I always had usbcom.sys towards the end of config.sys and it worked. Remming out the com.sys lines (and vcom.sys) for testing purposes seems the important step.
3
General Discussion / Re: PMfax
« Last post by Wayne A. Smith on Today at 02:05:59 am »
OK, Neil, I've made those changes but haven't tested PMFax yet.

The one curious think I note is that these DEVICE lines separate the initial BASEDEV lines and the
BASEDEV=USBD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBHID.SYS
BASEDEV=USBKBD.SYS
BASEDEV=USBCDROM.ADD /CDS:1
BASEDEV=USBMSD.ADD /REMOVABLES:3 /FLOPPIES:1
lines. 

Is this a problem?  It would seem the the above lines ought to precede
DEVICE=C:\OS2\BOOT\USBCOM.SYS /M:3
DEVICE=C:\OS2\BOOT\USBRESMG.SYS
DEVICE=C:\OS2\BOOT\USBPRT.SYS
4
Programming / Re: ClassiCube porting thread
« Last post by Jochen Schäfer on April 27, 2024, 09:57:10 pm »
Sure, I could use that. But I just wanted to understand DART.
5
Programming / Re: OpenDOC - Source Code
« Last post by Roderick Klein on April 27, 2024, 09:08:17 pm »
Hello.

There source code of OpenDOC released to the public with the intentions to be preserved.
- https://github.com/atcurtis/OpenDoc

I have zero experience with OpenDOC, as far as I know it was a framework created by Apple and with IBM and Microsoft they tried to turn it into a standard. I think it was close source and was discontinued on 1997.

I can not even list (or remember) one software that was created with OpenDOC on any of the platforms (OS/2, MacOS 7, Windows, or AIX). I guess all software created with OpenDOC was close source, so we can not even think on bringing some of that old software and port it to OS/2 today.

But on the bright side, I think it is interesting to keep releasing the source code of old software to the public for learning purposes or even some inspiration for something new.

If someone wants to chitchat and give some some insights, personal comments, opinions, it appreciated.

Regards

I think the OS/2 port was scrapped pretty quickly. And the standard had pretty serious security issue's. I seem to recall this was part of the reason Apple dropped it.
But this is from what I recall from many years ago.

Roderick
6
General Discussion / Re: PMfax
« Last post by Wayne A. Smith on April 27, 2024, 09:02:20 pm »
OK, Neil I'll give it a try.

> On my system, I made sure that USBCOM.SYS was the first device= statement. That ensures that the USB com port comes before all the other com ports.


I'll Un-REM <USBCOM.SYS> and move it up to the top of the Device lines.  I'll also REM the <USB.COM> line.  And, of course, I'll reconnect the USB cable to the modem.


> IBM File and Print services also shares COM ports, so if you install that, it will grab a com port.


Here I'll have to dredge up my recollection of how IBM File and Print services differs from CUPS.  I have an HP DeskJet 3052a connected via a USB cable.  Opening the Properties for it shows that it utilizes a CUPS Port and, of course, is identified by a network IP Address.  The Output Port window also shows COM ports 1 through 4, and as they are not "shadowed" they don't seem to be utilized by any printer.

And RM View doesn't show that either IRQ 4 or 3 are utilized by any device.  Maybe then there ought not be any conflict?


> I didn't bother installing COM.SYS, apparently.


As said, I'll REM out <COM.SYS> and see how this goes.
7
Programming / OpenDOC - Source Code
« Last post by Martin Iturbide on April 27, 2024, 06:36:44 pm »
Hello.

There source code of OpenDOC released to the public with the intentions to be preserved.
- https://github.com/atcurtis/OpenDoc

I have zero experience with OpenDOC, as far as I know it was a framework created by Apple and with IBM and Microsoft they tried to turn it into a standard. I think it was close source and was discontinued on 1997.

I can not even list (or remember) one software that was created with OpenDOC on any of the platforms (OS/2, MacOS 7, Windows, or AIX). I guess all software created with OpenDOC was close source, so we can not even think on bringing some of that old software and port it to OS/2 today.

But on the bright side, I think it is interesting to keep releasing the source code of old software to the public for learning purposes or even some inspiration for something new.

If someone wants to chitchat and give some some insights, personal comments, opinions, it appreciated.

Regards
8
Programming / Re: SDL_mixer?
« Last post by gt on April 27, 2024, 12:09:14 pm »
Thanks Dave, I got the digi build and it seems to work, I still have some other things to fix before the game will run though.

Cheers

Garry
9
Programming / Re: ClassiCube porting thread
« Last post by KO Myung-Hun on April 27, 2024, 10:07:17 am »
Hi/2.

libkai can mixer multiple audio streams. How about consider it ?

KO Myung-Hun
10
Multimedia / Re: mplayer - just stopped working...sort of...
« Last post by KO Myung-Hun on April 27, 2024, 10:02:56 am »
Hi/2.

@Dariusz Piatkowski

3. What's the value of '2D Acceleration' ?


"YES" on my machine


Then, your system should play a movie with 2D acceleration, that is, SNAP mode. Nevertheless, if it fails, your system or SNAP driver seem not to support 1080p with 2D acceleration. In order to verify this, how about other smaller clips than 1080p, such as 720p ?

@Pete


It seems smplayer must have the capability to switch video output mode if the selected mode fails.


I've found the reason. See `-vo' section of https://mplayerhq.hu/DOCS/man/en/mplayer.1.html#VIDEO%20OUTPUT%20DRIVERS%20(MPLAYER%20ONLY).

Quote
If the list has a trailing ’,’ MPlayer will fall back on drivers not contained in the list.

SMPlayer calls MPlayer with a trailing comma(,) for vo. In this case, `-vo kva:snap,'.

That is, if kva:snap fails, then MPlayer tries other VOs. In this case, try first just `-vo kva' without any suboptions such as snap. Therefore, libkva tries to find proper modes automatically and decides to use VMAN mode. This is the feature of MPlayer not SMPlayer.

And I recommend to use `Default' or `kva(fast)' option in SMPlayer not kva(snap) et al to minimize any confusions.

Finally, for the trap I cannot reproduce here at all. If possible, provide a clip to test, please...

Thanks!
Pages: [1] 2 3 ... 10