 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have been informed by a member of my vast user base that LionSnake
does indeed run under 64-bit Windows Vista.
www.geocities.com/evilsnack/lionsnake.htm
Regards,
John
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Second that... hehehehe
One caveat, though...
With this or *any* other app that was not specifically designed for
WinVista:
NEVER accept the 'default' install path (I.E. DO NOT put it under
(drive):Program Files or (drive:Program Files (x86). This is not an issue
with LionSnake, you basically unzip & put it where ever you want (but dont
put it into a Program Files path...)
I put my LS installation in c:LionSnake
Works perfectly fine under Windows Vista Home Premium 64 bit (AMD 63 X2
5200+ Processor)
John VanSickle <evilsnackKOSHER [at] hotmail com> wrote:
> I have been informed by a member of my vast user base that LionSnake
> does indeed run under 64-bit Windows Vista.
>
> www.geocities.com/evilsnack/lionsnake.htm
>
> Regards,
> John
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Minor Corrections (StupidFingersToday): My install path c:LionSnake
My processor is AMD 64 X2 5200+ (not 63(??) X2)
Anyway - should explain - Vista seems to exhibit very strange behaviour,
designed to 'protect' your system. Vista becomes an unholy 'control freek'
with many apps under the 'Program Files' or 'Program Files (x86)' paths; if
it is an app that was not specifically designed for Vista, following strict
Vista design guidelines and blessed by the high Muckety Muckety Priest of
Microsoft Billy Gates, you find that you can't change .INI files, or
changes to .INI files have no effect; if you change settings WITHIN the app
sometimes they have no effect, etc. I had to hack my registry to get my
virus scanner to work the way it should.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
JeffBTX wrote:
> Minor Corrections (StupidFingersToday): My install path c:LionSnake
> My processor is AMD 64 X2 5200+ (not 63(??) X2)
>
> Anyway - should explain - Vista seems to exhibit very strange behaviour,
> designed to 'protect' your system. Vista becomes an unholy 'control freek'
> with many apps under the 'Program Files' or 'Program Files (x86)' paths; if
> it is an app that was not specifically designed for Vista, following strict
> Vista design guidelines and blessed by the high Muckety Muckety Priest of
> Microsoft Billy Gates, you find that you can't change .INI files, or
> changes to .INI files have no effect; if you change settings WITHIN the app
> sometimes they have no effect, etc. I had to hack my registry to get my
> virus scanner to work the way it should.
Reason #475 that I am going to make the app Open Source very soon...
Regards,
John
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
JeffBTX wrote:
> Minor Corrections (StupidFingersToday): My install path c:LionSnake
> My processor is AMD 64 X2 5200+ (not 63(??) X2)
>
> Anyway - should explain - Vista seems to exhibit very strange behaviour,
> designed to 'protect' your system. Vista becomes an unholy 'control freek'
> with many apps under the 'Program Files' or 'Program Files (x86)' paths; if
> it is an app that was not specifically designed for Vista, following strict
> Vista design guidelines and blessed by the high Muckety Muckety Priest of
> Microsoft Billy Gates, you find that you can't change .INI files, or
> changes to .INI files have no effect; if you change settings WITHIN the app
> sometimes they have no effect, etc. I had to hack my registry to get my
> virus scanner to work the way it should.
That's because INI files (and other configuration files) for programs
should not be in Program Files along with the programs' binaries. They
should be stored in the appropriate place in the Users folder ("The Folder
Formerly Known as Documents and Settings").
Lance.
thezone - thezone.firewave.com.au
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
