dtieuf
11-02-2004, 01:37 PM
Some of our users have been getting the "Internal error V1" message. All of them were using a double-byte version of Windows (Chinese, Korean...). The workaround discussed in this forum worked fine.
But today I got this message at the office on an English win2kServer PC that apparently never had the VBuild engine installed. We were trying to install it to a custom path, on the D: drive.
Then we tried with the default C:\Program Files\<Our software>: we didn't get the message and the software got installed correctly.
Does this mean that VBuild does not support custom paths ???
Thank you
But today I got this message at the office on an English win2kServer PC that apparently never had the VBuild engine installed. We were trying to install it to a custom path, on the D: drive.
Then we tried with the default C:\Program Files\<Our software>: we didn't get the message and the software got installed correctly.
Does this mean that VBuild does not support custom paths ???
Thank you