getting Arca Noae USB drivers v12.18 to work on rev. 14.089_W4

[Pete]

Hi Kevin

Rebooted with the /V switches in place and the 1st usb driver that loads is usbd.sys followed by controllers then usbhid.sys then other usb drivers.

I believe the load order is determined by the kernel and kernel 104a was built with the IBM USB drivers as target so that will load controllers before usbd.sys causing the non-load problem with usbmsd.sys

I think your way around this is to revert to the earlier Arca USB drivers (v11.xxx?) in the OS/2 & eCS drivers package or install Lars USB drivers http://hobbes.os-2.in/files/os2/system-6/drivers-4/usb/usbdrv253.zip - or. more expensively, update to ArcaOS.

 
Regards

Pete

[KevinP]

Hi Kevin

Rebooted with the /V switches in place and the 1st usb driver that loads is usbd.sys followed by controllers then usbhid.sys then other usb drivers.

I believe the load order is determined by the kernel and kernel 104a was built with the IBM USB drivers as target so that will load controllers before usbd.sys causing the non-load problem with usbmsd.sys

I think your way around this is to revert to the earlier Arca USB drivers (v11.xxx?) in the OS/2 & eCS drivers package or install Lars USB drivers http://hobbes.os-2.in/files/os2/system-6/drivers-4/usb/usbdrv253.zip - or. more expensively, update to ArcaOS.

 
Regards

Pete

Hi, Pete
Thanks very much for the observation.  I had noticed that when I made changes in usbcfg and then closed it I would get a message that I was using a "non-standard" stack and that it might help if it were loaded in reverse order.  I didn't know if that was a factor just of usbcfg or the kernel or what but I had basically begun to suspect what you are saying.  I will revert to some of the older drivers and see what happens.

I do intend to buy a copy of ArcaOS at some point.  My goal for the moment has been simply to find out what OS/2 was about and get my feet wet using it to see what I could do with it and if it could meet my computing needs.  This is with a longer view to being able to use "something else" on computers that do not meet the requirements of Windows 11.  I see no reason to toss out perfectly good hardware just because the "Big M" company is casting a wider net.  I realize I need something a little more than a Pentium 4 but it will do for fun!   I'm not a gamer and don't do a lot of heavy lifting with computers.   I have run Linux in the past and ran my own Web and e-mail server with it for several years so I can also go that route.  I'm not very knowledgeable about the deep technical aspects but I can get by with help.  I will try out the older USB drivers and let you know.  Thanks very much.

[Rich Walsh]

There's _waaaay_ too much screwing-around going on here. There's nothing special about this machine and nothing difficult about the WPI-based driver install that would warrant it.

If two drivers don't load while the rest do, then maybe they're backlevel or there's more than one copy along the search path (said path is \,  \OS2, and \OS2\BOOT in that order). If that isn't the problem, then run "testlog generic" from a command prompt, fetch the report from your temp directory, and post it here (it's big but that's OK).

BTW... when you upgraded the kernel to 14.104a, did you also update DOSCALL1.DLL? It is in a separate package on the same page where you found the kernel.

[Lars]

Looking at the posted boot screen, I had the impression that there is a wild mix of 12.18 drivers and 10.162 (IBMs original) drivers ...

To make it short: all USB drivers (client drivers, class drivers, host controller drivers, USBD.SYS, USBRESMG.SYS/USBRESMG.DLL) need to come from the same package.

[Dave Yeo]

You can often use the bldlevel command to get the version number.

Code: [Select]

N:\OS2\BOOT>bldlevel USBMSD.ADD
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature:       @#Arca Noae LLC:12.14#@##1## 26 Nov 2022 14:16:33     DAZAR1
 ::::::@@USB Mass Storage Device Class driver (32 bit) (c) 2022 Arca Noae LLC
Vendor:          Arca Noae LLC
Revision:        12.14
Date/Time:       26 Nov 2022 14:16:33
Build Machine:   DAZAR1
File Version:    12.14
Description:     USB Mass Storage Device Class driver (32 bit) (c) 2022 Arca Noae LLC

Or as Rich said, download and run testlog, find the latest here, https://88watts.net/software.html run as "testlog generic" only once per boot.

[KevinP]

There's _waaaay_ too much screwing-around going on here. There's nothing special about this machine and nothing difficult about the WPI-based driver install that would warrant it.

