From: Chris Calvey Newsgroups: comp.os.msdos.djgpp Subject: Re: Bash crashes windows 98 Date: Thu, 9 Mar 2000 16:28:05 +0000 Distribution: world Message-ID: References: <12ibcss5keeo8gou06oobil7ppgfkovad3 AT 4ax DOT com> NNTP-Posting-Host: chris-calvey.demon.co.uk X-NNTP-Posting-Host: chris-calvey.demon.co.uk:193.237.119.218 X-Trace: news.demon.co.uk 952619775 nnrp-06:18623 NO-IDENT chris-calvey.demon.co.uk:193.237.119.218 X-Complaints-To: abuse AT demon DOT net MIME-Version: 1.0 X-Newsreader: Turnpike (32) Trial Version 4.01 Lines: 28 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com In article , Damian Yerrick writes >> >>> Windows is waiting for the "close window" dialog box. One part of the >>> OS has apparently taken out a lock on window creation when the C-M-del >>> code wants to put up the "Kill..." dialog, and the task manager is >>> waiting for that lock to be removed. So it BSOD's out to character- >>> cell mode and asks if you want to wait for the lock to go away (press >>> Enter) or restart the computer (C-M-del again). >I've seen the "waiting for Close Window box to open" BSOD before. Damian Thanks for clarifying matters. This indeed is the situation. To answer Eli, I exit from bash using plain old "exit". I must add that the problem is fairly intermittent and I have tried to identify any patterns in what programs that I have used while in bash, but there appear to be none. Sometimes I can work in bash for hours, exit to windows with no problem. While other times I shell out to bash execute vdir and exit and I get the BSOD. Thanks Chris... -- Chris Calvey