O.T. Avast pop-up

On Thursday, June 27, 2019 at 12:13:03 PM UTC-7, Paul wrote:
Robert in CA wrote:
I tried going through the pici.ids ,.. it's hard to go through
especially with my eyes. It's like reading music again.

I'm trying to keep up but don't understand what you mean by
0x15?

Regarding who else might be reading these from GRC InSpectre ,.
just a guess but Google, Sprint and the like ? It's widely known
they've become political or possibly from China?

These are the results, I see that one of the yellow triangles has
been eliminated.


http://i65.tinypic.com/2m4dhc2.jpg

http://i63.tinypic.com/nmj1xj.jpg

http://i63.tinypic.com/nf07xy.jpg Ven_8086 Dev 1E31

http://i67.tinypic.com/2qkjczr.jpg

http://i63.tinypic.com/1so9om.jpg InSpectre 406C4 ???


Thoughts/Suggestions?

Thanks,
Robert

Your USB device is Intel.

We need an Intel chipset driver for Windows 7,
as Microsoft doesn't do USB3 in Windows 7. Win8
and Win10 would have solved this on their own.

https://www.dell.com/support/home/ca...s-8500/drivers

Intel Chipset Driver

Chipset_Driver_H95F7_WN_9.3.0.1021_A00.EXE

Last Updated: 13 Jun 2014

File size: 9.08 MB

The file inside that that does the USB3 installing is "PantUSB3.inf",
not that this matters. The filename is changed by the OS
to the form of "OEM23.inf", which is used to prevent collision
of filenames.

*******

; ** Filename: PantUSB3.INF
; ** Abstract: Null driver for Intel(R) USB 3.0 devices
; ** Last Update: December 06, 2011 (Version 9.3.0 Build 1018)

Include=machine.inf

PCI\VEN_8086&DEV_1E31.DeviceDesc="Intel(R) 7 Series/C216 Chipset Family Universal Serial Bus (USB) Controller - 1E31"

*******

Even though it's in the Win7 folder of the Dell driver file,
it appears to be a null driver, and will just move the
unlabeled item into the labeled USB section. You still
have to do it though, to clean up Device Manager.

Chipset_Driver_H95F7_WN_9.3.0.1021_A00.EXE

HTH,
Paul

I'm not sure what driver your referring
to or how to get it? I tried this:

http://i64.tinypic.com/2vxocom.jpg

Should I download it?

Robert

On Thursday, June 27, 2019 at 12:33:00 PM UTC-7, Paul wrote:
Robert in CA wrote:
I tried going through the pici.ids ,.. it's hard to go through
especially with my eyes. It's like reading music again.

I'm trying to keep up but don't understand what you mean by
0x15?

Regarding who else might be reading these from GRC InSpectre ,.
just a guess but Google, Sprint and the like ? It's widely known
they've become political or possibly from China?

These are the results, I see that one of the yellow triangles has
been eliminated.


http://i65.tinypic.com/2m4dhc2.jpg

http://i63.tinypic.com/nmj1xj.jpg

http://i63.tinypic.com/nf07xy.jpg

http://i67.tinypic.com/2qkjczr.jpg

http://i63.tinypic.com/1so9om.jpg


Thoughts/Suggestions?

Thanks,
Robert

The CPU has a basic part number.

The "microcode" is a patching system. Even when a CPU is
brand new, it has on average "100 bugs" in it. The microcode
subsystem was invented to allow "correcting" the behavior
of the CPU, after you've sold some (and you're still testing
the CPU in the lab!).

In a project at work, a test procedure was still being run
18 months after a product ships. These include "obscure" test
cases that customers will never run, but nevertheless,
must be corrected by software updates. That's the basic idea
of the invention of patching systems like this.

*******

When your CPU and computer left the factory, the BIOS had
version 0x15 of microcode stored in it. It has microcode
for about eight different processor models on average.
A microcode patch varies from 2KB to 16KB or so.

The microcode store is part of the multicycle instruction
interpreter. By changing what a CISC instruction does during
interpretation, you hope to prevent hackers (using web pages)
from doing stuff to the machine. Such as, stealing a credit
card number you just typed into one https web page.

