On Sat, Jun 18, 2005 at 12:05:03PM -0400, irwin wrote:
>On Fri, 17 Jun 2005 21:49:39 -0400, Christopher Faylor wrote:
>>Corinna managed to narrow down the problem with 16-bit programs so
>>there will be a fix in the next snapshot (and eventually in 1.5.18) but
>>without specific information about f
On Fri, 17 Jun 2005 21:49:39 -0400, Christopher Faylor wrote:
>Corinna managed to narrow down the problem with 16-bit programs so there
>will be a fix in the next snapshot (and eventually in 1.5.18) but
>without specific information about failing 32-bit programs there will be
>no fix forthcoming f
On Fri, Jun 17, 2005 at 09:49:39PM -0400, Christopher Faylor wrote:
>On Thu, Jun 09, 2005 at 03:55:19PM -0400, [EMAIL PROTECTED] wrote:
>>When running some non-Cygwin programs from bash (seems to be mostly a
>>problem with 16-bit programs, but also some 32-bit programs), bash gets
>>an invalid page
On Thu, Jun 09, 2005 at 03:55:19PM -0400, [EMAIL PROTECTED] wrote:
>When running some non-Cygwin programs from bash (seems to be mostly a
>problem with 16-bit programs, but also some 32-bit programs), bash gets
>an invalid page fault in KERNEL32.DLL and pops up a fault dialog.
Corinna managed to n
irwin at bongo wrote:
When running some non-Cygwin programs from bash (seems to be mostly a problem
with 16-bit programs, but also some 32-bit programs), bash gets an invalid page
fault in KERNEL32.DLL and pops up a fault dialog.
I have seen the same problem with WindowsME for at least a mont
When running some non-Cygwin programs from bash (seems to be mostly a problem
with 16-bit programs, but also some 32-bit programs), bash gets an invalid page
fault in KERNEL32.DLL and pops up a fault dialog.
Also, quitting the fault dialog doesn't work - I just get another page fault
dialog each
6 matches
Mail list logo
