Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Canoscan background drivers fill the console log file' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Canoscan background drivers fill the console log file
Authored by: banditpup on Jun 14, '03 04:54:01AM

i have the LiDE 30. after much trial + error, i found out that there is no need to trash or even move any of the drivers or their preferences.

i was finally able to end my looooonnnng march by removing one of the two drivers from the Login list; unchecking it is not enough to disable the error message. it seems CanoScan will work with *either* driver, but for me, at any rate, the culprit turned out to be the N67U_ButtonManager (8718) and not the N124U_ButtonManager (8717). as soon as i deleted N67U from the Login pane + logged back in, the error line stopped. i guess each of us will have to determine for themselves which driver will work for them.

now i have pretty limited real estate, so i only hook up the scanner when i need it. which means when a scanner can't be found, this console bulls**t starts all over again! since apple obviously prefers that i never turn off the imac, the only solution--short of leaving the scanner plugged in--would be that i manually add the driver back into the Login list only when i use the scanner...

also, it seems the scanner likes to see *both* drivers, because when my scan launches photoshop (in os9, at that!! but that's a whole 'nother gripe...) i get an error message complaining about missing software (worded in a way that is dripping with irony). i just hit 'ok' + everything works just fine. i'd rather live with this than the console madness.

now let's see if canon ever reads my email on this...

---
banditpup



[ Reply to This | # ]
Canoscan background drivers fill the console log file
Authored by: mitra on Nov 15, '03 06:36:12PM

it doesn't look like Canon reads your email, the drivers I downloaded yesterday have this problem.

I disabled the button manager and hope the (intermittently connected) scanner still works, its probably easier to work without the buttons (using File->Aquire or whatever) than dealing with the log-bloat.



[ Reply to This | # ]