I've been using Script Editor for approx 5 years. Yesterday I tried to add the simple step to an existing project I ran "%COMSPEC% /c wmic /output:C:\Mfctr.ini computersystem get manufacturer" then tried to "Read lines of the file "x" into a variable". When it got to that section in the code the program started using memory at a rate of about 200 mb a second until the program crashed with a memory error.

Here's why I'm asking for help.
  • I've used the same feature hundreds of times before - no problems
  • I've used the same feature in the same script already - no problems
  • I've reimaged the system to exclude any recent M$ patches - memory spikes/app crashes
  • I've repaired Wise - memory spikes/app crashes
  • I've reinstalled Wise (5.6 patched and 7)- memory spikes/app crashes
  • I've installed Wise on another computer - memory spikes/app crashes
  • I've changed the text file so it's only 1 kb - memory spikes/app crashes
  • I've run the tool on XP, W2K Pro, and Server 2003 - memory spikes/app crashes
  • I created a new program on a different computer with a fresh install of Wise - the only code was to read the contents of a 1 kb text file - memory spikes/app crashes

Has anyone else experienced this? Please tell me it's not a pebkac situation [:(]

Thanks in advance for any suggestions

0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


You mean wise script editor? I've not used it for reading text files much, as I find vbscript to be more flexible. If Wise can't help you with it or reproduce it, you may consider another tool to do the job.
Or...(just a wild guess) did your text file change from ascii to unicode or vice versa? Maybe Wise script has trouble with one or the other? Good luck!
Answered 04/22/2009 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity