Use VB Code To Autologin Various Websites?

Issue: Can't find a way to utilize process.start to enable automatic login to various websites.Program: A simple window form application with a desired module/form to store user passwords and websites and launch a login from the form (a very basic "password manager" and launch) Side-issue: Data storage (Not yet explored because of inability to solve main issue) , would like to use text file to store System.Security.SecureString data-type.

Narrative: I'm really new to all of this but not lazy or unwilling to do the work. Two and-half months of no less than 14 hours per day reading and applying myself to VB language and VS IDE. Been able to solve all my own problems thus far with help of Web or my $600 library investment, and have a working app that I've been able to deploy. However, neither of these assets seems to hold answer for this problem, and unlike others I've encountered, I can't find a work-around.

Potential Answers: It seems that answers may lie within an HTML/XML/JS/AJAX get/post route, but this is an entire new area of study/research that I hope to avoid if there is indeed an answer utilizing Process.Start. There also seems to be a potential to solve my problem using ASP.NET, or using System.Windows.Browser and HTMLElementCollection (for the last I've only found snippets of code that utilize My.Settings.UserName, & My.Settings.Password, and it is unclear to me if these settings reflect the login to user machine or to actual desired site).

My Hope: (which may be forlorn) is that there is a simple explanation on how to plug a value in to the last parameter of Process. Start ---"Domain". I'm assuming Domain is not what I would normally interpret to be the root of a website, but is instead particular to user machine. I've found no good examples, other than a hint of using System.Configuration.ConfigurationManager, and statements that old VBCode made access easy.

My Assumption: I'm thinking this is another area where my newbie status has made me a believer there's a solution within my grasp before I found the answer but after I made a commitment. VS2008 fooled me in a similar manner in three other areas thus far, the PrintDialog control duped me into thinking printing was an easy process, HelpProvider control had me totlally convinced that Help installation was a snap, and OneClick deceived me into believing deployment was oh so simple.

Process.Start may be another place I've been had, but if you speak pretty good newbie Anyway, here's the small bit of code I've been playing with but without luck (Win32 exception, parameters are incorrect:)

[Code]...