|
Ran into local store & bought the _same_ box of printer ink I bought a couple of months ago (same $$ too).
Got it home and noticed that it isn't quite the same. Here's a snapshot (the one on the right is the new one[^]). 
Oh, for fox sake! 🦊🦊🦊
Yep, Epson punk'd me. They're so funny. Aren't they?
|
|
|
|
|
It appears will NOT be able to exceed your vision...
|
|
|
|
|
They did not punk you, you just did not order/purchase/pickup it correctly.
Epson 220: comes in BLACK only, multi-color, and Black/Multicolor.
You need to make sure you grab the correct box of 220. Look it up, you will see what I am talking about.
|
|
|
|
|
Ok, might be true, but did you see the photo of the two boxes.
They look (almost) exactly the same and they are the same size boxes too.
I know that all tricks committed on a person are always the victim's fault -- everyone cons theirself -- but this one was really tricky.
Also, I love marketing!!!! But, I love marketing-speak even better. And, Bureaucracy is an order of magnitude better than all marketing-speak. 
|
|
|
|
|
Well, to be honest, I am not sure why they don't have these boxes/products labeled: 220-1 Black, 220-2 Black/Multi-Color, and 220-3 Multi color, no black.
I am sure many, many people make the same mistake.
|
|
|
|
|
Yeah, but that's just bad product packaging. You shouldn't have to read the fine print to buy an ink cartridge.
|
|
|
|
|
Simple solution: pick up your printer and place it on your desk. Unplug it from the mains supply, then open it. Remove the Black cartridge and turn it upside down.
Then hurl the printer out the window and buy a laser ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I have followed the first N steps & my basement window is broken & my printer is in pieces on the front lawn.
I have obtained a laser (got it from the cat). Accidentally shined it in my eyes so I cannot follow further steps. 
|
|
|
|
|
That is part of the plan.
If you can't see, you don't need a printer.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
A good laugh cures most problems. Years ago, I bought a multi-color Brother laser printer. Used it a couple of times back then and have never used it since. The Toner was hideously expensive BWT.
ed
|
|
|
|
|
The solution is don't buy printers that use a multi-color ink cartridge. Yes, the printers will be more expensive but the lower ink costs, especially for heavy printer users, will cover it.
|
|
|
|
|
You're right.
Mine is a WF 2760 & I bought it explicitly because it uses separate ink cartridges for all 4 colors (black, yellow, cyan, magenta).
You can replace any one that runs low without the others buggering up.
|
|
|
|
|
Your only missing the Black...
Just print on Black Epson Paper... You'll be fine...
ROTFLMAO 
|
|
|
|
|
I plan to add logging into my Windows Form application.
NLog is still looking good for me in my case.
are there any people still using it from codeproject community?
diligent hands rule....
|
|
|
|
|
... this guy:
hehe[^]
Yeah that's what I'm talking about ... hehe ... use'n it. Awright!(sniff)
|
|
|
|
|
thanks for this link!
diligent hands rule....
|
|
|
|
|
We are using Log4Net, which I'm not very fond of, never tried NLog but it seems a better choice.
See overview here: best-net-logging-frameworks[^]
|
|
|
|
|
your input is always insightful for me.
I used this post as a jump start.
diligent hands rule....
|
|
|
|
|
I use nlog - I prefer it to log4net. It's very easily configured, and comes with pre-canned formatters for most situations that you can think of.
|
|
|
|
|
|
The better question is, should I do logging? Seriously. I'm not being facetious. Logging sounds great until, as I've always experienced, there are reams of output to wade through and nobody bothers and they even forget there's logging going on.
What is it you need to log, and when exactly does it need to be logged?
Now granted, years ago my team added logging to every user action (this was a DOS desktop app at that) which was enabled in "QA" mode. We logged the tester's activity, we were able to play it back, and when they said "I did x, y, and z" we could look at the log and say, "no, you did x, A and z" and they were stunned. So that kind of logging was quite useful! 
|
|
|
|
|
I think logging exceptions and/or unexpected errors is a must, especially for debugging purposes.
I am not really into informational logging in a Prod environment; maybe, in dev, but not prod.
we have a pageview table that stores all the page view stuff for troubleshooting and metrics for business team.
|
|
|
|
|
Slacker007 wrote: I think logging exceptions and/or unexpected errors is a must, especially for debugging purposes.
Agreed. I've actually become rather brutal about it - I send an email to myself when something critical blows up. I have a few Outlook rules as a result.
|
|
|
|
|
your question is great: my first step is to log some data files that are empty. I downloaded these kinds of files using web API.
I need to know what kind of files are empty.
later on I will go deeper to record exceptions.
diligent hands rule....
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
I needed that! 