Windows Vista Beta | WinVistaBeta.com - Message | Problems after installing Vista Service Pack??

October 11, 2008  
Subject: Problems after installing Vista Service Pack??
Group: microsoft.public.windows.vista.installation_setup
Date: 6/30/2008 2:10:36 PM
From: Bill Sands [Email Address Protection]


I really don't know if the problem is with Verizon, Vista, MS, or
something else, but hopefully someone has seen it:

Friday, everything was fine. Monday afternoon, big problem. The only
major difference was the Vista Service Pack 1 I ran this morning, so
maybe that's it.

I run the service pack on my Toshiba Satellite laptop (takes an hour or
so). The next time I try to use the Verizon Versalink Gateway, it does
connect my laptop to my Dell desktop (running XP), and I click on
"access shared files". I open the C: directory on my desktop, and in a
few seconds the status bar reads "179 items (Disk free space: 91.7 GB)."
The problem is that a file showed up about every 15-30 seconds - for
179 files, it took 30 minutes until all files were visible in the panel
on the right.

It "sees" that there are 179 files in the directory immediately, but the
the dark gray bar CREEPS across the top of the screen, taking forever.
If I want a file that starts with "w", I'd be waiting a half an hour for
it. I'd be faster driving somewhere and getting two 5.25" floppy drives
and installing one on each computer.

Thanks in advance for any advice -

BS

Problems after installing Vista Service Pack??

Back
Subject: Re: Problems after installing Vista Service Pack??
Group: microsoft.public.windows.vista.installation_setup
Date: 6/30/2008 3:32:09 PM
From: "Colin Barnhorst" [Email Address Protection]

Have you reinstalled the Verizon drivers? A few drivers have to be
reinstalled after upgrading to SP1.

Bill, did you crosspost? See: http://www.blakjak.demon.co.uk/mul_crss.htm
Posting separately to several newsgroups is frowned on.

"Bill Sands" <saucesman@verizon.net> wrote in message
news:g4bi4q$vfc$3@aioe.org...
>
> I really don't know if the problem is with Verizon, Vista, MS, or
> something else, but hopefully someone has seen it:
>
> Friday, everything was fine. Monday afternoon, big problem. The only
> major difference was the Vista Service Pack 1 I ran this morning, so maybe
> that's it.
>
> I run the service pack on my Toshiba Satellite laptop (takes an hour or
> so). The next time I try to use the Verizon Versalink Gateway, it does
> connect my laptop to my Dell desktop (running XP), and I click on "access
> shared files". I open the C: directory on my desktop, and in a few
> seconds the status bar reads "179 items (Disk free space: 91.7 GB)." The
> problem is that a file showed up about every 15-30 seconds - for 179
> files, it took 30 minutes until all files were visible in the panel on the
> right.
>
> It "sees" that there are 179 files in the directory immediately, but the
> the dark gray bar CREEPS across the top of the screen, taking forever. If
> I want a file that starts with "w", I'd be waiting a half an hour for it.
> I'd be faster driving somewhere and getting two 5.25" floppy drives and
> installing one on each computer.
>
> Thanks in advance for any advice -
>
> BS
>
> Problems after installing Vista Service Pack??


Back
Subject: Re: Problems after installing Vista Service Pack??
Group: microsoft.public.windows.vista.installation_setup
Date: 6/30/2008 4:19:42 PM
From: Bill Sands [Email Address Protection]


Colin Barnhorst wrote:
> Have you reinstalled the Verizon drivers? A few drivers have to be
> reinstalled after upgrading to SP1.

So why did TWO Verizon representatives not know this?? (sigh). Would it
be too much trouble to ask you what I need to do, where I can obtain the
drivers? I signed up with Verizon quite a bit ago and I'm not sure I
know where the software is (I'd call Verizon, but they might not know, eh?)

> Bill, did you crosspost? See: http://www.blakjak.demon.co.uk/mul_crss.htm
> Posting separately to several newsgroups is frowned on.

You of course meant "Did you multipost", and indeed I did, and I wasn't
aware of this issue - now I do, and I apologize (and I have crossposted
in the past plenty of times). It's just that I posted to a group, then
thought "Wait, maybe this group would help (click). Oh, and maybe this
group could provide assistance" (click).

So my impatience caused this inconvenience, and I again apologize and
won't do it again, here or anywhere else.

BS

Back
Subject: Re: Problems after installing Vista Service Pack??
Group: microsoft.public.windows.vista.installation_setup
Date: 6/30/2008 10:28:59 PM
From: "Colin Barnhorst" [Email Address Protection]

No problem with that but do it in such a way that a reply in one ng is
reflected in the other.

Try going into device manager and finding the device. See if there is a
yellow bang on it and report back.

I don't know the Verizon stuff but the driver should be on your system
already, just not reinstalled.

You need to find out if the device should be connected to the system before
or after the software is installed.

You can right click on the device, select uninstall, then reboot. See if
Windows will redetect the device and find the driver on your system.

I am describing what works with plug-n-play devices, but some, like many
printers, require a different procedure. Verizon should be able to help you
with that.

"Bill Sands" <saucesman@verizon.net> wrote in message
news:g4bpmt$rpd$1@aioe.org...
>
> Colin Barnhorst wrote:
>> Have you reinstalled the Verizon drivers? A few drivers have to be
>> reinstalled after upgrading to SP1.
>
> So why did TWO Verizon representatives not know this?? (sigh). Would it
> be too much trouble to ask you what I need to do, where I can obtain the
> drivers? I signed up with Verizon quite a bit ago and I'm not sure I know
> where the software is (I'd call Verizon, but they might not know, eh?)
>
>> Bill, did you crosspost? See:
>> http://www.blakjak.demon.co.uk/mul_crss.htm
>> Posting separately to several newsgroups is frowned on.
>
> You of course meant "Did you multipost", and indeed I did, and I wasn't
> aware of this issue - now I do, and I apologize (and I have crossposted in
> the past plenty of times). It's just that I posted to a group, then
> thought "Wait, maybe this group would help (click). Oh, and maybe this
> group could provide assistance" (click).
>
> So my impatience caused this inconvenience, and I again apologize and
> won't do it again, here or anywhere else.
>
> BS


Back