DIARY OF COMPUTER OPERATIONS/PROCEDURE NOTES

(Handwritten log maintained for repairs/service prior to 1/13/93.)

(Separate diary for maintenance activities and other than operational notes are in U:\SYSAD\DIARY)

Computer system error logs:

Open (in WordPerfect) the error log "f:\ezarc\arch$svr.log" file for VOL1 (and SYS) files for back-up recordings;

open the "f:\system\sys$log.err" file for system error recordings.

1/4/94	Trained new intern, Mike Senske, on computer network/use.

1/5/94	X?	Tested Chris' workstation re PCG. It did load with WP open, however, very slowly; left black screen at first. Same response with Pat loggin. Changed Chris' command line for PCG to G:\PCG4\PCG4dian.pif for now. Watch to see what happens in future. Shouldn't have to keep changing the PIF file (for speed issue).

Corrected Chris' set-up for using Lotus so she can now utilize smarticons. Refer to diary.ops for instructions.

1/5/94	Pat now also experiences locked loading of PCG when WP is open (having PIF file of PCG4s.pif). Changed execution to another pif file (original) to test.

1/10/94	Chris and Pat having trouble with PCG again. While attempting to modify (insert) columns in reports, we get thrown out of PCG after a msg about not enf memory.

1/18/94	Changed Pat's PIF to "s" for now til trouble starts again.

Changed Chris's PIF to (?)

Reported to ComputerEase when Rob called (re upgrading machines). He took some information and will discuss with Stephanie again.

1/24/94	X	On Sunday a.m., 1/23/94 the computer's UPS battery came on (for the first time since the dedicated outlet). The power returned in one minute, however, the UPS required 22 minutes to re-charge.

1/27/94	X	Set up new intern (Mike Sensky) as user. Copied Phung's files to Mike's u: drive AND ALSO COPIED THEM TO U:\INTERN AS TEMPORARY BACKUP. Deleted Phung as user. Delete the U:\intern files temporarily. Delete prior to Mike's leaving. Then when Mike is replaced, copy Mike's files to the u:\Intern drive before creating new user and deleting Mike.

X	Battery power came on again at 10:22 am., power returned immediately. Came on three times during the day, however, the downtown area was experiencing electrical problems due to freezing rain storm. Disregard for now.

Cleaned out salvageable deleted files (via Salvage). (Saved files from November 1, 1994 through today.)

X	Chris requests that if the Foundation "sells" any computer to replace it, may she purchase it?

X	Chris reported a problem with her A: drive that has been happening for quite some time. When in WP, if she inadvertently clicks on a: when opening or saving a file, if there is no disk in a:, the message appears "Cannot Read A: drive; cancel or retry"; when she clicks on cancel, or when she inserts disk and clicks on retry, the computer brings up large red screen with blue lettering on it; sometimes readable, sometimes garbled symbols. Is the a: drive bad?? (If she inserts disk in A: before clicking on a: drive in directories, it is fine. File manager can see a: fine; DOS can read a: fine.) Left msg at Computer Bay for service tech to call us.

1/28/94	Rob asked for Pat's and Chris' info on their permanent swap files and config.sys and autoexec.bat files. Reported this info to Rob via fax. (Perm swap file seen via Ctrl panel, 386 enhanced, virtual mem.) See repair file for copy of this info sent to Rob.

2/2/94	Followed up with ComputerBay re Chris' a: drive. Philip offered the following advice:

Test the a: drive isolated from network. Re-boot, run windows from c: and use program mgr to click on a: drive and see what happens.

If a: can be accessed by Program manager and Dos, rule out that it is a drive problem. Could be local Windows files; try re-loading Windows to fix problem. Then Do search for apps on network.

*Logged in as Pat on Chris' computer, (Ctrl C to break from login onto network); loaded windows from c:; used Program Mgr, file mgr, to click on a: without diskette in place; OK.

Logged out and went back in via network, loaded WP, clicked on a: from file open, OK! Problem seems inconsistent. Asked Chris to let me know when it happens again.

[Philip suggested Norton's Disk Doctor program - very good disk problem detector.]

2/4/94	Christina, Kelly and Dianne had problems in early morning. Dianne locked while loading PCGifts; Chris locked while in tables in WordPerfect (only program open) and had selected text to cut, system error came on fast and then retry or cancel, took her out of WP; Kelly experiences lockups when he has been in CompuServe and does not close systematically (closing each menu) and then alt tabs to WP.

Dianne Ctrl Alt Del to reboot and then was fine.

Kelly knows the sequence that preceeds the wincim error and will avoid it.

Chris rebooted and was ok.

2/6/94	Attempted to install Aldus Pagemaker 5.0 (upgrade). Followed instructions in Getting Started Manual. Would not load; stopped at first file, saying "Error While Installing File; Cannot access file (file name not readable); Retry, Cancel installation; Skip this file; Help."

According to manual, set buffers on config.sys at 30. (Were 20 before.) Manual says to shut off virus protection software; none resident, to my knowledge. Will call PageMaker or Rob at CE on Monday.

2/7/94	Spoke w/Rob at CE. He checked the autoexec.bat file and config.sys files. Took out smartdrive on autoexec file (rem); tried various combinations. Rob called Aldus Pagemaker for info.

2/8/94	The following information/assistance was given to Rob from Aldus. The instructions for installing onto a network included in the package were far from complete. Aldus faxed documents to Rob and I printed files from the Aldus upgrade disks for more info.

Documents referenced:

.ALDUS Fax-YI 2/9/94 (Aldus faxed to Rob)

.NETWORK.WRI file (printed out from PM5 directory) contains specific instructions for installing PageMaker 5.0 onto network, pg. 3. Option selected to install was "Install on network server".

.SETUP.WRI file from aldus\pm5 directory

.READTHIS.TXT file from aldus\pm5 directory

-Changed Pat's config.sys initially to 50 buffers (was 20) per recommendation on READTHIS.TXT. (Installed from Chris' computer. Not necssary after all.) Changed config.sys back to 20 buffers.

-Used sysedit command (in program mgr, file, run, "sysedit") to edit autoexec.bat and win.ini files:

Win.ini file

Under [Aldus], inserted a semicolon (;) before the line that reads PM4LangDir=USENGLSH.

Confirmed line: Netaldus directory=G:\ALDUS.

Autoexec.bat files: Temp directory changed to c:\windows\temp

Chris' temp directory was set to u:

Leslie's was set for c:\dos

