Mayayana
8/2/2010 11:34:00 PM
In addition to what others have said....
DEP prevents running executable code from
data areas. With VB I don't know of anything
that will set off DEP other than some methods
of using assembly code hacks.
I'm pretty sure there's no inherent DEP issue
with the PDW. I haven't heard of any problems.
BUT... The message you're getting implies the
problem is with setup.exe. That seems unlikely.
It may be a problem on your system. But if it
keeps happening you might try this:
www.jsware.net/jsware/vbcode.php5#set12
The original PDW is a VB project with at least 1 bug
and a lot of bloat. It also includes setup.exe written
in C++, which is mainly there to deal with installing
the runtime if necessary. These days it would be very
unlikely that you need to install the runtime. The link
above is for a rewrite of the PDW that eliminates
setup.exe, trims down setup1.exe to about half the
size, and adds new updates like the option to set
permissions, create a Desktop shortcut, create an
App Data folder, etc. There are full instructions
included.
The nice thing about using PDW is that it's VB and can
therefore be fully customized, but if you don't want to
deal with that -- and don't mind a "vanilla" installer --
a lot of people say good things about the free Inno
Setup as an alternative.
|I wrote a VB6 program used the P&D Wizard to make the setup package. I
| tried to install it on my machine to test the installer script because
| there are a couple of files that have to be installed in subfolders of
| the app.path, but when I ran setup.exe I got a DEP warning:
|
| Data Execution Prevention - Microsoft Windows
| To help protect your computer, Windows has closed this program.
| Name: Setup Bootstrp for Visual Basic Setup Toolkit
| Publisher Microsoft Windows
|
| I've never seen this before, does this indicate there is a problem with
| my system, or do I just need to turn off DEP for any VB installers?
|
| Any recommendations will be appreciated.
|
| Mike