Not only did you completely miss the point (the entire post was a Carlin bit) but you proved the points too. Your wonderful little dictionary definitions? NONE are the #1 listing. As we know from the bit, there's a reason they're not #1 -- they're not right!
Oof. True if and only if the signals are unencrypted. The point at which you begin decrypting signals is the point where it becomes illegal.
In fact, since that's the law for satellite communication (in the US, anyway) I would think that WiFi laws would be similar -- open APs are broadcasting unencrypted into your property, therefore you have legal right to make use of the signal. WEP/WPA cracking is where it stops being legal.
I should have specified. Mine is late 2007 MacBook (GMA X3100). FWIW, I noted more OpenGL capabilities after the 10.5.3 update. I think, for the X3100, the 10.5.3 update brought it to the same level as their fancy DirectX 10 Vista driver.
As for GMA950 (iirc, that's in first gen MacBoook) I can't really say.
Also, since yours is first-gen, it's 32-bit Intel; maybe a 32 versus 64-bit problem?
Oof I hate to reply to myself, but so far my experience has been that (1) ATi machines get the smaller update and (2) said machines seem to take an extremely long time to install.
MacBook (Intel graphics) got the 400M update, and sped right through it. iMac (ATi) got the 200M, and seemed to die on "Running Installer Script".
Anybody got an nVidia Mac to report in here? Anybody else seeing the same thing?
I never had problems before, however after 10.5.3 I initially could not get an IP from my AP. Another reboot fixed it though. Maybe the update cleans/breaks something, and that break, when detected, gets cleaned on reboot? Seems like they're forcing all airport settings to reset in one way or other.
Interesting, I had a similar experience. Moreover, the machine that got the 200M update took *forever* to install, but the 420M update machine went blazing quick.
By any chance, are your two 198M macs running with ATi Graphics?
Re:It's as if a thousands hands screamed out in pa
on
iMac Turns 10
·
· Score: 1
I hear this all the time, but I never had a problem with the puck. The trick is you cannot try to hold it like a normal mouse. Instead, if you hold it using your fingertips and thumb-tip, it is dead-simple to keep going the right way without cord confusion.
I have no idea what hes on about with the hard-pathed file references.
This used to be much more apparent on earlier NT systems that installed to \winnt rather than \windows. Sure enough, after installing some software, I suddenly had a windows dir, in addition to my winnt dir, created by the software assuming \windows was correct to use.
Further, his overall point there is that it is a programmer problem here; there have been APIs in-place forever to address all "special folders" as tokens.
Ok, now I understand more of what you mean. I will wholeheartedly agree that VB is great for mockups, and strangely it's a great testbed for WinAPI calls.
But still, what happens when the day comes that MS pulls support for VB6? Or is there simply too much inertia in the language to prevent them from killing it?
Indeed, AMDs can run OS X. The main thing Apple did to prevent this was to put CPUID calls into their binaries. Patch those out and you're running on AMD. (There's more to it than just this, of course, but that's the biggest issue).
Slashdot Mirror
...and enjoyed his past material should look at themselves. Maybe you've become the very thing George satirizes?
A rare gem from the Anonymous Coward
Not only did you completely miss the point (the entire post was a Carlin bit) but you proved the points too. Your wonderful little dictionary definitions? NONE are the #1 listing. As we know from the bit, there's a reason they're not #1 -- they're not right!
The simile/metaphor bit above (which *is* directly from the book) humorously lists two similes, not one simile and one metaphor.
I noticed this back when the book came out, always wanted to ask Mr. Carlin if that was intentional.
Oof. True if and only if the signals are unencrypted. The point at which you begin decrypting signals is the point where it becomes illegal.
In fact, since that's the law for satellite communication (in the US, anyway) I would think that WiFi laws would be similar -- open APs are broadcasting unencrypted into your property, therefore you have legal right to make use of the signal. WEP/WPA cracking is where it stops being legal.
Come on, Frenchie, 'fro ball!
And they made that space-like Tempur material for my bed! YAY!
I should have specified. Mine is late 2007 MacBook (GMA X3100). FWIW, I noted more OpenGL capabilities after the 10.5.3 update. I think, for the X3100, the 10.5.3 update brought it to the same level as their fancy DirectX 10 Vista driver.
As for GMA950 (iirc, that's in first gen MacBoook) I can't really say.
Also, since yours is first-gen, it's 32-bit Intel; maybe a 32 versus 64-bit problem?
You're correct about 10.2.7, and G5 machines *did* have a special 10.2.8, but there was never a 10.2.9.
http://en.wikipedia.org/wiki/Mac_OS_X_10.2
That's exactly why I always hit CMD+V when rebooting from an update... they'll generally print to stdout what's really going on.
Oof I hate to reply to myself, but so far my experience has been that (1) ATi machines get the smaller update and (2) said machines seem to take an extremely long time to install.
MacBook (Intel graphics) got the 400M update, and sped right through it. iMac (ATi) got the 200M, and seemed to die on "Running Installer Script".
Anybody got an nVidia Mac to report in here? Anybody else seeing the same thing?
I never had problems before, however after 10.5.3 I initially could not get an IP from my AP. Another reboot fixed it though. Maybe the update cleans/breaks something, and that break, when detected, gets cleaned on reboot? Seems like they're forcing all airport settings to reset in one way or other.
Correct. It was changed in 10.5.2 specifically.
Hate to be pedantic, but there was no 10.2.9. The 10.2 series stopped at 10.2.8.
Interesting, I had a similar experience. Moreover, the machine that got the 200M update took *forever* to install, but the 420M update machine went blazing quick.
By any chance, are your two 198M macs running with ATi Graphics?
Just like yesterday's test build.
... and it's been that way since last Thursday.
I hear this all the time, but I never had a problem with the puck. The trick is you cannot try to hold it like a normal mouse. Instead, if you hold it using your fingertips and thumb-tip, it is dead-simple to keep going the right way without cord confusion.
I have no idea what hes on about with the hard-pathed file references.
This used to be much more apparent on earlier NT systems that installed to \winnt rather than \windows. Sure enough, after installing some software, I suddenly had a windows dir, in addition to my winnt dir, created by the software assuming \windows was correct to use.
Further, his overall point there is that it is a programmer problem here; there have been APIs in-place forever to address all "special folders" as tokens.
Ok, now I understand more of what you mean. I will wholeheartedly agree that VB is great for mockups, and strangely it's a great testbed for WinAPI calls.
But still, what happens when the day comes that MS pulls support for VB6? Or is there simply too much inertia in the language to prevent them from killing it?
Slight correction... there were MacBook Pros on the market originally with Core Duos (32-bit); it's not just relegated to consumer desktops.
Hahaha nice troll... "good old VB6"
Indeed, AMDs can run OS X. The main thing Apple did to prevent this was to put CPUID calls into their binaries. Patch those out and you're running on AMD. (There's more to it than just this, of course, but that's the biggest issue).
Sorry, that 'special case' was valid, but Hixie got angry about it and confronted Hyatt.
See also http://ln.hixie.ch/?start=1206756775&count=1
CHELMSFORD! I had a feeling as soon as you said "used to be a rotary, and they haven't made a complete circuit".
(That's Chelmsford, MA for anyone else reading)