-Installed PageMaker 5.0 onto network (from Chris' workstation) on 2/9/94.

-Completion of installation takes place on each users workstation; need to go through "Setup" process (see SETUP.WRI docment). Since Chris and Leslie are only users, set them up only. Removed 4.0 icons from all other workstations. If emergency exists, we could re-install 4.0 in future. Probably would just have to revise the Win.ini file and then load 4.0 from g:\.

2/10/94

Rob: HELP!

Chris and Leslie were at first able to log into PageMaker 5.0 this morning. Now they both get message when logging into PageMaker 5.0:

" Cannot Run PageMaker 5.0. ?PM5RES.RSL <PM5 Resource file not found> " I was able to find the file on g:\aldus\usenglsh\pm5user.

I phoned Aldus regarding this matter. "Vince" requested we do the following:

The file date and size was confirmed. Should be OK.

THEREFORE,

1. Delete entire [Aldus] section from each workstation's Win.Ini file.

2. Delete PageMaker 5.0 icons from Program Manager on each workstation.

3. Remove Aldus from file server. Re- install using the instructions for installing to a network (a:\aldus a:\net\net.ctl). When it asks where to install it, take the default of g:\netaldus. (IE, use orthodox installation procedure; don't create different directory name.)

4. Re-install each user using the netinst.exe command. When it asks where to install it, tell it c:\aldus (best if on local drive; at minimum must be in different drive letter). (We had installed the user info to the same drive as the network program files. Not good.)

I won't do this without ya. Do I have to "uninstall" from file server, or just delete the directory?? Call when you can.

Pat

Bradley Foundation

291-9915

ALSO:

Should I flag the program files as read only? (See NETWORK.WRI file.) DO THIS AFTER RUNNING WINBUMPS.

Want to install on my computer (for support purposes). Won't install. " System Error. Sharing violation on drive u: (or upside down h) ". AFTER RUNNING WINBUMPS CAN USE NETINST.EXE FOR ANY WORKSTATION. ONLY TWO USERS WILL BE ALLOWED ACCESS AT ANY ONE TIME.

Do you remember how we handled the error message when installing Postscript printer drivers: " SEE SYSTEM ADMINISTRATOR c:\windows\control.exe CONTINUE 4646.4133 "? (Need to install for Les) (THIS SHOULD NOT HAPPEN AGAIN AFTER RE- INSTALL.)

Faxed document says to put win.ini file back (remove the semicolon) after using the setup. Should I?? I tried it with Chris' and it did not make a difference when trying to load; receive same error message.

2/11/94	Rob came out on site around 11:30 am to remove PageMaker 5.0 and start over. He discussed particular instructions with Aldus and was able to find out more information relative to the installation procedure. Finished at 2:00 pm; Chris is up and running. No one else can log in until PageMaker provides us with a password to run the winbumps.exe program for networking/licensing. Chris also can not log into PageMaker 5.0 at a different workstation until the winbumps program is run.

Answers to prior questions of 2/10 are typed in caps next to the questions.

FYI : Aldus PageMaker 5.0 now resides on f:\netaldus directory (originally installed to g:\apps\aldus).

By noon, 12/12, Aldus PageMaker will call with the password instruction for running winbumps.exe program. Rob gave these instructions to me on 2/10:

1. Go to each workstation and remove the Aldus section from Win.ini file (via sysedit) (and icons from prog mgr).

2. Run (once - probably from Chris' workstation) program called Winbumps.exe as instructed on pg. "6 of 13" on Rob's fax'd document. Will need the password from Aldus for this.

3. Then run Netinst.exe (from netaldus\usenglsh\pm5user directory), logged into computer with user name. Enter Bradley Foundation as user name; OK to put on C: like Aldus recommends. Run on each computer, but only two users will be allowed access at one time.

3/3/94	Chris began using the new PIF file for PCG developed by MicroEdge. She will use it for a while to determine if it is effective. Since Chris uses WP much more than PCG, we should find the one that is ulitmately best for her WP.

3/4/94	X	Pat tried using the new PC-Gifts PIF file (PCG.PIF) created by MicroEdge for testing purposes. The results were as follows:

If loaded PCGifts first, PCGifts operates well; WP somewhat slow to open and dramatically slow to operate. If Alt-Tab over to PCGifts and close it, then WP speeds up to normal (without reloading).

If WP is loaded first, speed is normal; if PCGifts is then loaded, WP slows down dramatically. If Alt-Tab to close PCGifts, then WP speeds up back to normal (without reloading).

(faxed this info to Stephanie)

3/10/94	A guest was in (Amber Engel) using the computer and had logged in as "guest". Problems arised immediately because access was allowed not only to all programs, but also Bradley common area (h: drive). Used TEMP login name instead; this increased control of access to only program manager, WordPerfect, the a:,c:,f:,g:,u:,w:,x:,y:,z: drives. \

1: Would prefer to see only a, c and u drives.

2: Also, access is not permitted to Lotus or PageMaker at this time. Can this be changed easily?

3: Different results with each workstation when temp logs in. (Windows error messages, etc.) Why?

Will discuss with Rob at convenient time.

7/2/93 source: Rob of ComputerEase

Copying files from one workstation harddrive to another utilizing the network:

For example, copying the Windows files of a good-working workstation to a workstation having Windows-related problems.

Login as supervisor. Work from pure DOS (not thru Windows).

To copy the (good) Windows files from a harddrive to the network (f:/), first make a directory on the network:

f:\cd pat

md Windows

cd windows

xcopy c:\windows\*.* /s (will copy to current drive "f")

Now, working at the target workstation, copy the network files to the target workstation harddrive. First move the current windows to a temporary directory ("old") onto network:

f:\pat

md Windows.old

cd windows.old

xcopy c:\windows /s f:\pat\windows.old

Then delete the all files in the current windows directory of the target workstation:

c:

cd\windows

del *.* (yes to question asked)

delete (and subdirectories under windows)

Copy the good windows files from the network to the target workstation:

xcopy f:\pat\windows c:\windows

Delete the f:\pat\windows directory from the network. Retain f:\pat\windows.old as a backup while evaluating the operations of the new directory over time. Delete at later date.

SETTING UP USERS TO USE LOTUS SMARTICONS

(The files that are required on C:\ can be found on G:\123W if necessary to copy via File Manager.)

First, verify that the following *.ini files reside on C:\windows for the user:

123W.ini

lsicon.ini

lgicon.ini

Next, the user must have on the C: drive, preferably in Windows directory, two sub-directories associated with Lotus. These are [SHEETICO] and [GRAPHICO].

The command line of the Program Item Properties (viewed with Ctrl Enter while icon is highlighed) is G:\123W\123W.exe. (No working directory is necessary.)

The 123.INI file located on C:\Windows may need to be updated to instruct Lotus to look onto C: drive for icons. Load Notepad; pull up the 123W.ini file from C:\Windows. Replace the information in the [DIRECTORIES] section to read as follows:

[DIRECTORIES]

personal=C:\WINDOWS

addin=G:\123W\addins

install=G:\123W

1/5/94

4/25/94	Ordered Canon BJC-600 color bubblejet printer from Office Depot via 800 number for next day delivery. Confusion about whether or not ink cartridges come with printer; ordered separately to be safe. (Chris picked up two colors at local Office Depot store; two were ordered from 800 number.)

Christina purchased at (Egghead Software) Harvard Graphics and PrintCache. Color printer and HG are for creating graphs and piecharts etc for annual report. PC is specifically for speeding up production by freeing up the computer while printer is printing. PC recommended by Scott Liddle, Canon rep.

4/26/94	Printer arrived; ink cartridges did come with product. Extra set here. Chris installed onto her computer all products. Pat completed registration cards and assisted with installations. Invoices/ receipts given to Leslie because the items were on Mr. Joyce's Amer Express card.

Installed TrueType fonts (from Canon diskette) on H:\ttfonts for everyone to use. To install to a workstation, since we all print from c:\windows, instructions were provided to staff on installing the fonts onto their workstations.

4/28/94	Ordered new HP Laserjet 4+ and cable from Dave Keup at Computer Bay. Should be delivered by UPS or RPS next week. Take new printer and replace HP4 in copy room. Give copyroom printer to Dianne. (Need to transfer paper tray, memory upgrade, and JetDirect network card to new printer.) Left msg for Steph at CB re the transfer of parts.

"	Exchanged printers between Bill S. and Acctg Intern/Ann. (Bill's had a network card in it; required by Intern and Ann M.) An extra network jack already existed at Intern's desk. (Borrowed Hillel's network HUB connection for the printer!!)

On 4/29/94, installation of networked printer in Acctg Office was done. Because it was being transformed from being local printer to network printer, several steps had to be taken. (A network card was already existing on the printer.)

* A new printer needs to be added to the Novell Netware via PCONSOLE. Several steps here: check each option carefully within Print Queue Information and Printer Server Information.

** Per Steph of CE, in PCONSOLE, Printer Server Info, PSBRADLEY, Print Server Configuration, Printer Configuration, we should not select Remote Other/Unknown as "Type". However, HP JetDirect Sofware instructions said it should be Remote Other/Unknown. We operated with the HP instructions.

* To "re-boot" the PCONSOLE, the print server must be unloaded and then loaded at the file server. (Notify all users to not print please.) At the colon type: unload pserver. When it finishes unloading, then type at colon: load pserver PS_BRADLEY. PASSWORD FOR PSERVER MUST BE KNOWN TO LOAD.

* In Prog Mgr, Control Panel, PRINTERS on the computer workstation, delete (if necessary) the printer currently hooked up to the port desired for the new printer. Add the new printer via ADD, highlight correct printer name, INSTALL (from c:\windows when prompted for a:\ diskette); CONNECT, NETWORK, etc. Check the setup too.

* The printer does not require a parallel or serial cable running from it to the computer, but rather a network cable running from the network card (the jack is located on the back of the printer near the serial port) to a network connection/jack on the wall. Activate the network connection (so the printer can speak to the file server) on the network HUB (near the file server). Take printer off-line and configure it (HP II, IID, III or IIID) referring to the printer's "Network Printer Interface for Novell Networks" manual. (The instruction to follow will have to do with "I/O optional".)

*Cold re-boot the computer and it should be able to print to the networked printer.

**We had difficulty getting all network users to print correctly on Friday, but on Monday all was well. Cold- reboot of all workstations seemed to help.

4/28/94	Teleport installed extra network jack by Christina (reception area) to move networked printer to her desk. (Will remain a network printer.) Two network jacks then will be available at the consultant area.

Teleport made 4 new network cords (one for Intern's printer and others for future use). Two short, and two 20-ft long.

5/2/94	Ordered additional HUB for the network from ComputerBay. All HUB connections are taken, in fact, need additional one right now.

5/13/94	Rob came to install the HUB; incorrect cable was with the new equipment, someone delivered correct cable; now have 7 HUB connections available for additional equipment.

Rob also installed new HP IV+ printer. The bottom paper cassette was not adaptable from older HP IV to newer one. Therefore, installed the IV+ to Dianne's office temporarily. Ordered cassette from CB (David Keup) 5/13/94. Should be in a two-three weeks. Will then exchange the copy room printer with Dianne's printer (placing IV+ in copy room).

5/19/94	Rob (CE) came to install video accelator card and 368Max v. 7 to Kelly's workstation to try to improve on the speed of the computer. Little result at this time; Pat will go through manuals to see in anymore adjusting can be done.

5/31/94	Scheduled appointment for CB to come and clean printers: Bill's, Mike S.'s, Copy room, and Leslie's.

5/26/94	Worked with Chris to clean up her hard drive. Chkdsk showed little space left on drive. Searched (with File Mgr) for and deleted a couple unnecessary hidden files. Deleted .temp files. Recovered quite a bit of space. Recorded in computer documentation file.

5/31/94	Discussed with Rob at CE attempt to clean up Les' harddrive on 5/27. Some problems with large hidden file (has to do with large permanent swap file). Ran a chkdsk /f to recover lost allocation chains. Seemed to work OK. Deleted files in temp directory. Recovered a little bit of space; not much there. Also saw ".old" copy of windows. Need to test that to see if it's really needed anymore. Per Rob, change name of the "old" directory and run the programs for a while to see if any problems are encountered. If not, delete the old windows. Recorded in computer documentation file.

Also discussed attempt to set restrictions of access on Novell for Peachtree Accounting. I had tried to create a new user (Mike2) and new group (Accouting) to try to give access to limited areas on network. Was unsuccessful at first glance. Can't really set command that gives access to everything "except" Peachtree; Rob will have to do this by re-arranging accesses that group "Everyone" has and not including Peachtree. Will probably set up a special group for those that use Peachtree. Will do this when paper cassette tray comes in for new printer.

6/2/94	Password was initiated for access to the Bradley file in Peachtree Accounting. Any user can open the software, however, the password allows access into the data file for "Bradley". Each user can be given a different password to allow access to different areas of Peachtree. In future, will develop more secure system with Novell by allowing only accounting personnel to access the Peachtree software in addition to having a password on the data file.

6/3/94	Mike Senske reported a problem with a Lotus file (RET-WKST.WK3) wherein what he previewed and printed was not the same at what he saw on the screen (different years). He needed to make changes to the current year, which he could print, but not see on the screen. Since he had just made changes the day before that were fine, I restored his Lotus document using Ezarc and the back-up tape from the night before. All was fine; however, he renamed it and now reports the changes being made are saved in both versions of the document. I asked him to talk with Pat since she is more familiar with Lotus.	(YE)

**This Lotus file that Mike was working in contained multiple worksheets. While he viewed the one worksheet which appeared on the screen, the other printed (because of prior print command saved in the file's memory). The way to distinguish the worksheets in Lotus is by their cell names. If a cell name is A:A1, the user is in the first (or the only) worksheet, cell A1, of the document (file) name. If the cell has a name of B:A2, the user is in cell A2 of the second (B) worksheet.

7/18/94	Rob of ComputerEase came for several maintenance projects. The following items were completed:

-Checked Aldus PakeMaker files for flagging read only. Removed old version of PageMaker. (f:apps\PM4.old and aldus.old)

-Protected Peachtree software from being loaded by anyone other than accounting staff.

-Worked with Chris on stalled printing with PC-Gifts. Print Cache may or may not have been the problem. Chris' workstation had 0 for timeout in printer control. Should be at least 10. The printer would not print out the document when the setting was at 0.(It could not determine where the end of the document was and timeout controls the printer starting point according to the end of the document.) CHRIS/PAT NEED TO CALL PRINTCACHE AND CHECK ON AVAILABLE PRINTER OPTIONS RATHER THAN GENERIC.

ITEMS TO COMPLETE ON ROB'S NEXT RETURN:

-Rearrange workgroups. (Pat - Think through if separate workgroups are really necessary and assign on paper before Rob arrives.) (ie Sys:apps too broad for "Everyone")

-PCG PIF files (gave Rob copies of info on PIFs).

-Exchange copy room printer with Dianne's and install papercassette on new (copyroom) printer.

-Remove "tests" from Yvonne's C:\ and check Leslie's c:\. Discuss the variable items to look for whan deleting software programs and how to properly delete them. (rather than using an "uninstall" program)

-Meet with Yvonne/Mike S. on security issues using Novell features.

-Diagnose Chris' a:\ problem. Must be a windows setting somewhere. Rob will call Windows.

-"Temp" login name needs some refining (or some explanation). Logging in at different workstations produces different results with availability of software.

7/25/94	Purged entire network of old deleted files (Salvage; sorted files by date; retained all July 1994 documents unless 0 bytes.) Purged both Sys and Vol1. (This process took over 3 hours for about 3 months worth of documents! Yvonne will do monthly from now on.)

7/27/94	Received and installed new 15" monitor onto Chris' workstation; moved her (old) monitor to library; moved library monitor to file server (old monochrome monitor on server burned out w/o 7/18/94). After installing (transferred from Chris') monitor onto library computer, the computer could not find file server or even load windows from c:\. Autoexec.bat file had incorrect path (including statment to look at f:\apps\windows. Corrected autoexec.bat and then it was ok.

7/28/94	Rob came to work on several outstanding maintenance items: Exchanged copy room printer (LJ4) with Dianne's (LJ4+); rearranged workgroups, creating one for the interns and temp as one w/more limited access; removed tests from Yvonne's harddrive and cleaned up Les' harddrive; explained how to uninstall test programs; corrected Chris' a: problem with an instruction line in one of her *.ini files (sysedit); agreed to address PIF problem again after installing the upgrade of WP (since WP is affecting it); agreed that Novell security devices that we currently do not use are not needed for our size office and will address security when outside communications happens.

Entered instructions on deleting old programs from harddrive into Diary.ops.

8/24/94	Today the copy room printer stopped printing. Specifically, print commands sent from software appeared normal however the printer did not print the documents.

RESOURCES CHECKED:

1. PCONSOLE, print queue info, current print job entries, showed that the documents had in fact been sent to the printer and were ready to print. Since the status reported ready but waiting for a pserver, network was ok.

2. Printer settings in control panel, printers, network were checked; OK

3. Manual test print from the printer was OK (and all settings on printer checked manually were ok).

Because the network config (pconsole) was OK and the printer was OK (self-test and checks on settings), the remaining piece is pserver. Somehow the connection between the printer and the network became corrupt (ie the pserver). This can happen with static, or something brushing against the server, etc. Turned power off of PRINTER and turned it back on. Documents which were waiting to print in print queue came out of printer and all subsequent documents printed fine. (Support from CE - Steph - 5 minutes)

8/26/94-	The back-up tapedrive unit on file server was flashing,

8/30/94	indicating there was a problem. Attempted to list the tape, unsuccessfully. Also could not format or initialize the tape. Error message appeared that the tape was in unreadable condition, or words to that effect. Phoned Steph at CE. Suggested we clean the tapedrive unit with a cleaning tape. We did not have one so she mailed one. Yvonne tried to clean the tape (per Steph's instructions of inserting and removing it about 15-20 times). Tapedrive still did not work. At Steph's suggestion, the next thing to try is to down the file server and put it back up. Sometimes the server and backup unit stop communicating, presumably because of all the flow of traffic on the system built up over time. Yvonne downed the server and all was OK with the backup unit. Yvonne also requested Steph order us a tapedrive cleaning tape.

8/29/94, by Yvonne while Pat's on vacation:

1)	Dianne's curser in WordPerfect was so small she could hardly see it. Problem resolved by selecting Courier W1 font size 12 instead of 1 in initial font of select printer.

2)	Dianne reported she couldn't get out of the centering mode; we selected left margin from the "ruler" choice and all was well again.

3)	Kim couldn't get the library software open. Using password of "books" we got to a screen with a menu. All is well.

4)	Kim couldn't get into the system at all; I used syscon to re-assign a password for her (pizza). She can now get into the system.

5)	I cleaned the tape back-up using the cleaning cartridge Stephanie sent us (18 times). The tape still would not re-wind. Tonight I will turn the tape drive off, down the file server, turn the tape drive back on and reload the file server to see if the system will read the tape drive and re-wind the tape. Further info to follow.

It worked! The back-up tape registered fine for tonight's back-up.

9/13/94	Moved all of Mike Senske's files to Jeff Johns. (will keep Mike in system for a while longer before removing entirely.)

9/20/94	Rob came to install a trial version of Office Logic onto our network. After installing it, the version reported that it had already expired, so Rob set the date at the file server to one month prior (8/20/94) to allow us one month for testing the product. This was a problem immediately for PC-Gifts and Peachtree, both of which use the date and time from the server as it processes information on a daily basis. I reported to Rob immediately the problem and I reversed the procedure (set date) on the server to today's date. Jeff's Peachtree files were apparently corrupted as he noticed that September data had moved into the August period and September period was now empty. While attempting to post/unpost August (or September?) he received the following message: Pre-Image file open error in file Journal.dat. This may be caused by lack of disk space. Please clear some space and try again. If that does not work, run Integrity Check. Retry, Cancel. We clicked on retry and the remaining data posted/unposted. We then ran the integrity check procedure; "reindex files, Journal, OK". It occasionally asked questions regarding placing certain data into retained earnings and Peachtree recommended that we click on yes so we did. Jeff reported at first that the September data was now back in September period. However, when he chekced the August period, the September data was in there, too. At this point, the data was backed up via Peachtree and a Peachtree Repair function was initialized. If this doesn't work, attempt to run a data synchronization test (suggested by Peachtree's message at the end of the integrity check because of putting data into retained earnings file). Last resort is a tape restore from the backup of Monday (9/19) evening or Friday (9/16) evening, depending on when the problem began.

