My user agent string is "Mozilla/4.5 [en] (Win98; I)", yet I get an OS of "Other" by default.

This bug is so easy to fix. Just add: /Mozilla.*\(Win98.*\)/ && do {return "Windows 98";}; to enter_bug.cgi Any reason why this easy bug hasn't been fixed? Or just time og lack of same?

Lack of time/focus/memory/organization. Something like that. Providing a patch makes it so excrutiatingly easy, though, that I run out of excuses. Fixed. Thanks!

Instead of: /Mozilla.*\(Win16.*\)/ && do {return "Windows 3.1";}; /Mozilla.*\(Win95.*\)/ && do {return "Windows 95";}; /Mozilla.*\(Win98.*\)/ && do {return "Windows 98";}; /Mozilla.*\(WinNT.*\)/ && do {return "Windows NT";}; it properly should be: /Mozilla.*\((Win16|Windows 3.1).*\)/ && do {return "Windows 3.1";}; /Mozilla.*\((Win95|Windows 95).*\)/ && do {return "Windows 95";}; /Mozilla.*\((Win98|Windows 98).*\)/ && do {return "Windows 98";}; /Mozilla.*\((WinNT|Windows NT).*\)/ && do {return "Windows NT";}; /Mozilla.*\((Win2000|Windows 2000).*\)/ && do {return "Windows 2000";}; I'm not quite sure the reg.exp is correct? Then Internet Explorer works to because the useragent string is: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)

Perhaps even: /Mozilla.*\((Win2000|Windows 2000|Win2k).*\)/

"I'm not quite sure the reg.exp is correct?" What aren't you sure about? Me, I'm not sure what the rules are at all in the user-agent field.

If this bug has been fixed why can't I access www.freelotto.com without an error report coming up telling me that it's malformed?

See also bug 35154.

Adding default QA contact to all open Webtools/Bugzilla bugs lacking one. Sorry for the spam.

moving to real milestones...

This got reopened after the changeover, and missed getting reassinged to tara... The person who reopened this is complaining of getting an error trying to access www.freelotto.com. What does that have to do with Bugzilla? I think this should be re-fixed, was reopened in error. CCing adawn@1st.net (reopener) for comment.

-> Bugzilla product, Creating Bugs component, reassigning. Maybe this just needs to be marked fixed again.

no comment from adawn@1st.net, who reopened the bug, in over a year. Setting this back to fixed, and setting the milestone to reflect the version it was fixed in. There are still a couple issues with this, but they're covered on bug 35154.