Home › Archive for Apple › Page 5

Apple

OS-X on ARM, opens up the world.

Posted on by

With the advent of the iPhone, comes the notion that OS-X now runs on ARM, the chip powering the iPhone. Something more interesting than that notion, is that OS-X now runs on an ARM chip inside an embedded device! Treo, Palm and many smart phones with windows mobile 5 and PDA’s are all running ARM cpu’s. That means OX-X running on just about anything. It may also be the reason that third party apps will not run, as there is no ARM/OS-X development environment (I’m a registered Apple developer). At best you need a compiler in the current developer package that can compile an ARM application. The current duel compile app (intel/PPC) could be used to deploy such a thing, but in a small embedded system would be wasting too many resources in that environment. Wait for for a Appet development package for ARM, then you will see third party apps.

Then wait for an applet to switch Mobil networks. 😉

VPN tcpdump assistance required

Posted on by — 2 Comments ↓

I’m still battling L2TP VPN connection issues, and at the suggestion of one of my readers I’ve done a series of TCPDUMP runs and they all boil down to the one below.

tcpdump: listening on en1, link-type EN10MB (Ethernet), capture size 96 bytes
20:24:27.580117 IP (tos 0x0, ttl 64, id 17897, offset 0, flags [none], length: 188) 192.168.23.2.isakmp > vpn.office.com.isakmp: isakmp 1.0 msgid cookie ->: phase 1 I ident: [|sa]
20:24:27.803567 IP (tos 0x0, ttl 59, id 0, offset 0, flags [none], length: 164) vpn.office.com.isakmp > 192.168.23.2.isakmp: isakmp 1.0 msgid cookie ->: phase 1 R ident: [|sa]
20:24:28.094352 IP (tos 0x0, ttl 64, id 17898, offset 0, flags [none], length: 276) 192.168.23.2.isakmp > vpn.office.com.isakmp: isakmp 1.0 msgid cookie ->: phase 1 I ident: [|ke]
20:24:28.653665 IP (tos 0x0, ttl 59, id 0, offset 0, flags [none], length: 256) vpn.office.com.isakmp > 192.168.23.2.isakmp: isakmp 1.0 msgid cookie ->: phase 1 R ident: [|ke]
20:24:29.290106 IP (tos 0x0, ttl 64, id 17901, offset 0, flags [none], length: 1428) 192.168.23.2.ipsec-msft > vpn.office.com.ipsec-msft: UDP, length: 1400
20:24:30.224387 IP (tos 0x0, ttl 59, id 0, offset 0, flags [none], length: 1420) vpn.office.com.ipsec-msft > 192.168.23.2.ipsec-msft: UDP, length: 1392
20:24:30.657375 IP (tos 0x0, ttl 64, id 17903, offset 0, flags [none], length: 100) 192.168.23.2.ipsec-msft > vpn.office.com.ipsec-msft: UDP, length: 72
20:24:32.667205 IP (tos 0x0, ttl 64, id 17906, offset 0, flags [none], length: 1428) 192.168.23.2.ipsec-msft > vpn.office.com.ipsec-msft: UDP, length: 1400
20:24:34.824612 IP (tos 0x0, ttl 59, id 0, offset 0, flags [none], length: 1420) vpn.office.com.ipsec-msft > 192.168.23.2.ipsec-msft: UDP, length: 1392
20:24:35.829802 IP (tos 0x0, ttl 64, id 17910, offset 0, flags [none], length: 1428) 192.168.23.2.ipsec-msft > vpn.office.com.ipsec-msft: UDP, length: 1400
20:24:36.504857 IP (tos 0x0, ttl 59, id 0, offset 0, flags [none], length: 1420) vpn.office.com.ipsec-msft > 192.168.23.2.ipsec-msft: UDP, length: 1392
20:24:38.556036 IP (tos 0x0, ttl 64, id 17914, offset 0, flags [none], length: 1428) 192.168.23.2.ipsec-msft > vpn.office.com.ipsec-msft: UDP, length: 1400
20:24:41.270765 IP (tos 0x0, ttl 64, id 17918, offset 0, flags [none], length: 1428) 192.168.23.2.ipsec-msft > vpn.office.com.ipsec-msft: UDP, length: 1400
20:24:44.272501 IP (tos 0x0, ttl 64, id 17922, offset 0, flags [none], length: 1428) 192.168.23.2.ipsec-msft > vpn.office.com.ipsec-msft: UDP, length: 1400
20:24:47.276414 IP (tos 0x0, ttl 64, id 17926, offset 0, flags [none], length: 1428) 192.168.23.2.ipsec-msft > vpn.office.com.ipsec-msft: UDP, length: 1400
20:24:50.277506 IP (tos 0x0, ttl 64, id 17930, offset 0, flags [none], length: 1428) 192.168.23.2.ipsec-msft > vpn.office.com.ipsec-msft: UDP, length: 1400
20:24:53.285464 IP (tos 0x0, ttl 64, id 17934, offset 0, flags [none], length: 1428) 192.168.23.2.ipsec-msft > vpn.office.com.ipsec-msft: UDP, length: 1400
20:24:56.287335 IP (tos 0x0, ttl 64, id 17938, offset 0, flags [none], length: 1428) 192.168.23.2.ipsec-msft > vpn.office.com.ipsec-msft: UDP, length: 1400
20:24:59.290376 IP (tos 0x0, ttl 64, id 17942, offset 0, flags [none], length: 1428) 192.168.23.2.ipsec-msft > vpn.office.com.ipsec-msft: UDP, length: 1400

