Ok, here's the results...
After I got home from work yesterday, I went and booted up the laptop. =
As soon as I could get a prompt, I did a cardctl eject, which resulted i=
the beeps; I then did a cardctl status, just to make sure that the card =
was actually off, which it was.
I then worked the laptop normally for about an hour and a half, and then=
pulled the card and checked. It was only a bit warm, but not hot by any=
means. Then, I re-inserted the card, and did a cardctl status, to make =
sure that it was now "on". It was, at 5.0 Volts, like before. Within 10=
minutes, the card was almost 3 times hotter than it was. I could feel=20
the heat through the palmrest in the case, even. I pulled the card, and=
voila, she was red hot.
I'm not sure now what to make of all this, but this is what happened...
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 8/29/00, 1:16:45 PM, David Hinds <firstname.lastname@example.org> wrote regarding=
Also try powering down the card:
> Another thing to try, is to work with the card in, but powered down
> (to do this, just do a "cardctl eject"). If the card still heats up,
> then it can't be due to the PCMCIA drivers.
> > if apm, or card services, or a combination of
> > both, is causing my mb/processor to get overly hot, then what sort o=
> > damage am I liable to incur?
> I have no idea.
> -- Dave