debugging obscure errors

If there's a web page error on a Gecko browser, it's easy to open the
javascript console (either before or after) to get details of the error
& line number.

Is there anything similar for ie6 ?

Background:
We've had a couple of obscure errors (ie we can't reproduce them), and
our non-technical customers aren't able to tell us much beyond "error on
page".
The user-agent is "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;
SV1; .NET CLR 1.1.4322)", which is ie6, winxp, and I'm guessing it's a
Swiss language variant.
If we could get the customer to give us good diagnostic information in a
couple of clicks, as with Gecko, it would help a lot - as it is, it's
just too hard, and she just wanted to fax the order & forget about it -
which means we can't fix it.

That's the general question - the page is several steps down an ordering
process ...
I'd sooner solve the general question of how to debug, as well as the
specific question of what's broke, but here's page details anyway:
services.ccagroup.co.uk/upbin/oformw?5BH370&bhs
enter quantity 20, Proof No, continue; wording any of d1-d4, continue to
personalisation; enter the wedding date & time.
Javascript is required, and the wedding date & time do little pop-ups,
which are where the problem is.
The underlying code's getting old, and falls short of recent best
practice, I know, but it works quite well and we get largely positive
feedback.

Thanks,
Chris

Safalra wrote:

Chris Sharman wrote:
The user-agent is "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;
SV1; .NET CLR 1.1.4322)", which is ie6, winxp, and I'm guessing it's
Swiss language variant.

SV1 stands for Security Version 1 (from Service Pack 2, I think), not
Svenska. Good guess though...

Oh - our pc expert is checking his sp2 upgrade now - he thought he had
it, but he's missing the 'SV1'.

Debugging in IE isn't possible without an extension (or getting the
user to insert lots of extra code...).

Boo, hiss. That makes life difficult. Still, perhaps when he's sorted
out sp2 we'll have more luck reproducing the problem locally ...

Thanks,
Chris