|
|
#11 |
|
Junior Member
Join Date: Nov 2006
Posts: 12
|
Thanks for the details, guys. I agree the issue is people with paths to the installer like C:\Documents and Settings\<username-with-extended-chars>\Desktop. I presume this means I'm not doing anything wrong with my plain-old-NSIS installer?
I wish there was a workaround for plain-NSIS because we've got it installed on a plethora of developer and build machines. Could it be because we're using CRC check? Can you guys think of a workaround other than switching to NSIS Unicode? James (I attached our installer script below in case you're curious.) |
|
|
|
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|