[Ryan Joseph]

Hey, finally a device where finger-poking the screen will work!
Where do I order?!

[Ryan Joseph]

Hey, finally a device where finger-poking the screen will work!
Where do I order?!

[Kevin Jackson]

Originally Posted by Ed Hansberry

Brad would need a new eVest for this iPAQ. :lol:

Actually, I think the iPaq could wear the vest and Brad could ride along. 8)

[Steven Cedrone]

I love the "Help me inflate the stylus"!

Steve

[busyforever]

Anybody mad at his ipaq?...a person could really punch that thing a couple of times....

[Kati Compton]

Originally Posted by Steven Cedrone

I love the "Help me inflate the stylus"!

Oh, I hear that line all the... um... What were we talking about? ops:

[Fishie]

Originally Posted by Ryan Joseph

Hey, finally a device where finger-poking the screen will work!
Where do I order?!

Not only your finger I presume.

[Steven Cedrone]

Repeat after me: Mind out of gutter, mind out of gutter...

Hover your mouse over the picture... :wink:

Steve

[Kati Compton]

Originally Posted by Steven Cedrone

Repeat after me: Mind out of gutter, mind out of gutter...

Fishie's comment isn't helping.

Originally Posted by Steven Cedrone

Hover your mouse over the picture... :wink:

I know that was the title of the Engadget story! Geez. :P

[ctmagnus]

OT:

I can't access the engadget site atm. I do a traceroute and the first entry I get is 10.247.0.1, an IP I know doesn't exist on my network. But I can ping that IP. Anyone else having this issue?

[Janak Parekh]

Originally Posted by ctmagnus

I can't access the engadget site atm. I do a traceroute and the first entry I get is 10.247.0.1, an IP I know doesn't exist on my network. But I can ping that IP. Anyone else having this issue?

That doesn't mean anything. Cable providers may use private IPs for intermediate routing nodes, and that's perfectly legitimate even though it may not exist in yours. Here's my tracert to Engadget, and 10.20.192.1 isn't an address of mine (I'm using 172.16.*.* addresses):

C:\Documents and Settings\Janak>tracert www.engadget.com

Tracing route to engadget.com [206.252.131.172]
over a maximum of 30 hops:

  1     3 ms     3 ms     3 ms  172.17.0.1
  2    11 ms    12 ms    15 ms  10.20.192.1
  3    12 ms    13 ms    11 ms  dstswr2-vlan2.rh.rslyny.cv.net [167.206.34.34]
  4    12 ms    11 ms    11 ms  r4-ge10-1.mhe.hcvlny.cv.net [167.206.34.5]
  5    13 ms    14 ms    17 ms  65.19.104.17
  6    15 ms    12 ms    13 ms  R2-srp1-0.wan.hcvlny.cv.net [65.19.104.2]
  7    13 ms    15 ms    12 ms  r1-srp5-0.in.nycmny83.cv.net [65.19.96.53]
  8    15 ms    13 ms    14 ms  pos5-2.pr1.lga1.us.mfnx.net [167.206.8.154]
  9    16 ms    13 ms    13 ms  so-4-3-0.cr1.lga1.us.above.net [64.125.30.185]
 10    14 ms    12 ms    14 ms  pos0-0.er1a.lga1.us.above.net [64.125.28.190]
 11   108 ms   302 ms   223 ms  208.184.36.230.dti.net [208.184.36.230]
 12    20 ms    13 ms    13 ms  sharedfw-pri-ext.core.logicworks.net [206.252.135.211]
 13    17 ms    13 ms    13 ms  blue2.frankensite.com [206.252.131.172]

Trace complete.

What it suggests is that your cable provider is having issues reaching the next hop.

--janak