AV wanted for Win95 through to XP Pro

[Virus Guy]

Evidently, for the original poster, the system running Windows 95
is a machine controller running proprietary software. At a
certain point new computers may no longer run the software,

That is not the point.

You made the point that the OP should migrate the system away from
win-9x for network/security reasons, which is typical IT thinking -
which is that IT people see win-9x through a cracked rear view.
Win-9x was in fact more secure from network malware than Win-2k and XP
were, and XP was not fully secure from passive network intrusion until
SP2.

Machine tool control involves a lot of sharp metal moving at
high speeds ... errors can be catastrophic.

So now you put up another straw man.

Presumably, once upon a time when that hardware control system was
new, that it, the computer, and win-9x were fully qualified to run and
work together.

Why should that be any different now?

Again, typical IT thinking that computer hardware MUST be turned over
every 3 years regardless the application.

Do you buy a new toaster every 3 years just because your old one is 3
years old?

 

[Virus Guy]

But it WILL get to a point where it is broke and we'll be stuffed.

Do yourself a favor and use norton ghost and ->CLONE THE HARD DRIVE<-.

Your hard drive will likely be the first (and only) component of the
computer to fail.

Buy a new hard drive, clone your existing drive, and keep the cloned
copy handy. In fact, make 2 clone drive copies and immediately start
using one of them. Keep the other clone copy, and the original drive,
in storage as backups. Drives are cheap.

Then, go buy a new power supply. They're $30. They're cheap. The
power supply is the next most-likely component to fail after the hard
drive.

While you're at it, open the system and clean out the dust. The CPU
fan is most likely caked with dust, and so is the power supply.

A little cleaning to will increase the life of the system by keeping
it running cool.

 

[Bart Bailey]

Win-9x was in fact more secure from network malware than Win-2k and XP
were,

My two remaining machines run respectively, 95B and XPpro
The XP(fat32) has been gutted of as much of the vulns I can and still
have it run. IOW: no MSIE, SQL etc.

and XP was not fully secure from passive network intrusion until
SP2.

No SP1 or 2 here, just an old warez copy from back in '01

 

[Phil Weldon]

'Virus Guy' wrote, in part:
| You made the point that the OP should migrate the system away from
| win-9x for network/security reasons ...
_____

I guess this is just outside your area of comprehension.

Phil Weldon

| Phil Weldon wrote:
|
| > Evidently, for the original poster, the system running Windows 95
| > is a machine controller running proprietary software. At a
| > certain point new computers may no longer run the software,
|
| That is not the point.
|
| You made the point that the OP should migrate the system away from
| win-9x for network/security reasons, which is typical IT thinking -
| which is that IT people see win-9x through a cracked rear view.
| Win-9x was in fact more secure from network malware than Win-2k and XP
| were, and XP was not fully secure from passive network intrusion until
| SP2.
|
| > Machine tool control involves a lot of sharp metal moving at
| > high speeds ... errors can be catastrophic.
|
| So now you put up another straw man.
|
| Presumably, once upon a time when that hardware control system was
| new, that it, the computer, and win-9x were fully qualified to run and
| work together.
|
| Why should that be any different now?
|
| Again, typical IT thinking that computer hardware MUST be turned over
| every 3 years regardless the application.
|
| Do you buy a new toaster every 3 years just because your old one is 3
| years old?

 

[Offbreed]

But it WILL get to a point where it is broke and we'll be stuffed. That's
why I would like to explore virtualisation on modern hardware now - it's
called contingency planning.

You can pick up a dozen old computers that will run that without
trouble, and you can get copies of Win95 as well. You need to copy the
program onto a half dozen CDs.

(shrug) Your project.

 

[Offbreed]

'Offbreed' wrote:
| Which is what?
_____

Evidently, for the original poster, the system running Windows 95 is a
machine controller running proprietary software. At a certain point new
computers may no longer run the software, the operating system, and possibly
the interface.

"Newest and latest" probably cannot run the proprietary software now, or
control the hardware properly, due to motherboard clock speed. Now is
the time to shop the junk stores for spare computers and parts.

 

[Virus Guy]

No SP1 or 2 here, just an old warez copy from back in '01

While I applaud and endorse your cost-reduction efforts, others
reading this must be gasping.

Any system(s) on your network running XP-gold are incredibly
vulnerable to many exploits, many of which are not IE related. Your
network is prone to poor and unpredicatable performance if one of your
machines becomes infected with something.

There are ways to obtain "ultra-low-cost" versions of XP-pro SP2 and
update it safely. I would advise you to do that.

I can see why you're worried about the malware threat to your win-9x
systems.

 

[Bart Bailey]

I can see why you're worried about the malware threat to your win-9x
systems.

I certainly didn't intend to convey any excess concern about the 95B
box, it's the only one behind a firewall however. Seems prudent usage
serves me better than stomach churning anxiety.

 

[Virus Guy]

I certainly didn't intend to convey any excess concern about the
95B box, it's the only one behind a firewall however.

I'm curious about that. Your 95b box is running your CCM software, and
is behind a firewall (yes?).

If so, then how do you communicate to it on your local LAN, through
the firewall?

Seems that the firewall would prevent you from sending it cad files
(or other shares) and hence I'm not sure why you would put that
machine behind a firewall vs your entire local LAN.

 

[Bart Bailey]

I'm curious about that. Your 95b box is running your CCM software, and
is behind a firewall (yes?).

If so, then how do you communicate to it on your local LAN, through
the firewall?

Seems that the firewall would prevent you from sending it cad files
(or other shares) and hence I'm not sure why you would put that
machine behind a firewall vs your entire local LAN.

Whoa, you're confusing me for some other person.
I'm not on a LAN, nor running any business enterprise here.
My original comment referred to the security aspects of XP.