THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700


S U M M A R Y


DIARY: January 14, 1999 05:15 AM Thursday; Rod Welch

Fix CPU10, install w98 again, create boot disk on CPU11.

1...Summary/Objective
2...W98 Installed on CPU10 using CD ROM Disk for CPU11
3...Program Files on C: 00 Omitted
4...Transferred SDS Program and Diary Files
5...Configure Video Driver
6...Network using Netbui Configuration
7...Failure CPU11 Not Finding CPU10 on Network
8...IBM Dialer and Modem
9...Netscape Installation
10...Address Book
11...Bookmarks
12...Dial-up Access to Internet
13...Deskscan and Omnipage Software for HP Scanner on CPU10
14...Problem with Scanner
15...MS Project Installation
16...Visio Organization Chart Program Installation
17...Novaback Tape Drive Software Installation
18...Problem with Tape Drive


..............
Click here to comment!

CONTACTS 
0201 - Netscape Communications              650 937 2555
020101 - Mr. Scott NLN; Customer Support Rep
020102 - Technical Support =800 639 0939
020103 - Description
0202 - PCtown                               415 788 8696 fax 217 7731
020201 - Mr. Chris Grossman; Sales Executive
020202 - Sales Department

SUBJECTS
CD ROM Drive Failing
CD ROM, Toshiba 3501B & Soundblaster
Operating System Failed, Explorer.exe
Video System
Setup
CPU #10, W98

0908 -    ..
0909 - Summary/Objective
0910 -
091001 - Follow up ref SDS 13 0000, ref SDS 12 0000.
091002 -
091003 - Was able to install w98 and configure CPU10 so that everything works
091004 - the same as on CPU11.
091005 -
091006 -     [On 990116 did a back up with Exabyte tape drive. ref SDS 14 0000]
091007 -
091008 -     [On 990118 transfered data from CPU11 to CPU10, so the systems are
091009 -     the same. ref SDS 16 0000]
091010 -
091011 -     [On 990120 may have solved network problem. ref SDS 18 2304]
091012 -
091013 -     [On 990121 netbeui failed had to use TCP/IP. ref SDS 19 0000]
091014 -
091015 -
091016 -
091017 -  ..
0911 -
0912 -
0913 - Progress
0914 -
091401 -  ..
091402 - W98 Installed on CPU10 using CD ROM Disk for CPU11
091403 -
091404 - Yesterday, on 990113, I spent about 10 hours configuring CPU10 again,
091405 - to solve the problem reported on 981108, ref SDS 9 2636, again on
091406 - 980109, ref SDS 10 0000, and also on 990111. ref SDS 12 3600
091407 -
091408 - Yesterday I was finally able to install the operating system on CPU10
091409 - using the 1.44 M boot disk and the CD ROM disk for CPU11, as reported
091410 - on 981113. ref SDS 5 2596
091411 -
091412 -
091413 -  ..
091414 - Program Files on C: 00 Omitted
091415 - Transferred SDS Program and Diary Files
091416 -
091417 - After getting CPU10 running, I deleted all SDS program and diary
091418 - records and transferred from CPU11 so the two computers are the same.
091419 -
091420 - Since the network was not working correctly, ref SDS 0 3071, did the
091421 - transfer from CPU10.
091422 -
091423 -      [On 990522 appears that when this installation was done, I forgot
091424 -      to install c: 00, including Medit. ref SDS 20 0001]
091425 -
091426 -
091427 -  ..
091428 - Configure Video Driver
091429 -
091430 - Yesterday, I called Pctown about the video driver problem.  Chris said
091431 - to use the CD with the strange face that looks the same as the cover
091432 - for the S3 Vigera users manual.
091433 -
091434 - I formatted c and i.  This seemed to enable the installation CD to
091435 - work properly after about 5 - 10 tries.
091436 -
091437 - After installing the program, there is an error message on boot up,
091438 - you actually go into Safe mode, because the system does not
091439 - automatically recognize the video controller.  After the program goes
091440 - through another boot cycle from Safe Mode, open the Control panel and
091441 - open by double clicking on the Display option.  Another way to do this
091442 - is to right click anywhere on a blank spot on the desktop, and then
091443 - select Properties.
091444 -
091445 - In the Display properties window, select the Settings tab at the top
091446 - of the window.  In the Settings window, click on Advanced near bottom
091447 - of this window.  In the Advanced window, select the tab for Adapter at
091448 - the top of the window.  In the Adapter window, select Change, after
091449 - first putting the S3 Viegra CD in the CD ROM drive.
091450 -
091451 -
091452 -
091453 -
091454 -
0915 -

