Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
"EXE has stopped working ..."
#3
Thanks. Tried it:

Replaced RUN with SHELL. It didn't solve problem (still got WIN error) and when SHELLING the calling program remains open which I don't want since going between programs leaves multiple iterations of programs still open.

Also, I am not sure what you mean by "Shell a compiled bas." I am compiling using QB64.exe and running the EXEs.

(FYI the original QB programs used CHAIN because of common variables but I removed CHAIN and used RUN, but that's going to be a question for a different thread.)

A
Reply


Messages In This Thread
"EXE has stopped working ..." - by arnoldhf - 07-16-2022, 03:50 PM
RE: "EXE has stopped working ..." - by bplus - 07-16-2022, 04:44 PM
RE: "EXE has stopped working ..." - by arnoldhf - 07-16-2022, 09:36 PM
RE: "EXE has stopped working ..." - by SMcNeill - 07-16-2022, 10:12 PM
RE: "EXE has stopped working ..." - by mdijkens - 07-17-2022, 07:20 AM
RE: "EXE has stopped working ..." - by arnoldhf - 07-17-2022, 02:34 PM
RE: "EXE has stopped working ..." - by mdijkens - 07-17-2022, 03:18 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  plotting shapes not working madscijr 6 654 10-22-2025, 05:29 AM
Last Post: SMcNeill
  make: *** No targets specified and no Makefile found. Stopped. Rudy M 6 696 10-10-2025, 08:04 AM
Last Post: Rudy M
  why isn't _FULLSCREEN working? madscijr 5 532 09-20-2025, 01:47 AM
Last Post: SMcNeill
  I'm working on an old MS-DOS thingy... KlamPs 2 518 08-25-2025, 09:43 AM
Last Post: hsiangch_ong
  keyword to get the EXE name and the EXE path instead of parsing Command$(0) ? madscijr 8 1,158 07-22-2025, 08:35 PM
Last Post: hsiangch_ong

Forum Jump:


Users browsing this thread: 1 Guest(s)