On Mon, Jan 17, 2005 at 04:06:52PM -0500, Christopher Faylor wrote:
> On Mon, Jan 17, 2005 at 12:17:52PM -0800, Mark Geisert wrote:
> >If you have by now identified the hardware/OSversion you need to
> >reproduce the problem yourself, please let us know so we can stop
> >annoying you.
>
> I did as
On Mon, Jan 17, 2005 at 12:17:52PM -0800, Mark Geisert wrote:
>If you have by now identified the hardware/OSversion you need to
>reproduce the problem yourself, please let us know so we can stop
>annoying you.
I did ask for people to respond with hardware which shows the problem.
A simple respons
Hi Christopher,
If you have by now identified the hardware/OSversion you need to reproduce
the problem yourself, please let us know so we can stop annoying you. If
that info is not important, please let us know. If you haven't identified
the hw/OS, how will you figure this out without more (ideal
On Mon, Jan 17, 2005 at 12:47:56AM -0800, Mark Geisert wrote:
>Hi, I don't know how additional narrowing-down info about this can be
>posted without sounding like a redundant annoying "me too" but here goes.
>
>I can easily reproduce it on a Dell Workstation PWS360 running WinXP SP1.
>The CPU is a
4 matches
Mail list logo