[Dixonary] OT: Computer Woes

[hello]

I have suffered a catastrophic computer failure on the main computer I
use for Dixonary (and almost everything else). I have managed to
cobble together an old email client on a notebook computer I
infrequently use to manage the rest of the deal.

The failure, for the computer geeks, seems to be in the motherboard
itself. The POST runs for about 8 seconds after powerup, then right at
the point the disk drive activity LED turns on, everything shuts down.
After a few seconds, it automatically tries to restart, and repeats
the cycle. Sometimes the shutdown happens after only a second or two,
so it's not totally regular.

All the disk drives are fine. The problem does not seem to be in any
peripheral board or device; I've disconnected them all. Removing he
memory causes the expected beep sequence for that condition, which
further vindicates the CPU, IMHO.

The board is only 6 or 7 years old, and has run fine until now. Never
had this happen before.

--
You received this message because you are subscribed to the Google Groups "Dixonary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+unsubscribe (AT) googlegroups (DOT) com.
For more options, visit https://groups.google.com/groups/opt_out.

[France International/Mike Shefler]

Ouch! If you can somehow move or connect the old hard drives to your
notebook, you can at least recover your files.

On 1/18/2014 12:35 PM, hello wrote:
> I have suffered a catastrophic computer failure on the main computer I
> use for Dixonary (and almost everything else). I have managed to
> cobble together an old email client on a notebook computer I
> infrequently use to manage the rest of the deal.
>
> The failure, for the computer geeks, seems to be in the motherboard
> itself. The POST runs for about 8 seconds after powerup, then right at
> the point the disk drive activity LED turns on, everything shuts down.
> After a few seconds, it automatically tries to restart, and repeats
> the cycle. Sometimes the shutdown happens after only a second or two,
> so it's not totally regular.
>
> All the disk drives are fine. The problem does not seem to be in any
> peripheral board or device; I've disconnected them all. Removing he
> memory causes the expected beep sequence for that condition, which
> further vindicates the CPU, IMHO.
>
> The board is only 6 or 7 years old, and has run fine until now. Never
> had this happen before.
>

--
You received this message because you are subscribed to the Google Groups "Dixonary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+unsubscribe (AT) googlegroups (DOT) com.
For more options, visit https://groups.google.com/groups/opt_out.

[hello]

Saturday, January 18, 2014, 12:43:40 PM, you wrote:

> Ouch! If you can somehow move or connect the old hard drives to your
> notebook, you can at least recover your files.

Oh, I have access to all the files...except the one critical one with
my passwords in it. Everything is multiply backed up, too. But that
one file with all my (generally strong and unrememberable) passwords
was encrypted using the native Windows/NTFS encryption feature.

Turns out I never understood how that works: you MUST export a
certificate onto some external device to be able to decrypt any
encrypted files or folders if they are accessed from a system and
logged-in user other than the one they were encrypted with. I had
never done so, thinking that, should it become necessary, all I would
need was my user ID and password. Wrong, wrong, WRONG! So the only
hope of recovering the file is to boot up the original OS on the
system drive. But I own no other computer with SATA controllers (just
IDE) that I could plug the system drive into, so I have to wait until
I can repair the old one.


> On 1/18/2014 12:35 PM, hello wrote:
>> I have suffered a catastrophic computer failure on the main computer I
>> use for Dixonary (and almost everything else). I have managed to
>> cobble together an old email client on a notebook computer I
>> infrequently use to manage the rest of the deal.
>>
>> The failure, for the computer geeks, seems to be in the motherboard
>> itself. The POST runs for about 8 seconds after powerup, then right at
>> the point the disk drive activity LED turns on, everything shuts down.
>> After a few seconds, it automatically tries to restart, and repeats
>> the cycle. Sometimes the shutdown happens after only a second or two,
>> so it's not totally regular.
>>
>> All the disk drives are fine. The problem does not seem to be in any
>> peripheral board or device; I've disconnected them all. Removing he
>> memory causes the expected beep sequence for that condition, which
>> further vindicates the CPU, IMHO.
>>
>> The board is only 6 or 7 years old, and has run fine until now. Never
>> had this happen before.
>>


