Agreed, that's why PasswordMaker has auto-populate.
Why? PasswordMaker is safe with keyloggers if you use auto-populate. With auto-populate, you type nothing.
Perhaps you should ask WHY this is in the FAQ before requesting it be removed? It looks like you didn't spend much time with PasswordMaker.
True, I have used mostly pwdhash, which has much less options.
I don't see how auto-populate would help somebody against keyloggers. Saving your password in a random text file is nice idea, but easy to catch for keyloggers too. Auto populate is nice if you have your master password typed in after the keylogger is enabled. When you start from scratch, PasswordMaker has now way to have your master password without you typing it in (or inserting it in another way).
When you are not on your own computer, it is not save to type your master password. Saying that PasswordMaker prevents against keyloggers is wrong if you don't describe how PasswordMaker protects against KeyLoggers. The statement that it does protect is wrong, and should be removed. You now may have people who use PasswordMaker in there local internet bar, and type in their master password and have all their accounts hacked.
PasswordMaker is a great concept, and it has his advantages, but without a challenge response system of some kind it isn't safe. It is maybe enough safety for your hotmail account, it is not safe enough for your bank details or logging in to your servers.
A method that is save is some kind of challenge response system. The cheapest and nicest I know is On Time Password Login package, which uses 100 codes on a piece of paper to give you a random code each time.
Remember, if you don't own the computer you are working at, anybody can monitor all your mouse clicks, key strokes and everything.
Regards,
Maarten