Charles Wilson wrote:
> Never mind. Although it is/was repeatable with the
> run-mkgroup/CYGWIN=ntsec/no-existing-/etc/group scenario, I just had it
> happen again while I was innocently running setup.
>
> My hardware is probably damaged, not just my previous NT software
> installation. @#$!&#$.
The first time, I "reinstalled" cygwin on top of an existing tree.
After completely deleting the entire tree, and *really* reinstalling
cygwin, I have seen no more wacky bluescreens. (/me crosses fingers)
So, problem "solved". I don't think this episode is worth tracking
down; it's probably some weird interaction between my damaged drive, new
W2K install, phase of moon, ...
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
