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 ... 5
1
Hardware / Re: USB32 USBMSD problem of re-read diskette
« on: January 24, 2023, 04:48:08 pm »
Of the known problems of USB devices, I only faced with the problem of electrical contact in the connection. David pointed to me a large number of USB errors and I really found bad contact in the connection. Windows reacted to him with an unstable definition of a floppy disc drive. I eliminated poor contact and now the equipment is determined stably.

When loading the driver, he gives a command to rotate the drive engine only if the diskette is inserted. Your driver performs this operation regardless of the presence of a diskette. This is a significant difference at the time of loading.
Subsequently, the AN driver does not track the fact that the diskette is removed and does not conduct the "Drive Ready" check when addressing the diskette.
If timeouts affect the work of equipment, it would be the best decision to give the user the number of repetitions, for example, through the command line key.

2
Hardware / Re: USB32 USBMSD problem of re-read diskette
« on: January 23, 2023, 10:35:56 pm »
I can say about the timer that I know that the AN software contains an error (still?) Because of which we have a crutch SET NSPR_OS2_NO_Hires_Timer=1 in the config.sys file.
Nevertheless, I tried to run this set of drivers in the system where this error is eliminated. This did not bring a positive result and the timer error and the drivers mistake are different.
However, of course, the proper processing of equipment timouts is a very important thing. And I want to note that your software, as well as Windows, successfully copes with this.

3
Hardware / Re: USB32 USBMSD problem of re-read diskette
« on: January 23, 2023, 03:24:41 pm »

Code: [Select]
2.7.4  Some USB floppy disk drives (i.e. IBM USB Portable Diskette Drive,
       ASM P/N 06P5222, FRU P/N 06P5223) are known to become inaccessible
       if there was no diskette in the drive during boot/attach time.
       To avoid this, a diskette should remain in the drive while the system
       is booting or while the drive is being attached.
 

Are you experiencing the effects described in 2.7.4 ?
 

Not certainly in that way. Even if the diskette was inserted at the time of loading the system does not work correctly when changing the diskette.
If the diskette is replaced by the driver AN does not notice this and when trying to record it saves on the new FAT disk with the one that was in the drive at the time of boot.
Additionally, I want to indicate that I use exclusively USB2.0 to connect a USB drive.

4
Hardware / Re: USB32 USBMSD problem of re-read diskette
« on: January 22, 2023, 03:11:17 pm »
I assume that with the "USBMSD driver of the 16-bit version" you mean the USBMSD.ADD from my USB driver set.
I spoke incorrectly about the 16-bit version. I really meant your version of the driver. The bit has nothing to do with this.

5
Hardware / Re: USB32 USBMSD problem of re-read diskette
« on: January 22, 2023, 03:07:32 pm »
Hi, Lewis!

Hi, guys...
...
I fail to see what is wrong, sorry.

I completely believe that you do not see what is wrong. I understand perfectly well that everything works for you and does not question your messages.

However, I have a device that works with Windows 7, works with another driver and does not work with your driver.

I propose to make tests for your instructions for you, send additional logs.

