C
Craig
jacaranda said:I agree. Until that happens, things should stay the way they are IMHO.
Agreed.
A big thanks, btw, to Sieste for outlining Blaiz install behavior.
-Craig
jacaranda said:I agree. Until that happens, things should stay the way they are IMHO.
I guess we have different ideas of 'problem.' The .exe ending would
make it clear its not a shortcut, should you ever forget. AFAICS it
would function just as well from the start menu as program files or
anywhere else - just is not CD/USB no-install-ware.
Would it relocate itself if made read-only?
If you keep programs on your Windows drive - some people don't.
Depends on what they're doing, but quite possibly. The registry entry
isn't read-only, nor is the start menu, so you'd be left with a dead
exe file wherever you put it, plus the one that runs, located in the
start menu.
Not nice and not following any known protocol. It's just lazy
programming.
Al said:If you keep programs on your Windows drive - some people don't.
Depends on what they're doing, but quite possibly. The registry entry
isn't read-only, nor is the start menu, so you'd be left with a dead
exe file wherever you put it, plus the one that runs, located in the
start menu.
Not nice and not following any known protocol. It's just lazy
programming.
That happens every time you run the executable, and a persistant nag screen onSietse said:Susan Bugher wrote:
There is an issue with the Blaiz freeware:
the programs (not the shortcuts) are installed within the Start Menu.
This behaviour has led a number of us to not use/recommend them.