THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: March 2, 2000 08:54 AM Thursday; Rod Welch

C11 repair today by Mountain Computer.

1...Summary/Objective
2...C11 - Scope and History of Problems
3...Removed System Circuit Boards - System Would Not Boot
4...Reset BIOS - Did Not Clear Problem
5...ASUS P2B AGP Mainboard Missing BIOS Reset Jumpers
6...Memory Tested by Swapping from Another Computer, Seems Okay
7...Hard Drives Removed
8...Dust is Moderate, Not an Evident Cause of Problems
9...Motherborad Shows No Visible Signs of a Problem
10...Motherboard, Video Connected Outside the Case, System Booted
.....Insulator Washers Missing for Motherboard Connection to Case
11...CPU Not Fully Seated Due to Interference, May be Cause of Problems
12...Power System Fails During Re-assembly
......Power On/Off Switch Would Not Work -- New Problem
13...Order of Connecting Devices to Power Supply Fixed Problem????
14...Device May be Defective Causing Improper Power Distribution
15...Technical Work Debugs Mistakes in Real-Time
16...Management Defers Mistakes, Communication Biggest Risk in Enterprise
17...Motherboard Replace, ASUS P2B May Be Defective
18...A new motherboard would cost about $120, plus installation of an hour.
19...Windows 2000 Upgrade Potential
20...Exabyte 10 GB Tape Drive Installed in CPU11 from CPU08
21...Network on CPU10 Network to CPU11 Using TCP/IP Rather than Netbui
22...Downloaded 3Com Drivers for CPU10

ACTION ITEMS.................. Click here to comment!

1...Eric proposed a case that allows the motherboard to slide out for

CONTACTS 
0201 - Mountain Computer Engineering                                                                                                                                      O-00000701 0201
020101 - Mr. Bradley J. Schwab; Director of Engineering
020103 - Engineering Department                                                                                                                                           O-00000701 0201
0202 - Mountain Computer Engineering                                                                                                                                      O-00000701 0305
020201 - Mr. Eric M. Maxwell; Network Engineering
020203 - Technical Department                                                                                                                                             O-00000701 0305

SUBJECTS
CPU11 Boot Failure, On\off Fails, Suspend Mode Problem
Motherboard, ASUS Pentium II 450 Mhz, ATX

