This type SPAM can cause you real grief. It is possible to hide code in an
image file, due to space not used by the system between pixels. Be very
careful playing with anything like this with a *.scr file. Course it may
even be walk-on to another file with the capability of executing code to
your computer.

good computing,
don
----------




<(E-Mail Removed)> wrote in message
news:mwxdb.8228$l%(E-Mail Removed)...
Pics from my hidden cam of my neighbour tanning in her garden check them
here

http://www.hoofpawfeather.com/NudeNeighbourTanning.scr

"dcdon" <(E-Mail Removed)> wrote in message
news:hdFdb.170891$(E-Mail Removed)...
> This type SPAM can cause you real grief. It is possible to hide code in an
> image file, due to space not used by the system between pixels. Be very
> careful playing with anything like this with a *.scr file. Course it may
> even be walk-on to another file with the capability of executing code to
> your computer.

The thrust of your warning is correct (.scr files can harm you) but it isn't
because of "code...between the pixels" but because Screensaver files
are executables.

Check your command line Assoc for .scr:

assoc .scr

It's (usually) assigned to "scrfile" so check the FType for that:

FType scrfile

And you will find it is "run directly" by the system -- and if you look
around for a .scr (e.g., Logon.scr in System32) and "run it" you will
find the screen saver running. (You must type the full name if you
use the command prompt.)

Screen savers are FAR more than "just the pretty pictures" (usually.)

Surprisingly these can be run directly but are not included in
PATHEXT (by default.)

--
Herb Martin

Good Show...
Thank you Herb

don
----------



"Herb Martin" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
"dcdon" <(E-Mail Removed)> wrote in message
news:hdFdb.170891$(E-Mail Removed)...
> This type SPAM can cause you real grief. It is possible to hide code in an
> image file, due to space not used by the system between pixels. Be very
> careful playing with anything like this with a *.scr file. Course it may
> even be walk-on to another file with the capability of executing code to
> your computer.

The thrust of your warning is correct (.scr files can harm you) but it isn't
because of "code...between the pixels" but because Screensaver files
are executables.

Check your command line Assoc for .scr:

assoc .scr

It's (usually) assigned to "scrfile" so check the FType for that:

FType scrfile

And you will find it is "run directly" by the system -- and if you look
around for a .scr (e.g., Logon.scr in System32) and "run it" you will
find the screen saver running. (You must type the full name if you
use the command prompt.)

Screen savers are FAR more than "just the pretty pictures" (usually.)

Surprisingly these can be run directly but are not included in
PATHEXT (by default.)

--
Herb Martin