COMPUTER DIARY 1995

1/5/95	Appt with Rob of CE for training on disaster recovery system is possibly postponed due to lack of specific cable required for the tape back up. He will check around to see if he can obtain the correct one today. His Friday schedule is pretty well booked; not sure he could come in then either. Rob informed us that Office Logic has come out with an upgrade that he feels will satisfy our needs better -- specifically the DOS (PCG) issue. He will download a copy and install on our system ASAP. He will phone again with date and time.

1/25/95	Rob (CE) will call soon to make appt for tape drive unit and to remove Ofc Logic and install CC:Mail. Re tape drive, he now has the Adaptec card to install into Chris' workstation to adapt to the tape drive unit.

1/26/95	Appointment was set for Rob to come on-site Tuesday 1/31/95 approximately 9:30 am to perform the following tasks:

-Install back-up tape drive unit to Chris' workstation;

-Train Pat and Yvonne on disaster recovery system;

-Remove Office Logic and install CC:Mail software

1/31/95	Rob came (9:30 am to 2:00 pm).

-Back up tape unit still not working -- cable still wrong and not returnable. Rob will check into software required to make the backup unit run off the server rather than workstation.

-(training could not take place w/o working tape unit)

- installed CC:Mail on server and Pat's workstation. Pat installed onto Ann's, Chris', Yvonne's and Les' for testing purposes.

-Left msg for Jim Jaeger to discuss charge to Fdn relative to tape drive unit -- extensive research and on-site time by Rob, parts ordered to make it work, etc.

2/7/95	Followed up with CE re tape drive (no call returned yet). Steph said that the problem is in her area and will be meeting with Rob today to discuss resolution and will phone back with a plan. She will not charge our account for this research.

2/10/95	Jeff Johns, acctg intern, reported on 2/9/95 that his Lotus icons are inactive. Certain icons, but not all, do not produce any result when clicked upon. We isolated it to various formating instructions like underscore, bold, etc. (The menu commands DO work.) After exiting and re-loading Lotus, the icons appear to work all right, but after a while, stop working again. Today I replaced Jeff's c:\windows\lsicons.ini file with a copy of my same c:\ ... dated 5/13/92 file (Pat's). (His old file was copied to c:\windows\ lsicons2.ini dated 2/9/95.) Jeff will test the icons on Monday, 2/13/95 and report back to me. We may have to look for other files in lotus which control icons.

2/16/95	Left msg (with Rick) at 3:15 pm for Steph to call and update me on the tape drive situation.

2/21/95	Jeff reported today that Peachtree was not performing as it should with the function of unposting a general ledger for month of December. When he clicked on the appropriate commands, the posting began but got stuck when 100% completion was reached. While the procedure runs, an option to "abort" remains up; this option did not disappear upon completion of the function, as it should have. He was unable to close Peachtree without ctrl atl del. When he opened Peachtree again, we could see that although 100% completion was stated during the procedure, the data did not appear in the edit box as it should.

Because Lotus was running in the background, I suggested he log off the system and log back in, closing Lotus (which is in Windows Start Up) before logging into Peachtree. This did not solve the problem. We turned the computer completely off, then closed Lotus, then opened Peachtree. This time the function ran properly, however, took considerably longer than normal to close the "abort" command (spontaneous upon completion). (The data appeared properly in the edit box.) If it happens again, we will run a Peachtree option to reindex or repair the company.

2/28/95	Upgraded Chris' workstation with Harvard Graphics 3.0. (Chris installed.) No problems. Selected option of HG removing old program files during installation of new program, since the old disks are here and could easily be reinstalled if necessary.

UPGRADED TO PEACHTREE 3.0! Per Bob's instructions, did not convert data from old version to new. The Foundation will begin using new pkg from scratch for 1995. Jeff will re-key data from January and February into new system. Had to first clean up the current peachtree program file directories on Pat's harddrive and data file directories on network (see below).

Notes regarding installation:

Printed out *.txt files for reference. Gave Jeff copy.

On Pat's harddrive: Renamed (had to actually "move" directories -- could not access as "rename") old version (5.0 Batch C7) directory as Peachw.old. This is the old program which would be needed to view the old data on network. Renamed newer version (3.0) erroneously installed in December 94 with converted data as Peachcon (con for converted data). Can remove both of these later in the year, as all goes well. Installation instructions indicate Dos Share must be loaded. Will check w/Peachtree support; if used only for opening multiple companies simultaneously, will not need. (PC-Gifts can not run with Dos Share in environment.) If required, will need two autoexec.bat files -- depending on what the user will need to load.

*Jeff's and Ann's workstations had insufficient disk space to retain old program files on their c:\. Deleted the directory with program mgr to make room for new program. Bob's workstation has old version on it (?). Keep as is until Bob needs Peachtree.

On network: f:\apps\peachw.old was the upgrade installed in December with Bradley data converted. (We then restored the old version (5.0 C.7) and older data til future time.) Moved peachw.old to peachcon directory (w/"con"verted data).

Then moved the old version (being used til today) peachw to peachold directory. This now is the program data files of the Fdn used on Peachtree version 5.0 C.7. (This is the directory that would need to be used to access the old data for the old version software.)

(THESE OLD DIRECTORIES WERE REMOVED FROM NETWORK ON 3/18/96; BACKUP TAPE OF 3/15/96 SAVED AS PERMANENT RECORD OF OLD PEACHTREE DATA.)

New installation of Peachtree for Windows 3.0: Ran a:\setup from Windows and installed setup files to f:\apps\peachw.

Then did harddrive installation for Pat, Jeff, Ann. a:\setup from Windows, installed setup to f:\apps\peachw, program files to c:\peachw.

3/2/95	Spoke with Peachtree tech support re DOS Share command. This is required to run Peachtree for Windows 3.0 (they were surprised that the package even loaded without it). The reason, they contend, is to allow read and write of multiple files at once needed for spontaneous recording (ie modifying a customer file utilizes more than one Peachtree file but can gain access to both only w/DOS Share). DOS Share is required even if the program is used only by one person.

Changed Jeff's and Ann's autoexec.bat files by removing the "rem" statement in the DOS Share line. Because PC- Gifts, the grants database, can NOT run with the DOS Share command, created new program group for PC-Gifts as reminder that s/he will need to modify the autoexec.bat file (rem out DOS Share statement).

Created new Program Group for Pat's Peachtree to remind of the need of modifying autoexec.bat file (activate DOS Share statement).

3/6/95	Rob - CE - installed the file server version of the virus scan software. That seemed to go okay.

Installation of tape backup unit and its software to run off the server did not go well. Apparent problem: the cables connecting the various devices to the NetGuard box are too long - maximum is really only 12 feet, even though specs say 17 feet.

Also, Rob noticed that the Fdn has been operating off the backup file server since Sunday, February 5, 1995 at 9:10 pm! (Since no one is logged in at that time/day, no message was sent. Could order separately an electronic paging device...to find us anytime.) Rob reset the NetGuard to run off the primary server, however, problems began, probably due to needing a new NIC card (newer version). Because of this, Rob returned the NetGuard system to operate off the backup server.

