Debugger allergic to the string 'install'

[Blue]

It took me quite a while to nail this one, and i still can't believe it...
This happens with PB 4.20, final, under Vista SP1.

If the string "instal" (single L, not a typo here) appears within the File Description Field ( listed as VersionField6 at the bottom of source files),
you get (well, at least I do!!!) the following message:

Code: Select all

 ---------------------------
  PureBasic
 ---------------------------
  Cannot execute the file with the internal debugger. 
  Please try the standalone one.
 ---------------------------
      [ OK ]

and you can't compile and run the appllication.

For instance, I had something like "Replacement File installed by TorqueCounter" entered as File Description.
With the debugger ON , I couldn't get the source to compile.
With the debugger OFF, it compiled without a hitch.

Changing the description to "Replacement File insta_lled by TorqueCount" made the problem go away.
Removing the string altogether was also a good option.

You have to admit: that's indeed a strange one !!!

I'm not even sure it's a bug.
What if it's a hidden feature... that I'm just too blue to see ?

Please, Freak, come rescue my self-esteem...

[freak]

You can thank M$ for that. Its not the debugger's fault.

Vista decides wether a program might be a setup program (and therefore requires admin rights)
by looking at stuff like filename, version info etc.

What happens here is that vista finds the "install" string and decides this must be a setup program.
The IDE/Debugger do not have the rights to execute this program then.
(You can see this if you create an executable from this program. It will get the "shield" icon)
I guess you probably run an admin account and have UAC turned off ? Then you can run the compiled exe without noticing anything.

Simple solution:
Turn on the "Request User mode for Vista" option in the Compiler options.
This tells Windows that it is no setup and it will stop guessing.


(btw, there is no need for all the colors and bold text. I can read normal text just fine )

[djes]

[Mistrel]

So if an installer does not request administrative rights I can install it from a normal account if I hex edit a couple of strings? :roll:

[freak]

Just call it "setup.exe" or "install.exe" and it will prompt you for admin rights when you try to run it

[Num3]

LOL

[Blue]

You can thank M$ for that. Its not the debugger's fault.

So, just another quirky twist that M$ seems to have an endless suplly of, huh?

For my sanity, I badly needed the rational explanation you just provided. I didn't need a fix (none needed, nothing broken) but i really wanted to know what had me losing a couple of precious hours.

Ahhhh... You've just saved my marriage again. So,
Thanks , Freak
Amazing the lenghts to which PB developers will go to help people.

BTW: so, my intuition was right on. It is NOT a bug, but a hidden feature, indeed, albeit one that I have no use for.

[Blue]

What happens here is that vista finds the "install" string and decides this must be a setup program. [...]
(btw, there is no need for all the colors and bold text. I can read normal text just fine )

The most irritating part of this is that Vista does not even look for "install" (with 2 L's). "instal" (with a single L), even as part of some totally unrelated word, is enough to trigger the reaction.

BTW: The colors aren't there for you, Freak. They're for me, so that...
(1) I know where I'm at
(2) I take good care of my allergy to a monochrome world
(3) I can impress my children with my abilities.

[blueznl]

BTW: The colors aren't there for you, Freak. They're for me, so that...
(1) I know where I'm at
(2) I take good care of my allergy to a monochrome world
(3) I can impress my children with my abilities.