If it were my office, my guess would be your network profile isn't being properly updated, and you'd probably need an IT administrator to sort it out.
You're probably right. Le sigh.
Anya ,'Get It Done'
Got a question about technology? Ask it here. Discussion of hardware, software, TiVos, multi-region DVDs, Windows, Macs, LINUX, hand-helds, iPods, anything tech related. Better than any helpdesk!
If it were my office, my guess would be your network profile isn't being properly updated, and you'd probably need an IT administrator to sort it out.
You're probably right. Le sigh.
I got mine. I'm waiting for everyone else to get theirs.
I've got mine. Scola and I have even chatted with ours.
Without a separate microphone (which we don't have), it's useless for video conferencing because you both just end up smiling at each other saying "What? I can't hear you..."
I've found the built in mic in my iSight to be quite good.
What the heck is ASCII character 11 (vertical tab) typically used for?
Like most of the control characters, it had a purpose when ASCII was used for mechanical teletype machines, but it's pretty much useless now.
Like most of the control characters, it had a purpose when ASCII was used for mechanical teletype machines, but it's pretty much useless now.
That's what I would have guessed.... except our client somehow got a lot of them in the memofields of a database we're working on.
Which brings me to my next question. I need an XSL file to be applied to data being exported to XML (in Access) that will get rid of stupid characters like that (Excel errors on ASCI 11). I'm sure I can RTFM and figure it out, but if anyone knows off the top of their heads how to do this....
eta: needs to work with any arbitrary XML document, as the XML depends on what fields the user selects and which query is used (out of a dozen).
According to the XML specification, the only control characters that are allowed in XML documents are carriage return (13), linefeed (10) and horizontal tab (9).
Thanks, Tom, that helps.
HBO is actively poisoning the BitTorrent downloads of the new show Rome. In addition to an older tactic of offering bogus downloads that never complete, HBO is now obstructing the downloads offered by other people. BitTorrent downloads are peer-to-peer, but the peers are introduced to each other by a tracker ("you're looking for Rome Season 1 Episode 2, talk to 127.0.0.1"). HBO runs peers that tell the tracker they have all the chunks of the show, but then send garbage data when a downloader requests a chunk. The downloading client can detect that it's garbage and will try another peer for the chunk, but the end result is that it takes much much longer to download shows.
Oooh. My boss said that it's the client's fault their data is screwey, so they have to fix it. So, not my problem.
The downloading client can detect that it's garbage and will try another peer for the chunk, but the end result is that it takes much much longer to download shows.
And so the arms race begins....
the end result is that it takes much much longer to download shows
Great. The big corps are DDOSing now. I'd like a sane world, please?