Also, there are apparent problems among the configura- tion files for the various devices on the network, also which may be preventing the proper operation of the tape drive.

Even after an excess of 1.5 hours downtime, a variety of these problems caused several workstation crashes during Rob's work on the server. Several people were logged in and lost work due to system errors. Because the Fdn has been, so far, very patient with the installation of the backup tape drive unit, Rob wishes to provide after-hour service at no charge to remedy this situation. There will be significant down time, and thus he proposes to come in during evening hours, probably Tues 3/7 or Wed 3/8 to:

a) replace the NIC card in primary server and run tests of it;

b) replace cables connecting devices to the NetGuard with shorter ones;

c) compare all configuration files for the network to see if a clash exists.

(Rob phoned Pat 3/7/95 3:30 pm to verify that he would come Tuesday 3/8/95 at about 4:30.)

3/17/95	The backup tape drive did not backup night of 3/16 (Thursday). A hardware error occurred. Report it to Stephanie of CE at 8:50 am (Rob out). She will let Rob know this afternoon; she would like him to come look at it. Red light on drive is flashing; green light is on. Error message can be read in the BackUp Exec Job Manager screen.

3/24/95	WordPerfect 6.1 upgrade was installed onto network (Rob-CE). The directories are at f:\apps\office\wpwin & ...office\shared. Workstation installs were done by Pat on 3/27/95. At file, run, type f:\apps\office\ wpwin\setup. Respond to questions: install, network, workstation, OK ("where located on f"). After installed onto workstation, set file preferences at u:\ for documents/backup and spreadsheets. The WP files were installed (co-mingled) into the c:\windows directory. Most users will continue using 5.1 until Yvonne and Chris attend seminar on 3/29/95. Chris is checking to see if we need updated printer drivers from HP for the IV, III, II, and color printer.

SEE NOTEBOOK AT FILE SERVER LOCATION FOR NOTES ON PROBLEMS RELATING TO FILE SERVER, TAPE BACK-UP, AND OTHER ASSOCIATED ITEMS TO FILE SERVER

