|BEST PRACTICE: Don't ignore or completely turn off Validation Messages|
Something should be done about validation messages and turning off more validations than required is not the way to handle the problem. Validation messages are an important feedback mechanism in ensuring quality packages. While you could use the "MsiValFilter" command or many other mechanisms to turn off all validations I would suggest you be very selective and only turn off those specific messages that after careful examination and thought you can safely ignore.
An unknown warning should be treated like an error until you are sure it is not an issue.
Also do not get into the habit of ignoring "known" issues, use the supplied mechanisms to ensure "clean" results so that any other reporting is immediately recognisable as a new issue (rather than you missing the new message as it is hidden in the middle of all your "expected" messages). That is the following "OK" message should always appear:
(@889)INFO: Validating the MSI (please wait)... (@889)INFO: Using: "C:\Program Files\MSIVAL2\darice.cub" (@889)INFO: Filtering validation results... (@889)INFO: ==================== (@889)INFO: === VALIDATED OK === (@889)INFO: ====================