Re: error#06:0000:00002C47 caused an error in KRNL385.exe by Mart
Mart
Mon May 09 18:03:29 CDT 2005
Michelle,
Almost a 'ditto' of Mikes post too <g>
As I've said many times in these Groups, you can learn something new every
day.
Good luck and visit again - whilst we are still here - if you have any other
WinMe related issues. There's still a few of us 'regulars' left who will try
to 'fix' thing for you if we can.
Mart
"miesha" <miesha@discussions.microsoft.com> wrote in message
news:F39F2925-DB32-4BAA-9B1F-FF2178FF38EC@microsoft.com...
> Mike and Mart,
>
> Thank you both for jumping in and staying a bit past bedtime. I really do
> appreciate both of you generously sharing your knowledge to help out a
> grandmother and her granddaughter.
>
> Final update: My grandmother sucessfully updated to the latest Windows
> Update and her computer is back to normal.
>
> I'm also privately pleased that my grandma and I helped add to your "Rainy
> Day" observations. I hope my post will help someone else!
>
> Thank you, thank you!
>
> Michelle
>
> "Mart" wrote:
>
>> > ... I can only assume that you had an early night last night - as did
>> > I,
>> > going to bed almost straight after that post.
>>
>> Not that early - must have been just before you posted <g> Keep promising
>> myself early ones but....
>>
>> None the less, a good observation in spotting the 06 link. Now copied
>> into
>> my 'Rainy Day Stuff' folder
>>
>> Mart
>>
>>
>>
>> "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
>> news:%2374Qpu6UFHA.628@tk2msftngp13.phx.gbl...
>> > Hi Mart,
>> >
>> > I only jumped in when I realised it was an 06 error which until the
>> > 891711
>> > debacle were few and far between so thought it worth a shot. As for my
>> > post being well past your bed time I can only assume that you had an
>> > early
>> > night last night - as did I, going to bed almost straight after that
>> > post.
>> >
>> > Cheers,
>> > --
>> > Mike
>> >
>> >
>> > Mart <mart(NoSpam)@nospam.nospam> wrote:
>> >
>> >> Hi Mike, - Good Call - not having been directly involved with the
>> >> KB891711 issue, I doubt whether I would have come with that solution.
>> >> And thanks for jumping in last night too - well past my bed time <g>
>> >
>>
>>
>>