Tilted Forum Project Discussion Community - View Single Post

yatzr · 05-20-2004, 09:13 AM

hrdwareguy, although that's a good idea, I don't know how to make the program close itself when it calls the batch file other than taskkill (I didn't write program A or anything and although it is open source, I don't have the skills to try and change it). Also, a pause does make it work, but I really don't want to have to hit a button each time I do it.

Another problem though, everytime program A calls the batch file or program B, it becomes "not responding", until program B is closed. So, the only way to close it is to force it (/f) and I think that causes a memory leak. So i don't know if I even want to go that route anymore.

I think all it really needs is a bit of a delay. I think program B get's loaded up too fast and doesn't give program A time to minimize or something like that (I don't really know if that is even a plausible cause). So how could i get it to delay? I think I'm going to just have it change directories a bunch before it calls program B and see if that works.

edit: okay. so the delay didn't work, it just took longer to load. The same problem still exists in that the two programs don't like each other. I've somewhat narrowed down when this happens though. Program A is just a frontend for emulators that I have startup when the computer starts up. The first time it starts up, it almost always screws up loading the certain emulator. Even though the emulator isn't showing on the screen, I can close it with alt-f4 and go straight back to the frontend. If I try it again, it usually does the same thing. If I close the frontend and re-open it, it works fine and continues to work fine. I really have no idea why it does this. If at anytime the emulator does load correctly, it will continue to load correctly until I close the frontend.
my batch file is only this for right now:
cd d:\programBdirectory
programB.exe parameters

adding other stuff in didn't seem to change the outcome and using TASKKILL just screwed it up more. So basically, I'm kind of lost as to what the problem is and how to fix it. If anybody has any more suggestions, please help me. thanks

05-20-2004, 09:13 AM	#9 (permalink)
yatzr Insane	hrdwareguy, although that's a good idea, I don't know how to make the program close itself when it calls the batch file other than taskkill (I didn't write program A or anything and although it is open source, I don't have the skills to try and change it). Also, a pause does make it work, but I really don't want to have to hit a button each time I do it. Another problem though, everytime program A calls the batch file or program B, it becomes "not responding", until program B is closed. So, the only way to close it is to force it (/f) and I think that causes a memory leak. So i don't know if I even want to go that route anymore. I think all it really needs is a bit of a delay. I think program B get's loaded up too fast and doesn't give program A time to minimize or something like that (I don't really know if that is even a plausible cause). So how could i get it to delay? I think I'm going to just have it change directories a bunch before it calls program B and see if that works. edit: okay. so the delay didn't work, it just took longer to load. The same problem still exists in that the two programs don't like each other. I've somewhat narrowed down when this happens though. Program A is just a frontend for emulators that I have startup when the computer starts up. The first time it starts up, it almost always screws up loading the certain emulator. Even though the emulator isn't showing on the screen, I can close it with alt-f4 and go straight back to the frontend. If I try it again, it usually does the same thing. If I close the frontend and re-open it, it works fine and continues to work fine. I really have no idea why it does this. If at anytime the emulator does load correctly, it will continue to load correctly until I close the frontend. my batch file is only this for right now: cd d:\programBdirectory programB.exe parameters adding other stuff in didn't seem to change the outcome and using TASKKILL just screwed it up more. So basically, I'm kind of lost as to what the problem is and how to fix it. If anybody has any more suggestions, please help me. thanks __________________ Mechanical Engineers build weapons. Civil Engineers build targets. Last edited by yatzr; 05-20-2004 at 01:34 PM..