So if the there are any brainier geeks out there that can point to the problem, I’d be grateful.

Apple Mac OS-X L2TP VPN Sucks

Posted on by — 10 Comments ↓

I come to the conclusion that the L2TP VPN native to OS-X sucks. Besides the fact that it sucks, it doesn’t connect to anything. It doesn’t even make the attempt to connect. I have no idea what it’s doing when it spinning that wheel, but it sure doesn’t connect. I have removed routers, and taken down firewalls, standing naked on the internet and still nothing, even dialup, nothing.

It’s no wonder that Apple is never used in business, they won’t communicate with the windows, linux or unix systems.

If you have ideas, leave them in the comments.

The one great reason to avoid Zune

Posted on by — 2 Comments ↓

In this article hyping Five Reasons Why The Microsoft Zune May Succeed , they give the one greatest reason not to ever buy a Zune

… but the next generation Zune will be even better. Why? Because Microsoft is developing that one entirely in-house. As we saw from just about every product they’ve put out, the second or third iteration is when they get things right. By half-skipping over the painful first-gen by using Toshiba, Microsoft may just shortcut their way into a great player.

The trick here is that if people find that the “Painful” first generation is painful, and that the real Zune isn’t for one or two more generations. Then no one will buy the first generation Zune, there will be no Zune community (one of the other points) and Zune will fail.

It took MS two years to get to windows 3.11, it too 3 years for MS to get to XP service pack 2. And second and third generation Zune is at least that far in the future.

The easy recomendation here is, save your money, or buy something else (an iPod comes to mind). Save yourself the ‘pain’ of being a MS Beta tester for Zune.

Mindless reporting, Scare Tactics

Posted on by

It’s almost as if no one in the Media, or for that matter, any reporter, makes any connections with the facts. As an example:

Connecting these two articles,

Mac OS vulnerabilities increased 200 percent McAfee rains on Apple’s smug parade

and again

Cold water thrown on Apple TV claim

Leave it to McAfee to rain on those new television commercials Apple Computer is running about its virus-free computing.

and this article?
Vista to hit anti-spyware, firewall markets

New security features in Windows Vista will largely eliminate the need to run separate antispyware or firewall software, according to a new analyst report.

Spyware-killing Vista could take out rivals

The first two articles, while feeding on themselves, never makes the connection that McAfee, or for that matter any anti-virus company is facing elimination at the hands of the Microsoft Monopoly Monster. And that for them to survive they, like President Bush, must find a new enemy, and a new platform that needs their protection. It has very little to do with Apple needing virus protection. And everything to do with scare tactics as a marketing tool.

The Stockmarket as Reality

Posted on by — 3 Comments ↓

I always love this Microsoft delays launch of Vista and Apple Stock price drops. With this kind of reality, it doesn’t matter how good Mac’s are or how much better OS-X is (now and in the Future) than Vista. If Vista fails to ship, Apple loses.

It’s like if the sun does not rise, neither will the moon. What kind of people trade stocks anyway. Apple will be making a killing on the Vista delay, heck, with Vista out of the running for the fall Christmas season, there will be only one computer to buy for the back to school crowd?

MacTel FireWire

Posted on by

I’m constantly amazed about all the fuss about only one FireWire connector on a Laptop, iBook, or PowerBook. It just speaks to the ignorance about the difference between USB 2.0 and FireWire 400/800. USB is a one to one serial connector, Firewire is a Bus connection much like SCSI only serial. Therefor you can connect up to 72 devices on a daisy chain. And in fact most FireWire devices are built Daisy chained. USB must be hubed together. FireWire 800 supports Firewire 400 devices, and can do so at the same time. USB when connecting 1.1 and 2.0 on the same port, slows down to the slowest device on the link.

So having only one FireWire port on a Laptop is NOT the same as having only one USB port.

Apple DRM

Posted on by

Again I agree with Daring Fireball about the TPM chip in the Mactel developer systems. And I’ll say again, what makes you think that the CPU or any other part of the Mactel production systems will be like a generic Dell PC?

Not going to happen!

Mac OS-X.4 upgrade

Posted on by

I Just recently upgraded my old first generation iMac (Flat panel, 800Mhz) and I have to admit I’ve been lazy. I have never run ‘disk permissions repair’ or ‘disk repair’ in the three plus years I have used this Mac. This is mostly as there appeared to be nothing wrong enough to use these tools. I started out with 10.2, upgraded through 10.3.9, but when I tried to move to 10.4, it failed citing ‘software errors’

So I actually had to try a ‘permissions repair’, no problem, it found a couple miner issues and fixed them. Then came the ‘repair disk’ under first aid, bad news, it could not repair the disk. And I thought, S__t I have to back it up. Good thing I have this external Maxtor, and I started a full backup. 20 Hours later it finished. Fearing the worst, I started a cleanup and moving some of the my important files, (iTunes songs, ect) to DVD-Roms. When I started to clean up some of my Virtual PC disk images (version 5) I had a disk copy failure on an image file of a Lycoris install I had created for testing. I finally managed to delete it, and got inspired to try the disk repair again, and bingo, it fixed the problem.

Now if the disk repair application could have told me I had a bad file, I could have saved a lot of time, heartburn and grey hair and I could have just removed it. It wasn’t that hard in my opinion, so why didn’t the disk repair just not offer to remove the offending file. I have no clues.

Other than that, the install was easy. And I’m a bit wiser. Backups are good, backups are wise.