le nubian, in my experience, installing a wireless card in a desktop is relatively painless. (Getting the card to work after installed may involve some pain, but not so much that I'd advise against you doing this yourself.)
Wait. People? She eats people? 'To Serve Man.' It's 'To Serve Man' all over again.
Gunn ,'Power Play'
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!
shrift - Mar 20, 2007 5:32:31 am PDT #937 of 25496
"You can't put a price on the joy of not giving a shit." -Zenkitty
esse - Mar 20, 2007 5:58:46 am PDT #938 of 25496
S to the A -- using they/them pronouns!
Theo, that should be no problem here.
le nubian - Mar 20, 2007 7:49:34 am PDT #939 of 25496
"And to be clear, I am the hell. And the high water."
okay buffistas, I bought the card, should be here next week, I'll let you know if I kill my machine while trying to install this card!
DCJensen - Mar 20, 2007 8:41:24 am PDT #940 of 25496
All is well that ends in pizza.
hoo boy!
Computer technician accidentally wipes out info on Alaska's $38 billion fund
That is what happened to a computer technician reformatting a disk drive at the Alaska Department of Revenue. While doing routine maintenance work, the technician accidentally deleted applicant information for an oil-funded account — one of Alaska residents' biggest perks — and mistakenly reformatted the backup drive, as well.
There was still hope, until the department discovered its third line of defense, backup tapes, were unreadable.
sumi - Mar 20, 2007 8:42:06 am PDT #941 of 25496
Art Crawl!!!
Oopsy.
§ ita § - Mar 20, 2007 8:52:32 am PDT #942 of 25496
Well not canonically, no, but this is transformative fiction.
Jesus fuckers. There are protocols, people! And wouldn't that be covered by some sort of regulatory board that would audit and make sure shit is backed up properly, above and beyond the department itself?
The technician is in hot water, but everyone above him in the org chart should be slapped around severely too.
Theodosia - Mar 20, 2007 8:57:36 am PDT #943 of 25496
'we all walk this earth feeling we are frauds. The trick is to be grateful and hope the caper doesn't end any time soon"
ita, that's from the state with the Senator who believes that the Internets are a series of tubes.
But yeah, damn sure there are protocols, and good reasons not to skip on them.
DXMachina - Mar 20, 2007 9:08:33 am PDT #944 of 25496
You always do this. We get tipsy, and you take advantage of my love of the scientific method.
At least they had their hard copies.
There are protocols, people! And wouldn't that be covered by some sort of regulatory board that would audit and make sure shit is backed up properly, above and beyond the department itself?
According to department staff, they now have a proven and regularly tested backup and restore procedure.
The technician is in hot water, but everyone above him in the org chart should be slapped around severely too.
Former Revenue Commissioner Bill Corbus said no one was ever blamed for the incident.
"Everybody felt very bad about it and we all learned a lesson. There was no witch hunt," Corbus said.
Governments jobs are the best...
§ ita § - Mar 20, 2007 9:15:39 am PDT #945 of 25496
Well not canonically, no, but this is transformative fiction.
they now have a proven and regularly tested backup and restore procedure.
It's 2007. Now they have one? Hopefully this'll prompt other groups to test their disaster recovery procedure.
At my last job, every system owner was required to test both disaster recovery and business continuity for not just data but business processes. So if hard copy it was, you had to show the process for resuming business that way too. Once a year. Because the Feds could come looking at any time.
Quis custodiet ipsos custodes?
flea - Mar 20, 2007 9:17:53 am PDT #946 of 25496
information libertarian
At my job, in a University library, we had a hardware failure and then discovered that the backup procedure had failed and nobody had noticed. We lost 6 weeks of work by ca. 120 people. Nobody was fired. I was pretty shocked.