Mail Archives: djgpp/1997/06/03/19:19:17
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
>You will have to investigate further, because your script works for me
>exactly as you'd expect. "/dev/null" is supported by the DJGPP
>library on its lowest level, so the chance of the shell to have any
>impact on that is extremely low.
>
>A few things to check:
>
> 1) Are you running on Windows 95? If so, try booting into
>plain DOS mode (no Windows at all). I tested your script on DOS 6.2.
Yes, I'm running W95. As I said in my reply to Daisuke Aoyama, I will
try under plain DOS 7 and DOS 6.22 and report back on the results.
> 2) Is the drive where you run it somehow unusual (e.g
>networked)? If so, copy everything to a local drive and try again.
H: is a SCSI 1G IOMEGA JAZ drive. SCSI card is IOMEGA JAZ JET, which
internally says it is Adaptec 2930 with Iomega BIOS 1.12. I will try
moving it to a "real" HD and see if the results change.
> 3) Remove any Bash-specific settings in your CONFIG.SYS,
>AUTOEXEC.BAT and DJGPP.ENV and see if that changes anything.
AFAIK, I have no Bash-specific settings in CONFIG or in AUTOEXEC (see
my reply to Daisuke for actual contents), I only set these in the BAT
file that invokes Bash.
>Btw, when reporting information on program versions, it is best to
>post the output of `dir' or `ls -l', so the size and the timestamps
>are clearly visible. Sometimes, updated ports are uploaded to DJGPP
>archives with the same version (since the version is derived from the
>official GNU release) which makes --version output ambiguous. At
>least for Bash, the time stamp you've posted says that you seem to
>have the latest version, so the problem is most probably elsewhere.
OK, I'll remember that.
I'll report back when I have the DOS results. Thanks for your
suggestions.
----------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org)
- Raw text -