Has my copy of Vista Ultimate been cortupted

[Guest]

Can anyone help please?
I bought a new computer which arrived complete with Vista Home Premium, most
of my applications worked perfectly as they had using XP. Two I had to
struggle with but got there in the end, these two were BookLibrary from
WenSoftware and WinBMD which I use with my genealogical hobby.
Then I upgraded to Vista Ultimate and since then neither BookLibrary nor
WinBMD will work. I have tried reinstalling both, using the Compatibility
Wizard, trying to use a shadow copy and every other I possible solution I
could discover. WenSoftware sent me a disc with the software on as it would
not work from the download and that did not work either.
I am getting two different error messages with BookLibrary it says: â€339 –
Component “COMCT332.OCX†or one of it’s dependencies not correctly
registered: a file is missing or invalidâ€
With WinBMD, the message says; â€Run-time error “429†ActiveX component can’t
create objectâ€
As no cure seems to work is it possible that Vista Ultimate itself has
become corrupted?

 

[John Barnett MVP]

There are quite a few applications out there that currently wil not run on
Vista, even in compatibility mode. I'm not familiar with the applications
you are using, but it may be the case that these two applications are not
compatible with Vista and are awaiting an upgrade from the software
developers - or even a new version. I know many of my applications don't
work with vista (well not very well, anyway) but i dual boot with XP and
Vista, so all those programs that are a bit 'dodgy' with Vista are installed
on the XP partition and if i need to use them, which is only occasionally
now, i boot to XP instaed of Vista.

--
John Barnett MVP
Associate Expert
Windows - Shell/User

Web: http://xphelpandsupport.mvps.org
Web: http://vistasupport.mvps.org

The information in this mail/post is supplied "as is". No warranty of any
kind, either expressed or implied, is made in relation to the accuracy,
reliability or content of this mail/post. The Author shall not be liable for
any direct, indirect, incidental or consequential damages arising out of the
use of, or inability to use, information or opinions expressed in this
mail/post..

 

[Mark]

So, the MVPs suggestion is to keep XP ready in waiting for anything that
won't run on Vista.
---
Try installing the programs by running the setup.exe as administrator (Run
as Administrator) to see if the ActiveX or OCX file will register correctly.
Vista has a problem with running child operations from within Setup programs
that result in setting improper permissions on some files, especially
ActiveX or .OCX files that are installed directly through download with IE7.
(Research Flash Player problems.)

If this fails to correct the problem, you may be able to directly correct
the File Permissions by going to the file properties and setting Everyone
and Current User to Full Control.

Worst case, which works, but it's a PITA...
Install the programs as stated, Run as Administrator, then re-install
Vista. Another Vista glitch... It may set the permissions improperly during
installation of the files, but they are installed. When you re-install
Vista, any files in System32 folder will be registered and the permissions
are set to defaults which corrects the problem.

Now for the disclaimer...
The program may be incompatible, but I find this unlikely since you had them
running on Home Premium.

 

[John Barnett MVP]

No Mark the MVPs suggestion is 'not' to keep XP ready in waiting. I simply
pointed out that I dual boot with XP and Vista and that any programs that
were a bit 'dodgy' in Vista were left on the XP partition and I used them
from XP. I should point out that I am not only an MVP but also a Beta tester
and, as such, am also running other Microsoft beta operating systems. As
loads of software also doesn't work on these future systems, then it is of
paramount importance that i have an operating system available that will run
the software.

While running the software 'as administrator' works in some cases, it
doesn't work with all, neither does compatibility mode.

--
John Barnett MVP
Associate Expert
Windows - Shell/User

Web: http://xphelpandsupport.mvps.org
Web: http://vistasupport.mvps.org

The information in this mail/post is supplied "as is". No warranty of any
kind, either expressed or implied, is made in relation to the accuracy,
reliability or content of this mail/post. The Author shall not be liable for
any direct, indirect, incidental or consequential damages arising out of the
use of, or inability to use, information or opinions expressed in this
mail/post..

 

[Guest]

Botrh are alleged to work with Vista by the authors. But if you are right
why did they work under VIsta Hone Premium and will not under Vista Ultimate?

 

[Kue2]

If you have DEP enabled for all programs,put both the exe files in the
exclude list for DEP.

 

[Mark]

Dear John (MVP),

Thank you for providing hours of work as a beta tester for future
products, but the problem statement of this request was not in reference to
a beta product. The problem statement referred to a product that has been
released to the public as a final product: Vista.
Your answer in a condensed statement was:
Some programs don't run on Vista. Those that do not, I manage to
run on my XP partition.

If this is your attempt to help the individual with their problem, then
the paragraph becomes:
Keep XP installed as a backup for anything that doesn't work on
Vista.

If you were simply stating how you manage to conduct beta testing on your
machine, then I fail to understand how you were answering the problem.

Regarding your post, I find the exact opposite to be true with Vista...
almost everything will run if you can just get past some of the bugs in this
"final product." Yes, bugs. Identified by consumers and reported to MS and
other vendors so that workarounds can be performed. Had you performed even a
minor search on this newsgroup for ActiveX file problems (such as Flash
Player) or researched some of the active forums (Adobe) that do not spend
all their time condemning Vista, you would have been able to provide a
comprehensive answer to the question.

The title MVP comes with a responsibility. I do not bear that title, nor
do I claim any expertise beyond having experienced the problem being
addressed. To that, there is an answer and I attempted to provide it. If
there wasn't enough detail, then a repost for clarification would have been
provided.

It's confusing enough trying to wade through the garbage on these
newsgroups to find an answer when you can barely get past the UAC prompting
at every mouse-click. So when an MVP speaks, we try to acknowledge the
expertise behind the information provided. You failed in this case and then
took the place of the common troll in your follow-on reply.

Good day.

 

[Guest]

Hi John,

I had a customer who was having the same type of errors in Vista Home.
Installshield should have registered the OCXs as it had done in all previous
version of Windows up to XP/2003.

I searched the web and foun this Intuit TurboTax support forum that had the
solution. Strange as the solution was, it works. The solution is to
UNREGISTER the OCXs which incidentally the problem ones are from Microsoft. I
suspect a Vista bug simewhere.

You can take a look at this forum link. the solution is found on page 4:

http://forums.turbotax.com/intuit/b...message.id=1307&view=by_date_ascending&page=1

Hope this help.

Regards
Cho