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

[Rich Walsh]

Be nice if USBKBD.SYS was a BASEDEV so the keyboard would be recognized sooner, like when there is an error in config.sys.

AN's USBKBD.SYS IS a BASEDEV. David A. refactored the USB stack specifically to enable PAUSEONERROR (and it works great here).

Doublecheck your config.sys - it seems unlikely a BASEDEV would even load if invoked from a DEVICE statement. My repeatedly-upgraded system has it as a BASEDEV.

[Dave Yeo]

Fresh 5.1 install has it as a DEV, this one that has been updated quite a few times has it as a BASEDEV.
Hmm, 5.1 has version 12.14 while this one has 12.16.

[Pete]

Hi Rich

I have ArcaOS 5.1.1 - fresh install - with USB12.17 installed and usbkbd.sys is a dev line...

Looking through the usb-12.17.exe install script I see that the dev line should have been removed to be replaced with the basedev line. Obviously did not happen here - not sure why...


Regards

Pete

[David Graser]

Here is what I noticed on my system.

ArcaOS Usb 2.18 drivers are recognized at bootup on my system.

BASEDEV=USBKBD.SYS

With Lars 10.253 USB drivers, my USB drive is not recognized at Bootup.  However, if I unplug it and reinsert, the drive is recognized.

DEVICE=D:\OS2\BOOT\USBKBD.SYS

[Lars]

Be nice if USBKBD.SYS was a BASEDEV so the keyboard would be recognized sooner, like when there is an error in config.sys.

AN's USBKBD.SYS IS a BASEDEV. David A. refactored the USB stack specifically to enable PAUSEONERROR (and it works great here).

Doublecheck your config.sys - it seems unlikely a BASEDEV would even load if invoked from a DEVICE statement. My repeatedly-upgraded system has it as a BASEDEV.

Hm, depends on the system, I suppose. I have a system that still offers "legacy USB" implementation. Which means, USB keyboard will work (directly supported by BIOS) during bootup even if no OS specific USB host controller driver has yet taken over. Which is the reason why I decided for 10.25x to only hand over to OS specific USB host controller drivers on INIT_COMPLETE, that is, very late in the boot process, just before all the RUN= statements are executed. And that works just fine for my system, I can use keyboard from a bootup command line.

[Lars]

Here is what I noticed on my system.

ArcaOS Usb 2.18 drivers are recognized at bootup on my system.

BASEDEV=USBKBD.SYS

With Lars 10.253 USB drivers, my USB drive is not recognized at Bootup.  However, if I unplug it and reinsert, the drive is recognized.

DEVICE=D:\OS2\BOOT\USBKBD.SYS

10.253 USBMSD.ADD driver needs to scan the USB drive/stick if it is of type "large floppy" or "partitioned". For that it needs to read the first few sectors and potentially "virtualize" a partition layout before it can report a new device to the system. If you use AN's USB monitor, it can fail as it has a timeout on device insertion. Just hit refresh in this case.

AN has solved this differently (better even), by updating OS2DASD.DMD and keeping USBMSD.ADD simpler.

[KevinP]

I had a bit of luck with this today.  I installed the XR_C005 fixpak.  Now the internal revision is 14.103_W4.  Now the ehci and msd drivers are showing up at boot but there is a message that they cannot connect to usbd.  The mouse and keyboard drivers now appear to be loading but the USB mouse and keyboard I have connected (to the rear sockets on the computer) still do not work.  Should I disconnect the PS2 mouse and keyboard I have been using?  After I first got the fixpak installed and rebooted I noticed that there was an extra drive letter showing but it eventually went away after another boot or two.  I installed the USBSER driver because I occasionally use serial devices for ham radio and wanted to see if that driver would load.  There is still one of the Arca Noae drivers (acpi) that I have not yet been able to install because it need kernel 104a or higher so I will have to try to update the kernel again.  I will attach a couple of photos of the output at boot.  Thanks,

[Dave Yeo]

Kernel is easy to update. Download https://www.os2site.com/sw/upgrades/kernel/w420050811.zip unzip and directions are at the bottom of the readme, basically changing the attributes, backing up your old os2krnl and os2ldr and copying the new ones into root and rebooting.
Then apply the ACPI package which may well help with your problems.

