4. Open your new wallet folder, and Rename "cleanwatercoin -qt_4.exe" to "cleanwatercoin -qt_4 -checknode=0.exe"
I'm sorry but you are mistaken, that won't make any difference at all for 2 reasons:
1) That's not how you send a command-line option to an executable. All you have done is change the filename, try renaming it to "cleanwatercoin-qt_4 -thisdoesnothinguseful.exe" it will have just as little effect.
2) As far as I am aware there is no such command line option as -checknode=0. You may be getting confused with -checkblocks=0 which will force your wallet to check every block on startup.
If you want to run your wallet with a command line option there are a couple of ways to do this:
1) Open a command line window and navigate to the folder your executable is in, and type the following:
cleanwatercoin-qt_4.exe -checkblocks=0
(Note the -checkblocks=0 is AFTER the .exe)
2) Open a new file in notepad, type exactly the same as above and click "Save As", choose "All Files" as the file type and save it as "RunCW.bat" - put this file in the same folder as cleanwatercoin-qt_4.exe and run it. You have now created a batch file which you can create a shortcut to and run from your desktop, and change as you wish if you want to add further command-line options to your wallet's startup routine in the future.
(BTW I wouldn't recommend running your wallet with -checkblocks=0 every time as it will take a very long time to load up each time)
Doh! So I guess the -checknode=0 wasn't doing anything all along! LOL! I got that from a suggestion in IRC weeks ago.
If the -checknode=0 was useless, it must be that I kept the conf file out of my %appdata% folder that allowed me to avoid bad nodes. Where/what addresses does the wallet try to connect to if there is no conf file? Perhaps just leaving out the conf file altogether will work for most people?
(I edited my previous post now that I realize the -checknode=0 was not actually doing anything
) 
