News: 11 March 2016 - Forum Rules

Author Topic: Sappy refuses to work on Windows 10 (vbalCbEx6.ocx)  (Read 12537 times)

Midna

  • Hero Member
  • *****
  • Posts: 710
  • Resident Panel de Pon Nut
    • View Profile
Re: Sappy refuses to work on Windows 10 (vbalCbEx6.ocx)
« Reply #20 on: January 12, 2017, 09:11:29 pm »
Would like to make a small correction. It was Dependency Walker that froze, not Process Monitor.

I ran Sappy through Process Monitor and I got a few "file locked with only reader" results for vbalCbEx6.ocx. Why? It's not marked as read-only at all.

Jorpho

  • Hero Member
  • *****
  • Posts: 5057
  • The cat screams with the voice of a man.
    • View Profile
Re: Sappy refuses to work on Windows 10 (vbalCbEx6.ocx)
« Reply #21 on: January 12, 2017, 10:22:55 pm »
I don't know exactly what that means either, but I get the same message here, so I suppose it's nothing to be concerned about.


Does that look similar to what you're seeing?

January 14, 2017, 02:14:23 am - (Auto Merged - Double Posts are not allowed before 7 days.)
So, oddly enough, I just ran into a very similar problem with AVS2DVD, which was oddly insistent about finding mscomctl.ocx despite it being properly located and registered.

After much gnashing of teeth I applied the instructions found here: I moved mscomctl.ocx out of C:\Windows\SysWOW64, uninstalled AVS2DVD, and then re-installed it.  That's all it took.

Perhaps you should try something similar with vbalcbex6.ocx ?
« Last Edit: January 14, 2017, 02:14:23 am by Jorpho »
This signature is an illusion and is a trap devised by Satan. Go ahead dauntlessly! Make rapid progres!