[Andi B.]

Should I disconnect the PS2 mouse and keyboard I have been using?

No. PS/2 keyboard and mice works well at the same time (even better than) beside USB keyboard/mice.

Code: [Select]

USBSER driver because I occasionally use serial devicesNo clue for what USBSER is useful today. For serial communication over RS232 (com ports) you usually take USBCOM nowadays. Depend of your special device (VENDOR/ID).

[KevinP]

No clue for what USBSER is useful today. For serial communication over RS232 (com ports) you usually take USBCOM nowadays. Depend of your special device (VENDOR/ID).
[/quote]

Hi, Andi

I don't know about the protocols.  The devices I was thinking about are old hardware ham radio "modems" or encoders/decoders.  They generally convert audio into RS232 and vice versa.  They were used for AFSK modes like Radioteletype, and PSK and other digital modes.  There are software modems now, of course, but some people (like me) still like to use the old hardware modems.  There were quite a lot of DOS programs for them and some Windows program up through about 98.  The USB converters are a lot better than they used to be so, admittedly, there is not as much need for serial ports now although I like to keep computers that have real serial ports.

[KevinP]

I have successfully (apparently) upgraded the kernel to 104a.  I have been known to screw up "simple" tasks so that was a relief.  I also installed the Arca Noae ACPI drivers although there were several error messages about not being able to create workplace shell objects.  I thought that those were probably/maybe harmless.  I am still getting the same error messages on boot:  EHCD and MSD drivers are not connecting to USBD.  There is, however, an extra drive, Drive F:, showing up in the drives list.  It shows as a disk drive.  I have a USB CDROM attached and put a disk in it to see if it would be recognized but it was not.  I also tried a USB thumb drive which also was not recognized.  Attached are the most recent shots of the bootup and config.sys:

[KevinP]

I had an idea that I am going to try; I don't know if this will help.  The USBECD driver I have installed is not the Arca Noae version (12.17).  I don't know if that interferes with the EHCD driver but I will try installing the 12.17 version later today and see.

[Pete]

Hi Kevin

What are you using USBECD.SYS for? - and, no, it should not interfere with usbehcd.sys...

With regard to config.sys image:

   I do not see a usb cdrom driver listed - BASEDEV=USBCDROM.ADD /CDS:1

   You do not have an OHCI controller so either start the line with REM  or delete the line.


Regards

Pete

[KevinP]

Hi Kevin

What are you using USBECD.SYS for? - and, no, it should not interfere with usbehcd.sys...

With regard to config.sys image:

   I do not see a usb cdrom driver listed - BASEDEV=USBCDROM.ADD /CDS:1

   You do not have an OHCI controller so either start the line with REM  or delete the line.


Regards

Pete

Hi, Pete

When the EHCD driver wasn't loading I thought I would see if the ECD driver would work with anything.  It does recognize one device but does not say which one.  One odd thing I noticed was when I installed the AN version 12.17 of the driver there would be an error message that there was an incompatible stack.  The version 23 loads fine and since the 12.17 version is supposed to be more compatible with the newer stack I did not understand that.  There is not a version 12.18 in the subscription drivers as far as I could see.

I have remarked out the OHCD driver line

I had disabled the older USBCDROM driver I had because I had read that the newer Arca Noae drivers supported USBCD's. 

I am still getting the error that the EHCD and MSD drivers are not connecting to the stack.  The EHCD driver says it is loading but the MSD driver does not say that.

Thanks,

Kevin

[Pete]

Hi Kevin

Yes, I see usbmsd.sys now supports the /CDS:n switch which needs to be on the usbmsd line eg

   BASEDEV=USBMSD.ADD /REMOVABLES:4 /FLOPPIES:1 /A_USAGE:0 /CDS:1 /V


I suggest using REM on the USBECD.SYS line for the moment while we try to figure out why usbmsd.sys is not loading.
From your bootup screenshot I suspect that usbd.sys is not loading when it should - have to add the /V switch to some drivers, reboot and try to spot if usbd.sys loads *before* controllers here.


Regards

Pete