Displaying 6 results from an estimated 6 matches for "lobotomized".
2009 Jul 02
2
Changing the PATH from the command line
...ve looked at the FAQ and googled a good bit. I found
a document where someone said I can't do this and must
change the PATH in the through the registry. That reference
was several years old so I'm hoping it was either wrong
or out of date.
I can't believe the command line has been so lobotomized !!
Ray
2007 Jan 14
1
fixed point speex encoder targeted to embedded devices
Hi!
I have heavily lobotomized libspeex, resulting in a fixed point
encoder for 8khz sampling rate and 32 bit signals.
More information and download:
http://magwas.freeblog.hu/archives/2007/01/14/2079127/#a2079127
(I am not in this list, please comment there, or cc me.)
1999 Nov 24
1
Release 1.2pre15 coming soon?
Given that we've had several major patches of late, is there any chance
that pre15 could get released within the next couple of days?
Thanks,
David
--
David W. Rankin, Jr. Husband, Father, and UNIX Sysadmin.
Email: drankin at bohemians.lexington.ky.us Address/Phone Number: Ask me.
"It is no great thing to be humble when you are brought low; but to be humble
when you are
2008 Dec 05
2
polycom no menu
Was messing with a polycom 501 and changed the IP from dhcp to static. Working with a user remotely. Now, the user says the phone does not show anything on the LCD and does not respond to any buttons.
When rebooting, there is text shown as it proceeds. ??
Is there a way to reset this to a default?
Does not respond to ping on the address we set.
joe a.
2008 Aug 22
1
Yum Issues with Dev groups
Just my luck,
None of my CentOS systems or my Fedora systems can #yum groupinstall "Development Tools" "Development Libraries"?
Both are having dep issues? Is that a coincidence, or what's going on?
The CentOS boxes all complain:
--> Processing Dependency: glibc-common = 2.5-18.el5_1.1 for package: glibc
Error: No Package Matching glibc.i686
jlc
2002 Jan 20
1
Failed to boot from one particular system
Hi all,
Last month we received the following mail from one of our users;
apparently, his system does not set register DL to the boot drive
number, so the rest of the process fails.
Unfortunatelly, I have not been able to contact the sender of this
mail, so I have not been able to gather more info about his system.
I will continue trying to contact him.
Does anyone know how could this be solved