Deadwood Dick (serial)

Deadwood Dick is a 1940 American Western Serial film directed by James W. Horne and starring Don Douglas and Lorna Gray.

Deadwood Dick
Directed byJames W. Horne
Produced byLarry Darmour
Screenplay byWyndham Gittens
Morgan Cox
(as Morgan B. Cox)
George H. Plympton
(as George Plympton)
John Cutting
StarringDon Douglas
Lorna Gray
CinematographyJames S. Brown Jr.
Edited byDwight Caldwell
Earl Turner
Production
company
Columbia Pictures
Distributed byColumbia Pictures
Release date
  • July 19, 1940 (1940-07-19)
Running time
285 minutes
(15 episodes)
CountryUnited States
LanguageEnglish

Plot

Deadwood Dick, a masked and mysterious hero, is in reality Dick Stanley, editor of the Dakota Pioneer Press and a leading member of Statehood For Dakota. He is on the trail of a masked villain known as the Skull, who leads a violent, renegade band infamous for its violence against the Deadwood residents' wishes for a statehood status. Our hero soon discovers that the Skull terrorizes the town to prevent statehood from being achieved in order to build his own empire in the vast territory. However, Dick suspects that one of his fellow committeemen might be responsible for the string of criminal acts. It takes him 15 episodes and about 40 choreographed slugfests to finally uncover the truth and reward the Skull's villainy with an exemplary punishment.

Cast

Chapter titles
  1. A Wild West Empire
  2. Who is the Skull?
  3. Pirates of the Plains
  4. The Skull Baits a Trap
  5. Win, Lose or Draw
  6. Buried Alive
  7. The Chariot of Doom
  8. The Secret of Number Ten
  9. The Fatal Warning
  10. Framed for Murder
  11. The Bucket of Death
  12. A Race Against Time
  13. The Arsenal of Revolt
  14. Holding the Fort
  15. The Deadwood Express
gollark: > sqlite is not less complex than this formatYes. *But*, you don't actually have to interact with the SQLite disk format directly because libsqlite3 exists.
gollark: I suspect SQLite would lose out somewhat in storage efficiency, but it could plausibly be faster for many things at runtime.
gollark: It's less complex for everyone interacting with it, since they can just... use SQLite, which has bindings for everything, instead of "zimlib". And by "efficiency" do you mean "space efficiency" or "lookup efficiency"? Because, as I said, SQLite would probably only add a few bytes per directory entry row, which is not a significant increase.
gollark: SQLite's overhead is pretty low, and the majority of the filesize is from the binary blobs which would remain the same in each.
gollark: It's less complex for them as the code is already there and written with a nice API, and "less efficient" how? Slightly more space on headers?

See also
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.