Your First Car


Recommended Posts

  • 3 weeks later...

1994 Red Automatic Mitsubishi Galant.

 

Pros: I like the Japanese products

 

cons: still working on it

 

Current status: Still have it.

 

mitsubishi_galant_1994_supersaloon_at_15

 

History: It was my friend's, a general surgeon, he was not taking care of her.Still Fabric from inside and made of leather.

 

just got new set of tires, gave it a new emperial red colour.

 

N.B: Image is not my car, but same model

I don't remember what the first car I drove was, but it was probably a Buick. When I was 12 my aunt asked me to back her car up because someone was blocked in; I backed up ok but didn't stop so well. I backed over the neighbors garbage bin across the street and crushed it. They were not pleased.

 

The first car I owned was a beat up twenty year old 1974 Datsun 260Z but it needed too much work so I didn't get to drive it very much. The first car I had registered and got to drive on the public roads and also the one I got my license with was an 86 Chevy Nova (which was apparently just a rebadged Toyota Corolla). I finally got my first new car in 1998, a Honda Accord EX.

  • 2 weeks later...

I don't remember what the first car I drove was, but it was probably a Buick. When I was 12 my aunt asked me to back her car up because someone was blocked in; I backed up ok but didn't stop so well. I backed over the neighbors garbage bin across the street and crushed it. They were not pleased.

 

The first car I owned was a beat up twenty year old 1974 Datsun 260Z but it needed too much work so I didn't get to drive it very much. The first car I had registered and got to drive on the public roads and also the one I got my license with was an 86 Chevy Nova (which was apparently just a rebadged Toyota Corolla). I finally got my first new car in 1998, a Honda Accord EX.

 

too many first cars !!!!

  • 4 months later...

The first car I bought was a used '55 Ford with a 272 V8 engine. I changed it from automatic to standard drive, put in a newly rebuilt short block and put a new paint job on it. Then I bought a brand new 1964 1/2 Mustang, 260 V8, with auto transmission. It had the same instrument cluster as the Ford Falcon.

  • 2 weeks later...

The first car that I drove on a regular basis on the road belonged to my girlfriend, but she later became my wife and we lived together for years, so I ended up taking care of it and doing all the maintenance.

 

Red Suzuki X90

 

Pros

Good on gas

4 wheel drive

Stick shift

Trunk was actually pretty big for the size of the vehicle

Glass t-top roof

 

Cons

Was used when we got it and had some damage to one of the headlights

Only two seats and absolutely no room behind them for anything

 

This picture isn't of ours, but it looks just like it.  Just snagged the image from google search.

96-suz-x90-red-amh-f.jpg

 

It was so small and light, that one time as a joke two of our friends picked it up and turned it sideways in our parking space while there were cars on either side of us.

My first car
Black 1979 J10 Pickup (got it around 1995)

33" ground hog tires

6" body lift

6" suspension lift

 

pros
I could driver anywhere and never get stuck

No one had one like it
 

cons
Except for ice which it would get stuck on

Rusty

No AC

Hard to find parts

mods and fixes history
Pioneer deck

Pioneer equalizer
Pioneer speakers

Two 500 W amps

Two 12" subs in one box behind the seat

I was always replacing parts on it

Current Status
When I left the home and was in the military my dad sold it. I can't be mad at him since he bought it for me and it was rusting away anyway. I probably would have got in trouble with it soon or later anyway. I was always four wheeling where I shouldn't.

My first car
Red Mk3 Golf

 

pros
Awesome sound from the aftermarket exhaust

Awesome Reliability being a VW

 

cons
had 100k miles on it when i got it

 

mods and fixes history

Kenwood Stereo

2 * 12" subs in the boot
500 W amp

 

Current Status
Scrapped it at 260k miles :) was still running strong but i got a new car and i was getting more money for scrap than i would selling it

  • Like 1

A 1986 Toyota Corolla 

16128062_large.jpg?v=1

 

That is not the actual car I had but very similar.

 

It was affectionately known as

 

El Bandido Azul

aka

The Blue Bandit

  • Like 1

my first car  , called her "my swallow" :

Suzuki Swift 1997 , 1.3 L engine, Benzine .  (bought it from girlfriend very cheap and I needed something to practice on)

 

pros:

Very nice mileage.

Easy to fix - - - -  very very simple engine

Cheap to fix

No rust (much plastic and good paint)

Small, perfect to practice parkings and sneak around

Agile and cozy

 

cons:

HP was very bad.

No safety

Suspension - had my jaw clenching on every road hole

Small car

 

 

mods:

Harman/Kardon sound system changed to a hardcore Pioneer line

 

not my personal car in pics but extremely close :

 

