Ticket #72 (closed defect: fixed)

Opened 3 years ago

Last modified 1 year ago

Windows commandline closed after error

Reported by: alban@tryphon.org Assigned to: alban@tryphon.org
Priority: normal Milestone: 20060515
Component: packaging - win32 Version: 20051009
Severity: normal Keywords:
Cc:

Description 

When a freecast application is started via a Windows menu shortcut, if it fails to start, the cmd windows is closed directly by the system .. the user can't read the output messages.

Attachments

start-freecast.bat (122 bytes) - added by alban@tryphon.org on 03/23/06 09:35:32.
script to start freecast root node and pause after execution

Change History

03/23/06 09:33:15 changed by alban@tryphon.org

  • status changed from new to assigned.
The bat scripts must be modified to make a "pause" if the jvm errorlevel is abnormal. This behavior should be optional because it's useless when the application is executed from a standard command line.

Workaround: use a small bat file which starts the freecast application like the shortcut but makes a pause after the freecast execution.

03/23/06 09:35:32 changed by alban@tryphon.org

  • attachment start-freecast.bat added.

script to start freecast root node and pause after execution

03/23/06 09:48:48 changed by alban@tryphon.org

  • component changed from default to packaging - win32.

04/23/06 23:04:08 changed by alban@tryphon.org

  • status changed from assigned to closed.
  • resolution set to fixed.
done, added a simple "if ERRORLEVEL 1 pause"

05/25/06 19:44:05 changed by alban@tryphon.org

  • milestone changed from next to 20060515.
released into 20060515

11/27/07 19:15:58 changed by alban

  • priority changed from high to normal.

Add/Change #72 (Windows commandline closed after error)




Change Properties
Action