4/20/95	Installed update to Peachtree for Windows v 3.0. (There were problems that Jeff reported to Peachtree; they supplied new batch (05) to correct the problems. (Data was appearing in one are but was missing in another.) Installed program files to Intern's, Ann's, pat's and Bob's workstations. (data files to f:\apps\peachw). Backed up all program and data files first. See Peachtree (paper) file for details. If there are problems with any of these workstations, revise the autoexec.bat file, share and smartdrv.exe command lines. Refer to Peachtree Installation manual. (To use Peachtree on Pat's workstation, make changes to autoexec.bat file - share and smartdrv.exe.)

4/25/95	Spoke with Robert Katz of MicroEdge (PC-Gifts) today re the problem with the DOS Share command. [The DOS Share command is required for many networked Windows programs, like Peachtree, the new Lotus Smartsuite product coming in, CC:Mail (if on workstations), etc. Per Rob of CE, there is definitely an increase amongst programs to require this command line in the Autoexec.bat file. However, PC-Gifts locks up with the DOS Share command loaded.] Robert Katz reported that MicroEdge can not "correct" this problem, that it is something in the actual platform of Advanced Revelation. He noted however, that the new Windows version of PCGifts is a true Windows package and does not conflict with the DOS Share command (it is written on Visual Basic platform - totally different than Adv Rev.) The Windows version of PCG is now out of beta and is available in both access engine and client server; both are currently supported by MicroEdge. A 486 minimum is required to run it, a Pentium is much better.

Robert faxed a document to us with DOS Share command optional solutions -- rerouting when the DOS Share loads, or running Vshare.386. This was faxed also to Rob at CE for review and recommendation.

Remember, expanded memory is required for PCG (DOS version). When installing new Pentium machines, we may have to reset configuration to allow for expanded memory. (Windows version does not need exp mem).

4/26/95	Installed upgrade of CompuServe Information Manager 1.4 (WINCIM) (prior version was 1.2) to Kelly, Bill and Pat. Installed "on top of" the Town Hall version per Town Hall (Pat's was not Town Hall ver, but 1.0.5 of WINCIM). Had to reset a couple settings, and re-enter the local access phone number. Note: the old script files were moved to *.old; if they are needed, can copy them back to *.scp.

Ordered 10 concurrent licenses of Lotus Smartsuite from Lisa at ComputerEase. It should be here within 2 weeks at most.

5/12/95	Chris had problem with computer on Friday a.m. at 8:30. Started having problems Thursday w/fonts in PageMaker. Potential exists for annual report and/or font files to be corrupt. Save Tues and Wed backup tapes for possible restoration requirement.

5/15/95	Chris determined her problem w/fonts had to do with copying them to a diskette for the printer doing the annual report and removed and reinstalled the fonts on her own.

5/17/95	Rob picked up tape drive unit (which has a tape stuck in it, not completely seated). He will phone Conner to see how long to repair. 5/19: Tape drive situation: 30 day repair delay with Conner!! Options: Buy new one? NO! Rental available??? Rob will check to see if we can use one that he has at his ofc (another customer's).

5/18/95	Rob (CE) installed Lotus Smartsuite 3.0 to file server. Installed nodes: Pat, Chris, Bob, Jeff (intern). Installed node files to u:\ rather than to c:\ because of the amount of space required for program files. Node install: Prog Mgr, File run, f:\apps\lotus\install.exe. The directory to install to is u:\lotsuite. Lotus will ask to put some files on harddrive. OK. There should be a lotus or lotsuite dir on c:\ with only two small dir on it.

5/19/95

Jeff (acctg intern) has problem with printing a particular report in Peachtree, Reports, General Ledger, Trial Balance R. When he excludes the "filter" (an option in layout of the report), the HP II loses one line of data at the bottom of page 1. The total dollars at the end on page 2 is accurate. The screen shows the complete report with all lines intact. Steps taken to correct it:

Identified printer driver:

File name: HPPCL.drv (seen in install drivers)

In Prtrs, setup, options, about:

Universal Printer Driver v 3.1

HP Laserjet Series II v. 1.1

MS 1990-1992

1. Printed other software programs of 2 page documents: WP and Write. OK

Support line from Peachtree:

2. Replace printer driver. Still didn't work.

Support line of MS Windows:

3. Printed to file (from Peachtree), captured in DOS to printer, one line is still missing.

3a. MS reports that no updated printer driver is available for HP II and believes problem lies with Peachtree.

Ideas of our own:

4. Printed to HP IV on network. Printed fine.

5. Printed with filter option on to HP II; prints fine.

6. Replaced printer driver again. Jeff's computer was taking drivers from f: during install, moved it out and replaced with the one he had in c:. Still didn't work.

Support from Peachtree:

7. Increased time out value to 20 (from 8) in Ctrl Panel, Prtrs. Peachtree also said to change the timeout value in network printer capture command. But we do not capture through network.

7a. Replace printer driver for HP II with the one listed for HP Laserjet (plain).

Our idea:

8. Unselected fast printing to port in network setup of ctrl panel, prtrs. No change.

ComputerEase support:

9. Rob downloaded via modem his HP II driver. Was different version number, but same date and file size. Deleted it.

10. Suggested we replace HP II in Jeff's ctrl panel, prtrs, with HP III or IIP. This showed some progress. We used the III, and the missing line printed out, but lost some formatting (lines drawn as borders).

Resolution: The problem apparently lies with Peachtree communicating to HP II regarding specifically the filter option command.

Replaced printer driver with plain HP Laserjet in ctrl panel, prtrs. Printed good! Jeff will either print with the filter on (to HP II) selecting the printer installed with HP II driver LPT1; or will print to HP Laserjet (plain), LPT 1 for filter off. IE, has two printers set up for LPT1.

5/30/95	Rob - CE came to perform following tasks:

- returned & installed repaired tape back up drive. Repaired by manufacturer under warranty.

- Set Pat's workstation to run with DOS share (for Lotus Smartsuite apps). The following line was added to autoexec.bat file:

lh share /F:2048 /L:20

This line may need to be modified if PCG has problems. Can rem it out temporarily if necessary. Then contact Lotus support or PCGifts support for help with parameters.

- brought a new mouse for Mr. Joyce's home computer. Gave it to Les for MJ to take home. MaryJo should be able to install with no problems.

- showed Pat how to send an E-Mail message via CompuServe.

-took Lotus Smartsuite registration forms to fill in vendor part of form. Will return completed forms (copies) to us 5/31/95.

6/5/95	Rob came to install new computers. Significant configuration had to be done. Got Kelly's and Pat's installed and moved Pat's to Ann. Also he changed batteries in 35s and 40s for sale. Returned Lotus registration copies from 5/30/95. Will call to arrange appt on approx 6/20 for addl computer installation. Returned CE's copy of Lotus CC:Mail they loaned us for testing. (We did not purchase.)

6/6/95	Pat assisted Bill Bergeron with installing Internet in a Box software onto Kelly's workstation and accessing the Internet. After some assistance from Exec-PC (service provider), success!

6/7/95	Pat had problem in WP6.1. When clicked on search, or print, or Format, page, paper size received error message: WPWIN61 caused a general protection fault in module SHWIN20.DLL at 005B:0F34. WordPerfect support - Network area (Clay) directed Pat to change the display driver (Main, Windows Setup) to regular VGA instead of the "#9gxe64.drv 640 x 480 x 8bpp" driver Dell had installed. Clay also suggested I contact Dell for an updated driver since they are aware of this problem. Also made same change to Kelly's new computer.

6/19/95	Installed color printer (Chris' HP Color Laserjet) to network. Utilized Pconsole to add the printer to the network. (Printer came with network card installed.) Rob assisted by identifying the printer's network card to the network (utility?). Used HP diskettes (Windows PCL Drivers Disks 1 (& 2) to install drivers to the workstations for the Color Laserjet printer. Installed to Pat's first on 6/19, then to Leslie's (same date?), then to Jeff's on 7/6/95.

6/21/95 -	Rob came to install new computers.

6/22/95	The following installs were done, with notes to specific workstations as required. Rob performed significant configuration of each new workstation shipped by Dell, although they came with Windows 3.1 installed, as well as Microsoft Office.

Installing new computers (and transferring old)

General notes:

Remove CC:Mail from all applicable workstations:

Yvonne, Chris, Les and Pat's (others?)

AUTOEXEC.BAT FILES:

Set all autoexec.bat files with command line for Dos share with additional parameters for compatability with PCG. (Including Intern's, Ann's, and Bob's. Should work with Peachtree too.)

Check each autoexec.bat file for instruction to delete the temporary file after closing out. syntax is: on line following "set temp=", "del c:\dos\*.tmp"

LOTUS SMARTSUITE

Install to all workstations. See reference sheet in Lotus upgrade file.

PRINTERS SETUP

(Re)install printers for each person. Be sure to increase memory in setup.

INVENTORY EACH ITEM. IF MOVING, REASSIGN INVENTORY ITEM TO NEW OFFICE.

User	Receives	Notes

Kelly	New 120	-Installed Internet In a Box, Town Hall

w/fax modem	Compuserve, Smartsuite.

Leslie	New 120	-Personal calendar, MJ's calendar,

w/fax modem	etc.; Aldus PageMaker; added color
printer to Les' ctrl panel/prtrs & driver; Smartsuite.

Yvonne	New 120	-Personal calendar, any other files she may have on c>

w/fax modem

Ann	Pat's	-

486 77	Installed Peachtree 3.0; Smartsuite.

Pat	New 120	-Installed Town Hall Compuserve, external modem, PC-Anywhere, (no Peachtree), Virus Scan, Aldus PageMaker; Smartsuite.

Library	Yvonne's	-Install library software and data files from c>; set up printer.

486 77

Jeff	New 120	-Install Peachtree 3.0; set autoexec.bat to use regular dos share command. Set up printers. Check c> for investment software pkgs.

Chris	New 120	-Check c> for fonts, etc; install Aldus PageMaker and Harvard Graphics.

Bob	Chris' 90	-Check c> for investment software and data files; install Peachtree 3.0; set regular dos share command.

Hillel	Bob's	-Pat-order (internal or external?) CD-Rom.

486 77

-----------------------------------------------------------------

Miscellaneous notes:

Bob did not have sound at first. When attempted to assign sounds to events in Ctrl Panel, Sound. Had to copy sound drivers off network (from another workstation's win.ini file) to Bob's Ctrl Panel, Drivers.

Jeff (intern) requires his LPT:1 HP Series II with two separate driver options. Needs generic and HPII selections for utilizing with Peachtree.

Chris' Smartsuite experienced errors in attempting to create certain icons during install. Following error msgs were noted:

Approach 3.0 APR:ADDICONSAPR:986; Approach notes APR:ADDICONSAPR:987; Organizer ORG:ADDICONSORG:1238; Lotus ScreenCam 1.1 CAM:ADDICONSCAM:1073; CAM:ADDICONSCAM:1076; CAM:ADDICONSCAM:1079; Lotus Dialog Editor SHAR:ADDSHAREICONS:2280.

Also, Chris needed her Ctrl Panel, 386 enhanced to be adjusted: uncheck 32 bit, increase perm swap file to 20,000.

Some workstations experienced problem accessing sound waves in Ctrl Panel, Sound because one could not move backward in tree when looking for wav files in right dialog box. (could advance to next level but not return) Rob had me open net.cfg file in notepad and add line at top that says: "show dots on".

Future:

Install Virus protection on all.

Remember, when replacing HPIV printer driver, use the one on f:\public\hp\hp4m supplied by CE.

7/10/95	Rob came to finish cleaning up old computers to prepare for sale; changed batteries. Also, Rob showed Yvonne and Pat how to run virus scan from workstation for both c:\ drives and file server/network. When scanning network files for virus, do not need to take users out or take server down. From workstation, open Virus Scan software (in Windows), click on select (drives), and set to f: for both sys and vol, one at a time. Can also run from pure DOS at f:\login\scannet (from any prompt).

7/12/95	Rob installed upgrade of WordPerfect 6.1 on MJ's home computer. He reported that the hard drive is completely full now; Mary Jo saves files to diskette. Purchase new computer??

7/14/95	Preventative maintenance (cleaning, adjustments, changing ozone filters) was performed by Mike of Todd Hoskins Service Specialists, on all HP laserjets except color.

7/17/95	Copied new HP printer driver for HP Color Laserjet to the h: drive for access by anyone who needs it. It is stored as follows: h:\prtdrv\hpclr101. The name stands for HP color version 1.01 driver. Install from ctrl panel, prtrs, add, install, h:\ etc. (It may take two tries; first attempt went to Geni port instead of LPT3.) Informed Christina only of the new driver.

7/20/95	All users were locked out of PC-Gifts. We could login and get to PCG's main menu but could not get past it to the blue data entry screen. When we tried, we only saw the gray pin-stripe background. The problem affected all user IDs and all workstations. Dianne had logged in earlier this morning and accomplished her work, having printed her write-up afterwards. She exited the system when we discovered the problem. Bill Schambra was the only one using the system at the time the problem was discovered; he continued with his write-up. When we asked him to exit PC-Gifts, he could not get back in. Yvonne noticed Bill had logged into the network at 8:17 am, where as she (YE) had logged in at 8:21 am.

Yvonne worked with Di Raucci at MicroEdge. Checking the "Ctrl S" at PCG's main menu revealed expanded memory is not in use, but Di said it should be and we'll address that at another time. She asked if any changes or installation of new software were made on the network since yesterday; there were none. We tried accessing PC-Gifts through pure dos instead of windows with the same results. Di suggested we restore the system from last night's backup.

We checked the space PCG is using (40mg) and, seeing there was enough room on the network, we created a new subdirectory (PCG-OLD) to move existing PCG-4 files into before restoring the PCG-4 directory and files from Wednesday night's backup. We used the xcopy command to do this, but received the following message: "SHELL-332-85: File in use during OPEN A FILE. File: G:REV49001.LK" so we were not able to save the current system. We restored last night's backup over current system files, losing all work done so far this morning, prior to 9:30. The backup was successful and the system was up and running at 11:00 am.

Di mentioned the above named file is a main system file and they could send us a new one if it is corrupt, which it might be. She said once a user is in PC- Gifts, they are in. The problem, whatever it is, somehow occurred during the four minute difference between Bill's and Yvonne's login this morning. She will call tomorrow to see if any other information is discovered and to continue work on existing issues with Yvonne.

7/25/95 -

7/27/95	Completed the following tasks on all workstations:

--Installed McAfee VirusScan software 2.1, and an upgrade to 2.2.3.

--Finished installing Lotus SmartSuite program; moved others from u:\ to c:\ as possible.

-Still on u:\: RB, KA, JJ, WS, JB (due either to lack of harddrive space or files already modified)

-Moved to c:\: CC, AM, DM, PW, YE, DS, LS, HF

--Checked autoexec.bat files for:

1. Dos share command

a. for Pentium: LH /L:1,13984 share /F:2048 /L:20

b. for 486 machines: LH share /F:2048 /L:20

2.	automatic deletion of windows temp file:

(line after set temp): del c:\dos\*.tmp (or whatever directory set temp is set to).

--Set up screen savers

--Noticed workstations are not set up to use expanded memory (that PCG requires). This is why PCG is unstable during reporting and long searches. Yvonne has set her workstation via config.sys by removing NOEMS command. Will change other workstations when there is more understanding.

--Checked for dots on in c:\netware\net.cfg files for the workstations w/CD-Rom. (Could not move backward to see sound files in windows sound.)

7/28/95	Yvonne and Pat set their config.sys files to utilize expanded memory for PC-Gifts. [To check if a workstation is running PCG with expanded memory, Ctrl-S after loading PCG and logging in. System info will be provided; expanded mem toward bottom of screen should be active and say how much memory.] (Without this could not use PCG features like adding columns to reports, lengthy searches, etc. MicroEdge stated emphatically that EMS (expanded memory) is required for PCG to run properly. Our config.sys line 3 had:

DEVICE=C:\DOS\EMM386.EXE NOEMS I=E000-EEBFF

Changed to:

DEVICE=C:\DOS\EMM386.EXE RAM=4096 I=E000-EEBFF

When attempted to change Chris', there was a conflict with Windows. Message appeared while loading DOS, "invalid parameter specified, press any key when ready..." but then continued w/o pressing a key. "EMM386 successfully installed." Continued with bootup process, but while loading Windows, error message came: "Program Manager: Insufficient memory to run this application. Quit one or more Windows apps and then try again. OK". Since no other changes had been made to Chris' config.sys file compared to Pat's and Yvonne's, we determined the problem lay with Windows. Chris had installed the #9 Hawkeye video monitor driver in Windows Setup, Display option. Since Pat's was re- set to standard VGA (because of a problem with WP 6.1), we changed Chris' to VGA also. This remedied the problem, however Chris lost the ability to control her monitor in the more sophisticated manner allowed by #9 Hawkeye driver. Also, Chris had a problem with the #9 driver not allowing her to have more than 15 icons in a Windows program group. With the standard VGA driver, no problem with that now! Pat is to find out if their is an updated video monitor driver from Dell so we can take advantage of the tools available. (No there is not.)

Kelly had lost sound to his computer system. After checking access to sound.wav files off the ctrl panel, sound, and checking all physical connections on the speaker and sufwoofer system, it was discovered that the power was turned off the auxiliary button on his proxima power protector. Sound restored when powered on.

8/3/95	Checked into problem with WordPerfect 6.1. Pat and Kelly could not access Writing Tools (Speller, Thesauraus and Grammatik) even though appeared to be set up properly (looking to correct directories). When clicked on the icon within WP, nothing happened. When clicked on the icons in accessories, msg appeared that languages were not available, reinstall. Yvonne was not able to see Insert, "Characters" within WP6.1. All characters appeared as empty boxes. (Pat could not see characters either, don't know about Kelly.) Chris could not access Graphics, Chart and Draw features. Read the Readme.Net file in WP61 for clues. Also read in the WP manual Appendix D, Networking WordPerfect for help. Could find nothing incorrect to repair, so reinstalled WordPerfect 6.1 on the workstations only according to instructions in WP manual, appendix D, networking - Yvonne's, Pat's, Chris' and Kelly's. If the same problem occurs again, will discuss with Rob his installation procedure on the network.

Kelly reported a problem in PC-Gifts. When hitting a certain key, he receives a "string error..." and is taken out of PCG. Also, when he attempts to use the spellcheck in PCG, he is taken back out to PCG login screen (without error message).

8/4/95	Today Kelly's PCG problem enlarged to not being able to log in at all. Changed Kelly's config.sys file to utilize the EMM.386, RAM=4096 according to PCG's recommendation as stated above in record of 7/28/95. Received error message "Request_WIN_Sub1 Line 1. [B700] Non-dimenstional variable used as a array." Re-booted and tried again, was able to go in, but when touched the speller key, the ""Dict requests" file is not available... press any key to continue" message came up. To enable logging in properly and overall PCG performance, changed Kelly's config.sys file to allow use of expanded memory (Device=C:\dos\emm386.exe ram=4096 I=EOOO-EBFF). Speller still did not work. Then changed Kelly's PCG PIF file (in program properties of PCG icon) to the regular pif provided by PCG. He had been using PCG4dian.pif. Everything seems to work well now. Also reinstalled Kelly's WP6.1 to return access to the writing tools. See above paragraph.

8/8/95	Dianne experienced a problem in PCG, with her record, which was open only once - confirmed, would not allow her to save her write-up due to 'someone else has record open, cannot save changes'. She had printed out write-up and so we closed PCG. Changed her config.sys to allow use of expanded memory (see above paragraph). There was no reference in her config.sys to the I=E... as in other workstations, although she uses a model 90 and the others are model 120c. We put it in anyway, if there are problems in near future, remove it. After making this change, Di's workstation still reported PCG as not utilizing expanded memory. We changed her PIF which was pcg4dian.pif to the regular pif. The the expanded mem was activated and all was well.

8/9/95	Jeff reported problem yesterday with Peachtree. He had phoned Peachtree support because of the original problem which they apparently worked out. However, he reported that P support mentioned that his "enhanced memory setting was surprisingly low." (Prog Man, Help, About Prog Man, Memory = , System resources = ) I changed it to the recommended amount with Peachtree and Lotus SmartCenter running. It increased it by about 2/3. If Jeff has problems again, he'll let me know.

8/9/95	Requested from Dell tech support updated driver for #9 video stuff to work better with WordPerfect and allow more than 15 icons in a program group. Hank, Tech Support, Hardware, Windows 3.1 (800) 426-5150 x 60995 "back-door" to tech support, confirmed that we had the latest driver version: #9GXE64.EXE version 2.38 (hawkeye feature set icon, Hawkeye ctrl panel, #9GXE status icon shows driver version. Dell had record at that a Fdn workstation downloaded the upgrade a couple weeks ago. Hank explained that with that the video ram can hold only so many feature requests. Chris' workstation, with 2MG VRAM was set up to have the absolute top amount of colors (set in Resolution Exchange icon) and top resolution. (She was following Hawkeye instructions to set colors for her monitor to match more closely with what was being printed off the color laserjet, to avoid repetitive printing tests.) With that combination drawing against the 2 MG VRAM, Windows cannot hold unlimited icons, and limited it to 15. When reduced colors and/or res, more icons could be held in a group. Icons, resolution and color are directly affective of one another in regard to VideoRAM. At this time, no driver upgrade is available. Upgrades, when available, can be downloaded from Dell's bulletin board service. The 2MG VRAM can not be added to, but can be replaced with 4 MG VRAM card. Chris did not feel it was necessary to obtain additional vram.

8/11/95	Yvonne reported to Di at MicroEdge that when creating a letter to be merged, the field "Staff" will not print "Code" when selected; both options of Code and Description print the description.

8/14/95	Pat is on vacation this week. When I (Yvonne) tried to open WP6.1, application error message occurred. Second message mentioned "share violation;" tried again with same results. Looked at config.sys and autoexec.bat; saw nothing different. Looked at Program Properties for WP6.1 selected "OK" upon exit. Was able to open WP6.1. (Same scenario in the afternoon when I tried to open WP6.1.)

Also, PC-Gifts locked me out each time I tried to log the activity of sending a letter. It actually recorded it in the activities file, but gave me the message "Another workstation is currently updating indexes on file "!ACTIVITIES" with control field "ORGANIZATION_ID*INDEXING" locked." I tried to run the Utilities' index maintenance feature but received the same error message. I left a message for Di at Microedge. Then I tried using the Utilities "Index Fix" feature (with all users out of PCG) and the problem seemed to be fixed. I called Di back to let her know. I then applied the Supplemental Upgrade to PC-Gifts 5.0, with no ill affects.

The JetDirect network card for the Consultant Area printer arrived today. Easily changed the Card and printed self-test. Called Jerry at CE for help with JetAdmin.Exe; checked settings, unloaded PCONSOLE and re-loaded PCONSOLE PS_BRADLEY. Set up done; phone time @ 30 min. I printed to the Consultant Area Printer ok. I changed Bill Bergeron's printer setting back to Consultant Area and let Chris know it was fixed.

Also, I noticed the system logged Leslie out Saturday night at 8:07 pm. I asked her if she'd like extended hours; we decided to change her time restrictions to allow usage 7 days/week from 7:30am-10:00pm.

8/15/95	I (Yvonne) spent 15 min. on phone with Rob from CE while he look at the file server via Pat's modem in response to Pat's memo of 8/10 regarding Jeff's Peachtree problems with record locks. Jeff reports no further problems; Rob said all is well.

I then asked him why we get messages when logging in noting "Expanded Memory" and "Invalid Parameter." He said we should not be using expanded memory. I explained that when we could not run PC-Gifts reports, I called PC-Gifts for support and they had me check system settings, discovering expanded memory was not in use. (According to PC-Gifts status screen, it was in use this past spring when this same information was checked for another reason.) They told me it was necessary to use expanded memory and helped me place it in config.sys, which I did. That cured the PC-Gifts problem. As other users noticed the same problem, their config.sys was changed to read "RAM=4096" also. Rob suggested we temporarily REM the rest of that line, I=E000-EBFF, which I did. When Pat is back from vacation he'll help us replace the method we used to use that imitates expanded memory.

8/16/95	Invalid Parameter message is still there, even though config.sys change was made.

8/18/95	PC-Gifts sent a disk to fix program so staff code will print in reports. After verifying everyone was out of PCG, I tried to apply the upgrade but received a message "Have 155,164 conventional memory available; need at least 200,000 bytes to apply upgrade." I left a message for Rob at CE to see if there is anything I can change in order to give me enough memory to apply the upgrade.

Sam from CE called back with a solution from Stephanie. I followed her advice and changed config.sys by removing RAM=4096 and adding NOEMS in its place (on the line containing EMM386.EXE). I rebooted; applied the PCG upgrade; changed config.sys back to reflect RAM=4096 & removed NOEMS; and rebooted again. The PCG upgrade fixed the staff code problem, too.

8/23/95	Spoke to Rob about the problem with EMS for PCG. (Kelly had problems yesterday apparently stemming from this also.) He will discuss with others to determine appropriate action to take and get back to us.

Rob downloaded a program to conduct a system documentation exercise via modem.

Today the copyroom network printer presented the same error message as the consultant room network printer did two weeks ago [18 MIO NOT READY]. Since the timing was so close and probably not a coincidence, did not order a replacement JetDirect card now. Unloaded the pserver at the system console and reloaded it. The printer came up normally and was functioning correctly.

8/24/95	Kelly reported that last night (8/23) the copy room printer again was down, with same message as earlier in that day. Today the message remains [18 MIO NOT READY]. Since Jerry (CE) was coming out to install CD- Rom drives, I asked him to take a look at the network devices in Netware to see if a setting was incorrect. (Coincidence that two printers gave same msg within two weeks of each other?) He noticed that two printers reported in pconsole the same printer number. Both Pat's and the Copy room's printer numbers were 0. He reassigned a printer number and now both printers are working fine.

8/30/95	Pat's workstation has been logging in incorrectly for at least two days. Upon logging into network via saber menu screen, the computer loads windows directly instead of asking Pat whether to Ctrl C to terminate (to go to pure DOS prompt) or to continue. After logging out, rather then going to the saber menu screen, takes Pat to u:\ dos prompt. Pat remains logged in, just Windows is closed. No other problems seem to be occuring. Today checked system login script, Pat's login script and security equivalences, (since only the supervisors are granted the particular command to allow a pure DOS prompt). These were all ok. Checked Pat's autoexec.bat file. The file had been changed: added WIN command as last line. Removed this line and rebooted, Pat now logs in correctly. Since Pat is unaware of why this occurred, will ask Jerry - CE when he arrives if he may have changed autoexec.bat when here last week.

9/7/95	Requested via fax upgrade to Internet in a Box 2.0.

Installed onto Chris' workstation (since library does not have CD-Rom yet) UMI's ProQuest 60 periodical record ordered by Bill Bergeron (CD set is a 30-day trial). Kept the installation CD with the database in case of return. If we keep it, should store installation CD with diskettes. There are significant notes in readme.txt left with Chris.

9/18/95	Jerry of CE installed the CD-Rom drives on models Dell P90 today (Dan, Bill, Dianne, Bob). The IBM models 77 need their reference diskettes for the installation but are missing from the office. Jerry will order 3 copies from IBM and return to install Hillel's and Library's.

9/19/95	Jerry returned with some IBM disks to try to finish the CD-rom install on Hillel's and library computers.

Installed Bookshelf '95 on Dan's, Bob's, workstations.

9/21/95	Rob - CE has been talking with Di at MicroEdge re the PCGifts need for expanded memory clashing with Windows. He had me try the following things:

Opened PCG-4.pif file in PIF editor and made changes; saved as PCGtest.pif. Created new program item in apps PCGtest to try it.

Edited config.sys in pure dos

(Incomplete notes. Rob will fax to me.)

Ameritech installed ISDN line at MJ's home for communications.

9/22/95	Calendar file became full again, could not move around or enter items. See u:\wp50\sysad\calendar.wpd file for instructions and memo to distribute.

Ameritech installed Fdn's ISDN line (MJ's office). Number is 297-9988.

9/25/95	Pat's workstation froze while loading windows first thing in the morning. Pat could log into and load windows at other computers. Windows froze on Pat's at the dialog box "Restoring connection to " (where it acknowledges each printer and its port). Had to ctrl alt del. Tried to power off and try again. Didn't work. Was able to log into network and pure dos prompt ok. Checked hardware cables from printer for proper connection. Examined *.ini files and autoexec.bat and config.sys in DOS for any obvious erroneous changes. The only change made to system Friday was to clear out the large calendar file on h: drive as noted above. Discused with Rob -CE over phone. He helped me check each parameter as it loads via F8 stop at "Starting MS DOS..." when rebooting. Error seemed to be with EMS configuration. Rob modified the config.sys file EMS line to run NOEMS again. Jerry came out to look at it. Discussed with Jerry the installation of Monarch demo software earlier last week, noting that it could run only with 16 colors and had to change video driver. Then changed driver back to hawkeye after finished with demo. He checked Windows settings via pure DOS, c:\windows\setup. Can change video driver or other windows setup commands there in DOS! Apparently Monarch demo software overwrote some windows files with things it required.

Jerry began installing MJ's office computer for communication station.

9/29/95	Dianne reported PCG problem of not being able to save her grant request which she had typed a writeup in. Remaining logged in as Di, I copied and pasted the write up to another grant (which PCG allowed me to do w/o any problem). Then closed the original grant and then closed PCG. Re-opened PCG with my login name and copied and pasted back the info from the other grant to the original grant. Saved fine. (Then opened up grant holding info temporarily and deleted the info from there.) Rebooted windows.

Bill Schambra reported continual trouble with PCG today, both morning and afternoon. It kept throwing him out with messages about "string" and out of memory. Also, a new message came up, unseen before, but PCG was closed before I could write it down. At that time he was using spell check (gave the command and it immediately broke out with the message and then the memory error before taking him completely out). The other problem was in trying to copy and paste betwen grants, something he has much experience with. PCG would throw him out just as he gave the command to paste. I checked to see which pif command he was running for PCG; it was pcgs.pif. I changed it to PCGtest.pif and checked to be sure he was not running EMS in the config.sys file (he wasn't).

10/3/95	Rob discussed with Pat the explanation of the PC-Gifts problem with Windows as he "discovered" in conjunction with MicroEdge. Their analysis: The problem we are experiencing now can be summed up as such: PC-Gifts (for DOS) and computer components with device drivers (software that allows physical components to communicate together like printers, harddrives, CD-Roms, etc.) utilize "base memory" differently and each wants to control the workstation configuration. The problems that we confront usually several times a week include the computer workstation "throwing" a user out of the system, losing valuable write-ups on PC- Gifts because no chance to save it was provided; erratic behavior of the software programs (it worked yesterday, but not today); frequent rebuilding of database indexes (first getting all users logged out for 30 to 60 minutes); inaccurate or difficulty running database reports; etc. While device drivers and PC-Gifts can "agree amongst themselves to coexist", they don't want to be operated simultaneously. Therefore, if we configure the computer workstation to function well for PC-Gifts use, there are problems with some of the hardware components that we now use. And vice versa. [Ironically, we expected fewer problems with the newer, faster, more technologically advanced pentium computers! However, the more abilities a computer has, the more software and device drivers are required to make things work together, like CD-ROM!]

Explanation: PC-Gifts requires the use of DOS' structure of expanded memory. The network drivers and (usually Windows) device drivers are designed only to use upper memory. In other words, PC-Gifts and device drivers use different methods of using memory in the computer system. If the workstation is configured to utilize expanded memory for PC-Gifts, the drivers are forced to load into low memory (instead of desired high memory). The result is less base memory available to run the programs using these drivers. Increasing the computer's memory will not help -- that's a different area of the computer.

Alternatives:

A.	Set up each workstation with a menu option upon booting up the computer so a user can specify with which configuration to run the computer -- PC-Gifts configuration for using expanded memory, or for devices like CD-Rom using high memory.

Positives:	More stable environment for the particular programs running under specific configurations.

Drawback:	Being forced to choose one configuration over another defeats the purpose of operating Windows. Often it is required by a computer user to have PC-Gifts open while looking into or working in other software program data files.

B.	More seriously consider at this time an upgrade to PC-Gifts for Windows.

Positives:	Finally, total integration between PC-Gifts and Windows. No more hassle with DOS share command or configuration problems.

OLE (high tech cut-and-paste) ability between PC-Gifts and other software programs, like WordPerfect.

Overall easier to operate from end-user standpoint.

Scanning option (to scan in proposals).

Negatives:	No checkbook available (OLE to Peachtree?).

Learning curve (operates quite differently from current program).

Customizing reports will require specific training on the part of support staff.

BASE MEMORY EXPLANATION FROM ROB (CE):

Expanded memory - exp mem takes only a little section of the high memory available (128K) between 512K and 640K (1 MG?), BUT locks it up so no other software can access it. Prevents anything from loading high.

Extended memory - uses the space between 512K and 640K (1MG?) (high mem) to push files up there that are running and need to be held temporarily. Allows Windows programs to load high.

Windows will run with expanded memory running, but will run a little slower and will be not able to optimize the available base memory for certain functions. Since we are trying to operate both PC-Gifts, a large program, and Windows programs, the expanded memory area fills and cannot load anything into the high area. CRASH!

10/4/95	This morning as all users logged into their workstations, the following situation occurred. While logging into the blue login screen, some DOS commands began operating automatically running for several seconds, then returned to the login screen. The second attempt to login was ok. After checking server console for error messages and last nights backup tapes for errors, and confirming that we are running on the A server, I phoned Rob. He explained that he had recently installed a documentation software program which is licensed to ComputerEase, not the Fdn, on the network that will initiate every quarter of the year to run a diagnostic program on each workstation as it is powered up on that date. (The program that actually runs on the workstations is a Microsoft product and probably doesn't involve legal issues.) Information is saved to a hidden network file named system\doc\ (username).rpt regarding each harddrive's condition. This info can be used by CE for tracing problems. It is important that the workstation be logged into with the correct user's name that normally uses that workstation.

10/11/95	The automatic documentation system activated again. This time, many users (not all) were not able to log in on the second attempt. On Dianne's, message read "Soundblaster 16 Incorrect MIDIPORT setting in the system.ini file". When accepted, could not load programs, error msg: "Working directory is invalid". Bob also experienced "Working directory is invalid". Bill S. and Pat were OK. Messages also stated "Insufficient memory to spawn Login.exe (56520)". Spoke to Rob on phone and he had me rem out the last command line in the system login script (which refers to the system documentation program). He will check it out the next time he is here.

10/13/95	Chris experienced a problem with her CD-Rom drive. It is unresponsive to the software commands to open a CD; says to insert the disk. (Like Bookshelf 95 and ProQuest.) File Manager shows nothing in the D drive even though the disk is in. The drive is difficult to open and close; must try several times. The disk shelf feels wobbly and a little crooked. Phoned Neil at Dell Customer Service; tech will be here Monday, 10/16/95. Service tag # on the computer is 4X1RO. Service reference #2512206 - tech will replace CD drive. ***REPLACED BY BANC TECH 10/13/95***

Ordered (and received) tech info and pricing on Monarch Software.

Ordered Peachtree 3.5 upgrade (gave literature to Karen to review and pay; ok'd by Bob). $9.95.

10/19/95	Jerry arrived 10:00 am. CD Rom parts not in; he worked on the ISDN line. At 11:50, he said he's done all he can do and its still not working. I insisted the "3rd party" installer was responsible for making it work and should be contacted and held accountable. He didn't know how to contact him; I suggested Lisa may have some information, too -- perhaps it just needs to be activated. Jerry suggested a regular phone line, but I said we feel an ISDN line is necessary. I also said if they can't make it work we have other people we can hire that will make it work.

Bill B. wanted to use the CD Rom at Pat's workstation. When attempting to log in, the screen came up "Access Denied." When I tried logging in with his name and password, the same thing happened. When I tried logging in with my name and password (to verify his password and check syscon settings), after running the usual system tests it got stuck at "Restoring Connections." I tried waiting for whatever connections it might be restoring to be complete, but after a few minutes I Ctrl/Alt/Del'd and tried to log in again with the same message resulting. Since Jerry was here working on the ISDN line, I asked him to look at it. The same thing occured when he tried to log in as CE. He did get into dos and checked the win.ini file. He placed a semi-colon in front of each line listed under the network section in order to "remove" the command. It worked fine when he tested it. I thanked him for his help.

10/20/95	Connie came down from Chipstone about 2:30 for Chris to show her around in the Organizer.

About 2:45, a man from the phone company came to fix the ISDN line in MJ's office. He left at 3:45 saying the Appleton end was using some wrong numbers and all is working now.

10/31/95	Jerry (CE) came in to introduce a new technician (Laura) and make the final configuration set-up for the ISDN line in MJ's office.

11/3/95	Noticed in the automatic backup of the network that it is taking longer and longer (inconsistently) to perform but there are not significantly more files. The speed of the backup performance is recorded in each job history; when backup speeds for various days checked against each other, it shows a slower performance is occuring. Attempted to print out a history record (to fax to ComputerEase for support) but could not find one anywhere in s:\ or f:\ and was unable to printout directly from the file server console, Backup Exec screen. According to the Backup Exec history log area, no logs exist. (?) Cleaned the backup tape drive with cleaning tape to see if improvement occurs. Check on Monday a.m. If no improvement, contact ComputerEase for support.

11/3/95	Pat was working in the network area, looking specifically at the various Saber elements, attempting to open certain files. At some point, even though I was working in pure DOS, the Windows files on my hard drive (c:\windows) were erased; the directory name remained. This was discovered only after attempting to load Windows upon completing my work in pure DOS. There was only a small bit of info left in system.ini (re the CD-ROM), and a file name I have never seen before, and some squiggly remarks. Windows was completely unusable, and probably not there. The software and other directories on C:/ appeared to remain intact. I was able to login at pure DOS again and load PC-Gifts and use it fine. But obviously, no Windows programs could be loaded. Jim Jaeger agreed to come and look at it first thing Monday 11/6/95 at 7:30am. He left around 8:30 or so after determining the machine would need to go to his office for reinstallation of Windows AND each windows software. (The softwares also need to be reinstalled because the "connection" between the drivers and *.ini files and Windows *.ini files are either blank or corrupted. He picked up the CPU at 2:45 pm Mon 11/6. He hopes to return it Tues or Wed at latest. At his instruction, I noted on a printout of each directory which softwares were installed by Dell, which were from network, etc. to guide the technician and also provided diskettes.

11/3/95	Bob Berkopec regularly experiences printer problems, either an error message that says Cannot access Input Output device, or the file appears to be printed but does not come out of printer. Also has trouble changing paper trays. The printer settings in ctrl panel revert back to 2 mg memory, even though the printer has 16 mg and is repeatedly set correctly. To try to make the printer control info more stable, Pat re-set Bob's Win.ini file to have the HP LPT1... information toward the beginning of the win.ini file (was at the very end).

At Bob's request, re-set his config.sys file to have the "numlock=on" button on when he powers up. (Don't know why his numlock doesn't come on but everyone else's does, even though the numlock instruction does not appear in the other config.sys files.)

11/13/95	File Server Netguard unit shows a message "AC 1 Fail" (left side opposite "Server A" indicator light). Phoned ComputerEase and spoke with Laura. After determining that we were up and running, she stated she will have Lisa call me to make an appointment to come out to examine it. I also told her I heard a couple times last week the tone a UPS unit gives off when kicking in; cannot see the indicator lights on unit because they are up against the wall. Also told her we are running at about 75% capacity.

11/15/95	Laura came but still could not finish CD-Rom install job for library and Hillel. Jerry said he gave IBM start-up disks to me, I think he has them. She will get another copy from IBM. Laura then checked the file server for the error message re power failure. The message was gone; after checking some things on the server, Laura suggested that its was a power surge that the UPS took care of. Also, discussed with Laura the Automatic documentation on file server --that it wasn't functioning properly and Rob had us rem it out of system login script. She said to leave it for now; may be clashing with something and may use something else. She also checked the file server storage space; we are at 90% capacity on vol1; the volumes cannot be reset (to move space from sys to vol1). She also reset my "sound", ok now. Also discussed backups and system running slow. Laura felt the backup may be running slower because the drive is almost full; also noted tapes are 6 months old; ordered new tapes and cleaning tape. She asked me to make a list of the particular softwares that run slow to evaluate other ideas.

11/15/96	Chris' trackball (mouse) has not been working properly for some time, appears to need repair on a spring. Probably cheaper to replace. Ordered new Logitech TrackMan direct. Should be here Wed 11/22/95. For temporary use, Chris installed an older (1992) style Microsoft Mouse (spare, unused) and installed also with software (from within Windows as directions stated). After logging in, computer would begin to identify mouse etc during loading Windows, but then come back out to blue login screen. Loading message appeared to refer to searching for mouse.drv at y:\! Checked autoexec.bat file and config.sys file. In pure DOS reinstalled the software from a:\ to c:\ to redirect from y:\. In autoexec.bat rem'd out line Set LMouse=c:\mouse (bcz refers to Logitch). Works OK now. Noticed that the f:\apps\windows\ directory contents are also mapped to y:\. Why is this? Perhaps will check with Laura when she comes in next.

11/17/95	On Laura's advice, (Yvonne) took the file server down first thing in morning so it could reset its short term memory, hoping the system would improve its speed performance. It seemed to help early in a.m., but by afternoon was same. Will check Organization with Laura in near future. Also issued memo regarding deleting old files from system ASAP to avoid completely filling up vol1.

11/21/95	Yvonne reports receiving an error message to "close an application due to insufficient memory to run ..." when she attempts to use the spell-check in WP 6.1 or open the Desktop component of Control Panel. Only had open the three applications always in use while using these features in the past: PC-Gifts, Lotus, WP 6.1. Was able to perform task upon closing an application. Also reports very slow to load WP 6.1 (a full 2 minutes) whether or not Organizer is open. Problem has existed for a while already (maybe 2 weeks?) and continues as of 11/22/95. Also, cannot open the "DOS prompt" via the Main icon without closing one of the three open applications; had not been a problem in the past.

SEE FILE SERVER NOTEBOOK FOR DETAILED INFORMATION REGARDING PROBLEM WITH EXTREME SLOWNESS ON SYSTEM.

Week of 11/20/95, when Jill attempted to login at blue screen, received message "unable to login, reason unknown". If this message appears again, run bindfix. (Jackie:CE).

Chris and Jill were unable to completely load PCG. Would hang for 15 minutes or more. No error message.

12/7/95	Bill Bergeron encountered a problem on Chris's workstation when trying to load WPWin 6.1 The following message appeared on the screen:

"WPWin Fatal Error

The necessary information to run an OLE 2.0 application cannot be found in the Windows registration database. WPWin cannot be executed without this information. Registering the information contained in Ole2.reg may fix this problem."

Bill had used WPWin 6.1 earlier in the day at this own computer. Windows loaded fine (at Chris'). All other programs loaded correctly. Found Ole2.reg file in f:\apps\windows\ole2.reg. Because the file appeared to be a text file or program associated with it (lines through the little icon next to file name) clicked on it twice to open. A message appeared that the registration database was successfully loaded. Was then able to launch WPWin 6.1. Unknown why this happened.

12/14/95	Jackie from C.E. arrived about 1:00 today and installed a new SMC Ether Power Card and updated driver (v1.13). This seems to have solved the problem with the network running slowly on server A. She checked the memory on the color printer; 24 MB currently installed (comes with 8, and 1 slot of 16 is being used). There is room for 48 MB additional, as 3 of the 4 16 MB slots are open. When she brought the server up, it halted while loading backup exec NML's. She tried again and all was fine. After running for about 10 minutes, the system crashed on a bend error. All workstations came to a halt and server B took over as expected. When Jackie rebooted server A, the system again halted while loading backup exec NML's. She tried again, successfully, but since 50% of the attempts halted today, she will check into an upgrade to the current version (v. 7.0) of back up exec. (Another C.E. customer has had file server crashes and has found this to be the problem and are about to install upgrade.) She will let us know the cost of the upgrade. Jackie left about 3:00.

About 4:30 Christina reported three problems: 1) "Not enough memory to perform undelete" in Microsoft Tools while trying to undelete; 2) OLE object not created; incorrect information about server in windows registration database (a WPWIN error); 3) was able to open document with a text object, but could not edit; message "no server for this object installed on this computer." She rebooted several times and continued to recreate these errors. She will try to recreate them from another workstation tonight. Yvonne called Jackie at C.E. to report problems. Chris mentioned the text object file was created December 6th; I noted that was while we were running on file server B and perhaps there is something amis with the way server A is set up. Jackie will look into that as well. I will let her know if the problems can be created from other workstations as well so we can narrow the problem down on Chris' specifically.

12/15/95	Chris was able to perform the tasks without problem at other workstations. Yvonne called Jackie to let her know it seems to be particular to Chris' workstation only. Chris verified she still could not perform those tasks and continues to receive the same error messages.

12/18/95	The Backup Exec did not perform a backup on Friday December 15, 1995. No error messages on server. The Job Manager does not appear to be loaded (at the list of screen options), however, can see at the console screen that "bemgr" was attempted to be loaded on 12/14 but message came stating already loaded, cannot reload. Phoned in to CE that no backup took place on Friday.

12/22/95	Ann's workstation was unable to create a system disk from DOS. After typing the command, a message appeared to insert a DOS diskette. After inserting either a blank diskette or a MS-DOS 5.0 diskette, would continue to give same message. Ann's version was IBM DOS 5.0. It would perform a regular format but not a format /s (for system). The library computer also has DOS 5.0 and did perform a format /s, but it is MicroSoft version, not IBM. Jackie from ComputerEase "upgraded" Ann's workstation's DOS from IBM DOS 5.0 to MS DOS 5.0 via diskettes we had on hand. (We did not have any MS DOS 6.2 diskettes on hand and Jackie didn't feel confident that copying DOS from a workstation to a diskette would be sufficient for something as important as an operating system.) The command to format /s now works fine; created the system disk as desired from Ann's workstation.

Will order DOS and Windows diskettes from Dell after 1/1/96 (because of possible shipping problems with move).