Thread: PRS-500 Reader internals
View Single Post
Old 10-13-2006, 04:12 PM   #12
igorsk
Wizard
igorsk ought to be getting tired of karma fortunes by now.igorsk ought to be getting tired of karma fortunes by now.igorsk ought to be getting tired of karma fortunes by now.igorsk ought to be getting tired of karma fortunes by now.igorsk ought to be getting tired of karma fortunes by now.igorsk ought to be getting tired of karma fortunes by now.igorsk ought to be getting tired of karma fortunes by now.igorsk ought to be getting tired of karma fortunes by now.igorsk ought to be getting tired of karma fortunes by now.igorsk ought to be getting tired of karma fortunes by now.igorsk ought to be getting tired of karma fortunes by now.
 
Posts: 3,442
Karma: 300001
Join Date: Sep 2006
Location: Belgium
Device: PRS-500/505/700, Kindle, Cybook Gen3, Words Gear
@N means the function has N bytes of arguments (stdcall convention). The DLL I use (ebookUsb.dll) is actually a higher-level one. It uses lower level calls from prsctr.dll, which in turn speaks to the driver (PRSUSB.sys) and the driver actually talks to the Reader over USB. So, while I more or less know how to use the high-level interface, I don't know how it maps to the actual USB traffic. However, a person with a USB spy program can probably recover this information pretty easily and that could be useful to people with other OSes.
igorsk is offline   Reply With Quote