Log in

View Full Version : Setup BD-RB with Win 7


Pages : 1 [2]

MickJT
18th March 2011, 17:15
Yes, but I can modify FF_RESET.BAT with the values needed to do it in "reverse-reverse", i.e set it up the way BD-RB needs it, and it works fine. Procmon is just showing me that in the BD-Rebuilder.exe process, no attempts are being made to alter anything except the AVC preferred filter, whether there's a permissions issue or not; It would still show up. Willing to run any tests you might have for me.

jdobbs
18th March 2011, 18:24
Yes, but I can modify FF_RESET.BAT with the values needed to do it in "reverse-reverse", i.e set it up the way BD-RB needs it, and it works fine. Procmon is just showing me that in the BD-Rebuilder.exe process, no attempts are being made to alter anything except the AVC preferred filter, whether there's a permissions issue or not; It would still show up. Willing to run any tests you might have for me. It is working for me, and it's been working for other users for a long time now as well -- that would seem to indicate it has to be something specific to your system. I can't imagine how it would work differently just because it is executed through a shell call via the O/S, though.

MickJT
18th March 2011, 18:43
It isn't specific to my system. Bokker is having the same issue, but you guided him through fixing it up manually. sbtuttle has the same issue, and couldn't be bothered with all the hard work to fix it up.

My HDD died recently and I simply installed Windows 7 64bit, fresh (no image restore), then ffdshow, Haali, AviSynth and BD-Rebuilder. There's nothing fancy on here. Again, procmon shows BD-Rebuilder isn't even attempting to fix up the other keys. So, whether it is something with my system or not, it must still be a bug. BD-Rebuilder should at least be trying, and it is successful at changing the AVC filter, but it doesn't try to change anything else other than that. It is able to read all 3 keys. It only tries writing one of them (AVC) when it's not set up correctly, and that works fine. So it's not failing at doing something, but actually not attempting it in the first place.

I do need to stress that this system is fresh. Plain Win 7 64bit install, Firefox, Haali, AviSynth, ffdshow, BD-Rebuilder, iTunes, VideoLAN. That's it. No virus checker, nothing. Oh, and AnyDVD HD but I only just put that on there today. I also installed Win 7 Service Pack 1.

Would you like me to send you a link to a full procmon log (nothing excluded from the list)?

Edit: Woah. Hold on, it appears to be working now. Double-checking.

I found the cause. Still a bug, sort of. Wait for an edit. Check next post.

