Monday, April 28, 2008

KABA Mac Problems?

I got the following request posted as a comment to another article:

I no longer have the ability to post on Keep and bear Arms board any longer having switch to Mac. I don't believe they know they have locked out a number of people because of this. If you some how could pass this on, thanks in advance. Yes I know I'm off topic to this story. (had to move to Mac because Vista sucks)
What I get when trying to post:

Microsoft VBScript runtime error '800a000d'

Type mismatch: 'oRSWordList'

/includes/subs_01.asp, line 241
Anyone else having Mac problems?

I'm not affiliated with KABA, but they are an important enough news source that they ought to be aware if this is an issue. I would suggest using their "Contact Us" link under the "About Us" tab, but will email one of the administrators with this.

A favor, please: I keep WarOnGuns posts on topic. If you have something that is not, or a request of me, please email me directly with it.

And indeed, Vista sucks.

19 comments:

Anonymous said...

I am a mac user but I don't normally post on KABA. I would try firefox. I don't use firefox a lot as I like Safari's speed compared to just about all other browsers, but it will usually work when all else fails.

Anonymous said...

Windows XP is getting the same sorts of errors when I try to post. Shortening the post or leaving the site and returning sometimes avoids the error message.

Jeff said...

Go return your Mac and install Ubuntu over Vista.

This should greatly enhance your life.

Also, Firefox would probably help.

David Codrea said...

Ah--some of us are assuming others of us share in tech savvy.

Bottom line: if it's a KABA issue, they need to make sure all can access their site--if it's just one guy having problems, then the helpful suggestions y'all are kindly providing may be the answer.

Me, I'm so burned on this new Microsoft crap I'm afraid to try anything new lest it freeze everything up and require me paying some egghead nerd to come into my house and laugh at the caveman.

Don't forget--some of us cut our teeth on the old coal-burning pull-start models.

Anonymous said...

What happens if he tries changing his user-agent string in Safari?

> Don't forget--some of us cut our teeth on the old coal-burning pull-start models.

"...uphill... both ways... in six feet of snow." ;-)

Mark Odell

Anonymous said...

I really do hate Vista. And I'm using it right now.....

About the only thing I like is the search bar added to the taskbar. And the Audio Mixer being able ot control volumes of individual programs.

I just hope enough people complain about Vista that they transform their SP1 into Vista XP (which means simply reverting it back to XP without buying an XP disk, but screws over those who actually payed for Vista) Vista Premium came on this machine, so I'm forced to get used to it for now.

Anonymous said...

Like Jeff said...
Ubuntu.
It's free, and it works.
Worth lots more than I paid for it.
Get the live CD and try it without installing.
Decrepitly slow, but will give you an Idea how it works.

Anonymous said...

I'm using a MacBook with MacOS 10.4 and using the stock Safari browser, just tested posting a comment on KABA and had no problem.

Stephen said...

Ugh... after trying unsuccessfully three times this morning to post here, i'm trying again (on a mac, safari, 10.5.2)

Stephen said...

Yay! It worked! I was having problems with the word verfication thingy.

Anonymous said...

The KABA site uses MS VBScript on the sever-side. To my knowledge, there is no use of VBScript client-side.

So any VBScript errors are *NOT* related to what operating system or web browser you use.

I happen to use SuSE Linux 10.3 with KDE 3.5.9 and my beloved Konqueror. ;-)

It works just fine.

Any *persistent* (as opposed to intermittent) VBScript errors should be reported to management.

Make sure when reporting issues you tell us what operating system & version; what browser & version, and what the exact error is. We need to be able to reproduce it in order to have a decent chance of fixing it.

Thanks,

Regards,

Mark A. Taff
KABA

Anonymous said...

Could I possibly prevail upon any of you to speak a language I understand? Please!

John S said...

straightarrow: Ok. The error reported is a program error from something running on the KABA site. "Type mismatch" is usually an error given when the program is expecting to get, say, a number and gets a character instead. (It can be a bunch more complicated than that.)

It has nothing at all to do with your operating system or your browser.

Based on Mark Taff's post, it seems to be transient, that is, it comes and goes. Without really good descriptions of what you were doing, what you typed and exactly what responses you got, it is very hard to fix those problems.

There is some reasonable likelihood that if you 'clear cache' your contribution to the problem might go away. Click on the Safari label at the top left of the top bar on your screen, select "Empty Cache" from the drop down menu, quit Safari, restart Safari.

David Codrea said...

I'm with SA.

"Klaatu Barada Nikto!"

Here: This might help.

As for quitting Safari, will I have to walk back across the savanna alone or can I get a porter to help with my gear? And have you ever been on a safari? Talk about clearing your cash!

Matt said...

A useful tip to help out those who have to solve such problems - when raising the issue, be sure to include what browser you use. I've forgotten how many times I've had to chase an error and learn its caused by Safari and doesn't manifest in FireFox or IE.

Oh, and Safari sucks, just FYI.

John S said...

"Oh, and Safari sucks, just FYI."

Oh, it isn't all that bad.

No browser is perfect. I like Firefox because I can easily turn off almost everything I don't want to see. Once in a while FF goes off into the ozone about some site that Safari has no problems rendering. For example, some Java things come up in too-small, non-resizeable windows that do not have scroll bars in FF on Mac (don't know about Windows).

And sometimes, to print a page from a site, I actually drop back to Explorer 5.2 (the last one built for OS X).

Anonymous said...

Uh... what?

StraightArrow? Wanna go fishin'?

Bill St. Clair said...

I just posted a comment to a newslink at keepandbeararms.com. Worked fine. Firefox on a Mac. My guess is that it was a short-lived server-side problem, that has been fixed.

Anonymous said...

it's theoretically a naughty word in your submission. i get that error occasionally, and despite spending more than 10 minutes trying to figure out what word is hitting the blacklist, no luck. whenever i get that error i just don't bother trying to post.