SupercheapAuto My Garage
The best way to find spare parts for your Mazda CX9 or any vehicle is to go to supercheapauto.com.au and use their "My Garage" feature. Enter your vehicle registration number, or choose which model vehicle you want to find parts for, click the little yellow arrow head that points down on the My Garage section on the main website page and then click "Shop All Parts For My Vehicle".
The page that loads will look a bit like a website from 1998, and it shows you all the spare part categories on the left which you can use to filter the products shown on the right. This catalog system is pretty good and it shows you photos of the parts in some cases which is really helpful. Once you find a part you want, you should then get some sort of part number, code or brand name you can google further to get more info.
Google for more Info
For example, I was after an air conditioning/heater blower motor for my Mazda CX9. I looked up the part in SCA's My Garage, then noticed it was made by a company called JAS Oceania.
Googling JAS Oceania brought up a location only about 1km away from the SupercheapAuto store's location in my area. In other words, the supplier of the part is in the same suburb as SupercheapAuto's store. I might be able to buy directly from the spare part manufacturer? The advantage to doing this is a lower lead time. I might be able to get the part immediately instead of waiting for SCA store to have it sent over to them, which can take at least a half day and usually takes a day on average in my experience.
Most spare parts, but not all, will have a part number on them and perhaps a brand name. This is a really good way to find the part online. Google for the brand and part number and you will find you can probably buy the part from a number of online stores, but buyer beware - I found the blower part I wanted on AliExpress but it wasn't the full part with the cylindrical fan blades attached. It was only the motor segment of the part and the pricing was about the same as buying the whole part locally. I prefer and recommend buying locally over online, especially for automotive spares because if the part is incorrect you can return it and exchange it or get a refund. Doing this is a big hassle with online purchases.
[ view entry ] ( 348 views ) | [ 0 trackbacks ] | permalink | ( 3 / 456 )
This will select last Thursday's date:
SELECT date('now', 'weekday 4', '-7 days')
weekday 4 = Thursday, but if we want last week we have to -7 days from it.
If you want the date to be returned as unix epoch value, do the following:
SELECT strftime('%s', date('now', 'weekday 4', '-7 days'))
[ view entry ] ( 485 views ) | [ 0 trackbacks ] | permalink | ( 3 / 535 )
Be aware of them and don't fall for their tricks.
This morning I noticed an email in my personal email account which is hosted on my own domain that I pay a webhost company for. I've had this website at this host company for the last 15 years. The email was in broken English and is very similar to most scam emails you will get, saying they've hacked you, they've got dirt on you (photos and videos) and to pay them in Bitcoin and they'll delete the stolen files (LOL)
Read More...
[ view entry ] ( 824 views ) | [ 0 trackbacks ] | permalink | ( 3 / 764 )
There is an error that you can get when building your KVS code and it tells you it found a curly brace when it shouldn't.
This can happen if you start writing a section of code and then forget about it and lose track of where you were in the Code Editor. This error is saying to you, "you've left out a curly brace or a parenthesis or something" and it will report to you a line number but this is the problem. The line number given sometimes is not helpful. In my case, it said:
[15:11:46] [KVS] Compilation error: Found character '}' (Unicode 7d) where an instruction was expected
[15:11:46] [KVS] In script context "kvirc::corecall(run)", line 978, near character 5
[15:11:46] [KVS] Code listing:
[15:11:46] [KVS] 976 ...
[15:11:46] [KVS] 977
[15:11:46] [KVS] 978 }
[15:11:46] [KVS] 979 }
[15:11:46] [KVS] 980 ...
[15:11:46] [KVS] Window:
[15:11:46] [KVS] classeditor [ID: 24]
So I knew what the problem was, and I knew it was in my classes code ("Window: classeditor" but it said "script context kvirc::corecall(run), line 978". This is not that helpful because when you're using Code Editor inside KVIrc all the code is split into classes and functions so line numbers don't match what you're looking at.
How to find the location of the problem
The way to find where this problem is, is to do the following:
1. In Class Editor, click Save button
2. Next, opposite click the class in the Class Editor's hierarchical tree and export the classes code to a new temporary file somewhere (keep a backup of your old classes code just in case)
3. Now go to Scripting -> Execute Script in KVIrc and select the file you just exported. KVIrc will try to load the code but fail with the same error it found before. But this time it will give you a line number you can actually find. In my case it said:
[16:16:38] [KVS] Compilation error: Found character '}' (Unicode 7d) where an instruction was expected
[16:16:38] [KVS] In script context "F:/temp/classes.kvs", line 2598, near character 5
[16:16:38] [KVS] Code listing:
[16:16:38] [KVS] 2596 ...
[16:16:38] [KVS] 2597
[16:16:38] [KVS] 2598 }
[16:16:38] [KVS] 2599 }
[16:16:38] [KVS] 2600 ...
[16:16:38] [KVS] Window:
[16:16:38] [KVS] classeditor [ID: 24]
Now I could go to the exported file, line 2598, and see the section of my code that was causing the problem.
Ohthankgoodness.
[ view entry ] ( 619 views ) | [ 0 trackbacks ] | permalink | ( 3 / 662 )