Computer Services
Stanton/Wilmington Campus
Shelly Cashman CAI Programs
Ah, whenever I hear "Shelly Cashman" spoken, it brings back horrible memories
of taking COBOL in 1981 using a Shelly Cashman textbook. Looks like these
guys are still going.
So, they haunt me still. Now, I need to install their cruft to our
network so new students may join the eternal Shelly Cashman fan club.
Table of Contents for This Page
NOTE:Additional confidential information for DTCC admins
is in the file /m/admin/docs/ctm.txt on apache. This file includes install
location and CTM supervisor ID and password.
User Run Instructions
Reference Web Sites
Permission requirements
- Documented in ctm\testbank\readme.wri file on install CD. Also see
observation notes below.
Observations
- Engine and testbanks installed separately
- Testbank should be installed into engine directory
- Doesn't install stuff in any system directories or make unusuall registry
changes (YEAH!). Might be able to install it once on network, and not have
to do work at each station (DOUBLE YEAH!). The README docs in
ctm\testbank on the CD are GREAT! I wish all software vendors would
document what is required security and install wise this well.
- FAQ claims that access rights docs are in a README file in the test manager
engine directory. It's not. It's ctm\testbank directory. Read this file
carefully. In addition to access rights, it documents what files should
be backed up on a regular basis. We can do a cron job to park them into
a different subdir for a few generations. Not like this is a ton of data.
Backup tapes can get the larger picture when they are done too.
- Supervisor password should be changed
- share command that install tells you to put into autoexec.bat is N/A to
NT. Don't do it.
- Docs say you should run a setup program from each testbank directory
(e.g. off97.exe in off97 directory) to set up icons. Let's hope that's all
it does (we can do that automatically)
- Since some files need to be world-writable, it's best to do some
security thru obscurity by parking stuff down two levels with upper
levels not having read-access to directory. This prevents someone from
wandering around and trying stuff. Those determined can still do
something nasty like zero the files. :-(
- Office 97 Test Manager run via:
STARTUP.EXE Off97
Install instructions
- Refer to file /m/admin/docs/ctm.txt for path info and passwords
- Login as Administrator on NT domain
- Map G: to \\apache\nt as your own (admin-grouped) username
- Dive into CTM directory on CD
- Run CDSETUP, install engine and testbank to correct path
- chmod proper files (see ctm.txt file for details)
- Create icon to run program (see Launch program below)
Launch Program
None needed. Just create proper icon to launch program and place in the
global menu at /dos/nt/profiles/Start Menu/programs
In luck, this thing will run with standard NT install, no workstation
modifications necessary. (Well, *did* have to change standard install
to ensure winspool.exe is world-readable in system32 directory).
I copied directory to server. Only caveat I have is that there can't
be any path components to the start.exe program with spaces in it. Just
use dos legal names. Then just create an icon to start.exe...
Last page update: 18 August 1998
Official
URL for this page:
http://www.stanton.dtcc.edu/stanton/cs/admin/nt/notes/sc.html
Page Maintained by: Ken
Weaverling