--
You received this message because you are subscribed to the Google Groups "Dixonary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+unsubscribe (AT) googlegroups (DOT) com.
For more options, visit https://groups.google.com/groups/opt_out.

[France International/Mike Shefler]

Double ouch! I keep all my passwords on a piece of paper, but it's
either in Tengwar script or dwarvish runes, so unreadable to the casual
observer.

On 1/18/2014 1:16 PM, hello wrote:
> Saturday, January 18, 2014, 12:43:40 PM, you wrote:
>
>> Ouch! If you can somehow move or connect the old hard drives to your
>> notebook, you can at least recover your files.
> Oh, I have access to all the files...except the one critical one with
> my passwords in it. Everything is multiply backed up, too. But that
> one file with all my (generally strong and unrememberable) passwords
> was encrypted using the native Windows/NTFS encryption feature.
>
> Turns out I never understood how that works: you MUST export a
> certificate onto some external device to be able to decrypt any
> encrypted files or folders if they are accessed from a system and
> logged-in user other than the one they were encrypted with. I had
> never done so, thinking that, should it become necessary, all I would
> need was my user ID and password. Wrong, wrong, WRONG! So the only
> hope of recovering the file is to boot up the original OS on the
> system drive. But I own no other computer with SATA controllers (just
> IDE) that I could plug the system drive into, so I have to wait until
> I can repair the old one.
>
>
>> On 1/18/2014 12:35 PM, hello wrote:
>>> I have suffered a catastrophic computer failure on the main computer I
>>> use for Dixonary (and almost everything else). I have managed to
>>> cobble together an old email client on a notebook computer I
>>> infrequently use to manage the rest of the deal.
>>>
>>> The failure, for the computer geeks, seems to be in the motherboard
>>> itself. The POST runs for about 8 seconds after powerup, then right at
>>> the point the disk drive activity LED turns on, everything shuts down.
>>> After a few seconds, it automatically tries to restart, and repeats
>>> the cycle. Sometimes the shutdown happens after only a second or two,
>>> so it's not totally regular.
>>>
>>> All the disk drives are fine. The problem does not seem to be in any
>>> peripheral board or device; I've disconnected them all. Removing he
>>> memory causes the expected beep sequence for that condition, which
>>> further vindicates the CPU, IMHO.
>>>
>>> The board is only 6 or 7 years old, and has run fine until now. Never
>>> had this happen before.
>>>
>

--
You received this message because you are subscribed to the Google Groups "Dixonary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+unsubscribe (AT) googlegroups (DOT) com.
For more options, visit https://groups.google.com/groups/opt_out.

[Daniel Widdis]

I am now motivated to learn runes to hack your system.

Sent from my iPhone

> On Jan 18, 2014, at 11:29 AM, France International/Mike Shefler <stamps (AT) salsgiver (DOT) com> wrote:
>
> Double ouch! I keep all my passwords on a piece of paper, but it's either in Tengwar script or dwarvish runes, so unreadable to the casual observer.
>
>> On 1/18/2014 1:16 PM, hello wrote:
>> Saturday, January 18, 2014, 12:43:40 PM, you wrote:
>>
>>> Ouch! If you can somehow move or connect the old hard drives to your
>>> notebook, you can at least recover your files.
>> Oh, I have access to all the files...except the one critical one with
>> my passwords in it. Everything is multiply backed up, too. But that
>> one file with all my (generally strong and unrememberable) passwords
>> was encrypted using the native Windows/NTFS encryption feature.
>>
>> Turns out I never understood how that works: you MUST export a
>> certificate onto some external device to be able to decrypt any
>> encrypted files or folders if they are accessed from a system and
>> logged-in user other than the one they were encrypted with. I had
>> never done so, thinking that, should it become necessary, all I would
>> need was my user ID and password. Wrong, wrong, WRONG! So the only
>> hope of recovering the file is to boot up the original OS on the
>> system drive. But I own no other computer with SATA controllers (just
>> IDE) that I could plug the system drive into, so I have to wait until
>> I can repair the old one.
>>
>>
>>>> On 1/18/2014 12:35 PM, hello wrote:
>>>> I have suffered a catastrophic computer failure on the main computer I
>>>> use for Dixonary (and almost everything else). I have managed to
>>>> cobble together an old email client on a notebook computer I
>>>> infrequently use to manage the rest of the deal.
>>>>
>>>> The failure, for the computer geeks, seems to be in the motherboard
>>>> itself. The POST runs for about 8 seconds after powerup, then right at
>>>> the point the disk drive activity LED turns on, everything shuts down.
>>>> After a few seconds, it automatically tries to restart, and repeats
>>>> the cycle. Sometimes the shutdown happens after only a second or two,
>>>> so it's not totally regular.
>>>>
>>>> All the disk drives are fine. The problem does not seem to be in any
>>>> peripheral board or device; I've disconnected them all. Removing he
>>>> memory causes the expected beep sequence for that condition, which
>>>> further vindicates the CPU, IMHO.
>>>>
>>>> The board is only 6 or 7 years old, and has run fine until now. Never
>>>> had this happen before.
>
> --
> You received this message because you are subscribed to the Google Groups "Dixonary" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+unsubscribe (AT) googlegroups (DOT) com.
> For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Dixonary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+unsubscribe (AT) googlegroups (DOT) com.
For more options, visit https://groups.google.com/groups/opt_out.

