DAY 2 OF The VIA Nightware Still Tons IF Dead Laptops Where IS The

Imexecptionally Upset there is still no fix, any 'fix' posted so far assumes
you can still boot your laptop in either safe mode or last know good config.

My laptop as many others out there
(A) went to windows update and downloaded the hardware updates
(B) rebooted as normal only to BSOD to the how would you like to boot scrren
(C) Tried imidiatly "last Known Good Configuration" only to see the BSOD and
be back at the same window.
(D) Then tried Safe Mode, after a ton of text wizes by the screen instant BSOD
(E) Booted from a xp disk went into the repair console and tried to look for
the $NTUninstall file cant find one looked into the ViPar.sys file noting
seems to help.Even ran chkdsk knowing it would do noting.
(F) yes were all (F)ked for sure, and we sit here like lemmings worried
about viruses and security leakes..

Where is the fix instructions? im about to reload back to October of last
year...

Not Happy At All
Andrew H. Hochheimer
The Software Artist Limited.

Tallen Atear wrote:
> Imexecptionally Upset there is still no fix, any 'fix' posted so
> far assumes you can still boot your laptop in either safe mode or
> last know good config.
>
> My laptop as many others out there
> (A) went to windows update and downloaded the hardware updates

How many times has it been repeated in these newsgroups (and elsewhere on
the Internet) to NOT get the hardware updates from Microsoft?

They do *not* make the majority (if any) of your hardware - so why would you
trust* them to supply you with the best drivers/software for your hardware?

> (B) rebooted as normal only to BSOD to the how would you like to
> boot scrren (C) Tried imidiatly "last Known Good Configuration"
> only to see the BSOD and be back at the same window.
> (D) Then tried Safe Mode, after a ton of text wizes by the screen
> instant BSOD (E) Booted from a xp disk went into the repair console
> and tried to look for the $NTUninstall file cant find one looked
> into the ViPar.sys file noting seems to help.Even ran chkdsk
> knowing it would do noting. (F) yes were all (F)ked for sure, and
> we sit here like lemmings worried
> about viruses and security leakes..
>
> Where is the fix instructions? im about to reload back to October
> of last year...

Perform a REPAIR INSTALLATION.. Has nothing to do with a Repair Console.

How to Perform a Windows XP Repair Install
http://www.michaelstevenstech.com/XPrepairinstall.htm

How to perform an in-place upgrade (reinstallation) of Windows XP
http://support.microsoft.com/kb/315341

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

It's one thing when the driver is a proper tested driver, it's totally
another when this appears to be a total "stuff up" as my Aussie friends
would say.

Shenan Stanley wrote:
> Tallen Atear wrote:
>> Imexecptionally Upset there is still no fix, any 'fix' posted so
>> far assumes you can still boot your laptop in either safe mode or
>> last know good config.
>>
>> My laptop as many others out there
>> (A) went to windows update and downloaded the hardware updates
>
> How many times has it been repeated in these newsgroups (and elsewhere on
> the Internet) to NOT get the hardware updates from Microsoft?
>
> They do *not* make the majority (if any) of your hardware - so why would you
> trust* them to supply you with the best drivers/software for your hardware?
>
>> (B) rebooted as normal only to BSOD to the how would you like to
>> boot scrren (C) Tried imidiatly "last Known Good Configuration"
>> only to see the BSOD and be back at the same window.
>> (D) Then tried Safe Mode, after a ton of text wizes by the screen
>> instant BSOD (E) Booted from a xp disk went into the repair console
>> and tried to look for the $NTUninstall file cant find one looked
>> into the ViPar.sys file noting seems to help.Even ran chkdsk
>> knowing it would do noting. (F) yes were all (F)ked for sure, and
>> we sit here like lemmings worried
>> about viruses and security leakes..
>>
>> Where is the fix instructions? im about to reload back to October
>> of last year...
>
> Perform a REPAIR INSTALLATION.. Has nothing to do with a Repair Console.
>
> How to Perform a Windows XP Repair Install
> http://www.michaelstevenstech.com/XPrepairinstall.htm
>
> How to perform an in-place upgrade (reinstallation) of Windows XP
> http://support.microsoft.com/kb/315341
>

Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] wrote:
> It's one thing when the driver is a proper tested driver, it's
> totally another when this appears to be a total "stuff up" as my
> Aussie friends would say.

Personally - I stick to the advice I have given for years...
If Microsoft did not make the hardware - why would you trust getting the
software/driver for it from Microsoft?

Any other advice would contradict the advice I would normally give.

You always want to download something from the most trusted source.

In the case of a piece of hardware - the most trusted source for a
software/driver download for said device would be from the actual
manufacturer's (of said device) web site - as they are the creators of said
product and provide the support for said product.

Microsoft - while the 'most trusted source' for drivers and updates for
*their* products is not, to me, the most trusted source for drivers and
updates for, say, ATI's products... NVidia's products... Creative Labs'
products... Intel chipsets... VIA chipsets... and so on.

While I agree that the VIA driver is totally messed up and just being
offered to practically everyone - if people did not get their hardware
drivers from a source where the product wasn't created/supported directly -
then they would not have a problem. =)

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

What if the next time the "stuff up" is not a driver that those of us
experienced patchers say to avoid but some other patch that shouldn't be
offered up?

I would hope that someone is going back and reviewing processes to see
what got "stuffed".

It would also be nice if there was an official post from a Microsoft
source. Additional help and guidance would be nice.

