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 ... 5 6 [7] 8
91
Hardware / Re: DOS session does not work. Motherboard Asrock B85
« on: December 01, 2020, 01:34:40 pm »
Try to disable dos=umb

set
DOS=HIGH,NOUMB
in config.sys

and check in vdm settings of each dos session shotcut , incl win/os2 sessions

Ps dos+emm386 runs on this motherboard with
device=c:\dos\emm386.exe  /nomovexbda noems ram
Many big thanks!
Indeed, after disabling the UMB, everything worked!
Problem solved!

92
Hardware / Re: DOS session does not work. Motherboard Asrock B85
« on: November 25, 2020, 02:40:54 pm »
Are you with UEFI support enabled and with a latest ArcaOS on this machine. As far as I understood there were some changes/updated on the drivers to run VDM (Virtual DOS) on UEFI mode. Maybe the issue goes on that side.

If the issue is happening on ArcaOS 5.0.6 with UEFI mode, I think it will be good to open a ticket.

Okay, I'll update the system to ArcaOS in the future. Hope there will be Christmas discounts.
Or is it better to wait for version 5.1?

93
Hardware / [Resolved] DOS session does not work. Motherboard Asrock B85
« on: November 19, 2020, 10:31:02 pm »
After starting a full-screen DOS session, a screen with "C:\" appears as in the picture (see attachment).
After pressing any key, the screen closes and the popuplog.os2 is formed.
Code: [Select]
19.11.2020  22:58:30  SYS   0  PID 0038  TID 0001  Slot 00A7
C:\OS2\PMSHELL.EXE
16D7FFFF
EEF3FFFF
P1=FB92E113  P2=2F0CE14B  P3=FF62F000  P4=FEE2E10E
EAX=00006247  EBX=0000FFFF  ECX=0000E118  EDX=0000FEC2
ESI=000091C3  EDI=00001240
DS=0348  DSACC=1092  DSLIM=00010FFF
ES=FFFF  ESACC=0000  ESLIM=00000000
FS=0000  FSACC=0000  FSLIM=00000000
GS=0000  GSACC=0000  GSLIM=00000000
CS:EIP=EB00:00000313  CSACC=0000  CSLIM=00000000
SS:ESP=FFFF:00000A74  SSACC=0000  SSLIM=00000000
EBP=00000A6A  FLG=000A6212

What can be done?
Motherboard Asrock B85. Bios UEFI and compatible.

94
Hardware / Re: USB 12.07 stack - Audio Clicking Issue
« on: August 24, 2020, 07:16:03 pm »
Which usb driver do you load :
BASEDEV=USBXHCD.SYS  ?
BASEDEV=USBEHCD.SYS  ?

Did you a try loading USBEHCD only ?
Regards
I not use USBXHCD. USBUHCD and USBEHCD only.

95
Hardware / Re: USB 12.07 stack - Audio Clicking Issue
« on: August 24, 2020, 07:13:46 pm »
Does USB audio also properly work with the 11.17 EHCI driver (or the 11.17 driver set in its entirety) ? If yes, that should give David some good hint of what to change.
I have installed and tested version 11.17. The version 11.17 stack works correctly and the sound is not interrupted or spoiled. The problem is only in version 12.xx.

96
Hardware / Re: USB 12.07 stack - Audio Clicking Issue
« on: August 20, 2020, 02:46:28 pm »
AFAIK, the original IBM USB Audio driver has never had any significant updates - v12.07 is pretty much the same as every other version back to IBM's v10.something. Since AN now includes Lars/Wim's drivers in ArcaOS, I wouldn't expect any new development. Why bother with the IBM driver when the alternative is clearly better?
Both drivers (from Lars and from Ark) behave the same with the 12.07 stack. Both work with clicks. This is not a sound driver problem, but the USB ECHI driver.

97
Hardware / USB 12.07 stack - Audio Clicking Issue
« on: August 19, 2020, 01:39:10 pm »
Version 12.07 looks much better. However, the problem with the quality of USB sound has not been fully resolved.
The new version does not lose data anymore, but the sound is choppy. It's like listening to a clipped vinyl record with clicks. Obviously, by the time the playback of the data packet is completed, the next one does not have time to arrive.
Most likely this is a problem in the ECHI driver that they tried to solve. I advise developers to rely on the experience of the 16-bit version. These problems are not there...

98
Hardware / Re: USB 3 - ArcaOS - Hardware Reports
« on: June 20, 2020, 02:16:56 pm »
Hello Igor
You can try to kill ACPIDAEMON.exe with top.exe or similar tool. Or rem in config.sys acpidaemon.exe. And test.
Saludos
Thank you for the idea. I tried - it didn’t work. I updated ADCI to the latest version 3.23.13 and stopped the ACPIDAEMON.exe. But the sound is still torn when loading multiple processors.

99
Applications / Re: OS/4 (non technical issues)
« on: June 19, 2020, 01:08:55 pm »
Hi Igor,

