  Ŀ
    Strategic FALCON Version 1.22 Update - UNHACK.EXE v1.3 
  

  Strategic Falcon, Falcon 3.05, Windows 95, and MS-DOS 7.0:  
    
    If you've got Falcon working well under Windows 95, 
    congratulations!  If you've also used StratFalc, you may 
    have noticed something--namely, it doesn't work!
    
    Microsoft, in all its wisdom, has altered the way DOS 
    handles a call to Interrupt 21h, function 3Dh ("Open disk 
    file with handle"). Previously, when Falcon made this call, 
    hiding the file it requested (I'm talking about the MIS 
    file) was enough to keep Falcon from altering it. 
    
    Not anymore. Under DOS-7, it makes no difference whether 
    the file is hidden.  So we've got trouble.  I had to go 
    back to setting the read-only bit--but that makes Falcon 
    3.05 crash. Falcon 3.05 asks for "read & write" access to 
    the file (although the particular routine in which we're 
    interested only requires "read" access). When Falcon 
    doesn't get its read & write access, it takes its ball and 
    goes home.
    
    Back to the hack. I altered Falcon so it requests only read 
    access to the MIS file (just like it used to). Now 
    StratFalc can work again. Whenever you run StratFalc with 
    Falcon 3.05 under MS-DOS 7, StratFalc automatically alters 
    your falcon3.exe/falconcd.exe file to accommodate the 
    read-only bit being set. This behavior of StratFalc is 
    imperative and cannot be turned off. However, UNHACK can 
    undo the changes StratFalc makes to the falcon executable.
    Copy UNHACK.EXE from your \STRAT directory into the Falcon
    directory and run it. This will put Falcon back to normal.

    Note that if you do *not* rerun StratFalc after flying each
    mission, you'll get the same mission type, over and over,
    until you do run StratFalc again (or until you run UNHACK,
    which will also restore Falcon to normal).
