Exetools  

Go Back   Exetools > General > General Discussion

Notices

Reply
 
Thread Tools Display Modes
  #1  
Old 06-22-2013, 15:17
Kerlingen Kerlingen is offline
VIP
 
Join Date: Feb 2011
Posts: 338
Rept. Given: 0
Rept. Rcvd 278 Times in 100 Posts
Thanks Given: 0
Thanks Rcvd at 358 Times in 110 Posts
Kerlingen Reputation: 200-299 Kerlingen Reputation: 200-299 Kerlingen Reputation: 200-299
Wild guess: You installed the source code in the "Program Files" directory which is by default read-only to all users expect admin, so the command line tools have no write rights and will fail instantly.
Reply With Quote
  #2  
Old 06-22-2013, 19:26
rcer rcer is offline
Friend
 
Join Date: Dec 2008
Posts: 171
Rept. Given: 5
Rept. Rcvd 9 Times in 8 Posts
Thanks Given: 6
Thanks Rcvd at 30 Times in 22 Posts
rcer Reputation: 9
Hi Kerlingen,

Your guess is right, but I have been running the command line as administrator, and I have checked that read & write access is O.K.

Anyway just to run a check I copied the SDK to the D drive, and I did get the same result.

From all the Googling I did, I understand that the problem is related to incorrectly set environment variables, but I haven't been able to figure out which variable(s) need to be set, and with what values?


regards

rcer
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
What's the regular SDK compile flow with ECC check? bridgeic General Discussion 1 08-29-2014 09:14
How to fix these three RadASM compile errors? bridgeic General Discussion 39 04-10-2013 12:32
how to compile windows NT4/2000? jonwil General Discussion 9 09-05-2004 10:30


All times are GMT +8. The time now is 11:50.


Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX, chessgod101
( Since 1998 )