can you patch the OS/4 kernel to revision 14.x and see if then the USB AN 12.x drivers will work ?

I am aware of the fact that it is not AN's job to support a kernel they don't provide (so: as an OS/4 kernel user, you are on your own, it's all your problem, if it works, then fine, if it does not, too bad) but I still see no technical limitation to use the AN drivers with an OS/4 kernel.

Note: In my own USB drivers (namely: USBD.SYS) I had added some small piece code to do something specific for the OS/4 kernel but keeping compatibility with the OS/2 and AN kernels. As far as I know my USB drivers still work on the OS/2, AN and OS/4 kernels and in fact I normally use the OS/2 kernel but occasionally I boot into the OS/4 kernel, none of either is a problem.

I already tried it, but did not get a positive result. USB3 drivers check not only this line, but something else. I am not an OS / 4 developer, I do not have source codes and cannot change anything in the kernel except for text strings.

I express my deep gratitude to you for your USB drivers that work perfectly with OS / 2 in OS / 4 kernels.

100
Applications / Re: OS/4 (non technical issues)
« on: June 19, 2020, 10:45:51 am »
Interesting. I thought they had gone for the KEE version,
This is also possible. I have yet analyzed their code. My research was done on the lines of text in their driver and their changes from version to version.

101
Applications / Re: OS/4 (non technical issues)
« on: June 19, 2020, 10:22:19 am »
I conducted a study and found out that the new USB3 drivers check the line "Internal revision" and if they find something other than "14.", they refuse to boot without diagnostic messages. In OS / 4 kernel, revision is 15.
The test was conducted as follows: at the IBM core, the revision number was replaced for research purposes. Drivers stopped loading without any diagnostic messages.

It also turned out that this is not the only test that is present in the drivers of version 12.05+, and was missing earlier.

102
Applications / Re: OS/4 (non technical issues)
« on: June 18, 2020, 07:03:02 pm »
Is there any evidence that AN prohibits the drivers to run on OS/4 kernel on purpose? Or is this just a side effect cause OS/4 kernel is not as compatible as it should be?

Guess OS/4 kernel developers have to debug the reason to shed some light on this.
There is no direct evidence and I sincerely hope that this is a mistake that will be fixed sooner or later.
The OS / 4 team carefully monitors compatibility with the OS / 2 kernel, but it’s hard to keep track of undocumented features if they were or weren’t brought to the core of the system by Arca Noae.

103
Applications / Re: OS/4 (non technical issues)
« on: June 18, 2020, 04:34:20 pm »
I have the only request to programmers and Arca Noae's management - do not make deliberate changes to the code that interfere with the launch and operation of drivers on the OS / 4 kernel. I really hope that the community will support my request.
This will help develop research projects and will allow, among other things, to sell drivers to users of these projects. You chop a tree branch on which you sit.

I also inform you that I regularly pay for a driver subscription and so far everything has been fine with me. If it turns out that driver inoperability is intentional destructive actions, I will reconsider my attitude to paying for products and most likely refuse.
Naturally, no one can require Arca Noae to support their drivers in an environment that they did not choose.
But it’s also natural to require the product to have no specially made incompatibility.

104
Applications / Re: OS/4 (non technical issues)
« on: June 17, 2020, 10:46:09 am »
Quote
Use OS/4 if you like, but don't expect Arca Noae to even recognize that it exists. They just can't take the chance that IBM will take them to court.
Can a deliberate introduction of an algorithm into the code be considered due to which some software refuses to work on the OS / 4 kernel by recognition of its existence? ???

I do not suggest Arca to deal with the OS / 4 kernel. People are already doing it and everything is fine there. However, I believe that community efforts should be aimed at preventing a developer war.
OS / 4 Group is actually working on the development of Arca Noae business. And he does this without receiving financial benefits.

105
Applications / Re: OS/4 (non technical issues)
« on: June 16, 2020, 10:33:04 pm »
I want to note that I am an official user of drivers from Arca Noae. I paid them for a subscription and expect them to work. In the meantime, even in OS / 2 with the official kernel, they are not quite operational.
I see no reason to divide the land in our cemetery. Actually OS / 2 has not been supported for a long time and is rather not alive. However, both Arca Noae and the OS / 4 team are involved in the development of the system. Both of them did a lot for the system to develop. And now it’s very important to find a way for the various components supported by different developers to work together.
The OS / 4 kernel has been seriously updated; significant errors have been removed from it; it is significantly faster than the OS / 2 kernel. In the OS / 4 kernel, virtual machines run significantly faster. And in some modern systems, the OS / 2 kernel does not work at all and the system starts only with OS / 4. Not only that, some Arca Noae drivers do not work on the OS / 2 kernel, but they work on OS / 4. And most importantly, the OS / 4 kernel is supported and updated regularly.
If we abandon development that ensures progress, then there will be much less movement in our cemetery.

Pages: 1 ... 5 6 [7] 8