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 - Igor

Pages: [1] 2 3 ... 8
1
Networking / Re: SMB server Linux and ArcaOS (solved)
« on: Today at 01:06:27 pm »
Rings a bell about being a bug in ndpsmb.dll, I would try with https://smedley.id.au/tmp/ndpsmb-3.7.3-samba411-20220108.zip
Thank you,
it works!

2
Networking / Re: SMB server Linux and ArcaOS
« on: July 02, 2025, 09:10:18 pm »
It is log files from client.

3
Networking / Re: SMB server Linux and ArcaOS
« on: July 02, 2025, 05:49:50 pm »
What Samba client are you using?

I use client 3.07.1 from 28 Jul 2020.
From distibutive ArcaOS.

4
Networking / Re: SMB server Linux and ArcaOS
« on: July 02, 2025, 05:44:21 pm »
And did you have disabled EA support?
Yes, disabled in client driver.

5
Networking / SMB server Linux and ArcaOS
« on: July 02, 2025, 04:47:31 am »
I put an SMB server on Rapsberry.
Everything is fine. The user made, the axis comes in, logs, sees resources, reads.
But he writes strangely. File Commander begins to write a file and writes to the very end, and at the end reports that there is no rights. What?
If you create a file from the text editor, then it will be recorded and preserved.
If you copy through the PM file, it is copied.

Is it possible to fix it and how?

6
Programming / Re: Brainstorm: OS/2 on a Different Kernel
« on: June 30, 2025, 09:56:03 pm »
I want to offer you two interesting articles.
They are in Russian, but I think the Google translate will cope.
http://ru2.halfos.ru/core/articles/core003.html
http://ru2.halfos.ru/core/articles/core001.html

7
Hardware / Re: USBCOM big problem
« on: February 04, 2025, 03:50:34 pm »
Thank you for the comment. I also managed to configure PL2303, but only with the driver Lars Erdmann 10.250.
This is enough for me. But I am ready to check the performance of other drivers and chips.
Unfortunately, I never achieved the stable operation of Pscom.sys drivers in my configuration.
While the PL2303 decision suits me.

8
Hardware / Re: USBCOM big problem
« on: January 16, 2025, 04:19:45 pm »
For the "Future Technology" device you should try USBSER.SYS instead of USBCOM.SYS.

I checked this configuration. Unfortunately, this does not work.
Code: [Select]
DEVICE=C:\OS2\BOOT\USBSER.SYS /V /Z /N:COM5
The system say:
SYS1620: The COM port specified is not installed.

lsusb:
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC

9
Hardware / Re: USBCOM big problem
« on: January 06, 2025, 09:11:22 pm »
Thank you very much, ALL!

I installed USBCOM from the USB 10.250 package from Lars Erdmann with /Z key
It worked.
The USBCOM 12.16 driver from Arca Noae does not see my device:
Bus 001 Device 004: ID 067b: 2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Action Ma-8910p
Also, they are not recognized any of the drivers and do not work:
Bus 001 Device 005: ID 0403: 6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 005: ID 1A86: 7523 Qinheng Electronics CH340 Serial Converter

10
Hardware / USBCOM big problem
« on: January 06, 2025, 12:17:51 am »
I spent some money (thanks to the Chinese industry) and a lot of time.
It turned out that the work of USBCOM is seriously broken.
Of the three different devices that I checked, only PL2303 is recognized and only on USB16 drivers.
But he does not work either.

PL2303 in USB32 is not identified by the system. Checked with USBCOM and USBSER drivers.
If you put the driver from USB16, then you can configure the port.
However, the device only works on receiving information.
Sending does not work.
If someone works for someone, please indicate which version of the drivers this can be launched.

11
Hardware / Re: CH340 serial
« on: December 24, 2024, 08:03:58 pm »
The usbcom driver supports a lot of devices already. What is your output of this.

Device=C:\os2\boot\usbcom.sys /v

If nothing is found, maybe you need a different USB serial port converter?

Also, even the newest desktop computers still seem to have serial ports.

Of course, the USBCOM.Sys driver is installed and launched.
And, alas, on my motherboard there is not even a detachment for serial port. And there is no chip either.
I have already ordered another converter of the outdated model. If nothing can be done, I will try with him.

12
Hardware / Re: CH340 serial
« on: December 24, 2024, 07:54:41 pm »
Hello

Just in case I had a little experience with this device: Prolifc PL2303 USB 2.0 to COM - 067b:2303
https://www.os2world.com/wiki/index.php?title=Prolifc_PL2303_USB_2.0_to_COM

I used USBCOM.SYS.
My testing was very light, I no longer have any serial device to try.

Regards
I use Prolifc PL2303 USB 2.0 to COM and it works (partially). But I can’t connect this to Arduino.
Perhaps he gives out 5 volt COM and this solves the problem.
I will check it soon.

I ordered ProLIFC PL2303 converter to com-TTL and expect delivery. Perhaps this will work.

However, CН340 is much more common and affordable.

13
Hardware / Re: CH340 serial
« on: December 23, 2024, 10:48:12 pm »
Hi Igor,

What are you using that requires a com port?  I haven't used one for the last 10 years so am interested in your usage.
62 / 5 000
I use GSM module. I also plan to use Arduino.

14
Hardware / CH340 serial
« on: December 23, 2024, 07:27:29 pm »
Help me, please. Add support for this device to the USBCOM driver.
Code: [Select]
Bus 001 Device 004: ID 1a86:7523 QinHeng Electronics CH340 serial converter
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x1a86 QinHeng Electronics
  idProduct          0x7523 CH340 serial converter
  bcdDevice            2.64
  iManufacturer           0
  iProduct                2 USB Serial
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               98mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      1
      bInterfaceProtocol      2
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0020  1x 32 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0020  1x 32 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               1
Device Status:     0x0000
  (Bus Powered)

15
Programming / Re: Qt6 Application Testing
« on: October 03, 2024, 11:32:48 pm »

Pages: [1] 2 3 ... 8