How to write a defective product letter ?
483494
on the top left of the blank page write ur address.after that leave a line and put date below it.below the date write the address of the person u are writing to.the below it write subject.below it write salutation.then start the letter explainig ur problem in 2 paragraphs.then conclude the letter in the last para
669521
You don't want to file a lawsuit. You want resolution of the situation. Document what has been done, put in chronological order and attach a letter asking for investigation. CC the heads of appropriate agencies, and perhaps the local DA or head of Family Court as well as the Judge in your case.\n\nBEFORE you send this out, take it to a civil (generalist)  lawyer, pay his hourly rate and ask him to edit /rewrite in better language.  It's your letter, he isn't representing you, simply assisting you in dealing with others.\n\nSuing a state is like nailing jelly to a tree.  Instead,  take some steps that outline the negligence of the state, your attempts to fix and be persistent and polite.
686806
There is not one specific Test Case Format, it really depends upon the standards of who you are doing it for.  Every company has their own standards.\n\nHowever, just for reference, I would suggest the following format:\n\n1. Test Condition Description:  A short synopsis of what you are trying to test (and always test for things to FAIL as well as to work)\n\n2. Test Steps: This should be a list of detailed steps to follow in order to complete the test.  This includes all the setup required to get to that point.  If you want to test a program that is printing an invoice, for example...  part of the test case has to be creating the order/invoice in the software and getting it ready to be processed.\n\n3.  Expected Results:  This is a description of what SHOULD happen when the Test Case is run.  Some people like to put expected results after every step of the Test Case, while others put one Expected Result after all the steps have been run through.  It all depends on how detailed of a process you want the testing to be.\n\n4.  Actual Results:  This is a section where the person testing the Application writes in the actual results.  Sometimes they match the expected results, sometimes they don't.  If the two do not match, then it must be determined if it is a bug or the Test Case was written incorrectly.  Actual Results should come after all Expected Results (so if you are doing Expected for each step in the Test Case, you have to do Actual for each step as well)\n\n5.  Pass/Fail/Status:  Finally, I suggest a status on the Test Case.  This should indicate if the Test Case was Passed or if it Failed.  Depending upon the complexity of your application, you could have other statuses such as Passed with Conditions (like a message has a typo, but they don't want to retest this just because you have to change the wording of a message) or Failed Pending Review (they think it failed, but there will be a meeting to discuss if the bugs are critical).\n\nFinally, I think it's important to note that you have a Test Plans and Test Cases.  Test Cases are every single situation you want to test.  You can write general ones like "Add a Customer" to just see if functionality works, then you should have detailed ones that test specific functionality.  Remember, part of Testing is trying to BREAK the software, not prove it works.  So, some Test Cases may involve "bang on keyboard" or steps that you KNOW are wrong, but a typical user might do.\n\nThe Test Plan is an assembly of different Test Cases.  You can have a Test Cases that do some pre-setup of data and include those FIRST in your Test Plan so you don't have to include this setup in every single Test Case.\n\nRemember to be thorough, that is the most important part.  Think of EVERYTHING.  That is what makes Application Testing so difficult... there is no way that you can test every single situation, but test the most likely ones.  Test the limits too.  If you can enter a value from 0-100, test 0, 1, 99, 100, -1, and 101 as well as things in between.  Those are the most likely areas for bugs.
383504
send it to dell to get fixed
551479
try holding CAPITAL shift down plus return key and P for print. good luck...ACE
59991
Did you get one?  Do you want to write one?  Need more information .... otherwise the answer above mine seems to work ....
591573
CORRECTIONS FOLLOW.  Look carefully, as some of them are easily missed (such as the colon after the salutation).  Corrected format, syntax, clarity, paragraphs, etc.  Good luck.\n\nDear So and So:\n\nI am writing this letter on the behalf of my Legacy for the Art Studio class. \n\nOur project consists of a storyboard/framed pictorial that focuses on a comedic story about about a man -- my father, in fact -- who does not know how to speak English, and what happens when he tries to buy chickens at KFC. \n\nThe artwork will contain multiple pen and pencil sketches on standard leter-sized white paper. I would like the artwork to be hung in suitable location at eye-level on the second or third floor. Please note that the contents (i.e., story, size, medium, etc.) of the artwork can be changed if necessary, however, due to the nature of this project, that could impose an unrealistic deadline on the project. \n\nPlease let me know if you require any further information or if I may be of assistance.\n\nSincerely yours,\n\nFalennixonx
761338
It can be a H/W error or some driver errors or some incompatibilities between drivers and the H/W. It is difficult to judge through mails.
1162764
shut off your copier and let it rest for 10 mins.. and turn back on, \n\n\nif it is still no good, call for repair!
60313
Please specify what your problems are with e-mail.
787298
A strongly-worded letter has always worked well for me. Far better than phone calls. Make sure you address it to the head of the company. If I'm not mistaken, that would be Brian Roberts, CEO of Comcast. Things have a way of magically getting done when you write to the big cheese.
656365
In work at an electronics store and last time a customer bought a printer in for repair with this problem, before i sent it to the manufacturer, i did these three things which have all been mentioned already. Print head cleaning mode a couple of times. Ran allignment utility. These two did not actually fix the problem. Last of all i did the most obvious thing and replaced the cartridges and BINGO.
338478
tnx 4 corectin da typos miss manager. but, hey dnt swear it s*hit hapens. im cool. try not 2 drift out of da pic & motivate peeps 2 keep writing. da otha day wen i was tryin 2 write sumfin in ere a godam msge apeared sayin i woz not a memba. i hada hell of trouble getin round it. seems u aint got round 2 it yet.\nbut dnt botha, a u c, everyfin is in place now & if it was u who fixed it, den gud stuff. keep up da gud work
586146
The best and easiest thing is to send a test mail. If the ID is not active, then the mail administrator sends you a mail detailing the error.\nYou can test the validity of the e-mail using Yellopipe's Free E_Mail Validating Tool. Visit http://www.yellowpipe.com/yis/tools/email-validator/verify_email.php
752305
Find the error. It's impossible!\nCapital "F" and capital "I" and a "." or an"!".\nThe alphabet is just "a red herring"
420220
Try unplugging it from the wall, this will reset all errors.  If it still says the message, try opening up different areas too reseting the message.  Dell aka Lexmark has had many problems such as this one and depending how old it is trash it if can't fix problem.  The cost of fixing will be too much, buy a epson or hp.  good luck!
1055846
I cannot buy this unless I get the discount.\nYou should be able to find out what the mistake was.\nWe can find where it has been misplaced.\nYou have given us a discount for the moth of April because of the letter that was issued by Mr. Smith.\n\nI think these sentences sound a lot better.  \n\nGood luck.