Talk:HMS Resolution

From Wikipedia, the free encyclopedia
Latest comment: 11 February 2011 by Benjamin Trovato in topic Sir Thomas Button and a ship named Resolution
Jump to navigation Jump to search

<templatestyles src="Module:Message box/tmbox.css"/><templatestyles src="Talk header/styles.css" />

Script error: No such module "Check for unknown parameters".Script error: No such module "Check for deprecated parameters".

Template:WikiProject banner shell

1653 Resolution

In the Image:Witmont, Battle of the Gabbard.jpg depicts the encounter between Dutch ship Brederode and a Resolution as early as in 1653, while the first Resolution listed in the page dates back to 1667. Any suggestion?--Panairjdde 14:25, 11 May 2005 (UTC)Reply

The ship depicted is the brand-new Tredagh of 66 cannon; this ship was renamed Resolution in 1660 and was destroyed by a Dutch fireship from Tromp's squadron in the St James's Day Battle in 1666. The renaming is of course the cause of the confusion :o).

--MWAK 09:28, 28 May 2005 (UTC)Reply

O, dear, I made a mistake; though the Tredagh was indeed renamed, the ship pictured was the Prince Royal, renamed Resolution during Commonwealth times, for obvious reasons.--MWAK 14:39, 19 June 2006 (UTC)Reply

Sir Thomas Button and a ship named Resolution

While wintering at Port Nelson, Manitoba many men died of scurvy, therefore the Resolution was abandoned and the voyage continued in the Discovery. The Port Nelson and the Nelson River were named after the master of the Resolution who died and was buried there. (Arthur S. Morton, A History of the Canadian West',page 30,no date, perhaps 1960) Benjamin Trovato (talk) 01:07, 11 February 2011 (UTC)Reply

12th Resolution

I believe the reference to the 12th Resolution on this article is actually the HMNZS Resolution (A-14). --JAYMEDINC 03:59, 30 December 2006 (UTC)Reply

1770 vs 1771

Cook's ship is listed as 1771 but the 1770 ship is listed until 1782. Overlap of the same ship or two with the same name? --MartinezMD (talk) 04:53, 14 September 2010 (UTC)Reply