Willow: Something evil-crashed to earth in this. Then it broke out and slithered away to do badness. Giles: Well, in all fairness, we don't really know about the "slithered" part. Anya: No, no, I'm sure it frisked about like a fluffy lamb.

'Never Leave Me'


Buffistechnology 3: "Press Some Buttons, See What Happens."

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!


aurelia - Apr 04, 2007 8:42:45 am PDT #1155 of 25496
All sorrows can be borne if you put them into a story. Tell me a story.

Daniel, if you are interested in my G3 Powerbook w/ dead hard drive shoot me an e.


DebetEsse - Apr 04, 2007 1:29:06 pm PDT #1156 of 25496
Woe to the fucking wicked.

Question: What's more fun than re-installing an operating system?

Answer: Not much!...Oh wait, no. Going home. Going home is a lot more fun than re-installing an OS.


Jessica - Apr 05, 2007 7:02:26 am PDT #1157 of 25496
And then Ortus came and said "It's Ortin' time" and they all Orted off into the sunset

I'm having a weird problem with one of my Macs at work -- the DVD Player software is refusing to recognize or play DVDs. No matter what we put in the drive (DVD data discs, playable DVDs created on this same Mac, playable DVDs created elsewhere), it loads in the finder as "Untitled CD" and refuses to acknowledge the presence of any media.

We've run all the updates we can find, and are currently running DVD Player 4.6.5, which as far as I can tell is the newest version available.

Anyone have a clue what might be causing this or how to fix it? Since we can still create DVDs on this Mac (that will play everywhere else), I'm pretty confident that it's a software issue and not the drive itself.


Kevin - Apr 05, 2007 9:13:06 am PDT #1158 of 25496
Never fall in love with somebody you actually love.

Jess, that's a common problem -- I saw it mentioned the other day. [link]

The Mac I got from eBay on Sunday still hasn't shown up. I'm nervous.


bon bon - Apr 06, 2007 6:20:15 am PDT #1159 of 25496
It's five thousand for kissing, ten thousand for snuggling... End of list.

I have a MSWord puzzler. Why would a document refuse to print? I have a letter that I've printed many times before. One day, I selected the print command, pressed OK and...nothing. I can print other things, just this document, when commanded to print, will not print. I saved it to the document storage system...nothing. Tried other printers...nothing. It just doesn't tell the printer to print, the printer icon doesn't come up or anything. I've tried looking at all the various settings to see if there's something I accidentally checked that says "don't print"-- haven't found it. I've been able to c/p the doc and print that, but has anyone else seen this problem?


Sean K - Apr 06, 2007 6:26:05 am PDT #1160 of 25496
You can't leave me to my own devices; my devices are Nap and Eat. -Zenkitty

About the only thing I can think of is that in the Print dialog box, instead of an active printer, it's being told to print to a file, and dumping copies of itself on the hard drive somewhere. But this:

I saved it to the document storage system...nothing. Tried other printers...nothing.

....makes it sound like you've tried all that.

Other than that, I've got nothing. Sorry, bon.


bon bon - Apr 06, 2007 6:32:26 am PDT #1161 of 25496
It's five thousand for kissing, ten thousand for snuggling... End of list.

That sounded like a very good answer, actually. As far as I know, the only way to print to file is checking a box on the print dialog, and that box isn't checked when it fails to print. If there's another setting, though, that might be it.


Sean K - Apr 06, 2007 6:36:17 am PDT #1162 of 25496
You can't leave me to my own devices; my devices are Nap and Eat. -Zenkitty

The only place I know for sure to do that is the check box in the print dialog. If there's someplace else to do it, maybe somebody else will know.

Oh, what OS are you using?


bon bon - Apr 06, 2007 6:43:59 am PDT #1163 of 25496
It's five thousand for kissing, ten thousand for snuggling... End of list.

XP, this is my work computer.


§ ita § - Apr 06, 2007 6:59:17 am PDT #1164 of 25496
Well not canonically, no, but this is transformative fiction.

In situations where c&p works, I breathe a sigh and pretend it never happened. Word is weird, but I've never had that particular problem.

Hokay. I solved my PostgreSQL "what's the row_id of the last insert?" question two ways--first by issuing a "SELECT currval()" query right afterwards, but have now replaced that with the PostgreSQL extension to INSERT that means you can say:

INSERT INTO table (row_id, row_field1) VALUES (DEFAULT, "This is how we roll") RETURNING row_id

and the insert query returns a row I can grab stuff from. Neat, and I've yet to consider the full ramifications.

Because I can never get enough, I'm now missing a MySQL extension, REPLACE. The difference between

INSERT INTO table (primary_key, rowvalue) VALUES (17, "For Nilly);
and
REPLACE INTO table (primary_key, rowvalue) VALUES (17, "For Nilly);

is that the latter will overwrite a preceding row with the same unique key. Saves me writing a sequence of commands.

Anyone know a 'standard' PostgreSQL way to do that?