Also, changing the date on the server seemed to initiate the backup tape to go on immediately and a backup started. The automatic backups were checked and seem to be ok (for nightly backups.)

9/21/94	Automatic tape backup did not initiate at 9:00 pm as instructed. Also, Peachtree repair function was not complete overnight (stopped to ask question); completed it in the morning and then ran a data synchronization.

Phoned Rob at CE to report the problems believed to be associated with turning clock back on server. He suggested we down the file server tonight just for a few minutes and load back up to fix tape backup initiation problem. For Peachtree problem he suggested we call Peachtree support and tell them what happened and ask which files may be in jeapardy because of turning clock back. See if we can restore only the ones necessary or the entire directory.

PCG problem/YE: One check was printed fine this morning and the transaction recorded properly. Instead of the report which prints immediately after the check, we received the initial message (as indicated below). We receive the same message when trying to print the "Check Printing Report" from "Checkbook" using the "Reports" pop-up menu. We can print other reports from this menu. We have tried running the report by different people from different workstations with the same results.

'CHECK_PRING_PAYEE_ORGANIZATION' Line 1. [B10] Variable has not been assigned a value. Zero used.	and

Line 1 "CHECK_PRINT_PAYEE_ORGANIZATION' broke because a run time error was encountered.

I have tried rebuilding all of the transaction and report indexes from "Index Maintenance" in the Utilities menu. Ctrl S at PCG main menu revealed the following:

