I used to run /start scripts between processes to get the pipes to wake up as I started my app. Today I found out I was being very silly switching from local to global, I don’t even know how it worked…
so now I’m not running any “wake up” scripts and I’m back where I have been for the past year or so. I start the app, and I have some pipes not working. Sometimes it’s enough to get out of Perform mode (even if I don’t see them in the editor) to get them to wake up, sometimes I need to navigate to the network, sometimes I need to delete and re-create the pipe.
Working with pipes has been one of the most frustrating experiences of working with Touch (and I’m not the only one).
Obviously, it must be really trick otherwise Derivative would have fixed it. But I’m wondering, do we know what causes pipe death?
When you shut down Touch, how do you do it? I’ve found that if you shut down Touch by closing the Black console windows, or using the Close Window Group (or whatever its called) feature in the windows task bar at the bottom then windows closes touch without letting it clean up the pipes. Then when you try to restart some of the ports are still in a SYNC_WAIT state (according to windows) and can’t be re-opened yet.
When we started closing Touch using the X in the actual Touch window, we stopped having any issues with pipes starting up correctly. Touch shuts down slower, but thats because it’s cleaning stuff up.
We’ve never had to massage the pipes to get them going since we started doing this.
By Restart I mean computer restart. Is it possible that something’s still hanging after that?
True, often when Touch crashes the pipes tend to be have a higher chance of coming back up broken, but after a Windows restart?
Anyway unless it crashes, I close touch using the X.
I’m curious to know whether or not the file I sent you yesterday is coming up ok or not… there was a pipe that was broken after a windows restart I believe, that is why I sent it.
Hey Dani,
The file seems to start up fine for me. Everything seems to work.
I wonder if you have an app running on your computer that is sometimes grabbing one of the ports you are trying to use? Next time it happens try using an app called ActivePorts (freeware) that will show you what running processes are using which TCP/IP ports.