pluMmet

Problem now resolved. Thank you StarDock.

My last communication with Stardock support was that I needed to name the file sig2.bin instead of sig.bin. I responded 3 days ago that that did not work and I still have not gotten a response... 72 hours...this is getting ridiculous. What is the procedure for a refund?

It's been a week and i still don't have a working ObjectDock!!!! Don't you people feel badly when something like this happens and expedite the issue. At each turn I have to wait 2 days for a non working response!!!

I put it into the folder that has the ObjectDock .exe (main ObjectDock folder.) When I change it to sig2.bin it gives me a popup that says "it looks like the right activation type but is wrong" or something like that. If it's just a sig.bin file it keeps trying to get me to activate it like there is no sig file at all.

I have followed everyone heres suggestions and I'm still not able to use the program that I paid for. This is very frustrating. I have been given thru email yet another bad sg.bin file. Of course the error is that I need a sig2.bin file but even the support I'm getting straight from stardock does not seem to know this. I'm fairly angy at this point!

[quote who="Neil Banfield" reply="8" id="2994072"]Did you try renaming the sig.bin to sig2.bin? The name of the file may vary from product to product, but the format of the files should remain the same.[/quote] That I tried before I even sent in a ticket or posted here... so no that did not work.

Beyond 48 hours now... 51 hours since I put in the ticket.

Even though I only reported the trouble once it gave me 2 tickets. Here is the second [#TIE-987127] the info is the same on both tickets.

[quote who="Hankers" reply="3" id="2993210"]You may need to use the email activation procedure.[/quote] The email activation procedure is also an Impulse process. I tried it too and it also does not work. How long do these guys take to respond? I've had a trouble ticket in on this for over 24 hours...

http://www.impulsedriven.com/alternative_activation/ creates the wrong file name for activation. It creates sig.bin instead of sig2.bin So no ObjectDock for me until It's fixed or until I get a response from the email I sent Stardock support this morning [e digicons]:annoyed:[/e]