Licensing problem Vista 64 from v.8.0.0.3

[Darwin]

This persists in the latest build (8.0.04). I have a lifetime licence for XYPlorer and have had no problem with running it "unlocked" on this machine... until yesterday!. I have my start menu, desktop and quick lauch bar links configured to launch XYplorer using "Run as administrator" privileges on a Vista 64 bit (Sp-2) installation. After updating from 8.0.01 to yesterday's beta (8.0.03) these links run the app in trial mode, while launching the exe file by double clicking it from within Windows Explorer (ie NOT as administrator) starts XYplorer running normally (ie fully licensed and configured as I am used to). I'm not sure what other information to give you, so please ask questions if necessary! FWIW, I'm running a Core 2 Duo notebook with 4GB RAM...

EDIT: made some adjustments in hopes of making this more clear...

[admin]

Hmm, nothing in yesterday's release could have possibly anything to do with that. Can anybody confirm such problems?

[Darwin]

Just to add to the above - if I iright click the exe file at C:\Program Files (x86)\XYplorer\XYplorer.exe and select "Run as administrator", XYPlorer opens in trial mode, if I simply double-click it it launches no problem. This is expected, given the other behaviour that I've seen, but I thought I'd note it here to be thorourgh.

[Darwin]

Weird. I updated to 8.0.0.6 this morning using the No-install package and the problem persists. On a whim, I checked a USB installation of XYplorer that I hadn't gotten around to updating. It was at a beta version of v.8 (forget the build - 415, I think) and I verified this morning that it opens "licensed" under Vista 64 bit when "Run as administrator". So, I used the same No-install update to get it to version 8.0.06 and it still worked fine (ie opened with Admin privileges on Vista 64). I selected the new files from it's directory on my thumbdrive and overwrote the same files in C:\Program Files (x86)\XYplorer with them et voila! I can now run XYplorer Licensed on my Vista machine. Not sure what happened there, but it's fixed now...

[admin]

When you open the Configuration Dialog (F9) the titlebar will tell you the path to the current application data folder. This folder should be writable.

[Jeeves]

Running all the latest betas and no such issue on my Vista 64 machine.

[Darwin]

That's a useful tip, thank you Don. Just to be clear, though, I appear to have fixed the problem... which I have just verified by updating to 8.0.0.7 via the No-install download from the BETA version thread.

[noir]

similar problem just pop-uped up today for me too in .0008 upgraded from 0004 i think, in windows 7 64, said something about my license, only happens in windows 7 64, runs fine for hours in my virtualbox /w XP 32bit, (unless i wasn't supposed to run it under two OS and it broke it :X).

[zer0]

similar problem just pop-uped up today for me too in .0008 upgraded from 0004 i think, in windows 7 64, said something about my license, only happens in windows 7 64, runs fine for hours in my virtualbox /w XP 32bit, (unless i wasn't supposed to run it under two OS and it broke it :X).

I do not think it's about running it on two operating systems simultaneously. Licence definition states

Code: Select all

As an individual person, you need a license to use XYplorer. 
This license grants you a non-exclusive and non-transferable 
right to use XYplorer on any number and kind of devices.

[admin]

similar problem just pop-uped up today for me too in .0008 upgraded from 0004 i think, in windows 7 64, said something about my license, only happens in windows 7 64, runs fine for hours in my virtualbox /w XP 32bit, (unless i wasn't supposed to run it under two OS and it broke it :X).

Again: When you open the Configuration Dialog (F9) the titlebar will tell you the path to the current application data folder. This folder should be writable.

I see no other ways licensing could fail.

[noir]

similar problem just pop-uped up today for me too in .0008 upgraded from 0004 i think, in windows 7 64, said something about my license, only happens in windows 7 64, runs fine for hours in my virtualbox /w XP 32bit, (unless i wasn't supposed to run it under two OS and it broke it :X).

Again: When you open the Configuration Dialog (F9) the titlebar will tell you the path to the current application data folder. This folder should be writable.

I see no other ways licensing could fail.

folder is writable and fine nothing has changed. XY has worked fine until recently , it seems to only happen on copy / move & winrar shell extensions and only in windows 7 64bit (maybe OS language /unicode has something to do with it too?).

[admin]

similar problem just pop-uped up today for me too in .0008 upgraded from 0004 i think, in windows 7 64, said something about my license, only happens in windows 7 64, runs fine for hours in my virtualbox /w XP 32bit, (unless i wasn't supposed to run it under two OS and it broke it :X).

Again: When you open the Configuration Dialog (F9) the titlebar will tell you the path to the current application data folder. This folder should be writable.

I see no other ways licensing could fail.

folder is writable and fine nothing has changed. XY has worked fine until recently , it seems to only happen on copy / move & winrar shell extensions and only in windows 7 64bit (maybe OS language /unicode has something to do with it too?).

Hmmm, the licensing is utterly trivial - it cannot fail. You find the registration information at the top of the INI file (Name=...; Key=...). Open it and look at it. When you have your problem, what happens to it?

[noir]

your guess is as good as mine, i don't know the inner workings so i don't know why its failing
but it does it in trial mode too, even after removing the ini or deleting the section in the ini
[Register]
Name=***
Code=***
dc=***

it pops up a message saying there is a problem with your key and closes , only when using the context menu if i do nothing or just click around it stays open fine.

do you use tmxprotector for this app? cause i was messing around with that for my own program, (although it shouldn't effect this since i believe this is programed in VB where tmxprotector is for delphi)

[admin]

it does it in trial mode too, even after removing the ini or deleting the section in the ini
[Register]
Name=***
Code=***
dc=***

it pops up a message saying there is a problem with your key and closes , only when using the context menu if i do nothing or just click around it stays open fine.

do you use tmxprotector for this app? cause i was messing around with that for my own program, (although it shouldn't effect this since i believe this is programed in VB where tmxprotector is for delphi)

Please send me the name and key.

[zer0]

Has this problem been resolved? If so, how? Licensing problems when Don's away on holiday are some of the worst ones that could have happened.