hoster 4.08 error 1706 plus won't read CD

[bendrew]

This is my situation :
I installed hoster v4.08 (upgraded v.4.03) and almost at the end of the installation, this code 1706 showed up and installation didn't go thru. I reboot and start Hoster and Dr. Watson (crash) won't start the program. So, i installed back v4.03 and works again ( no error code). I tried to re-installed back 4.08 and give me the same result and now I.m stuck with v4.03. Now I tried at my show computer with v4.06, installed v4.08 and gives me the same result so, I got stuck with v4.06, too. Not too worried about the situation but if somebody is saying that this is a windows problem, why is it that it only happen with Hoster. Somebody at MTU should should give us a solutions for this. I'm not new with computer so I'm gonna research this problem..Just remember, this code just pop up recently and hoster is both working on my 2 computer but with the old version. And guys, I did what you have recommended but to no avail, no good result. So, My frustration is building up right now...................

[marklwood]

Bendrew, on the 1706 error. I have been doing a little testing and have a theory. Try moving the Hostersetup.exe to C:\. See if you still get the error. The other possibility is a registry modification which I don't want to reccomend until I am ABSOLUTELY sure it will work.

[ddouglass]

Originally Posted by bendrew

This is my situation :
I installed hoster v4.08 (upgraded v.4.03) and almost at the end of the installation, this code 1706 showed up and installation didn't go thru. I reboot and start Hoster and Dr. Watson (crash) won't start the program. So, i installed back v4.03 and works again ( no error code). I tried to re-installed back 4.08 and give me the same result and now I.m stuck with v4.03. Now I tried at my show computer with v4.06, installed v4.08 and gives me the same result so, I got stuck with v4.06, too. Not too worried about the situation but if somebody is saying that this is a windows problem, why is it that it only happen with Hoster. Somebody at MTU should should give us a solutions for this. I'm not new with computer so I'm gonna research this problem..Just remember, this code just pop up recently and hoster is both working on my 2 computer but with the old version. And guys, I did what you have recommended but to no avail, no good result. So, My frustration is building up right now...................

This error is a Microsoft Installer (which MTU uses to create the setup files for their programs) error and it happens with their own program installs. It is not a constant error though. I get it on all 3 of my computers but only if I do the upgrade. If I remove and install it won't do it. However it is not a fatal error and does not normally keep you from opening the program. If MTU had a solution then they would certainly pass it on. This is not just a recent error it has been around for a while now but not everyone is getting it, so if you are just now getting it then you have been lucky.
What is the error message you get from Dr Watson when you try to open the program? That will help track down the cause for it not opening.

[rmryanjr]

Originally Posted by ddouglass

What is the error message you get from Dr Watson when you try to open the program? That will help track down the cause for it not opening.

It opens fine....the problem was that it didn't like the drive I had been using for some time now...anyway, I tried a suggestion to open in 3.4 and detect the drive then open 4.08. This worked and the drive is saved as a show drive.

So, one problem down

Thanks to all for your help

Bob

[ddouglass]

Originally Posted by rmryanjr

It opens fine....the problem was that it didn't like the drive I had been using for some time now...anyway, I tried a suggestion to open in 3.4 and detect the drive then open 4.08. This worked and the drive is saved as a show drive.

So, one problem down

Thanks to all for your help

Bob

All I was trying to say about the error is it is a nusance but harmful.
Glad you got your drive back Bob. I only had that happen to me one time a while back (early version 4 beta) and 3.4 fixed mine too.