I'm starting a new thread because the old ones have been bogged down by
people answering questions I didn't ask, not the ones I did.

As I mentioned, I found a zip with a setup that's supposed to install the
amdk8.sys. The install didn't work, but hung instead of completing.

I then found a download of what was supposed to be the actual file. I put it
in my c:\windows\system32\drivers folder. It improved things, but didn't
quite work.

I'm not getting the prompt for installing it, but the system still regularly
reboots a few times and then hangs. It starts recognizing the new hardware,
mainly the new mb items, but the installs aren't always working. I tried
using the AMD S-Series CD to install the chipset drivers, but the system
hasn't let me complete that yet either.

Does anyone have any experience with the same AMD problem who has some
direct suggestions based on their experience? If so, I'd love to hear them.

thanx,
David

David Teich wrote:
> I'm starting a new thread because the old ones have been bogged
> down by people answering questions I didn't ask, not the ones I did.
>
> As I mentioned, I found a zip with a setup that's supposed to
> install the amdk8.sys. The install didn't work, but hung instead of
> completing.
>
> I then found a download of what was supposed to be the actual file.
> I put it in my c:\windows\system32\drivers folder. It improved
> things, but didn't quite work.
>
> I'm not getting the prompt for installing it, but the system still
> regularly reboots a few times and then hangs. It starts recognizing
> the new hardware, mainly the new mb items, but the installs aren't
> always working. I tried using the AMD S-Series CD to install the
> chipset drivers, but the system hasn't let me complete that yet
> either.
>
> Does anyone have any experience with the same AMD problem who has
> some direct suggestions based on their experience? If so, I'd love
> to hear them.

"As I mentioned" <-- Where? A link to what has been discussed - especially
if you are going to bring it up - would be useful. ;-)

Essentially - you seem to be starting a new conversation - but like you were
halfway through it and the rest of the people weren't involved at all in the
prior conversation. Sure - some of those previously involved *may* happen
by - but I wouldn't just rely on that.

What is your specific issue and what specific OS do you have?

At this point there are two unique things about your posting. You and
amdk8.sys.

Googling for the latter:
http://www.google.com/search?q=amdk8.sys

Adding in you:
http://www.google.com/search?q=amdk8.sys+David+Teich

If I had to make a best guess (I do) - this would be the original
conversation you were having?
http://groups.google.com/group/micro...fe6d71e41dbe56

Looking just cursory over that post - I would like to clarify that Service
Pack 3 did not mess up AMD based computers - but the OEMs (Original
Equipment Manufacturers - like HP in particular) did mess up originally when
they created a base-install image to apply to all of their machines (easier
for them to roll out hundreds/thousands a day) on an Intel system and then
applied that base-install image on AMD processor based machines. When SP3
updated the install - it did not see evidence the machine was AMD-Based and
thus - things went weird. On any AMD based machine where the installation
was done properly/on an AMD-based system originally - this problem did not
occur. SP3 was not at fault - but did expose a problem that was hidden from
the user - incorrect original installation.

You also seemed to avoid/ignor questions in the above conversation. Maybe
you did not know how to answer them?

What is your system? Be specific. HP, Dell, IBM, etc? Model number?
Motherboard make/model would be great (download/install Belarc Advisor - run
it and it should tell you the motherboard/mainboard information.)

What operating system - specifically - are you running?
Start button --> RUN (no "RUN"? Press the "Windows Key" + R
on your keyboard) --> type in:
winver
--> Click OK.

The picture at the top of the window that opens will give you the general
(Operating System name) while the line starting with the word "version" will
give you the rest of the story.

** Post both in response to this message verbatim. **

You've given some generalities:

- that you found (where?!) the file you think you need and where you copied
it but it 'didn't quite work' (in what way - how did you know?)
- that you used the AMD S-Series CD (the what? from who, where?) to
install the chipset drivers, but the system did not let you complete that
(what do you mean? what messages do you get, what is stopping it? etc...)

You have to give information to get accurate assistance.

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

As with too many people on these forums, you seem too interested in posting
volumes in attempts to absolve MS from any and all problems and NONE in
answering the fairly obvious questions asked. I'll do it again and attempt to
simplify it even further for you. Attempt to just address these questions and
NOTHING ELSE:

