This is an Urban Assult Vehicle, but that does not necessarily mean they are planning a raid on New York.
Remember, if we HAVE to go into Iraq|Afganistan|Bosnia|... we will be fighting in the cities. The last Gulf War was an anomaly - this time, Saddam will allow us to take all the sand we want. However, if we want to move into the cities, then we will pay dearly.
So, you want a vehicle designed to fight in a city. Any city - Bagdad, Prague, Paris, Wichita, it doesn't matter.
That said - some of the moves being made to prepare for citizen suppression scare the crap out of me. I expect that by the time I am ready to retire, we will be living in what Civilization calls a "Corporate Republic".
The characteristic impedance of TV co-ax is 75 ohms. Thinnet Ethernet cable is 50 ohms, as is the impedance of an Ethernet card. This will cause a VSWR mismatch.
You are getting a reflected signal off each network card in the system. As you describe it, you have a simple point-to-point link, so your reflections are "only" bouncing from one card to another. This will cause errors in the system.
I would suggest that you get REAL network cable (preferably CAT-5), tie it onto the existing cable, and pull it through. You will then be able to run 100Mbit, you won't have the reflection problem, and I think you will be much happier overall.
(actually, I would suggest that you go to the local hardware store, and while you are picking up the CAT5, pick up a spool of nylon cordage. Strip the end of the coax, and securely tie the cordage to the shield of the coax. Then smoothly tape it over with electrician's tape, starting on the coax jacket and with a 1/3 overlap moving to the cordage. When you reach the cordage, wind one extra pass, then cut the tape and UNWIND and REWIND that last wrap with no tension on the tape. Then pull the cordage through. Once it is through, then tie the CAT5 to the cordage and tape as you did the coax. Then pull BOTH the CAT5 and a new run of cordage. Leave the cordage in place - it will save you grief later if you need to pull an additional cable.)
I went to the Trinity site opening this last October - it would have been fun to have had this watch then as I wandered around the site of the first nuclear blast.
I can think of some people that this would be useful for - anybody who works in caves. Due to naturally occuring uranium in granite, all caves with poor air circulation exhibit increased levels of radon. In fact, the National Parks Service workers at Carlsbad Caverns wear dosimeters, and are not allowed to work there longer than a couple of months before being rotated out, to limit their exposure.
(the fact that Bittmann's father was the chemist at a refinery helps too!)
However, have you seen the special on TEL that was on (I think) NOVA? TEL at the time of its discovery was known to be quite toxic. And, according to the documents shown in that special, alcohol was rejected precisely because it was not patentable.
Also, another way to boost power on engines was water injection - would drying the alcohol be quite as important? (of course you need to make sure your fuel system is corrosion proof, but then again, you should anyway!)
But Bit's advise is sound - Google for information on TEL. Then form your own opinions....
For those of us who have older Unix workstations that don't know how to spell IDE, these allow us to put a decent amount of storage on them for a reasonable cost.
If you are buying IDE drives, and IDE to SCSI converters, and a SCSI card, to put into your x86 box, then yes, you need to order a nice big bowl of InstaClue.
But if you are trying to install the Gnu development tools onto an old SGI Indy, this is a great idea.
I just contacted Addonics to get a returned materials authorization (RMA) number for my IDE to SCSI adaptor, since it would not work.
Specifically, when I hooked it up to my Maxtor 120G drive and my SGI Indy, the Indy didn't see the drive. Hooking it up to my Linux box's Adaptec controller let me get the drive info (cat/proc/scsi/scsi), but any attempt to actually access sectors on the drive locked the SCSI bus up solid.
The drive itself works just fine on the Linux box's IDE, as well on my Firewire bay, so that exonerates the drive. The Adaptec works just fine on my scanner, outboard 3G SCSI disk, and CD burner, so that exonerates the Linux box's SCSI controller. The SGI boots fine from its SCSI disks, exonerating the Indy.
I told Addonics all this. Their response - "We've passed that on to our engineers." Two weeks later, when I had heard nothing, I contacted them again. "We are still waiting for our engineers".
At that point I asked for an RMA. After they emailed me the RMA request form, and I faxed it back, they contact me via email - "Have you tried using our SCSI controller card - it works much better with our SCSI card."
Now, were I using some generic SCSI card from a back alley somewhere I could accept this sort of a response, but Adaptec? Excuse me, who CREATED the SCSI standard? Ignoring the fact that I seriously doubt they have a SCSI controller card for my Indy (which is what I am trying to put the drive on).
I'll be interested in hearing anybody else's experiences - after all my experience is just a datum.
But if anybody else has a different IDE to SCSI adaptor they want to recommend, please reply.
Now, criticizing rudeness is really quite rude, according to Miss Manners. The problem is that the rude people are too clueless to understand polite put-downs. The end (good manners) doesn't justify the means (bad manners). I think there's nothing you can do: Western Civ as we know it is DEAD DEAD DEAD by suicide.
Critizing rude behavior need not be rude itself - if a person insists upon using their cell phone in a movie, saying quietly to them "Please go outside - I am trying to watch the movie" is not rude.
Now, screaming
DID THIS MOVIE START WITH BIG RED LIPS ON SCREEN? THIS ISN'T ROCKY HORROR - SHUT THE FUCK UP!
Tetraethyl Lead was a TERRIBLE idea - the only reason it was chosen over grain alcohol was that tetraethyl lead could be patented and marketed, whereas grain alcohol could not.
Perhaps it was a great business innovation, but a lousy scientific innovation.
13) Discourage common courtesy - glorify rudeness and arrogance as being "forceful and dynamic". However, make sure that anybody who dares to critisize somebody for their rudeness is called "intolerant". Manners are the oil that lubricates society - throw as much grit in there as you can.
It sounds like this guy needs to communicate to some device that is at a different potential than the rest of the system.
Have you considered using fiber? High bandwidth, pretty much immune to RF interference, high voltage isolation.
However, if the target is moving around (some sort of industrial machine, perhaps?) this might not work.
That's the problem with a lot of Ask Slashdots - the person asking really cannot give a lot of information about his needs, so we cannot weed out suggestions that won't work.
I haven't seen an Office XP document, but that's not the point in any case.
That is exactly the point - Microsoft has repeatedly and for no good reason introduced incompatiblities on every upgrade of Word - a standardized XML schema would prevent that. Since incompatiblities are how Microsoft forces everybody to upgrade, it is unlikely they would change.
I don't see how one can expect the previous version of an application to open a file created with a newer version.
You mean like how every version of Wordperfect can open any WordPerfect document, as long as you don't use features added in the newer version? It is child's play for a competent software engineer to design a format that describes a document in chunks, and to specify that a conforming processor will skip over the chunks it does not understand. For example, the Amiga Information File Format described and audio file in chunks, and the first words of each chunk were the chunk type and length. Perhaps you are familiar with it - Microsoft stole the format for WAV files (although they DID reorder the words from big endian to little endian).
Second, Microsoft can hardly break their own code by "changing the methods of an object" because you can access the data in those compound documents with a few, well documented interfaces that have absolutely nothing to do with Office.
Of course, those methods exist only under Windows, and only if the appropriate DLL is present. Have you ever looked at the very files you claim to be an expert on, without a Microsoft supplied DLL between you and the data?
Of course, once you get the data you need to know how to format it, which is the real problem.
And that is the real nub - once you have recovered the data, how do you format it - information that is curiously undocumented - and that is my point. The odds that Microsoft will of their own choosing define an XML format that allows everybody to see how to interpet and format the data are approximately the same as Sarah Brady sending a sympathy card to Charlton Heston.
I will bet all they will do is create an XML schema for the COM serialize function, since that is pretty much all any Microsoft application does when you select File->Save - it just calls the COM serialize function with the output pointed at the disk.
So, you will have a file that is nominally XML, but is nothing but memory dump of the COM object.
And for the record, I am not an "audiophile". I'm an audio and broadcasting engineer.
Obviously - were you an audiophile you would either have
a) Asked me what catalog I was quoting b) "Whipped it out" by telling me you OWNED a set of Dominus Speaker Cables, thus "proving" your superior size. c) Modded me -1, Troll
Besides:
And for the record, I am not an "audiophile". I'm an audio and broadcasting engineer.
Rather my point - audiophiles are not rational individuals who are well versed in signal processing theory, they are rabid indiviuals who's sound systems are a penis substitute.
Hence why audiophiles hate modern sound systems - it is far too easy to get great sound reproduction nowadays, and how are you to demonstrate how large you are when a $19 CD player sounds as good as your $3000 turntable?
That is why audiophiles use "oxygen-free copper wires with authentic virgin yak wool insulation, cryogenicly treated to release signal-distorting sub-micron strain! A steal at $300/ft! Act now, and we will throw in our patented Feng Shui turntable stones - five of these will disgronificate your turntable! Normally $150 each, but a steal at $800 for a set!"
Slashdot Mirror
... A pretty lady asked me what time on my watch.
And I said....
"It's two bluescreens past 3:00"
(with apologies to Chicago....)
Don't tell me I'm not the only person making comparisons to some other form of, shall we say, more intimate entertainment....
This is an Urban Assult Vehicle, but that does not necessarily mean they are planning a raid on New York.
Remember, if we HAVE to go into Iraq|Afganistan|Bosnia|... we will be fighting in the cities. The last Gulf War was an anomaly - this time, Saddam will allow us to take all the sand we want. However, if we want to move into the cities, then we will pay dearly.
So, you want a vehicle designed to fight in a city. Any city - Bagdad, Prague, Paris, Wichita, it doesn't matter.
That said - some of the moves being made to prepare for citizen suppression scare the crap out of me. I expect that by the time I am ready to retire, we will be living in what Civilization calls a "Corporate Republic".
Not for a living, but I did extensively rewire my house and those of 2 friends, AND I have friends in the telephony industry.
But no, if you want to get a cable from hither to yonder, you either use a gopher pole (a long, extensible PVC pole) or you use a slingshot.
The characteristic impedance of TV co-ax is 75 ohms. Thinnet Ethernet cable is 50 ohms, as is the impedance of an Ethernet card. This will cause a VSWR mismatch.
You are getting a reflected signal off each network card in the system. As you describe it, you have a simple point-to-point link, so your reflections are "only" bouncing from one card to another. This will cause errors in the system.
I would suggest that you get REAL network cable (preferably CAT-5), tie it onto the existing cable, and pull it through. You will then be able to run 100Mbit, you won't have the reflection problem, and I think you will be much happier overall.
(actually, I would suggest that you go to the local hardware store, and while you are picking up the CAT5, pick up a spool of nylon cordage. Strip the end of the coax, and securely tie the cordage to the shield of the coax. Then smoothly tape it over with electrician's tape, starting on the coax jacket and with a 1/3 overlap moving to the cordage. When you reach the cordage, wind one extra pass, then cut the tape and UNWIND and REWIND that last wrap with no tension on the tape. Then pull the cordage through. Once it is through, then tie the CAT5 to the cordage and tape as you did the coax. Then pull BOTH the CAT5 and a new run of cordage. Leave the cordage in place - it will save you grief later if you need to pull an additional cable.)
I went to the Trinity site opening this last October - it would have been fun to have had this watch then as I wandered around the site of the first nuclear blast.
I can think of some people that this would be useful for - anybody who works in caves. Due to naturally occuring uranium in granite, all caves with poor air circulation exhibit increased levels of radon. In fact, the National Parks Service workers at Carlsbad Caverns wear dosimeters, and are not allowed to work there longer than a couple of months before being rotated out, to limit their exposure.
"I KNOW NOTHING! NOTHING!" was not Col. Klink's catchphrase (which was "HO-GEN!"), it was Sgt. Shultz's.
4 neutrons in a clump - HAH! I've had that beat for ages:
Behold the wonder that is Administratium
And the wonderful (uhhh, awful???) thing is that most of you can see this element in operation yourselves.
(the fact that Bittmann's father was the chemist at a refinery helps too!)
However, have you seen the special on TEL that was on (I think) NOVA? TEL at the time of its discovery was known to be quite toxic. And, according to the documents shown in that special, alcohol was rejected precisely because it was not patentable.
Also, another way to boost power on engines was water injection - would drying the alcohol be quite as important? (of course you need to make sure your fuel system is corrosion proof, but then again, you should anyway!)
But Bit's advise is sound - Google for information on TEL. Then form your own opinions....
The idea is not to place a SCSI drive on an IDE bus, but to place an IDE drive on a SCSI bus.
You might try reading the article before posting - sometimes there's actually useful information there.
For those of us who have older Unix workstations that don't know how to spell IDE, these allow us to put a decent amount of storage on them for a reasonable cost.
If you are buying IDE drives, and IDE to SCSI converters, and a SCSI card, to put into your x86 box, then yes, you need to order a nice big bowl of InstaClue.
But if you are trying to install the Gnu development tools onto an old SGI Indy, this is a great idea.
If it works - see my other post in this thread.
I just contacted Addonics to get a returned materials authorization (RMA) number for my IDE to SCSI adaptor, since it would not work.
/proc/scsi/scsi), but any attempt to actually access sectors on the drive locked the SCSI bus up solid.
Specifically, when I hooked it up to my Maxtor 120G drive and my SGI Indy, the Indy didn't see the drive. Hooking it up to my Linux box's Adaptec controller let me get the drive info (cat
The drive itself works just fine on the Linux box's IDE, as well on my Firewire bay, so that exonerates the drive. The Adaptec works just fine on my scanner, outboard 3G SCSI disk, and CD burner, so that exonerates the Linux box's SCSI controller. The SGI boots fine from its SCSI disks, exonerating the Indy.
I told Addonics all this. Their response - "We've passed that on to our engineers." Two weeks later, when I had heard nothing, I contacted them again. "We are still waiting for our engineers".
At that point I asked for an RMA. After they emailed me the RMA request form, and I faxed it back, they contact me via email - "Have you tried using our SCSI controller card - it works much better with our SCSI card."
Now, were I using some generic SCSI card from a back alley somewhere I could accept this sort of a response, but Adaptec? Excuse me, who CREATED the SCSI standard? Ignoring the fact that I seriously doubt they have a SCSI controller card for my Indy (which is what I am trying to put the drive on).
I'll be interested in hearing anybody else's experiences - after all my experience is just a datum.
But if anybody else has a different IDE to SCSI adaptor they want to recommend, please reply.
Critizing rude behavior need not be rude itself - if a person insists upon using their cell phone in a movie, saying quietly to them "Please go outside - I am trying to watch the movie" is not rude.
Now, screaming
DID THIS MOVIE START WITH BIG RED LIPS ON SCREEN? THIS ISN'T ROCKY HORROR - SHUT THE FUCK UP!
would be rude.
Fun.
But rude.
Tetraethyl Lead was a TERRIBLE idea - the only reason it was chosen over grain alcohol was that tetraethyl lead could be patented and marketed, whereas grain alcohol could not.
Perhaps it was a great business innovation, but a lousy scientific innovation.
13) Discourage common courtesy - glorify rudeness and arrogance as being "forceful and dynamic". However, make sure that anybody who dares to critisize somebody for their rudeness is called "intolerant". Manners are the oil that lubricates society - throw as much grit in there as you can.
It sounds like this guy needs to communicate to some device that is at a different potential than the rest of the system.
Have you considered using fiber? High bandwidth, pretty much immune to RF interference, high voltage isolation.
However, if the target is moving around (some sort of industrial machine, perhaps?) this might not work.
That's the problem with a lot of Ask Slashdots - the person asking really cannot give a lot of information about his needs, so we cannot weed out suggestions that won't work.
I won't go into the validitiy of using SPEWS as a blocklist - there are good arguments pro and con there.
... s... l... o... w... l... y...
But here's a twist to the basic idea:
Given the the email sender is in $BLOCKLIST, have the filter daemon give the 450 response
v... e... r... y...
Combine a teergrube with the 450 response to fill up both their mail spool AND their socket connection table.
(For those who don't know, a teergrube (tarbaby) is a mail server that response slowly to a spammer, the better to tie up his connections).
Now, not only will the open relay's mail queue fill, but it will run out of (file descriptors|sockets) and choke on that too!
That is exactly the point - Microsoft has repeatedly and for no good reason introduced incompatiblities on every upgrade of Word - a standardized XML schema would prevent that. Since incompatiblities are how Microsoft forces everybody to upgrade, it is unlikely they would change.
I don't see how one can expect the previous version of an application to open a file created with a newer version.
You mean like how every version of Wordperfect can open any WordPerfect document, as long as you don't use features added in the newer version? It is child's play for a competent software engineer to design a format that describes a document in chunks, and to specify that a conforming processor will skip over the chunks it does not understand. For example, the Amiga Information File Format described and audio file in chunks, and the first words of each chunk were the chunk type and length. Perhaps you are familiar with it - Microsoft stole the format for WAV files (although they DID reorder the words from big endian to little endian).
Of course, those methods exist only under Windows, and only if the appropriate DLL is present. Have you ever looked at the very files you claim to be an expert on, without a Microsoft supplied DLL between you and the data?
And that is the real nub - once you have recovered the data, how do you format it - information that is curiously undocumented - and that is my point. The odds that Microsoft will of their own choosing define an XML format that allows everybody to see how to interpet and format the data are approximately the same as Sarah Brady sending a sympathy card to Charlton Heston.
Then why are MS-WordXP documents not compatible with MS-Word 2000?
The bad thing about COM streams is that if you change the methods of the object, you render the data incompatible with previous versions.
If you represent a paragraph as <p>, then you needn't worry if you redefine WordDoc::BeginParagraph.
I will bet all they will do is create an XML schema for the COM serialize function, since that is pretty much all any Microsoft application does when you select File->Save - it just calls the COM serialize function with the output pointed at the disk.
So, you will have a file that is nominally XML, but is nothing but memory dump of the COM object.
Technically, XML. Actually, COM.
Obviously - were you an audiophile you would either have
a) Asked me what catalog I was quoting
b) "Whipped it out" by telling me you OWNED a set of Dominus Speaker Cables, thus "proving" your superior size.
c) Modded me -1, Troll
Besides:
No pun intended, I'm sure.... NOT!
And I shall file a patent on:
... click patents!
"A method, given an N-click shopping method, to convert it into an N+1 click shopping method."
Thus, I shall be able to stymie Amazon's 3, 4, 5
MWHAHAHAHAH!
In fairness, I did not come up with that term, it was another.
In *nix, everything is a file.
In Windows, everything is a virus.
Rather my point - audiophiles are not rational individuals who are well versed in signal processing theory, they are rabid indiviuals who's sound systems are a penis substitute.
Hence why audiophiles hate modern sound systems - it is far too easy to get great sound reproduction nowadays, and how are you to demonstrate how large you are when a $19 CD player sounds as good as your $3000 turntable?
That is why audiophiles use "oxygen-free copper wires with authentic virgin yak wool insulation, cryogenicly treated to release signal-distorting sub-micron strain! A steal at $300/ft! Act now, and we will throw in our patented Feng Shui turntable stones - five of these will disgronificate your turntable! Normally $150 each, but a steal at $800 for a set!"