When Spectre/Meltdown came out, this was the first time
that Intel suffered "architecture bugs", instead of
"instruction bugs" such as the FDIV fiasco. The patching
system had never been meant for architecture bugs. The
thing is, life was easy when "instruction bugs" existed,
as you *always* patch those. With confidence, Microsoft
could put new microcode in Windows Update, deliver it
via the microcode loader in the OS, and this would
fix everybody up. There were no "conditionals" involved.
If Intel issued microcode, you delivered it.

This changed with Spectre/Meltdown. Initially Intel delivered
microcode, but some platforms experienced performance problems
(boot problems perhaps). The microcode was withdrawn. If
you made the mistake of taking the Dell BIOS update on that
date, you might have to install an older BIOS to "re-fix"
your damn computer.

Here we are today, about nine exploits later, still patching
these damn things.

1) Yes, you can install that Dell BIOS. Dell has tested it.

There is the usual risk, with any BIOS update, of bricking
the machine.

My Test Machine motherboard is different. If that one is
bricked, there is a USB port and a white colored push button,
and I can "flash in" a new BIOS, even with no CPU in the socket.
There aren't a lot of machines with such a feature. The
alternative "unbricking" solution is a USB to 7 pin connector
device, which would be a similar thing to what the pushbutton
is doing on my computer.

If you've updated the BIOS on the XPS 8500 before and there
were no issues, then you could likely do it again with little
worry.

BIOS flashers fail when:

a) Power goes off during flashing.
Flashing might take five minute (don't know current number).

b) For the dumbest schemes, an Internet connection failure
in the middle of a flash, can cause brickage of the computer.
The file should always be fully on the machine when you flash!

c) Dumb ass developers mix versions of boot loaders and
flash main body, and "something bad happens" when mixing
certain versions. Asus used to have extensive "do this do that"
things on their web page, hinting at the complexity of mixing
and matching "from--to" BIOS combinations.

That's about it for risks.

2) All that this BIOS update will do for you, is take
the 0x15 number to 0x20 or so. It might change the Spectre
protection to "Yes". It may or may not affect the latest
exploit methods, which aren't even documented properly yet.

Windows 10 offers slightly better options.
Or so Microsoft would have us think.

Without extensive test tools, it's rather hard to tell how
exposed any machine is. The Gibson Research InSpectre is
about as useful as the Microsoft Powershell script, except
it's a bit more user friendly.

Actual exploit testers aren't to be seen. The thing is,
if a White Hat writes a tester that probes a machine locally,
Black Hats will analyze the code and "weaponize it". To prevent
aiding and assisting Black Hats, exploit testers are out
of the question (at the moment). If all these things
were "curable instantly", then exploit testers would have
been made available. And with these architectural class
bugs in CPUs, we're not in a position right now to be
"giving free weapons to bad guys".

Your AV cannot stop all these. Your credit card number being
stolen, is not something that an AV excels at.

As a result of these architecture bugs, the three platforms
(ARM, Intel, AMD) have different degrees of resistance
to attacks of this sort. I don't know the current status
of each, to be recommending "only use your credit card on X".

One of the recent problems discovered, would require you
to turn off Hyperthreading at BIOS level on the 8500.
Cutting the number of virtual cores in half. For many people,
this is "going too far" in terms of covering off bugs.

Paul



I had only a basic idea of microcode and had to
look it up but with the Spectre/Meltdown it's
only a matter if time before my credit card number
is stolen?

Robert

Robert in CA wrote:

I had only a basic idea of microcode and had to
look it up but with the Spectre/Meltdown it's
only a matter if time before my credit card number
is stolen?

Robert


The partitioning inside the CPU isn't good enough.

These particular exploits allow one web page to
look at what another web page is doing.

That's the basic idea.

While it's not an immediate concern (you don't
see mass exploits in the news), it still represents
a weakness in how computers work. And different
companies, have different levels of exposu
ARM, AMD, and Intel.

My protection here isn't bulletproof.

And even with the BIOS update, yours would
likely still have some holes right now.
(InSpectre program doesn't have indicators
for the latest problems.)

I don't have a good answer for this, just as
I don't have a good answer for Ransomware. I have
backups to protect against Ransomware, but if something
got loose in my computer room, it would be
one hell of a mess.

