Updated:
12/16/99 10:40 PM
[Sunday] [Monday]
[Tuesday] [Wednesday]
[Thursday] [Friday] [Saturday]
Sunday, December 12, 1999
With the help of some of the other Daynoters I have been playing around
with the bookmarks on these pages in attempt to 1) make the pages easier to navigate and
2) decrease the load on the server. I actually didn't realize I was loading down the
server, but when you think of it my bookmarks were actually hyperlinks. Don't want
to crow too early about the changes becasue they haven't been tested yet. I
originally put in the HTML code that looked something like <A HREF="#Monday">Monday </A>
and when I saved the file it looked like this: <a href="121299.htm#Sunday">Sunday</a>.
So we'll see what happens. Drop me an email if
it doesn't come across just right. Thanks to Dan Bowman and Gary Berg for the
emails. Bob Thompson also gave me a call with advice on how he has his page
arranged.
It was actually Gary who alerted me that I was
putting a drain on the server. While this isn't a problem today it could become one
if this site gets too large and I started to use more than my allocated bandwidth.
If this happens I would have to move away from FrontPage anyway, but that's another story
for another time.
[TOP]
[Sunday] [Monday]
[Tuesday] [Wednesday]
[Thursday] [Friday] [Saturday]
Monday, December 13, 1999
[TOP]
[Sunday] [Monday]
[Tuesday] [Wednesday]
[Thursday] [Friday] [Saturday]
Tuesday, December 14, 1999
I have decided that I want to make the IBM Intellistation my main
workstation in the office and begin migrating my files over to it. Therefore, I was
faced with a decision. Should I leave the beta version of Windows 2000 Professional
on this machine or drop back to a stable version of NT 4.0?
I thought this machine would make a good backup domain server, so I
should install Win NT 4.0 Server. Sounds simple enough. So I performed a low
level format on the SCSI drive and fired up Server. Everything was going along just
fine and then when I went to install the networking we hit a snag.
The snag was with my Intel 10/100 network card that imbedded into the
motherboard. NT found the network card and I selected the defaults. Then I get
the message there is no domain controller to verify my existence. I went back to the
network card and ran the tests. Everything passes on the card, but when I get to the
cable tests everything bombs. I tried a different cable. Same result. I can not back
out of the install at this point, so I fire up another install. This time I have
consulted the driver disk and use the driver from the CD provided by IBM. It
installs a slightly different version of the network card and passes all of the tests
including the cable test, but when I go to make this machine part of the TUCKER domain, NT
reports it can not find the domain. I killed the power and went to bed.
I now have a decision. Look deeper into the driver thing or install
Windows 2000 Professional. Windows 2000 Professional found the network just fine the
last time I installed it on this machine, heck I was even using the same cable I was last
night, so I really don't think I have a cable or network adapter problem.
Currently I am running a low level format on the drive to start from
scratch. I think I am going with Win NT 4.0 Workstation first when it time to start
the installs. I can then progress up the food chain. First I am going to
search out the utilities disk and make sure I have been selecting the correct Network
Adapter when I attempted the installs.
And these things are supposed to make your life easier.
[TOP]
[Sunday] [Monday]
[Tuesday] [Wednesday]
[Thursday] [Friday] [Saturday]
Wednesday, December 15, 1999
We had our office Christmas Luncheon today. Normally, because of our
travel schedule this function signals the end of the work year. However, because of
some of the happenings we have going on at year end I think I'll have to work a few more
days into December than normal. I know I am hearing a lot of pity sounds out there,
so try to keep 'em down.
I THINK I AM FINALLY ON THE RIGHT TRACK. I got Win
NT Server 4.0 Server to load on Rubble, which is the IBM IntelliStation M Pro. I have
subsequently installed service pack 5 and am in the process of updating to Internet
Explorer 5.01.
My network card problems were with the default Intel Network card that NT
suggested and my stupidity to use it. I had tried using the driver CD ROM IBM provided,
but this too failed because II never blew away the old network adapter when installing the
new one from the CD.
So I ran another low level format and started yet another install of Win
NT 4.0 Server. While the install was gearing up I went to IBM's web site and downloaded
the Intel Ethernet driver. When I went to put this driver on a floppy I encountered yet
another head scratcher. The drivers were in one self-extracting file and when I doubled
clicked on this file I got a quick blip on the screen. I then went out to a dos window and
ran the file to see what was happening. Yes, some of us still know a few dos commands.
When running the exe file I would get some OS/2 help line. I didn't know what the heck was
going on.
This is almost like reading the instruction manual. I called IBM's help
desk. The nice gentleman (Chip) told me that IBM used OS/2 to build these files and there
was a way aroundmy problem. Copy the .exe file to the root directory and execute it. Done.
File extracted to a floppy with no problems after attempting from the root. Why IBM
or their beloved OS/2 would make you go through this gyration is beyond any normal
thinking human. Of course there is no tip to try this anywhere that I have found,
but then I haven't done much reading either :-).
When I got the portion of the install that allowed me to use this disk to
install a network adapter I installed the driver from floppy just fine. I made sure
not to accept the default Intel adapter. The new driver disk installed a Intel
EtherExpress Pro. I ran the test diagnostics and everything passed, including the cable
test which had been giving me problems last night. I then was able to enter the static
address for my private network and FINALLY this install of NT found a domain controller
that would allow network access. Of course since Rubble had previously been installed it
barked back that this machine had previously been installed on the network and that I
needed to select a new computer name or contact my system administrator. I went to my main
NT box and deleted Rubble and started again. I had a minor heart failure when the next
screen said that no domain controller could be found. Minor fix: When I backed up of
course NT automatically changed the domain to DOMAIN. duh. Changed the domain to Tucker
and everyone lived happily ever after.
The install finished and I then went back and changed the video driver to
the InterGraph 3400. Done. Hey, didn't this whole process start with the video driver?
I now plan to make this IBM a workstation/server on my network. It'll
probably be one of my main workstations. My next project will be to install the scanner
software and connect the scanner to the external SCSI port and see what happens. I
hope this process goes easier.
IT WILL BE INTERESTING TO SEE HOW THIS ACTUALLY TURNS OUT.
The airlines supposedly have put together a new customer service plan they say will make
flying easier. I think congress or some other Federal agency was about to get on their
butts. They claim they are going to be more up front about discounted ticket
purchases and flight delays. Are they really going to keep us updated every 15-20 minutes
when we're stuck in an airport. Don't bet the farm on this one.
[TOP]
[Sunday] [Monday]
[Tuesday] [Wednesday]
[Thursday] [Friday] [Saturday]
Thursday, December 16,
1999
I think I have been pretty successful at getting Rubble up again with Win
NT 4.0 Server. I made this machine a backup domain controller.
So far I have gotten these packages reloaded on this machine: Internet
Explorer 5.0, Microsoft Office, VistaScan Scanner Software, Quicken 99.
One shortfall in testing my scanner is the cable I had was a 50 pin to
centronics and the IBM IntelliStation's SCSI adapter is a 68 pin, so I'll head off to
Computer and Software Outlet tomorrow to see if I can find the 68 pin to centronics SCSI
cable. Yes my scanner is older (24 bit). Those USB models of today are much nicer (read
that easier to install)...and less expensive than the $500 I plunked down for this one
several years ago. But remember, I am running NT 4.0 with no USB support. This scanner
used to work just fine (you never know what's going to happen when you move things
around), so I'll wait before upgrading. I can wait on Windows 2000 and the scanner.
Believe it or not.
I am installing Outlook 98. Outlook 97 loaded with the reinstallation of
Office 97. The newer version of Microsoft's software is such a pain. Anytime you want to
do anything you have to go the web to download the package. This upgrade is going to cost
me better than 17 megabytes worth of time. Urgh.
ARE THE ISP WARS ON among the mass merchandisers? America
on Line announced today they were teaming up with Wal-Mart to provide internet service to
America's Low Price Leader. Not be outdone, Microsoft also announced that it had teamed up
with Best Buy for MSN to provide net service. I guess Yahoo already has a deal with Kmart.
Sorta reminds me when citizens band radios got cheap. Let the price wars begin.
As a side note Microsoft is buying $200 million in Best Buy stock to encourage Best Buy to
push the MSN deal and other Microsoft products. In your face, DOJ.
HERE'S ANOTHER EXAMPLE WHY YOU SHOULDN'T depend on me for
stock picking advice. Once upon a time I owned a stock called Siliconix. I think I bought
it back in 1986, probably about 200 shares. I think I paid about $15 a share and in 1991 I
had watched it tumble to less than a buck a share, so I got rid of it as worthless. Today
I noticed Silconix had declared a 3-for-1 stock split and zoomed up more than $39 a share
to $128.50. Guess that's why they say you should buy and hold. No matter what.
[TOP]
[Sunday] [Monday]
[Tuesday] [Wednesday]
[Thursday] [Friday] [Saturday]
Friday
[TOP]
[Sunday] [Monday]
[Tuesday] [Wednesday]
[Thursday] [Friday] [Saturday]
Saturday
[TOP]
 Email Steve Tucker
|
