From: Brian Beuning , com AT cygnus DOT com Subject: RE: bash on NT 4.0 (was forkee heap_init) 28 Apr 1997 18:50:31 -0700 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <01BC53B3.0DB81330.cygnus.gnu-win32@BRIANB> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Original-To: "gnu-win32 AT cygnus DOT com" , "'Jeff Oh'" Original-Sender: owner-gnu-win32 AT cygnus DOT com Jeff, I have been running bash on two different NT 4.0 systems. One with a p5-166 and NT 4.0 (build 1381) and one a dual p6-150 with NT 4.0 (unknown build level). Good Luck, Brian ---------- From: Jeff Oh Sent: Friday, April 25, 1997 12:14 PM To: gnu-win32 AT cygnus DOT com Subject: bash on NT 4.0 (was forkee heap_init) Despite several good suggestions from this list, I have not been able to determine why bash is generating the forkee heap_init error 487 (this actually happens in the cygwin.dll code, when the child process uses virtual_alloc() to try and reserve a memory block at the same base address as it's parent.) Unfortunately, I can't compile debug versions of the shell or cygwin.dll, since I need to run configure to do so, and I need a working shell to run configure, and bash isn't working, and..... So, as no one else on the list seems to be having this problem, and I get this problem on two separate NT 4.0 systems that I've tried, but on WIN95, is anyone else running bash successfully on a NT 4.0 system of any flavour (but especially build 1381, service pack 2)? Alternatively, while I would prefer to use bash, assuming that I cannot make bash work, has anyone on the list looked at or evaluated other sh or ksh variants for NT. Thanks, Jeff 8-) -- Jeff Oh, Zadall Systems Group. jeffoh AT zadall DOT com 8-) "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." -- Rich Cook - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help". - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".