swift2-fl-2door-hatchback-12.jpg

suzuki__swift_1_3_1995_4_lgw.jpg

  • 1 month later...

First car I drove was a 2001 Peugeot 206 but the first car I owned (and still own) is a E32 BMW 735i (1989)

 

Here's a really tacky picture of it (the only one I had on hand)

 

Bimmer.jpg

 

Pros:

M30 Engine is damn reliable and fairly easy to fix

E32 body has many similar parts to other BMW's of the late 80's to 90's

Plenty of after market and OEM parts

Lots of space & comfortable drive

 

Cons:

It's a damn electrical gremlin!

It likes expensive petrol. Lots of expensive petrol

parts can be expensive to get into New Zealand

 

Bought the E32 off an uncle after he lent it in near pristine condition to his brother... who promptly ran it into the ground. When I received it it was full of mice amongst other things. Slowly working on getting it back to mint condition again. Luckily the head gasket was done recently so no big engine overhauls yet, just need to do the pan gasket, Valve cover gasket amongst a myriad of minor/medium maintenance tasks. Anyone who's done the pan on a BMW will feel my pain (you have to lift the engine clear of the bell housing to undo the bolts at the back of the pan)

 

Other than that it's good fun to work on, basically made worthwhile because I bought it from a family member cheap. Wouldn't be worth it to buy from a dealer in the condition it was in!

wasn't so much a car, more of a 3.5ton lorry

 

millagge wasn't great but no one got in my way. :glare: :woot:

 

parking could be a bit of a pain but that's what loading bays are for :whistle:

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • UK nudity blockers are a looming privacy disaster, we must be able to see the source code by Paul Hill Image via Pexels The UK government, just like many state governments in the US and national governments around the world, has begun going on a bit of a power trip when it comes to digital safety. The major step taken so far is the introduction of the Online Safety Act, which requires users to prove their age to access adult websites (it includes more than this, too). Now, UK PM Keir Starmer is calling on Apple and Google, and presumably other mobile OS makers, to scan phones for explicit images to protect children. This potentially mandatory on-device scanning by vendor-controlled software will create unacceptable harms to individual freedoms and transparency, and introduce massive surveillance risks. In a statement on June 8, the Prime Minister stated that big tech companies, such as Apple and Google, must add features to their platforms, such as iOS and Android, that will detect and block sexually explicit or nude images involving under-18s on phones or tablets. Adults who want to take or send nudes would be required to hand over some form of identification to stop their phone from blocking these pictures, creating unnecessary privacy risks. According to the government, it wants to see these measures implemented within three months; otherwise, the government will introduce legislation to force them to introduce such technology. The legislation will include fines for companies and maybe even criminal liability for tech bosses who do not comply with the measures. In its announcement, the government said that stopping users from taking, sending, or receiving nudes without verifying their age is technically feasible, and pointed to a British firm called SafeToNet, which has made proprietary, closed-source, uninstallable software called HarmBlock and is actively selling a device with it enabled and is working with other OEMs. The fact that this software is closed source is a huge problem because it’s a black box; you do not know what it is doing on your device. The fact that it is unremovable is also a problem because you lose control of a phone that you own. Laughably, the government, just before highlighting SafeToNet, says that companies must introduce such measures “without threatening privacy or collecting any data.” It then says over-18s will still be able to view adult content by providing proof of age… Which sounds to me like data collection. SafeToNet makes some debatable claims about HarmBlock The government’s example software, HarmBlock, is a hugely alarming choice to espouse the virtues of this type of software. SafeToNet claims that HarmBlock is “ethically developed,” but this is the opposite of the truth. This black box software puts digital handcuffs on you if it’s installed in your device, taking away your freedom to control what software runs on your device, as it cannot be removed. It is not even free software, so we cannot inspect the source code to see what it is doing. For all we know, it could be acting maliciously. While that’s unlikely, we can’t verify that it’s not doing that. When Google and Apple do inevitably integrate these features on devices in the UK, they are very likely to be closed-source binaries, which will also be non-auditable. They will also have identity services built into them, which will require at least temporary collection of sensitive identity documents to verify your age. One saving grace for Android users is that this nudity blocker will very likely be implemented within the Google Play infrastructure that’s deeply tied into commercial Android devices. However, anyone with enough determination to throw out Google apps from their phone by flashing a custom ROM could find they regain control over their phone again without these digital handcuffs. Obviously, this is only how I expect Google to implement the feature; if it bakes it into the open-source Android somehow, that would be bad news for anyone looking to escape it. Outside of stripping mobile phone users of their freedom and sovereignty over their devices, these proprietary on-device machine learning or hash-matching solutions cannot be independently audited. This means that hackers could potentially exploit them because security researchers can’t investigate the code, and they could overstep their intended use case and collect even more user data without anybody knowing. We also wouldn’t know if the code is prone to detecting false positives or biased classification, because we can’t see the code. In the government’s announcement, contributing comments from the Internet Watch Foundation keep talking about “on-device protections” as if to say that users don’t need to worry about server-side processing; however, this is misleading, as data could flow from devices for the purpose of updates, remote model changes, telemetry, or server-side matching. We’ve also seen with the Online Safety Act that the government is never content with the laws it introduces; it always wants to expand the controls. If this scanning functionality arrives on devices, it might only block nudes initially, but later governments could pressure vendors for expanded access or use mandated features for other surveillance aims. The introduction of on-device scanners opens the door to massive risks in the future. Once nude blocking becomes normalized, regulators like Ofcom or politicians themselves could push for more controls over people’s devices. Very possible candidates for blocking include hate speech, misinformation, or undesirable political content. Also, there is a chance that once Apple and Google have developed this software, they might attempt to reuse the infrastructure for commercial or foreign requests, putting customers in greater danger. Just the UK's demand for this sets a precedent. What if a dictatorship decides to spy on activists by demanding that Google or Apple implement similar controls? Another concern with this scanning is that it adds compliance costs for businesses looking to get into the mobile operating system space. While Google and Apple dominate the space right now, there are lots of smaller companies creating mobile operating systems too, including community projects with very shallow pockets. How are these smaller competitors supposed to implement sophisticated nudity detectors? Simply put, they can’t. Then the government goes after them, causes them to shut down, and Google and Apple have less competition. Image via Aurora Store For us users who value sovereignty over our technology, this development will force us to seek freedom-respecting alternatives. The simplest path forward will likely be to install a custom ROM on an Android device; however, kicking Google off the phone with its black box nudity blocker could also make it harder to access apps such as banking apps, which tend to need you to pass Google's integrity checks. Thankfully, Google Play Store apps can still be obtained by storefronts such as the Aurora Store, but it just adds to the friction. To be fair to those pushing this measure to protect children, I think it will be reasonably effective, but people will still try to find ways around it, just as they’ve done with age gates on adult websites introduced under the Online Safety Act. In the effort to find circumvention methods, it could lead users to join riskier platforms that introduce new dangers. This effort also diverts resources from proven interventions such as law enforcement cooperation, targeted investigations, education, and support services to broad technical controls that have uncertain effectiveness (due to their newness). If the government is set on introducing such tools, then there ought to be safeguards in place. Any mandated code should be released as free software so that it can be audited, and the binaries should be reproducible builds so that the public knows nothing has been tampered with in the code used to create the binaries shipped out. Ideally, these tools should also be voluntary, opt-in, and even community-run. This would also allow people to have full control over their hardware while allowing parents to flip a switch to turn on these protections for children, with the knowledge that the code being run is doing exactly what it says on the tin, and nothing nefarious, like a black box solution could be doing. The government should also have a narrow legal scope where this technology stays with blocking nudes and not spreading to blocking political opinions, hate speech, and so on. Ideally, any implementation should avoid identity-linked age verification to keep user data safe, and matching should be done locally with no server telemetry to ensure it is truly on-device. While I do understand that stakeholders such as parents want to keep children safe, the potential for abuse with this type of software is colossal. It would entrench black-box surveillance and take away our freedom to use our devices as we want. There is also the acute risk that the government will demand this surveillance be expanded to block other activities, which could be particularly dangerous. If you are in the UK and don’t wish to see these measures implemented, it is still possible to write to your MP, which could lead to some better safeguards being introduced before it’s too late. Once we get more technical information about how this will be implemented, then we will be able to see if de-Googling Android devices will bypass this measure. For anyone with an iPhone, there is zero chance that you’ll be able to take off these handcuffs because Apple doesn’t let you mess with your software.
    • I'm reading the reports as EU rejecting Apple's proposal because Trusted System Agent would be an intermediary offered to third party AI's (this article is also worded as such) but Siri AI itself would not pass this intermediary. This would cause a situation where Siri AI would have more direct system access and offer it an unfair advantage. (speaking from EU regulator perspective here) Apple is citing security issues with doing what EU asked for, and I think this also supports this theory, because truly direct system access like Siri AI would make it impossible to control third party AI's running on the devices and e.g. reign them in via adjustments to Trusted System Agent. So, I _think_ this is the sticking point right now: EU saying they need to be on equal footing as Siri AI, Apple saying they can't be because Apple only trusts their own AI. Apple could of course be leaning a bit extra hard towards this because they're biased in terms of excluding competitors. One method to find an agreement would be to have Siri AI also run through Trusted System Agent and treat it as untrusted. This kind of defensive architecture design (especially when involving an AI) would honestly not be a very bad idea from a sheer engineering standpoint. But then Apple would need to swallow their pride and adapt worldwide due to EU, and make perhaps major updates delaying Siri AI once more.
    • I have not even heard of that game. will take a look
    • Chasys Photo 5.41.01 by Razvan Serea Chasys Photo is a suite of image editing applications including a layer-based image editor with adjustment layers, linked layers, timeline and frame-based animation, icon editing, image stacking and comprehensive plug-in support (Chasys Photo Editor), a fast image viewer (Chasys Photo Viewer) and a fast multi-threaded image file converter (Chasys Photo Converter) , with RAW image support in all components. It supports the native file formats of several competitors including Adobe Photoshop, Affinity Photo, ArtWeaver, Corel PhotoPaint, FireAlpaca, GIMP, Krita, Paint.NET, PaintShop Pro and Pixlr, and the whole suite is designed to make effective use of multi-core processors, touch-screens and pen-input devices. Designed under the mantra of “unique, flexible and powerful”, Chasys Photo takes a radically different approach to image editing with the aim of opening up new possibilities for those who dare to be different. Chasys Photo key features: Free-style layering with blending modes Adjustment layers with multiple adjustments per layer Linked layers (a.k.a Linked Smart Objects) Composite, Image List, Frame Animation and Object Animation image modes Animation, both frame-based and object-based (timeline animation) Animation Composer engine Image Stacking for noise reduction, super-resolution, etc. Tablet/Pen-input/Stylus support with pressure control Touch-screen support with gestures including pitch-to-zoom and multi-finger panning Support for the native formats of Adobe Photoshop, Affinity Photo, ArtWeaver, Corel PhotoPaint, FireAlpaca, GIMP, Krita, Paint.NET, PaintShop Pro and Pixlr Support for common formats such as JPEG, animated PNG, animated GIF, TIFF, PICT, WebP, HEIF, DDS, JPEG-2000, JPEG-XR, JPEG-XL, AVI video, etc. Support for the OpenRaster interchange file format and rare formats such as QOI, MNG/JNG and DPX Support for older formats such as PPM/PGM/PBM, PCX/DCX, PCD, TGA, COKE, etc. Comprehensive Camera RAW file support with live adjustment Extensive plug-in support with streamlined SDKs Support for Photoshop Filter Plug-ins (.8BF) Advanced printing and scanning engines PDF document generation Icon and cursor editing, import and export, including Vista-style and Mac-OS icons Screen Capture, including Video Screen Capture with multiple triggering modes Video capture from devices (e.g. TV/Video) Supports multi-core processors, High-DPI displays and Multiple Display setups Integrated File Browser, Bluetooth OBEX and in-built utilities (Calculator, Notepad) Shell integration with thumbnails and conflict detection Unlimited Undo/Redo and Asynchronous Auto-Save, with Just-in-time memory compression to save space Fully re-editable text with advanced styling and effects (TextArt) Full alpha channel through out the workflow with Alpha protection (a.k.a. transparency protection) Multiple language support with user-editable language files and translation assistant (Chasys Photo Language Studio) Anti-aliasing and super-sampling support in tools and paths* Smart-resizing (similar to seam-carving) Best-in-class post-edit heuristics anti-aliasing engine Physical measurement specification with display size detection via EDID Uses the latest CD5 specification with animation and multi-resolution Super-fast internal graphics engine (JpDRAW2) Full UNICODE support in all components Metadata save, restore and scale to imitate vector art Configurable Guides and Grids with Snap-to-Grid Smart-dither to custom palette Asynchronous preview rendering engine Pantone equivalent palettes for PMS 100 to 814-2x Automatic color naming ... and many more! Chasys Photo 5.41.01 changelog: New Features Layered images with multiple pages (Composite/Multi-page) Additional templates to support template-centric workflow New Layer Blend Mode: Inverse Luma Mask Horizon detection in Rotate Transform Cropping option when importing video Orientation options in QR Code Generator plug-in Solved angle ambiguities (CCW versus CW) Internal Improvements Improved graphics engine (JpDRAW2™ v26.05) Improved CD5 codec (v4.10, improved ACSC compression) Improved interpolation when downsizing images Improved motion detection in Video Capture Slightly lower memory usage (RAM is getting expensive!) File Support and Bug Fixes Improved PXZ file support (placeholders, blanks) [bug-fix] Memory leak in flt_JPEG.dll Download: Chasys Photo 5.41.01 | 46.1 MB (Freeware) View: Chasys Photo Home Page | Wikipedia Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!