On 8/10/07, Graeme Gill <> wrote: > > With printread, I like the beep confirming that it's ready to > > scan. But I'd *really* like audible feedback for the success or > > failure of scanning. Perhaps one beep on success, and three on > > failure? That way, I wouldn't have to look up to make sure that > > the strip was read okay. > > I thought about something like that, but there are cross platform > issues. Linux simply doesn't have a reasonable beep capability. > I've literally got to send a bell character to the console > to get it do something ! OS X is only slightly better. There are > other paths, but they are not simple, and create dependency and > configuration complexity. (On my test Linux box I can't even > get it to beep. I can get the screen to flash, but no beep > from Linux. I know the HW is OK because the BIOS happily > beeps on startup). On my linux box it beeps when I use printread in the start of each row, not in the end. This was after I read about the beep and loaded the pcspkr module $ /sbin/modprobe pcspkr Another issue is that I often have to unplug the device after I have read one target before I start on a new target, If not printread will not recognize the usb path, but I guess this issue is related to the ,impossible for humans to understand, udev system on linux. Lars Tore Gustavsen