BigK

"Jordan H." <JordanH@discussions.microsoft.com> wrote in message
news:B5B81EC1-7278-4F8A-B8AB-6A1E0BC617D4@microsoft.com...
> Ok if it's MS's Fault, Why use Vista? The whole point in Beta and RC1
> TESTING is just that, TESTING. I don't know if you remember, but XP
> wasn't
> any great shakes either when it first came out.
>
> Another question I'd really like answers to, Besides trying to throw blame
> around, is why can you see the shared documents folder on an XP home
> machine
> yet can't connect to the printer? makes no sense. Let's try and see what
> we
> can find out, all this back and forth over who's at fault for what isn't
> solving the problem. it's just creating an issue between people when
> there
> really isn't any reason for one.

Sorry, but I've tried everything that has been advised. And none of it has
worked. I'm downloading the latest RC2 now so we'll see if Vista RC2 has
fixed this problem. I don't know why I can see shared folders and printers
but cannot connect to printers. Someone says it is becasue of the way XP
shares printers but there have been no solutions yet that have worked for
anyone I've seen yet.


>
> "BigK" wrote:
>
>>
>> "Jordan H." <JordanH@discussions.microsoft.com> wrote in message
>> news:3947E2A4-A79A-4792-88B9-4AEFE99C3214@microsoft.com...
>> >I haven't actually gotten anything to work either. that's not what i'm
>> > saying. what i'm trying to say is that you gotta remember that MS in
>> > NOT
>> > responsible for writing 3rd PARTY MFGs DRIVERS. Everyone that i've
>> > seen
>> > here
>> > is running one of the big 3 MFGs printer, Cannon, HP, and Lexmark.
>> > Their
>> > the
>> > ones we should be going after.
>>
>> I have an Epson and a Samsung. so if ALL printers are affected then it
>> might not be the printer companies that are having the problem. It seems
>> that the one common denominator is Vista trying to access XP Home. That
>> is
>> MS's fault.
>>
>>
>>