SUBJECTS
Network, W95, EtherPCI
Ethernet Card, Fast EtherLink XL, PCI
Network, EtherPCI LAN
Network Computers
Network Setup Using Passwords for W95 Logon
Netbui
Network Failing on CPU11

1610 -
161001 -  ..
161002 - Network using Netbui Configuration
161003 -
161004 - Follow up ref SDS 7 8096. ref SDS 6 1261.
161005 -
161006 - Will try record on 981114 for setting up CPU11. ref SDS 7 8096
161007 -
161008 - Looks like instructions are in record on 970116. ref SDS 1 3242
161009 -
161010 - The basic process is to install netbui from within Network
161011 - Properties.
161012 -
161013 - Then set sharing for each drive.
161014 -
161015 - Open Network folder.
161016 -
161017 - The other CPU should be listed.
161018 -
161019 - Double click to open the folder, and map each drive for access on the
161020 - local CPU.
161021 -
161022 - Our objective is to connect computer, at this moment, CPU10 to CPU11,
161023 - in order to transfer files directly between them.  We have a PCI
161024 - network adpater card.  We need software configurtion. This entails a
161025 - "protocol" which in this case is...
161026 -
161027 -                            netbui
161028 -
161029 -      [On 990121 netbeui failed had to use TCP/IP. ref SDS 19 0000]
161030 -
161031 -      [On 990808 netbui failed on Kath's computer. ref SDS 21 6149]
161032 -
161033 -      [On 990808 direct cable worked. ref SDS 21 6933]
161034 -
161035 - Instructions for configuration are in a document that comes with the
161036 - network card, as explained in the record on 970116. ref SDS 1 5640
161037 - ..
161038 - That instruction says to enter a password only for mapping the
161039 - last drive, in this case i.
161040 -
161041 -
161042 -
161043 -  ..
161044 - Failure CPU11 Not Finding CPU10 on Network
161045 -
161046 - For some reason CPU10 is not showing up as a network drive on CPU11.
161047 -
161048 - CPU11 is listed and there is access to it on CPU10.
161049 -
161050 - On 990108 there are instructions on maping drives. ref SDS 9 2397
161051 -
161052 - I mapped the drives on CPU10.
161053 -
161054 - I changed the identification of CPU10 from 10 to 08, and this enabled
161055 - CPU11 to recognize CPU10 and so I can transfer files.
161056 -
161057 -     Further analysis on subsequent date, indicates the problem may
161058 -     have been that TCP/IP Address was not set as explained in the
161059 -     record on 970106. ref SDS 1 0876
161060 -
161061 - However, after awhile, this no longer worked.
161062 -
161063 - CPU10 continued to see CPU11, but CPU11 was not accessing the disk
161064 - and files on CPU10, even though I identified it as 08.
161065 -
161066 - CPU11 showed itself, but did not show CPU10 in the Network list.
161067 -
161068 - CPU10 showed CPU11 in the network list, but did not show itself.
161069 -
161070 - When CPU11 is shut down, the operating system reports being connected
161071 - on the network, which seems to conflict with the failure to find any
161072 - of the drives across the network on CPU10.
161073 -
161074 - Over the span of a day, I tried mapping the drives over.  Eventually,
161075 - I changed the identification of CPU10 back to "10".
161076 - ..
161077 - The next day, for some unknown reason, CPU11 and CPU10 now each
161078 - show both themselves and the other in the Network list, and everything
161079 - is working properly.  I can transfer files from CPU11 to CPU10, and on
161080 - CPU10 I can transfer files to CPU11.
161081 -
161082 -      [On 990120 had similar experience. ref SDS 18 3895]
161083 -
161084 -      [On 990121 netbeui failed had to use TCP/IP. ref SDS 19 0000]
161085 -
161086 - Maybe the processing that occurred in changing the identification,
161087 - caused the w98 register to reset itself.
161088 - ..
161089 - I took a nap for a few hours, and when I resumed work, the same
161090 - problem occurred described above. ref SDS 0 3071
161091 -
161092 - I called Morris on Saturday, and discussed whether the suspend mode
161093 - causes the operating system to loose track of networked computers?
161094 -
161095 - He indicated the network is impacted by suspend mode, and suggested
161096 - shutting each system down and starting them again.
161097 -
161098 -      [On 990120 the network connection was restored during suspend
161099 -      mode on CPU10. ref SDS 18 3895]
161100 -
161101 - This did not solve the problem.
161102 -
161103 - It appears that we had a similar problem on 981114. ref SDS 7 1952
161104 -
161105 - In that case, there were some drives that had not been configured as
161106 - "Full shared access" using the procedure on 970116. ref SDS 1 3410
161107 -
161108 - I decided to change the configuration of the last drive on CPU10 by
161109 - adding a password, which was not done, per above. ref SDS 0 5218
161110 -
161111 - This did not seem to solve the problem.
161112 -
161113 -     [On 990118 mouse pointer changing symbol. ref SDS 17 0000]
161114 -
161115 -
161116 -
1612 -

SUBJECTS
Modem, U.S. Robotics Sportster 56K Fax
Dialer, IBM, W95

2105 -
210501 -  ..
210502 - IBM Dialer and Modem
210503 -
210504 - Follow up ref SDS 7 9640.
210505 -
210506 - This installs in...
210507 -
210508 -                       h: 00 19
210509 -
210510 - I copied from CPU11 the latest setup.exe file downloaded from IBM
210511 - yesterday.
210512 -
210513 - When this installed, it found that the modem was not configured.
210514 -
210515 - Setup automatically initiated a w98 wizard routine to configure the
210516 - modem.  This asked for where to look for software drivers.
210517 -
210518 - I assumed the drives would be on the w98 CD disk and so designated the
210519 - CD ROM drive to look for drivers in addition to the hard drive.
210520 -
210521 - Installation completed.
210522 -
210523 - I tried the dialer and got a message that the modem was not properly
210524 - connected.  The indication was that the hardware was defective.  An
210525 - example is that the modem was not adequately seated in the motherboard
210526 - slot.
210527 -
210528 - Control Panel - Modems
210529 -
210530 - I doubled clicked on the modem listing in the Control panel.
210531 -
210532 - This opens Modem Properties
210533 -
210534 - It showed the modem connected to COM1.  I looked at the same listing
210535 - on CPU11, and it showed the modem is connected to COM2, which
210536 - indicates a possible configuration problem, rather than a hardware
210537 - installation problem.
210538 -
210539 - I clicked on the Diagonstics tab in Modems Properties.
210540 -
210541 - Clicked "Help" in Diagnostics.
210542 -
210543 - There is a "Troubleshooter" list of questions to identify the type of
210544 - problem.
210545 -
210546 - Clicked the first question...
210547 -
210548 -         Windows 98 doesn't detect my modem.
210549 -
210550 - Scrolled to the bottom and clicked "Next>"
210551 -
210552 - The next screen asks...
210553 -
210554 -     Is your modem connected correctly?
210555 -
210556 -     Conslut your modems's documentation to verify that your modem is
210557 -     installed correctly and that any cables are secure.
210558 -
210559 -     Did this solve your problem.
210560 -
210561 - I clicked on "No."
210562 -
210563 - The next screen asks...
210564 -
210565 -     Are there any resource conflicts?
210566 -
210567 - There is an explanation to examine "System" in Control Panel, and look
210568 - under the Device Manager tab.
210569 -
210570 - Look for devices with an exclamation point symbol in a yellow circle,
210571 - because this indicates a device conflict.
210572 -
210573 - We had that problem.
210574 -
210575 - I double clicked on the modem listing in the Control Panel again.
210576 -
210577 - I clicked on the "Remove" button.
210578 -
210579 - This removed the incorrect configuration of the modem.
210580 -
210581 - I clicked on "Add"
210582 -
210583 - This brought up the operation to install the modem again.
210584 - ..
210585 - When I went through the installation again, I noticed a system
210586 - comment that a driver was not found on the A: drive.
210587 -
210588 - I checked the box with manuals and disks for CPU10.  There is a disk
210589 - marked "U.S. Robotics Driver.
210590 -
210591 - I put this in the A: drive and started in the setup operation again.
210592 -
210593 - The installation operation found a driver and configured the modem
210594 - correctly, so it is on COM2, the same as CPU11.
210595 -
210596 - The Device Manager in System in Control Panel no longer showed the
210597 - exclamation point symbol in a circle, which signifies a resource
210598 - conflict.
210599 -
210600 - I tested the IBM Dialer.  It found the modem and successfully
210601 - connected to the Internet.
210602 -
210603 - Decided to put these drivers on the hard disk.
210604 -
210605 -
210606 -
210607 -
2107 -

SUBJECTS
Installation
Netscape, 4.04 W95
Book Marks Import

2406 -
240601 -  ..
240602 - Netscape Installation
240603 -
240604 - Follow up ref SDS 7 9922.
240605 -
240606 - Use instructions from work on 981114 to install Netscape on CPU11.
240607 -
240608 - This simply requires executing from the file listing in Explorer on
240609 - the file ...
240610 -
240611 -                      h: 00 07 cc32e45.exe
240612 -
240613 -    ...which was downloaded the other day.
240614 -
240615 -
240616 -  ..
240617 - Address Book
240618 -
240619 - Follow up ref SDS 7 2852.
240620 -
240621 - Used instructions from work on 981114 at ref SDS 7 2852 to transfer
240622 - the address book.
240623 -
240624 -     [On 990116 discovered that Netscape has new way of organizing user
240625 -     files. ref SDS 15 0888]
240626 -
240627 -
240628 -
240629 -  ..
240630 - Bookmarks
240631 -
240632 - Follow up ref SDS 7 2808.
240633 -
240634 - For some reason when Netscape was installed, it did not include
240635 - bookmarks that were already on the system.
240636 -
240637 - There is a record on 981114 of contacting Netscape. ref SDS 7 2808
240638 -
240639 - I tried copying from CPU11 to CPU10 the files...
240640 -
240641 -            h: 00 07 Users Internet usinet rowelch bookmark.htm
240642 -
240643 -            h: 00 07 Users Internet usinet rowelch abook.nab
240644 -
240645 - This did not solve the problem.
240646 -
240647 -
240648 -  ..
2407 -
2408 -
2409 - 1435 called Netscape
2410 -
241001 - Talked to Paul.
241002 -
241003 - He said that even though we copied the bookmark file to the user
241004 - directory, we have to then import it to the bookmark program code
241005 - with the following steps.
241006 -
241007 - In the Browser, click on Bookmarks.
241008 -
241009 - Select Edit
241010 -
241011 - In Edit, click on the File menu.
241012 -
241013 - To save the bookmarks, click...
241014 -
241015 -       Save as
241016 -
241017 - It will create a filename...
241018 -
241019 -                          bookmark.htm
241020 -
241021 - ... I changed the save directory to...
241022 -
241023 -                          c: sd 10
241024 -
241025 - To Import the bookmark file, transfer bookmark.htm to the target
241026 - computer.
241027 -
241028 -
241029 - In File, select Import.
241030 -
241031 -       Select the file bookmark.htm
241032 -
241033 -   This could be on another computer, or you can copy it to the
241034 -   current computer over a network, or with the a: drive.
241035 -
241036 -
241037 -
241038 -
2411 -

SUBJECTS
Dial-up Network Connection
Ws_ftp
Installation

3106 -
310601 -  ..
310602 - Dial-up Access to Internet
310603 -
310604 - Follow up ref SDS 7 0206.
310605 -
310606 - This is actually an alternate route for accessing the Internet, since
310607 - the IBM dialer program is adequate.  This gives us two different paths
310608 - to the Internet.
310609 -
310610 - Used record configuring CPU10 on 980317. ref SDS 3 0000
310611 -
310612 - Installed ws_ftp pro that is used for uploading files to the web site.
310613 - This is the new program received on 981110, per ref SDS 4 9360. It
310614 - was installed on CPU11, but not on CPU10, so this is an improvement
310615 - for CPU10.
310616 -
310617 - I was able to make the installation across the network, by executing
310618 - the installation file on CPU11...
310619 -
310620 -                  q: 00 41 instl inst32.exe
310621 -
310622 - I then created an installation directory on CPU10 as well.
310623 -
310624 -
310625 -
310626 -
3107 -

SUBJECTS
Omnipage Pro v 7.0 for W95 Only
Deskscan for HP ScanJet IIc VER A.01.01,
Scanner
Scanner Not Found by W98

3807 -
380701 -  ..
380702 - Deskscan and Omnipage Software for HP Scanner on CPU10
380703 -
380704 - Follow up ref SDS 8 0000.
380705 -
380706 - Decided to install Omnipage on CPU10 even though it is in Concord and
380707 - is not connected to the scanner.  There may come a time when it is
380708 - needed, so might as well go ahead and make both computers have the
380709 - same configuration.
380710 -
380711 - Installation requires a two step process.  We need...
380712 -
380713 -       1.  Drivers for the deskscan program that runs the scanner.
380714 -
380715 -       2.  Omnipage which a text recogniation program that uses
380716 -           deskscan.
380717 -
380718 - Installation on CPU11 is reported on 981114. ref SDS 7 0780
380719 -
380720 - It turned out that to run the scanner on a PCI scsi controller, we
380721 - needed new drivers from HP.  Installation of updated deskscan drivers
380722 - and the Omnipage program itself is reported on 981120. ref SDS 8 4158
380723 -
380724 -  ..
380725 -
380726 - Problem with Scanner
380727 -
380728 - I installed the HP drivers, but w98 does not seem to be recognizing
380729 - the scanner.
380730 -
380731 - On CPU11, the Device Manager in System under Control Panel lists the
380732 - scanner, but it is not listed on CPU10.
380733 -
380734 - I tried Add Hardware.  W98 does not find the scanner attached, which
380735 - indicates the cable connection is bad or the scsi controller on CPU10
380736 - is not working correctly with the scanner.
380737 -
380738 - I ran Add Hardware twice.  On the second pass, it found the Exabyte
380739 - tape drive, but it should have already found it, so that was not a
380740 - great achievement.  It did not find the scanner.
380741 -
380742 - I tried to use the manual device selection process, and selected
380743 - Imaging Device.  It opened a screen that listed Kodak.  I clicked on
380744 - Have Disk, and selected the J drive which has the HP CD, that I
380745 - already installed.  Got an error message saying it does not have the
380746 - stuff w98 wants to recognize the scanner.
380747 -
380748 - We have a Jaz Jet driver disk.  I tried to install it using
380749 - instructions on the readme file, but w98 reported its own driver is
380750 - the "best driver" and it is already installed, so I did not install
380751 - anything on this disk.
380752 -
380753 - As a result, I did non install Omnipage.
380754 -
380755 -
380756 -
380757 -
3808 -

SUBJECTS
MS Project, CPU #10, MS W98

4004 -
400401 -  ..
400402 - MS Project Installation
400403 -
400404 - Follow up ref SDS 7 3510.
400405 -
400406 - Used the record on 981114 for installation on CPU11, ref SDS 7 3510,
400407 - to configure MS Project on CPU10.
400408 -
400409 - I copied the files from CPU11 in...
400410 -
400411 -                    i: 00 02 04
400412 -
400413 -     ...to CPU10, so that MS Project installation program would
400414 -     recognize we already have a program installed.
400415 -
400416 - Then ran the setup program using the installation disks.
400417 -
400418 -     [On 000620 installed on C12 and then to C11 again because these
400419 -     systems are now using W2K. ref SDS 22 0001
400420 -
400421 -
400422 -
400423 -
4005 -

SUBJECTS
Visio, V 4.0 SN:  117 713 042036

4204 -
420401 -  ..
420402 - Visio Organization Chart Program Installation
420403 -
420404 - Follow up ref SDS 7 8388.
420405 -
420406 - The code for this program is already installed on CPU10 in...
420407 -
420408 -                    g: 00 15
420409 -
420410 - I moved it from g: to...
420411 -
420412 -                    i: 00 15
420413 -
420414 -    ...so it is consistent with CPU11. ref SDS 7 8388
420415 -
420416 -
420417 -
420418 -
4205 -

SUBJECTS
Novaback W95 SN: 11701-SCSI, 970207
Tape Backup, Exabyte 10 GB

4505 -
450501 -  ..
450502 - Novaback Tape Drive Software Installation
450503 -
450504 - Follow up ref SDS 2 2459.
450505 -
450506 - On 980103 had needed terminator pins to install Exabyte tape drive in
450507 - CPU10. ref SDS 2 2459
450508 -
450509 - I really don't have to install the Exabyte tape drive because it is
450510 - already installed, but this link may be useful to find this
450511 - information at some future time.
450512 -
450513 - I used the Novaback CD disk.  It initially said the program is not
450514 - compatible with w98, and to contact Exabyte about getting updated
450515 - software.  A web site address is given to get information about
450516 - updating software for compatibility with w98.  I checked the web site,
450517 - but could not find anything on this subject.
450518 -
450519 - We have been using this version of Novaback with w98 configuration for
450520 - nearly a year.  It has seemed to work correctly.
450521 -
450522 - I therefore went ahead and ran installation.  Put the program on...
450523 -
450524 -                      h: 00 34
450525 -
450526 - Formerly it was on i: 00 34 01 -- but it seems useful to have it on
450527 - h:, so if the operating system has to be reinstalled again, it may not
450528 - require installing Novaback again, similar to Visio.
450529 -
450530 - This version of Novaback is for an Exabyte SCSI interface, rather than
450531 - the Qic version.
450532 -
450533 -  ..
450534 -
450535 - Problem with Tape Drive
450536 -
450537 - After installation, I ran the program and got an error message saying
450538 - the tape drive was not recognized.  There was a recovery procedure
450539 - for "configuring the SCSI controller."
450540 -
450541 - I ran it.
450542 -
450543 - The tape drive now seems to be working.  I did a test by building an
450544 - index for tape 13.  It is an extra tape, so if it is messed up it
450545 - will not cause a problem.
450546 -
450547 - It seems to be running okay.
450548 -
450549 - Maybe this explains the problem with the Scanner, the SCSI card needed
450550 - to be "configured." ref SDS 0 2754
450551 -
450552 - For some reason
450553 -
450554 -     Control Panel
450555 -        System
450556 -           Device Manager
450557 -              Tape Drive
450558 -
450559 -                  This lists 7 Exabyte tape drives.
450560 -
450561 -    I deleted 6 so we have only a single listing.
450562 -
450563 - Tested tape drive again.
450564 -
450565 -
450566 -
Distribution. . . . See "CONTACTS"