Conference kernel::csguk_systems

$ if f$mode() .nes. "INTERACTIVE" then exit
$!
$ set control_y
$ on control_y then goto end
$ on error then goto end
$!
$ word = p1
$ if p1 .eqs. "" then prompt/inter="" "Enter a word to spell. " word
$ if word .eqs. "" then goto end
$ open/write file spell.tmp 
$ write file word
$ close file
$ spell spell.tmp


$ open/read file spell.tmp
$ read file word1
$ close file
$ write sys$output "The correct spelling for your word is ",word1
$ delete/erase spell.tmp;*
$!
$end:
$ exit

    This toolshed,is it where a gardener would keep his tools?
    Would an uphill gardener keep his tools here too?????
    
    
    
    
    KM

    Choose your words carefully - "a repositry for useful tools" could
    easily be misunderstood by those not as worldly wise as we.

    
    
    Well........as an ex crabby you should know Mr Plank(T5.5).
    
    
    
    
    Ex Roughy-toughy Submariner.
        

    Mr edmunds - point of order.I've heard you use a loofah with your
    soap.
    
    
    
    km
    

    
    
    
    Kev mate...
    
    
    
    They dont sell loofah's in Next.
    
    
    
    
    Rocky-man-at-next
    

    Steve,
    
    Loofahs (plural) doesn't need an apostrophe.
    
    I heard Submariners got to be roughy-toughy by excessive association
    with Rum-Bum-and Baccy. Is this something you'd like to tell us
    about?
    
    
    Steve.

	Hello All,
		   The TSC in Munich have created a Crash_Tool that assists
	with bug-check analysis. To find out it's capabilities try running
	the following command-file after logging into Lookin. It will show
	how a stack should be interpreted, how S0 and P1 space is formatted.
		I have a hardcopy of the output from this command file if
	anyone wants a look. There is a copy of this command file in my
	login account on Lookin.
              
	Alan.

      
$ set proc/priv=bypass
$ set def disk$dumps:[000000.tools.crash_tool]
$ !
$ analyse/crash sys$system      ! do sh stack to see what SDA thinks
sh stack
exit
$ !
$ @login			! invoke crash_tool login
$ @help				! invoke crash_tool help
$ !
$ sda_max_v5			! set up V5 symbols
$ !
$ ana_cra sys$system		! analyse crash using crash_tool
sh stack			!   sh stack
@s0_v5				!   format S0 space
@p1_v5				!   format P1 space
exit
$ !
$ set def sys$login
$exit

From:	KERNEL::HORSNELL "YOU CAN USE ME AS AN ARMCHAIR ANYTIME M/F  09-Mar-1989 1514"  9-MAR-1989 15:15
To:	@POST:SYSTEMS
Subj:	duff version of dsaerr

                  DSAERR PROBLEMS.....


Hello fellow devices,

       Over the last couple of days myself and Alan James have been talking
to Frank Chaffin about problems with our new version of dsa303.exe.

       You may of noticed when you run dsa303 in dt the header banner you
get is t3.03-3............and guess what the "T" stands for test...

       As Frank Chaffin has explained below,the latest version is dsaerr
v3.03...

       I have put this new version into rdc$common,please can you use this
from now on and let me or Alan know if you get any problems......




P.s.  DT has now been amended to point to this new version....


cheers Daryl

********************************************************************************
From:	USWAV3::CHAFFIN      "Frank C. Chaffin"  3-MAR-1989 02:52
To:	KERNEL::HORSNELL
Subj:	RE: dsaerr t3.03-3 query

Daryl,

The "f" means that the block is in the FCT (Format Control Table). You may
also see an "r" which indicated the block was a RBN.

The version of DSAerr that you have is out of date,  KERNAL::JAMES just
picked up the latest and greatest about 10 days ago.  I also sent him
a special version (smaller) you may be interested in.  In any event you
can always get the latest ang greatest from:

USWAV3::USER1:[CHAFFIN.PUBLIC]DSAERR.*

Suggest you copy the .obj file and link it on the target system. Use the
$LINK/NOTRACE commmand, it makes a smaller inamge.

I am always open to comment and suggestions.

Regards,