If two drivers don't load while the rest do, then maybe they're backlevel or there's more than one copy along the search path (said path is \,  \OS2, and \OS2\BOOT in that order). If that isn't the problem, then run "testlog generic" from a command prompt, fetch the report from your temp directory, and post it here (it's big but that's OK).

BTW... when you upgraded the kernel to 14.104a, did you also update DOSCALL1.DLL? It is in a separate package on the same page where you found the kernel.

Rich,
No, I did not update DOSCALL1.DLL.

[KevinP]

Looking at the posted boot screen, I had the impression that there is a wild mix of 12.18 drivers and 10.162 (IBMs original) drivers ...

To make it short: all USB drivers (client drivers, class drivers, host controller drivers, USBD.SYS, USBRESMG.SYS/USBRESMG.DLL) need to come from the same package.

Lars,

I did make sure that all the drivers were 12.18.  The only one that was 10.162 was the CDROM driver and I uninstalled it.

[KevinP]

Now I have a bit of a different problem.  I was going to revert to one of the older USB drivers (10.253) so I uninstalled the Arca Noae drivers with WarpIN.  Then I copied the 10.253 drivers over and rebooted.  I noticed that the computer "froze" at some point.  I determined that it was hanging up at "Installed OS2LVM.DMD".  It won't get past that point.  Is that a kernel problem or a driver?  I thought maybe if I could get to the config.sys that I could see what was wrong (assuming it was something with the USB drivers).  I can get to a command prompt and start the Enhanced Editor to edit the config.sys and that will get me to the desktop.  It has some functionality but not completely.  It will still freeze up sometimes and I can't do anything.  Strange things.

[Rich Walsh]

BTW... when you upgraded the kernel to 14.104a, did you also update DOSCALL1.DLL? It is in a separate package on the same page where you found the kernel.

No, I did not update DOSCALL1.DLL.

You should: they're a matched pair.

[KevinP]

BTW... when you upgraded the kernel to 14.104a, did you also update DOSCALL1.DLL? It is in a separate package on the same page where you found the kernel.

No, I did not update DOSCALL1.DLL.

You should: they're a matched pair.

Thanks, Rich, I will try to get that done.

[KevinP]

I got testlog installed and started running it.  How long should that take?

How do I update doscall1.dll?  I have saved a copy of it and have moved the new one to the c:\os2\dll directory but the old one is always in use.

Thanks,

[Dave Yeo]

Here's unlock.exe, put it somewhere on the PATH, here in X:\OS2 after unzipping it.
Run it like unlock nameof.dll, or "unlock C:\OS2\DLL\DOSCALL1.DLL" in this case and replace the DLL, then reboot.
Unlock will load the DLL into memory allowing its replacement while the old DLL is still being used, rebooting will use the new copy.
Edit: testlog should only take a couple of minutes at the longest, shorter on a simple system

[KevinP]

On testlog, I ran that from the command prompt last night.  When it asked that I enter some identifier for the output I typed "Ticket_1" and hit enter.  After that, the cursor just blinked and I never received any additional messages or instructions.  I left the computer running all night and it was still like that this morning.  I re-booted and tried again and got the same result.

I got unlock.exe installed, then unlocked the previous doscall1.dll.  That worked.  It would not let me rename the doscall1.dll_w4 to doscall1.dll so I did "copy doscall1.dll_w4 doscall1.dll" and that appeared to work.  Then I rebooted.  It still hung at "Installed OS2LVM.DMD".  I rebooted, got to the command prompt, and typed epm as I had been doing to get to the desktop.  This time I got the error message about doscall1.dll as shown in the first photo.  Then I tried running testlog again and received the error message shown in the second photo.  Does any of that output help?  As far as I know, this problem first started after I uninstalled the AN USB stack and drivers with WarpIN.  I can't remember doing anything else before this started.  Thanks,

[Dave Yeo]

For testlog, I'd guess a wrong DLL installed, perhaps an older one of the Rexx utilities. Look in %TEMP% to see if anything was written. Not sure where %TEMP% is on your system, enter SET TEMP at a cmd prompt to find out.
The doscall1 trap looks to me a mismatch between the kernel and doscall1. The kernel presents as doscalls.dll and doscall1 is a very basic DLL. Can you revert the upgrade? Hopefully you backed up the DLL.

[KevinP]

SET TEMP returns TEMP=(null).  I did back up the previous doscall1.dll as doscall1.sav.  Now when I try to run unlock I also get the same doscall trap message.  The doscall file I used was from the os2site:   Icon    dc20050811.zip.  There wasn't one bundled with the kernel I downloaded.