1) Do you know where a good copy of the amdk8.sys file is?
2) Are there any particular instructions to installing it other than just
putting it in the c:\windows\system32\driver directory?
3) Are there any other files associated with it that I should copy at the
same time?

Notice, the answer to none of these requires any of what you've typed or the
information for which you've asked. For instance, we're talking about SP3, so
which OS do you think I'm running? Concentrate, please, just on answering
those questions.

"Shenan Stanley" wrote:

> David Teich wrote:
> > I'm starting a new thread because the old ones have been bogged
> > down by people answering questions I didn't ask, not the ones I did.
> >
> > As I mentioned, I found a zip with a setup that's supposed to
> > install the amdk8.sys. The install didn't work, but hung instead of
> > completing.
> >
> > I then found a download of what was supposed to be the actual file.
> > I put it in my c:\windows\system32\drivers folder. It improved
> > things, but didn't quite work.
> >
> > I'm not getting the prompt for installing it, but the system still
> > regularly reboots a few times and then hangs. It starts recognizing
> > the new hardware, mainly the new mb items, but the installs aren't
> > always working. I tried using the AMD S-Series CD to install the
> > chipset drivers, but the system hasn't let me complete that yet
> > either.
> >
> > Does anyone have any experience with the same AMD problem who has
> > some direct suggestions based on their experience? If so, I'd love
> > to hear them.
>
> "As I mentioned" <-- Where? A link to what has been discussed - especially
> if you are going to bring it up - would be useful. ;-)
>
> Essentially - you seem to be starting a new conversation - but like you were
> halfway through it and the rest of the people weren't involved at all in the
> prior conversation. Sure - some of those previously involved *may* happen
> by - but I wouldn't just rely on that.
>
> What is your specific issue and what specific OS do you have?
>
> At this point there are two unique things about your posting. You and
> amdk8.sys.
>
> Googling for the latter:
> http://www.google.com/search?q=amdk8.sys
>
> Adding in you:
> http://www.google.com/search?q=amdk8.sys+David+Teich
>
> If I had to make a best guess (I do) - this would be the original
> conversation you were having?
> http://groups.google.com/group/micro...fe6d71e41dbe56
>
> Looking just cursory over that post - I would like to clarify that Service
> Pack 3 did not mess up AMD based computers - but the OEMs (Original
> Equipment Manufacturers - like HP in particular) did mess up originally when
> they created a base-install image to apply to all of their machines (easier
> for them to roll out hundreds/thousands a day) on an Intel system and then
> applied that base-install image on AMD processor based machines. When SP3
> updated the install - it did not see evidence the machine was AMD-Based and
> thus - things went weird. On any AMD based machine where the installation
> was done properly/on an AMD-based system originally - this problem did not
> occur. SP3 was not at fault - but did expose a problem that was hidden from
> the user - incorrect original installation.
>
> You also seemed to avoid/ignor questions in the above conversation. Maybe
> you did not know how to answer them?
>
> What is your system? Be specific. HP, Dell, IBM, etc? Model number?
> Motherboard make/model would be great (download/install Belarc Advisor - run
> it and it should tell you the motherboard/mainboard information.)
>
> What operating system - specifically - are you running?
> Start button --> RUN (no "RUN"? Press the "Windows Key" + R
> on your keyboard) --> type in:
> winver
> --> Click OK.
>
> The picture at the top of the window that opens will give you the general
> (Operating System name) while the line starting with the word "version" will
> give you the rest of the story.
>
> ** Post both in response to this message verbatim. **
>
> You've given some generalities:
>
> - that you found (where?!) the file you think you need and where you copied
> it but it 'didn't quite work' (in what way - how did you know?)
> - that you used the AMD S-Series CD (the what? from who, where?) to
> install the chipset drivers, but the system did not let you complete that
> (what do you mean? what messages do you get, what is stopping it? etc...)
>
> You have to give information to get accurate assistance.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>

<snip>

