Unwanted Programs:

I uninstalled File Association Manager but left 7-Zip
at your suggestion.

I went into my 8200:

Dell Dimension 8200(Seagate Barracuda 7200 HD 160Gb)
with XP, SP3, with Spywareblaster, Avast, Malwarebytes and Windows
firewall.


and found (1) program I'm unsure of:

MSXML Parser

should I keep this or uninstall it? As
I understand it it helps build XML applications
whatever they are? I've never used this.


Thanks,
Robert

On 01/17/2014 08:55 AM, wrote:
MSXML Parser



I can't imagine that you would need that.

wrote:

I uninstalled File Association Manager but left 7-Zip
at your suggestion.

I went into my 8200:

Dell Dimension 8200(Seagate Barracuda 7200 HD 160Gb)
with XP, SP3, with Spywareblaster, Avast, Malwarebytes and Windows
firewall.


and found (1) program I'm unsure of:

MSXML Parser

should I keep this or uninstall it? As
I understand it it helps build XML applications
whatever they are? I've never used this.


Thanks,
Robert


According to this, you get it from being updated to SP3.
It's also dragged in with certain packages.

http://en.wikipedia.org/wiki/MSXML

I did a search on my machine and I can see bits and pieces
of 2,3,4,6 versions.

In terms of release structure, it seems to be eerily similar
to how .NET works. The difference being, I don't know what
tool you'd use, to tell what software on your computer needs
it. With .NET at least, you could scan the computer and get
some idea whether .NET is being used or not.

I'd just leave it.

As for what is XML. It's a text file. It is a container
for configuration information. Think of it as a "tiny
Registry" of its own. If you want to look at XML files,
you should be able to view them with Wordpad or Notepad,
as what is inside is just text.

Paul

On 01/17/2014 12:59 PM, philo wrote:
On 01/17/2014 08:55 AM, wrote:
MSXML Parser



I can't imagine that you would need that.



Since Paul said to leave it...I'd take his advice.

In message , Paul
writes:
[]
In terms of release structure, it seems to be eerily similar
to how .NET works. The difference being, I don't know what
tool you'd use, to tell what software on your computer needs
it. With .NET at least, you could scan the computer and get
some idea whether .NET is being used or not.
[]
Are you saying there's a way of scanning your computer to see what uses
..net? If so, how do you do it, and does it show what _version_ of .net
is being used by what?
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Sarcasm: Barbed ire

On 1/17/2014 4:59 PM, J. P. Gilliver (John) wrote:
In message , Paul writes:
[]
In terms of release structure, it seems to be eerily similar
to how .NET works. The difference being, I don't know what
tool you'd use, to tell what software on your computer needs
it. With .NET at least, you could scan the computer and get
some idea whether .NET is being used or not.
[]
Are you saying there's a way of scanning your computer to see what uses
.net? If so, how do you do it, and does it show what _version_ of .net
is being used by what?

I seem to recall there is an utility out there that tells you what
programs need for what version of .NET.

