Hello audioz friend,
suddenly this morning (on the top of the Mac/LPX plug Serum) I found this written 'Error -534' and most of the plug is no longer visible.
The plug is blocked with Little Snitch... anyway nothing change: online or offline.



Has this happened to any of you, or do you know how to fix it?
I reinstalled the plug but nothing has changed.

 

Last edited: Sep 14, 2020

Check your OSX Harddrive with the Diskmanager and let him check the Filesystem.
Then Restart <

 

Done, but yet 'Error 534' it's yet there

 

Last edited: Sep 14, 2020

I'm on Windows and I've got Serum blocked in my Firewall as well. However, I get this error message in Serum too.

I normally get it when I've been browsing presets. Generally, I can just restart the plug-in and it goes back to normal.

The best I can figure out what's happening is that despite my blocking Serum in my firewall and having the various xfer domains in my host files, the app has some surreptitious way of checking in with Xfer that doesn't go through the usual channels. Or alternatively, if you've been online but have *never* checked in with Xfer, it may throw the error message up then.

I stopped using Serum for years because it was just never cracked reliably. And while I still don't think it's 100%, it works well enough to be usable for me now -- I think setting the prefs file to read only is what stops the time bomb from actually blowing the damn thing up and lets me reset.

I realize that the Mac install and the Windows install are different, but it looks like there are definite similarities in this time bomb/check in system. No idea how to fix on the Mac though. Sorry.

 

No, you don't have to apologize... Simply fantastic, you gave me an idea and it worked!

The problem is not in the installation (Mac or Win) but that Serum goes to read something here:
Users > Your name > Library > Application Support > com.xferrecords.serum > user.dat

So, trash that named 'user.dat' file in that location. Reopen your DAW and then Serum.
The plug will now open asking you for the Serial, just insert it and it's done!
That's how it worked for me, try yourself on Win and see.
I have closed and opened Logic and Serum many times and now everything works fine.

 

Last edited: Sep 14, 2020

Sorry, I think you've misunderstood me. I get the error message but then I need to do is re-start Serum and it starts working again.

I think this is because I have user.dat set to read only, so although Serum figures out that it isn't a legitimate copy from time to time, and iy tries to stop me using it, it never manages it for more than about 10 seconds.

I'm glad you've figured it out though. I suggest you try setting user.dat to read only on the Mac in case this happens again.

 

You entered an original Serial Number?

 

Error 534 means:
the user.dat file is marked read only. Just remove the write protection and the error goes away.

On windows there's a patch available that allows the usage of that file marked as read only but for Mac
there's nothing as of my knowledge. The advantage of marking it read only is: Serum isn't able to delete
the used serial key (which happens quite often by using keygenned serials). In your case I wish you luck
that your key works for you.

 

I got the serial from the ancient keygen. It worked fine when I installed v.127b6 and since then I've just been reinstalling updates on top -- currently on 1.30b1

Yeah, before I started marking it read only, Serum would work for a while and then it'd delete the serial and the whole thing would be dead again. It's been working well for some time now though.

That's really helpful to know what's going on, r4e. Thanks. I'll stop worrying about it now.