Actually I don't bother to crack the password. Much easier to roll in there with a copy of NT crack on floppy (a mini-linux distro mind you) and simply put my own damn password in for Administrator.
Comes in handy when you have to 0w# and entire network after they can the NT admin. And I do have the procedure down to about 65 seconds. (Even works for XP.)
And I don't crack passwords while getting head from hot chicks. My hot wife hates when the keyboard is in the way.
Granted, I had to invent my own install method for my Sony Vaio, but that is what Linux is all about people. But in all that monkeying I did end up getting EVERYTHING working on this baby, the jog dial, the battery monitor, even DVD playback.
BTW, you have me beat. I only started fiddling with computers since the PCjr in '82. I was 6. Say, when you started off with BASIC, could you actually find anything written for your interpreter. I remember having to constantly translate games from Apple and C64 basic over to IBM. After a while it was more fun writing games than playing them. (sniff)
I worked for Kulicke and Soffa for a few years in College. One of our products was a large bonder that they were planning to buy because NOTHING ELSE COULD ACCOMODATE A CHIP THAT SIZE.
It's like the damn Space shuttle. The only reason it is that complicated is because it wasn't all that well thought up in the beginning. Intel has historically been known as the first with the worst.
I think he meant Baroque to mean classical and eclectic. When you think of Baroque music, you have Mozart, Handle, and Beetovan. Baroque art introduced oil painting. Baroque was no so much a style as a way of encompasing so many other styles.
Frankly, all of my Ghz dual headed machines spend most of their life waiting for the network card. My email server MIGHT hit a load of.4 on a busy day.
What I REALLY need in my data center is stuff that runs cooler, without so many fans that go bad, catch fire, short out, etc.
Have a pipeline party for all I care, but the reason PC's have been historically slow has been because they use cheap RAM, and older IO bus techonologies. Open up an SGI from 1996 and you will see an SDRAM chip that PC's didn't start using until 1998. Look at an AIX box from 1990, and you'll see (gasp) PCI when PC's were running ISA.
What we learned with RISC is that creating smaller, faster instructions requires hitting the memory bus more often, negating most improvement in throughput.
And BTW Intel has had it's ears boxed in by customers before. Anyone remember the 80186. That chip did away with the goofy little endian addressing scheme. Since it broke all the software thusfar written for the 80086, sales plummeted until the release of the 80286, which reinstated little endian.
The pentium architecture has been loading 64 bits of memory at a time since the PII. They have to because that is the only way the RAM has a chance in hell of keeping up with the processor. Basically they load 2 instructions at once, and have them execute at double the speed of the RAM. (That's also part of why you get such a kick in the pants when you optimize with the -mcpu=i686 flag in gcc.)
Back in '98 when I was an EE major, we studied the IA-64 in our computer architecture class. It didn't take long for me to realize that damn thing was going to fly like a brick.
My first model was to try to calculate Easter on assembler. Sure all of that data can sit in a register, with room to spare. The problem is getting the INSTRUCTIONS in and out. Since the damn thing is so superpipelined, you get to drop in one instuction, wait, drop an address to the register, wait, load data into register, wait,...
I developed my EASTER test after a disasterous presentation where I had to demonstrate a processor architecture I had designed. It worked great for vector math, but it crawled on everything else...
Now if they are hiring dropout EE majors to design their next chip, I'll be happy to give them my resume.
I remember those good old days. My parent's 386 packerd bell churning away for a week or two to render an image.
Kids have it too easy these days with 3d Studio and Maya. Well back in my day I had to code my scenes in C damnit. We had to write our own graphics drivers, and make interupt calls to listen to the mouse. If we had a mouse dag nabbit. That was back when 3d meant you could draw a wireframe with a Z axis.
Kids these days. They have it so easy. Hitting the internet with their Pentium IV's with a gigabyte of RAM. Hell, my first computer had 128Kb of RAM. It operated at 4.7 Mhz. And we didn't have hard drives back then, we had to keep all of our stuff on floppy disks. We didn't have the internet. If we were lucky we had a bulletin board, at a whopping 4800 baud.
Yes, but at that point NASA officials would loose the ability to frob one budget to make up for overruns *cough* shortfalls in the other.
I hear you. It's time to make NASA make a budge just like the rest of us. Sure I can budget a boat and new Scuba equipment, AFTER I pay for food, rent, insurance, car payments, the electricity bill... and so on.
For experience again? It just doens't seem to be anywhere on that darned spreadsheet. I mean hell if money can't buy it, how are they supposed to keep track of it?
(HHOS)
I hope we are seeing the end of a very ugly way of thinking.
Slashdot Mirror
7) ??? 8) PROFIT!!!
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness buy them.
Comes in handy when you have to 0w# and entire network after they can the NT admin. And I do have the procedure down to about 65 seconds. (Even works for XP.)
And I don't crack passwords while getting head from hot chicks. My hot wife hates when the keyboard is in the way.
No, really.
Granted, I had to invent my own install method for my Sony Vaio, but that is what Linux is all about people. But in all that monkeying I did end up getting EVERYTHING working on this baby, the jog dial, the battery monitor, even DVD playback.
BTW, you have me beat. I only started fiddling with computers since the PCjr in '82. I was 6. Say, when you started off with BASIC, could you actually find anything written for your interpreter. I remember having to constantly translate games from Apple and C64 basic over to IBM. After a while it was more fun writing games than playing them. (sniff)
Gotta remember to put some oregano on my words for when I have to eat them.
It's like the damn Space shuttle. The only reason it is that complicated is because it wasn't all that well thought up in the beginning. Intel has historically been known as the first with the worst.
Now if only Motorola could save us now...
That's my story and I'm sticking with it.
What I REALLY need in my data center is stuff that runs cooler, without so many fans that go bad, catch fire, short out, etc.
That would be the Playstation 2.
Throw in the playstation 1 and we might be up to 100 million.
I want a low-power quiet machine that can play my DVD's and run open-office. Explain how any of this dicksizing to 64 bits gets me there?
Well, except for all of those device drivers and low-level kernel routines that make assembler calls...
Have a pipeline party for all I care, but the reason PC's have been historically slow has been because they use cheap RAM, and older IO bus techonologies. Open up an SGI from 1996 and you will see an SDRAM chip that PC's didn't start using until 1998. Look at an AIX box from 1990, and you'll see (gasp) PCI when PC's were running ISA.
What we learned with RISC is that creating smaller, faster instructions requires hitting the memory bus more often, negating most improvement in throughput.
And BTW Intel has had it's ears boxed in by customers before. Anyone remember the 80186. That chip did away with the goofy little endian addressing scheme. Since it broke all the software thusfar written for the 80086, sales plummeted until the release of the 80286, which reinstated little endian.
I don't know. I'd wait until the 3.1 rev of the Kernel before I make an trastic statements like that.
The pentium architecture has been loading 64 bits of memory at a time since the PII. They have to because that is the only way the RAM has a chance in hell of keeping up with the processor. Basically they load 2 instructions at once, and have them execute at double the speed of the RAM. (That's also part of why you get such a kick in the pants when you optimize with the -mcpu=i686 flag in gcc.)
My first model was to try to calculate Easter on assembler. Sure all of that data can sit in a register, with room to spare. The problem is getting the INSTRUCTIONS in and out. Since the damn thing is so superpipelined, you get to drop in one instuction, wait, drop an address to the register, wait, load data into register, wait, ...
I developed my EASTER test after a disasterous presentation where I had to demonstrate a processor architecture I had designed. It worked great for vector math, but it crawled on everything else...
Now if they are hiring dropout EE majors to design their next chip, I'll be happy to give them my resume.
(BANG BANG BANG BANG)
And for the record, the only way to do graphics in PERL is by using Tcl's TK API. (Same for Python.)
The sign that our world is a truely twisted place: a TCL package exists to load PERL modules, and a PERL module exists that will load TCL.
Open Source at work.
And you know, it doesn't do a half bad job. If only someone around here know vax enough to do anything BUT the planetarium shows...
I remember those good old days. My parent's 386 packerd bell churning away for a week or two to render an image.
Kids have it too easy these days with 3d Studio and Maya. Well back in my day I had to code my scenes in C damnit. We had to write our own graphics drivers, and make interupt calls to listen to the mouse. If we had a mouse dag nabbit. That was back when 3d meant you could draw a wireframe with a Z axis.
Kids these days. They have it so easy. Hitting the internet with their Pentium IV's with a gigabyte of RAM. Hell, my first computer had 128Kb of RAM. It operated at 4.7 Mhz. And we didn't have hard drives back then, we had to keep all of our stuff on floppy disks. We didn't have the internet. If we were lucky we had a bulletin board, at a whopping 4800 baud.
And we were grateful...
Once it hits the freak show, suits want it like a bad toy.
The tricky part is building a custom stage-1 bootloader. Gotta love cross-compiling.
No, no, it was the space debris from the grassy knoll.
I hear you. It's time to make NASA make a budge just like the rest of us. Sure I can budget a boat and new Scuba equipment, AFTER I pay for food, rent, insurance, car payments, the electricity bill... and so on.
Now that must be one Magic piece of foam...
(HHOS)
I hope we are seeing the end of a very ugly way of thinking.