--
Bill
Motion Computing LE1700 Tablet ('09 era) - Thunderbird v12
Centrino Core2 Duo L7400 1.5GHz - 2GB RAM - Windows 8 Professional

J. P. Gilliver (John) wrote:
In message , Paul writes:
[]
In terms of release structure, it seems to be eerily similar
to how .NET works. The difference being, I don't know what
tool you'd use, to tell what software on your computer needs
it. With .NET at least, you could scan the computer and get
some idea whether .NET is being used or not.
[]
Are you saying there's a way of scanning your computer to see what uses
.net? If so, how do you do it, and does it show what _version_ of .net
is being used by what?

Another poster here, posted a script to do it.

Basically, the .NET info is in the file header. And
the CLR version is there too. The script (VBScript)
actually examined individual bytes in the file, to tell
what it was.

*******

This site has "CLRver", which does it for a single file.

http://www.devfish.net/downloads.aspx

http://www.devfish.net/.%5Cdownloads...s%5Cclrver.zip

If I run this in a command prompt window, as a test...

clrver clrver.exe

I get

clrver.exe=v2.0.50727

which is .NET 2.0

If I run it on a non-dotNET program, such as file.exe, I get

file.exe=NotCLR

and then we know that one doesn't use .NET libraries.

With sufficient scripting skills, you could make a text
file containing the names of all .exe files, then put
"clrver" in front of each line, to do the check.

*******

This was a script from Mayayana. In Jan.2012 or so.
It's no longer available, and not in archive.org either.
(checkdotnet.vbs)

http://www.jsware.net/jsware/test/dotnetv.zip

HTH,
Paul

I won't touch it then,

Thanks,
Robert

In message , Paul writes:
J. P. Gilliver (John) wrote:
[]
Are you saying there's a way of scanning your computer to see what
uses .net? If so, how do you do it, and does it show what _version_
of .net is being used by what?

Another poster here, posted a script to do it.
[]
This site has "CLRver", which does it for a single file.
[]
http://www.devfish.net/.%5Cdownloads...s%5Cclrver.zip

Thanks for that.

If I run this in a command prompt window, as a test...

clrver clrver.exe

(Though not quite an example, reminds me of my favourite glossary entry
of all time, in a manual giving the syntax of HP BASIC [for 9000 series
computers, IIRR]:
recursive see recursive)

I get

clrver.exe=v2.0.50727

which is .NET 2.0

If I run it on a non-dotNET program, such as file.exe, I get

file.exe=NotCLR

and then we know that one doesn't use .NET libraries.

With sufficient scripting skills, you could make a text
file containing the names of all .exe files, then put
"clrver" in front of each line, to do the check.

Indeed! It's a long time since I've done any such, but I _might_ be able
to manage it - if I ever need the information.

*******

This was a script from Mayayana. In Jan.2012 or so.
It's no longer available, and not in archive.org either.
(checkdotnet.vbs)

http://www.jsware.net/jsware/test/dotnetv.zip

Pity. I liked Mayayana's stuff.

HTH,
Paul
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"The thing that impresses me most about America is the way parents obey their
children." - Duke of Windsor

J. P. Gilliver (John) wrote:
In message , Paul writes:
J. P. Gilliver (John) wrote:
[]
Are you saying there's a way of scanning your computer to see what
uses .net? If so, how do you do it, and does it show what _version_
of .net is being used by what?
Another poster here, posted a script to do it.
[]
This site has "CLRver", which does it for a single file.
[]
http://www.devfish.net/.%5Cdownloads...s%5Cclrver.zip

Thanks for that.
If I run this in a command prompt window, as a test...

clrver clrver.exe

(Though not quite an example, reminds me of my favourite glossary entry
of all time, in a manual giving the syntax of HP BASIC [for 9000 series
computers, IIRR]:
recursive see recursive)
I get

clrver.exe=v2.0.50727

which is .NET 2.0

If I run it on a non-dotNET program, such as file.exe, I get

file.exe=NotCLR

and then we know that one doesn't use .NET libraries.

With sufficient scripting skills, you could make a text
file containing the names of all .exe files, then put
"clrver" in front of each line, to do the check.

Indeed! It's a long time since I've done any such, but I _might_ be able
to manage it - if I ever need the information.
*******

This was a script from Mayayana. In Jan.2012 or so.
It's no longer available, and not in archive.org either.
(checkdotnet.vbs)

http://www.jsware.net/jsware/test/dotnetv.zip

Pity. I liked Mayayana's stuff.
HTH,
Paul

I'm not very good at this stuff, but this is a copy of
"listdir3.vbs" in my scripting folder... It has no command
line parameters (I don't know how to do that), it has no
error handling, and this script will die if it hits
"Access Denied" stuff. Still, it's to illustrate how
easy it is to recursively descend into a file system.
Most of this is just copied from an example on the web :-)

' // *************** ListDir3 ****************

Dim objFSO

topDir = "E:\"
set objFSO = CreateObject("Scripting.FileSystemObject")

' Create text file to output test data
Set OutputFile = objFSO.CreateTextFile("ScriptOutput.txt", True)

Set objFolder = objFSO.GetFolder(topDir)
Set colFiles = objFolder.Files
Set colFolders = objFolder.SubFolders

For Each objFile in colFiles
OutputFile.write(objFile.Path)
OutputFile.write("\")
OutputFile.write(objFile.Name)
OutputFile.write(" ")
Outputfile.writeLine(objFile.size)
Next

For Each objSubFolder In colFolders
ScanSubFolders(objSubFolder)
Next

' Close text file
OutputFile.Close


Sub scanSubFolders(objFolder)

Set colFiles = objFolder.Files
Set colFolders = objFolder.SubFolders

For Each objFile in colFiles
OutputFile.write(objFile.Path)
OutputFile.write("\")
OutputFile.write(objFile.Name)
OutputFile.write(" ")
Outputfile.writeLine(objFile.size)
Next

For Each objSubFolder In colFolders
ScanSubFolders(objSubFolder)
Next

End Sub

' // *************** End ListDir3 ****************

I store that as listdir3.vbs. Then open command prompt,
cd to the folder holding the executable, and enter
"listdir3" as the program to execute. It'll likely
die before it finishes. Look for the text file
ScriptOutput.txt, now sitting in the same folder.

I consider any programming task as "easy", if
it takes 60 lines of code or less :-) Mainly,
because I probably couldn't successfully write
anything bigger than that.

HTH,
Paul

In message , Paul
writes:
[]
I'm not very good at this stuff, but this is a copy of
"listdir3.vbs" in my scripting folder... It has no command
line parameters (I don't know how to do that), it has no

(For batch file scripting, you use things like %1, I think; I've never
done any of this sort of thing [is this Javascript?].)

error handling, and this script will die if it hits
"Access Denied" stuff. Still, it's to illustrate how
easy it is to recursively descend into a file system.
Most of this is just copied from an example on the web :-)

Thanks for it!
[]
I consider any programming task as "easy", if
it takes 60 lines of code or less :-) Mainly,
because I probably couldn't successfully write
anything bigger than that.

HTH,
Paul

I think I'd have a similar attitude! Except that I think it might be
more like 30 lines (excluding comments) now.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Nothing is more dangerous than a boss with a spreadsheet. (Scott Adams [via
Dilbert], 1998-12-12)

I store that as listdir3.vbs. Then open command prompt,
cd to the folder holding the executable, and enter
"listdir3" as the program to execute. It'll likely
die before it finishes. Look for the text file
ScriptOutput.txt, now sitting in the same folder.

How do you direct the command prompt to the executable?
Will using listdir3.vbs remove the problem I'm having
with the malware by typing it on the command prompt
and nothing else?

Thanks,
Robert

wrote:
I store that as listdir3.vbs. Then open command prompt,
cd to the folder holding the executable, and enter
"listdir3" as the program to execute. It'll likely
die before it finishes. Look for the text file
ScriptOutput.txt, now sitting in the same folder.

How do you direct the command prompt to the executable?
Will using listdir3.vbs remove the problem I'm having
with the malware by typing it on the command prompt
and nothing else?

Thanks,
Robert

I was demonstrating how to write a copy of "dir" effectively.
VBS is some kind of scripting language. The source code
I showed, was for a script to do something similar to "dir".

Using "dir" is not going to fix your problem.

I was merely demonstrating how easy it is to code up
some recursive descent to list the file contents of a partition.

I'm not a programmer, and I like to copy stuff off the web :-)
I hope you understand.

Paul