Yes but I need to be able to develop this application first on my PC. The ActiveX EXE app is huge and will require a great deal of testing and debugging so I must be able to get this working. PWS is IIS 4 isn't it, I can't see any reason why this will not function correctly, thats the whole idea...
Well no go on your suggestion, and I've tried about every path that I can think of.
Does anyone else have any idea about this
I can't be the only one trying to do this, or should the example above work and there is something wrong with my system.
Thanks for any help.
I could look at it all day and not notice the problem:)
I'm new to this ASP stuff, so I'm just fumbling my way through. I think if I can get past this problem I'll be OK the rest of the way.
I'll give what you said a try,
Thanks
I am trying to use an ActiveX exe with an ASP, and I am testing on a WIN98 running PWS. I understand what this problem is and that I need to make a change in the metabase to allow this to work but all the examples around the net do not work for me. I'm assuming the examples are based on a NT...
Heres the deal, I wrote a windows application/GUI that talks to a peice of equipment via a telnet connection(Winsock component), using VB6.
I would now like to migrate this over to a web based interface but if at all possible use most of the VB coding that I have already done, is this...
I posted below about trying to get one script to talk to multiple procomm sessions, and I see others are interested in this as well. Anyway, I have been all over trying to get help with no luck. Looks Like symantic wants you to have the newest version or you have to pay for help. This is a load...
I have put a little thought into this as well:) Using "timeval" could do this job, just have the script compare this regester with your expire value and have it not execute if its greater. I think they might be able to get around this by playing with the computer clock. So you could...
For an interrupt type setup in aspect you might be able to use a "when target" command, this will call a procedure when a predetermined character(s) are received without having to continually poll the com port. This might work better for grabbing error codes. Aspect strings as far as I...
I have worked a little with this and the rget command works well, its quite flexible. If your looking specifically to capture something from the com port and its preceded by a static key word you can use a "waitfor" command followed by the "rget", you can set the rget to only...
I am trying to have the script initially activate and connect to 2 or more devices via telnet and then have one running script send commands to any one of the sessions depending on whats required.
It starts the new procomm windows OK but always sends commands to the main procomm window(the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.