May 12, 2003 7:15 AM PDT
DYMO label printers can prevent sleep under Mac OS X
The DYMO LabelWriter 330, which only recently received Mac OS X compatible drivers, is disallowing some Macs to stay asleep.
Attached to the USB bus, the printer/driver will not allow some Macs to stay in sleep mode. It appears to us that the printer continues to make calls across the bus, waking up the host. The only option at this point is to disengage the printer from the USB bus; this allows the Mac to continue in sleep mode.
DYMO admits to the bug:
"Solution: Hardware development is presently working to resolve this situation. Once there is a resolution should you will be notified."
Feedback on this issue? Late-breakers@macfixit.com.
Resources
They couldn't organize a prayer in a mosque!
connected computer sleep is to turn off the unit of unplug the USB. Both
choices are a hassle.
Last week I called DYMO and the tech person I spoke with told me that
the new 330 model had fixed this issue. Appearantly, either he was
misinformed or just BSing me.
I do hope they fix it soon, but it wouldn't have been a "deal breaker" for me if I had known about this bug before I bought it. I love my Dymo, and the new OSX software is really fine.
Steve
front of the printer for about 5 seconds. The light will turn off as the
printer turns off. Wake it up again by momentarily pressing the key
again.
<p>
I noted the USB sends from the Dymo in OS X 10.25 --- it was what kept
crashing my Macs by sending the USB signals!
- by pderby May 13, 2003 9:02 AM PDT
- As a beta tester for Dymo, I reported the sleep issue to Dymo 4 times
- Like this Reply to this comment
-
(5 Comments)during the beta test of the Mac OS X software. April 22, the day of
release, I reported the problem again directly to Joe Horvath, Director of
Customer Relations at DYMO, and asked them why the sleep issue didn't
get fixed during the beta test cycle. He didn't seem to be aware of the
situation and contacted the developers. (I think Dymo outsourced their
development to a company in Russia). He said it was probably a
firmware issue and would get back to me. I'm still waiting.