David Teich wrote:
> As with too many people on these forums, you seem too interested in
> posting volumes in attempts to absolve MS from any and all problems
> and NONE in answering the fairly obvious questions asked. I'll do
> it again and attempt to simplify it even further for you. Attempt
> to just address these questions and NOTHING ELSE:
>
> 1) Do you know where a good copy of the amdk8.sys file is?
> 2) Are there any particular instructions to installing it other
> than just putting it in the c:\windows\system32\driver directory?
> 3) Are there any other files associated with it that I should copy
> at the same time?
>
> Notice, the answer to none of these requires any of what you've
> typed or the information for which you've asked. For instance,
> we're talking about SP3, so which OS do you think I'm running?
> Concentrate, please, just on answering those questions.

As with too many people on these forums - you seem too interested in making
people guess at what *your* problem is and the details surrounding it and
then giving attitude when someone asks you basic queries to help *you*
resolve *your* issue.

I could assume you have Windows XP w/SP3 - but Windows XP what? Home
Edition? Professional Edition? Starter Edition? It may make a difference
in how one would tell you to go about things.

Recall - you came here for help, you *asked* for it... If you do not want to
oblige those who might help by answering a few questions, giving a few
details - good luck to you.

Microsoft may be at fault, may not - don't care. I've said it before, I
will likely have to say it again - if Microsoft disappeared tomorrow - it
makes no difference to me. Absolve them? Please... Perhaps you are just
too eager to blame anyone else.

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

David Teich wrote:
> I'm starting a new thread because the old ones have been bogged
> down by people answering questions I didn't ask, not the ones I did.
>
> As I mentioned, I found a zip with a setup that's supposed to
> install the amdk8.sys. The install didn't work, but hung instead of
> completing.
>
> I then found a download of what was supposed to be the actual file.
> I put it in my c:\windows\system32\drivers folder. It improved
> things, but didn't quite work.
>
> I'm not getting the prompt for installing it, but the system still
> regularly reboots a few times and then hangs. It starts recognizing
> the new hardware, mainly the new mb items, but the installs aren't
> always working. I tried using the AMD S-Series CD to install the
> chipset drivers, but the system hasn't let me complete that yet
> either.
>
> Does anyone have any experience with the same AMD problem who has
> some direct suggestions based on their experience? If so, I'd love
> to hear them.

Shenan Stanley wrote:
> "As I mentioned" <-- Where? A link to what has been discussed -
> especially if you are going to bring it up - would be useful. ;-)
>
> Essentially - you seem to be starting a new conversation - but like
> you were halfway through it and the rest of the people weren't
> involved at all in the prior conversation. Sure - some of those
> previously involved *may* happen by - but I wouldn't just rely on
> that.
> What is your specific issue and what specific OS do you have?
>
> At this point there are two unique things about your posting. You
> and amdk8.sys.
>
> Googling for the latter:
> http://www.google.com/search?q=amdk8.sys
>
> Adding in you:
> http://www.google.com/search?q=amdk8.sys+David+Teich
>
> If I had to make a best guess (I do) - this would be the original
> conversation you were having?
> http://groups.google.com/group/micro...fe6d71e41dbe56
>
> Looking just cursory over that post - I would like to clarify that
> Service Pack 3 did not mess up AMD based computers - but the OEMs
> (Original Equipment Manufacturers - like HP in particular) did mess
> up originally when they created a base-install image to apply to
> all of their machines (easier for them to roll out
> hundreds/thousands a day) on an Intel system and then applied that
> base-install image on AMD processor based machines. When SP3
> updated the install - it did not see evidence the machine was
> AMD-Based and thus - things went weird. On any AMD based machine
> where the installation was done properly/on an AMD-based system
> originally - this problem did not occur. SP3 was not at fault -
> but did expose a problem that was hidden from the user - incorrect
> original installation.
> You also seemed to avoid/ignore questions in the above conversation.
> Maybe you did not know how to answer them?
>
> What is your system? Be specific. HP, Dell, IBM, etc? Model
> number? Motherboard make/model would be great (download/install
> Belarc Advisor - run it and it should tell you the
> motherboard/mainboard information.)
> What operating system - specifically - are you running?
> Start button --> RUN (no "RUN"? Press the "Windows Key" + R
> on your keyboard) --> type in:
> winver
> --> Click OK.
>
> The picture at the top of the window that opens will give you the
> general (Operating System name) while the line starting with the
> word "version" will give you the rest of the story.
>
> ** Post both in response to this message verbatim. **
>
> You've given some generalities:
>
> - that you found (where?!) the file you think you need and where
> you copied it but it 'didn't quite work' (in what way - how did you
> know?) - that you used the AMD S-Series CD (the what? from who,
> where?) to install the chipset drivers, but the system did not let
> you complete that (what do you mean? what messages do you get,
> what is stopping it? etc...)
> You have to give information to get accurate assistance.

