I realize what he's talking about, but he's not quite on the ball. Reading the charge doesn't obliterate the state, and the caps naturally decay which is what refresh is all about anyway. And as I stated, while not an expert at quantum physics, I don't believe you can refresh quantum bits the same way that you can refresh decaying charge in a cap.
Uh... sensing the charge on a capacitor doesn't destroy the charge on that capacitor. Yes, there will be some (increased) leakage by the sense amps but you're clearly stretching things here.
While my understanding of quantum theory is not as extensive as my electrical knowlege, I'm under the impression that making an observation of a quantum bit destroys its state. The two don't seem to be anything similar.
Yeah and I bet the tiny screen and lack of real keyboard are real convenient, too.
Palms are meant as extensions to a real computer, not a real computer replacement. People who constantly try to put ten pounds of shit in a one-pound bag are rather amusing, because it's usually those same people who give up after a while, claiming that the Palm platform sucks balls because it can't replace their computer.
If it works for you, great, but you are one of the very small minority who can function in such a restrictive environment. And hell, I'm an embedded systems designer, I know all about restrictive environments.:-)
I used to love my V, then got an m515 and was totally in love with it. the LED on the power button and the vibrate motor were awesome additions, and the colour was alright too. Battery life still rocked.
Now I've got a Tungsten E and even though I miss the lack of the LED and vibrate motor and I miss the form factor that the V and 500 series had, I can't give up the screen. Hell I miss the cradle/serial port connection but I got over it. Battery life is still stellar but that screen is just unbelievable. I didn't think I'd give a shit about a high-res colour screen on a Palm but I'm telling you I use those features every single day. Yes battery life isn't what the V had but you know what, lasting a full week to two weeks without a recharge is still pretty damned good in my opinion.
I've never understood how BPL even made it to the trial stage. Any EE with two brain cells is going to recognize that putting broadband HF/VHF carriers on unshielded power lines is a recipe for interference to many licensed radio services. See that wire going down the road? It's a fscking antenna, you moron!
What a brilliant navel-gazing point of view.
I personally wouldn't mind seeing the signal combined with a decent spreading code to minimize the peaks in the spectral pattern (at the cost of raising the general noise floor, yes) or even figuring a way to couple the three phases together such that at a distance the radiated power would be next to nil, in much the same way that thousands of Amps of current flow through the lines but there's hardly any net magnetic flux when you're even a dozen feet away from the lines.
Technical problems are there to be overcome. Simply throwing your hands in the air saying "of course there are going to be problems, what a moron" is a combination of elitism and a defeatist attitude the likes of which I've never seen before. Do you give up on everything because someone said it was going to be hard?
Amateur radio operators (note: I am not one) are the first people to use their "lovably nerdy hobby" in practically every major emergency to coordinate resources and get help to where it's needed most. Amateur radio is far, far more than some little hobby. Making things difficult or impossible for this (small and growing smaller, sadly) portion of the population is not something to be taken lightly. They're not your neighbourhood vintage car restorer.
Oracle already bought out Steltor's CorporateTime, which was an Exchange Killer, and then buried it in proprietary bullshit. I've since moved over to Exchange4Linux, which, barring the poor name, I feel really is an Exchange Killer.
Basically the entire thing runs inside of Postfix and PostgreSQL. It's written in Python, and the server software is 100% open source. The Outlook Connector is not (it too is written in Python). So far it's been working great (huge datastore, calendaring, delegation, it all works). Basically N-H went about it differently than all the others: instead of making Outlook wrap around open services, they made the open services conform to Microsoft's bastardized MAPI. I have to say this has owrked better than anything else I've found.
Riders should be disallowed, period. Attaching a completely unrelated bit of business on to a bill is insane, especially since it does not have to be pointed out BIG FLASHY LETTERS that someone's trying to sneak something through.
Take it from someone with a UID one tenth yours - low UIDs are meaningless.
As someone with a UID 1/10 of yours, I have to agree; all it means is that I got here before you. Every now and again I notice the UID but it is never something I go out and seek.
(having said that, I wonder if user 150 and then user 15 will reply, this is kind of an interesting thread:-)
I dunno about you, but I read over the document with the hidden parts unhid... I did not see anything that was hidden that would have revealed the soliders did anything wrong; the classified bits were more about details about the war and specific training.
Again: the full document does not incriminate the soldiers. This looks like typical censoring of specific details which might make it easier for the enemy to break through the defenses.
An electric drill -- of the non-cordless variety -- throws out just such an EM field. Try firing one up next to your monitor. (At the risk of advertising my age -- this is slashdot, I know better than to say dating myself -- back in the old days this was considered one way to manually de-gauss a monitor. Move an electric drill under power back and forth around the edges. It worked, after a fashion. Or at least we got a neat light show out of it.)
The EM field you see on your monitor is not capable of inducing any serious current into anything; (cheap) monitors are extremely sensitive to any magnetic field. Even your flexible fridge magnets have enough of a field to cause deflection errors. You can also confirm that the drill's field is NOT far-reaching just by noticing how much reduced the effect is even 6 inches away.
Throwing a little current into the traces is not what you have to worry about. It's the CMOS chips. A changing EM field can induce a current in the silicon itself, as well as the wires leading to it. It doesn't take a lot to fry one. As in you won't even feel the electric shock.
This is where I can tell that you have some electricity knowlege but it's only "enough to be dangerous." -- Yes, CMOS is sensitive but it is sensitive because of the extremely thin oxide later at the junction of the FETs. Static electricity can punch through this oxide layer at extraordinarily low potentials. Magnetic fields can damage equipment by induction. If it hasn't got enough power to induce signficant current in the traces, it ain't gonna do shit to the (much much much smaller) traces on the dies. ICs (CMOS or otherwise) are far more likely to die from static than induced currents simply because it's rather hard to get a strong enough magnetic field coupled to the circuit board in such a way to generate a damaging current.
I don't know what you're designing, but I generally don't run current through my heatsinks. At thousands of amps, your heat loss is going to be enormous (RI^2). What voltage are you running at? Is it some ultra-low-voltage ultra-high-current app? Or are you in some massive industrial environment? Is your heatsink between your circuit and the powerline? Is it acting as a faraday shield? Is the current AC or DC? Is it changing over time? Is your circuit moving relative to the powerline? Or have you avoided that whole inductive currents issue? Are you really sticking CMOS right next to a strong inductive field with no shielding? Not even a little pig iron? Or are you using TTL or other, more robust, less sensitive, components?
Industrial motion controllers, soft starters and VFDs. Unbelievably noisy environments and no, the only thing between the heat sink and the circuit board is a sheet of 3/8" Lexan. It's all AC (at least in, we do some DC conversion for oddball applications, startup current is typically 3-6x the running (steady-state) current, and fault currents can be thousands of times nominal, although part of the job of the controller is to prevent them. The ICs on the board are almost exclusively CMOS (PICs, Motorola 683XX, op-amps, ADCs, etc.). The heat sink is used as the conductor, it sandwiches the high current "hockey puck" style SCRs. (it's been a while since I've seen a large VFD but I think they still use the brick style modules.)
Back when I used to work in the magnetometer lab, we had serious problems with inductive noise. It's amazing how many sources there are. Then again, we were working at the sub-microvolt level. Ventilation moving the wires caused us noise. Still, I earned my stripes on unwanted inductively and capacitively coupling fields.
Yes; if you're trying to measure tiny voltages you are in for a rough ride; one of the engineers here used to build detectors for tiny tiny currents. The measurement table was not only stabilized but had to be isolated from the rest of the room for motion. All the wires had to be taped down and immobilized or their motion would induce (ti
Or, if applied in the right place, it could be as strong the a hand of a compass.
Sure, but if you've got the lid off the drive you've got bigger problems anyway.
Besides, that HDD "degausser" is likely to render the HDD useless anyway; you'd have to re-low-level-format the HDD to put all the cylinder indexes back on the platters.
I've managed, unfortunately, to fry a pda that way. Pda was in my pants pocket. I was drilling holes in my wall. The EM field from the drill fried the motherboard. And they weren't that close together...
Bullshit. I am an embedded systems designer and there's no way in hell your drill induced enough of an EM field to generate significant current in the traces of your PDA's mainboard. The stuff I design is strapped on to heatsink with thousands of Amps running through it without any kind of EMC protection and it runs flawlessly. Static discharge is more likely than not the cause of that particular failure.
Doesn't 2000rpm fan produce 2kHz electromagnetic wave regardless of the current?
No.
the magnetic field in any motor is VERY tightly coupled. Use a magnetometer (I think that's the name of the instrument anyway) -- you'll be hard pressed to find any significant magnetic field near a motor. And I'm talking about the thousands of horsepower motors industry uses, not the tiny little impedance-protected DC motors in your computer.
Similarly, you can't set up a coil and pull power from the high tension lines running around the nation -- the three phases are in close proximity to each other (at least relative to you on the ground) and their magnetic fields cancel out. If you can get close enough to one of the lines you can induce a bit of power and run some lights... we had a snowmobile hut that had "free power" for lights by doing this.
"Hey, I like this little color-selector widget that company XYZ uses in their paint program. It doesn't have the strange little artifacts here and there that ours does. I wonder how they did that? Fire up the debugger... oh, they hooked into WinObscureInternalFunctionCall32 and did fleem"
You could argue that you're reverse engineering the app to get (better) interoperability with Win32...
HylaFax is very nice but I have a Lucent Max I'd like to use its modems for Hylafax. Basically if you telnet to port 9000 you get an AT command session to one of the modems. I've been looking for a serial port emulator that when you open/dev/fakettyx it simply opens a telnet session to s.o.me.ip:9000 and relays data back and forth.
I've found plenty of things that do the opposite (telnet to them and they open a real serial port) but so far my quest has been unfulfilled.
The DMCA specifically allows reverse engineering for compatibility.
I just had a discussion over dinner with some friends about this very subject. What it basically came down to was that even if there is a provision for it, it's gonna take someone with deep pockets willing to go to court over this. Hell even Adobe won't take it on, and they'd need it to use the Nikon raw file format.
The discussion also brought up an interesting point -- When is compatibility not the reason to reverse-engineer something? I mean even if you reverse engineer with the intent to make your own product, are you not technically trying to interoperate with something else?
This is incorrect. You're thinking of trademark law. In the United States (and presumably elsewhere), patents can be selectively enforced to the heart's delight of the patent holder.
Which is, IMO, one of the biggest failings of patent law. It allows the patent holder to sit tight until someone with a lot of money (or political differences) comes along and only then "pounce". Hardly the spirit and original intent of patents.
Are you the parent or are your kids parenting you? My children go to bed when told; that is usually between 7 and 8pm. I don't give a rat's ass whether the sun's up or not, as they are sleeping the entire 12 hours and waking up at the appropriate time. This tells me they need the sleep. When they start waking up at 5am because they're not tired, I will adjust their bedtime appropriately later to compensate.
Yes, my five year old daughter and four year old son say equally cute and warm fuzzy things but they aren't responsible for parenting themselves; that is my duty. Tugging at the heartstrings may buy you a few more minutes but when they're tired, they're tired, and I will put them to bed.
And it runs on Windows, Mac and Linux natively. None of this WINE nonsense. Clicky.
Not affiliated with them by any means, just a happy customer. I'm planning on eliminating AccPAC and MiSYS at my office for their Appgen Custom Suite since it too is multiplatform, modular and you can get a developer license without the hassles that AccPAC has.
If data integrity is not present, I don't want that db near my application ever...
Then you don't want MySQL. Their philosophy is that if the data doesn't fit, they'll make it fit and not tell you (great philosophy, eh?). They say that you should do all the data checking in the application. Great idea -- not. WTF's the point of table constraints?
Slashdot Mirror
I realize what he's talking about, but he's not quite on the ball. Reading the charge doesn't obliterate the state, and the caps naturally decay which is what refresh is all about anyway. And as I stated, while not an expert at quantum physics, I don't believe you can refresh quantum bits the same way that you can refresh decaying charge in a cap.
Uh... sensing the charge on a capacitor doesn't destroy the charge on that capacitor. Yes, there will be some (increased) leakage by the sense amps but you're clearly stretching things here.
While my understanding of quantum theory is not as extensive as my electrical knowlege, I'm under the impression that making an observation of a quantum bit destroys its state. The two don't seem to be anything similar.
Yeah and I bet the tiny screen and lack of real keyboard are real convenient, too.
Palms are meant as extensions to a real computer, not a real computer replacement. People who constantly try to put ten pounds of shit in a one-pound bag are rather amusing, because it's usually those same people who give up after a while, claiming that the Palm platform sucks balls because it can't replace their computer.
If it works for you, great, but you are one of the very small minority who can function in such a restrictive environment. And hell, I'm an embedded systems designer, I know all about restrictive environments. :-)
I used to love my V, then got an m515 and was totally in love with it. the LED on the power button and the vibrate motor were awesome additions, and the colour was alright too. Battery life still rocked.
Now I've got a Tungsten E and even though I miss the lack of the LED and vibrate motor and I miss the form factor that the V and 500 series had, I can't give up the screen. Hell I miss the cradle/serial port connection but I got over it. Battery life is still stellar but that screen is just unbelievable. I didn't think I'd give a shit about a high-res colour screen on a Palm but I'm telling you I use those features every single day. Yes battery life isn't what the V had but you know what, lasting a full week to two weeks without a recharge is still pretty damned good in my opinion.
I've never understood how BPL even made it to the trial stage. Any EE with two brain cells is going to recognize that putting broadband HF/VHF carriers on unshielded power lines is a recipe for interference to many licensed radio services. See that wire going down the road? It's a fscking antenna, you moron!
What a brilliant navel-gazing point of view.
I personally wouldn't mind seeing the signal combined with a decent spreading code to minimize the peaks in the spectral pattern (at the cost of raising the general noise floor, yes) or even figuring a way to couple the three phases together such that at a distance the radiated power would be next to nil, in much the same way that thousands of Amps of current flow through the lines but there's hardly any net magnetic flux when you're even a dozen feet away from the lines.
Technical problems are there to be overcome. Simply throwing your hands in the air saying "of course there are going to be problems, what a moron" is a combination of elitism and a defeatist attitude the likes of which I've never seen before. Do you give up on everything because someone said it was going to be hard?
You're funny.
Amateur radio operators (note: I am not one) are the first people to use their "lovably nerdy hobby" in practically every major emergency to coordinate resources and get help to where it's needed most. Amateur radio is far, far more than some little hobby. Making things difficult or impossible for this (small and growing smaller, sadly) portion of the population is not something to be taken lightly. They're not your neighbourhood vintage car restorer.
Hey, i dont have a 6 pack.
I do, but it's behind the keg.
Oracle already bought out Steltor's CorporateTime, which was an Exchange Killer, and then buried it in proprietary bullshit. I've since moved over to Exchange4Linux, which, barring the poor name, I feel really is an Exchange Killer.
Basically the entire thing runs inside of Postfix and PostgreSQL. It's written in Python, and the server software is 100% open source. The Outlook Connector is not (it too is written in Python). So far it's been working great (huge datastore, calendaring, delegation, it all works). Basically N-H went about it differently than all the others: instead of making Outlook wrap around open services, they made the open services conform to Microsoft's bastardized MAPI. I have to say this has owrked better than anything else I've found.
I think you missed one thing:
Riders should be disallowed, period. Attaching a completely unrelated bit of business on to a bill is insane, especially since it does not have to be pointed out BIG FLASHY LETTERS that someone's trying to sneak something through.
Take it from someone with a UID one tenth yours - low UIDs are meaningless.
As someone with a UID 1/10 of yours, I have to agree; all it means is that I got here before you. Every now and again I notice the UID but it is never something I go out and seek.
(having said that, I wonder if user 150 and then user 15 will reply, this is kind of an interesting thread :-)
Unless he's changed it since you posting that and me reading it, it looks like a short, concise resume to me.
According to Giuliana, they were not driving fast and the U.S. military had been informed of their presence.
It should be a simple matter to prove that the US was informed of their presence.
I dunno about you, but I read over the document with the hidden parts unhid... I did not see anything that was hidden that would have revealed the soliders did anything wrong; the classified bits were more about details about the war and specific training.
Again: the full document does not incriminate the soldiers. This looks like typical censoring of specific details which might make it easier for the enemy to break through the defenses.
An electric drill -- of the non-cordless variety -- throws out just such an EM field. Try firing one up next to your monitor. (At the risk of advertising my age -- this is slashdot, I know better than to say dating myself -- back in the old days this was considered one way to manually de-gauss a monitor. Move an electric drill under power back and forth around the edges. It worked, after a fashion. Or at least we got a neat light show out of it.)
The EM field you see on your monitor is not capable of inducing any serious current into anything; (cheap) monitors are extremely sensitive to any magnetic field. Even your flexible fridge magnets have enough of a field to cause deflection errors. You can also confirm that the drill's field is NOT far-reaching just by noticing how much reduced the effect is even 6 inches away.
Throwing a little current into the traces is not what you have to worry about. It's the CMOS chips. A changing EM field can induce a current in the silicon itself, as well as the wires leading to it. It doesn't take a lot to fry one. As in you won't even feel the electric shock.
This is where I can tell that you have some electricity knowlege but it's only "enough to be dangerous." -- Yes, CMOS is sensitive but it is sensitive because of the extremely thin oxide later at the junction of the FETs. Static electricity can punch through this oxide layer at extraordinarily low potentials. Magnetic fields can damage equipment by induction. If it hasn't got enough power to induce signficant current in the traces, it ain't gonna do shit to the (much much much smaller) traces on the dies. ICs (CMOS or otherwise) are far more likely to die from static than induced currents simply because it's rather hard to get a strong enough magnetic field coupled to the circuit board in such a way to generate a damaging current.
I don't know what you're designing, but I generally don't run current through my heatsinks. At thousands of amps, your heat loss is going to be enormous (RI^2). What voltage are you running at? Is it some ultra-low-voltage ultra-high-current app? Or are you in some massive industrial environment? Is your heatsink between your circuit and the powerline? Is it acting as a faraday shield? Is the current AC or DC? Is it changing over time? Is your circuit moving relative to the powerline? Or have you avoided that whole inductive currents issue? Are you really sticking CMOS right next to a strong inductive field with no shielding? Not even a little pig iron? Or are you using TTL or other, more robust, less sensitive, components?
Industrial motion controllers, soft starters and VFDs. Unbelievably noisy environments and no, the only thing between the heat sink and the circuit board is a sheet of 3/8" Lexan. It's all AC (at least in, we do some DC conversion for oddball applications, startup current is typically 3-6x the running (steady-state) current, and fault currents can be thousands of times nominal, although part of the job of the controller is to prevent them. The ICs on the board are almost exclusively CMOS (PICs, Motorola 683XX, op-amps, ADCs, etc.). The heat sink is used as the conductor, it sandwiches the high current "hockey puck" style SCRs. (it's been a while since I've seen a large VFD but I think they still use the brick style modules.)
Back when I used to work in the magnetometer lab, we had serious problems with inductive noise. It's amazing how many sources there are. Then again, we were working at the sub-microvolt level. Ventilation moving the wires caused us noise. Still, I earned my stripes on unwanted inductively and capacitively coupling fields.
Yes; if you're trying to measure tiny voltages you are in for a rough ride; one of the engineers here used to build detectors for tiny tiny currents. The measurement table was not only stabilized but had to be isolated from the rest of the room for motion. All the wires had to be taped down and immobilized or their motion would induce (ti
Or, if applied in the right place, it could be as strong the a hand of a compass.
Sure, but if you've got the lid off the drive you've got bigger problems anyway.
Besides, that HDD "degausser" is likely to render the HDD useless anyway; you'd have to re-low-level-format the HDD to put all the cylinder indexes back on the platters.
I've managed, unfortunately, to fry a pda that way. Pda was in my pants pocket. I was drilling holes in my wall. The EM field from the drill fried the motherboard. And they weren't that close together...
Bullshit. I am an embedded systems designer and there's no way in hell your drill induced enough of an EM field to generate significant current in the traces of your PDA's mainboard. The stuff I design is strapped on to heatsink with thousands of Amps running through it without any kind of EMC protection and it runs flawlessly. Static discharge is more likely than not the cause of that particular failure.
Doesn't 2000rpm fan produce 2kHz electromagnetic wave regardless of the current?
No.
the magnetic field in any motor is VERY tightly coupled. Use a magnetometer (I think that's the name of the instrument anyway) -- you'll be hard pressed to find any significant magnetic field near a motor. And I'm talking about the thousands of horsepower motors industry uses, not the tiny little impedance-protected DC motors in your computer.
Similarly, you can't set up a coil and pull power from the high tension lines running around the nation -- the three phases are in close proximity to each other (at least relative to you on the ground) and their magnetic fields cancel out. If you can get close enough to one of the lines you can induce a bit of power and run some lights... we had a snowmobile hut that had "free power" for lights by doing this.
"Hey, I like this little color-selector widget that company XYZ uses in their paint program. It doesn't have the strange little artifacts here and there that ours does. I wonder how they did that? Fire up the debugger... oh, they hooked into WinObscureInternalFunctionCall32 and did fleem"
You could argue that you're reverse engineering the app to get (better) interoperability with Win32...
HylaFax is very nice but I have a Lucent Max I'd like to use its modems for Hylafax. Basically if you telnet to port 9000 you get an AT command session to one of the modems. I've been looking for a serial port emulator that when you open /dev/fakettyx it simply opens a telnet session to s.o.me.ip:9000 and relays data back and forth.
I've found plenty of things that do the opposite (telnet to them and they open a real serial port) but so far my quest has been unfulfilled.
The DMCA specifically allows reverse engineering for compatibility.
I just had a discussion over dinner with some friends about this very subject. What it basically came down to was that even if there is a provision for it, it's gonna take someone with deep pockets willing to go to court over this. Hell even Adobe won't take it on, and they'd need it to use the Nikon raw file format.
The discussion also brought up an interesting point -- When is compatibility not the reason to reverse-engineer something? I mean even if you reverse engineer with the intent to make your own product, are you not technically trying to interoperate with something else?
Amish. On Slashdot. +5 funny.
This is incorrect. You're thinking of trademark law. In the United States (and presumably elsewhere), patents can be selectively enforced to the heart's delight of the patent holder.
Which is, IMO, one of the biggest failings of patent law. It allows the patent holder to sit tight until someone with a lot of money (or political differences) comes along and only then "pounce". Hardly the spirit and original intent of patents.
Are you the parent or are your kids parenting you? My children go to bed when told; that is usually between 7 and 8pm. I don't give a rat's ass whether the sun's up or not, as they are sleeping the entire 12 hours and waking up at the appropriate time. This tells me they need the sleep. When they start waking up at 5am because they're not tired, I will adjust their bedtime appropriately later to compensate.
Yes, my five year old daughter and four year old son say equally cute and warm fuzzy things but they aren't responsible for parenting themselves; that is my duty. Tugging at the heartstrings may buy you a few more minutes but when they're tired, they're tired, and I will put them to bed.
And it runs on Windows, Mac and Linux natively. None of this WINE nonsense. Clicky.
Not affiliated with them by any means, just a happy customer. I'm planning on eliminating AccPAC and MiSYS at my office for their Appgen Custom Suite since it too is multiplatform, modular and you can get a developer license without the hassles that AccPAC has.
If data integrity is not present, I don't want that db near my application ever ...
Then you don't want MySQL. Their philosophy is that if the data doesn't fit, they'll make it fit and not tell you (great philosophy, eh?). They say that you should do all the data checking in the application. Great idea -- not. WTF's the point of table constraints?