freeme2 - free software to remove DRM protection from Windows Media WMA,WMV,ASF files

Originally Posted by ZenMasta

so does this mean the enabling bits problem is solved?

What IBX version and OS do you use?

[ZenMasta]

XP Pro / Rhapsody. Dont know what version anymore because I stopped trying months back after one of my older posts. I was able to free a few songs successfully but most gave the enabling bits error. I tried following the instructions exactly.

Originally Posted by ZenMasta

XP Pro / Rhapsody. Dont know what version anymore because I stopped trying months back after one of my older posts. I was able to free a few songs successfully but most gave the enabling bits error. I tried following the instructions exactly.

And your IBX???

If Rhapsody forces your to upgrade IBX to the latest version, then you can only use lossy DRM removal software.

Otherwise please read the following thread:
HowTo Instructions for Removing DRM with drmdbg & FreeMe2 (from Windows Media Player)

[notsupported]

i have a few files which used to play but do not any more
the website which supported them says not supported

i started to look for something to solve this drm stuff and found this forum and software
i run drmdbg which extracts kid and sid keys for files
and freeme2 which created freed files

the freed files are scrambled when played in wmv players
i run freeme2 with -s and -2 switches with the same result
one thing i noticed is that the sid key is echoed diffrently than
it is saved in drmv2.key file. maybe this diffrence is causing the problem. pic shows what i am talking about

second to last key character is echoed as "k" but "l" in drmv2.key file
thank you for some hope in solving this stuff

Originally Posted by notsupported

i have a few files which used to play but do not any more
the website which supported them says not supported

i started to look for something to solve this drm stuff and found this forum and software
i run drmdbg which extracts kid and sid keys for files
and freeme2 which created freed files

the freed files are scrambled when played in wmv players
i run freeme2 with -s and -2 switches with the same result
one thing i noticed is that the sid key is echoed diffrently than
it is saved in drmv2.key file. maybe this diffrence is causing the problem. pic shows what i am talking about

second to last key character is echoed as "k" but "l" in drmv2.key file
thank you for some hope in solving this stuff

What IBX version do you have?

Neither freeme2 nor drm2wmv support the latest versions of IBX.

You have sid and kid, so you may also try to play DRM protected WMV files with MPlayer

[Chips]

In reply to 'notsupported': When I run DRMDBG against a DRM protected file I get the same SID in the program's window and in the .KEY file. It doesn't matter if I use the .KEY file or specify the SID on the command line, it still doesn't work. I don't know why your SIDs differ, sorry.

Anyway, I've got IBX version 11.0.6001.8015 and freeme2 doesn't work with DRM files any more. I'd love to know how I can get it to work again.

Try to use FairUse4WM 1.3 fix 2 with Windows Media Player 10:
Tutorial: Remove DRM from WMV on Windows XP with freeware FairUse4WM

[sectroyer]

I am willing to take a look at this. It seems that quick fix will solve the problem Please provide some more sid's that do not work with FreeMe2. The app is created in such way that it should work with any IBX version.

[notsupported]

thankyou for a quick response

i tried mplayer and it echoes out of range errors when playing
the sid must be not valid and it gets out of sync my guess
the problem seems to be sid generation

each time i run drmdbg it gives different value for sid
but the same value for kid

when running next freeme2 with new drmv2.key file the same happens
the last but second character in sid is echoed as an ascii char which has ascii code -1 eg. Y = Z - 1

[sectroyer]

First of all It's impossible to get different SID every time you launch drmdbg. If it happens it means the problem is with drmdbg and not with the freeme2. I checked the problem with the last character of SID and the problem is only with displaying. Decoded hex key is correct and this key is used for decryption. So if your SID (in drm2.key file) is correct then everything should work.