where else exactly could the problem lie?? All you have to do is read the
posts to conclude the obvious, it's not just me or anyone else ... whether
the problem lies in XP or Vista or both, Microsoft should have realized the
problem and solved it before release, it's a simple thing really!!! They can
fix both programs with their incessant updates whenever they want, they could
have solved it without all this hullaballoo!!
Let's be logical ... I could plug in a new XP computer to another and
voila!, there it is, we're set to go ... now I do that and I can't even get
it to work after hours of frustration, endless online chats and rooms, phone
support from MS and HP, both of whom acknowledge that "there is a known issue
...." ... DUH!! FIX IT!!!
"DP" wrote:
>
> "Dave B" <Dave B@discussions.microsoft.com> wrote in message
> news:351A100D-9C42-4AA8-85A5-BBF574F1EE15@microsoft.com...
>
> > I have searched high and low, talked to people who [should] know, and have
> > yet to hear someone explain how it is that MicroSoft, in all of its glory,
> > could launch such a major marketing campaign to get us to all sign on to
> > the
> > new OS ... they never thought to think that maybe, just maybe ... someone
> > somewhere just might want to have an XP computer exist in peace and
> > harmony
> > with a Vista computer?????
>
>
> I'm guessing -- purely a guess -- that this is not a Vista problem. My Vista
> computer connects to a network that has an XP computer on it.
> You're right to be pissed that it doesn't work. So far all your venom is
> aimed at MS. But what if the problem lies elsewhere?
>
>