closing port 445

  • Thread starter Thread starter Jason Wade
  • Start date Start date
Richard Steven Hack said:
No, I blame the program AND MS - the program for screwing up and MS
for having the Registry which is too EASY to screw up.


I am aware of that.


Here you are absolutely correct - I should have backed up the Registry
first. On the other hand, the program involved said that it would
disable ports - while that should have been a clue to me to back up
the Registry, it did not explicitly say it would do anything to the
Registry.

I install and uninstall stuff all the time and while I should back up
the Registry before every install, ninety-nine percent of the time
there is no ill-effect.

However as someone else pointed out here, on Linux it is extremely
difficult to hose the system so bad as to require a reinstall. You
may have trouble finding the files involved or figuring out what they
do (which is also true on Windows) but at least they're there, they're
in text format, and they can be fixed.

The Registry is a poor idea even more poorly implemented. It is a
symptom of the "Big Brother" Microsoft mentality that critical system
files are both poorly documented and hidden from the user. It is one
thing to require administrator access to system files to protect them
and quite another to engage in obfuscation of the system.
Click to expand...
I have done lots of things with the MS registry over the years programming
wise and have never *jacked* the registry. So, I myself don't view the
registry as a problem. I like it. :)

Duane :)
 
I have done lots of things with the MS registry over the years programming
wise and have never *jacked* the registry. So, I myself don't view the
registry as a problem. I like it. :)
Click to expand...

As I point out above, it is a poor design decision. I have never
screwed up the Registry either on my previous Windows 98 even though I
had one that was 9MB in size and had to be pruned down using several
Registry editors, cleaners and compacters.

Try installing and uninstalling enough third party programs and sooner
or later someone will screw it up. There are a *lot* of *bad*
programmers.

Last Tuesday the damn 2000 DID IT AGAIN! Had to reinstall again.
This time I have no clue what caused it to hose.

Critical system files should be *robust* and *documented*.
 
As I point out above, it is a poor design decision. I have never
screwed up the Registry either on my previous Windows 98 even though I
had one that was 9MB in size and had to be pruned down using several
Registry editors, cleaners and compacters.

Try installing and uninstalling enough third party programs and sooner
or later someone will screw it up. There are a *lot* of *bad*
programmers.

Last Tuesday the damn 2000 DID IT AGAIN! Had to reinstall again.
This time I have no clue what caused it to hose.

Critical system files should be *robust* and *documented*.
Click to expand...
What are you talking about here?

Windows XP Professional Resource Kit book ISBN 0-7356-1974-3 1,706 pages
discussing the XP O/S.

Part 4 System Troubleshooting

Chapter 25 Troubleshooting Concepts and Strategies
Chapter 26 Troubleshooting Disk and File Systems
Chapter 27 Troubleshooting Startup

And it talks about the whole 9 yards from everything to system files,
registry, boot process, etc. etc -- all of it.

There is a Resource Kit book for Win NT workstation and server, Win 2K
workstation and server, Win 2K3.

None of this you're talking about on documentation is going to hold with
me none of it.

You have no excuses as far as I am concerned -- none. :)

Duane :)
 
As I point out above, it is a poor design decision. I have never
screwed up the Registry either on my previous Windows 98 even though I
had one that was 9MB in size and had to be pruned down using several
Registry editors, cleaners and compacters.

Try installing and uninstalling enough third party programs and sooner
or later someone will screw it up. There are a *lot* of *bad*
programmers.

Last Tuesday the damn 2000 DID IT AGAIN! Had to reinstall again.
This time I have no clue what caused it to hose.

Critical system files should be *robust* and *documented*.
Click to expand...

One other thing, I don't know who you think you're talking to about this.
I have been doing this for 30 some years plus. You're not coming past me
on none of it -- so stop. :)

Duane :)
 
Back
Top