Hi there, I hope I am posting to the coorect news group, if not please point me to the correct one. I installed Vista SP1 yesterday and MS SCRENC stopped working. It gives an error message and of course does not encode. We are encripting ASP pages written in VB script. Is there a solution to the problem. Regards, George
I ran into the same problem. I found that specifying the /xl or -xl switch made it work and encode. However, this leaves out the <%@ LANGUAGE = VBScript.Encode %> line from the top of the encoded file and therefore causes a compile time error when you run the file: Microsoft VBScript compilation error '800a0400' Expected statement main_nav.asp, line 2 #@~^7AEAAA==@#@&ZG ^ I'm still looking for a good solution. If you find one, please post back here. Thanks. "GVG" wrote: > Hi there, > > I hope I am posting to the coorect news group, if not please point me to the > correct one. I installed Vista SP1 yesterday and MS SCRENC stopped working. > It gives an error message and of course does not encode. We are encripting > ASP pages written in VB script. Is there a solution to the problem. > > Regards, > George >
I have found a work around for this problem. You can manually insert the <%@ LANGUAGE = VBScript.Encode %> line into the top of the encoded file, and it will work fine. So you can use the /xl switch, then copy the file with another file before it that just has the line in it: copy /b header.inc+myencodedfile.asp finalserverfile.asp You have to use the /b switch so that the EOF character is not inserted at the end of the output file. Another way to do it is to insert it in a text editor. However, some lines are very long and that approach won't work for them. Alternatively, you can write a program that inserts the line at the beginning and copies the file, as I did. This approach can allow for automatic handline of files that begin with <%@ ENABLESESSIONSTATE = True %> or other such @ Directives, since only one such line can exist in the output. The above example needs to be turned into: <%@ LANGUAGE = VBScript.Encode ENABLESESSIONSTATE = True %> So, even though the documentation says you can't change the file due to checksum calculations, it appears that you can change this top portion quite successfully.
