Sqlyog.ini On Vista With Enterprise 6.02

[peterlaursen]

I experienced the same first I tried Vista.  But later it (sqlyog.ini) appeared again (after I changed in Vista standard settings) .  I have changed quite a lot in Vista settings and I never researched in depth which of the settings that made the difference, but I think windows Explorer on Vista hides .ini files away in a special folder by default!  

1) try go to control panel .. folder settings .. show and

— uncheck 'hide file extensions for known file types'

— check 'show hidden files and folders

2) Check the user's 'roaming' folder.  (c:users{user}AppDataroamingsqlyog – and note AppData is a hidden folder)

I also have a sqlyog.ini there.  It is zero byte.  (and you may notice that your 'favorites' are also there on Vista!)

But I think before I disabled the Vista (crap) extended user account control feature it had some size differenct from 0 (zero).

So maybe Vista moves .ini files to that folder with that so-called security-feature enabled …

3) you may also try using command line to locate the file.  See attached image! (and I you have a non-English Vista you will also get across the most annoying localisation bug in Vista: command-line has problems with using localized folder names! – but maybe this should be considerd a 'feature'!) (my image shows the traditional position of the file, because the way I have configured Vista it stores configuration data like 2k/XP/2003 does

And if you find out the exact reason for this or can give more details, don't forget to tell!

[tomc]

Hi,

Completly random I think ! – there is a sqlyog.ini file in c:program files (x64)sqlyog enterprise – but that doesnt do anything

However the real one that actually has any affect is in c:users{user}AppDataLocalVirtualStoreProgram Files (x86)SQLyog Enterprise

Thanks for pointing me in the right direction.

I hope this helps other people – I spent hours earlier looking for the settings, not knowing if it was a vista “feature” or a change in the way sqlyog saved the settings.

Thanks,

Tom

[Author]

Posts