This page is a wiki. Please login or create an account to begin editing.


25 posts / 0 new
Last post
gingerbeardman's picture
Offline
Joined: 2018 Aug 1
Snapz Pro 2 registration problem

I am using Basilisk II

I downloaded SnapzPro 2.01 and tried both of the the 68K-compatible serial numbers listed on the page
https://macintoshgarden.org/apps/snapz-pro-2

the registration app recognises and says it is registered.

but the main app still says unregistered and i see a nag every reboot.

any help appreciated.

Comments

MikeTomTom's picture
Offline
Joined: 2009 Dec 7

I can't help with this one on 68k Mac... I did install it for a while and gave up for the same reasons you are experiencing.

I "downgraded" and installed Snapz Pro version 1.1.1 on Basilisk II

Not as many features as version 2, but at least it can save screenshots to JPEG.

It works well enough and without nags.

WhosIt.There's picture
Offline
Joined: 2014 Aug 23

Setting the system date back to around the app's released date before entering the registration code works for some old OS X versions of Snapz Pro, but I don't know about the 68K versions.

gingerbeardman's picture
Offline
Joined: 2018 Aug 1

I need PNG saving, and have installed QuickTime Picture Viewer to enable Snapz Pro 2 to save as PNG.

I'll keep searching for a solution.

Date trick did not work for me.

WhosIt.There's picture
Offline
Joined: 2014 Aug 23

I can't test it, but try this generated registration code for version 2:

Name: Anon
Copies: 1
Code: KMGEFPNI

Again, it may or may not need the system date reverted before entering.

gingerbeardman's picture
Offline
Joined: 2018 Aug 1

That isn't accepted at all.

I read there are different codes for 68K vs PPC. I need 68K codes, there are two 68K codes listed on the page. Codes that are bundled with the app are PPC.

Elyus's picture
Offline
Joined: 2009 Aug 9

A few weeks back, the details of Ambrosia's registration systems were shared on reddit. I just fiddled around with the 68k version of Snapz Pro 2, and it appears to use the original registration system, with the application name in the hash being "Snapz Pro 2".

The problem you're encountering sounds like codes that have been internally blacklisted by Ambrosia's registration app. It pretends to register but doesn't actually. I recommend using the v1 registration script posted on reddit to roll your own code. For instance, I downloaded it and ran:


python aswreg_v1.py "Anon" 1 "Snapz Pro 2"

and received

GGJFDJEH

I then tried entering "Anon", 1 copy, and code "GGJFDJEH" in the registration app, and it appears to work. You'll probably need to delete the "Snapz Pro 2 License" file under System Folder -> Preferences before entering this code.

It's interesting that the 68k version is still using their original hashing method. Later versions of Snapz Pro upgraded to Ambrosia's fancy expiring code system, which has been reverse-engineered but is more difficult to generate usable codes.

At any rate, I hope this helps fix the problem for you!

Edit: @WhosIt.There, I just noticed your code as well. It looks like you generated it including the $DEADBEEF hash, which honestly I figured Snapz Pro 2 would use! Apparently, they never bothered to update the registration app for the 68k version, which surprises me. I guess they figured no one was really using 68k anymore once they shifted fully to PPC.

WhosIt.There's picture
Offline
Joined: 2014 Aug 23

I just used the old Buck's Serial Number Generator (BSNG) app with the Snapz Pro 2 plug-in. Possibly the emulator / ROM used made it think it was a PPC or maybe the plug-in doesn't create 68K codes at all.

Elyus's picture
Offline
Joined: 2009 Aug 9

Interesting! I'm actually not at all familiar with that serial generator. I don't see it on the Garden either; would it be something that's allowed to be posted? I'm very curious to take a look at it.

WhosIt.There's picture
Offline
Joined: 2014 Aug 23

I don't know if it's allowed / wanted on MacintoshGarden either, although it is mentioned in a couple of topics. I can't remember where I got it years ago, but it's an old program that has a pile of plug-ins to know how to the generate serial numbers for various other old programs.

I did a quick Google search and I found a copy is downloadable (with more plug-ins then I already had) from WEBSITE_NAME_CENSORED Wink - the naughty website that steals all of the MacintoshGarden's uploads and data without asking, but does have a few bits not on here.

MikeTomTom's picture
Offline
Joined: 2009 Dec 7

Thanks for this information and post, Elyus.
Unfortunately the py script didn't work for me. I DL'd the script, ran it, getting this error:

macbook:Ambrosias mike$ python aswreg_v1.py "mike" 1 "Snapz Pro 2"
Traceback (most recent call last):
  File "aswreg_v1.py", line 2, in 
    from bitstring import BitArray
ImportError: No module named bitstring
macbook:Ambrosias mike$ 

It got as far as line 2 of the script and failed.

Any suggestions, or even possibly run the script using the lower-case "mike" for me ?

Elyus's picture
Offline
Joined: 2009 Aug 9

Here's what I got using "mike" and 1 copy: NFKLCJEO

From the error message, it looks like the bitstring module needs to be installed on your system, so if you have pip you could use


sudo pip install bitstring

as an administrator user. If the "pip" command fails, you should be able to use easy_install, bundled with Macs, to install it by running


sudo easy_install pip

first and then running the pip command.

It also looks like python3 will fail unless you apply the changes described by mrxak in the reddit post, but if you're using the base python on Mac OS, that should be 2.7 and not have any issues.

Hopefully that will work but let me know if you still have a problem!

MikeTomTom's picture
Offline
Joined: 2009 Dec 7