David Teich wrote:
> As with too many people on these forums, you seem too interested in
> posting volumes in attempts to absolve MS from any and all problems
> and NONE in answering the fairly obvious questions asked. I'll do
> it again and attempt to simplify it even further for you. Attempt
> to just address these questions and NOTHING ELSE:
>
> 1) Do you know where a good copy of the amdk8.sys file is?
> 2) Are there any particular instructions to installing it other
> than just putting it in the c:\windows\system32\driver directory?
> 3) Are there any other files associated with it that I should copy
> at the same time?
>
> Notice, the answer to none of these requires any of what you've
> typed or the information for which you've asked. For instance,
> we're talking about SP3, so which OS do you think I'm running?
> Concentrate, please, just on answering those questions.

Shenan Stanley wrote:
> As with too many people on these forums - you seem too interested
> in making people guess at what *your* problem is and the details
> surrounding it and then giving attitude when someone asks you basic
> queries to help *you* resolve *your* issue.
>
> I could assume you have Windows XP w/SP3 - but Windows XP what? Home
> Edition? Professional Edition? Starter Edition? It may make
> a difference in how one would tell you to go about things.
>
> Recall - you came here for help, you *asked* for it... If you do
> not want to oblige those who might help by answering a few
> questions, giving a few details - good luck to you.
>
> Microsoft may be at fault, may not - don't care. I've said it
> before, I will likely have to say it again - if Microsoft
> disappeared tomorrow - it makes no difference to me. Absolve them?
> Please... Perhaps you are just too eager to blame anyone else.


You have, assuming from your other post linked to above by myself -
specifically "I'm trying to get an old C drive running that has XP SP3" -
hooked a hard disk drive originally installed on an Intel based system into
a new system based on AMD or something similar. There is also the
possibility you applied the image of this "old C drive" to a new system just
expecting it to work. There is also the possibility it came from a factory
like this (HP had a similar issue when SP3 came out.) In any case - the
original system was Intel, the new system is AMD.

You might try this:
(Only if you are now on an non-intel-based computer.)
http://support.microsoft.com/kb/953356/

In the end - even after performing the steps (all of them) in that
knowledgebase article - you may need to perform a simple 'repair
installation' of Windows XP (it is non-destructive to your files.)

You'll need a Windows XP CD of the same service pack level and 'flavor'
(Windows XP Home, Professional, TabletPC, Media Center, etc) in order to do
this - but it is a fairly painless process. One (if not both) of the
following web pages may help you complete the process...

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

The above is what you need. That single file *is not* your only issue.

Again - good luck to you.

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

Yes, I've asked for help, and you've constantly refused to directly answer
the issues for which I've asked help. That seems to be typical. I always post
on the forums, hoping I'll get help and expecting that I won't. Why? Because
do many MS-MVP's seem to think that getting the t-shirts and other MS toys is
all you're in it for, not to actually help the poster.

I gave you specific issues I needed addressed, and in multiple threads,
continual posting by you and others have failed to address the specific issue.

Meanwhile, I kept trying other sources and tweaking my system. Yet again,
I've solved the problem w/o help from these forums. I've installed that file,
done a repair after it and am now busy trying to recover application software
-- all w/o a useful response from you.

Thanx for nothing but wasting my time.

David

"Shenan Stanley" wrote:

