The way those tools work is that they write a customized firmware image onto the controller. (or an EEPROM, or the start of the flash) This way, if you don't need the thing to impersonate a CDROM, that code doesn't get loaded onto the chip. Specifics about partition sizes, read-only settings, etc, get tacked onto the end of the appropriate image as a data block.
If the chip manufacturer released a firmware update to address a bug in a previous release, the same tools can be used to install the firmware updates. You just have to replace the packaged images.
But you don't HAVE to use the bundled firmware images. A little legwork (or disassembly of the bundled firmwares) will yield all you need to know to write your own firmware for the thing that does whatever you want it to. Frequently, like the MV6208, the controller is built around an 8051-derivative. ( ref: http://www.belinking.com/downl... ) knowing that, you can write your own custom firmware that enumerates as a second keyboard to try and run commands. Or whatever else you want to make it do.
A typical USB stick or a webcam don't have hardware to permit firmware upgrades, even though the silicon inside could be theoretically upgradable.
How uninformed you are!
https://forums.hak5.org/index.php?/topic/8630-collection-of-production-tools-for-usb-devices/ is a discussion of "production tools" for USB flash drives.
These tools are specific to the controller in the flashdrive (chipsbank, micov, etc) and allow you to do things like change what size the drive reports itself as, load files onto the thing and make it behave as a read-only flash drive, load files on and make it behave as a USB CD/DVD-ROM drive with a disk preloaded, make it behave as a single flashdrive with multiple partitions, make it come up on the USB bus as a compound device consisting of any combination of the above.
My company uses these sorts of tools to distribute software on read-only flashdrives.
That's why it's important to actually read what they wrote instead of just stopping at the first "red flag" you come to.
Why flexible funding? We choose flexible funding because we want to give people a chance to contribute to the software as early as possible. The hardware part is already done and we have sold units to existing customers who were very happy about it. Specially for this campaign we made a new revision ready for mass production so we can sell it at an even better price than we already had in our shop: https://dptechnics.com/shop/?q...
They already have finalized hardware in production. They're not trying to fund hardware development and production. They've already done that. They're using indiegogo as an advertising channel and as a secondary storefront.
The steering wheel.
Most vehicles (if not all) being marketed for consumer road use have power steering. The standard (in the USA, if not globally) is to use hydraulics to help you move the wheels back and forth as you steer.
Those two models of Audi use electric motors to provide power assist, instead. That makes it MUCH easier to interface the control system.
duckintheface didn't say it wasn't being used in court.
the statement was that it can't [LEGALLY] be used in court.
Dude. Some shit ain't going to get upgraded no matter how many times you taze that dead horse.
Hell, I've still got SunOS 4.0 in production.
Link to Original Source
The entry for "Alpha Particles" was updated from "Harmless." to "Mostly Harmless." quite some time ago. Because it is... AS LONG AS the emitter is *OUTSIDE* the body.
An alpha particle is going to steal electrons from the first molecule it comes in contact with, and become a helium atom. If you're exposed to alpha radiation from the outside, it's going to hit and react with the layer of already dead skin cells called the epidermis.
So yes, as long as you don't swallow, inhale, inject, or otherwise insert the alpha-emitting radioisotope, you're probably going to be just fine.