Search results for query: *

The support team in our company uses a Windows 2003 R2 Terminal Server hosted on a VMWare ESX 3.5 virtual machine, using 8 virtual modems from a Digi PortServerII (phew!) ProComm just won't die. I'd like it to, but it just won't :)

As the title suggests, I'm wondering if it's possible to set per category viewing permissions. I want to have my team start using the blog to communicate ideas and concepts and such but would also like for them to be able to allow certain ideas or annoncements to become public. So I've...

Well, I thought so as well but any other process works just fine. I'm going to code a little .net exe that looks for another instance of itself and shuts down if it finds one, like the Procomm .exe does, to see if the behaviour that I'm seeing is caused by some "inter-context-bleeding" so to...

Either. I can try to launch just pw5.exe or pw5.exe scriptname.was and the result is the same.

The only way I can tell that it actually starts is that it shows up for roughly 10 seconds in the process mananger. It then vanishes and I don't see a single thing on the screen. As far as things changing goes, I can't think of anything that's relevant. Of course, patches are applied as they...

Yes, I can launch Procomm from my user or the service account's user while over TS. I have tried renaming the prm and dir files also to no avail. And I'm using 4.8. It seems to me that there's something in the console's environment that it doesn't like. The only thing that I can think of that...

When I'm connected to the console, my user is used to start the application. I'm an administrator of this server and have effective rights everywhere. When I run the scheduled tasks, I use a production service account, which is also an administrator of the server and thus also has sufficient...

Hi, This isn't really an Aspect question but here goes. I run Procomm on a Windows 2000 server in terminal server mode. Clients connecting to the server can, without issue, start Procomm and work happily with all the scripts and such. When I try to launch Procomm on the console, however, the...

You know what? As I pasted it I realized what you asked for in the first place, which was to comment everything BUT the fgets and the yield commands. I did that and found that the for loop is execute way too many times when it doesn't have to. I added an extra check to prevent the script from...

Here you go. It'll a little all over the place as it still needs some polishing. while not feof 443 fgets 443 LineBuffer substr ReportDate LineBuffer 18 5 substr ReportName LineBuffer 27 6 ReportFileName = LineBuffer if strfind...

Just tried that. Commenting out the fgets doesn't change anything. I still hit 100% as soon as I get in the while feof loop. I'm thinking I might have to write a dll to handle the file processing. I've never done that before but I'll look it up on your site and see what I can come up with.

Hi there, Currently writing a script that, at some point, needs to read through a file which will have more than 50000 lines and sometimes 200K or more. I'm doing so with a while not feof, and then some fgets'. If I don't put a yield in the while loop, pw5.exe takes up 100% cpu usage. If I do...

I noticed this in the Aspect help about my 1) issue. " Procomm Plus makes available two DDE topics when acting as a server: "System" and the name of a script file with a .wax extension. If a valid script name is supplied, the script will run when the DDE session is established...

Hi Knob, Me again. :) My script is coming along nicely and there's only things that bug me. 1) Seems that when if I do a DDEInit from my "slave" script to my "master" script and the "master" was already running before, the DDEInit fails. So I need the slave the...

w00t! I got things by changing the topic in my DDE init to the name of the parent script ("test.wax" in my test case) and changing to a predefined global string variable ("s0") as the variable that is transmitted back and forth. I also had to change my ChangeSite procedure...

I wrote two little test scripts this morning. The server or parent script is this: ================================================= string NextSite string Sites[5] integer SiteNumber=0 proc main integer MainPWWin = $PWMAINWIN string LineBuffer Sites[0] = "Site0&quot...

Here's thought. Tell me what you think... I read your technical bulletin about DDE and noticed that only 2 sessions could be used at once. If that means that a single PW5 session can only be a DDE client twice, maybe I could set the CHILD script to be the DDE client and do dderequest command to...

Oh right. I kept talking about connection entries as if I was using the connection directory, but I'm not. I need more information per connection than what the directory can hold, so it's all in a seperate text file. It really would have to be a string variable.

Alright. If all works well, that takes care of the 2nd question. Thanks. I still don't see how I can tell the "child" Procomm which connection entry to use for the child script.... Unless I missed something??

Hi there (Knob), I currently have a script running every night that connects to roughly 450 telnet or dial up sites, downloads X amount of reports and moves on to the next one. It works to my liking but it takes WAY too long to run. What I was thinking of doing is a main script that...