> <snip>
>
> David Teich wrote:
> > As with too many people on these forums, you seem too interested in
> > posting volumes in attempts to absolve MS from any and all problems
> > and NONE in answering the fairly obvious questions asked. I'll do
> > it again and attempt to simplify it even further for you. Attempt
> > to just address these questions and NOTHING ELSE:
> >
> > 1) Do you know where a good copy of the amdk8.sys file is?
> > 2) Are there any particular instructions to installing it other
> > than just putting it in the c:\windows\system32\driver directory?
> > 3) Are there any other files associated with it that I should copy
> > at the same time?
> >
> > Notice, the answer to none of these requires any of what you've
> > typed or the information for which you've asked. For instance,
> > we're talking about SP3, so which OS do you think I'm running?
> > Concentrate, please, just on answering those questions.
>
> As with too many people on these forums - you seem too interested in making
> people guess at what *your* problem is and the details surrounding it and
> then giving attitude when someone asks you basic queries to help *you*
> resolve *your* issue.
>
> I could assume you have Windows XP w/SP3 - but Windows XP what? Home
> Edition? Professional Edition? Starter Edition? It may make a difference
> in how one would tell you to go about things.
>
> Recall - you came here for help, you *asked* for it... If you do not want to
> oblige those who might help by answering a few questions, giving a few
> details - good luck to you.
>
> Microsoft may be at fault, may not - don't care. I've said it before, I
> will likely have to say it again - if Microsoft disappeared tomorrow - it
> makes no difference to me. Absolve them? Please... Perhaps you are just
> too eager to blame anyone else.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>

David Teich wrote:
> I'm starting a new thread because the old ones have been bogged
> down by people answering questions I didn't ask, not the ones I did.
>
> As I mentioned, I found a zip with a setup that's supposed to
> install the amdk8.sys. The install didn't work, but hung instead of
> completing.
>
> I then found a download of what was supposed to be the actual file.
> I put it in my c:\windows\system32\drivers folder. It improved
> things, but didn't quite work.
>
> I'm not getting the prompt for installing it, but the system still
> regularly reboots a few times and then hangs. It starts recognizing
> the new hardware, mainly the new mb items, but the installs aren't
> always working. I tried using the AMD S-Series CD to install the
> chipset drivers, but the system hasn't let me complete that yet
> either.
>
> Does anyone have any experience with the same AMD problem who has
> some direct suggestions based on their experience? If so, I'd love
> to hear them.

Shenan Stanley wrote:
> "As I mentioned" <-- Where? A link to what has been discussed -
> especially if you are going to bring it up - would be useful. ;-)
>
> Essentially - you seem to be starting a new conversation - but like
> you were halfway through it and the rest of the people weren't
> involved at all in the prior conversation. Sure - some of those
> previously involved *may* happen by - but I wouldn't just rely on
> that.
> What is your specific issue and what specific OS do you have?
>
> At this point there are two unique things about your posting. You
> and amdk8.sys.
>
> Googling for the latter:
> http://www.google.com/search?q=amdk8.sys
>
> Adding in you:
> http://www.google.com/search?q=amdk8.sys+David+Teich
>
> If I had to make a best guess (I do) - this would be the original
> conversation you were having?
> http://groups.google.com/group/micro...fe6d71e41dbe56
>
> Looking just cursory over that post - I would like to clarify that
> Service Pack 3 did not mess up AMD based computers - but the OEMs
> (Original Equipment Manufacturers - like HP in particular) did mess
> up originally when they created a base-install image to apply to
> all of their machines (easier for them to roll out
> hundreds/thousands a day) on an Intel system and then applied that
> base-install image on AMD processor based machines. When SP3
> updated the install - it did not see evidence the machine was
> AMD-Based and thus - things went weird. On any AMD based machine
> where the installation was done properly/on an AMD-based system
> originally - this problem did not occur. SP3 was not at fault -
> but did expose a problem that was hidden from the user - incorrect
> original installation.
> You also seemed to avoid/ignore questions in the above conversation.
> Maybe you did not know how to answer them?
>
> What is your system? Be specific. HP, Dell, IBM, etc? Model
> number? Motherboard make/model would be great (download/install
> Belarc Advisor - run it and it should tell you the
> motherboard/mainboard information.)
> What operating system - specifically - are you running?
> Start button --> RUN (no "RUN"? Press the "Windows Key" + R
> on your keyboard) --> type in:
> winver
> --> Click OK.
>
> The picture at the top of the window that opens will give you the
> general (Operating System name) while the line starting with the
> word "version" will give you the rest of the story.
>
> ** Post both in response to this message verbatim. **
>
> You've given some generalities:
>
> - that you found (where?!) the file you think you need and where
> you copied it but it 'didn't quite work' (in what way - how did you
> know?) - that you used the AMD S-Series CD (the what? from who,
> where?) to install the chipset drivers, but the system did not let
> you complete that (what do you mean? what messages do you get,
> what is stopping it? etc...)
> You have to give information to get accurate assistance.

