Recent Posts

Pages: [1] 2 3 ... 10
1
Applications / Re: LarsenCommander - new test version
« Last post by Andi B. on Today at 07:44:28 pm »
Speed tests with SSDs vary on my system. I've tested with -
Samsung SSD 850 PRO 256GB
Samsung SSD 870 EVO 2TB
Samsung SSD 860 QVO 1TB
Crucial CT500MX500SSD1

It's sometimes not clear why copying from one SSD to another is faster with some setting while it's a bit slower with another target or source. I ever thought the maximum throughput you can get with an OS/2 system is copy from CLI cause a GUI program with progress indicator will always lower performance (the progress indicator needs to be update while CLI copy only waits for disk to accept new data, CLI does not even check CTRL-C). To my findings this is still true with disks although now LCMD comes very close to CLI. But in the last months I've even found scenarios where copying with LCMD is much faster than CLI copy (which TTBOMK uses 4k fixed buffer).

You may think copying with LCMD should be faster when not much else is running at the same time. But I've even scenarios where copying is actually a bit faster when LCMD lost the focus and some other heavy task are running. Once I even need a reboot to get the copy speed from/to a specific source/target to the level I'm used to. It was about 20% slower for unknown reason before.

Bottom line is it needs a lot of tests to get reproducible results. In most scenarios you can't get the same full speed with LCMD than with CLI but we are very close to that. Facts based on my tests for single big files are -
- Samba is way slower than ftp (more than 1,5 times slower here), both via netdrive *)
- for SSDs and harddisks LCMD is not exactly as fast als CLI copy but very close to it
- Ramdisk is way slower than SSD or harddisks (JFS is faster than HPFS but still 3 times slower)
- Peak values may be very high cause of SSD (and JFS) cache

*) Samba is way faster than FTP with a lot of small files I think because of it's directory caching which FTP is missing
2
Applications / Re: LarsenCommander - new test version
« Last post by Dariusz Piatkowski on Today at 06:05:07 pm »
Hi Andi,
...
File xfer performance wise, here are the results for movement of a test 800M AVI file:

1) from SAMBA share to ramdisk
OLD:  Peak=58,270K, Avg=43,550K
NEW: Peak=56,220K, Avg=46,516K

...so I'm thinking this is more about being network bound (1G LAN, but of course the Samba share box - NAS is the limitation here)

2) from ramdisk to SSD drive (Samsung 860 Evo, SATA)
OLD:  Peak= 82,788K, Avg=  45,545K
NEW: Peak=310,118K, Avg=220,910K
...

Repeat of the same performance tests for the newest version:

1) from SAMBA share to ramdisk
OLD: Peak=56,220K, Avg=46,516K
NEW: Peak=51,367K, Avg=45,832K

2) from ramdisk to SSD drive (Samsung 860 Evo, SATA)
OLD: Peak=310,118K, Avg=220,910K
NEW: Peak=503,901K, Avg=311,825K

...which naturally made my eyeballs nearly pop out b/c let's be honest, my SSD isn't that fast!!!

So a re-do produced the following NEW:
NEW: Peak=430,674K, Avg=183,007K

...which while still pretty high for a Peak, I suspect this has everything to do with my crazy ass JFS cache, which is 1G in size.

Couple more tests later though the higher Peak appears to be sustained, so perhaps there is a little bit more improvement here Andi!!!?

Thank you again!
3
General Discussion / Re: PMfax
« Last post by Neil Waldhauer on Today at 03:21:41 pm »
The serial device drivers, USB, IBMCOM and COM all work fine in any position. All the position in Config.Sys does is determine which com port COM1, COM2, etc. is assigned to which device.

RMVIEW is voluntary, so if a device driver doesn't participate, RMVIEW will not show it.

BASEDEV statements are processed in an earlier pass. We've presented the process at Warpstock several times. They have to be correct, but their order compared to DEVICE= statements is not relevant.
4
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.
5
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.
6
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
7
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.
8
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
9
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.
10
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
Pages: [1] 2 3 ... 10