P.C. Gifts version: 4.5

Checkbook module: Installed (1.0k)

Conventional memory available: 306,012

Expanded memory used: 448,512

Expanded allocated: 1,048,576

Available on drive G: 169,598,976

I am sending a complete backup of our PCG-4 system and data files to Di at MicroEdge via Federal Express tonight.

I apparently removed a disk from Hillel's drive A prematurely at the end of formating because the drive won't accept another disk; abort, retry, and fail bring no results.

9/22/94	Peachtree support stated that turning the date/clock back to August on the server would not have caused any problems. The support rep stated that she had experience turning back the server clock/date and has never had any problems. She felt the reason for the data appearing in the August period that should have been September was probably caused by not changing accounting periods after 8/31/94. (Separate procedure from posting.) She also stated that this is really not a problem and that Peachtree is designed to work this way. If for example a company produced checks early (post-dating them) and held them for a few weeks (for example produced in August but dated & mailed in September) the checks would appear in the August Cash Disbursement Journal and Purchase Journal on the screen, but when printed, would show only the current period user is using according to how the period is defined (one month) and thus show only August transactions. No reports should be distorted according to Peachtree support rep. When asked what files are necessary for a proper restore from a tape drive back-up, she stated that the company directory is all that is needed. Thus, Rob from CE assisted us with a restore procedure from the Friday, September 16, 1994 back-up tape. (See notes in "restore" file in Pat's Sysad subdirectory.) (can't find this file on 11/23/94) After restoring the Bradley directory (company) of PeachW directory (f:\apps\peachw\bradley) Jeff examined the data in the two acctg periods. He found that the September data still appears in August and we concluded that it was possible that he did not actually change accounting periods when he thought he had. After testing printing different reports we further concluded that rather than erase data from August period and have to re- key it into September that we would leave it alone as suggested by Peachtree rep. If it becomes a problem later, we will then take the time to erase and re-type.