David Teich wrote:
> As with too many people on these forums, you seem too interested in
> posting volumes in attempts to absolve MS from any and all problems
> and NONE in answering the fairly obvious questions asked. I'll do
> it again and attempt to simplify it even further for you. Attempt
> to just address these questions and NOTHING ELSE:
>
> 1) Do you know where a good copy of the amdk8.sys file is?
> 2) Are there any particular instructions to installing it other
> than just putting it in the c:\windows\system32\driver directory?
> 3) Are there any other files associated with it that I should copy
> at the same time?
>
> Notice, the answer to none of these requires any of what you've
> typed or the information for which you've asked. For instance,
> we're talking about SP3, so which OS do you think I'm running?
> Concentrate, please, just on answering those questions.

Shenan Stanley wrote:
> As with too many people on these forums - you seem too interested
> in making people guess at what *your* problem is and the details
> surrounding it and then giving attitude when someone asks you basic
> queries to help *you* resolve *your* issue.
>
> I could assume you have Windows XP w/SP3 - but Windows XP what? Home
> Edition? Professional Edition? Starter Edition? It may make
> a difference in how one would tell you to go about things.
>
> Recall - you came here for help, you *asked* for it... If you do
> not want to oblige those who might help by answering a few
> questions, giving a few details - good luck to you.
>
> Microsoft may be at fault, may not - don't care. I've said it
> before, I will likely have to say it again - if Microsoft
> disappeared tomorrow - it makes no difference to me. Absolve them?
> Please... Perhaps you are just too eager to blame anyone else.

Shenan Stanley wrote:
> You have, assuming from your other post linked to above by myself -
> specifically "I'm trying to get an old C drive running that has XP SP3" -
> hooked a hard disk drive originally installed on an Intel based system
> into
> a new system based on AMD or something similar. There is also the
> possibility you applied the image of this "old C drive" to a new system
> just
> expecting it to work. There is also the possibility it came from a
> factory
> like this (HP had a similar issue when SP3 came out.) In any case - the
> original system was Intel, the new system is AMD.
>
> You might try this:
> (Only if you are now on an non-intel-based computer.)
> http://support.microsoft.com/kb/953356/
>
> In the end - even after performing the steps (all of them) in that
> knowledgebase article - you may need to perform a simple 'repair
> installation' of Windows XP (it is non-destructive to your files.)
>
> You'll need a Windows XP CD of the same service pack level and 'flavor'
> (Windows XP Home, Professional, TabletPC, Media Center, etc) in order to
> do
> this - but it is a fairly painless process. One (if not both) of the
> following web pages may help you complete the process...
>
> 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
>
> The above is what you need. That single file *is not* your only issue.
>
> Again - good luck to you.

David Teich wrote:
> Yes, I've asked for help, and you've constantly refused to directly answer
> the issues for which I've asked help. That seems to be typical. I always
> post
> on the forums, hoping I'll get help and expecting that I won't. Why?
> Because
> do many MS-MVP's seem to think that getting the t-shirts and other MS toys
> is
> all you're in it for, not to actually help the poster.
>
> I gave you specific issues I needed addressed, and in multiple threads,
> continual posting by you and others have failed to address the specific
> issue.
>
> Meanwhile, I kept trying other sources and tweaking my system. Yet again,
> I've solved the problem w/o help from these forums. I've installed that
> file,
> done a repair after it and am now busy trying to recover application
> software
> -- all w/o a useful response from you.
>
> Thanx for nothing but wasting my time.

Glad you followed the advice given and fixed your issue.

Couldn't have been clearer than the answer I gave you.

Essentially - repair installation - even though that was based off
assumptions those in the newsgroups were forced to make due to your
stubborness.

BTW - again - Microsoft can disappear - don't care. I'm someone just like
you, I gave you assistance and you spit in my face. So be it.

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