Talk:Enhanced motion vehicle

This Additional daughter article -> EMV
The Enhanced Motion Vehicle should be a candidate for spinning off into an additional article. This would isolate the patent and operational details without spoiling the four articles that would reference it: Disneywizard (talk) 18:46, 9 April 2010 (UTC)
 * Dinosaur (Disney's Animal Kingdom)
 * Indiana Jones Adventure (expose)
 * Indiana Jones Adventure (Tokyo)
 * Indiana Jones Adventure

16-gig
In the "Audio systems" section: "Sections of track trigger various audio sequences stored onboard 16-gig EEPROM storage..."

This doesn't appear to make sense whether it is gigabits or gigabytes, as I'm not sure why that much storage space would be needed, and it would be physically impractical to provide that much storage via EEPROM chips as conventionally defined.

The claim appears to be unreferenced anyway; the patent that is cited elsewhere in the article mentions computer memory in general and EEPROMs in particular, but it does not address the question of storage capacity. --SoledadKabocha (talk) 19:44, 15 November 2015 (UTC)

It isn't clear whether the editor meant 16 gigabit (2 gigabyte) or 16 gigabyte. I have some personal expertise with the subject and given the short amount of audio used for a 5-minute ride, I wouldn't expect more than 30 minutes of audio to be stored in a multitrack format for this application. I'd think the former (16 gigabits) makes more sense. 16 gigabytes would be overkill for such an application. Perhaps, is this cited in the patent for the EMV?FA Jon (talk) 05:41, 7 June 2018 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on Enhanced motion vehicle. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20160109041546/http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=5623878 to http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=5623878

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 09:04, 21 September 2017 (UTC)