9/27/94	Bill Bergeron reported today that although the Library software will open, it is not allowing him to access the menu and utility items. I attempted with my own login name as well and the same result occured. The program will take the user only to the limited library-user function of searching for a book, even though the password is entered for the administration utilities. A support call has been placed to the software company, Right On Programs (ROP) at 9:25 am.

**ANSWER: JOAN OF ROP REMINDED US (CALL RETURNED AT 3:00 PM) THAT THE PASSWORD IS CASE SENSITIVE. THE PASSWORD SET BY ROP IS TO BE ENTERED IN LOWER CASE. This worked fine!

10/12/94	Rob - CE came to fix the Office Logic problems we are having (to test the product). He needed to update our Novell ipx and odi files on the workstations.

10/13/94	Chris still has crashes from Office Logic.

10/14/94	Les' workstation had a problem when first turned on. After the RAM counted successfully, a message came on the screen as such:

E01 = K -----> IBM

ie, Not OK with IBM (in red print); the IBM was the traditional blue insignia

Phoned CE and spoke w/Steph. She indicated that 301 always means a keyboard hardware error. I unplugged the keyboard from the back of the CPU and plugged it back in. Then cold booted computer; all was fine!

(Could also check to see if there is a single key stuck in down position. Touch it til it comes up.)

10/25/94	Ann had trouble after 5:00 last night w/calendar again. After opening via startup apparently correctly, it is noticed that the data shifts from the prior week to the current week. The current week's info shifts ahead to the next week. Some info just seems missing altogether. When changes are made and the file is attempted to be saved, Windows apparently detects the error and then closes the application. (We've had periodic trouble w/calendar -- application error, then progman error, sometimes taking us all the way out of windows. Theory was perhaps that two people were saving the file simultaneously, but that could not be the case w/Ann since she was here alone.)

Checked the file (h:\wpdata\bradley.cal) attibutes and noticed it was not checked as shareable. Marked shareable and also delete inhibited. If this is insufficient, may want to try to mark the file as transactional also (provides data integrity check while saving to prevent some changes from being saved and not others).

10/26/94	Phoned Rob (CE) to inquire why our Ctrl Panel, Printers, resets the memory of the printers back to default of 2MB when we have 8MB installed. This is inconvenient because Lotus will sometimes send a message that it cannot locate the device. The printer memory setting in the ctrl panel, printers then requires to be reset and a warm-reboot performed.

11/8/94	Reported the following glitch to Di at PCG: When in the modify columns section of customizing a report, the item listed as "Grant Amount Current Year - 5" (F1 help describes as "Grant amount for the current fiscal year minus 4") actually does use the minus 4 year information (instead of minus 5); the "Grant Amount current Year - 4" listing prints the number of grants awarded instead and will not let you into the Display Format to select the dollars, commas and zeros display. She will report this and get it fixed for all their customers.