Shenan Stanley wrote:
> Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] wrote:
>> It's one thing when the driver is a proper tested driver, it's
>> totally another when this appears to be a total "stuff up" as my
>> Aussie friends would say.
>
> Personally - I stick to the advice I have given for years...
> If Microsoft did not make the hardware - why would you trust getting the
> software/driver for it from Microsoft?
>
> Any other advice would contradict the advice I would normally give.
>
> You always want to download something from the most trusted source.
>
> In the case of a piece of hardware - the most trusted source for a
> software/driver download for said device would be from the actual
> manufacturer's (of said device) web site - as they are the creators of said
> product and provide the support for said product.
>
> Microsoft - while the 'most trusted source' for drivers and updates for
> *their* products is not, to me, the most trusted source for drivers and
> updates for, say, ATI's products... NVidia's products... Creative Labs'
> products... Intel chipsets... VIA chipsets... and so on.
>
> While I agree that the VIA driver is totally messed up and just being
> offered to practically everyone - if people did not get their hardware
> drivers from a source where the product wasn't created/supported directly -
> then they would not have a problem. =)
>

Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] wrote:
> It's one thing when the driver is a proper tested driver, it's
> totally another when this appears to be a total "stuff up" as my
> Aussie friends would say.

Shenan Stanley wrote:
> Personally - I stick to the advice I have given for years...
> If Microsoft did not make the hardware - why would you trust
> getting the software/driver for it from Microsoft?
>
> Any other advice would contradict the advice I would normally give.
>
> You always want to download something from the most trusted source.
>
> In the case of a piece of hardware - the most trusted source for a
> software/driver download for said device would be from the actual
> manufacturer's (of said device) web site - as they are the
> creators of said product and provide the support for said product.
>
> Microsoft - while the 'most trusted source' for drivers and
> updates for *their* products is not, to me, the most trusted
> source for drivers and updates for, say, ATI's products...
> NVidia's products... Creative Labs' products... Intel chipsets... VIA
> chipsets... and so on.
> While I agree that the VIA driver is totally messed up and just
> being offered to practically everyone - if people did not get
> their hardware drivers from a source where the product wasn't
> created/supported directly - then they would not have a problem. =)

Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] wrote:
> What if the next time the "stuff up" is not a driver that those of
> us experienced patchers say to avoid but some other patch that
> shouldn't be offered up?
>
> I would hope that someone is going back and reviewing processes to
> see what got "stuffed".
>
> It would also be nice if there was an official post from a Microsoft
> source. Additional help and guidance would be nice.

There is no disagreement there.

Someone should have caught this at Microsoft by now.
Someone should have made a public announcement or at the very least - pulled
it from the site.
(From Microsoft.)

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

"Shenan Stanley" wrote:
>
> There is no disagreement there.
>
> Someone should have caught this at Microsoft by now.
> Someone should have made a public announcement or at the very least - pulled
> it from the site.
> (From Microsoft.)
>
> --
> Shenan Stanley
> MS-MVP


Shenan,

It is Microsofts responsibility to ensure all drivers being sponsored on the
update page are working fully and tested fully before sponsoring any drivers
at all.

This is not an issue of where you got the drivers, we all have experiences
that drivers from the website directly have caused the same problem, but in
this case, we expect a little bit more than just a cursory glance. If this
means paying someone OT and cuts those few dollars out of the profit margin
to ensure this, then too bad. Price you pay when you have pretty much
dominated the market.

So, the question still remains, what are VIA and MS doing about preparing a
self boot CD to patch/fix the current problem since repairing does not work?!

> Someone should have caught this at Microsoft by now.
> Someone should have made a public announcement or at the very least - pulled
> it from the site.

As of this morning the hardware updates have been removed, but there is
still no public fix outside of reinstall xp - unexceptable from a 126k update
that could not of changed much.

I download all updates simply becuase (a) i never ran into a problem before
doings so, and (b) I have 100's of clients that will no matter what I tell
them so if there is a problem I at least need to be aware of it and have a
solution.

Andrew

I also had the problem yesterday.
I was able to sucessfully fix and repeat the issue several times.
If last known good fails.....safe mode and goto device manager.
From there "IDE ATA/ATAPI controllers/Primary IDE channel, roll back driver.
You can also go into the Windows directory system32 drivers and look for the
driver that was created on the date you instaled it.....the name was short
and had "pr" in it. Looking at the info of the driver, it will say VIA in it.

"Tallen Atear" wrote:

> > Someone should have caught this at Microsoft by now.
> > Someone should have made a public announcement or at the very least - pulled
> > it from the site.
>
> As of this morning the hardware updates have been removed, but there is
> still no public fix outside of reinstall xp - unexceptable from a 126k update
> that could not of changed much.
>
> I download all updates simply becuase (a) i never ran into a problem before
> doings so, and (b) I have 100's of clients that will no matter what I tell
> them so if there is a problem I at least need to be aware of it and have a
> solution.
>
> Andrew

"miadlor" wrote:

> I also had the problem yesterday.
> I was able to sucessfully fix and repeat the issue several times.
> If last known good fails.....safe mode and goto device manager.
> From there "IDE ATA/ATAPI controllers/Primary IDE channel, roll back driver.(repeat for secondary)
> You can also go into the Windows directory system32 drivers and look for the
> driver that was created on the date you instaled it.....the name was short
> and had "pr" in it. Looking at the info of the driver, it will say VIA in it.
>
> "Tallen Atear" wrote:
>
> > > Someone should have caught this at Microsoft by now.
> > > Someone should have made a public announcement or at the very least - pulled
> > > it from the site.
> >
> > As of this morning the hardware updates have been removed, but there is
> > still no public fix outside of reinstall xp - unexceptable from a 126k update
> > that could not of changed much.
> >
> > I download all updates simply becuase (a) i never ran into a problem before
> > doings so, and (b) I have 100's of clients that will no matter what I tell
> > them so if there is a problem I at least need to be aware of it and have a
> > solution.
> >
> > Andrew