Sorry but I dont think you can in the viewer. Security gone mad maybe! I'm
involved in Outdoor Education too and have to deal with "risk assessment gone
mad" we call it Compulsive Risk Assessment Psychosis"- I think it has an
acronym!

Signature
Did that answer the question / help?
_____________________________
John Wilson
Microsoft Certified Office Specialist
http://www.technologytrish.co.uk/ppttipshome.html
> Hello,
>
[quoted text clipped - 19 lines]
>
> Geoff
Geoff Cox - 07 Aug 2006 15:51 GMT
>Sorry but I dont think you can in the viewer. Security gone mad maybe! I'm
>involved in Outdoor Education too and have to deal with "risk assessment gone
>mad" we call it Compulsive Risk Assessment Psychosis"- I think it has an
>acronym!
too true!
Cheers
Geoff
> Hello,
>
[quoted text clipped - 9 lines]
> This seems crazy - surely it is my responsibiliy to check the CD for
> viruses before making it available to users?
Ah, but what if you aren't a nice guy? What if your a hacker sending out
presentations with a little something "special" to your competition?
> In addtion I can warn users to run their own check on the CD but the
> last thing I want is to have these MS warnings cropping up whilst the
> user is running the ppt presentations!
Not really doable is it? Yes they could scan for known viri, but lets say
you are doing something that writes to the disk or registry. Is that you
just saving a file, or is that a hacker formatting a hard drive? A virus
scanner can't tell...
> Can I stop these warnings? NB using the Viewer.
Nope
Geoff Cox - 07 Aug 2006 20:30 GMT
>> Hello,
>>
[quoted text clipped - 21 lines]
>just saving a file, or is that a hacker formatting a hard drive? A virus
>scanner can't tell...
Austin,
I see that but what is a user supposed to do - select no and not be
able to use something they have paid for?!
Geoff
>> Can I stop these warnings? NB using the Viewer.
>
>Nope
Austin Myers - 07 Aug 2006 22:32 GMT
>>> Hello,
>>>
[quoted text clipped - 26 lines]
> I see that but what is a user supposed to do - select no and not be
> able to use something they have paid for?!
That of course is up to them. :-) The problem obviously is that the end
users machine has no ability to tell the difference between running code vs
bad code, it's all just code. The only remaining alternative is to ask the
end user if they trust it enough to give it a go ahead. If there was
another alternative we could be very, very wealthy from selling it.