11/8/94	Rob (CE) installed additional printer memory in Les', Bill's, Acctg, Copy Room and Consultant area printers. He also checked Office Logic; also copied Windows 3.1 onto the Dell test worksstation (Windows for Workgroups was on it).

Rob indicated that the problem of Windows reverting back to default printer memory size in Ctrl Panels Printers may be rectified in following manner: After changing the memory size in control panel, printers, open up the Sysedit and check the Win.ini file -- search to the printer area (try HP) and find the area which records the memory size. Verify it is correct; if it is incorrect, change it and save the file. If it continues, try moving the entire block of printer information toward the top of the win.ini file. This should help according to Rob's Microsoft support source.

Most computers were updated with the proper printer memory size in control panel, printers; win.ini file was checked (but no info moved toward top yet). Remaining workstations will be done tomorrow.

11/8/94	Ann's calendar program crashed again. See 10/25/94. Call MicroSoft support (?) to get this figured out. Check tips from Windows classes.

11/11/94	Rob suggested we change the PIF files on Chris' computer to the following settings to allow PC-gifts to operate in full Window screen and be quicker (for optimal use of Office Logic): (via PIF editor) display usage full screen, execution background should be selected. We checked Chris' workstation and these settings are already in use. (ie that was not the answer to why Chris' PCG runs at about less than 1/2 screen in a window and is slow).

Set appt for Rob to install Peachtree upgrade on Wed 11/16.

Color printer arrived; toner appears to have exploded inside machine; toner is all over outside and inside of machine. Reported to David Keup of ComputerBay; he had me speak with Heidi at Help Desk (Service); she will send out the same technician who prepared the printer for us to see if it needs only a cleaning or replacement. Save all shipping containers and packing for his review. He should be here either late today or on Monday. Mark came out same day and began cleaning up the unit after he verified that UPS damaged it (he was the one who packed it at CB). After consultation with Bob Berkopec, we decided that the Fdn would not accept the printer anyway, even after cleaning. Also we determined it better for UPS to inspect the goods in as is condition. Sent Mark back. Phoned CB to have UPS sent out for inspection.

11/14/94	UPS phoned in early am that Fred Brisson would be out today. He arrived at about 3:50 pm. CB Service Mgr, Richard Chu, also came at about 3:20 to meet with the UPS rep. They discussed the shipping regulations and appearances of what happened. UPS will put a report through; CB will discuss with UPS at CB site tommorrow to determine claim procedure. CB will arrange for pick up of the damaged printer.

11/15/9	Christina and Pat discussed a new color printer w/copier attachment made by Tektronix. Literature is received; Chris requested quote from Fox River Graphics.

11/16/94	Per Dave Keup of CB, it has not been determined yet how and when the printer will be picked up from Bradley. He agreed that Bradley will not receive this printer even after cleaning. Pat informed Dave to remove our order temporarily until we better evaluate the Fdn's overall printing and copying needs. He will send fax for Pat's signature re returned printer. He will inform pat how to handle the current invoice.

Rob - CE installed Peachtree Acctg for Windows 3.0 upgrade onto network and Pat's workstation. (first had to install 2.0 and convert files, then install 3.0. Old program files saved on network in case things don't work out.) Pat installed to Acctg Intern and Ann's workstation. (LEAVE BOB'S WORKSTATION TIL WE VERIFY ITS WORKING) Had to change property of Peachw.hlp file in f:\apps\peachw to not read-only in order to install on Jeff's. PEACHTREE INSTALLED WITH DOS SHARE COMMAND; REM'd OUT THE DOS SHARE COMMAND IN THE AUTOEXEC.BAT FILES.

Rob moved the pentium computer from Yvonne's desk to Bill's desk, replacing certain Windows files pertinet to each user (calendar, cardfile, etc.). Bill agreed good computer and recommended we order the additional workstations right away. Logged new unit on inventory sheet.

11/23/94	Via modem, Rob assisted Pat in restoring the original Peachtree software onto workstations and data onto network. (The data had been restored by Pat from the backup tape of Tuesday night, 11/15/94, since the upgraded software converted the files on 11/16/94.) All workstations were restored to old version, Ann's, Acctg Intern's, Pat's (Bob's was always running old). The upgraded software is to be installed on Jeff's workstation only (?) after consulting w/Peachtree Support to see where on the harddrive is should be so it won't clash with the old version. It is important to Bob that the new version NOT contain coverted data from the old -- we will be starting fresh in January with the new version. We will however need access to the old version during January in order to close out the books.

12/12/94	Installed VirusScan on Pat's workststion. Test for a week or so before installing on other workstations and server.

Rob installed three new Pentium computers (Dan, Dianne, Chris). Moved the tape backup unit to Chris' workstation. Chris' workstation required more attn due to extra things on her hard drive. Rob did a combination effort of copying certain directories to the new workstation and re-installing some software. Chris and I will handle the re-installing as necessary.

(needed to re-install the Typeface fonts for Harvard Graphics)

12/13/94	Tape backup unit was interrupted during the process at 12:34 am; "fatal error on tape drive 1"; error log name is:

f:\conner\dos\bedos.log

See file in computer file drawer for screen printout of message. Rob had us attempt a manual backup but it also stopped midway (at a different file name) with same message. Rob believes the pentium processor is too fast for the card installed the computer which allows communication to the tape backup unit. He will check on best method -- new card or new tape backup -- to complete this job.

Chris is having several problems utilizing her softwares (WP, Harvard Graphics, PageMaker). 1) All of her windows files are located under c:\windows\system. 2) HP fonts are not on the harddrive, at least not in their proper place. 3) HP Color laserjet printer driver seems to not be working.

1. Re-installed HP printer driver.

2. Re-connected the printer in the control panel, printers. Had to reset memory. Checked the *.ini files for HP info. (Compared to old computer)

3. Re-installed/moved? fonts.

4. Re-installed Harvard Graphics.

