Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
02/28/05 19:18
Read: times


 
#88678 - Incorrect Tools.Ini edit
Responding to: ???'s previous message
Mian Ahmed Jehnzeb Anwer said:
i edit the Tool.ini file according to the direction by adding line after copying the file VDM.dll in bin directory of KEIL.
TDRV4=BINVDM51.DLL (“Proteus VSM Monitor-51 Driver”)
But the option of Proteus VSM Monitor-51 Driver was not available.

In that case, your edit of Tools.ini was wrong, or didn't work.

uVision simply reads the TDRV lines to populate its list of Debug drivers - it does no validation of the drivers.
Therefore, if the entry doesn't appear in the list, your edit didn't work.

In your post here, I not that you are using the opening & closing double quotes. Tools.Ini is a plain ASCII text file, so does not support these - you need to use just the "straight" double-quote character, ASCII code 0x22.


List of 15 messages in thread
TopicAuthorDate
Proteus VSM nad KEIL connectivity            01/01/70 00:00      
   Dunno 'bout VSM, but...            01/01/70 00:00      
   Proteus VSM nad KEIL connectivity            01/01/70 00:00      
      Is it in the list now?            01/01/70 00:00      
         Eval Version?            01/01/70 00:00      
            Not Keil            01/01/70 00:00      
   few hints            01/01/70 00:00      
      Not Keil            01/01/70 00:00      
   Proteus & KEIL            01/01/70 00:00      
      Incorrect Tools.Ini edit            01/01/70 00:00      
   Proteus & KEIL            01/01/70 00:00      
      Appnote            01/01/70 00:00      
         This is *DEFINITELY* Your problem            01/01/70 00:00      
         More on Quotes            01/01/70 00:00      
   Proteus and Keil are connected            01/01/70 00:00      

Back to Subject List