|
|
|
| Authored by: Anonymous on Saturday, November 10 2012 @ 04:32 PM EST |
| I've seen that terminology used before! [ Reply to This | Parent | # ]
|
| |
| Authored by: Anonymous on Saturday, November 10 2012 @ 11:25 PM EST |
When you first start testing, notice that there are so many
problems that the device will not work at all. In order to
maintain a small part of your sanity, turn off all functions
that aren't being tested at the present time. Forget to turn
them back on later.
I was doing a hardware upgrade once that I ended up doing in
7 plants all over North America. At one plant, I couldn't
get the nightly sales forecast download to finish - it kept
dropping off at different points. After a week of struggling
with this, I realized that this plant was still using the
old SNA scripts, and it was the second largest plant (the
largest still on the SNA scripts). The reason it was
stopping at random times was that there was a cron job that
restarted the download process every hour. This was to
address some SNA connection problems. Of course, SNA would
restart where the download stopped and keep going on its
merry old way. FTP would restart from scratch. The random
part was that we started the job up whenever we were ready
to test it, but the cron job was scheduled at a specific
time.
Live and learn, and don't forget the old obsolete stuff, or
it will come back to bite you.
None of this should be construed to mean that Microsoft
knows what it is doing. They can't even write documentation
to satisfy court orders.[ Reply to This | Parent | # ]
|
|
|
|
|