(problems/error msgs keep coming up after each Windows re- load...

5. Phoned Rob for assistance!! 2:15pm Steph reported that he will either be here late today, or will phone in.

Rob arrived 3:15 or so to check things out. Chris and Pat need to call Harvard Graphics, which is still not printing adequately. HP drivers are updated periodically; call HP AND Harvard Grphics to see if a new driver is available to replace first one issued with the color printer. PageMaker: Chris will need to click on the subsitute font box each time she opens a file created prior to upgrade to Pentium / color prtr? There may be minor adjustments to make in choosing font styles.

12/15/94	Spoke w/Steph of CE re publicity of Pentium problem. She explained the following important facts:

1. The problem lies only within the floating point calculation component of the chip. In fact, the problem exists only at the 8 points to the right of the decimal point. Therefore, only very advanced scientific types of software programs will be affected by it.

2. The software being run on the computer actually controls whether or not that component of the chip is actively utilized. Most home and general business softwares (word processing, spreadsheets, business databases) do not use the floating point calculation component. (Per ComputerEase, none of our application softwares, including the Novell network system, are using this component.)

3. Improved chips were being shipped before the announcement of the problem was made. Since we purchased our pentium machines so recently, the chance that we have a faulty chip in our office at all is very slim.

. Basically, bottom line is, there is no need for concern.

12/19/94	Copy room printer (LJIV Plus) was working improperly. The message on the LCD screen reported a jam. As the printer attempted to clear itself of the message about every 10 seconds, a considerable grinding sound was made, and the printer was unable to restore itself to operations. Checked all areas for paper jams and no paper was found, although the corners of about 50 sheets of paper in the bottom tray were bent (software command was to take paper from MP tray). After several attempts of opening the printer and removing paper trays and replacing them, powered off the printer and waited about 5 minutes for buffer to clear. Powered back on, ran self test, seemed OK.

Rob (CE) attempted to get the new tape drive unit functioning via phone. Printed out the directory of f:\conner\dos for him to look at to find the right *.exe command. Conner asked him to run a debugging program with a /zl switch during a manual backup. This should reveal where the problem lies.

12/20/94	Tape back up reported a fatal error again. Reported to Rob.

PEACHTREE decision re installation per RB: Continue running old program on network through the final close of the books (mid-January). Install new program on network after that time. (Any data entered into old program in early January can be easily re-entered into new program.)

12/27/94	Tape backup was set for Tuesday nite, 12/20/94. "Fatal error occured on tape 1. See f:\conner\dos\bedos.log." Although the log reports a fatal error, all the files did appear to back up normally. The compare also indicates that no discrepancies were found. So what the error is exactly is unknown still. Rob called and had me modify the file name "bedos.cfg" as follows: "Debug mode = 4F1" (before said "Debug mode = 0"). Set up again tonight and check for fatal error. At some point, may want to remind Rob that the drive has been dropped and we may need to replace it??

12/29/94	9:10 a.m. System crashed!!! (Variety of) messages received on all workstations as follows:

If in PCG: "Network Error on Server BRADLEY. Error locating router. Abort, Retry?" tried Retry, didn't work.

If in Windows: "SHELL-332-80: Network Error on Server BRADLEY. Connection no longer valid. About, Retry?"

-OR- : "1.1.86 Volume SYS dismounted drive to drive deactivation."

All users were locked. After rebooting workstations, could not log back into system. 11:30 a.m. Rob came out to examine situation. (Les was able to log in again a few minutes after the event, but we felt she was probably unstable and had her log out. As it turns out, the system was stable at that time...)

Rob explained that:

1) there WAS a system crash (not power failure or other type of problem; (HE WILL EXAMINE DOCUMENTATION TO SEE IF PROBLEM IS DETERMINABLE AND GET BACK TO US)

2) because it was a crash, the secondary server did kick in, but needed a chance to reboot itself which is why all users locked and were taken out of the system. After the secondary server booted, the system was stable and usable (hence, Les was--and others would have if tried --able to log in). We could have logged in and worked as usual.

3) if a power failure (or other hardware type problem) were to occur on the primary server, the secondary server would kick in automatically and not have to reboot. In that type of situation, only the network administrators are notified of the secondary server initiation.

Regarding the tape drive unit, Rob will obtain a different cable and adapter to allow us to hook it up to my SCSI workstation (rather than the Pentium).

Regarding the problem with Pat's workstation: VShield on the virus software, he prefers that it not run as a TSR and removed the autoexec.bat command that permits that. Periodically I should run the Vshield and VirusScan while other programs are closed.

7/28/94 source: Rob of ComputerEase

Notes on removing old programs or trial/test programs from harddrive.

for a Windows type of program:

Bring up the icon and program group;

-in the properties, write down the name of the directory in the command line (to get rid of it later);

-same with the working directory (if any);

-*Check all the properties of EACH icon in the program group if deleting the entire program group (like WordPerfect has several icons and directories - WP, File Mgr, Speller, etc.)

From File Manager, go to the directory that needs to be deleted (optional to go into Options/confirmation to not have to confirm each deletion - but return to original status when done). Casually view the filenames for familiarity (for checking *.ini files later) and delete the directory and its subdirectories.

Then delete the icon.

