Repair option crashes IDRIVER.EXE

[NewsArchive]

Hello. When I choose "Repair" from the maintnance dialog it crashes
"IDRIVER.EXE" on Windows 98 and it does not do anything on Windows 2000 and
XP (just closes the InstallShield Wizard without any error message). I know
it was working before but one day it started crashing. I don't know what I
did. The only big change I remember I did is to change the "Product Code"
and "Package Code" in all my product configurations because I want different
versions of the same product and I don't want the maintnance dialog to pop
for products that are not the same!

Did a bug report because this is A BUG but did not get any reply from
InstallShield Corp. I don't want to restart from scratch.

Anyone has an idea?

Sebastien

[NewsArchive]

I am not supposed to answer this anymore. In the future you should use our
community instead (http://community.installshield.com)

It is one of our bugs. I guess what happens is that your have a wrong
requirement relationship and we failed to detect that.

At least one of you feature lists its parents (Or grandparents), as
"Required". This will cause an infinite loop
(Feature->Required->Children->itself->.....) during our state flagging. By
default, parents are forced to be required if the sub feature is selected so
you don't need to do that.

Fei

"Sebastien Clermont" <clers00@dmi.usherb.ca> wrote in message
news:3c14d5a4$1@news.installshield.com...
> Hello. When I choose "Repair" from the maintnance dialog it crashes
> "IDRIVER.EXE" on Windows 98 and it does not do anything on Windows 2000
and
> XP (just closes the InstallShield Wizard without any error message). I
know
> it was working before but one day it started crashing. I don't know what
I
> did. The only big change I remember I did is to change the "Product Code"
> and "Package Code" in all my product configurations because I want
different
> versions of the same product and I don't want the maintnance dialog to pop
> for products that are not the same!
>
> Did a bug report because this is A BUG but did not get any reply from
> InstallShield Corp. I don't want to restart from scratch.
>
> Anyone has an idea?
>
> Sebastien
>
>

[NewsArchive]

Thank you very much! It worked!

But I have one last question. What is the difference between the newsgroup
and the community? I went to the newsgroup and people are asking questions
so I asked my question here!

Sebastien


"mingbiaofei" <mf@installshield.com> wrote in message
news:3c14f399$1@news.installshield.com...
> I am not supposed to answer this anymore. In the future you should use our
> community instead (http://community.installshield.com)
>
> It is one of our bugs. I guess what happens is that your have a wrong
> requirement relationship and we failed to detect that.
>
> At least one of you feature lists its parents (Or grandparents), as
> "Required". This will cause an infinite loop
> (Feature->Required->Children->itself->.....) during our state flagging.
By
> default, parents are forced to be required if the sub feature is selected
so
> you don't need to do that.
>
> Fei
>

[NewsArchive]

I am also very confused. :)

The Community is something we just established. It is much powerful than
this simple newsgroup. Since it is hard for us to monitor both of them so we
encourage people to use community.

Fei

"Sebastien Clermont" <clers00@dmi.usherb.ca> wrote in message
news:3c161f04$1@news.installshield.com...
> Thank you very much! It worked!
>
> But I have one last question. What is the difference between the
newsgroup
> and the community? I went to the newsgroup and people are asking
questions
> so I asked my question here!
>
> Sebastien
>
>
> "mingbiaofei" <mf@installshield.com> wrote in message
> news:3c14f399$1@news.installshield.com...
> > I am not supposed to answer this anymore. In the future you should use
our
> > community instead (http://community.installshield.com)
> >
> > It is one of our bugs. I guess what happens is that your have a wrong
> > requirement relationship and we failed to detect that.
> >
> > At least one of you feature lists its parents (Or grandparents), as
> > "Required". This will cause an infinite loop
> > (Feature->Required->Children->itself->.....) during our state flagging.
> By
> > default, parents are forced to be required if the sub feature is
selected
> so
> > you don't need to do that.
> >
> > Fei
> >
>
>
>