?

Log in

No account? Create an account

fuckingmotherfuckshit // techie woes - Lograh — LiveJournal

(Recent Entries) (Archive) (Friends) (Profile)

(customize)

Friday, 28.Jan.2005

19:38 - fuckingmotherfuckshit // techie woes

Previous Entry Share Flag Next Entry

so, in this house we have two desktop computers and one laptop. we are using a wireless router with broadband and got wireless cards in the lot of 'em. while not the most stable of solutions, it seems to work well enough most the time.

except now.

this Fucking laptop I use has decided that it can't get on the wireless network anymore. It sees the network just fine, but can't actually connect for shit. so, in what has got to be the absolute perfect definition of WTF, in a house where two windows machines with third-party wireless cards slapped in (one of them an emachine, the perfect example of "rock-bottom components") are working fine, a motherfucking APPLE LAPTOP (with built-in wireless, from apple) needs to use a fuckingcat5 to get online. Fucking APPLE!!!!!!! The company that built its entire reputation on "it just works" is the only piece of hardware in the house that can't get on the wireless. It worked just damn fine earlier this week -- hasn't worked for shit the past three days.

fuck.

and, I go to our network software depot at work (connected through da 'net) planning on grabbing the isos for the OSX discs (for to burn copies here and do a re-install this weekend) and turns out that while we have directories created for OSX, the actual discs haven't been ripped yet. shit. So looks like I'll be walking on in to work this weekend to grab the discs from our physical library.

(6 comments | Leave a comment)

Comments:

[User Picture]
From:noisepimp
Date:3:59 29.Jan.2005 (UTC)
(Link)
The motto should be "It just works, or it doesn't." Unlike IBM-architecture hardware, which typically can be ghetto-rigged to work somewhat but seldom achieves the ideal performance, Mac hardware tends to either work flawlessly or not at all.
(Reply) (Thread)
[User Picture]
From:lograh
Date:4:07 29.Jan.2005 (UTC)
(Link)
true dat, true dat... I've recovered from tons of HDD crashes on wintel machines, and only about one on a mac. That mac one was far worse than any of the wintel crashes, easy.

When apple hardware goes bad, it doesn't dick around with the idea -- it goes all the way. Wintel systems will pussyfoot around the concept of going bad, but never quite take it as far as apple shit will all the time.
(Reply) (Parent) (Thread)
[User Picture]
From:urbeatle
Date:4:36 29.Jan.2005 (UTC)
(Link)
turn on interference robustness.
repair disk permissions.
test in a new user.
and if it doesn't work in either user, yank /library/preferences/whatever_the_heck_the_network.plist is called.
(Reply) (Thread)
[User Picture]
From:lograh
Date:15:42 29.Jan.2005 (UTC)
(Link)
thanks for the tip, I'll give it a try later today (gotta run right now).
(Reply) (Parent) (Thread)
[User Picture]
From:gravilim
Date:7:16 29.Jan.2005 (UTC)
(Link)
there's all kinds of fun stuff on search.info.apple.com. and applecare would probably be happy to help you too. ;)

you act like it's impossible for a mac to go down, ever. nothing is infallible. :P
(Reply) (Thread)
[User Picture]
From:lograh
Date:15:42 29.Jan.2005 (UTC)
(Link)
oh, I know everything is fallible and I never assumed it would work without problems. In fact, I thought I made it clear that I know macs go down sometimes. What I don't like is the way in which it goes down. Wintel machines are constantly bitching about something and never work 100%, where apple machines will work near perfectly while there are minor problems only to break completely once the number of minor problems passes a certain point.

I actually like having the machine keep a running tally of things that are wrong but not lethal.
(Reply) (Parent) (Thread)