You do need a 34-pin to 50-pin adapter, but those aren't hard to build, or you can buy one from www.dbit.com.
Actually, if your floppies are 100% double density, you can probably even read them with an adapter cable and a regular PC floppy controller. If they are all or partly single density, you may have problems, because some PC controllers can read single density and some fail to.
800 K Mac floppies are read/written at a variable rotation speed, which is impossible to simulate with a standard PC floppy controller.
...which the Catweasel is not! There's no problem using a Catweasel to simulate the variable rotation speed; instead of changing the physical rotation speed of the drive, you simply change the data rate.
> The only way to break a OTP is to get a copy the > pad or by breaking the random number generator > used to create the pad.
A proper OTP cannot be created by a (pseudo-)random number generator. You must use a source of true randomness, such as radioactive decay or some other such physical process. So you can't "break" an OTP by "breaking the random number generator" -- unless perhaps you mean finding out that the equipment was not working correctly and was not generating truly random numbers.
Some OTP's have been "broken" because the factory making them did not use the key material only once as they were supposed to, but printed multiple copies of pages and used them in more than one pad. But of course, the output of such a factory isn't really a one-time pad at all.
...but not for x86? Is there a good book to bone up on the details of the x86 that doesn't start with "this is a 0, this is a 1"?
I've done extensive assembly language programming for Z-80, and small to moderate amounts for 68000, PDP-10, PDP-11, VAX, and Alpha, but managed to avoid the x86 until I took my current job. Here most of what I do is well above the assembly level, but it would occasionally help to be fluent in x86 assembler.
I suppose the answer is to just read over code with the Intel manuals in hand to look things up, until I get to where I don't have to look up so much anymore. But I was hoping for something less tedious.
Red Hat CD's already have this feature built in. The installer has a self-test mode where it will read each CD and compare its actual MD5SUM against what it's supposed to be. I think this is new in 7.3. It's a great feature; we've had way too many problems in the past where we downloaded an ISO image, burned a CD-R, and an error was silently introduced somewhere along the way.
"Comments Considered Harmful" and "sometimes comments are indicative of a need to change the code" are not at all the same thing.
Although I could nitpick the examples, yes, sometimes if you read the comments on a piece of code perceptively, they will help you pick up something that needs to be changed in the code. Does that mean the comment was harmful? Certainly not! It was helpful -- it raised a red flag that helped you see the problem. Deleting the comment would not fix the problem; it would only obscure it.
Other times, of course, comments can be trivial or plain wrong and would be better deleted. A good comment is one that describes what's being done more compactly and at a higher level of abstraction than the code. If you like, it describes the "what" rather than the "how".
Seems like getting fired by the stupid people was a good thing for you, if you're now working for smart people instead. So your advice to conform to the stupidity instead of pointing out the problems doesn't sound so good to me. In hindsight, would you really rather still be working for the folks who fired you instead of where you are today?
Re:My Solution Was Simple:
on
Disconnecting
·
· Score: 1
Are you kidding? You aren't obliged to give them a reason at all. You certainly aren't obliged to come up with a reason that satisfies them. You are in charge here.
Re:...isn't always beautiful
on
Disconnecting
·
· Score: 1
Open a new one? I would take the cashier's check and open a new account at a different bank if my bank gave me that much trouble.
Yes -- configure a different address for the VM than for the host. The VM appears to be a different machine, so it needs to have a different IP address. In your setup, you probably want to use the VMware "bridged networking" option and set the VM to something like 192.168.1.4 (or some other address in your private network that is unused).
(Just being helpful, not posting as official VMware representative.)
That paragraph doesn't matter, because the claims refer specifically to chains and tree branches and don't allow for any alternatives. For the patent to cover it, it has to be in the claims. The rest is essentially just commentary to clarify what the claims mean.
For uniformly distributed random data (white noise), the average compression ratio has to be 1:1. The "2:1 for 8-bit random" in the parent article is silly, so it puzzles me why it's been modded up. 2:1 is a common rule of thumb for data that's typically stored in computer file systems, but that's far from random; it has lots of ASCII text, executable programs, etc.
The poster is close but has EV68 and EV7 confused.
The internal code names EV6, EV67, EV68 correspond respectively to external part numbers 21264, 21264A, and (I'm 99% sure) 21264B. I say "99% sure" because I left Compaq 2 months ago and haven't checked with contacts there, but 21264B would be the natural part number for EV68.
EV68 is mostly a process shrink of EV67, but I think with some bug fixes and minor improvements.
EV7, which should be released as 21364, uses a core based on EV67/EV68, but has an all-new memory subsystem with multiple RAMBUS channels for fast memory access and for building grid-structured multiprocessors. That's what the parent to this article was talking about, but it's not in EV68. EV7 is still under development, very far along but not quite done yet, and Compaq is committed to finishing it and releasing a generation of servers using it, according to what was announced at the time of the Intel deal.
EV8 was going to be an all new core with simultaneous multithreading, reusing the EV7 memory subsystem. It would have been released as the 21464. EV8 was cancelled with the sale of the Alpha IP and engineering group to Intel. My friends in the EV8 group are at Intel already, while the Alpha engineers who were on EV68 and EV7 are still at Compaq for the time being.
I don't have any contacts at Samsung/API, so I'm not sure exactly what they're doing. But it would be quite weird if they released something called 21264B that was anything other than an EV68...
AltaVista is still nice because it indexes every word (including "the", etc.), so phrase queries are more exact. If you query AltaVista for "The Who", you'll get results about the band; if you try that on Google, you get no results and are told that "who" (not to mention "the") is a very common word and was not included in your search.
You can avoid most of the ads and nonsense by using http://www.altavista.com/sites/search/text instead of http://www.altavista.com
In running English text, the frequency of "the" is just about 70,000 per million. In other
words, 7% of all English text consists of the definite article, and most web pages contain many distinct
copies. You've got to kill that.
Well, actually you don't. AltaVista indexes every word, including "the". This helps it do exact phrase queries. For instance, try searching for "The Who".
The idea seems to be to blur the distinction between sharing your own work (obviously laudable) and sharing someone else's work without their permission (obviously unethical, and folks generally knew that even in 1975).
It also tries to oversimplify all the complex debates that are going on right now into a simple black and white question of whether "computer software and digital information should be bought and sold or freely shared".
Thus to me, the article reads like a subtle propaganda piece for the groups today who are trying to extend their rights under copyright beyond all reasonable bounds using DMCA, UCITA, etc. By citing a past case where people were clearly stealing and calling that the start of the debate, the article suggests that today's debate is not a legitimate discussion about where copyright ends and fair use rights begin, but simply a debate about whether or not stealing is OK. Since Joe NYT Reader probably doesn't think that stealing is OK, this tends to push him towards one side of the debate...
My, is this poster confused. Everything he has "gathered from the article" is wrong. - Enterprising hackers? Well, actually the people who did the Linux port to the iPaq H3600 mostly work for Compaq's research labs. I guess you could call them enterprising hackers if you want, though. - Closed platform with no documentation? No, actually Compaq is supplying complete hardware documentation on the Web, accessible from handhelds.org. The folks who did the port had this early (being inside Compaq), but now you have it too. - No support for the iPaq's framebuffer, let alone an X server? No, actually the Linux port comes with an X server. Works fine, in color. (Notice that the announcement was sent out by Jim Gettys, one of the two original developers of X!) - Support for the digitizer? Yep, the Linux port comes with support for the touchscreen and a unistroke recognizer (xscribble).
Yes indeed, you can run X on it! The Linux port includes X and some X applications, including a stroke recognizer.
Re:Intel makes alphas ... remember (?)
on
1.4-1.6 GHz Alphas
·
· Score: 1
Quoting from that press release, "Intel will serve as a foundry." That is, they manufacture Alphas on their production lines under contract to Compaq. This certainly doesn't inhibit Compaq from competing with Intel to design the fastest chips. Compaq doesn't have to make any concessions to Intel in order to keep the manufacturing relationship going. Other companies, such as Samsung, manufacture Alphas too, and Compaq is always looking for better deals from other foundaries.
Slashdot Mirror
Oops, here I am lamely replying to myself.
You do need a 34-pin to 50-pin adapter, but those aren't hard to build, or you can buy one from www.dbit.com.
Actually, if your floppies are 100% double density, you can probably even read them with an adapter cable and a regular PC floppy controller. If they are all or partly single density, you may have problems, because some PC controllers can read single density and some fail to.
I have an 8" drive plugged into my Catweasel MK1 ISA card. Works great. I'm sure they'll work fine with the MK3 card too.
...which the Catweasel is not! There's no problem using a Catweasel to simulate the variable rotation speed; instead of changing the physical rotation speed of the drive, you simply change the data rate.
> The only way to break a OTP is to get a copy the
> pad or by breaking the random number generator
> used to create the pad.
A proper OTP cannot be created by a (pseudo-)random number generator. You must use a source of true randomness, such as radioactive decay or some other such physical process. So you can't "break" an OTP by "breaking the random number generator" -- unless perhaps you mean finding out that the equipment was not working correctly and was not generating truly random numbers.
Some OTP's have been "broken" because the factory making them did not use the key material only once as they were supposed to, but printed multiple copies of pages and used them in more than one pad. But of course, the output of such a factory isn't really a one-time pad at all.
...but not for x86? Is there a good book to bone up on the details of the x86 that doesn't start with "this is a 0, this is a 1"?
I've done extensive assembly language programming for Z-80, and small to moderate amounts for 68000, PDP-10, PDP-11, VAX, and Alpha, but managed to avoid the x86 until I took my current job. Here most of what I do is well above the assembly level, but it would occasionally help to be fluent in x86 assembler.
I suppose the answer is to just read over code with the Intel manuals in hand to look things up, until I get to where I don't have to look up so much anymore. But I was hoping for something less tedious.
Red Hat CD's already have this feature built in. The installer has a self-test mode where it will read each CD and compare its actual MD5SUM against what it's supposed to be. I think this is new in 7.3. It's a great feature; we've had way too many problems in the past where we downloaded an ISO image, burned a CD-R, and an error was silently introduced somewhere along the way.
Um, weirding modules are from Dune, not Doctor Who.
Or was this post some advanced form of subtle humor?
"Comments Considered Harmful" and "sometimes comments are indicative of a need to change the
code" are not at all the same thing.
Although I could nitpick the examples, yes, sometimes if you read the comments on a piece of code perceptively, they will help you pick up something that needs to be changed in the code. Does that mean the comment was harmful? Certainly not! It was helpful -- it raised a red flag that helped you see the problem. Deleting the comment would not fix the problem; it would only obscure it.
Other times, of course, comments can be trivial or plain wrong and would be better deleted. A good comment is one that describes what's being done more compactly and at a higher level of abstraction than the code. If you like, it describes the "what" rather than the "how".
Seems like getting fired by the stupid people was a good thing for you, if you're now working for smart people instead. So your advice to conform to the stupidity instead of pointing out the problems doesn't sound so good to me. In hindsight, would you really rather still be working for the folks who fired you instead of where you are today?
Are you kidding? You aren't obliged to give them a reason at all. You certainly aren't obliged to come up with a reason that satisfies them. You are in charge here.
Open a new one? I would take the cashier's check and open a new account at a different bank if my bank gave me that much trouble.
Simple. Most OSes execute a HALT instruction inside the idle process. When the guest OS does this, VMware gives the CPU back to the host.
Yes -- configure a different address for the VM than for the host. The VM appears to be a different machine, so it needs to have a different IP address. In your setup, you probably want to use the VMware "bridged networking" option and set the VM to something like 192.168.1.4 (or some other address in your private network that is unused).
(Just being helpful, not posting as official VMware representative.)
That paragraph doesn't matter, because the claims refer specifically to chains and tree branches and don't allow for any alternatives. For the patent to cover it, it has to be in the claims. The rest is essentially just commentary to clarify what the claims mean.
:-)
IANAL! I do have one granted patent, though.
For uniformly distributed random data (white noise), the average compression ratio has to be 1:1. The "2:1 for 8-bit random" in the parent article is silly, so it puzzles me why it's been modded up. 2:1 is a common rule of thumb for data that's typically stored in computer file systems, but that's far from random; it has lots of ASCII text, executable programs, etc.
The poster is close but has EV68 and EV7 confused.
The internal code names EV6, EV67, EV68 correspond respectively to external part numbers 21264, 21264A, and (I'm 99% sure) 21264B. I say "99% sure" because I left Compaq 2 months ago and haven't checked with contacts there, but 21264B would be the natural part number for EV68.
EV68 is mostly a process shrink of EV67, but I think with some bug fixes and minor improvements.
EV7, which should be released as 21364, uses a core based on EV67/EV68, but has an all-new memory subsystem with multiple RAMBUS channels for fast memory access and for building grid-structured multiprocessors. That's what the parent to this article was talking about, but it's not in EV68. EV7 is still under development, very far along but not quite done yet, and Compaq is committed to finishing it and releasing a generation of servers using it, according to what was announced at the time of the Intel deal.
EV8 was going to be an all new core with simultaneous multithreading, reusing the EV7 memory subsystem. It would have been released as the 21464. EV8 was cancelled with the sale of the Alpha IP and engineering group to Intel. My friends in the EV8 group are at Intel already, while the Alpha engineers who were on EV68 and EV7 are still at Compaq for the time being.
I don't have any contacts at Samsung/API, so I'm not sure exactly what they're doing. But it would be quite weird if they released something called 21264B that was anything other than an EV68...
AltaVista is still nice because it indexes every word (including "the", etc.), so phrase queries are more exact. If you query AltaVista for "The Who", you'll get results about the band; if you try that on Google, you get no results and are told that "who" (not to mention "the") is a very common word and was not included in your search.
You can avoid most of the ads and nonsense by using http://www.altavista.com/sites/search/text instead of http://www.altavista.com
Well, actually you don't. AltaVista indexes every word, including "the". This helps it do exact phrase queries. For instance, try searching for "The Who".
The idea seems to be to blur the distinction between sharing your own work (obviously laudable) and sharing someone else's work without their permission (obviously unethical, and folks generally knew that even in 1975). It also tries to oversimplify all the complex debates that are going on right now into a simple black and white question of whether "computer software and digital information should be bought and sold or freely shared".
Thus to me, the article reads like a subtle propaganda piece for the groups today who are trying to extend their rights under copyright beyond all reasonable bounds using DMCA, UCITA, etc. By citing a past case where people were clearly stealing and calling that the start of the debate, the article suggests that today's debate is not a legitimate discussion about where copyright ends and fair use rights begin, but simply a debate about whether or not stealing is OK. Since Joe NYT Reader probably doesn't think that stealing is OK, this tends to push him towards one side of the debate...
Nice sig quote from Bill Gosper, but you spelled his name wrong.
What a ridiculous post.
My, is this poster confused. Everything he has "gathered from the article" is wrong. - Enterprising hackers? Well, actually the people who did the Linux port to the iPaq H3600 mostly work for Compaq's research labs. I guess you could call them enterprising hackers if you want, though. - Closed platform with no documentation? No, actually Compaq is supplying complete hardware documentation on the Web, accessible from handhelds.org. The folks who did the port had this early (being inside Compaq), but now you have it too. - No support for the iPaq's framebuffer, let alone an X server? No, actually the Linux port comes with an X server. Works fine, in color. (Notice that the announcement was sent out by Jim Gettys, one of the two original developers of X!) - Support for the digitizer? Yep, the Linux port comes with support for the touchscreen and a unistroke recognizer (xscribble).
Yes indeed, you can run X on it! The Linux port includes X and some X applications, including a stroke recognizer.
Quoting from that press release, "Intel will serve as a foundry." That is, they manufacture Alphas on their production lines under contract to Compaq. This certainly doesn't inhibit Compaq from competing with Intel to design the fastest chips. Compaq doesn't have to make any concessions to Intel in order to keep the manufacturing relationship going. Other companies, such as Samsung, manufacture Alphas too, and Compaq is always looking for better deals from other foundaries.