The thing is, there has to be some balance between
"maintenance" and "usage" of computers. We can't
put 99% of our waking hours into doing backups
and huddling in fear in a corner.

It will take time to plug these holes. Plenty
of time. Initially, I joked with someone that
six months time would be enough. Boy, was
I wrong.

Before you install the BIOS.

1) Try and determine what the current BIOS version is.

2) See if the BIOS tool makes a backup. In the past,
a BIOS tool offered to capture the current BIOS version
and put it in a file, which is better than nothing.
In some cases, if the BIOS flash fails, you try and
install the "old" BIOS *before rebooting the machine*.
Never reboot or shut off, until you've done everything
possible to ensure *some* BIOS update finished OK.

3) Consider the possibility you'd be down to one machine
for a while, if it failed. The Dell flasher is likely
pretty good, and better than most.

After you're done, the InSpectre display might remove
the "microcode update available", since you'd be "closer"
to the current value. I don't know if the latest Intel
microcode is ready at Dell yet. If Dell would print the
Microcode values, that would be nice :-/ I hate having
to analyze microcode versions with a hex editor.

The Intel PIU should show 0x20 or 0x21 in place of
the 0x15 seen today.

HTH,
Paul

Robert in CA wrote:
On Thursday, June 27, 2019 at 12:13:03 PM UTC-7, Paul wrote:
Robert in CA wrote:
I tried going through the pici.ids ,.. it's hard to go through
especially with my eyes. It's like reading music again.

I'm trying to keep up but don't understand what you mean by
0x15?

Regarding who else might be reading these from GRC InSpectre ,.
just a guess but Google, Sprint and the like ? It's widely known
they've become political or possibly from China?

These are the results, I see that one of the yellow triangles has
been eliminated.


http://i65.tinypic.com/2m4dhc2.jpg

http://i63.tinypic.com/nmj1xj.jpg

http://i63.tinypic.com/nf07xy.jpg Ven_8086 Dev 1E31

http://i67.tinypic.com/2qkjczr.jpg

http://i63.tinypic.com/1so9om.jpg InSpectre 406C4 ???


Thoughts/Suggestions?

Thanks,
Robert
Your USB device is Intel.

We need an Intel chipset driver for Windows 7,
as Microsoft doesn't do USB3 in Windows 7. Win8
and Win10 would have solved this on their own.

https://www.dell.com/support/home/ca...s-8500/drivers

Intel Chipset Driver

Chipset_Driver_H95F7_WN_9.3.0.1021_A00.EXE

Last Updated: 13 Jun 2014

File size: 9.08 MB

The file inside that that does the USB3 installing is "PantUSB3.inf",
not that this matters. The filename is changed by the OS
to the form of "OEM23.inf", which is used to prevent collision
of filenames.

*******

; ** Filename: PantUSB3.INF
; ** Abstract: Null driver for Intel(R) USB 3.0 devices
; ** Last Update: December 06, 2011 (Version 9.3.0 Build 1018)

Include=machine.inf

PCI\VEN_8086&DEV_1E31.DeviceDesc="Intel(R) 7 Series/C216 Chipset Family Universal Serial Bus (USB) Controller - 1E31"

*******

Even though it's in the Win7 folder of the Dell driver file,
it appears to be a null driver, and will just move the
unlabeled item into the labeled USB section. You still
have to do it though, to clean up Device Manager.

Chipset_Driver_H95F7_WN_9.3.0.1021_A00.EXE

HTH,
Paul

I'm not sure what driver your referring
to or how to get it? I tried this:

http://i64.tinypic.com/2vxocom.jpg

Should I download it?

Robert

Well, yes. Looking at your picture, that's
probably the item. Using the triangle "twiddler" on the
left should show the details for the item.

And eventually you'll get to a thing to click for the download.

I downloaded it and that's why I can see "PantUSB3.inf"
has your VEN/DEV in it. I basically verified there
was a matching driver in it.

But, the driver doesn't do much, technically. It puts
a text string in Device Manager (to correct the labeling).
It calls machine.inf, but I don't understand how that
helps, as I thought Win7 didn't have its own XHCI
in the OS (class driver for such things).

