The MASM Forum Archive 2004 to 2012

General Forums => The Campus => Topic started by: vikas on October 31, 2008, 02:13:35 PM

Title: MASM : fatal error A1000:
Post by: vikas on October 31, 2008, 02:13:35 PM
Assembling: c:\Documents
MASM : fatal error A1000: cannot open file : c:\Documents
Project : error PRJ0019: A tool returned an error code from "Performing Custom Build Step"


I am getting above erroe.

Kindly help me if possible.

Thanks in advance
Title: Re: MASM : fatal error A1000:
Post by: Mark Jones on October 31, 2008, 02:53:59 PM
...Did not you just say, in another thread, that this is an error from the MSVC++ tool chain?
Title: Re: MASM : fatal error A1000:
Post by: MichaelW on October 31, 2008, 03:13:27 PM
vikas,

I'm not sure exactly what you are doing, but for the command lines of the versions of ML and LINK supplied in the MASM32 package (and I think probably later versions) any path with one or more embedded spaces must be enclosed in double quotes. One way around this, that may or may not be possible in your case, and assuming that the filenames do not contain embedded spaces, is to work from the directory were the source files are stored, so you need only specify the filenames on the command lines.

Title: Re: MASM : fatal error A1000:
Post by: KeepingRealBusy on November 01, 2008, 02:32:27 AM
You could also use the short (mangled DOS 8.3) path name for the .BAT call.
Title: Re: MASM : fatal error A1000:
Post by: vikas on November 01, 2008, 05:05:19 AM
Actully I created the application in which we are using few asembly files too . Its vc++ application . I run the same application on Window xp,then I got the error ml.exe missing something like that.

So I just copy the required file in the proper location and it start working fine...

But when I am trying to run the same application on Mac machine ,it give me error given below:-

Assembling: c:\Documents
MASM : fatal error A1000: cannot open file : c:\Documents
Project : error PRJ0019: A tool returned an error code from "Performing Custom Build Step"
Actuall I have a software which creates the virtual environment in Mac machine that you are working in Window Xp machine. So why such error is coming in there..

Can anybody help me in this regard, Thanks in advance...