MickJT
18th March 2011, 19:24
OK. The culprit is Win 7 DS Filter Tweaker. After running that, it does something that I can't detect that prevents BD-Rebuilder from setting the registry keys. BD-Rebuilder doesn't even make FF_CONFIGURE.BAT (I wish it didn't delete it, so I could view what was in it).

Here is where it gets weird. Open up regedit, and double-click on {31435641-0000-0010-8000-00AA00389B71}

Change it (the value inside the key, not the key itself) to something else (regedit won't save non-edits).

After that, it's fine, BD-Rebuilder can do its thing. The weird thing is, no matter whether it's the AVC, VC-1 or MPEG-2 codec you changed in Win 7 DS Filter Tweaker, it is the {31435641-0000-0010-8000-00AA00389B71} key (AVC) that must be re-saved before BD-Rebuilder is able to fix the VC-1 / MPEG-2 keys and all the ffdshow settings.

At least you know what to look for now jdobbs! Run the tweaker program. It won't mess anything up, I promise (well, other than present this bug/issue to you).

Remember it's not only Win 7 DS Filter Tweaker that may do something like this that prevents BD-Rebuilder from fixing it. Seeing as regedit (or FF_RESET.BAT) works to fix it so BD-Rebuilder can fix the settings again, i'm a bit baffled. Is it a permissions issue or not? Hmm.

jdobbs
18th March 2011, 19:45
OK. The culprit is Win 7 DS Filter Tweaker. After running that, it does something that I can't detect that prevents BD-Rebuilder from setting the registry keys. BD-Rebuilder doesn't even make FF_CONFIGURE.BAT (I wish it didn't delete it, so I could view what was in it).

Here is where it gets weird. Open up regedit, and double-click on {31435641-0000-0010-8000-00AA00389B71}

Change it (the value inside the key, not the key itself) to something else (regedit won't save non-edits).

After that, it's fine, BD-Rebuilder can do its thing. The weird thing is, no matter whether it's the AVC, VC-1 or MPEG-2 codec you changed in Win 7 DS Filter Tweaker, it is the {31435641-0000-0010-8000-00AA00389B71} key (AVC) that must be re-saved before BD-Rebuilder is able to fix the VC-1 / MPEG-2 keys and all the ffdshow settings.

At least you know what to look for now jdobbs! Run the tweaker program. It won't mess anything up, I promise (well, other than present this bug/issue to you).

Remember it's not only Win 7 DS Filter Tweaker that may do something like this that prevents BD-Rebuilder from fixing it. Seeing as regedit (or FF_RESET.BAT) works to fix it so BD-Rebuilder can fix the settings again, i'm a bit baffled. Is it a permissions issue or not? Hmm. So how does an issue with "Win 7 DS Filter Tweaker" suddenly become my problem to fix?

MickJT
18th March 2011, 19:56
So how does an issue with "Win 7 DS Filter Tweaker" suddenly become my problem to fix?

Well, clearly Win7DSFilterTweaker does something, but it could have been something else, who knows.

When someone has a problem whereby BD-Rebuilder does not set the filters and ffdshow settings but says it did, then this is just 1 way in which this problem could be caused.

Forget Win7DSFilterTweaker was used. Fact is, BD-Rebuilder said it did something which it didn't. This is one way you can replicate the problem, that is all. Just one way. It could be something else for other people, but nevertheless this is one way for you to replicate the issue.

jdobbs
18th March 2011, 20:00
Well, clearly Win7DSFilterTweaker does something, but it could have been something else, who knows.

When someone has a problem whereby BD-Rebuilder does not set the filters and ffdshow settings but says it did, then this is just 1 way in which this problem could be caused.

Forget Win7DSFilterTweaker was used. Fact is, BD-Rebuilder said it did something which it didn't. This is one way you can replicate the problem, that is all. Just one way. It could be something else for other people, but nevertheless this is one way for you to replicate the issue. You have posted this now in two different threads and I have answered you in both. This is NOT AN ISSUE WITH BD REBUILDER and no matter how many times you cross-post it the bottom line is that even if I wanted to (which I don't) I cannot fix an issue in someone elses software. Send your bug report to them. :mad:

MickJT
18th March 2011, 20:05
You have posted this now in two different threads and I have answered you in both. This is NOT AN ISSUE WITH BD REBUILDER and no matter how many times you cross-post it the bottom line is that even if I wanted to (which I don't) I cannot fix an issue in someone elses software. Send your bug report to them. :mad:

Lets move this to the bug reporting thread. As said there, the issue is that BD-Rebuilder says it fixed something which it didn't. The cause that makes BD-Rebuilder do that, is irrelevant. Fact is, it is possible for something to make BD-Rebuilder exhibit this behaviour.

Like a buffer overflow which can be used to inject code on unsecure platforms. You don't say "I won't fix it, the solution is to not use that tool to overflow the buffer". Clearly there would be a bug that allows the buffer overflow to occur!

jdobbs
18th March 2011, 20:10
@MickJT

You have gotten your answer and now you're talking nonsense for which I have not time. Asking me to fix an issue caused by someone elses software is about as silly as it gets. If you can't understand that, then I have to assume you won't understand any further explanation either.

As moderator I am instructing you to cease posting on this subject. It is off topic. You have violated rules 3, 8, 10, and now rule 16. Continue and you will receive strikes and/or be banned.

Siddus
22nd June 2011, 07:44
I have tried 20 times now to install BD-Rebuilder on my windows 7 64 bit ultimate (with sp1) and I have followed all the suggested ways to install (uninstall everything, reboot and reinstall).
Run REG_MSCOMCTL.BAT as admin, and then run BD-Rebuilder.exe as admin which gives this at every startup:
"It appears your windows 7 system may not be configured for
use with FFDSHOW. BD-Rebuilder can attempt to configure your
system for you. This involves making changes to the DirectShow
REGISTRY. Failure to do so may result in ouf-of-sync audio
or encode failures

Would you like BD-Rebuilder to do this for you ?"
I always click ok..

And this is what the inspect.exe give as result:
- Windows Version: 6.1 [7601]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.11.96.14, Ok
- FFDSHOW: 3882, Ok
- WIN7 preferred AVC CODEC: Not Set correctly
- WIN7 preferred VC-1 CODEC: Not Set correctly
- WIN7 preferred MPEG2 CODEC: Not Set correctly
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libmpeg2": Ok
- FFDSHOW AVC set to "ffmpeg-mt": Ok
- BD Rebuilder v0.38.0.4, Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
The versions I am using is the latest recomended at http://forum.doom9.org/showthread.php?t=143716 (BD-Rebuilder BD-RBV03804)
and I have followed all the suggested settings on that page.
I have only a few burn software installed (dvdfab, alcohol-soft and nero) + media player classic HC and I don't understand why BD-Rebuilder
can't make the "WIN7 preferred CODEC" settings ??
I have also tried to login as administrator to remove the need for "right click and run as admin" and still no luck..
How can I make these settings manually (if there is a way)??
/Siddus

Capsbackup
22nd June 2011, 14:50
Have you tried jdobbs suggestion, found on page 2 of this thread, from post # 22 and continue reading?

Siddus
23rd June 2011, 08:54
I have tried all suggestions found here..
But the problem is solved now, I managed to save the FF_CONFIGURE.BAT before it disappeared and made these changes manually (the only way to get it to work), so now it's up and running..
/Siddus

SLOVEHEART
14th August 2011, 03:52
(deleted words)...I can't seem to get it to even start up, I get this error:
"Component MSCOMCTL.OCX or one of it's dependencies not correctly registered: a file is missing or invalid"
I try the fix - "Look in the BD-RB folder. There is a .BAT file called "REG_MSCOMCTL.BAT" -- simply right click onit and run it as administrator."
But then I get this - The Module MSCOMCTL.OCX failed to load... So this does not work for me...(deleted words)


What I have had to end up doing to avoid the lang.xml error or others, is to use the Windows Command Line Processor (old DOS window), and start this w/ right click - Run as Administrator - then navagate to BD Rebuilder's directory (useful trick - when changing directories - type first letter of wanted directory (on target drive) then use 'Tab' key- it will jump through all directories starting w/ that letter, one by one, until your desired one pops up - then continue) once inside BD Rebuilder - locate "REG_MSCOMCTL.BAT" (tab key works also for file names) - then simply run the batch file - no issues - for me at least...

Cheers...

monstirz
11th January 2012, 03:20
I clicked on BD-Rebuilder and then right clicked Administrator and I am still getting the mscomctl.ocx error. I offloaded the software to recycle bin and re installed BD-Rebuilder and the reg..,bat file was right clicked on first and ran as administrator and still got the same error message. I even have this as sucessfully loaded in in cmd under regserver32. Still the same error message..,Any cures for this in 32 bit Win 7? Desperate in Vegas.

jdobbs
11th January 2012, 14:22
Right click on "REG_MSCOMCTL.BAT" in the BD Rebuilder folder and "Run as Administrator". Normally MSCOMCTL is registered on Windows 7 as a part of the Win7 installation -- but on rare occasions it isn't there. I've never been able to figure out why.

cinephage
19th April 2012, 23:22
Right click on "REG_MSCOMCTL.BAT" in the BD Rebuilder folder and "Run as Administrator". Normally MSCOMCTL is registered on Windows 7 as a part of the Win7 installation -- but on rare occasions it isn't there. I've never been able to figure out why.

Didn't work for me: failed...

Capsbackup
20th April 2012, 01:47
Didn't work for me: failed...

You also need to right click on BDRB.exe and select "Run as Administrator". ( Just the 1st time ) :)
I would recommend placing the unzipped folder of BD-RB on the desktop or directly in C:, not in the Windows Program folder.

cinephage
20th April 2012, 08:55
You also need to right click on BDRB.exe and select "Run as Administrator". ( Just the 1st time ) :)
I would recommend placing the unzipped folder of BD-RB on the desktop or directly in C:, not in the Windows Program folder.

Thanks. It did work.

duftopia
6th April 2014, 21:26
OK. The culprit is Win 7 DS Filter Tweaker. After running that, it does something that I can't detect that prevents BD-Rebuilder from setting the registry keys. BD-Rebuilder doesn't even make FF_CONFIGURE.BAT (I wish it didn't delete it, so I could view what was in it).

Here is where it gets weird. Open up regedit, and double-click on {31435641-0000-0010-8000-00AA00389B71}

Change it (the value inside the key, not the key itself) to something else (regedit won't save non-edits).

After that, it's fine, BD-Rebuilder can do its thing. The weird thing is, no matter whether it's the AVC, VC-1 or MPEG-2 codec you changed in Win 7 DS Filter Tweaker, it is the {31435641-0000-0010-8000-00AA00389B71} key (AVC) that must be re-saved before BD-Rebuilder is able to fix the VC-1 / MPEG-2 keys and all the ffdshow settings.

At least you know what to look for now jdobbs! Run the tweaker program. It won't mess anything up, I promise (well, other than present this bug/issue to you).

Remember it's not only Win 7 DS Filter Tweaker that may do something like this that prevents BD-Rebuilder from fixing it. Seeing as regedit (or FF_RESET.BAT) works to fix it so BD-Rebuilder can fix the settings again, i'm a bit baffled. Is it a permissions issue or not? Hmm.

I have the same problem and bd-rebuilder cannot get around the vc-1 issue due to it, I can't seem to fix the registry, ffdshow changes the parms but it gets changed back and so I went with alternative methods to get the issue resolved.

YES win 7 64 bit issues is the problem, but it would be nice to get a simple fix for it

Duf

MrVideo
10th July 2018, 16:31
My curiosity has done me in!
I wanted to see if I could run Windows 7 on my I7 920 computer, and after running the Win 7 update advisor, it warned me there could be some conflicts. The challenge was on.
I decided to try the Ultimate edition RC, since it was free, and if I did not like it or it did not seem worth the upgrade price, it would expire soon enough and only a few hours would be waisted. ( waisted plenty in my time! ):)
Well, all installed fine, and after searching around for updated drivers for some hardware, all was a go.
Now trying BD-RB, all is not so well.:o
I can't seem to get it to even start up, I get this error:
"Component MSCOMCTL.OCX or one of it's dependencies not correctly registered: a file is missing or invalid"
I try the fix - "Look in the BD-RB folder. There is a .BAT file called "REG_MSCOMCTL.BAT" -- simply right click onit and run it as administrator."
But then I get this - The Module MSCOMCTL.OCX failed to load... So this does not work for me.
Can BD-RB run with Windows 7 RC?
How else can you get rid of this MSCOMCTL.OCX REG issue just to get BD-RB to start?
After reading back numerous pages, I can't seem to find out what to do next. Any help is sure appreciated.:confused:

EDIT:
OK, I got it to work by right clicking on BD_Rebuilder and selecting "Run as Administrator", which it then set up ffdshow for me, and now it starts up.
Off to try out a backup! :p
I had to reinstall M$ because I got in my new Gigabyte mobo Monday. I hate M$ security. I have to go find all the things I found before to stop M$ from this or that file change from happening.

In any event, right-clicking on "REG_MSCOMCTL.BAT" and running as administrator will always fail, because when run as administrator, the regsvr32 program is started from within the c:\Windows\system32 directory. MSCOMCTL.OCX is not in that location. If you right-click on "REG_MSCOMCTL.BAT" and click on OPEN instead, it will fail because you aren't admin. Which is fracking stupid because I am the only user on the system. Damn M$ permissions. We're M$ and we are trying to protect you. :mad:

So, I did the trick of right clicking on BD_Rebuilder and selecting "Run as Administrator." That worked. I think there should be text added to the readme for doing this trick in the installed location. Or, an improved BAT file that can get at the file in the OCX file in the installed location.

I do not remember having this bad of an issue the first time I installed it. Maybe I had frack'd with the permissions before installing BDRB.

Ch3vr0n
10th July 2018, 18:07
check the BOLD NOTE under item 9 in the setup instructions :p

Note to Windows 7, Windows 8, and Windows 10 Users: The first time (and only the first time) you run BD Rebuilder, you may have to "Run As Administrator". This is necessary so BD-RB can make CODEC preference changes in the Windows Registry.

No need to add when it's already there :p

MrVideo
11th July 2018, 02:33
Argh!!! And to think I read the readme before posting and still missed that paragraph. :o