USB (DOT4) Printers & OS4.1 **Testing in Progress**

@rwo

big thanks for the update ..unfortunately I get an immediate guru and system hang up when I try to rpint from both DOpus or AmiPDF??
now I'm not sure it this is due to Update2 as my USB devices that worked great under Update 1 no longer work under Update 2

@328gts

could you send me the debug info, capture it with dumpdebugbuffer

RWO

@rwo

i never tried this myself but googled it and will give it a go....can you give me a quick synopsis

@328gts
Let the app crash, open a shell and type
Quote:

@ZeroG

But the system crashes so I think rwo is referring to a serial connection via another computer

@328gts

Crash here too, takes down the USB stack and doesn't print anything.

I'll get some debug output when I can be bothered to switch my old Windows laptop on.

I have a HP Photosmart C3180, and I think it is supposed to be DOT4 compatible, but I'm not sure. Anyway, it doesn't work with the usbdot4.device, it only spews out nonsense when I try printing from notepad or amipdf. Does anywone know if this printer is supposed to work with the device?

Some of the earlier versions was able to print out the first line fo text from multiview but anything else made it crash. I can't even get that far with the latest version, it crashes at once no matter what program I try to print from.

The printer is a HP LaserJet 1010

Crashes here also, does not print anything from NotePad. HP LaserJet 1012, usbdot4.device version 1.5, OS4.1 update 2.

I really need the Debug Buffer to fix this, for I can print with out any problems..

So please send it to ac@rebels.com

RWO

@rwo

How do I get hold of the debug buffer? I don't have any serial terminal, if that's what you are talking about...

EDIT: I can tell you, that from amipdf the following text is written by the printer:

%!PS-Adobe-3.0
%%DocumentMedia: letter 612 792 0 () ()
%%EndComments
% The line abo

(each line starting horizontally at the point where the above line ended)...and then comes a lot of (6-7) page feeds, and the printer seems to be left waiting for more data.

@rwo

Quote:

The thing is, my system hangs up completely when I try to print.

@alfkil

Well this shows the my driver is working.. it manages too send of data to the printer.

And that was the hole point of the driver, as its just a transport layer.

The problem you have is the printer do not understand the data send, it looks like postscript (not sure).

To test driver driver you should really first open a small text file in multiview and then select Print.. I expect that would work just fine.

When it comes too graphics it gets tricky.. i'm not really an expert setting up printers. Maybe some of the other nice users around here can help you with that.

RWO

@trixie

Can you manage with a fast reboot?

for the debugbuffer should suvive that.

just open a shell and type

DumpDebugBuffer ram:dot4.txt

and send the text file in ram to me.

RWO

@rwo

Hehe, it's working alright, but something is still missing.

I found out, that prefs/Printer was set to Postscript instead of Generic. So far so good. But when printing from Multiview, the printer takes in the paper, and then it just sits there waiting for smth and nothing is printed. Then I try switching back to Postscript, go to a shell and type "echo hello >prt:" and suddenly my text file comes out, followed by the PS mumbo-jumbo from before follower by lots of linefeeds...

So it seems, that when printing generic, the printer is missing a 'flush' or 'eof' at the end of printing. Correct??... Is this an issue of your driver, or is it the software (multiview etc.)?

EDIT: typing "echo hello >prt:" with Generic turned on does nothing. Also "cat file >prt:" does nothing, except add data, that is eventually flushed when switching to PS mode.

EDITEDIT: Hurrah! I got it printing graphics from amipdf, just needed to install generic HP Deskjet driver from SYS:Storage/printers. Ren?, you are a genius!

@alfkil

Yeah, I powered everything on to get some debug output, and discovered it was all working. I haven't tried it again without the serial debug enabled (maybe it's a timing thing), but it generally seems to be working. Need to do some more testing.

Thanks rwo :)

@Chris

Maybe update the readme to explain a bit more for us dummies, who don't know how the printer system actually works ... ? :)

Quote:

ahh ok finally rene I was able to soft reboot my Miggy and I just sent you the ram:dot4.txt file!...I must have tried 20 times to print but always immediatley got a complete system crash and always had to hard reset to get the4 system going again but luckily just a few minutes ago it soft booted and I was able to get the file..hope it helps and thanks for continuing to try to get this driver going for all of us

@rwo

OK I've sent you the debug buffer saved after soft reboot.

any news Rene ?