Problem with native (internal) card reader

[Anchieri]

After installing version 10209 and now 10210 I have tested my native multi card reader for reading my SD Card that range from 128MB to 4GB, but none of this card is attached and readable.

With AN v. 11.14 this is possible with all of this card.

I have tested also this reader with a key card (San Disk Cruzer Edge 16GB) and this is attached and is possible to read it.

G.M. Anchieri

[Anchieri]

Another bug erase a few minutes ago, I have two USB printer attached to my PC:

• 1) HP PSC 1610 ALL in ONE
• 2) HP OFFICEJET PRO 8610 network printer

I can print with the first, but if I want print using the second, the page printed remain in SPOOL and I receive a window error with the message that the printer is offline or not attached. This error is present either if I use deskjet driver or CUPS This don't happen with AN v. 11.14.

[Lars Erdmann]

Have you read "readusb.txt" in the zip file ? USBMSD.ADD does not offer LUN support which in practice means it does not support multi-slot card readers. You will need to revert back to USBMSD.ADD version 10.162 (the original IBM driver) if you need that. However, you will then lose "large floppy" support and the various stability fixes I have done over the years.

About printer: I very much doubt this has anything to do with USB and I also doubt it works with AN 11.14 with 2 USB printers. Just open USBRES.EXE and see if both printers show up if you attach both of them.
I rather would delete all USB printer ports, all USB printers and redo the printer installation.
Make sure that USB auto monitor (USBMON.EXE USBPRT) is running and that "USBPRT Auto Monitor" is enabled in the USB port.
Each USB printer needs its OWN USB printer port which will be auto created by "USBPRT Auto Monitor".

[Anchieri]

OK, if I want use this multi-card reader I have to use AN v.11.14 or waiting till you have inserted in the new stack this possibility.

I use the 1610 printer by six or seven year and I acquired the 8610 by a year or so because the first is now unable to scan/copy data.

I use one or the other conforming to the work that is to be done and using AN v 11.14 I can print with one or the other indifferently using deskjet driver or CUPS.

I attach startup-folder pr-1610 and pr-8610.

I have run USBRES.EXE but I receive three window error (figure1/2/3) that I attach.

G.M. Anchieri

[Lars Erdmann]

1) you have to start USBRES.EXE from the \ecs\bin directory. You can create yourself a program object that correctly sets the working directory.
2) for the traps: what did you do ? Looks like your system is not correctly set up. I suppose you are using an outdated USBCALLS.DLL.
3) create a screen shot for the two printers properties, in particular the output port page. Should look like the attached "PMGRAB00.BMP".

I think you should stick to the AN drivers if they work better for you.

[Lars Erdmann]

I attached another screenshot.

What you can also do is trace if the 2 printer are correctly detected:
1) read file "readusb.txt" in the zip. You should find it in the root directory.
It will explain how to enable tracing.
2) enable tracing for trace code 227. That's the trace code for USBD.SYS.
3) Attach as little USB devices as possible. Of course, attach the 2 USB printers.

Attach the created trace file to this ticket so that I can have a look at it.

[Anchieri]

Mr. Erdman, I have executed all your request and now I have three file to attach:

• USBRES.jpg with the response of running usbres.exe
• USBPORT.jpg with an image of my USBPORT as you can view we have three USBPORT I use the first two for my printer the first for HP 1610 and the second for HP 8610.
• TRACE-227.zip with the trace obtained as stated in readusb.txt, I have power on all the two printer before to stop trace and formatting it.

[Lars Erdmann]

Some comments:
1) try the attached usbprt.zip.
2) your USB ports are set up incorrectly. The USB ports should have the same name as the printer object. I suggest to delete all USB printer ports ("5740_1" and "A7F64A_2", "USB_PRINTER") and have them recreated by the USB auto monitor ("USBPRT Auto Monitor" in your startup folder).
3) looking at the trace, the printers have not been turned on when you took the trace. They obviously do show up in USBRES.jpg so that means that they are detected. But the trace only contains some mass memory device (the memory stick, or more likely, the card reader you were talking about: "Genesys Logic X-PRO CR20xA"). This mass memory device also leads to a lot of errors, for the printer tests it would likely help if you removed that card reader until we get the printer problem sorted out.

You have a problem with the USB port driver (USBPRT.PDR) not properly associating the printer queue with the USB printer.
I hope the usbprt.zip will somewhat improve the situation. Unfortunately the USB port driver (USBPRT.PDR) is also flawed (that's my experience at least). What you can also try is unplug and replug the USB printer until the port info shows "ONLINE (ATTACHED)". It can take quite some tries until you are finally successful.

[Anchieri]

• 1) I have tried your usbprt, without success
• 2) my usb port are correct because with v. 11.14 this work correctly
• 3) I have tried many time to plug and unplug the two printers on vary USB slot on my PC,

but the printer are never connected.

After that I have reinstalled v. 11.14 because I have to print some PDF files and now for your convenience I attach two more files,

• HP1610-1.jpg with information from property folder
• HP8610-1.jpg with information from property folder

When you have other build to test I can test this too.

[Lars Erdmann]

Will not implement multi-LUN support in USBMSD.ADD. Unfortunately this functionality is missing from the DDK source code that the updated USBMSD.ADD builds upon.

For the printer problem, I cannot find a fix, I have tried some improvement in 10.211 but that does not seem to significantly improve the situation. The port detecting printer attachment is unreliable but this is also true if I install the original USBPRT.SYS from IBM. However, the printer always properly connects to USBD.SYS / the system which can be verified with either OS/2 HW manager or with USBRES.EXE.