This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Win2k Prof SP4. Installer hangs at 9% complete.
Is it reproducible? If yes run installer from console and use command line option -is:log <Log file> and attach log here.
Created attachment 26501 [details] Install log file
Yes, the issue is reproducable. I have attached a log file, but it may not be completed as the install process had to be killed instead of terminating normally.
Install log does not contain any error. You can run installer with command line option -is:extract. It will extract setup.jar. Then run command java -Dtemp.dir="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp" -jar setup.jar from console. Of course you can set othet dir for temp.dir. If it hangs you can get thread dump using Ctrl-Pause from console. Please attach thread dump here as attachment. During run you can get also more detailed log in console from installer. You can attach it here too. As workaround you can use zip distribution to get working IDE.
Please also check MD5 checksum with value given at download page to make sure your installer is not corrupted. For beta Win installer size is 59554272 and MD5 checksum is cf9a5dda291ada975bec0a4df4fdfbba netbeans-5_0-daily-beta-bin-200509261930-windows-26_Sep_2005_1930.exe If you use some daily or Q-build let me know exact build number so I can give md5sum here.
Created attachment 26781 [details] Thread Dump (As Requested)
There is no deadlock. It hangs in native method (creating desktop icon for NB): "Thread-24" prio=5 tid=0x18305428 nid=0xc58 runnable [389f000..389fd88] at com.installshield.wizard.platform.win32.Win32DesktopServiceImpl.createDesktopItem(Native Method) It is InstallShield code. I am sorry I have no idea why it happens. I did not see such problem so far. Please use zip distribution as workaround.
Does it still happen with latest installer? We did not change anything in this area. If there will be more reports the only thing we can do is to report this problem to InstallShield. Closing for now.