Vista & Acer

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

On March 1, 2007, I purchased an Acer Aspire E380 running Windows Vista Home
Premium (32 -bit). I set it up, ran the Windows Updates, and promptly lost
the DVD-RW. I also had an issue with the sound card, it put no sound out
through any place that you pluged the speakers into on the back of the CPU,
but the earphone jack worked. I exchanged that CPU at the place of purchase.

I had the place of purchase make recovery discs for the new CPU prior to
bringing it home. After seting up the system again, I ran Windows Update and,
again, lost the DVD-RW. I purchased a SONY DRU-830A DVD-RW and installed it
in hopes that it would work but to no avail.

I do not recall how the DVD-RW in the first CPU was identified in the Device
Manager, only that it was not the same as the LG GSA-H21N or the SONY
DRU-830A that I have now. After running Windows Update and installing updates
KB915597,KB931573, KB929427, KB928089, KB890830, KB927978, KB929735,
KB930857, KB905866, KB929685, NVIDIA Corp. driver update for NVIDIA MCP61
Serial ATA Controller, and NVIDIA driver update for NVIDIA GeForce 6100
nForce 430 (Microsoft Corp. - WDDM), the properties of all of the DVD-RWs
involved, in the Device Manager, reflect a Device Status of "Window cannot
load the device driver for this hardware. The driver may be corrupted or
missing. (code 39)". Restoring the system to the very first Restor Point did
not solve the problem.

After discussing this issue with ACER , their solution was for me to send
the CPU back to them so that they could re-install Vista. However, after
dealing with two CPUs that developed the same issue in the same manner,
re-installing Vista to a pristene condition would appear to be taking another
trip down the very same path which, to me, is foolhardy.

In researching this issue, I have found that there have been issues of this
type with other Windows operating systems and solutions have been found. I
have not found a solution for Vista.

While attempting to contact Microsoft via e-mail to reduce this issue, their
website tells me that it cannot find the Product ID for Vista installed on my
PC. So I went through the Activation Process with the Product Key off the
side of the CPU but that didn't change anything. After typing in the Product
ID as read from the Windows Activation portion of System Information,
Microsoft again told me that this number is not valid or not in the proper
format.

I have never had such a quagmire of problems with any of the five PCs that I
have owned but then none of them were Acers. This one may well be my first
and last.

Please help if you can...lol, but right now I feel like throwing this ACER
into a VISTA, something like the Grand Canyon or the ocean.......lol.
 
This is not an uncommon problem.. follow the instructions on this web page
to get your optical drive recognized again..

http://support.microsoft.com/kb/320553



Flyin_Lion_1066 said:
On March 1, 2007, I purchased an Acer Aspire E380 running Windows Vista
Home
Premium (32 -bit). I set it up, ran the Windows Updates, and promptly lost
the DVD-RW. I also had an issue with the sound card, it put no sound out
through any place that you pluged the speakers into on the back of the
CPU,
but the earphone jack worked. I exchanged that CPU at the place of
purchase.

I had the place of purchase make recovery discs for the new CPU prior to
bringing it home. After seting up the system again, I ran Windows Update
and,
again, lost the DVD-RW. I purchased a SONY DRU-830A DVD-RW and installed
it
in hopes that it would work but to no avail.

I do not recall how the DVD-RW in the first CPU was identified in the
Device
Manager, only that it was not the same as the LG GSA-H21N or the SONY
DRU-830A that I have now. After running Windows Update and installing
updates
KB915597,KB931573, KB929427, KB928089, KB890830, KB927978, KB929735,
KB930857, KB905866, KB929685, NVIDIA Corp. driver update for NVIDIA MCP61
Serial ATA Controller, and NVIDIA driver update for NVIDIA GeForce 6100
nForce 430 (Microsoft Corp. - WDDM), the properties of all of the DVD-RWs
involved, in the Device Manager, reflect a Device Status of "Window cannot
load the device driver for this hardware. The driver may be corrupted or
missing. (code 39)". Restoring the system to the very first Restor Point
did
not solve the problem.

After discussing this issue with ACER , their solution was for me to send
the CPU back to them so that they could re-install Vista. However, after
dealing with two CPUs that developed the same issue in the same manner,
re-installing Vista to a pristene condition would appear to be taking
another
trip down the very same path which, to me, is foolhardy.

In researching this issue, I have found that there have been issues of
this
type with other Windows operating systems and solutions have been found. I
have not found a solution for Vista.

While attempting to contact Microsoft via e-mail to reduce this issue,
their
website tells me that it cannot find the Product ID for Vista installed on
my
PC. So I went through the Activation Process with the Product Key off the
side of the CPU but that didn't change anything. After typing in the
Product
ID as read from the Windows Activation portion of System Information,
Microsoft again told me that this number is not valid or not in the proper
format.

I have never had such a quagmire of problems with any of the five PCs that
I
have owned but then none of them were Acers. This one may well be my first
and last.

Please help if you can...lol, but right now I feel like throwing this ACER
into a VISTA, something like the Grand Canyon or the ocean.......lol.

--


Mike Hall
MS MVP Windows Shell/User
http://msmvps.com/blogs/mikehall/
 
Thank you for the info, it got me up and running so well that I got to
playing with my music and other files that I forgot to thank you.

I was a bit afraid to modify the Registry on any info that didn't say Vista
without the knowledge of someone a bit more computer savvy than I am. I ran
into a similar problem a few years ago and followed instructions that I found
in the MS database that was supposed to correct the problem. I ended up
re-installing Windows, then doing the same correction again. In the end, I
found that the Registry in the two Operating Systems were very similar but
not exactly the same and the correction that worked in the older one caused
the newer one to crash and burn.

Again, many thanks.
 
Back
Top