Installshield Havoc

[nboy22]

I have been having trouble with installshield, i have my 120 gig hd formatted in ntfs and partitioned into two 60 gb drives, and i have my 80 gig as slave drive. A while back before i reformatted my 80 gig that was back then at master, i had no problem with installshield, now i have the 80 gig reformatted and set as slave obviously, and one of the 60 gb partitions has windows xp pro on it. Now the problem is, that installshield will hang at 99%, then dissapear, and then come back when it feels like it.. i have had this problem for 3 installations now, and i had none in between them so this problem has a 100% reputation of showing up.. i have heard of other people having this problem but i have searched and not found a thing on how to fix it, anyone else have this problem? and possibly know why its happening?

 

[calpha]

Your problem could be more of a windows installer issue----although Installshield != Windows Installer----but in most likelihood, it's a MSI package.

When you install windows installer files----one of the things it does is extract the contents of the msi to a temp folder, and execute it from there. There's not enough information to troubleshoot your particular setup----besides, debugging hung windows installers is a PITA by itself-----but one of the things you cna do if you're getting errors/hung installs is to do an admin or network install of the .msi file in question---which extracts the compressed MSI to a folder you specify----and after that's done, you can run the installation from non-compressed files, directly from your hard disk. just do a google search for msiexec + admin install or msiexec command line switches, and you should be able to find the info you need.

Again....the above is all guess work----but nowadays, most all installshield packages are windows installer based for products that I use----so the assumption may not be too far off. I've had to do that before.......but it was mostly because my machine needed a reinstall b/c my user's temp folder (the default path used for decompression on a standard msi file) was corrupted.