Thanks for that Elyus. I hadn't checked the (very important) reddit link in your post above, before I went ahead with running the script from the 2nd link. Glasses

I needed to then find and install the bitstring module - and the python aswreg_v1.py command then worked as you 1st reported ! - I got the same code output for "mike" as what you did.

So, thanks for this news, it looks like a great tool to have for dealing with the Ambrosia back-catalog.

[Edit] Except... I tried it out on Snapz Pro 2 on Basilisk II and it still shows Snapz as unregistered.

Elyus's picture
Offline
Joined: 2009 Aug 9

Now that is odd. I see the same but the license seems to be ok. Is it possible there's a mismatch between the Snapz Pro application and the registration application? I expected Snapz Pro 2's registration would use the expiring code system, so maybe we're missing the updated register app. We should look for another Snapz Pro 2 demo and see what's bundled with that I guess.

MikeTomTom's picture
Offline
Joined: 2009 Dec 7

Yes, maybe. I was using the copy we have here at the MG. Tho' it does have an installer and this installs both the CP and the registration program at the same time.

Try setting the system date back perhaps?

-- Nope, still no luck for me. Rats. Sad

[Edit] I have discovered tho', that Snapz Pro 2 installs a hidden file into the Preferences folder named "thaumaturgy.log". This is the date and time stamp that will trigger the shareware reminders after x number of days and then really begin the nags, proper.

Deleting "thaumaturgy.log" anytime the nags appear after x # of days, will allow you to run Snapz on 68k Mac's without too many interruptions, indefinitely. Writing a wee shutdown script should see it cleared each time you rebooted the Mac, which would mean zero nags from then onwards, registered or not.

[Edit 2] I may have found a workaround, see my response to mrdav's post.

Elyus's picture
Offline
Joined: 2009 Aug 9

I wonder how thaumaturgy.log ties into registration verification. Maybe it's part of the problem.

Either way, I'm glad to see you found a workaround!

MikeTomTom's picture
Offline
Joined: 2009 Dec 7

So far it seems to be working.

I think the log file is just a date & time stamp and is used by Snapz to determine when to start nagging, if it remains unregistered.

I also think the registration app is the problem on 68k installs. Curiously the registration app on 68k installs a "fwst" resource into the CP, containing I assume the reg info. On PPC installs, it inserts a "kwst" resource into the CP. I'm assuming that fwst is the location for blacklisted names and kwst is for whitelisted names. As the copied over CP and license from a successful PPC install, instantly becomes a valid registered CP on 68k Macintosh.

mrdav's picture
Online
Joined: 2011 Dec 3

Given the difficulties others have had using the serial on the Snapz Pro 2 page, I have to say that I have not experienced any problems registering using the second serial listed on that page (didn't try the first one). I am running Mac OS 9.2.2 on a G4 iMac. Maybe the registration process is not compatible with emulation?

MikeTomTom's picture
Offline
Joined: 2009 Dec 7

Hi mrdav: The issue here is not the PPC install but installing it onto 68k Mac systems where the problem is...

I think now that I have a working solution, if a password for 68k isn't found: i.e.;

Install it on PPC (SheepShaver is fine for this) and register it, I used the HotSix code from the included serials in the DL. Then run Snapz on PPC to ensure the registration is set.

Next, copy the installed Snapz Pro 2 Control Panel and the Snapz Pro 2 License from the Preferences folder over into a 68k Mac or Basilisk 2, etc, placing them into the Control Panels and Preferences folders, respectively.

Restart the 68k Mac or emulator and all should be OK. This has seemingly worked for me as I now have Snapz Pro 2 installed on a 68k Mac registered to the codes used in the PPC install.

The installed Snapz Pro Control Panel's architecture is 68k encoded (contains no PPC code) so it's no problem using it on either platform, just curious as to why registering in on 68k is such an issue.

Jatoba's picture
Offline
Joined: 2018 Apr 16

Install it on PPC (SheepShaver is fine for this) and register it, I used the HotSix code from the included serials in the DL. Then run Snapz on PPC to ensure the registration is set.

This is smart. Smile Brilliant bypassing.

m68k's picture
Offline
Joined: 2016 Dec 30

I myself was never able to get Snapz Pro registered on B-II and I tried *hard*. I ended up switching to another screen capture tool and call it a day.

MikeTomTom's picture
Offline
Joined: 2009 Dec 7

It's easy enough to install this on PPC, register it with the PPC code, then move it over for use in 68k Mac...

But I was forgetting about you hard core Mac 68k only users Wink

I've uploaded a preinstalled, registered copy to the Snapz Pro 2 page, if you care to revisit it (works on B2).

What was the other 68k screen capture tool, btw, if you remember it's name?

m68k's picture
Offline
Joined: 2016 Dec 30

I am on Screen Catcher now and not sure if Snapz Pro has anything to offer, that SC hasn't. Took me long enough to settle on a good capture tool and unless I get some extra value out of this, I don't feel like going back. Specially if anything happens to the prefs info where the reg code is stored, the whole darn registration hassle starts all over again. Shock

PS: I am die hard 68k and if I had my way about it, I'd demand the whole darn Internet be run on 68k clusters Laughing out loud

m68k's picture
Offline
Joined: 2016 Dec 30

Before reboot the CP did not accept the lucense code and after boot it hangs my system. Shock
So I guess Snapz and I just won't snap it together.

MikeTomTom's picture
Offline
Joined: 2009 Dec 7

Pity it didn't work for you. I have it working on 2 different B2 builds and Mini vMac (Mac II build), so maybe it's an Extensions conflict on your side? At least you have something that works (Screen Catcher) thanks for the link for it.