home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
hcshdemo.zip
/
csh-os2.zip
/
README.TOO
< prev
next >
Wrap
Text File
|
1994-06-16
|
73KB
|
1,657 lines
Hamilton C shell(tm) for OS/2(R) Release Notes 2.2.v
Copyright (c) 1989-1993 by Hamilton Laboratories. All rights reserved.
Change Summary
The basic release history for the C shell has been:
Dec 1988 1.0 First release, running on OS/2 1.0.
Jan 1989 1.01 Cleanup and final release for OS/2 1.0.
Feb 1989 1.02 First release for OS/2 1.1 (Presentation Manager).
Mar 1989 1.03 Cleanup and base release for OS/2 1.1.
Aug 1989 1.04 Command line editing and filename and command
completion added.
Mar 1990 1.05 Support for OS/2 1.2, HPFS and long filenames added
along with many important utilities including grep,
diff, head, tail, sed, etc.
Feb 1991 1.06 Support for user-defined screen colors, inheritable
local variables, higher performance, etc.
Jul 1992 2.0 First release from a unified codebase supporting
OS/2 and Windows NT.
Apr 1993 2.1 Support for Berkeley mode scripts, better error
diagnostics, support for Windows NT March beta.
Sep 1993 2.2 Complete rebuild for Windows NT final release.
Support for starting Win3.x apps seamlessly from
the command line under OS/2 2.x. Addition of the
cron utility.
Along the way, Hamilton C shell has grown from about 35,000 lines of C
to over 113,000 lines. Not one line was ported from or written on anything
but OS/2 or Windows NT.
This document is a detailed summary of all the changes that were made
along the way from one release to another, beginning with the 2.0 release.
Changes affecting only the NT builds are so indicated. (Old release notes
for the various 1.03 through 1.06 builds can be found in oldnotes.zip; unzip
it using PKware's pkunzip shareware utility, available on most bulletin
boards.)
Changes are presented chronologically, so if you're updating from a previous
release, you'll want to jump in somewhere in the middle to start reading.
At the very end of this document is a short list of the known bugs, which
actually tend to be minor limitations in the various releases of OS/2.
You'll also find contact information in case you encounter a problem or
have a suggestion.
Fix Level 2.0 Changes:
493. First release from a new unified codebase from which both OS/2
and Windows NT versions can be built.
494. The shell and all the utilities have been fixed so they no longer
routinely translate a filename to lower case before trying to open it.
That didn't work in situations with an NFS network connection to a UNIX
system with case-sensitive filenames.
Fix Level 2.0.a Changes:
495. [OS/2] The 2.0 version of ls wasn't adding up the allocated sizes of
directories properly when using the -Lw options. It does now.
Fix Level 2.0.b Changes:
496. [OS/2] The C shell can now be run when escaping to the command line from
the OS/2 1.x and 2.0 installation disks.
497. [NT/MIPS] Final cleanup on the C shell codebase to make it portable to
the MIPS RISC processor under NT.
498. [NT] Trying to run a .bat or .cmd file started cmd.exe but didn't
actually run the script. It does now.
499. [NT/x86] A codegen error in the compiler caused :s/.../.../ operations
to trash the heap, causing the C shell to crash randomly.
500. [NT] A minor bug in the common routines used to read number pad
keystrokes was fixed.
501. [NT] A number of bugs in tar.exe that caused it problems opening new
tar files and setting or reporting timestamps on files extracted from or
listed in a tar file were fixed.
502. [NT] More no longer fails with a complaint that it can't scroll or
fill the console if, e.g., you go to the end of a file, page down and
then search backward for text that's not found. The console api's were
erroneously reporting failures when in fact they worked fine.
Fix Level 2.0.c Changes:
503. [NT] The common screen painting library used by the shell and a number of
the utilities would sometimes set the cursor incorrectly if scrolling was
involved. It should now be correct.
504. [NT] cut.exe couldn't read files specified on the command line. It can
now.
505. The di (diff interative) alias for diff -b! (merged diff using color,
ignoring white space differences) has been added to startup.csh and the
definition for the mi (more interactive) alias has been fixed for NT.
506. [NT] ver.csh was added to the bin directory.
507. [NT] The common keyboard routines now recognize ctrl-H as the same as a
backspace and ctrl-[ as an escape.
Fix Level 2.0.d Changes:
508. A long-standing bug in the shell's command line editing routines that
could cause the screen to be painted incorrectly has been corrected.
509. [NT] A bug in the common seek logic used in tar, tail, and xd caused them
to have problems reading files that came in over a pipe on stdin. That
problem has been fixed. binedit, more, sed and tee used the same logic
and were recompiled even though they were unaffected.
510. A long-standing, but usually benign bug in the more filter's ISAM
mechanism was fixed.
511. The shell no longer complains under NT nor fails under OS/2 if one tries
to edit a history reference (e.g., with !!:s/X/Y/) that's > 64K.
512. [OS/2] dskwrite now properly detects and autoformats any unformatted
disks it's given as disks 2 or following when using dskwrite -ac.
513. The sizeof sample script has been improved to run a bit faster and to
avoid problems running out of memory in the C shell if a big directory
is being measured.
Fix Level 2.0.e Changes:
514. [NT] The common keyboard routines have been fixed to silently gobble up
CapsLock keystrokes. They were being passed through to the application.
The shell, mv, cp, rm and more were affected.
515. [NT] The help screens for label, more and tar and for the internal
commands hashstat, kill and ps have been edited to replace references
to OS/2 with NT.
516. eval -h now indicates "success" as its return value. (It no longer
causes a loop to exit.)
517. [NT] The C shell no longer litters the output generated by the setenv
command with current directory variables such as "=C:". Also, it now
correctly reads all current directories out of the environment at
startup.
518. [NT] The C shell now properly treats environmental variable names as
case-insensitive. (They're still case sensitive under OS/2.) The set,
unset and @ statements are case-sensitive (that's so you can still create
shell variables that differ from environmental variables only by case)
but the setenv and unsetenv statements and $var and other variable
references first try case-sensitive, then case-insensitive variable
lookups.
Fix Level 2.0.f Changes:
519. [NT] The NT version of the C shell can now determine, just as the OS/2
version can, whether a child will run in the same or a different window.
If it's a different window, the shell immediately prompts for a new
command.
520. [NT] hlabel.exe now includes a warning in the help screen that setting the
volume label is disabled under NT due to a kernel limitation. Also, it
properly gives an error message if you type "label a:foo".
Fix Level 2.0.g Changes:
521. [NT/x86] rm -x was broken in the 2.0.e build when we switched to the July
SDK compiler; the optimizer generated bad code that we didn't spot.
Rebuilding with optimization turned off with pragmas fixed the problem.
Fix Level 2.0.h Changes:
522. All the utilities have been cleaned up in preparation for the 32-bit
release for OS/2 2.0.
523. binedit, chmod, dim, fgrep and head no longer routinely translate
filenames to lower case, thus avoiding any problems with mixed-case
filesystems.
524. [OS/2] more no longer has problems forward or backward searching across
more than 32,000 lines.
525. When moreh [OS/2] or hmore [NT] recognizes that it's reading from a
file, meaning it can use seeks to re-read any data it discards, it
now buffers only a 100K window into the file. That reduces swapping
under OS/2 and dramatically improves heap performance under NT without
sacrificing functionality.
526. [NT] The C shell now correctly recognizes that it must wait for DOS apps
to complete before prompting for another command.
527. [NT] The C shell now responds to Close events from the pull-down on its
window.
Fix Level 2.0.i Changes:
528. [OS/2] markexe now understands how to mark 32-bit 2.0 applications.
529. The ts.csh script was broken when quoting rules inside a backquoted
string were changed at release 1.06 but went unnoticed until now.
The fix was to delete the now superfluous escaped single quotes.
530. If filename completion matched a file with a ! in the name, it wouldn't
always escape it. Sometimes it'd just single quote it, causing it to
be mistaken for a history reference.
531. des had a couple bugs. Under NT, it would often fail with a divide by
zero due to improper initialization. And under both NT and OS/2, it
didn't handle EOF if data was being read from stdin properly. Both
problems have been fixed.
Fix Level 2.0.j Changes:
532. [OS/2] Since there's no .. entry in the root of a FAT drive, cd .. there
wouldn't work. Instead, the C shell would try cd'ing to one of the CDPATH
directories. It now does the right thing.
Fix Level 2.0.k Changes:
533. [OS/2] The change to markexe at 2.0.i broke it, causing markexe to garble
the .exe header. It now works as it should.
Fix Level 2.0.L Changes:
534. [NT] Complete rebuild of everything for the October Beta version of NT.
535. [NT] Background children are now protected from ^C in a console window
using the new CREATE_NEW_PROCESS_GROUP option to the CreateProcess api.
Also, the kill command now uses, by default, the new GenerateConsole-
CtrlEvent api call to send a ^Break to a child. The advantage is that
if the child is willing to accept it, links to any DLL's are closed
properly.
536. [NT] Support for the new shutdown and logoff signal events has been
added, allowing copies of the C shell to automatically exit when
shutdown or logoff is selected from the Program Manager.
537. [NT] Support for the new LocalTime notion has been added to the date
and ls utilities.
538. Additional work has been done on all the utilities and the shell in
particular to prepare for a full 32-bit OS/2 2.0 release from one common
source base.
539. [NT] The -s option to fgrep and grep didn't work. It does now.
540. [OS/2] A number of bad semaphore races were inadvertently introduced
when support for NT was added at release 2.0. Apparently, they never
caused problems (none were ever reported) but, in any event, they are
fixed now.
Fix Level 2.0.m Changes:
541. [NT] The built-in sleep command no longer forgets to close its open
thread handle. Previously, after running sleep roughly 5000 times, it'd
fail, claiming it couldn't start a new thread.
542. [NT] The -i (interactive) option for mv, cp and rm now works.
543. [NT] Minor changes were made to the shell to prepare it for the DEC
Alpha version of NT.
544. [NT] Support for LocalTime has been added to the touch utility.
545. [NT] The NTVersion (NT Build number) and WinVersion built-in variables
have been added and used in the ver.csh script.
546. A new -u (unbuffered) option has been added to the C shell to allow
it to be used over a communications line.
547. First release of a demo version of the shell and all its utilities.
Fix Level 2.0.n Changes:
548. [NT] Split was broken. It works now.
Fix Level 2.0.o Changes:
549. [NT] If an ordinary foreground child process was started, wait would not
work; it'd think the child never completed. It works now.
550. [NT] ^C now properly kills nested C shell scripts. Previously, ^C only
worked if it happened to come in while the top-most level was running.
551. [NT] The shell could trap in certain situations, usually involving labels.
For example, the one-line script, "foo: echo hello", would trap. It
works now.
552. [NT] If the current directory on the current drive was changed in a
script or other thread, the shell wouldn't properly set it back for child
processes created from other threads. That's been fixed.
553. The w option to a search/replace operation in sed was broken. It's now
working.
554. [NT] The w command to sed didn't know how to open a file that didn't
already exist. It does now.
555. [NT/MIPS] The search/replace command to sed often failed due to datatype
misalignment in the compiled sed script. That's been fixed.
556. [NT] The shell now issues an error message if an attempt is made to pass
a command line longer than 32,282 characters (the limit for the NT
CreateProcess call) to a child.
557. The fullpath function now knows not to let .. segments back up over the
system or resource names in a UNC (network) name. Also, the driveno
function now reports an error if its argument has an invalid drive
specification or is a UNC name.
558. The shell now runs logout.csh scripts properly. A primordial bug caused
it to issue a prompt if it found a logout.csh script (it shouldn't have)
and run just the first statement.
559. [NT] Erroneous statements like "cat >" (i/o redirection with no filename
following) no longer cause the shell to crash. (Actually, this bug has
been in the OS/2 version all along also but just didn't happen to cause
problems.)
560. [NT] File sharing or other errors that prevented a file from being copied
are now reported by cp and mv. Previously, the copy would fail, but
there'd be no warning.
Fix Level 2.0.p Changes:
561. Rerunning a statement that set any of the colors variables to a literal
(e.g., "for i = 1 to 10 do setenv COLORS = black on white; end") used to
cause a trap. It works now.
562. Escape characters in a substitution containing command or variable
subsitutions that were edited to produce more than one word were not
correctly processed. E.g.,
echo "`echo a b`:s/a/A/^""
produced:
A b^"
It should have produced (as it does now):
A b"
563. A long-standing, but only recently reported bug that could cause traps
and assert failures doing a cd +c to a subdirectory on another drive
has been found and corrected.
564. unset'ing or unsetenv'ing a non-existent variable is no longer treated
as an error.
565. [NT/Alpha] First release with support for the DEC Alpha processor.
566. [OS/2 2.0] First build with complete, working, debugged support for
use of 32-bit code and the 32-bit API's under OS/2 2.0.
567. [NT] The SHELL variable, if wasn't already defined in the inherited
environment, would be set to the pathname of the C shell, but with the
last character dropped. This has been fixed.
568. ls.exe now accepts a -q (quiet) option, telling ls not to complain
about non-existent files. Also, it's more consistent when it does
complain. (Previously, it would not complain if it was asked to look
for an "impossible" name, e.g., a long filename on a FAT drive.) ls
also now looks for an LSOPTIONS environmental variable.
569. sed will now ignore Ctrl-Z characters between statements in a script.
This change lets it process scripts created with editors that insist
on pasting a Ctrl-Z (EOF) character onto the end of the files they
produce.
570. [NT] The help alias has been deleted from startup.csh. It really
applied only to OS/2.
571. [NT] The cl.csh (compile and link) and makecpgm.csh (make all the C
programs) scripts have been added to the samples directory along with
a sample skip file containing fragments of lines that should be skipped in
the compiler/linker output.
Fix Level 2.0.q Changes:
572. [NT & OS/2 2.0] A very minor performance improvement was made, eliminating
some unnecessary checks for stack overflow. (The check was superfluous
because under NT and 2.0, the system grows the stack automatically as
needed anyway.)
573. The popup that appears if an internal assertion fails in the C shell
now goes away, showing what was underneath it, when you press a keystroke.
Fix Level 2.0.r Changes:
574. Minor fixups were done to the C shell, patchlnk, dskread, dskwrite,
markexe and setrows to allow demo versions to be built for OS/2.
575. The cookie passed to demo versions of the utilities now expires
more slowly. Previously, the cookie expired too fast to allow the
utilities demos to be run reliably from a CD-ROM.
576. [NT] A typo in the kill -h help screen was corrected.
577. [NT/x86] A compiler optimization bug in rm, mv, and cp that affected
recursive operations against directories has been fixed by turning off
certain optimizations where the problem occurred.
578. [NT] pwd now exits with a correct return code of 0 if it's successful.
Also, it now reports an error if asked for the current directory on an
invalid drive.
Fix Level 2.0.s Changes:
579. [NT] ps was incorrectly reporting running threads as zombies and zombies
(threads that had ended but which hadn't been cleaned up yet) as running.
That's been fixed.
Fix Level 2.0.t Changes:
580. [NT] touch didn't properly recognize 4-digit year numbers. It does now.
581. [NT] ls and pwd didn't properly interpret the MIXEDCASEDRIVES variable
(off-by-one error). Also, the shell and pwd didn't show current
directories in the right case on mixed case drives.
582. [NT] The cl.csh script in samples directory didn't work properly with the
DEC Alpha compiler; it does now. Also, it's been enhanced to look for the
skip file in the same directory with the cl.csh script.
583. [NT] If a child of the C shell changed the console mode (e.g., disabling
processed input, thus turning off Ctrl-C processing) but didn't reset
things before exiting, it could affect the shell. That's been fixed; now
the C shell resets the console mode every time it prompts for a new
command from the keyboard.
Fix Level 2.0.u Changes:
584. [NT] The C shell now ensures that the drive letters passed to the NT
kernel for the current directories are always upper case. Lower case
drive letters have been found to be a problem when spawning POSIX
children.
Fix Level 2.0.v Changes:
585. The C shell now supports command and variable substitution in <<-style
inline i/o ("here" documents). Quoting (with single, double or back
quotes) or escaping any part of the word immediately following the <<
operator suppresses the substitutions.
586. Error reporting is now substantially improved. Messages will now show
the line number of the statement that failed, not where it was called
from even if it was inside a user-defined procedure. Also, by default,
the shell will print out a complete trace of the call stack showing
arguments passed to procedures, scripts, eval statements, etc., all the
way down the stack. (To suppress call stack dumps, invoke the C shell
with the new -t option.)
587. A new mode that provides more strict compatibility with the original
BSD C shell has been added. Triggered by trying to run a script that
starts with #!/bin/csh or if the shell is invoked with the new -B
option, the C shell will attempt to process statements in a more fully
Berkeley-compatible fashion. (Scripts that do not start with #!/bin/csh
will still be processed according to Hamilton C shell rules, even if
the -B option is used to request Berkeley compatibility interactively.)
In BSD compatibility mode:
a. The status variable will reflect the return code from the rightmost
stage of a pipeline. The tailstatus variable will be ignored.
b. All the shell variables will be snapshotted and all new variables
made local to the thread.
c. Berkeley-style $var[...] indexing notation will be used, where the
indexing is by word selection operators (like the :-editing operators)
rather than by expression.
d. All variable arrays (except argv) will start with element 1.
Accessing element 0 will give a null.
e. $0 or $argv[0] will be the scriptname. $argv will be the rest of the
argument vector. The bsdargv variable will be ignored.
f. The # character will not need to be followed by white space to be
considered the start of a comment.
g. The patterns in a case test (inside a switch) will be strings and need
not be quoted, rather than arbitrary expressions. Also, the switch
value is evaluated as a wordlist which may contain variable or command
substitutions and wildcards and then rendered as a string.
h. endif and endsw will be predefined aliases for end (but only when
closing an if or switch, respectively). breaksw will be a pre-defined
alias for break.
i. "set foo" and "setenv foo" will set foo to a null string, not dump
its value.
j. / and /= will perform integer division.
k. The right operand of the =~ and !~ pattern matching operators will be
taken as a word which may contain wildcards.
l. In an expression, a variable must be preceded by $. If it doesn't, it'll
be taken as a literal string.
The changes should allow most scripts to run without problems. However,
there will still be a few differences:
a. The escape character will still be controlled by the escapesym
variable (shared across all threads), which defaults to ^, not \.
b. Environmental variables will still be shared. Changing them in a
script will change them as seen by the parent.
c. The special meaning of several break statements on one line will
not be supported.
d. unset and unsetenv still do not accept patterns.
e. The following commands are not supported: bg, exec, fg, glob, jobs,
limit, nice (but eval gives similar functionality), nohup, notify,
stop, suspend, unlimit and %job.
f. History references inside alias definitions will still not be
supported.
g. The (...) construct will isolate only the current directory, not all
variables and other state information.
588. Running a statement in the background using the & flag at the end of the
line will cause a new "job ID" number rather than a thread ID to be
printed. Any threads, processes or screens spawned by that thread will
inherit that same job ID. The job ID can be passed to the kill command
to kill everything associated with that background job. Also, the ps
command has been enhanced to show job ID numbers.
589. $* is now supported as an alias for $argv.
Fix Level 2.0.w Changes:
590. A number of minor problems associated with supporting substitutions
inside <<-style inline i/o documents were fixed: a) If there was a syntax
error, the prompt would not be properly reset to prompt1. b) Single and
double quotes should have been treated as ordinary characters in inline
i/o. (To quote something, only the escape character can be used.)
c) Any line containing a substitution caused a blank line to be added
to the history list. d) If a substitution was at the end of a line, an
extra space was erroneously added.
591. [NT] The sleep command left a thread entry lying around in the threads
list after it had already exited. It's now properly cleaned up.
592. Filename completion with ^F did not quote special characters if there was
only a partial match. It does now.
593. Doing a "sed '#'" caused a segment fault. It now works.
Fix Level 2.0.x Changes:
594. [NT] rm didn't work on read-only directories even with -f or -x. It
does now.
595. The more -t option for setting tabstops from the command line didn't
work. It does now.
596. diff, uniq, cut, fgrep, grep and sed shared a common i/o buffering
routine that had a bug that could cause them to crash or produce
erroneous results on files with line ends other than \r\n. That's
been fixed.
Fix Level 2.0.y Changes:
597. There was a bug in the Berkeley compatibility mode introduced at 2.0.v
that would cause the shell to hang if a #!/bin/csh script that contained
any set statements was run more than once. That's been fixed.
Fix Level 2.0.z Changes:
598. Calling the abs() built-in function without an argument caused the shell
to crash. It now gives an error message as it should.
Fix Level 2.0.27 Changes:
599. The changes made at 2.0.v to provide call stack dumps caused line
numbers not to be shown in parser error messages when compiling scripts.
That's been fixed.
600. The -I, +I, -O and +O command line options have been added to the C shell
to allow insert mode to be customized. Type "csh -h" for more info.
601. [NT] mv didn't properly move read-only files across disk partitions. It'd
make a copy, then complain it didn't have proper access. It works now.
Fix Level 2.1 Changes:
602. [NT] First complete rebuild for the March beta.
603. [NT] tar now knows that NT keeps track of timezone information. The TZ
variable and the -g and -G options are no longer used.
604. [NT] The shell is dramatically faster, especially at inserting into long
command lines and compiling scripts on the DEC Alpha and MIPS R4x00.
605. The -b option has been added to the C shell to turn off Berkeley mode
even on scripts that start with #!/bin/csh.
606. Error messages from the C shell should now all be properly displaying line
numbers where appropriate.
607. A bug that potentially could have (but was never reported to have) caused
the shell's unproc and unalias commands to crash was fixed.
608. [NT] The cl.csh script in the samples directory has been updated for
the March NT beta and now knows about the hybrid compilers on the MIPS
and Alpha machines. Use -old to get the old compilers.
609. [NT] hlabel.exe can now set the label on a volume. (There was no Win32
API to support this under the October Beta.)
610. [NT] The C shell -Z option now works. (Previously, it was ignored under
NT because there was no support for it under the October Beta Win32.)
611. [NT] The rm.exe command has been renamed hrm.exe and an "alias rm hrm"
command added to the default startup.csh script to avoid conflicts with
the brain-dead Microsoft rm.exe command supplied with the NT SDK.
612. [OS/2 2.0] Inexplicably, DOS VDM applications were being started in
invisible windows. Accessing them required typing Ctrl-Esc. They're
now properly started in visible windows.
Fix Level 2.1.a Changes:
613. [NT] Touch, mv, cp and tar now know how to set the timestamps on
directories.
614. csh -XC now looks for a command immediately following the "C". It no
longer tries to parse any remaining characters in that word as option
characters and no longer requires the command to start in the next word.
Fix Level 2.1.b Changes:
615. [NT] Hlabel would only change the label on the current drive. It works
properly now.
616. The C shell didn't properly handle $i[$j] and $i[$k[^]] references in
Berkeley compatibility mode. That's been fixed.
617. Set variables weren't always inherited by child threads in Berkeley mode.
For example,
% set i = 1; echo `echo $i`
didn't work. It does now.
Fix Level 2.1.c Changes:
618. In Berkeley mode, double quoted substitutions involving $0 could fail.
E.g.,
% echo "$0 a"
caused the shell to crash. It works now.
619. The Berkeley C shell would accept case clauses that didn't have colons
following the test and those with quotes around the pattern. This wasn't
the documented behavior but some users did write scripts that depended on
it so Hamilton C shell now allows that also in Berkeley mode.
620. for i = 1 to 1 by -1; echo $i; end would loop thru 1, 0, -1, -2, -3, etc.,
rather than exiting after the first iteration. That's fixed now.
Fix Level 2.1.d Changes:
621. [NT] Trying to set path[i] garbled the global variables lock. That
statement would appear to work, but, e.g., trying then to do a setenv
would hang and eventually crash. That's been fixed.
622. In Berkeley mode, other indexed variable references such as @ i[$j]++
didn't index properly. They do now.
623. [NT] The cl.csh script in the samples directory didn't properly work
with -O options. It does now.
Fix Level 2.1.e Changes:
624. [NT] The dskwrite and dskread utilities have (finally!) been added.
625. [NT/x86] Tar no longer fails when it tries watching for binary files and
automatically turning off \n to \r\n conversions. (This was actually a bug
in all versions of tar; for some reason, it just didn't manifest itself
except in the NT/x86 version.)
Fix Level 2.1.f Changes:
626. [NT] A bug in NT's DOS subsystem caused DOS apps started from the C shell
to think they were running in the wrong current directory. E.g.,
1 C% cd \tmp
2 C% dosapp
3 C% cd ..
4 C% dosapp <-- Still thought it was in \tmp
This build contains a workaround for the problem.
627. In Berkeley compatibility mode, the C shell no longer tokenizes #
separately to recognize comments. Thus, where previously
echo `echo '#r'`
produced "# r", it now properly produces "#r".
Fix Level 2.1.g Changes:
628. dskread and dskwrite didn't properly handle missing ordinates, e.g.,
(35,,) or ranges that weren't closed, e.g., (50,0,0)-. It works now.
629. [NT] dskwrite didn't work at all writing an entire disk. It does now.
630. [NT] ls no longer generates a spurious "'*.*' does not exist" message
when listing a blank formatted diskette. Also, it now does give a
message when listing an unformatted diskette.
Fix Level 2.1.h Changes:
631. Changes made to support stack tracing caused the shell to crash if the
prompt was set to something involving command substitution. That's fixed.
632. In certain cases, the diagnostics would indicate an error at line 1 when
it should have said something else. That's been fixed.
633. The C shell's -I option didn't work. It does now.
634. [NT/Alpha] Expressions such as i += 1, where i is an integer, were
incorrectly producing a floating point result due to a compiler
optimization error. In this build, optimization has been turned off
for the relevant module to ensure correct results.
635. [NT/Alpha] du didn't correctly report the total space on a drive.
This build contains a workaround.
636. [NT] dskwrite -F crashed. It works now.
637. [NT/Alpha] dskread and dskwrite would frequently fail, complaining they
couldn't read the drive parameters, if the diskette drive had not
previously been accessed. Rerunning dskread or dskwrite would work.
This has been traced to a bug in the Alpha/NT system; the current build
contains a workaround to ensure correct results.
638. [NT] It's now possible to redirect stdout to a device such as \\.\a: or
\\.\tape0.
Fix Level 2.1.i Changes:
639. tar complained about archives created on UNIX SVR4. The SVR4 tar writes
all octal fields in the header as null-terminated strings, contrary to
spec as defined in the BSD 4.3 Programmer's Manual which says that many
of the fields should be terminated with space + null and others not
terminated at all. Hamilton tar now knows to accept this variant format
without complaint. Also, when tar extracts files, it now sets the archive
bit on the newly-extracted files.
640. mv and cp now retain the case of any filenames they move. Previously,
if one typed "mv foo ..", the resulting file would be in whatever case
was typed, not what it had been stored as previously.
641. [NT/Alpha] Expressions like 2**10 resulted in floating point results
(albeit correct ones) when they should have produced integer results.
This build contains a workaround.
642. [NT] winerror.c and winerror.exe were added to the samples directory
and the help proc definition were added to startup.csh. This gives a
convenient means of getting the Win32 error message corresponding to a
return code.
643. [NT] The source command should have tried pasting a .csh extension onto
the filename if the name as specified didn't exist. It does now.
644. Command substitution now processes certain unquoted escape sequences in
the backquoted string before parsing it. This ensures, e.g., that the
following will work, producing "1 2 3 4 5":
echo `for i = 1 to 5 do ^
echo $i ^
end`
645. If callstack reporting was turned off with csh -t, there was a possibility
(never reported) that the shell could crash following stack pops. That's
been fixed.
646. The shell now generates callstack reports for scripts read with the
source command and now reports the correct linenumber if a syntax error
is encountered inside the sourced script.
647. [NT/Alpha] strings was broken due to a bug in the Alpha compiler. This
build contains a workaround.
648. [NT] International keyboard keying conventions (e.g., ALT + 8 to create
the "[" character on a German keyboard) should now be working. This
change affects the C shell, mv, cp, rm, more and des.
Fix Level 2.1.j Changes:
649. [NT/x86] diff had two problems with binary files: a bug in the code that
automatically detected binary data could cause diff to crash. Also, a
compiler optimization bug caused diff to claim there were differences in
binary files that were in reality exactly the same. This build fixes
both those problems.
Fix Level 2.1.k Changes:
650. [NT] The change made at 2.1.i for international keyboards ended up
breaking support for Ctrl + other keys such as Enter or [. That's now
fixed, affecting the C shell, mv, cp, rm, more and des.
651. Startup.csh changed to show how users might customize it to have operands
to dir wildcarded by the C shell or by cmd.exe itself.
652. [NT] The cl.csh script in the samples directory now accepts the CPU
variable values typed in mixed case.
653. [NT] The C shell no longer hangs if you attempt to kill a child Win3.x
app and then do a ps. (But you still can't kill the Win3.x children,
apparently due to a bug in NT.)
654. [NT] The C shell now places =X:-style current directory variables into
the environment for all valid drives at startup, even for drives for
which the current directory is the root. This is to work around an
apparent problem in the VDMs under NT on the RISC machines.
Fix Level 2.1.L Changes:
655. The changes made to support the -B (Berkeley compatability) option
broke the use of the bsdargv variable and could cause the shell to
crash. bsdargv is more-or-less obsolete now, but it certainly shouldn't
cause a crash; it's been fixed in this build.
656. The startup.csh file has been fixed so that the alias/proc mechanisms
used to intercept copy, xcopy, etc., will still work if the shell is
invoked with -B. (The problem was with the @ s = nowild statements in
the aliases. In Berkeley mode, a $ was needed to make a valid
expression.)
Fix Level 2.1.m Changes:
657. The changes made to support the -B (Berkeley compatability) option
introduced a bug in indexed variable evaluations done in the prompt1
and prompt2 variables. Also, some never reported but latent bugs in
iterated statements containing indexed variable references were fixed.
Fix Level 2.1.n Changes:
658. Yet another UNIX tar was discovered that formatted octal fields in
the headers slightly differently than the spec required, causing our
tar to reject the file. This release contains a fix to cause tar to
accept virtually anything that looks like a plausible octal number.
659. Filename expansion now knows to quote or escape any { or } characters
in any files it matches.
Fix Level 2.1.o Changes:
660. [NT] The C shell now knows to ignore nonsensical Ctrl-<key> combinations.
Previously, these keystrokes could cause the C shell to get confused about
the cursor position.
661. [NT/Alpha] Problems with expressions for which workarounds were added
at 2.1.h and 2.1.i have finally been tracked down to a legitimate coding
bug in the long precision math routines for the Alpha. It's corrected
in this build.
Fix Level 2.1.p Changes:
662. sed no longer allows "." to match either CarriageReturn or NewLine. This
ensures that
echo abc | sed 's/./& /g'
sensibly produces "a b c \r\n", not "a b c \r \n ".
663. Typing a few characters onto the command line, pressing Escape and then
End caused the C shell to put the cursor in the leftmost column in the
window rather than, as it should have, in the column following the prompt.
That's been fixed.
664. [NT] The cl.csh script now knows how to handle C++ files with .cpp
or .cxx extensions, resources in .rc, .res or .rbj files, and create
either console (default or -console) or graphical (-GUI) applications.
665. [NT/x86] The args.exe, dumpenv.exe, myecho.exe and rcode.exe files in
the samples directory had never been rebuilt since the October beta.
They worked on the March beta but not the later builds. They have
now been rebuilt.
Fix Level 2.1.q Changes:
666. [OS/2] The startwin.exe utility has been added. This is a tiny PM
program that can be used to start Win3.x apps seamlessly on the desktop
under OS/2 2.x. It's automatically invoked by the C shell if you type
the name of a Win3.x app when running under OS/2 2.x. For more info,
type "startwin -h".
667. The C shell now intercepts the situation where a PM child under OS/2
or a non-console app under NT is being run and stdout or stderr is tied
to the C shell's console window. Since console handles aren't inheritable
in these cases, the C shell will instead pass a handle to the input end
of a pipe and start a new background thread to copy anything written into
that pipe onto the screen. This lets ordinary printf's be used in PM
or Win32 GUI apps without losing the output.
668. In Berkeley mode, the C shell no longer does any history expansion inside
comments.
Fix Level 2.2 Changes:
669. [NT] A complete rebuild of the whole product on the release versions
of NT on all three platforms.
670. [OS/2] If a child process ended with a hard error or a trap, the
C shell didn't dump out the call stack. It does now.
671. The C shell no longer routinely translates the PATH directory names
to lower case.
672. Processing of special characters inside single- or double-quoted
strings has been improved slightly. It's now possible to type, e.g.,
set prompt1 = '$ansi("bright yellow")$cwd '
673. ls.exe now gives an error message if a UNC name it's given doesn't
exist. Previously, the message was generated only for non-existent
local names.
674. [NT] cl.csh in the samples directory has been updated for the final
release of NT, which does not use an ntdll.lib. It now accepts -O...
optimization options which override the defaults. When it finds a
skip file, it sets the shell variable, skip, to the full pathname; that
allows the ferr alias to work even if cl is called first from its own
directory and later from another directory. Also, cl knows that in
the final release for the Alpha, acc can (finally!) use the INCLUDE
environment variable; it's no longer necessary to break it up into
a series of -I options. Finally, the _MT symbol is now defined.
675. [NT] cp now knows how to set the timestamps on any read-only directories
it copies.
676. head, tail and tabs had a bug that caused the [ in an ANSI escape
sequence to be turned into two ['s if it fell on a buffer boundary
when expanding tabs.
677. The demo.exe supplied with the demo version of the C shell no longer
uses the existing HOME variable even if it's defined. That was causing
problems when HOME pointed to something with different/missing login.csh
or startup.csh files. Also, under NT, it now registers a signal handler
so it won't exit before its child has exited.
678. It's now possible to wildcard drive letters. E.g.,
ls *:\*\bin
now works. If an * or ? is specified for the drive letter wildcard,
then the set specified by the DRIVEMASK environmental variable is used.
If DRIVEMASK has not been set, the drives c: thru z: (as may exist) are
searched. To search drives a: and b:, which are usually floppies, you
must specify them explicitly, e.g., [a-z]:\*\bin. Also, if the path
is on one of the MIXEDCASEDRIVES, the entire resulting path will be in
the correct case.
679. fullpath now puts the resulting pathname into the actual case stored
in the filesystem if the the path is on one of the MIXEDCASEDRIVES.
Otherwise, it puts the result into all lower case.
680. ls wouldn't report anything on a UNC drive if invoked with the current
drive was one of the MIXEDCASEDRIVES. It works now. Also, MIXEDCASEDRIVES
can now accept a list of UNC servers and/or drives following the range
of drive letters. For example:
setenv MIXEDCASEDRIVES = d-f,\\alpha\drive-c,\\beta
means that drives d: thru f:, drive-c on \\alpha, and all drives on
\\beta are mixed case. \\ without a machine name means all UNC names
should be reported in mixed case. Individual list items should be
separated by commas, semicolons or white space.
681. du now complains if you ask for it to report on something other than
a: thru z:.
682. cp and mv no longer attempt to set the timestamp of an existing directory
when merging in another directory (e.g., in doing "mv a: .").
683. [NT] cp and mv no longer give a bogus message about not being able to
query path info about the root directories on diskettes.
684. [OS/2] newer and older failed to compare the seconds component if two
timestamps matched down to the minutes. That's fixed.
685. The cron utility has been added. For help, type "cron -h".
686. The -Y option to suppress the installation of an interrupt handler
has been added to the C shell. Under NT, this option is ignored.
687. fgrep -x didn't match lines that didn't happen to cross buffer
boundaries. It should now work in all cases. Also, a minor change
in the interface to internal get_line routine was made in fgrep, grep,
and cut.
688. The C shell now accepts empty statement lists in an if/then/else,
following a default: case in a switch statement or in (...) or
{...} groups for better compatibility with the Berkely C shell.
689. more didn't properly truncate the filename in the prompt at the bottom
of the window if the filename was too long. Under NT, that caused it
to fail completely. Under OS/2, it ran, but it couldn't display command
keystrokes. All that's fixed.
690. [NT] If dskread/dskwrite is unable to open a drive because of a
sharing violation, it waits 3 seconds and tries again. This is to
allow any writes in the system buffers to get flushed to the drive.
Fix Level 2.2.a Changes:
691. [NT] The mt (mag tape) utility has been added. Type "mt -h" for help.
692. Tar now ensures that it never writes blocks of less than 512 bytes
at a time. That was important for writing to the tape device under NT.
693. [NT] dskread and dskwrite will now sleep up 7 seconds in 100 millisecond
increments, waiting for a slow diskette to free up rather than a flat,
all-or-nothing 3 seconds.
Fix Level 2.2.b Changes:
694. [NT] Changes (mostly just to the makefiles) to support a port to another
unannounced RISC processor running Windows NT.
695. [NT] strings -v didn't properly display the filenames associated
with the strings it found. It works now.
Fix Level 2.2.c Changes:
696. [NT] If the C shell was started with a title bar longer than 127
characters, it would crash. That's fixed.
Fix Level 2.2.d Changes:
697. [NT] More minor changes for yet another port to an unannounced RISC
processor running Windows NT.
698. [NT] mt.exe didn't format error messages properly. It does now.
699. [NT] touch.exe had an uninitialized variable that caused it to set
timestamps off by a random number of milliseconds. That's fixed.
Fix Level 2.2.e Changes:
700. Changes made at release 2.2 related to better support for mixed case
drives created a bug in the fullpath built-in function which caused a
number of problems on a mixed case drive: (a) fullpath("*.*") returned
"c:\foo\." rather than "c:\foo\*.*", (c) under NT, fullpath opened a
FindFirstFile directory handle that it would forget to close, making it
impossible to delete the directory, (d) the shell would claim it
couldn't find executable files in the current directory, (e) if nohashing
was set to 2, then the shell wouldn't be able to delete any directory
which had been a current directory at a time when any external program
was run. All these (seemingly different) problems were the result of
the same 2-line bug, now fixed.
701. Those same changes at 2.2 to support mixed case also involved turning
all filenames to all lower case on non-mixed case drives in the fullpath
function and in the filename editing functions (:b, :e, :f, :t). That
caused problems for a large customer and has been backed out.
702. [NT] The C shell now uses _beginthread/_endthread to start or exit any
threads it creates instead of calling CreateThread directly. Microsoft
has advised that the C run-time library (including even basic functions
like malloc) may cause memory leaks if _beginthread isn't used.
703. [NT/Risc machines] tr -s (squeeze option) didn't work. It does now.
704. [NT] A bug in the common display routines caused ANSI escape sequences
to be parsed incorrectly if the escape sequence was broken across a
buffer boundary. The failure was a very rare event, but it could
affect lots of utilities. It's fixed in this build.
705. [NT] xd -w didn't work properly. It does now.
706. A set of sed scripts have been added to the samples directory for
converting Bourne/Korn shell scripts into C shell scripts. Customers have
reported these sed scripts eliminate about 85% of the work of converting
shell scripts.
Fix Level 2.2.f Changes:
707. Statements joined with the && conditional execution operator were
viewed as having failed with an error (causing loops to exit, etc.) if
the leftpart returned a non-zero return code. It should not have been
an error and is now fixed.
Fix Level 2.2.g Changes:
708. If there were any command or variable substitutions inside a <<-style
"here document", the line number was incorrectly incremented a second
time. That's been fixed.
709. Cron has been enhanced to treat blank lines and lines beginning with
# as comments. It also now give a warning if the values specified in
any particular field are not monotonically increasing (to help catch
mistakes forgetting to use 24-hour times). Finally, a bug in the
parsing of the day/date specification fields has been fixed.
710. The C shell has been enhanced to support use of Tab and Shift-Tab for
file completion. Repeatedly pressing Tab gives the first and following
matches, one at a time. Shift-Tab starts at the end and works backward.
To disable Tab completion, start the C shell with the -T option. (You
may wish to use the CSHOPTIONS variable to do this.)
711. Heapstat figures could become garbled if filename completion was used
and it resulted in a large number matches. That's corrected.
712. A dollar sign that's not followed by a valid variable reference is now
treated as literal text rather than as an error. That makes it more
convenient, e.g., to type UNC names such as \\alpha\d$; it's no longer
necessary to remember to escape the $.
713. A bug in processing of the MixedCaseDrives variable has been fixed.
Fix Level 2.2.h Changes:
714. The Tab completion introduced at 2.2.g had a few bugs: If there were
no matches found, the shell crashed. The original wildcard string was
garbled if one tabbed all the way thru the ring back to the original
wildcard. There were some minor memory leaks. Finally, the help
information was wrong: -T _disables_ tab completion. These problems
have all been fixed.
715. [NT] The blksize utility has been added to the samples directory. It
can be useful for reading/writing tape devices that support only certain
blocksizes.
716. [NT] cp no longer allows one to destroy a file by copying it over the
top of itself.
Fix Level 2.2.i Changes:
717. More work on tab completion: when tab completion is enabled, a plain
tab can be typed as Ctrl-Tab. When -T is specified, tab completion is
now still available, but as Ctrl-Tab and Shift-Tab.
718. Aliases now support arguments using the history reference-style syntax
used by the Berkeley C shell. If there are no references, any arguments
are simply pasted on the end of the expansion as before. For example:
1 D% alias test echo ^!^* world
2 D% alias test
test echo !* world
3 D% test hello
hello world
4 D% alias test echo hello
5 D% test world
hello world
719. Long-form history references now properly support braces around the
argument. E.g., "!{!}" is the same as "!!".
720. [NT] "mt -v status" now continues dumping the tape device status even
if it cannot determine the block number at which the device is positioned.
Also, some of the status information was garbled; it's now correct.
721. Editing operators may now be used inside the curly braces in a variable
reference, e.g., ${cwd:h}. Also, any number of braces may be nested
around a variable substitution.
722. A memory leak when aliases were unaliased has been fixed.
723. The member.csh script has been added to the samples directory.
724. (...) statement groups and {...} expressions weren't being evaluated
correctly. The status code was being discarded. (That made {...}
expressions pretty useless.) That's fixed now. Also, {...} expressions
no longer push & pop the directory stack on entry and exit.
Fix Level 2.2.j Changes:
725. Wildcarding and filename completion didn't work with MixedCaseDrives
set if the pattern contained a ".." or "." level. That's fixed.
726. Doing Shift-Tab, then Tab skipped over the step of reposting the
original wildcard string. That's fixed.
727. The -Z option has been added to rm.exe (hrm.exe under NT) to allow
a file to be completely overwritten with binary zeros before deletion,
thus guaranteeing that no one can "undelete" the file later.
728. [NT] The change made to cp at 2.2.h was too conservative and caused
it to refuse to some copies that were legitimate, e.g., "copy foo\bar .".
That now works.
729. tar has been dramatically improved. Over 30% more code was added,
to provide these new features and improvements:
a) It now is able to read/write CPIO ascii and binary files and to
automatically recognize them when it encounters them.
b) It now knows how to do \r\n -> \n conversions to an archive even
when it's writing the archive to a pipe or a tape device where seeking
back to the header to fixup the size field is impossible. (It now
uses a prescan of the data if seeking is not going to be possible.)
c) A new -ff variation on the fullpath option causes tar to write the
entire pathname specified on the command line (including any drive
letter and colon) into the archive. This isn't really legal for
restoration on a UNIX machine, but it does let you use tar to back
up more than one drive at a time.
d) If \'s were typed in filenames given on the command line, tar would
not convert those to /'s in the archive. That caused problems for
restoration on a UNIX machine. tar now converts all \'s to /'s.
e) A lot of work was done to directly support tape drives under NT.
Tape devices can now be opened as an archive file using the name
\\.\tape0. It's now possible to specify a blocksize to be used in
reading/writing the archive. Also, if tar discovers the archive
is on a tape device, tar will try to ensure that it's using a
blocksize that's compatible with the drive and that the drive has
been properly initialized.
f) The -v (verbose) option now causes tar to report the format (TAR vs.
CPIO binary vs. CPIO ASCII) and byte sex was used in the archive.
g) The -b (bytesex) option didn't work. It does now.
h) If a file being added to an archive is on a drive listed in the
MixedCaseDrives environment variable, the filename will be stored
into the archive in mixed case.
730. uniq -u didn't report the last line if it was unique. It does now.
731. Null argument words weren't being passed to child processes started
from the C shell. E.g.,
1 C% myecho hello "" world
'myecho' 'hello' 'world'
arg length = 19 characters.
It should have (and now, does) produce:
'myecho' 'hello' '' 'world'
arg length = 20 characters.
732. The sample startup.csh has been modified so that it can be re-invoked
by the same copy of the C shell without causing the layer number to be
incremented.
733. [Demo versions] The maximum number of commands that can be typed before
the demo exits, forcing the user to start a new copy has been raised from
5 commands to 10 commands.
Fix Level 2.2.k Changes:
734. If certain wildcarding situations with MixedCaseDrives, the shell would
forget to close a directory handle, making it impossible to delete the
directory without exiting the shell. That's fixed.
735. More work on cp to avoid problems copying files on top of themselves,
this time treating the case "cp x d:" where x is on d:.
Fix Level 2.2.L Changes:
736. Corrected minor typos in the tar help screens.
737. [NT] Minor support work for unannounced RISC platforms.
738. [NT] A new, more standard makefile has replaced the old samples.mak
in the samples directory.
Fix Level 2.2.m Changes:
739. A bug in the goto statement implementation that could cause access
violations in the C shell was fixed.
740. Minor typos in the tar help screens were fixed.
Fix Level 2.2.n Changes:
741. Incrementing or decrementing an indexed built-in variable (e.g.,
processid[1]++) actually changed argv, not the intended variable. That's
fixed.
742. The new tar was incorrectly writing directory names as if the -f option
was specified, even if it wasn't. Files themselves were added correctly.
Now, both should be right. Also, when listing the contents of a tar
archive, tar printed the trailing / following directory names, just as
they appeared in the archive. That trailing / is no longer shown, making
the output a little more like that of ls.
743. [NT] Trying to move a directory from one partition to another would fail
with a sharing violation, claiming the directory was in use by another
process, if the directory contained subdirectories. That's fixed.
744. If MixedCaseDrives was used, wildcards like ..\..\* would fail if used
more than 2 levels down from the root. That's fixed.
745. Ctrl-C interrupt handling has been improved. Interrupts now bubble
up better from interrupted child processes and threads to the threads
that created them.
746. The C shell no longer abitrarily sets its exit code to 1 when it
should be 0.
Fix Level 2.2.o Changes:
747. The new tar was properly reading cpio ASCII files, but wasn't writing
them correctly. Support for cpio binary files just didn't work at all.
Appends to either tar or cpio files also didn't work. All this should
be working now.
Fix Level 2.2.p Changes:
748. Environment variables could be properly set to zero words, but if a
new child copy of the C shell was started, it'd parse the value it was
passed as a single word consisting of the null string. That's fixed.
749. If ignoreerors was set to 2 (ignore everything), then continue, break,
goto, exit, logout and return statements were treated as nops. That's
fixed.
750. The -e (execute only, no logging to history) and -L (load history)
options have been added to the source command. Also, the -n (no
execute) option has been changed to do a syntax check, consistent
with the -n option for the C shell itself.
751. If the C shell is started with the -n (no execute) option, exit didn't
work. It does now.
Fix Level 2.2.q Changes:
752. [NT] The mt -f option didn't work. It does now.
753. source -s could cause the shell to crash if it was trying to read
from the keyboard. The bug could apparently (though never reported)
also cause other failures. The problem is now fixed.
754. If the new argument notation was used in an alias, then word separator
characters were incorrectly handled. Aliases such as the following
didn't work, but should now:
alias x (echo ^!^*; echo hello)
Also, errors involving unpaired quotes in an alias expansion such as
the following were overlooked. They're now caught.
alias y echo "'"
Fix Level 2.2.r Changes:
755. The demo version of cron were looking for csh.exe; they should have
been looking for cshdemo.exe.
756. Minor work to support a demo version of the C shell that would expire
at a future date.
Fix Level 2.2.s Changes:
757. [NT] The work done at release 2.2.e to use _beginthread instead of
CreateThread has been undone after it was discovered that the thread
handle returned by _beginthread is unreliable. The C shell and all the
utilities and samples now use the single-threaded CRTL, locking each
use with a critical section. In general, things are now a bit smaller
and a bit faster.
758. [NT] Everything has been recompiled on Daytona. It should, however,
still be fully compatible with the released NT 3.1 build.
759. [NT] dskread and dskwrite now use paragraph-aligned (16-byte aligned)
buffers for all I/O to the diskette. Something changed in Daytona,
non-paragraph-aligned buffers used to work under NT 3.1, but stopped
working on the MIPS under Daytona.
760. [NT] The blksize utility in the samples directory now uses a paragraph-
aligned buffer.
761. Tar didn't work if you tried backing up a root directory. Under NT,
it did nothing; under OS/2, it crashed. That's now fixed.
762. Sed now accepts escape sequences like \r and \n in search and replace
expressions. Also, the help information for static text operations
(a\, c\ and i\) has been made a bit more readable.
763. [NT] The cl.csh sample script has been updated for the Daytona beta.
764. [NT] The tape device always reports an error, ERROR_BUS_RESET, if
GetTapeParameters is called immediately after a new tape has been
inserted. Calling GetTapeParameters again gives useful information.
The mt and tar utilities have been fixed to do that second attempt.
765. [NT] The eraseshort operation has been added to mt.
766. [NT] Some additional nuisance messages produced by the Daytona compilers
have been added to the skip file in the samples directory.
Fix Level 2.2.t Changes:
767. Expressions in an elif clause were evaluated in Hamilton C shell mode,
even inside #!/bin/csh scripts, where clearly Berkeley rules should be
used. That's been fixed.
768. [NT] Under Daytona (NT Release 3.5) or later, the C shell now starts
child processes with error mode set to zero, just as cmd.exe does.
The C shell itself uses a non-zero error mode to disable popups,
allowing the shell to intercept any error conditions. That's important
to allow unattended scripts to be run. But error mode was inheritable
under NT 3.1 and it caused problems with some 3rd party apps that
just assumed they'd be started with error mode = 0. Daytona has a
new option to CreateProcess to allow apps running with a non-zero
error mode to start children with a zero error mode.
Fix Level 2.2.u Changes:
769. [NT] Changes made at 2.2.s to use CreateThread instead of _beginthread
and GlobalAlloc instead of malloc introduced a bug into the C shell
and cron: their use of GlobalReAlloc was flawed and caused any
reallocations (e.g., if editing caused the command line to grow beyond
4 lines) to fail.
770. Dskwrite and cp, rm and mv can now diagnose more clearly those
failures due to write-protected media.
771. cron now considers a Ctrl-Z character in a crontab as an end-of-file.
Also, if any of first five fields is garbled, the message is better.
772. The line numbers in any messages resulting from a garbled command
specified with -C or -c are now correct. A counter hadn't been
re-initialized after login.csh and startup.csh were read.
773. Tar's verbose messages now mention the blocksize it's using.
Fix Level 2.2.v Changes:
774. Support for escape sequences such as \r, added to sed at build 2.2.s,
has been added to grep. Hex escape sequences, which didn't work right
in sed, have been fixed and work properly in both sed and grep.
775. Sed and grep now accept span expressions using the \{n,m\} syntax.
E.g., grep '10\{2,4\}1' will match 1001, 10001 and 100001, but not
101 or 1000001.
776. The rot13 alias (for decoding off-color jokes on Internet) has been
added to startup.csh.
777. A number of improvements were made to tar:
a. [NT] Tar would crash in its error message routine if it was asked
to copy a file to the archive that was open for writing by another
process. That's fixed.
b. [NT] Tar now normally rewinds the tape device at the start and
at the finish of the operation. This can be suppressed with the
new -N (no rewind) option.
c. Tar's messages about suppressing \r\n -> \n line end conversions on
binary files now appear only if the -v (verbose) option is selected.
d. If it encounters a file that can't be copied to the archive, tar now
just gives a warning and continues; it used to give a message and
just quit.
e. The spurious messages about garbled headers are suppressed for
empty tar files.
f. [NT] Failed attempts to set the blocksize on a tape device are now
treated as cause for a warning message, not a fatal error.
778. The sh_2_csh.csh script had some out-of-date references to an
sh-2-csh subdirectory. Because the hyphen isn't a legal character on
CD-ROM filesystem, that directory was renamed but the change wasn't
made to the script. Now it's correct.
779. [NT] The how2tar.txt and how2tar.wri files were added to the distribution
disks to explain how to get tar to work with a tape drive under NT.
780. The license.txt file was added to each of the .zip files on the demo
disks.
Known Bugs
1. A long-standing problem has been that if you tried to run certain apps
such as MAKE in the background (using & at the end of the line) or piped
into MORE, they would "hang" apparently for no reason until a keystroke
was pressed. The problem was that the OS/2 process completion logic was
requesting a semaphore in KBDCALLS.DLL that was already owned by any
process in that window that might be sleeping in a KbdCharIn call. Until
another keystroke was pressed, that semaphore was never released and the
background process was never allowed to cleanly exit.
This bug has been logged by IBM as APAR JR04161 and has been fixed in
a CSD 5050 for OS/2 1.3 with a new KBDCALLS.DLL. That CSD is available
on request from IBM or your local dealer. Alternately, the new DLL is
available on request from Hamilton Laboratories or can be downloaded from
the listings area in the 'hamilton' conference on Bix.
2. The keyboard editing logic only checks to see if the cursor's been moved
by a background process or thread when it reads the first keystroke. That
catches most situations, but if you begin typing a command and then some
background activity starts writing to the screen or moving the cursor,
the result can be a scrambled display.
3. The Microsoft OS/2 link editor shipped with MSC 5.1 can fail, reporting
error L1101, "invalid object module," if it is called with a very long
list of object files either directly by the C shell or even by a copy of
cmd.exe running as a child of the C shell. Packing some of the object
modules into a .lib file before linking overcomes the problem. More
rarely, it may report L1102, "unexpected end of file," even when a .lib
is used.
This problem has been traced by Microsoft's Online technical support
staff to a bug in Microsoft's C library routines used by the linker.
The C library can fail if the process has a maximum file handle
count above the system default of 20. OS/2 allows any particular process
to increase its maximum but not lower it; further, child processes
inherit their initial maximum count from their parents. The problem
then arises because csh.exe needs to be able to open lots of handles
(because you could spawn lots of threads or long pipelines) and sets
the maximum to 255 at initialization, which is inherited by the linker
and fails when the linker calls the C library.
A new version of the linker, using a corrected C library, is now
shipping with Microsoft C 6.00 and 6.00a and does fix the problem.
But if you must use the MSC 5.1 linker, you can use the patchlnk.exe
utility to "zap" the particular instruction byte that is in error from
a JLE to a JB. Type patchlnk -h for more info.
Alternately, we've added a special (ugly) -Z option to csh.exe that
tells it _not_ to boost its maximum file handle count. To use this
option, you _must_ invoke csh.exe -Z in a separate window, directly from
Start Programs; for the reasons above, it won't work if run as a child of a
normal invocation of csh.exe. Be aware, though, that with only 20 handles,
you may find it won't let you run some long pipelines, etc., you might
otherwise be able to.
4. Under OS/2 releases 1.x, the C shell is not able to spawn applications
to which you have execute, but not read privilege. This really applies
only to people using network servers since the FAT and HPFS filesystems
don't provide any way of marking a file this way. The solution is make
the file readable.
The C shell does not use DosQAppType to determine whether a given .exe
file is a full screen, text windowable or PM graphics application due
to a bug in the kernel in releases prior to OS/2 2.0. If QAppType
is called from one thread while another is sleeping in a filesystem-
related call, e.g., DosFindNext, QAppType can cause the other call
to return garbage because it apparently trashes the per-process name
cache the kernel maintains. The solution the C shell uses is to go out
and read the .exe itself to look at the tag bits. For this reason, if
it can't read it, it can't spawn it.
5. Under IBM OS/2 EE 1.2 CSD level WR04098 and Microsoft OS/2 1.21 with
LAN Manager 2.0 and possibly other builds issued around year-end, 1990,
the shell and utilities are occasionally unable to list all the contents
of a directory. The problem is a bug in the OS/2 networking code, not
the C shell and occurs only if (1) the directory is read over a network,
(2) directory entries are read (as the C shell does for higher performance)
in blocks, rather than one at a time and (3) the total number of characters
in all the filenames in the directory happens to be just right. In all
cases observed, adding or deleting any arbitrary entry in the directory
makes the problem go away.
IBM has developed a fix. If you're an IBM customer, you can request a
copy of the new netwksta.sys file being distributed as APAR IC02287 by
calling 1-800-237-5511 or by contacting your local IBM representative.
You can also download it from the listings area of my 'hamilton' vendor
support conference on Bix or contact me directly and I'll mail you
a copy.
In the meantime, you can work around this problem by defining and
setting the environmental variable NETWORKBUG = 1.
6. If you install the C shell as the PROTSHELL and select View Icon in
Group-Main, the default OS/2 icon will be shown, not the C shell's
icon. But clicking on it, the C shell that starts up will have the
correct icon when it runs. We consider this a bug in OS/2; IBM claims
this is how it's supposed to work.
7. Under the OS/2 2.0 6.167 beta and LA builds, the C shell is not able to
change its title bar and icon even if it's installed as the PROTSHELL.
Here again, the problem is OS/2 2.0, not the C shell. This problem is
fixed under the 6.304E, GA and later releases; change the OS2_SHELL line
in your config.sys to read:
set OS2_SHELL=c:\hamilton\bin\csh.exe -L
(filling in the appropriate pathname).
8. More.exe and moreh.exe fail if you have an 8514 display under OS/2 2.0
builds prior to 6.307. IBM has issued a new display.dll to fix the
problem. It can be downloaded from the listings area in the hamilton
conference on Bix or requested directly from us.
Thank you for using Hamilton C shell.
Douglas A. Hamilton
June 16, 1994
Hamilton Laboratories
13 Old Farm Road
Wayland, MA 01778-3117
U.S.A.
phone: 508-358-5715
FAX: 508-358-1113
BIX Network: hamilton
CompuServe: 70034,2025
MCI Mail: 389-0321
Telex: 6503890321
Internet: 3890321@mcimail.com or hamilton@bix.com