Just the other day, I tried to run 2.03c and was instead of greeted with:
"This version has expired. Please go to http://sourceforge.net ... and download the latest version." (A small popup.)
I have 2.02 installed and it works fine, as well as the new beta 2.04. I won't say they work 'fine,' but that problem entirely rests with me, lol. Additionally, I have gone to sourceforge and downloaded a couple of other 2.03 versions; b ... and c, once again ... same thing happens when I try to run them. The prompt to get the latest.
This may just be something I am unaware of, 'cause in searching the archived versions of Apophysis on sourceforge, I did take note of what I believe was an 'expiration date' of sorts for one particular version.
Ok, this enquiring mind wants to know if this is commonplace to all, or just weird me and my beloved pc.
Thanking you in advance for your time ... purmusic.
Oh k, at least we now know ... yeah, you and me and maybe counting? ... that it isn't just limited to our own beloved ethernet experiences.
Thanks Randy for the f.y.i. . I had my fingers and boot disk ready for a reformat. Uhm, I take things to the extreme some times. Read my discussion board posts. :oP
Um .. they installed an expiration date to correspond with the release of the next version .. I wasn't thinking they did it with 2.03c .. but if they did it with one they'll do it with another
second to last "paragraph" in the opening post .. (above toodles) .. it's a shame they still do that .. cancels out your option to continue using a favorite version
I really liked 2.03c as far as the random batches that were generated are concerned ... and I know not the why ... upon opening and running the program. Many a time, I would close and reopen (deleting any files generated in the first instance) and be pleasantly surprised and inspired.
I haven't delved into the heart of the beast that is 2.04 yet ... some nice additional options allowing for easier control of the transforms and those I do appreciate, given my less than exacting mouse (hmm, perhaps eyesight too, lol).
But ... so far, images look pretty grainy and the settings are the same insofar as sample density, variations et al.
Maybe I am being critical 'cause the sourceforge dingos took my 2.03c baby ... *sniff*
Yes, thanks I am aware of that ... still, for me ... the best batches, and I swear this seems to bear out statistically for me ... are the ones that would be generated upon starting and running the program. Hence, the closing and restarting on my part.
For a sec there I thought you ingeniously figured out a method to get my baby back from the dingos a la Sam's suggestion.
I have in fact been doing just that ... except ... I get scared in that neck of the woods. Just ... just managed to crawl out the other day.
Nutz, now I am sort of regretting not going for that deal with my buddy, where if you purchased two or more copies of the Windows XP bible ... uhm ... hmm, what was that deal? Oh ... yeah ... you got a copy of "A Hundred and One Mac User Jokes."
Like ... (but, of course)
Did you hear about the Mac User that went to the zoo?
He spent a half hour looking for the exit and decided that it must have escaped. :oP
Arggghhhhh !!!! I liked to go back to the oldies but goodies ! Though I can still open 2.02 .....I tried to open 2.03c & you all were right, I got the same message.....ratz !
Aye Lauren ... maybe we, I, just need to give the new version a chance to warm our collective creative spirits.
Thankfully ... thankfully we don't have to reconfigure the settings on the newer versions. And on that I am not sure if it is because, like you, I still have 2.02 residing on my HD. Hmm, there's a thought and a question. Keith addressed it this before here and the how to's (scroll down to his post of 04/23/06 12:14, and there is a little bit above as well).
As much or as little I know about the Windows registry, I am assuming that if 2.02 has been installed at least once there would be some permanent keys and values associated with versions installed afterewards. Or for that matter, as long as you have run/installed any previous version ... I think?
Hey lauren .. go to zeuek's page and show him a little leg .. (*borrow one if you have to*) .. ask him how to reverse engineer the dateline via the registry
tell him about your $800.00 dollar cabinet, bat your eyelashes, cry
Actually Keith, I had thought of trotting over there already ....grabbing him by the throat & asking him ..." Hey ! What gives ??!!!!" or something else equally gentle & lady-like & conciliatory ...;o)
Well, I'm bummed.....it doesn't work for me. Oh if I leave my date set back a year it works just fine, but as soon as I bring the date current, it won't open. Anyone else with this problem ?
"This version has expired. Please go to http://sourceforge.net ... and download the latest version." (A small popup.)
I have 2.02 installed and it works fine, as well as the new beta 2.04. I won't say they work 'fine,' but that problem entirely rests with me, lol. Additionally, I have gone to sourceforge and downloaded a couple of other 2.03 versions; b ... and c, once again ... same thing happens when I try to run them. The prompt to get the latest.
This may just be something I am unaware of, 'cause in searching the archived versions of Apophysis on sourceforge, I did take note of what I believe was an 'expiration date' of sorts for one particular version.
Ok, this enquiring mind wants to know if this is commonplace to all, or just weird me and my beloved pc.
Thanking you in advance for your time ... purmusic.