Anyway, when you test a USB3 device on a USB3 port
and note the transfer speed, that will tell you whether
it all works or not. USB2 only does 30MB/sec, while
USB3 can do at least 400MB/sec (when talking to an SSD
drive).

Paul

In message , Paul
writes:
[]
Your USB device is Intel.

We need an Intel chipset driver for Windows 7,
as Microsoft doesn't do USB3 in Windows 7. Win8
and Win10 would have solved this on their own.
[]
Is USB3 backwards compatible at the _hardware_ level - in other words,
if someone has USB3 hardware on a Windows 7 system, and _doesn't_ get
the necessary driver, will it work, but just at USB2 speeds? (And maybe
USB3 current limits?)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

.... she has never contracted A-listeria or developed airs and graces. Kathy
Lette on Kylie, RT 2014/1/11-17

Your USB device is Intel.

We need an Intel chipset driver for Windows 7,
as Microsoft doesn't do USB3 in Windows 7. Win8
and Win10 would have solved this on their own.
[]
Is USB3 backwards compatible at the _hardware_ level - in other words,
if someone has USB3 hardware on a Windows 7 system, and _doesn't_ get
the necessary driver, will it work, but just at USB2 speeds? (And maybe
USB3 current limits?)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

... she has never contracted A-listeria or developed airs and graces. Kathy
Lette on Kylie, RT 2014/1/11-17


Let me see if I understand this.. all this
concerns the USB ports? I have blue colored
ports on the 8500 and they work, OK.or does
this mean something else?

Also were working toward of getting a Windows
10 Key just in case and while I still can until
we found these yellow triangles and now trying
to remove them. We eliminated one but the other
is still present.

Robert

Thanks,
Robert

On Thursday, June 27, 2019 at 1:48:27 PM UTC-7, Paul wrote:
Robert in CA wrote:
On Thursday, June 27, 2019 at 12:13:03 PM UTC-7, Paul wrote:
Robert in CA wrote:
I tried going through the pici.ids ,.. it's hard to go through
especially with my eyes. It's like reading music again.

I'm trying to keep up but don't understand what you mean by
0x15?

Regarding who else might be reading these from GRC InSpectre ,.
just a guess but Google, Sprint and the like ? It's widely known
they've become political or possibly from China?

These are the results, I see that one of the yellow triangles has
been eliminated.


http://i65.tinypic.com/2m4dhc2.jpg

http://i63.tinypic.com/nmj1xj.jpg

http://i63.tinypic.com/nf07xy.jpg Ven_8086 Dev 1E31

http://i67.tinypic.com/2qkjczr.jpg

http://i63.tinypic.com/1so9om.jpg InSpectre 406C4 ???


Thoughts/Suggestions?

Thanks,
Robert
Your USB device is Intel.

We need an Intel chipset driver for Windows 7,
as Microsoft doesn't do USB3 in Windows 7. Win8
and Win10 would have solved this on their own.

https://www.dell.com/support/home/ca...s-8500/drivers

Intel Chipset Driver

Chipset_Driver_H95F7_WN_9.3.0.1021_A00.EXE

Last Updated: 13 Jun 2014

File size: 9.08 MB

The file inside that that does the USB3 installing is "PantUSB3.inf",
not that this matters. The filename is changed by the OS
to the form of "OEM23.inf", which is used to prevent collision
of filenames.

*******

; ** Filename: PantUSB3.INF
; ** Abstract: Null driver for Intel(R) USB 3.0 devices
; ** Last Update: December 06, 2011 (Version 9.3.0 Build 1018)

Include=machine.inf

PCI\VEN_8086&DEV_1E31.DeviceDesc="Intel(R) 7 Series/C216 Chipset Family Universal Serial Bus (USB) Controller - 1E31"

*******

Even though it's in the Win7 folder of the Dell driver file,
it appears to be a null driver, and will just move the
unlabeled item into the labeled USB section. You still
have to do it though, to clean up Device Manager.

Chipset_Driver_H95F7_WN_9.3.0.1021_A00.EXE

HTH,
Paul

I'm not sure what driver your referring
to or how to get it? I tried this:

http://i64.tinypic.com/2vxocom.jpg

