MIDI-OX User Forum - Print Page


    
      
        MIDI-OX User Forum
        (http://www.midiox.com/cgi-bin/yabb/YaBB.pl)
      

        MIDI-OX >> Questions and Discussion >> Seem to get random error messages on startup.....
        
(Message started by: swayzak on Dec 19^th, 2002, 3:49am)

Title: Seem to get random error messages on startup.....
Post by swayzak on Dec 19^th, 2002, 3:49am

hi

I have set up shortcuts in the Startup folder which point towards the appropriate profiles (e.g. "hammerfall to yoke 1" and "sw1000 to yoke 1").

I get a message saying something like "Driver didn't close correctly last time. Do you want to try again ?"

If I click OK then everything continues as normal.

This error doesn't seem to happen everytime.

I am not aware of a problem with driver closing in the previous shutdown prior to this message.

Any ideas ?

cheers

swayzak

Title: Re: Seem to get random error messages on startup..
Post by symo on Dec 19^th, 2002, 5:57am

Are you the real Swayzak?? If you are I love your groovetechnology1.3 CD. Not that this helps you with your problem................................................................

s

Title: Re: Seem to get random error messages on startup..
Post by swayzak on Dec 19^th, 2002, 7:54am

Alas no - just love the stuff....

Title: Re: Seem to get random error messages on startup..
Post by Jamie OConnell on Dec 19^th, 2002, 10:47am

That message is part of the MIDI-OX fail-safe mechanism. It logs driver opens as it connects them to a log file named _MOXBOOT.TXT in the application directory. You can use this file to determine which driver failed. It also sets a registry flag for each MIDI-OX instance (Profile1, Profile2, ...) named LastOpenFailed prior to opening each driver and clears the flag upon a successful return.

On a subsequent session, if it finds LastOpenFailed set, it assumes MIDI-OX has crashed or hung while trying to open the device, and then displays the message, rather than trying to open it again. This prevents never being able to run MIDI-OX again because of a bad driver.

I suppose you could always force a MIDI-OX launch by forcibly resetting that flag on each instance with a .REG file before launching.