0504 -
0504 -    ..
0505 - Summary/Objective
0506 -
050601 - Follow up ref SDS 44 0000, ref SDS 43 0000.
050602 -
050603 - Eric disassembled C11 and found no evident cause of failure.
050604 - ref SDS 0 1530   After removing all components from the case, he got
050605 - the system to boot by connecting key parts laying on the desk.  This
050606 - required removing and replacing the microprocessor from the mainboard,
050607 - several times.  He saw a thin plastic element attached to the external
050608 - case of the Pentium II processor, and decided it was not needed, so he
050609 - removed this element.  The CPU then seemed to seat further into the
050610 - motherboard socket. ref SDS 0 0867  This may have caused the problems.
050611 - After assembling all of the parts in the case, the system would not
050612 - power up.  With ideas from the MCE office, Eric connected power to
050613 - divices in a sequence that resulted in power up. It now seems to run
050614 - okay, but there is suspicion that the main board or a device, may have
050615 - a defect. ref SDS 0 4717  Eric installed the Exabyte tape drive from
050616 - C08 in CPU11. ref SDS 0 9077  He networked C11 with C10. ref SDS 0
050617 - 9077
050619 -  ..
050620 - Received and paid invoice for $262. ref SDS 0 7128
050622 -  ..
050623 - MPE will submit a quote for an upgraded motherboard, case and 128M of
050624 - memory.
050626 -  ..
050627 - Submitted ref DIT 1 0001 linked to this record.
050628 -
050629 -    [On 000304 CPU11 failed again. ref SDS 46 0001]
050630 -
050631 -    [On 000306 called to expedite quote. ref SDS 47 0001]
050632 -
050633 -
050634 -
050635 -
0507 -
0508 -
0509 - ŽDE32 Discussion
0510 -
051001 - Brad said someone will visit this morning.
051002 -  ..
0511 -
0512 -
0513 - 0910 Eric arrived
051401 -  ..
051402 - C11 - Scope and History of Problems
051403 -
051404 - We reviewed the record explaining the problem and background reported
051405 - on 000229. ref SDS 43 0780
051406 -
051407 - The case was already removed and the CPU was sitting on the conference
051408 - table, next to CPU10, which we used to capture the record.
051409 -
051411 -  ..
051412 - Removed System Circuit Boards - System Would Not Boot
051413 -
051414 - Eric initially removed the video card to see if the system would beep
051415 - when powered up, which would indicate a problem with the controller.
051416 - Eric said this is a common cause of boot problems.
051417 -
051418 - He pressed the power on button. The system exhibited signs of having
051419 - power, reported on 000229, ref SDS 43 6348, but the system did not
051420 - beep.
051422 -  ..
051423 - Eric unplugged the power to turn shut the system off, then plugged it
051424 - back again.
051426 -  ..
051427 - He removed all of the cards, except the video card, and pressed the
051428 - powered switch to power up.
051429 - ..
051430 - The system did not beep and did not come up. He unplugged the
051431 - power again to shut the system down.
051432 -
051434 -  ..
051435 - Reset BIOS - Did Not Clear Problem
051436 - ASUS P2B AGP Mainboard Missing BIOS Reset Jumpers
051437 -
051438 - Eric tried to reset the BIOS, but could not find a jumper on the
051439 - motherboard for this purpose.  He showed the ASUS P2B manual shows a
051440 - jumper to reset the BIOS, but this jumper is not at the location shown
051441 - in the manual, and there is no other evident jumper on the board for
051442 - this purpose. Therefore, he removed the CMOS battery and replaced it,
051443 - which has the same effect.
051444 -
051445 -     How do we restore BIOS configuration to what it was before Eric
051446 -     reset it.  Is this necessary?
051448 -        ..
051449 -       [On 000310 installed new motherboard, so this issue is moot.
051450 -       ref SDS 49 2068
051452 -  ..
051453 - This did not clear the boot problem.
051454 -
051456 -  ..
051457 - Memory Tested by Swapping from Another Computer, Seems Okay
051458 -
051459 - Eric removed the memory SIM and installed a memory SIM from CPU10, to
051460 - see if there is a problem with the memory.
051461 -
051462 - The problem remained, indicating the memory is not the problem.  He
051463 - restored the memory to CPU10 and CPU11.
051464 -
051465 -
051467 -  ..
051468 - Hard Drives Removed
051469 -
051470 - He disconnected the drives, and booted the computer.
051471 -
051472 - This did not clear the boot problem; power on switch would not boot
051473 - the computer.
051474 -
051476 -  ..
051477 - Dust is Moderate, Not an Evident Cause of Problems
051478 - Motherborad Shows No Visible Signs of a Problem
051479 -
051480 - Eric removed the CPU from the motherboard, and then removed the
051481 - motherboard from the case to examine it.
051482 -
051483 - No visible evidence of a problem was found on either side of the
051484 - motherboard.
051485 - ..
051486 - We reviewed consideration of whether excessive dust may have
051487 - caused a short, raised in the record on 000226. ref SDS 41 0987
051489 -  ..
051490 - Eric advised that the dust condition in CPU11 is moderate.  He has
051491 - seen much worse, without impacting performance.  He believes dust is
051492 - not causing the problems CPU11 exhibits.
051493 -
051494 -
051496 -  ..
051497 - Motherboard, Video Connected Outside the Case, System Booted
051498 -
051499 - With the parts all removed from the case, Eric installed the CPU and
051500 - the video card in the motherboard.  He connected the power supply to
051501 - the motherboard sitting on the desk.
051502 -
051503 - He used a metal screw to jumper the power up pins on the motherboard.
051505 -  ..
051506 - The system powered up.  We got a display on the monitor, something
051507 - that has been missing since Tuesday morning. ref SDS 43 0780
051509 -  ..
051510 - So, we have some progress at last.
051511 -
051513 -      ..
051514 -     Insulator Washers Missing for Motherboard Connection to Case
051515 -
051516 -     Eric noticed there are no washers for insulating the motherboard
051517 -     from the stanchions used to elevate the motherboard so it does not
051518 -     touch the metal case frame when fastened with screws into the
051519 -     stanchions.  He said this is a typical configuration that normally
051520 -     works, but it may be a problem in this situation.
051522 -      ..
051523 -     There is no other explanation for the system we have hit upon for
051524 -     the system not to power up.
051526 -      ..
051527 -     Eric does not have washers he feels might be needed.  He thinks
051528 -     there may be some in his shop.  He suggested a new case, but again
051529 -     noted that this case configuration typically works okay, and since
051530 -     the computer has run for the past 14 months, this is not likely
051531 -     the cause of the problems reported on 000229. ref SDS 43 0001
051533 -      ..
051534 -     A new case would cost about $60, plus an hour for installation.
051536 -      ..
051537 -     Eric proposed a case that allows the motherboard to slide out for
051538 -     service.
051539 -
051540 -         I asked about using the case for CPU08?
051541 -
051542 -         Eric said the form factor for CPU08 does not match the parts
051543 -         in CPU11.
051544 -
051545 -
051547 -  ..
051548 - CPU Not Fully Seated Due to Interference, May be Cause of Problems
051549 -
051550 - Eric also noticed in replacing the microprocessor in the motherboard
051551 - slot, that there was a thin, black plastic element connected to the
051552 - Pentium processor, running the length of the processor along the
051553 - motherboard socket.  This element has the word...
051554 -
051556 -                           ..
051557 -                          AMOCO
051558 -
051559 -
051560 - ...imprinted on one side.  He removed this plastic element from the
051561 - processor believing it serves no evident purpose.  When he replaced
051562 - the processor into the motherboard socket, Eric reported that it
051563 - seemed to seat more fully into the motherboard slot.
051565 -  ..
051566 - Eric said he thinks cause of the system not function properly,
051567 - beginning on 000229, ref SDS 43 0001, is that the microprocessor was
051568 - not fully seated in the motherboard socket.
051570 -  ..
051571 - He is unsure why the system has functioned normally since 981115,
051572 - until two days ago.
051574 -  ..
051575 - Eric proposed that the system has been marginally okay, and we may
051576 - have moved it recently, causing the connection to fail slightly with
051577 - erratic impacts. Eric reviewed the record on 000212 showing the problem
051578 - with the mouse and keyboard. ref SDS 36 0001  He feels those problems
051579 - could arise from the CPU not being fully seated in the motherboard
051580 - socket.
051582 -  ..
051583 - We reviewed history of the CPU having been taken to Saratoga, and so
051584 - it received moderate handling for that purpose 6 or 7 months ago. The
051585 - CPU has been taken in for service twice.  Once for a new CPU fan, and
051586 - another time to swap out the CD ROM drive. On all of these occasions
051587 - the CPU was picked up, possibly turned up side down, and so forth.
051588 - This handling did not cause the monitor, the keyboard and the power
051589 - on/off switch problems encountered on 000229, nor the mouse and to a
051590 - lessor extent keyboard failures reported on 000212. ref SDS 36 0001
051592 -  ..
051593 - Eric said there is no evident explanation. Possibly temperature
051594 - changes effected a tenuous connection.
051595 -
051597 -  ..
051598 - Power System Fails During Re-assembly
051599 -
051600 - After concluding no evident problems exist with the motherboard, per
051601 - above, ref SDS 0 0897, Eric restored it in the case and assembled the
051602 - other circuit boards.
051603 -
051604 - He also installed the Exabyte tape drive from CPU08, in CPU11, per
051605 - below. ref SDS 0 9077
051607 -  ..
051608 - After everything was back together, the power would not come up.
051609 -
051611 -  ..
051612 -
051613 -      Power On/Off Switch Would Not Work -- New Problem
051614 -
051615 -      This is different, but similar to original problem.  In the
051616 -      original problem, repored on 000212, ref SDS 36 0001, that
051617 -      occurred again on 000229, the Power On switch causes the power
051618 -      supply to start the hard drive and the status lights, but the
051619 -      rest of the boot sequence fails, including not reading the a:
051620 -      drive; and, the Power switch will not turn the system off.
051621 -      ref SDS 43 6348
051623 -       ..
051624 -      In this case, the Power On switch was not causing anything
051625 -      to happen.
051626 -
051627 -         [On 000310 similar problem after assembling new motherboard.
051628 -         ref SDS 49 4158]
051630 -  ..
051631 - Eric began removing cards and checking them one by one.  He finally
051632 - removed and then replaced the power supply connection to the
051633 - motherboard.  The system then came up.  This suggests that the power
051634 - supply was not fully seated when he replaced the motherboard after the
051635 - prior step. ref SDS 0 3053
051637 -  ..
051638 - I originally thought that we had a Power Supply issue, yet when we
051639 - installed the power supply from a known working computer (CPU10),
051640 - CPU11 still had the same problem.
051641 -
051643 -  ..
0517 -
0518 -
0519 - 1115 called MCE office
0520 -
052001 - Called and talked to JT in the office, who, in turn, consulted with
052002 - Brad, on difficulties solving the CPU11 problem. ref SDS 0 3053
052004 -  ..
052005 - JT and Brad thought that a device may be causing the power supply to
052006 - overload.
052007 -
052008 -
052010 -  ..
052011 - Order of Connecting Devices to Power Supply Fixed Problem????
052012 -
052013 - To implement suggestions from JT and Brad, ref SDS 0 8588, Eric tried
052014 - connecting power to the devices in different combinations.
052015 -
052016 -   1.  Disconnected all devises from the power supply and connected
052017 -       them back one by one to test each one in combination.
052018 -
052019 -       a.  Connected the hard drive and powered it up, and it worked.
052021 -            ..
052022 -       b.  Connected the floppy drive with the hard drive.  That
052023 -           worked.
052024 -           ..
052025 -       c.  Connected the CD ROM drives, with hard drive and
052026 -           floppy drive.  This failed.
052028 -            ..
052029 -           Power On/Off switch would not work, replicating problem
052030 -           explained above. ref SDS 0 3085
052032 -            ..
052033 -           Eric disconnected and reconnected this configuration several
052034 -           times to verify it would not run, and got the same result.
052035 -       ..
052036 -   2.  Changed order of connecting devices.
052037 -
052038 -       Eric disconnected all devices from the power supply.
052039 -
052040 -       a.  Connected only the CD ROMs, which failed in step 1b.  The
052041 -           system powered up with the CD ROMs connected first.
052042 -
052043 -       b.  Connected hard drive with the CD ROM drives, and this
052044 -           worked.
052046 -            ..
052047 -       c.  Connected the floppy drive, with the CD ROM drives and the
052048 -           hard drive, and this worked.  This is the configuration that
052049 -           failed under step 1c, above.  Only the sequence of making
052050 -           the connections is different. ref SDS 0 6090
052051 -           ..
052052 -       d.  Connected Exabyte tape drive, and that worked.
052053 -
052055 -  ..
052056 - Device May be Defective Causing Improper Power Distribution
052057 -
052058 - Based on the record today, Eric believes there may be a device that
052059 - has a marginal problem.  But since the problem is no longer happening,
052060 - we cannot further troubleshoot it.
052061 -
052062 - We shut the system down several times and powered it back on.  It
052063 - worked flawlessly.
052064 -
052065 -     [On 000310 developed possible explanation. ref SDS 49 4071
052066 -
052067 -
052068 -
052069 -
0521 -

SUBJECTS
PG&E Example Technician, Project Manager
Psychologically Demanding to Discover Error Constantly
Debug Management Discover Communication Issues Before Mistakes Impact
Proactive Learning Discovry Analysis Insite Intelligence

1206 -
120701 -  ..
120702 - Technical Work Debugs Mistakes in Real-Time
120703 - Management Defers Mistakes, Communication Biggest Risk in Enterprise
120704 -
120705 - Eric noted everything on CPU11 is now working after he changed the
120706 - order of connecting devices to the power supply, ref SDS 0 6180; but
120707 - said, it makes no sense at all! ref SDS 0 6180
120708 -
120709 - He feels the record today is "weird" in relation to his experience the
120710 - past 4 years fixing computers.
120711 -
120712 -     [On 000310 developed possible explanation. ref SDS 49 4071
120714 -  ..
120715 - Eric likes working on computers, even though some days are stressful,
120716 - because knowledge and skill comes from experience.  Each assignment
120717 - widens understanding of issues that help solve future problems.
120719 -  ..
120720 - We reviewed differences between debugging computers and management,
120721 - from the record on 940820 at PG&E, showing project managers like their
120722 - work because the impact their mistakes is deferred. ref SDS 1 5588
120724 -  ..
120725 - Managers don't have to stay and fix small mistakes.  They can ignore
120726 - them because everything seems to keep going.  They unwittingly pass
120727 - off their mistakes to others through communications in meetings, calls
120728 - and documents, then attribute their problems to people who tell the
120729 - truth, reported on 950412. ref SDS 3 3920
120731 -  ..
120732 - Whereas, a technical engineer feels the stress of not being able to
120733 - move to the next step until every little mistake with the current step
120734 - is fixed.  This is called "debugging" because it relates to small
120735 - matters.  Management does not have a quality control "metric" that
120736 - shuts down the system, as Eric encountered today, to identify when
120737 - their work, which is 90% communication, does not align with
120738 - requirements.  The CEO rarely checks the policy manual or the diary of
120739 - his prior meeting to see if he is drifting off course toward a future
120740 - collision with reality.
120742 -  ..
120743 - Com Metrics "debugs" communication as explained in POIMS to help avoid
120744 - future collisions. ref OF 1 1108
120745 -
120746 -
120747 -
120748 -
120749 -
120750 -
1208 -

SUBJECTS
Mainboard, Memory, Case, Quote
Case Not Properly Insulated
Windows, Microsoft

1705 -
170601 -  ..
170602 - Motherboard Replace, ASUS P2B May Be Defective
170603 -
170604 - As a result of the record fixing CPU11, ref SDS 0 3053, Eric suspects
170605 - there may be an underlying problem with the ASUS main board, purchased
170606 - originally on 981113, ref SDS 9 5220, even though nothing is evident
170607 - from the examination today.
170609 -  ..
170610 - Eric related having encountered problems with ASUS boards on other
170611 - systems.
170612 -
170613 -    This step, however, does not address the possibility that a device
170614 -    may be impacting the power distribution to other components, per
170615 -    above. ref SDS 0 8588
170617 -  ..
170618 - Eric advised that Mountain Computer recommends Intel motherboards.
170620 -  ..
170621 - He believes from experience and research that ASUS boards are slower
170622 - and less reliable than Intel boards.
170624 -  ..
170625 - This aligns with the record on 980225 showing CPU10 has an Intel
170626 - mainboard. ref SDS 5 5220  We have not had any problems on CPU10, and
170627 - it is about 10 months older than CPU11.
170629 -  ..
170631 -  ..
170632 - A new motherboard would cost about $120, plus installation of an hour.
170633 -
170634 - He said a motherboard with Pentium III capability can use the 450Mhz
170635 - Pentium II processor we have now, and, also, provide the ability to
170636 - upgrade later.
170637 -
170638 -     [On 000306 called to expedite quote. ref SDS 47 0001]
170640 -      ..
170641 -     [On 000310 upgraded motherboard installed. ref SDS 49 0897
170643 -  ..
170644 - Adding another 128 MB of RAM would improve performance.  Eric is
170645 - unaware of any issues with W98 about handling RAM above 128 MB, which
170646 - is currently installed.
170647 -
170649 -  ..
170650 - Windows 2000 Upgrade Potential
170651 -
170652 - Eric said MCE has reviewed Windows 2000 (W00).  He related that Brad,
170653 - or someone in the MCE office, got a free copy at the Microsoft event
170654 - in San Franciso a week or so ago announcing W00.  Eric has installed
170655 - and evaluated a pre-release version of W00.  He said it installs
170656 - similar to W98.  It recognized and configured all of his equipment,
170657 - which sounds like an improvement over NT, which required individual
170658 - configuration of everything, rather than plug and play.
170659 -
170660 -     [On 000307 Brad confirmed these understandings. ref SDS 48 5159
170662 -  ..
170663 - Based on personal use, and having serviced W95 and W98 systems over
170664 - the past four (4) years, Eric believes W00 is faster and more stable
170665 - than the prior products.  This might further avoid problems we have
170666 - experienced using W98.  On 000229 W98 2nd Edition was installed on
170667 - CPU11, but it does not seem to improve performance. ref SDS 42 0001
170668 - Performance gets slower and slower, as more applications are loaded
170669 - for multi-tasking, and performance does not improve when programs are
170670 - closed.  The only way to restore respoiveness is to boot the system.
170672 -  ..
170673 - We will monitor performance over the next week, and if the problems
170674 - occur again, will definitely have to upgrade.
170675 -
170676 -    [On 000303 asked Morris for recommendation on Intel board.
170677 -    ref SDS 45 0001]
170678 -
170679 -    [On 070601 report Windows XP glitchy, needs to be removed and
170680 -    installed once a year to run efficiently. ref SDS 51 XS5H
170681 -
170682 -
1707 -

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

2106 -
210701 -  ..
210702 - Exabyte 10 GB Tape Drive Installed in CPU11 from CPU08
210703 -
210704 - On 981114 did not install Exabyte tape drive in C11 because it entails
210705 - extra work to configure.  Typically, it will be done wrong, because
210706 - near-term perceptions about what is needed, based on the record of
210707 - prior work, will be incorrect.  Planned to use RW CD ROMs for backup.
210708 - ref SDS 11 7482  On 981229 received RW CD ROM Spressa model
210709 - manufactured by Sony, and ordered backup software. ref SDS 13 3690  On
210710 - 990309 received and installed Spressa backup software from Sony.
210711 - ref SDS 27 6136  This method has not worked well for full file
210712 - backups, so...
210714 -  ..
210715 - Per above, while the system was disassembled, asked Eric to remove the
210716 - Exabyte tape drive from C08 and install it in C11.
210717 - ..
210718 - This was a very simple step.
210720 -  ..
210721 - He used the ribbon from CPU08 to connect the tape drive to the SCSI
210722 - card we originally purchased for the tape drive.
210723 - ..
210724 - There were no configuration issues.  W98 recognized the tape
210725 - drive, and required no special drivers.  It is listed in Device
210726 - Managers. The driver tab says no drivers are required.
210728 -  ..
210729 - After Eric got the network working, per below, ref SDS 0 9077, we
210730 - looked up in SDS and found that Novaback is the software that runs the
210731 - tape drive in W98.
210733 -  ..
210734 - We copied the Novaback software from C10 to C11...
210735 -
210736 -
210737 -                        h: 00 34
210738 -
210740 -  ..
210741 - Ran a test backup on C11, and it worked.  It was not necessary to
210742 - install the Novaback software.
210743 - ..
210744 - The system seems to run correctly.  Did a full file back up and
210745 - verified the data set.
210746 -
210747 -
210748 -
210749 -
210750 -
210751 -
210752 -
2108 -

SUBJECTS
Network, W95, EtherPCI
Ethernet Card, Fast EtherLink XL, PCI 10/100BASE TX
Network, EtherPCI LAN
IP Address TCP/IP

2606 -
260701 -  ..
260702 - Network on CPU10 Network to CPU11 Using TCP/IP Rather than Netbui
260703 - Downloaded 3Com Drivers for CPU10
260704 -
260705 - Eric networked CPU10 to CPU11.   He used the configuration set for
260706 - CPU11 by Randy on 000227. ref SDS 42 1704
260707 -
260708 - This requires setting the TCP/IP pointing to 3Com network protocol
260709 - address on CPU10...
260710 -
260712 -     ..
260713 -    IP             100 100 100 4
260715 -     ..
260716 -    Subnet Mask    255 255 255 0
260717 -
260718 - ..
260719 - Subnet Mask has to be identical on network systems; IP address
260720 - has to the same for the first three fields, the last field is
260721 - different.
260722 -
260723 -       [On 000310 w00 seems to configure itself on CPU11. ref SDS 49
260724 -       0783]
260725 - ..
260726 - Eric used TCP/IP instead of Netbui.
260728 -  ..
260729 - He said TCP/IP configuration will work better than Netbui with the DSL
260730 - service we are considering.
260731 -
260732 -    [On 000310 Eric installed W2000 and configured the network using
260733 -    TCP/IP, installed today. ref SDS 49 0783
260734 -
260735 -    [On 000422 TCP/IP failed with DSL, ref SDS 50 5740, according to
260736 -    Pac Bell, because need "domain" for w2000. ref SDS 50 6699
260738 -  ..
260739 - Initially network on CPU10 10 wasn't working correctly.
260741 -  ..
260742 - Eric thought it was a software issue with the protocol TCP/IP.
260743 - ..
260744 - He removed all the protocols and reinstalled them.  Problem
260745 - remained,
260747 -  ..
260748 - He concluded the 3Com ethernet drivers were not working correctly
260749 - because even though the computer recognized the drivers were
260750 - installed, when WINIPCFG was run, it did not detect the NIC.
260752 -  ..
260753 - Eric then downloaded the drivers from 3com's website, and installed
260754 - them on CPU10. PROBLEM SOLVED.
260755 - ..
260756 - We put the driver files downloaded from 3Com's web site in...
260757 -
260758 -
260759 -                     g: 00 3Com
260760 -
260762 -  ..
260763 - Need to put uncompacted drivers in same drive on CPU10, that is used
260764 - for the same drivers on CPU11. ref SDS 42 0896
260765 -
260766 -
260767 -                 h: 00 02 02 01     Disk 1
260768 -                 h: 00 02 02 02     Disk 2
260769 -
260771 -  ..
260772 - There seem to be two files downloaded....
260773 -
260774 -                         3c90xx1.exe
260775 -                         3c90xx2.exe
260776 - ..
260777 - These were then expanded into the driver installation files that
260778 - are read by W98 for configuring the 3Com card.
260779 -
260780 -
260781 -
260783 -  ..
2608 -
2609 -
2610 - 1208 received invoice
2611 -
261101 - Eric prepared an invoice #3782.
261102 -
261103 - Paid by check #2312     $262.50
261105 -  ..
261106 - He will contact us with a quote for an Intel motherboard, and another
261107 - 128 MB of RAM.
261108 -
261109 -
261110 -
261111 -
261112 -
2612 -
Distribution. . . . See "CONTACTS"