| Author |
 Topic  |
|
|
MichaelBadichi
New Member
2 Posts |
 Posted - May 31 2005 : 04:31:44 AM
|
As your tool is designed for developers, i see it really annoying that i have to unload SoftIce every time i wish to use VA. since i am writing drivers and debugging kernel modules, you actually force me to abandon VA in favour of SICE.
I understand that you dont want your tool to be cracked, but you can use methods like obfuscating your code to make a cracker's life harder.
a good cracker dont really need to execute code in order to crack or keygen. he simply extracts and dissasembles. |
|
|
Stephen
Tomato Guru
United Kingdom
781 Posts |
Posted - May 31 2005 : 04:56:47 AM
|
| My recollection is that SoftIce and VA are compatible once you have purchased VA. Search these forums for previous threads mentioning SoftIce. |
Stephen Turner
ClickTracks http://www.clicktracks.com/
Winner: ClickZ's Best Web Analytics Tool 2003 & 2004
|
 |
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - May 31 2005 : 05:04:56 AM
|
Once you registered your copy of VAX with a legal key, you can run SoftICE parallel to VS/VAX.
To quote support in this Thread:
quote:
We permit licensed customers to run our software with SoftICE. Only during trial cannot you not run the two at the same time.
|
 |
|
|
|
kevinsikes
Tomato Guru
USA
271 Posts |
Posted - Jun 30 2005 : 2:16:15 PM
|
| A similar issue is when writing add-ins for Visual C++ 6.0, then attaching the debugger to another instance of VS to step through your add-in code, VAX takes a poop and unloads, displaying this message box: "For security purposes, this program will not run while system debuggers are active. Please remove or disable the system debugger before trying to run this program again." This prevents me from seeing how my add-in might react to VAX during debugging. I don't do this often, though, so I don't worry about it too much. |
Kevin Sikes
Infotainment Platform Design Engineer
Ford Motor Company |
|
|
|
annajayne
Starting Member
United Kingdom
1 Posts |
Posted - Aug 04 2005 : 11:32:05 AM
|
quote:
Originally posted by kevinsikes
A similar issue is when writing add-ins for Visual C++ 6.0, then attaching the debugger to another instance of VS to step through your add-in code, VAX takes a poop and unloads, displaying this message box...
We have issues with this behaviour too (it also affects all versions of VS.NET), and with our primary activity being add-in development, its incredibly annoying to not be able to debug any issues which might be related to interactions between VA-X and our code.
Whilst we understand the reasons for protecting VA-X in this way (we have similar considerations, but a different security solution) it does make like unduly difficult for add-in authors.
Regards,
Anna-Jayne Metcalfe
Owner, Riverblade Limited |
Edited by - annajayne on Aug 04 2005 11:46:56 AM |
|
|
|
feline
Whole Tomato Software
United Kingdom
19014 Posts |
Posted - Aug 04 2005 : 12:32:39 PM
|
first the "silly" question, are you using a trial of VAX, or do you have a licence for VAX on the machines that do this?
if you have a licence can you point me in the right direction for how to go about reproducing this problem? i have never attempted to write a plug-in for the IDE, so being able to download a sample project from codeproject.com and use that to test this would help.
these two posts are the only references to this problem that i am familiar with, probably because most people do not write plugin's. |
zen is the art of being at one with the two'ness |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Aug 04 2005 : 5:30:08 PM
|
| If you have a valid license for VA X, contact us for a version that works while debugging your add-in. |
|
|
|
MichaelBadichi
New Member
2 Posts |
Posted - Aug 04 2005 : 6:01:17 PM
|
ok ok...
i got it the first time, no need to shout.
we already purchased some licences at work.
10x anyway :) |
|
|
|
kevinsikes
Tomato Guru
USA
271 Posts |
Posted - Aug 06 2005 : 12:55:02 AM
|
Feline, to answer your question, yes - I do have a licensed copy of VAX. I know support has already responded indicating they'd provide a copy of VAX that works under a debugger, but I wanted to post this information for the sake of completeness.
When I get some time I'll send you the source for a VC6 add-in I wrote to provide some BRIEF behaviors that aren't implemented quite the same in M$'s BRIEF emulation. |
Kevin Sikes
Infotainment Platform Design Engineer
Ford Motor Company |
|
|
|
feline
Whole Tomato Software
United Kingdom
19014 Posts |
Posted - Aug 08 2005 : 3:17:14 PM
|
| excellent, i will look into this when it arrives. |
zen is the art of being at one with the two'ness |
|
|
|
kevinsikes
Tomato Guru
USA
271 Posts |
Posted - Aug 14 2005 : 5:24:16 PM
|
| The addin project may be found here. Enjoy! |
Kevin Sikes
Infotainment Platform Design Engineer
Ford Motor Company |
|
|
|
feline
Whole Tomato Software
United Kingdom
19014 Posts |
Posted - Aug 16 2005 : 5:33:37 PM
|
interesting 
after some experimentation i got a message box with the title "E" telling me that some program would not run while a system debugger was running.
there is just a *slight* difference trying to run this dll in debug mode with VAX enabled and disabled. it is time to go and ask support what the policy here is, although i have the suspicion i know what the answer is going to be. |
zen is the art of being at one with the two'ness |
Edited by - feline on Aug 16 2005 5:37:56 PM |
|
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Aug 16 2005 : 5:44:55 PM
|
The problem we're facing here is the copy-protection.
It has the multiple-license built-in, and also the check for System-Debuggers and multiple usage over network.
All this comes from the copy-protection, not from VAX... so I doubt that there's an "easy" solution to this problem. Not impossible maybe, but definitely not easy... |
|
|
|
| |
Topic |
|
Topic Locked
