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

2
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

3
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

4
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.

5
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.

6
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.

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

8
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)

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

10
Applications / Re: AcpiDaemon start
« on: January 28, 2024, 11:43:06 am »
Hmm...always had it in CONFIG.SYS, never tried in startup.cmd, but I am not experiencing the sort of issues you are seeing.
I understand that these are synchronization errors between different processes. They are not always manifested and only on certain hardware.

11
Applications / AcpiDaemon start
« on: January 26, 2024, 11:56:23 pm »
I have clarified an interesting pattern.
After moving acpidaemon in Startup.cmd
Code: [Select]
detach acpidaemon.exe, the system has never been hanging when loading.
At the same time, when the demon started in the config - at the first launch of Villo in 80% of cases, during a reboot of another 10%.
Also, loading without detection of the mouse ceased to occur (USB start error).
Such errors at starting regularly occurred. The system is loaded, but the USB does not function.

I use mainly OS4 core.

12
Hardware / Re: [Solved] Iomega ZIP 100 IDE
« on: December 19, 2023, 03:25:49 am »
I understood the reason and solved the problem of unstable IOMEGA ZIP 100.
It's all about an unsuccessful design. Magnetic powder flies from the disk to the printed circuit board and forms random connections.
In my case, it helped to remove dust from the printed circuit board of the device.
Unfortunately, I admit that in some cases, random compounds can cause damage to electronic components or the logic of the drive and physical damage of disks.

13
Hardware / Re: Connexant cx31993 and USB3 stack
« on: October 29, 2023, 10:17:30 pm »
I do not have a 14.204 kernel and I do not know where to get it from. But I can say that on the 14.203 kernel, I have no problems with neither USBAUDIO.SYS nor USBAUD2.SYS. I have USB audio devices of both types but of course, I only have one of each type.

There are problems with any audio driver if the WPS comes into play. If I play a sound via UNIAUD and access a USB drive, UNIAUD will immediately stop playing. For USB the situation is better in that it will not stop, but a hiccup can still be heard.
WPS is such a lousy piece of SW that it is beyond hope that it will ever become reliable. I have had many,many,many desktop freezes where the only cure was to hit the reset button and often enough, to completely turn off the PC.

USBXHCD.SYS has known problems with isochronous transfers. There is nothing that I can do about it. And it should be plain obvious that a trap in USBXHCD.SYS needs to be fixed in USBXHCD.SYS and nowhere else, regardless of if USB client drivers (like USBAUDIO.SYS / USBAUD2.SYS) are badly written or not. You should not accept that as an excuse.

Ask AN for proper USB isochronous support, in fact, ask them for proper USB audio client drivers too, just in case they answer you that "many USB client drivers are broken and do not follow specs". If they have no interest and it still is important for you, then move to another OS. It is that easy.

Sorry, Lars. I inadvertently misled you regarding the driver usbaudio.sys and core 14.204.
Everything works correctly. The error arose due to the fact that the installer added another line to Config.sys with the driver's loading and the situation with double loading of different versions of the driver arose. As a result, an error occurred when loading the system.
There was no error with the OS4 core, because there I edit the Config file with my hands.
One way or another, but now everything starts and plays in both configurations.
However, there are problems with the stability of sound and Progress bar in PM123. I am surprised to observe when playing the sound of a jerk
Progress Bar back. Perhaps this is due to the incorrect work of isosynchronous transmission.
The sound has not croaks yet, but I spent few tests without the load of the system.

14
Hardware / Re: Connexant cx31993 and USB3 stack
« on: October 29, 2023, 07:16:21 pm »
Hi Igor.

I created this Wiki page based in your HW report: https://www.os2world.com/wiki/index.php/Synaptics_Conexant_CX31993

1) For what I know USBAUDIO.SYS is for some specific USB Audio devices (USB 1.x ?) and USBAUD2.SYS for some other kind of USB Audio devices (USB 2) with other chipsets. I'm guessing that your "Synaptics Conexant CX31993" works with "USBAUD2.SYS", so we can forget about "USBAUDIO.SYS".

2) What are your specific audio tests here? Are you running an MP3 with some specific player? and what disk activity makes the audio intermittent? Are you running MIDI? Audio from the WPS?
Does your machine has an Audio device that works with UNIAUD so you can test the difference between the two devices?

3) I don't know if Lar's "USBAUD2.SYS" works with AN USB 3.0 drivers. Maybe Lars can answer that. I assuming your machine has USB 2 and USB 3 ports that are independent because of your comments.


1. Yes, right. This device is supported by the USBAUD2.Sys driver.
However, I also have other USB 2.0 devices supported by usbaudio.sys.
I already realized that I can’t use them together. At the same time, they are connected in two different ports, but even the USBRes scanner does not see them.
Separately - sees. I wonder why?

2. I use version 1.43 for the PM123 test (build 2022-08-02). As far as I understand, the player uses the DART for playing sound.
I play FLAC and mp3 files.
I also have an onboard device Uniaud, which works very well in all tests.

3. I have separate independent USB 2.0 and USB 3 controllers on my motherboard.

15
Hardware / Re: Connexant cx31993 and USB3 stack
« on: October 25, 2023, 11:43:26 pm »
I managed to play the sound from this device (with some problems).
First of all, I re -installed the USBAudio and USBWAV set from Lars on top of the installed AOS 5.1 system.
Most likely, the installer prescribed everything correctly this time.
Problems that have arisen:
1. The USBAudio.Sys driver does not load with a core 14.204. With the OS4 core, this driver is loading, but does not work.
At the same time, the USBAUD2 loads in both cases and play the sound.
2. With disk activity, malfunctions arise in the sound - it becomes intermittent, sometimes there are artifacts in the sound and in the calm
condition.
3. The device does not work in the USB3 port, the system does not see it.

All ports are checked - they work USB Flash.

Pages: [1] 2 3 ... 8