[France International/Mike Shefler]

First, you'd have to find the piece of paper. No easy task in my office.

On 1/18/2014 2:52 PM, Daniel Widdis wrote:
> I am now motivated to learn runes to hack your system.
>
> Sent from my iPhone
>
>> On Jan 18, 2014, at 11:29 AM, France International/Mike Shefler <stamps (AT) salsgiver (DOT) com> wrote:
>>
>> Double ouch! I keep all my passwords on a piece of paper, but it's either in Tengwar script or dwarvish runes, so unreadable to the casual observer.
>>
>>> On 1/18/2014 1:16 PM, hello wrote:
>>> Saturday, January 18, 2014, 12:43:40 PM, you wrote:
>>>
>>>> Ouch! If you can somehow move or connect the old hard drives to your
>>>> notebook, you can at least recover your files.
>>> Oh, I have access to all the files...except the one critical one with
>>> my passwords in it. Everything is multiply backed up, too. But that
>>> one file with all my (generally strong and unrememberable) passwords
>>> was encrypted using the native Windows/NTFS encryption feature.
>>>
>>> Turns out I never understood how that works: you MUST export a
>>> certificate onto some external device to be able to decrypt any
>>> encrypted files or folders if they are accessed from a system and
>>> logged-in user other than the one they were encrypted with. I had
>>> never done so, thinking that, should it become necessary, all I would
>>> need was my user ID and password. Wrong, wrong, WRONG! So the only
>>> hope of recovering the file is to boot up the original OS on the
>>> system drive. But I own no other computer with SATA controllers (just
>>> IDE) that I could plug the system drive into, so I have to wait until
>>> I can repair the old one.
>>>
>>>
>>>>> On 1/18/2014 12:35 PM, hello wrote:
>>>>> I have suffered a catastrophic computer failure on the main computer I
>>>>> use for Dixonary (and almost everything else). I have managed to
>>>>> cobble together an old email client on a notebook computer I
>>>>> infrequently use to manage the rest of the deal.
>>>>>
>>>>> The failure, for the computer geeks, seems to be in the motherboard
>>>>> itself. The POST runs for about 8 seconds after powerup, then right at
>>>>> the point the disk drive activity LED turns on, everything shuts down.
>>>>> After a few seconds, it automatically tries to restart, and repeats
>>>>> the cycle. Sometimes the shutdown happens after only a second or two,
>>>>> so it's not totally regular.
>>>>>
>>>>> All the disk drives are fine. The problem does not seem to be in any
>>>>> peripheral board or device; I've disconnected them all. Removing he
>>>>> memory causes the expected beep sequence for that condition, which
>>>>> further vindicates the CPU, IMHO.
>>>>>
>>>>> The board is only 6 or 7 years old, and has run fine until now. Never
>>>>> had this happen before.
>> --
>> You received this message because you are subscribed to the Google Groups "Dixonary" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+unsubscribe (AT) googlegroups (DOT) com.
>> For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Dixonary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dixonary+unsubscribe (AT) googlegroups (DOT) com.
For more options, visit https://groups.google.com/groups/opt_out.