Grant Stockdale
GBVery poor information available from… Very poor information available from Fixya . Much better answers to my DIY repair questions almost everywhere else on the internet. I now NEVER go to FIXYA.
David Meaden
GBI was looking for direction on where I… I was looking for direction on where I might Find A short in the blower motor wiring on a 1992 dodge Dakota pick up! I told them up Front that the blower motor and Blower motor resistor had been replaced with No condition change and they told me I had a short in my system which I already Knew and that I should check my Blower motor for high amp draw If these people Had Ever worked on Dakota pickups they should have been able to point me to some places they have found in stead of giving me generic answers I do not Believe these are Mechanics But Just People Posing as Mechanics and scamming People Out Of Money For Giving Generic Answers! I Did Find My Short And Fixed it With No Help From Them
Customer
GBGeneric response for Auto issues FIXYA? Really? Get a new name They charge a $1 fee upfront. For what I don't know. And $34 for the month with automatic billing. For automotive inquiries, they provide causes of listed codes that you the customer provide - along with some troubleshooting tips- the same you'll get at Advanced Auto. To a novice car owner, this may seem like a lot. It's very basic. Save your money
customer
FRDO NOT USE this site DO NOT USE this site, they offer a 1 euro joining fee, then immediately draw a hidden charge of $39 on top and set this up as a monthly charge. The "technician" suggested blatantly obvious potential fixes like turning the oven off for 20 minutes, then suggested it could be various other parts that have failed...what, buy every part until it s fixed? straw clutching at best, AVOID!!!!
Llia
GBSomeone doesn't want some issues fixed Seems someone doesn't want some issues fixed. I posted a way to give Yahoo mail users a simple way to change their display language via the address bar and the question and answers were deleted. The problem started in 2012 and continued to 2018 unresolved. I thought I'd share my fix and put the issue to rest -- and now it's been inexplicably swept under the rug.