ISD 7.03 clash with VMware 3?
Posted 10 May 2002 - 17:50
Is this something to do with the new Product Activation? Is it somehow getting confused by the various networks that VMware creates?
Or is it my PC?
Does anyone have an identical or even similar configuration? Does it work okay for you?
I can't believe I'm the only person who uses VMware for testing installers.
Posted 13 May 2002 - 12:01
Geez, when InstallShield introduce a bug (pretty much every version), they really don't like to make it a small one, do they?
I'm inclined to agree that it is ISD and instinctively I'm sure it's related to activation (it's a huge change to the software that will be triggered every time you open ISD).
Now... if only I could figure out how to report a bug to IS without having to convince my boss that a support package is required (after learning from past experience that it's not all the helpful, considering the cost -- at least the first three mails consisted of me rephrasing the problem and the support department picking out key words and pointing me to barely related KB articles).
Damn, damn, damn!
Posted 13 May 2002 - 12:13
Posted 14 May 2002 - 09:01
Maybe the same workaround will solve your VMWare problem.
Posted 14 May 2002 - 12:05
Posted 14 May 2002 - 13:29
Turned out that only needed a new cable; I happened to see one lying around and thought I'd try it. The floppy now works even with the conflicting IRQs (I hoped as much, this is a new Gigabyte motherboard and I'm assured it pretty damned good).
However, the ISD/VMware clash is still present.
Posted 14 May 2002 - 19:01
Posted 15 May 2002 - 00:48
Failing that, may I contact you offline for the details?
Posted 15 May 2002 - 17:58
Posted 21 May 2002 - 16:22
1) Install to VM Ware image
2) Leave VM Ware image up and running
3) Try to rebuild the same installer on the host machine
I can avoid this if after installing to the VM Ware image, I select a file in a different directory than the installer source (on the VM Ware image). This would seem to mean that the VM Ware image's knowledge of the current directory causes the problem if you attempt to delete the directory from the host machine.
Thats my current level of investigation because I can work around it with that.