The Barrow-Downs Discussion Forum

The Barrow-Downs Discussion Forum (http://forum.barrowdowns.com/index.php)
-   The Books (http://forum.barrowdowns.com/forumdisplay.php?f=9)
-   -   Saruman's acquiring of Isengard (http://forum.barrowdowns.com/showthread.php?t=1965)

The Balrog-Durin's Bane 09-07-2002 04:28 PM

Saruman's acquiring of Isengard
 
In my Middle-Earth knowledge, I still do not know how Saruman came by Isengard. Did he ask for it, did the men present him with it because they thought it would do him more good then them, or did saruman use his voice to convince them to hand over the fortress? I might have missed something in the book, or a small description. They said he was given the keys to it by the steward or something like that(i'd quote it but my trilogy is loaned out to a relative) but I was always supsicious that Saruman used his voice as I dont think Gondor would have so easily handed it over to him. Does anyone have any info on this? Anything would be appreciated.

piosenniel 09-07-2002 04:40 PM

Here is a reference for you:

Isengard

You can also find it in 'The Tolkien Companion' by Tyler - p. 238-9.

There is also a reference in the Barrow Downs' Encyclopedia in the section on Saruman:

Saruman

akhtene 09-07-2002 05:03 PM

Saruman settled in Isengard in 2726, after Rohan had suffered from invasions and Long Winter. Sone invaders,the Dunlendings came from Isengard. When they had been finally driven away by forces of Gondor, the Rohirrim were weakened and grieviously reduced.
Beren the Stuart was only happy to welcome a powerful friend at the border of the allied realm, which was rather helpless at the moment. The more so that Saruman was supposed to hold Isengard as Stewart's lieutenant.
I don't think that Saruman had to use any of his powers to convince the Stuart give him the key. At that time such an arrangement must have suited both (or better say all the three) sides involved.


All times are GMT -6. The time now is 01:06 PM.

Powered by vBulletin® Version 3.8.9 Beta 4
Copyright ©2000 - 2025, vBulletin Solutions, Inc.