Install 'patches' to make IE seem even more buggy than it is. The boss will get sick of the instability and start using FireFox more often. Eventualy he'll agree to switch.
Way back in the day, when a 486dx/66 was *hot stuff*, I had an interesting day. I started by inserting the CPU backwards. It emitted a large puff of smoke and a horrible squealing sound. Surprizingly enough after correcting the CPU orientation it still worked. Later in the day while fiddling with it, I bumped the tower and it fell out the second story window on to a concrete pad. Since it was not screwed together properly, it took the fall rather well, the only casualty being the case (Bent to hell), and the massive-for-the-day 2gig harddrive, which still worked, albeit at less-than-floppy speeds with a horrible click-clack sound every 10 seconds. Recovering my data took 10 days, with the computer living in a cardboard box. I had this bad habit of heating cans of spaghetti-O's on the CPU, but nothing ever came of it (thankfully).
I find, that for low-bitrate mp3's and other such digitaly degraded music, a tube amp is the best thing to sweeten up the sound. I run a low THD amp for everything below 300hz, everything above goes to a nice lil tube amp. Analog distortion does wonders for digitily degraded sound, it adds harmonics and generaly livens up the sound, removing that "flatness" that is otherwise quite hard to get rid of. A motherboard with a tube amp doesn't sound like such a good idea to me though, a shielded external [pre]amp would be a much better choice, tubes are EMI/RFI sensitive, and computers are *NOISY*.
Too late. Voyager is currently running on Nuclear Power, that 20 year life estimate mentioned in the article is actualy when they figure the juice will run out.
Perhaps they are.. But Can you remember 10 phone numbers? If so, you can remember 10 passwords. Once you are up to a certian number of passwords, you can do neat tricks like interleaving them to generate a new password. A simple example would go somthing like this.. You have 10 passwords you know by heart,and you pick two of them:
s3k0Ic$a and f^lPcZtt
You could derive a password such as: sf3^kl0PIccZ$tat
And not have much problem remembering it (alternating chars between two memorized passes)
I'm sure you can think up more tricks. Personaly, none of my self-chosen passwords are written down, Passwords that are chosen for me, however, are a completely different matter. I keep them stored in simple code, on a notepad, in my home office (Nobody ever comes in here..)
Re:Slightly OT But..
on
30-pin SIMMs
·
· Score: 3, Interesting
There is a hole drilled for the wires, power and 10baseT, with a nice rubber gromet installed. It does not get wet or need defrosting, frost-free freezers have a dehumidifying property. I run it there because the largest HD I own suffers from major thermal problems, and does not work properly unless chilled.It does not keep a grocery list(Good idea though..), it is a headless NFS server.
Appropripriately enough, it's hostname is 'penguin'
If you need 30pin SIMMS, slackware 3.x is a good choice. Old software works good on old hardware, my 486/33 I keep in the freezer(Don't ask) is a perfectly useful machine running slack 3.6. I tried slack 7 and it was *sloooow*. It seems to me, as hardware grows more powerful, code becomes less efficiant/more bloated. Ever install Win 3.1 on a modern machine? It's quite fast, for only using mostly 16bits..
SendIP seems to be just what you are looking for: http://www.earth.li/projectpurple/progs/send ip.htm l
Nemesis is also pretty good. There are a variety of "human IP stack" type tools available. I can also reccommend the Net::RawIP PERL module, if you are PERL literate.
I think the best CPU/Motherboard combination for your purposes would be a Socket 7 motherboard with an AMD K6-III+ (note the +) 550mhz. If you set the clock multiplier to 2, you can easily get 600mhz out of it. Being a laptop CPU, it's cooling requirements are low, and you can get away with a 100% passive cooling system(Think: large heatsink, no fan, or a very small/quiet fan). Combine this with a pizzabox case with holes or a screen in the top and sides for ventilation, and a small fanless power supply, and you have a small, very quiet system. You may also want to consider lower RPM hard drives, their not as fast, but are quieter and produce less heat.
I can vouch for that. A Windows machine to handle the really windows-ish stuff, and a slackware box for the heavy lifting is a good, balanced solution., and has worked very well for me in the past.
Oh of course. But porting a DirectX game is damn well near impossible, wheras porting an OpenGL game is much easier, so anything that moves game developers away from DirectX is fine by me.
This is great news. Games written for osX will use OpenGL instead of DirectX, this means that porting them to other operating systems won't be such a chore. With the demise of Loki, it's nice to see somthing positive on the Linux/BSD gaming frontier.
EMACS has a DOS port, and there are packages for EMACS to turn it into a fairly decent GCC IDE. I have no DOS/Win machines, but perhaps you should give it a try.
One of the reasons Slackware is (imho) more stable out-of-the-box is it's general simplicity. Most other distributions have much more complex inner workings and interdependancies. Ever try to configure a RedHat box WITHOUT using any of their config scripts/tools?
The more complex a system becomes, the more opprotunity there is for problems to arise.
Anyone ever hear of KISS? Keep It Simple Stupid!
Most older IP stacks for Apples have a low amount of available sockets, such as 16 or 32. Once those are all being used, the machine can no longer accept connections.. Thus this link suffered instant slashdot. Good job!
What's the deal with XML? It's just a markup language, big deal. Why impliment an RPC system based on XML? You want to see how bloated you can make it or what? I mean, be sensible, RPC can be implimented in much simpler ways without losing any 'features'. Score one more to the bloat god.
Hey, I do it. It's not as hard as you would think. Audit the entire source once the first time you download it, then simply run diffs between that and the new version, look them over, if it's cool install. Once I am satisfied that the original package is OK, auditing upgrades takes anywhere from 5 to 30 minutes, well worth the time for a paranoid bastard like me.
Slashdot Mirror
No it doesn't.. I just did this 5 minutes or so ago. One word: DOH!
Install 'patches' to make IE seem even more buggy than it is. The boss will get sick of the instability and start using FireFox more often. Eventualy he'll agree to switch.
Way back in the day, when a 486dx/66 was *hot stuff*, I had an interesting day. I started by inserting the CPU backwards. It emitted a large puff of smoke and a horrible squealing sound. Surprizingly enough after correcting the CPU orientation it still worked. Later in the day while fiddling with it, I bumped the tower and it fell out the second story window on to a concrete pad. Since it was not screwed together properly, it took the fall rather well, the only casualty being the case (Bent to hell), and the massive-for-the-day 2gig harddrive, which still worked, albeit at less-than-floppy speeds with a horrible click-clack sound every 10 seconds. Recovering my data took 10 days, with the computer living in a cardboard box. I had this bad habit of heating cans of spaghetti-O's on the CPU, but nothing ever came of it (thankfully).
I find, that for low-bitrate mp3's and other such digitaly degraded music, a tube amp is the best thing to sweeten up the sound. I run a low THD amp for everything below 300hz, everything above goes to a nice lil tube amp. Analog distortion does wonders for digitily degraded sound, it adds harmonics and generaly livens up the sound, removing that "flatness" that is otherwise quite hard to get rid of. A motherboard with a tube amp doesn't sound like such a good idea to me though, a shielded external [pre]amp would be a much better choice, tubes are EMI/RFI sensitive, and computers are *NOISY*.
Too late. Voyager is currently running on Nuclear Power, that 20 year life estimate mentioned in the article is actualy when they figure the juice will run out.
Perhaps they are.. But Can you remember 10 phone numbers? If so, you can remember 10 passwords. Once you are up to a certian number of passwords, you can do neat tricks like interleaving them to generate a new password. A simple example would go somthing like this.. You have 10 passwords you know by heart,and you pick two of them:
s3k0Ic$a and f^lPcZtt
You could derive a password such as:
sf3^kl0PIccZ$tat
And not have much problem remembering it (alternating chars between two memorized passes)
I'm sure you can think up more tricks. Personaly, none of my self-chosen passwords are written down, Passwords that are chosen for me, however, are a completely different matter. I keep them stored in simple code, on a notepad, in my home office (Nobody ever comes in here..)
The solution is simple: Filter the ports, chmod -s some stuff, and call it a day.
A camel eh? Hmm.
There is a hole drilled for the wires, power and 10baseT, with a nice rubber gromet installed. It does not get wet or need defrosting, frost-free freezers have a dehumidifying property. I run it there because the largest HD I own suffers from major thermal problems, and does not work properly unless chilled.It does not keep a grocery list(Good idea though..), it is a headless NFS server.
Appropripriately enough, it's hostname is 'penguin'
If you need 30pin SIMMS, slackware 3.x is a good choice. Old software works good on old hardware, my 486/33 I keep in the freezer(Don't ask) is a perfectly useful machine running slack 3.6. I tried slack 7 and it was *sloooow*. It seems to me, as hardware grows more powerful, code becomes less efficiant/more bloated. Ever install Win 3.1 on a modern machine? It's quite fast, for only using mostly 16bits..
SendIP seems to be just what you are looking for:d ip.htm l
http://www.earth.li/projectpurple/progs/sen
Nemesis is also pretty good. There are a variety of "human IP stack" type tools available. I can also reccommend the Net::RawIP PERL module, if you are PERL literate.
I think the best CPU/Motherboard combination for your purposes would be a Socket 7 motherboard with an AMD K6-III+ (note the +) 550mhz. If you set the clock multiplier to 2, you can easily get 600mhz out of it. Being a laptop CPU, it's cooling requirements are low, and you can get away with a 100% passive cooling system(Think: large heatsink, no fan, or a very small/quiet fan). Combine this with a pizzabox case with holes or a screen in the top and sides for ventilation, and a small fanless power supply, and you have a small, very quiet system. You may also want to consider lower RPM hard drives, their not as fast, but are quieter and produce less heat.
Of course, it's much more than I pay for. Hey, the DOCSIS 1.0 standard is weak.
I can vouch for that. A Windows machine to handle the really windows-ish stuff, and a slackware box for the heavy lifting is a good, balanced solution., and has worked very well for me in the past.
Oh of course. But porting a DirectX game is damn well near impossible, wheras porting an OpenGL game is much easier, so anything that moves game developers away from DirectX is fine by me.
This is great news. Games written for osX will use OpenGL instead of DirectX, this means that porting them to other operating systems won't be such a chore. With the demise of Loki, it's nice to see somthing positive on the Linux/BSD gaming frontier.
I just figured I'd get that tune stuck in everyones head.
EMACS has a DOS port, and there are packages for EMACS to turn it into a fairly decent GCC IDE. I have no DOS/Win machines, but perhaps you should give it a try.
One of the reasons Slackware is (imho) more stable out-of-the-box is it's general simplicity. Most other distributions have much more complex inner workings and interdependancies. Ever try to configure a RedHat box WITHOUT using any of their config scripts/tools?
The more complex a system becomes, the more opprotunity there is for problems to arise.
Anyone ever hear of KISS? Keep It Simple Stupid!
Most older IP stacks for Apples have a low amount of available sockets, such as 16 or 32. Once those are all being used, the machine can no longer accept connections.. Thus this link suffered instant slashdot. Good job!
New features AND less bloat. It loads up faster on my machine and it also appears to use less memory. I like this trend in development.
What's the deal with XML? It's just a markup language, big deal. Why impliment an RPC system based on XML? You want to see how bloated you can make it or what? I mean, be sensible, RPC can be implimented in much simpler ways without losing any 'features'. Score one more to the bloat god.
It is however, fairly easy to clone camels. My plot for world domination is still right on schedule..
Hey, I do it. It's not as hard as you would think. Audit the entire source once the first time you download it, then simply run diffs between that and the new version, look them over, if it's cool install. Once I am satisfied that the original package is OK, auditing upgrades takes anywhere from 5 to 30 minutes, well worth the time for a paranoid bastard like me.