P.S. A long time ago (more than 20 years ago) in a distant galaxy... I worked as a programmer in large projects of American companies. If I answered the customer to the claim that I have the software I developed work properly, I would have lost my job :(

6
Hardware / USB32 USBMSD problem of re-read diskette
« on: January 21, 2023, 02:43:35 pm »
The problem is partially solved by replacing the USBMSD driver with a similar one of the 16-bit version. At the same time, USB2 disk2 work and do not operate USB3 discs.
Provided to replace the diskette in the drive is determined and re-read correctly and all functions also work correctly - recording, reading, formatting, which unambiguously indicates a problem in the USBMSD driver from AN.
To my regret, AN, after my appeal, did not show interest in solving the problem, despite the ticket issued according to their requirements. They referred to the fact that everything works for them.

7
Hardware / Re: PSCOM.SYS problem
« on: December 22, 2022, 10:08:34 pm »
Blonde Guy has some notes on Serial Cards on eComstation.

It say a.o. and I quote "The PSCOM.SYS driver supports the /F option, and along with specifying the built-in motherboard ports makes this and a lot of other serial cards work."

Reading the notes I think you will have just to specify:

DEVICE=C:\OS2\BOOT\PSCOM.SYS /F /V (1,3F8,4) (2,2F8,3)

even when there are no built-in motherboard ports.
Thank you so much. That helped.
However, I received two fake comports with numbers 1 and 2. Real comports took numbers 3 and 4. The attempt to change them failed. As I understand it, this is the only way to use external ports.

Among other things, it goes only with the original core. The core of OS4 does not find external comports.

8
Hardware / Re: PSCOM.SYS problem
« on: December 19, 2022, 12:14:46 pm »
Try using two 'device=' lines: one with (1,A010,21) /V and one with (2,A000,23) /V

device=c:\os2\boot\pscom.sys (1,A010,21) /V
device=c:\os2\boot\pscom.sys (2,A000,23) /V

It is very strange to me. Previously, I have never seen two lines when loading the drivers of comments.
When trying to add two lines, the load stops on the first line with the message SYS1201 and Press Enter to continue.

After pressing the Enter, the system works even more strange. The next line loads 2 ports, but the interruptions are not specified correctly and the UART is different for different ports!

DEVICE=C:\OS2\BOOT\PSCOM.SYS (1,A010,21) /F /V
COM.SYS: Asynchronous Communications Driver v1.21
COM.SYS:   Addr     IRQ   Sharing    UART   FIFO

DEVICE=C:\OS2\BOOT\PSCOM.SYS (2,A000,23) /F /V
COM.SYS: Asynchronous Communications Driver v1.21
COM.SYS:   Addr     IRQ   Sharing    UART   FIFO
COM1:    0xA010      3    No    16550    16
COM2:    0xA000      23    No    16450    1


UPD
In the case of two lines after loading, the core is 14.203 when contacting comports, it goes into a trap.
The nucleus of the OS4 remains stable and even allows you to set the speed of 115200 for the port, where UART 16550 is determined.
Further tests were not carried out. It seems to me that still somewhere there is a mistake when loading drivers.

9
Hardware / PSCOM.SYS problem
« on: December 15, 2022, 10:22:19 pm »
When loading the system, I see:

DEVICE=C:\OS2\BOOT\PSCOM.SYS (1,A010,21) (2,A000,23) /V

COM.SYS: Asynchronous Communications Driver v1.21
COM.SYS:   Addr     IRQ   Sharing    UART   FIFO
COM2:    0xA000      23    No    16450    1

The parameter is determined here UART: 16450
This is not true.

From output pci.exe:
 Bus 6 (PCI Express), Device Number 0, Device Function 0
 Vendor 125Bh Asix Electronics Corporation
 Device 9100h Unknown
 Command 0007h (I/O Access, Memory Access, BusMaster)
 Status 0010h (Has Capabilities List, Fast Timing)
 Revision 00h, Header Type 80h, Bus Latency Timer 00h
 Self test 00h (Self test not supported)
 Cache line size 64 Bytes (16 DWords)
 PCI Class Simple Communication, type Serial - 16550
 Subsystem ID 1000A000h Unknown
 Subsystem Vendor A000h Unknown
 Address 0 is an I/O Port : A010h
 Address 1 is a Memory Address (0-4GiB) : F0803000h
 Address 2 is not present or not configured!
 Address 3 is not present or not configured!
 Address 4 is not present or not configured!
 Address 5 is a Memory Address (0-4GiB) : F0802000h
 System IRQ 21, INT# A

 Bus 6 (PCI Express), Device Number 0, Device Function 1
 Vendor 125Bh Asix Electronics Corporation
 Device 9100h Unknown
 Command 0007h (I/O Access, Memory Access, BusMaster)
 Status 0010h (Has Capabilities List, Fast Timing)
 Revision 00h, Header Type 80h, Bus Latency Timer 00h
 Self test 00h (Self test not supported)
 Cache line size 64 Bytes (16 DWords)
 PCI Class Simple Communication, type Serial - 16550
 Subsystem ID 1000A000h Unknown
 Subsystem Vendor A000h Unknown
 Address 0 is an I/O Port : A000h..A007h
 Address 1 is a Memory Address (0-4GiB) : F0801000h
 Address 2 is not present or not configured!
 Address 3 is not present or not configured!
 Address 4 is not present or not configured!
 Address 5 is a Memory Address (0-4GiB) : F0800000h
 System IRQ 23, INT# B

How to make two comports with correct parameters (UART: 16550) be determined?

10
Programming / Re: Building Qt5
« on: November 22, 2022, 03:57:00 pm »
Dear builders Qt5 please turn off the AVX (and AVX2) code. Due to its presence, the browser does not display the pages. And it is impossible to use libraries. I don’t understand why this code is included if it does not work on OS/2 correctly?

11
Hardware / Re: Iomega ZIP 100 IDE
« on: November 13, 2022, 09:53:58 pm »
Solved!

1. Install ZIP100 as a hard drive (not like a floppy disk).
2. Install Danis driver:
BASEDEV=DANIS506.ADD /!BIOS /A:1 /I /V
BASEDEV=DANIATAP.FLT /EJ /V
3. After installing the disk in the wildcard, use the LVM command - lvm /rediscoverprm
4. A disk letter will appear and you can work with it
5. Before extracting the disk, use the command - eject drive:

Thank you all for participating in solving the problem!

12
Applications / Re: Test build of dooble with qt5
« on: May 02, 2022, 03:03:34 pm »
Hi!

Please create an assembly QT5 without support of the ABX. Due to the presence of ABX, an error occurs and the browser falls into the trap.

13
Hardware / Re: WebCam Driver Question
« on: March 27, 2022, 11:35:54 pm »
May be you can give a try recording video+sound using ffmpeg and check if the sound problem exist too !

ffmpeg correctly records video with sound over 2 minutes. This is amazing.

14
Hardware / Re: WebCam Driver Question
« on: March 26, 2022, 10:24:27 pm »
Hi Remy,

What did you before having sound issue ?
Did you try your webcam with all other programs stopped ?
 
(I've got the symptom you describe when audio driver has to handle mutiple sources)
ex: Out of webcam + pm123 or pm123 + youtube or wps playing audio + other audio programs...

Before I got the problem with the sound, I tried several times to start the video server program, because it starts correctly for me only on the third try. And always on the third try.

No other sound programs were active during the test. The only thing I can notice is the system sounds when the camera is connected. However, in this case, I did not disconnect the camera and did not reconnect it. It has been attached before.

15
Hardware / Re: WebCam Driver Question
« on: March 25, 2022, 04:34:23 pm »
Hi Wim,

Thank you. I updated the programs to the version you specified.
The program wmaudio outputs sound from 30 seconds to 1 minute. Then the last fragment is repeated forever. After restarting the program wmaudio, the sound is restored and works for some time. Not more than a minute. The server webcam.exe does not need to be restarted. It works correctly.

Pages: [1] 2 3 ... 5