Should I download it?

Robert

Well, yes. Looking at your picture, that's
probably the item. Using the triangle "twiddler" on the
left should show the details for the item.

And eventually you'll get to a thing to click for the download.

I downloaded it and that's why I can see "PantUSB3.inf"
has your VEN/DEV in it. I basically verified there
was a matching driver in it.

But, the driver doesn't do much, technically. It puts
a text string in Device Manager (to correct the labeling).
It calls machine.inf, but I don't understand how that
helps, as I thought Win7 didn't have its own XHCI
in the OS (class driver for such things).

Anyway, when you test a USB3 device on a USB3 port
and note the transfer speed, that will tell you whether
it all works or not. USB2 only does 30MB/sec, while
USB3 can do at least 400MB/sec (when talking to an SSD
drive).

Paul



I downloaded it but its still present:

http://i65.tinypic.com/300whsj.jpg

In passing,.. I know were ultimately trying to get
a key for Windows10 while I still can and this came
up but in regards to Windows 10 and maybe having to
upgrade what do you think of using Linux/Ubuntu,Unnex?

So are we out of options in resolving this? As I told
J.P. Gilliver if this concerns my USB ports, I have 3.0
and also 2.0 ports and they work OK.

Robert

I went back and re-read how all this started when we were originally
setting everything up to get the Windows 10 key just in case I needed
it and I just ran Smart scan by chance and all this came up.

So I ran it again:

http://i64.tinypic.com/a5g6tc.jpg

http://i63.tinypic.com/1y4wb8.jpg

http://i63.tinypic.com/1y4wb8.jpg

http://i68.tinypic.com/xmomlx.jpg

Robert

Robert in CA wrote:
I went back and re-read how all this started when we were originally
setting everything up to get the Windows 10 key just in case I needed
it and I just ran Smart scan by chance and all this came up.

So I ran it again:

http://i64.tinypic.com/a5g6tc.jpg Avast scareware

http://i63.tinypic.com/1y4wb8.jpg

http://i63.tinypic.com/1y4wb8.jpg

http://i68.tinypic.com/xmomlx.jpg

Robert


In the "Avast scareware" picture, read this article.

AV programs are primarily for their AV coverage.

The added bloat is sometimes, wildly bad.

https://www.howtogeek.com/239950/don...you-less-safe/

Where it says "Hackers could hijack your DNS settings",
yeah, I suppose they could, and it could also snow in July.

OK, so the trigger in this case, is probably the recent
"repair" of the Wifi entry in Device Manager. If you're
not using that Wifi adapter, you can select "Disable" in
Device Manager. Then Avast will stop scanning it and coming
up with corny messages.

https://forum.avast.com/index.php?topic=219895.0

I appreciate this scareware more, when there is a
corresponding webpage where the "method" is elucidated.

The "3 primary folders" thing ? Windows 10 has a feature
for locking down folders that you select, which may have
some merit. But there is likely to be a "Mother May I"
ceremony when you go to use the folders.

The closest "Exploit Guard" gets to Windows 7, is for Windows 7 Enterprise
users. Basically what Exploit Guard does, is only allow certain
applications you "bless", to write to selected folders.

https://www.ghacks.net/2018/02/13/wi...ows-7-and-8-1/

If you aren't aware of it yet, the industry is like a
tree with a very flexible trunk. The wind always
seems to blow in the direction that makes money. Every
company uses "scareware" and not putting features in
certain products, as part of the "marketing strategy".
It's like shearing sheep, when if comes to security.

As for your router itself, a little Googling using

make model number exploit

for your make and model, might give some idea whether
it needs a firmware update.

Paul

Robert in CA wrote:

I downloaded it but its still present:

http://i65.tinypic.com/300whsj.jpg

In passing,.. I know were ultimately trying to get
a key for Windows10 while I still can and this came
up but in regards to Windows 10 and maybe having to
upgrade what do you think of using Linux/Ubuntu,Unnex?

So are we out of options in resolving this? As I told
J.P. Gilliver if this concerns my USB ports, I have 3.0
and also 2.0 ports and they work OK.

Robert

Well, I indicated my concerns about Intel and the
possibility this is a "cop-out" driver. And not
the right driver for a Windows 7 user. I don't understand
how the file uses

