FL Studio 8 regcode isn't accepted
FL Studio 8 regcode isn't accepted
Has anyone else experienced this?
Running the latest wine 0.9.58. FL7 installed alongside accepts the new regcode, FL8 doesn't and is a demo.
Running the latest wine 0.9.58. FL7 installed alongside accepts the new regcode, FL8 doesn't and is a demo.
Re: FL Studio 8 regcode isn't accepted
What's the full name of your program?flat wrote:Has anyone else experienced this?
Running the latest wine 0.9.58. FL7 installed alongside accepts the new regcode, FL8 doesn't and is a demo.
I've been following this bug since FL7.4-ish and Wine 0.9.5?-ish. I suspect this is an advapi32 problem because I see no calls (directly) to crypt32 or rsaenh, but I am not crypto expert. It could also be related to the way Wine checks time/date, since these FL beta reg codes are all time-limited expiring. If so, then this problem (might) go away when FL8 is officially released (ie if it is not time limited).
I also see there are various issues with values being read from the registry by other unrelated programs, so that could be part of the problem. For example my Goldwave program intermittently loses it's registration code and I have to re-enter it. Once entered though, it works for a while (versus FL where it never works). The only reason I have not filed a bug report is that FL8 is not publicly available and is in beta. It would no doubt help to regress back to a Wine version that works, but there may not be one, as the problem might be the combination of (the newer) FL and Wine.
Bill
I also see there are various issues with values being read from the registry by other unrelated programs, so that could be part of the problem. For example my Goldwave program intermittently loses it's registration code and I have to re-enter it. Once entered though, it works for a while (versus FL where it never works). The only reason I have not filed a bug report is that FL8 is not publicly available and is in beta. It would no doubt help to regress back to a Wine version that works, but there may not be one, as the problem might be the combination of (the newer) FL and Wine.
Bill
FL Studio 8 was officially released two days ago and it's not a beta anymore and it is publically available for download at www.flstudio.combillstei wrote: The only reason I have not filed a bug report is that FL8 is not publicly available and is in beta.
I actually tried the previous verson of Wine (0.9.46?). I ran FL7 on it with no glitches, then installed FL8. Seeing it doesn't accept my regcode I upgraded Wine to 0.9.58, but still the same problem. It just won't get out of demo mode (I have the latest FL8 regcode).billstei wrote:
It would no doubt help to regress back to a Wine version that works, but there may not be one, as the problem might be the combination of (the newer) FL and Wine.
Use one of your (20) *votes* for bug 12279:
http://bugs.winehq.org/show_bug.cgi?id=12279
Bill
P.S. And vote for all the rest of the bugs too: http://appdb.winehq.org/objectManager.p ... &iId=11368
P.P.S. FLSynthmaker is going to be another big problem...(I think)
http://bugs.winehq.org/show_bug.cgi?id=12279
Bill
P.S. And vote for all the rest of the bugs too: http://appdb.winehq.org/objectManager.p ... &iId=11368
P.P.S. FLSynthmaker is going to be another big problem...(I think)
I have voted for 12279, Will look at the other bugs soon. Thanks.billstei wrote:Use one of your (20) *votes* for bug 12279:
http://bugs.winehq.org/show_bug.cgi?id=12279
Just tested FL8 with Wine 1.0 rc3 and FL does not accept the reg code.
About a month ago I did some debugging and what I can say is that Wine appears to be reading the reg code from the registry okay (every char had a leading 00 which I assume is unicode? Is that screwing it up? No idea.) I think this has something to do with the way that Wine reports back date/time. There was at least one bug/thread that discussed the year-month-day default formats of date/time in Wine -- related? I'm just shooting in the dark, but this may not be a cryptographic problem at all.
This is a complete show-stopper from my point of view for FL Studio. Being able to run the demo and not the registered version is about the same as not being able to run it.
Bill
About a month ago I did some debugging and what I can say is that Wine appears to be reading the reg code from the registry okay (every char had a leading 00 which I assume is unicode? Is that screwing it up? No idea.) I think this has something to do with the way that Wine reports back date/time. There was at least one bug/thread that discussed the year-month-day default formats of date/time in Wine -- related? I'm just shooting in the dark, but this may not be a cryptographic problem at all.
This is a complete show-stopper from my point of view for FL Studio. Being able to run the demo and not the registered version is about the same as not being able to run it.
Bill
You should probably use Wine 1.1.5 at this point if you want to have something more current. The only step that you need to change is the configure. Instead of these typical steps:
./configure
make depend
make
You would use this:
CC="gcc-4.1" ./configure
make depend
make
You will of course need to have the gcc-4.1 package installed in order to use it, and here on my debianish Ubuntu, gcc 4.1 can peacefully coexist alongside gcc 4.2.x without issue.
I also prefer to put Wine into /usr (rather than /usr/local ) and then use checkinstall to generate a deb, so my own personal scheme looks like this:
CC="gcc-4.1" ./configure --prefix=/usr
make depend && make
sudo checkinstall --install=no
sudo dpkg -i [whatever_package_you_just_created].deb
Checkinstall unfortunately is not without it's quirky problems... it helps to have both wine and wine-dev packages installed prior to running checkinstall, and once checkinstall has created the deb (but not installed it yet) remove both wine and wine-dev, then install the deb.
Bill
./configure
make depend
make
You would use this:
CC="gcc-4.1" ./configure
make depend
make
You will of course need to have the gcc-4.1 package installed in order to use it, and here on my debianish Ubuntu, gcc 4.1 can peacefully coexist alongside gcc 4.2.x without issue.
I also prefer to put Wine into /usr (rather than /usr/local ) and then use checkinstall to generate a deb, so my own personal scheme looks like this:
CC="gcc-4.1" ./configure --prefix=/usr
make depend && make
sudo checkinstall --install=no
sudo dpkg -i [whatever_package_you_just_created].deb
Checkinstall unfortunately is not without it's quirky problems... it helps to have both wine and wine-dev packages installed prior to running checkinstall, and once checkinstall has created the deb (but not installed it yet) remove both wine and wine-dev, then install the deb.
Bill