HalVisionX Beta

snowman · May 27, 2009, 04:03:21 PM

That's one of the things we are trying to assess. Most have had success, and like you said before Vista already has SDK installed on it (i think). If this solves the problem then perhaps it will narrow our search down a little more.

Data · May 27, 2009, 04:05:57 PM

Snowman that link takes me to a page with six things to download, which one do i need ?

snowman · May 27, 2009, 04:10:37 PM

Visual Basic 2008 Express Edition

Data · May 27, 2009, 05:07:06 PM

It's not good news, halvision is still not working, gives me the same error as before, after installing Visual Basic 2008 Express Edition I do have the folder C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages

jasondude7116 · May 27, 2009, 05:19:39 PM

i don't know if this is of any consequence:
(xp only) many people have had problems with the install of net 3.5, because their registry was improperly (manually) altered from the previous net framework edition. i personally had to uninstall all net framework packages back to 1.1, and then reinstall all of them starting with the 2.0 package and then the 3.5 and so on...blah blah..

note: i had never manually altered the registry, but i used a tool to remove some "left over" install data. this is where my problem came from. also, the 3.5 package (before i uninstalled anything)initially installed properly (or so it looked) but it didn't install the full package.
going back to 1.1 , then reinstalling all remaining net framework has solved many problems related to the 3.5 install.
believe me...there are a lot of problems related to that install!

-the dude

snowman · May 27, 2009, 05:53:45 PM

Datahopa,

Did you find the "DotNetFX35SP1" filefolder in that directory location.

C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35SP1\

Data · May 27, 2009, 06:26:39 PM

Affirmative, DotNetFX35SP1 is there.

One · May 27, 2009, 10:19:40 PM

quote:
Originally posted by snowman

ONE said (or implied) in another post:

quote:
De Bugging services are not usually available on proprietary programs that is why the De Bugger wouldn't work ( else reverse engineering capability would show)

And HalVision certainly isn't proprietary.

AAWWW NOW, common Snowman this aint politics, no need to take me outta context.
You know I was referring to other "EXE" errors and nocho Proggie! I didn't see any help coming and I was givin' thought and a little effort.

Chill dude, um sorry ,SNOWMAN!

snowman · May 28, 2009, 12:14:21 AM

I thought it was informative, not offensive.

It's sort of difficult to get me any more offended than I already am normally [:D]

Although I appreciate the misplaced apology.

Made me feel all warm and cozy inside.[:p]

snowman · May 28, 2009, 12:40:03 AM

Well rlederer, I guess its not that file...Maybe. The Dude's theory could be at play here. Either way this is not my forte and I feel stupid.

We might need to know the cause of this for long term reasons. After all, if any A.I. is produced or any subsequent program is made. Then it would be nice to have it running (at least) on the majority of Windows machines.

Whether you want to hear this or not, you definitely have superior troubleshooting skills. Probably from much, much experience too.

Art · May 28, 2009, 12:55:06 AM

Datahopa,

If you're running VISTA do you have all the authorization settings
/ properties made correctly? Admin settings....?

Have you tried to install and run say, Visual Studio (which uses .NET) without error?

Have you received any other errors with programs other than Hal?

Have you disabled any AV programs you might have running while performing the upgrade?

During the removal, download and reinstall, did you perform a registry cleaning?

Yea...I know....picky...picky...but if it might help who knows.

One · May 28, 2009, 01:51:39 AM

quote:
Originally posted by snowman

I thought it was informative, not offensive.

It's sort of difficult to get me any more offended than I already am normally [:D]

Although I appreciate the misplaced apology.

Made me feel all warm and cozy inside.[:p]

All warm and cozy[:p][^][:p]

jasondude7116 · May 28, 2009, 01:55:58 AM

it is this "registry cleaning" that is causing a mass of problems with the 3.5 install. the same type of thing happened when net 2.0 was released. figured microsoft would have fixed that by now?

One · May 28, 2009, 03:14:07 AM

Jason DuDe~
I installed the 3.5 sp1 in about every variation including cleaning the registry or not with 100% success with a single exception,,

The Assistant will not let you install it.

More than 10 different machines were used in their various states of dis-repair, even my perfect running machines [:D]

Art · May 28, 2009, 06:32:24 AM

jasondude,

The exact same thing holds true in my case and One is right on...it IS the assistant that prevents the install from happening.

Try to install VB Studio without removing Hal.

This is something that Microsoft should have caught before hand not us.

Any decent registry cleaner will sort and remove old / improper entries...not the valid ones, else they would have a product to sell for very long.

Then again, I know people who will reformat their hard drive every month in order to "refresh" it!

Go figure!