Possible causes:
•Obsolete DirectX version
DirectX 8.1 is the minimum requirement for the system.
•Non-administrative privileges (XP/Vista/Windows 7)
You must have administrative rights to the computer.
•Hotkey conflict
a.If the program has been running okay and only crashes after a recent hotkey assigment/reassignment, this is probably the reason. Remove the conflicting assignment.
b.You may have another program running that has already hogged one or more of the hotkeys. We have reports from a user who had a this problem because of his ICQ program, until he disabled some of ICQ's hotkeys.
There are two things you can do to diagnose the conflict:
1.Try running the TitleVision program with everything else disabled. Close all visible programs and after that press Ctrl-Alt-Delete and remove all tasks except Systray and Explorer.
OR:
2.Try and move the file named keyboard config.txt temporarily somewhere else (eg. your desktop) and run the Sub Machine program again.
The file is found here:
XP: C:\Documents and Settings\[Username]\Application Data\Titlevision 2011
Vista, Win 7 and 8: C:\Users\[Username]\Appdata\Roaming\TitleVision 2011
If the program runs, it is one or more of the hotkey definitions that is the problem.
If this is the case, you must either change the conclicting hotkey definition in the other program (whatever that program is) or redefine the conflicting hotkey(s) in Sub Machine under Options/Setup/Keyboard Configuration in the main program or just change it/them manually in keyboard config.txt.
• Old file damaged
If the file last processed has been damaged, the program may crash at startup if it's configured to open the last file saved. To stop this, delete the troublemaking file's name in C:\Documents and Settings\[Username]\Application Data\Titlevision 2011\LastFilesOpen.txt (XP) or C:\Users\Niels\AppData\Roaming\Titlevision 2011\LastFilesOpen.txt (Vista, Win 7, Win 8)
If you experience unexplainable crashes at startup, please e-mail the file loginfo.txt to TitleVision. The easiest way to do this is to select Options/help/view logfile and copy the contents to a mail. The info in this file will help us diagnose the problem.