#include machine.inf

and how that's supposed to pick up an XHCI driver.
Normally you'd use something like usbport.inf, on
say Windows 8 or Windows 10 (which have built-in USB3).

*******

When you first got the XPS 8500, did you make three
or four "recovery discs" as DVDs ?

One of those discs could have around 500MB of drivers.
Take a look at the "Intel Chipset Driver" from that lot.

My test machine has Asmedia USB3 and no Intel USB3. And
there is a proper driver package for that. It's possible
Asmedia uses MCCI-written drivers. I seem to remember
seeing some branding in the driver files, somewhere along
the way. MCCI used to write USB2 drivers too I think,
at one time.

But for your Intel port, we have to "catch Intel in a
weak moment", where they "do the right thing". Check the
first driver disk you ever burned on the 8500 and
see if there is a driver for it.

I still have the four discs for my Acer laptop.
Sitting there, waiting for "that emergency" to come up :-)

I would try and trace an INFINST for you on downloadcenter.intel.com,
but I'm not confident they would show something useful
on the site today. Bloody Rolex-wearing *******s :-/
(I've had personal dealings with Intel before,
I hope my feelings don't betray themselves.)

Paul

Robert in CA wrote:
Your USB device is Intel.

We need an Intel chipset driver for Windows 7,
as Microsoft doesn't do USB3 in Windows 7. Win8
and Win10 would have solved this on their own.
[]
Is USB3 backwards compatible at the _hardware_ level - in other words,
if someone has USB3 hardware on a Windows 7 system, and _doesn't_ get
the necessary driver, will it work, but just at USB2 speeds? (And maybe
USB3 current limits?)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

... she has never contracted A-listeria or developed airs and graces. Kathy
Lette on Kylie, RT 2014/1/11-17


Let me see if I understand this.. all this
concerns the USB ports? I have blue colored
ports on the 8500 and they work, OK.or does
this mean something else?

Also were working toward of getting a Windows
10 Key just in case and while I still can until
we found these yellow triangles and now trying
to remove them. We eliminated one but the other
is still present.

Robert

Thanks,
Robert

We will solve this. It's just a matter of
banging on the pipes a few more times.

Paul

Paul wrote:
Robert in CA wrote:
Your USB device is Intel.

We need an Intel chipset driver for Windows 7,
as Microsoft doesn't do USB3 in Windows 7. Win8
and Win10 would have solved this on their own.
[]
Is USB3 backwards compatible at the _hardware_ level - in other
words, if someone has USB3 hardware on a Windows 7 system, and
_doesn't_ get the necessary driver, will it work, but just at USB2
speeds? (And maybe USB3 current limits?)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

... she has never contracted A-listeria or developed airs and graces.
Kathy
Lette on Kylie, RT 2014/1/11-17


Let me see if I understand this.. all this concerns the USB ports? I
have blue colored ports on the 8500 and they work, OK.or does
this mean something else?

Also were working toward of getting a Windows 10 Key just in case and
while I still can until
we found these yellow triangles and now trying to remove them. We
eliminated one but the other is still present.
Robert
Thanks,
Robert

We will solve this. It's just a matter of
banging on the pipes a few more times.

Paul

https://www.intel.ca/content/www/ca/...-software.html

Last Reviewed 03/08/2019

Why did Intel release two Windows* 7 USB 3.0
eXtensible Host Controller (xHCI) drivers? === Why, indeed :-/

"Download USB 3.0 xHCI Windows* 7 driver for Intel 7 Series/C216 Chipset Family"

https://downloadcenter.intel.com/Det...&DwnldID=21129

Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver .zip

5,472,920 bytes

iusb3xhc.inf === Looks like the right driver.

In 7ZIP, I see this folder. You can unpack the ZIP and
locate that x64 folder.

Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver \Drivers\Win7\x64\

Unpack that folder, which has 8 files total in it.

Open Device Manager, locate the duff USB item, do the
"Update Driver" dance, tell it you have a folder with
the goods in it, when it sees your unpacked x64 folder
with the eight files, it will install the correct one.

That's better than some "machine.inf" bull****.

HTH,
Paul

On Thursday, June 27, 2019 at 7:33:23 PM UTC-7, Paul wrote:
Robert in CA wrote:
I went back and re-read how all this started when we were originally
setting everything up to get the Windows 10 key just in case I needed
it and I just ran Smart scan by chance and all this came up.

So I ran it again:

http://i64.tinypic.com/a5g6tc.jpg Avast scareware

http://i63.tinypic.com/1y4wb8.jpg

http://i63.tinypic.com/1y4wb8.jpg

http://i68.tinypic.com/xmomlx.jpg

Robert


In the "Avast scareware" picture, read this article.

AV programs are primarily for their AV coverage.

The added bloat is sometimes, wildly bad.

https://www.howtogeek.com/239950/don...you-less-safe/

Where it says "Hackers could hijack your DNS settings",
yeah, I suppose they could, and it could also snow in July.

OK, so the trigger in this case, is probably the recent
"repair" of the Wifi entry in Device Manager. If you're
not using that Wifi adapter, you can select "Disable" in
Device Manager. Then Avast will stop scanning it and coming
up with corny messages.

https://forum.avast.com/index.php?topic=219895.0

I appreciate this scareware more, when there is a
corresponding webpage where the "method" is elucidated.

The "3 primary folders" thing ? Windows 10 has a feature
for locking down folders that you select, which may have
some merit. But there is likely to be a "Mother May I"
ceremony when you go to use the folders.

The closest "Exploit Guard" gets to Windows 7, is for Windows 7 Enterprise
users. Basically what Exploit Guard does, is only allow certain
applications you "bless", to write to selected folders.

https://www.ghacks.net/2018/02/13/wi...ows-7-and-8-1/

If you aren't aware of it yet, the industry is like a
tree with a very flexible trunk. The wind always
seems to blow in the direction that makes money. Every
company uses "scareware" and not putting features in
certain products, as part of the "marketing strategy".
It's like shearing sheep, when if comes to security.

As for your router itself, a little Googling using

make model number exploit

for your make and model, might give some idea whether
it needs a firmware update.

Paul

A quick reply after reading the article and follow their links'to see if I'm infected. It seems I'm am with man-in-the-middle because my system says something different than Google Internet Authority or Geo Trust Global.

http://i64.tinypic.com/15n8xh5.jpg

http://i68.tinypic.com/w86mx1.jpg

Robert

On Thursday, June 27, 2019 at 8:15:20 PM UTC-7, Paul wrote:
Paul wrote:
Robert in CA wrote:
Your USB device is Intel.

We need an Intel chipset driver for Windows 7,
as Microsoft doesn't do USB3 in Windows 7. Win8
and Win10 would have solved this on their own.
[]
Is USB3 backwards compatible at the _hardware_ level - in other
words, if someone has USB3 hardware on a Windows 7 system, and
_doesn't_ get the necessary driver, will it work, but just at USB2
speeds? (And maybe USB3 current limits?)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

... she has never contracted A-listeria or developed airs and graces.
Kathy
Lette on Kylie, RT 2014/1/11-17


Let me see if I understand this.. all this concerns the USB ports? I
have blue colored ports on the 8500 and they work, OK.or does
this mean something else?

Also were working toward of getting a Windows 10 Key just in case and
while I still can until
we found these yellow triangles and now trying to remove them. We
eliminated one but the other is still present.
Robert
Thanks,
Robert

We will solve this. It's just a matter of
banging on the pipes a few more times.

Paul

https://www.intel.ca/content/www/ca/...-software.html

Last Reviewed 03/08/2019

Why did Intel release two Windows* 7 USB 3.0
eXtensible Host Controller (xHCI) drivers? === Why, indeed :-/

"Download USB 3.0 xHCI Windows* 7 driver for Intel 7 Series/C216 Chipset Family"

https://downloadcenter.intel.com/Det...&DwnldID=21129

Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver .zip

5,472,920 bytes

iusb3xhc.inf === Looks like the right driver.

In 7ZIP, I see this folder. You can unpack the ZIP and
locate that x64 folder.

Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver \Drivers\Win7\x64\

Unpack that folder, which has 8 files total in it.

Open Device Manager, locate the duff USB item, do the
"Update Driver" dance, tell it you have a folder with
the goods in it, when it sees your unpacked x64 folder
with the eight files, it will install the correct one.

That's better than some "machine.inf" bull****.

HTH,
Paul



I did make (4) Delll Data Safe DVD-R (10-3-16)and have the 8500
rescue media CD-RW (7-25-15) and a Win 7 Pro master DVD-RW.

I checked all the folders and couldn't find anything with 500MB,
all KB. Here's the 1st disc and the 2-4 were all the same and
disabled the port


http://i68.tinypic.com/2uqit21.jpg

http://i64.tinypic.com/5tbno.jpg

http://i67.tinypic.com/xdia6a.jpg


I don't have 7Zip, could you please give me a link for it?

Thanks,
Robert

Robert in CA wrote:
On Thursday, June 27, 2019 at 8:15:20 PM UTC-7, Paul wrote:
Paul wrote:
Robert in CA wrote:
Your USB device is Intel.

We need an Intel chipset driver for Windows 7,
as Microsoft doesn't do USB3 in Windows 7. Win8
and Win10 would have solved this on their own.
[]
Is USB3 backwards compatible at the _hardware_ level - in other
words, if someone has USB3 hardware on a Windows 7 system, and
_doesn't_ get the necessary driver, will it work, but just at USB2
speeds? (And maybe USB3 current limits?)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

... she has never contracted A-listeria or developed airs and graces.
Kathy
Lette on Kylie, RT 2014/1/11-17

Let me see if I understand this.. all this concerns the USB ports? I
have blue colored ports on the 8500 and they work, OK.or does
this mean something else?

Also were working toward of getting a Windows 10 Key just in case and
while I still can until
we found these yellow triangles and now trying to remove them. We
eliminated one but the other is still present.
Robert
Thanks,
Robert
We will solve this. It's just a matter of
banging on the pipes a few more times.

Paul
https://www.intel.ca/content/www/ca/...-software.html

Last Reviewed 03/08/2019

Why did Intel release two Windows* 7 USB 3.0
eXtensible Host Controller (xHCI) drivers? === Why, indeed :-/

"Download USB 3.0 xHCI Windows* 7 driver for Intel 7 Series/C216 Chipset Family"

https://downloadcenter.intel.com/Det...&DwnldID=21129

Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver .zip

5,472,920 bytes

iusb3xhc.inf === Looks like the right driver.

In 7ZIP, I see this folder. You can unpack the ZIP and
locate that x64 folder.

Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver \Drivers\Win7\x64\

Unpack that folder, which has 8 files total in it.

Open Device Manager, locate the duff USB item, do the
"Update Driver" dance, tell it you have a folder with
the goods in it, when it sees your unpacked x64 folder
with the eight files, it will install the correct one.

That's better than some "machine.inf" bull****.

HTH,
Paul



I did make (4) Delll Data Safe DVD-R (10-3-16)and have the 8500
rescue media CD-RW (7-25-15) and a Win 7 Pro master DVD-RW.

I checked all the folders and couldn't find anything with 500MB,
all KB. Here's the 1st disc and the 2-4 were all the same and
disabled the port


http://i68.tinypic.com/2uqit21.jpg

http://i64.tinypic.com/5tbno.jpg

http://i67.tinypic.com/xdia6a.jpg


I don't have 7Zip, could you please give me a link for it?

Thanks,
Robert


I just asked about your recovery disks, because sometimes
one of the discs is a separate driver disc.

As for 7-zip...

https://www.7-zip.org/

there are two download links under the green. The current
version is 1900. On a 64-bit OS, you can select the
64-bit one.

Once 7ZIP is installed, you will have right-click options.
Right-click the EXE from Intel and you can

7ZIP : Open Archive

as an example. You can select a particular folder and
click the "Extract" button at the top. It will ask
where you want to store the folder, and the default
location would be next to where the EXE file is stored.

The EXE would also run and make a folder for you, but
who knows where it would be put.

For me, 7ZIP is a major tool for "peering inside stuff".
The program does not handle every format - it doesn't
have packers like UPX in it or a thing to bust
InstallShield. But for regular archives, it is pretty
good.

Paul