Nope, just the one. It's disappointing I know, but I'm the only one. (Made sure my kids have proper sounding, but globally unique names as well [at time of birth, YMMV, etc.])

Well, in my case at least the first comment (the one I made) actually has the proper information, and is diametrically opposed to the fake one; so at least in my case it's easy to prove that at least 1 is fake.

If it'd remove the stain from my name, I'd gladly see both of them go away (as my proper name is well, unique... can't blame the stupid on someone else if you're the only person on the planet with that name.)

Yep, got me here too; even though I have a previous accepted, disseminated comment supporting the Title II restrictions. Funny though how the duplicate got nearly everything right, except where I actually live, and that I might actually not be braindead.

I shouldn't say I'm surprised, I'm not, just oh, oh so jaded.

Thanks, looks interesting. I can see some applications for use in long term storage... it's better to get some data back rather than lose it all.

I wasn't trashing ActiveX per se; but rather the idea the label represents, binary embedding in (an expected) document; or binary embedding period. I hope most people read that I dislike the idea, not the brand name.

Or OCX (OLE, etc) lets another wolf into the flock. Embed by default is broken, and well terrifying.

You've never know a (clinical) sociopath; they're quite good at faking anything that furthers their wants.

My jumpdrive happily fits into that internet hole on the HP swatch thing... never could get it to read though.
(No... I really don't miss late 90's tech support)

At the risk of sounding like I've come from /b/, perhaps it won't break 4k because you're driving a Neon and a Scion. My RX-8 will break 9k RPM in park/neutral.
((Yeah, yeah, cue the /over 9000/ lines))

I use a similar system for personal use but I do not have it wipe all the data on each restart, instead I just wait for the system to start getting a bit sluggish or I am ready for a clean start and restore the original virtual machine. Still kind of a pain but so much better then restoring your whole system. I have been using this setup for a couple years and I have not had to reformat my main system.

Just to clarify, I was in a small town (Atwater). It's the kind of place where everyone knows your name (and in a biblical sense, probably your cousin). Elsewhere YMMV.

Last time I beat a speeding ticket in that state... I paid for it dearly. Six tickets for less than 3 mph over the limit in a month. I find, although morally repugnant, it's much cheaper to pay up now and complain later; rather than to invert the order.

Parece que he perdido mi copia de la guía, pero como yo soy un príncipe de Nigeria, con mucho gusto a comprar uno por $ 10 millones de dólares EE.UU., si usted me ayudará a transferir fondos de mi hermano, que ha robado mi difunto padre trono. Por favor, responda con su información bancaria para que podamos ayudarnos mutuamente.

Yes, I am familiar with that idea... the point however is access control. How do you decide the X lucky recipients of your partial key? How do you assume they are trustworthy? Then again, if you're not watching the logs, how to you know they aren't cheating the system, and trying to assemble the full key without your permission?

The whole point of DRM is to give permission when you wish. Any system that allows someone to skip asking permission, and later beg forgiveness is broken. In that same vein, any DRM system gives you the keys at some point, and says "do not unlock this door"; therefore it always fails, even if we use it simply because it's easier to ask then to beg permission.