Amazing is right!! I had never noticed this in fifteen years using
Bruker systems. Bruker must be aware of this bug, since our "new"
ADAKOS-SCSI 931118.A gives an error message as follows:
*DELOC\OC\OC16*.*<ret>
DELOC16* <=== SPECIFICATION ERROR
*
We are, I believe, one of the few institutions that purchased
AC's late enough to have SCSI hard disk drives, and therefore
also have ADAKOS-SCSI. I don't know if a bunch of other problems
in ADAKOS 890201.0 have been fixed in ADAKOS-SCSI or not, but
if this version works with older disks, maybe you could upgrade
to it.
I noticed also that the ADAKOS problem does not occur inside of
DISNMR (we use DISR91), where:
1.DELOC[OC]OC16*.*<ret> ? 1.
gets the informative error message ?, and doesn't do anything. If
only the wildcard ? (and the COP command) would work in DISNMR!!
We have had a somewhat similar problem for some
time with DISR91, where the following commands:
WR TESTDATA.001<ret>
USR FASTU<ret>
gets confused when the first <ret> is not issued (either the
student doesn't type hard enough, or thru a keyboard fault. The
second command, by the way, is a FASTRAN command to transfer
the data to a PC. If the first <ret> is not issued, then
the command looks like the following:
WR TESTDATA.001USR FASTU<ret>
which DISR91, in its loving way, doesn't give back the terribly
informative and preferred ?, but instead interprets as:
WR FASTU<ret>
and bye-bye FASTRAN transfers until FASTU program is corrected.
If students complain that a file they thought they saved doesn't
seem to be there, this is a good possibility (where the data
was saved to the second half of whatever two-word command followed
the WR).
Life is more interesting with an ASPECT, isn't it!?!
Charlie Fry
Director-Magnetic Resonance Facility
Department of Chemistry
University of Wisconsin
(608)262-3182
fry@chem.wisc.edu