To check for changes to *.ini files, do a File Run, sysedit. Check over the autoexec.bat and config.sys files first (usually programs do not put anything in these). Then check the other two remaining *.ini files: Win.ini (check the "load line" and page down and scan for a reference to that program that you wish deleted; System.ini - look for similar things as in Win.ini file. (Useful to use search feature to look for things that may be associated with that program, using any hints from previewing the filenames previously, like WP for WordPerfect. Use F3 to repeat the last search.)

Finally, and importantly, run all remaining programs to make sure nothing was deleted inadvertently that was required for their use.

Source: Rob - CE 9/22/94

Using workstation as file server console

Be in pure DOS prompt, not Windows

f:\system\rconsole

-use minus key on 10-key pad to move from screen to screen

-use Shift Esc to exit rconsole

[NO LONGER USED AS OF 3/95. NOW USE BACKUP EXEC BY CONNER (F:\BKUPEXEC) RUN AS NLM AT SERVER; CANNOT OBTAIN ACCESS AT WORKSTATION ]

(SAVE FOR REFERENCE ONLY: RESTORE FROM EZARC BACK-UP TAPE UNIT:

1.	Log into system with pure DOS (not Windows).

2.	Go to f:\ezarc>ezarc

3.	Select File Tracking System (FTS)

4.	Select Locate/QFS restore

5.	Arrow down to the date and volume (sys or vol1) of restore desired.

6.	When highlighted, DO NOT "ENTER", touch F2 key.

7.	Be sure correct tape is loaded into tape drive unit.

8.	Enter tape name; restore session number (Sys = session 1 and Vol1 = session 2). Session listings can be examined in rconsole or at file server, "list" from ezarc screen.

9.	Destination directory = target; where you want the restored information to reside on the network.

10.	Include files and directories are toggle switches; use arrow keys to indicate include or exclude. Type *.* for all files or can type file names; correct directory path must be typed (F1 for help with syntax - it must be exact). This directory is the source directory on the tape for what will be restored (ie the information desired to appear on network following the restore procedure).

11.	Restore hidden files = Y (usually)

Restore System files = Y (usually)

Restore method = complete all files (usually)

Confirm overwrites = Y (usually)

Create script = N unless this procedure will be performed regularly. If so, a copy of the form for restore procedure is placed on users Mail directory.

12.	F2 when done to initiate restoration procedure.

10/14/94

error when booting the computer: EO 301 = K ----> IBM

301 means error with the keyboard due to hardware issue, usually the plug. Unplug the keyboard and plug back into the back of the CPU to reset. Then cold reboot.

(Could also check to see if there is a single key stuck in down position, especially if there is a repetitive beeping noise. Touch it til it comes up.)

(per Steph - CE)

12/8/94	error booting up Chris' workstation (model 56-486 SLC):

"00016300 IBM" (went into testing menu)

163 always represents a date and time problem/issue which is a CMOS problem; frequently caused by static generated under the workstation -- like from sliding the workstation on the desktop, dry air in office during winter months, etc. The semi-conductor is in the bottom of the CPU box and is very susceptible to static during movement.

Use reference ("configuration", "boot") diskette that came w/computer. Re-boot workstation, select reset date and time; enter correct information, then enter. Re-boot workstation.

10/__94

Using PC-Anywhere communications software in DOS, to set up a host connection:

from pure DOS: c:\winaw\aw5host (enter)

(Rob - CE)

NOTES FROM TRAINING ON DISASTER RECOVERY SYSTEM 3/15/95:

(Rob, ComputerEase)

FYI : NLM - Network Loadable Module - defined as a piece of software that will work on a file server.

This disaster recovery system was recommended and implemented by ComputerEase of Milwaukee. The components were purchased in November 1994. Installation of NetGuard and UPS's occured at that time; fine tuning of backup tape drive took place through March 1995.

NSI 7000 NetGuard

Cables run from each file server (primary and backup) to the NetGuard. The NetGuard does not prevent crashes/lockups, but provides a way for a network to get up and running again quickly. This unit contains the (external) hard drives that are actually controlled by the primary and backup servers. As disaster recovery goes, we are functioning in-between mirroring (extra copy of data and system files) and duplexing (copies of data and system files in addition to extra controller). Although there is only one controller in each server, the NetGuard allows use of the backup server and its controller (to use the mirrored data and system files).

NetGuard runs as a "window", or menu, item via the options of Ctrl Esc.

The NetGuard unit has two power supplies of its own, with two toggle switches in back. IF in a situation where all power is down and all equipment is actually turned off, follow this procedure:

1.	Turn power on NetGuard (both switches); wait 2 minutes.

2.	Turn on primary server and wait for it to boot up completely (3-5 mimutes).

3.	Turn on backup server.

NetGuard labels the primary server as A and backup as B. Usually, the NetGuard will switch operations from the primary server to backup server automatically and will attempt to send notification to the supervisor via a pager. (We do not have pager working since there is no phone line to hook it up to.) The backup server will need to boot up for a minute or so.

If there is a crash of the primary server, log everyone off of system. Allow backup server to boot up. Then everyone can log back in and continue operations. If the primary server fails during a time when no users are logged into the system, the backup will boot up and there is no visible sign of change to the users. For this reason, it is good to periodically check the NetGuard status of the servers.

If the NetGuard changes server from primary to backup, and ComputerEase determines to return functioning from the primary server, follow this procedure (assuming primary is down):

1.	Take down B server (first unload the NLMs for Backup Exec: Network Client and Job Manager via "EXIT" for each one; then type DOWN.) Turn power off BOTH servers.

2.	Use NetGuard key to reset to A server. (Wait 2 minutes?)

3.	Power on primary server (3-5 minutes to reboot). When the server is brought up, the Backup Exec NLM's will load automatically. The system will check itself for problems and automatically run a VREPAIR if necessary.

4.	After primary server is completely up, turn on backup server. Error messages will be present relating to its taking over from the primary before; generally ignore these. Final screen will come up with 'NetGuard is currently monitoring..."

BACK UP TAPE DRIVE UNIT and its SOFTWARE

The backup tape drive, manufactured by Conner, is a DAT device.

There are two NLM's for the BackUp Exec for Netware verson 5.01 software; they need to be loaded in order for the backup to take place. If the NLM for the BackUp Exec Netware Client program should be unloaded accidentally, at system console type ":load be". If need to load the BackUp Job Manager, type at console ":load bemgr". Need supervisor name and password. (This software can not be loaded at a workstation remotely to reset scheduling, etc. All work must be done at the file server, or at the workstation via RCONSOLE.)

BackUp Exec Netware Client allows for job scheduling details. Make any job or configuration changes here. It is set up to run backups Monday thru Friday at 10:00 pm. The backup takes about 1.5 hours including verification, comparing files from tape to server.

BackUp Exec Job Manager controls the activation of the program. Ctrl M is menu. The tape backup will work if either server is running.

[BackUp Exec has capability to also backup remotely the c:\ drives of all workstations connected to the network. This requires additional software, which is installed but not configured for time being. It can be set to run at night, but the workstations would have to be left on, and set with certain configuration -- each workstation individually. Because of the number of workstations and variety of configs, etc there are often glitches errors. It is better to run it during the daytime, one workstation at a time. Something to consider in future.]

UNINTERRUPTIBLE POWER SUPPLY

There are two UPS units, one connected to the servers and one to the NetGuard unit. The concentrator (HUB station mounted on wall) is connected to the old UPS unit.

VIRUS SOFTWARE

Virus software, VirusScan by McAfee, has been installed onto the file servers to detect viruses only on the network. It runs as an NLM. (At the present time, it would probably conflict with the NLM for the backup exec software. After the backup is running smoothly for a while, we will unload the backup NLM and load the Virus protection NLM to test the servers. Thereafter, because the backup NLM needs to be loaded all the time, we will periodically load and unload appropriate NLM's to run virus protection, particularly before and after installing software.)

TO EXAMINE OR CHANGE WINDOWS SETUP OPTIONS (WHEN WINDOWS CANNOT LOAD):

(Rob, CE)

If there is a problem running Windows and it is not stable enough to click on Windows Setup icon to check settings, reboot computer and go to pure dos prompt. Go to the c:\windows prompt and type setup, enter. This will show the windows setup in a dos format. Reboot when finished.

TO HELP DETERMINE WHERE AN ERROR/BAD PARAMETER LIES IN THE BOOTUP PROCESS OF THE AUTOEXEC.BAT FILE:

(Rob, CE)

As the computer boots and comes to the prompt, "Starting MS-Dos ...", touch F8 key to test each parameter and watch for messages.

To bypass the autoexec.bat and config.sys files while booting, touch F5 at "Starting MS-Dos..." prompt.

To allow a user to opt for PURE DOS BOOTUP rather than Windows 3.1, (like Yvonne and pat), edit the saber.srv file. The winpause.bat file controls the pause. (per Dean, TCS)