drawString() is used to output a String to an applet. This method is included in the paint() of the Applet

getAppletInfo() : Returns a string describing the applet, its author, copyright information, etc.
getParameterInfo( ) method: Returns an array of string describing the applet's parameters

The applet stub interface provides the means by which an applet and the browser communicate. Your code will not typically implement this interface

In the same way every class that is defined by the user has access to methods defined in
Object class.
A few advantages of doing this 
-- Object class has a special privilages set in JVM (Any one who is an expert in JVM can comment on this)
-- All the methods defined in Object class have some functionality that is common if extended by any class. 
      User is given permission to override these defaults with the logic he/she intends with.
For ex--.
public class A {
       public boolean equals(Object obj) {
              //perform user logic here         } } 
--  Initiation of garbage collection happens through Object class

Legacy classes are those that were built using Java 1.1 or Java 1.2 API. In general we cannot use this term for java classes. Say for example when Java 1.0 was available Vector was used instead of dynamic array and since there was no ArrayList class people were forced to use Vector for this purpose.
When Java 1.2 was released ArrayList was much more advanced to Vector but has all the features of Vector too.
So people started using ArrayList instead of Vector (this again depends on the project requirement, both Vector and ArrayList have their own advantages). And in this case Vector became legacy class
But this is not constant since in future Sun may introduce a new class that is much more advanced to ArrayList and Vector. And then we call both ArrayList and Vector as legacy classes.
But in general a "legacy" is a term used to define a software created using older version of software.

The memory in the Virtual Machine is divided into a number of regions. One of these regions is PermGen. It~s an area of memory that is used to (among other things) load class files. The size of this memory region is fixed, i.e. it does not change when the VM is running. You can specify the size of this region with a commandline switch: -XX:MaxPermSize .
The default is 64 Mb on the Sun VMs.
If there~s a problem with garbage collecting classes and if you keep loading new classes, the VM will run out of space in that memory region, even if there~s plenty of memory available on the heap. Setting the -Xmx parameter will not help: this parameter only specifies the size of the total heap and does not affect the size of the PermGen region.