Very simple.

dnnprintmode=true (this is what signals DNN to even worry about it)

mid is your Module Id - simplest way to determine this - go to Edit mode or Settings for this module and see in url something like /mid/123/ or mid=123 - the number is the value of your Module Id

SkinSrc - thi is the replative path to the Skin file you want to use when displaying Printer Friendly version - the structure of that path is as follows [G] or [L] followed by folder name(s) where file is and FileName without the extenstion - [G] gets replaced with a path to your Portals/-default/ folder and [L] gets replaced with a path to your current portal folder. So, if I wanted to reference a No Skin skin :) that is located in Portals/_default/Skins/_default folder, I'd do [G]/Skins/_default/No Skin - notice the absense of .ascx

ContainerSrc is the same as SkinSrc but, you guessed it, for a container.

Ok , I guess I'm missing something here.

I want to dynanically in code set the print link based on the edit/details page I am on.  The edit page will have a "print" link button and all I want to do is have it launch the same print view in a new browser the same way as the pritn link does for a module.  I don't want to hardcode anything.  So basically on click I want to create it and trigger it but I'm still not sure where these parameters are all coming from or how to call it.