Fatal Error A1000 Masm
MASM Forum » General » The Campus » MASM : fatal error A1000: cannot open file : C:\masm32\aaa.asm « previous next » Print Pages: [1] Author Topic: MASM : fatal error A1000: cannot open file : C:\masm32\aaa.asm (Read 3757 fatal error a1000 cannot open file irvine32 inc times) Dark_Mark Regular Member Posts: 1 MASM : fatal error A1000: cannot open file : masm32 C:\masm32\aaa.asm « on: December 30, 2014, 07:58:13 PM » Hi. Ive just installed the MASM32 SDK and tried to assemble & link a simple kip irvine program and Im always having this error message." Assembling: C:\masm32\aaa.asmMASM : fatal error A1000: cannot open file : C:\masm32\aaa.asm "And here is a screenshot.Ive seen some people having the same error in this forum. And Ive tried the solutions but I couldn't solve the problem. Besides they were installed the MASM32 in directories other than C:\What's the wrong with this and how can I solve it ?Im using windows 8.1 x64 and both windows and MASM32 are installed in C:\Thanks. Logged dedndave Member Posts: 8695 Still using Abacus 2.0 Re: MASM : fatal error A1000: cannot open file : C:\masm32\aaa.asm « Reply #1 on: December 31, 2014, 01:07:59 AM » where is the aaa.asm file located ?to save a step - show us the codeeven though it isn't at fault, it will save us some typing - lol Logged jj2007 Member Posts: 5979 Assembler is fun ;-) Re: MASM : fatal error A1000: cannot open file : C:\masm32\aaa.asm « Reply #2 on: December 31, 2014, 02:23:44 AM » "can't open" can mean "can't find" or "I'm blocked by something". As Dave wrote, check if the file exists, and if yes, try to find a reason why it cannot be opened. For example, using Microsoft Word for looking at your source is not a good idea, as it locks files. Logged Masm32 Tips, Tricks and Traps anunitu Member Posts: 619 Re: MASM : fatal error A1000: cannot open file : C:\masm32\aaa.asm « Reply #3 on: December 31, 2014, 02:49:53 AM » Not sure,but if you just up graded to 8.1(I just started using win7-64) you might be running into what I did at first...files blocked by the system. it took me a bit to figure out how to unset the block on files that came from outside(download) until I snooped a bit in the system.as in "Files did not originate on this system" so blocked. Logged FORTRANS Member Posts: 890 Re: MASM : fatal error A1000: cannot open file : C:\masm32\aaa.asm « Reply #4 on: December 31, 2014, 03:24:57 AM » Hi, You can open a command prompt s
Links and Website Archived Old Forum Files Links for VC and MASM 128553 Posts in 15254 Topics by 684 Members Latest Member: mottt The MASM Forum Archive 2004 to 2012 Project Support Forums IDE Development and Support RadAsm Support Forum (Moderator: KetilO) fatal error A1000: cannot open file « previous next » Pages: [1] Author Topic: fatal error A1000: cannot open file (Read 9955 times) Slugsnack Member Posts: 463 fatal error A1000: cannot open file « on: August 08, 2009, 03:59:18 PM » does anyone http://masm32.com/board/index.php?topic=3908.0 know how to fix this error ? i installed windows 7 RTM last night but the system drive is F as opposed to C which is i am guessing is why this error is occuring Logged dedndave Member Posts: 12523 Re: fatal error A1000: cannot open file « Reply #1 on: August 08, 2009, 04:17:12 PM » the last 4 paths say "masm" instead http://www.masmforum.com/board/index.php?PHPSESSID=786dd40408172108b65a5a36b09c88c0&topic=12043.0 of "masm32" ????of course, that has nothing to do with the include filemasm32 is set up to use a drive other than C:you might try a simple program that only needs kernel32something like - INVOKE ExitProcess,0 - and that's itthen, instead of including masm32rt.incinclude windows.inc, kernel32.dll, and includelib kernell32.lib (without the masm32\include path)now, take the paths out of the file - seeing as how they are defined in the environment variables, they should not be requiredat least you can test to see if it's a problem reading environment variables or a problem related to the way the files are declaredalso, you might take a peek inside masm32rt.inc and see if there is anything odd therethat file declares a number of other include/includelib's Logged dedndave Member Posts: 12523 Re: fatal error A1000: cannot open file « Reply #2 on: August 08, 2009, 04:32:44 PM » i see the problem Mike - lolyou are running from the D: drive\masm32\include - it is looking for that on D:if it is on F:, taking the path out of the include won't fix a thingthat is because ALLLLLL the masm32 files have "\masm32\" in th
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more http://stackoverflow.com/questions/32017546/error-a1000-with-masm-visual-studio-2015 about Stack Overflow the company Business Learn more about hiring developers or posting ads http://www.asmcommunity.net/forums/topic/?id=30743 with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up error A1000 with MASM visual studio 2015 up vote 1 down vote fatal error favorite I'm reading a book "Guide to Assembly Language" by James T.Streib in order to learn Assembly but I can't compile the test example on visual studio 2015 because of the following error: 1> Assembling: 1>MASM : fatal error A1000: cannot open file 1> Microsoft (R) Macro Assembler Version 12.00.31101.0 I added this in the Custom Build Tool Command Line of my main.asm file: ml -c -Zi "-Fl$(IntDir)\$(InputName).lst" "-Fo$(IntDir)\$(InputName).obj" fatal error a1000 "$(InputPath)" And Outputs: $(IntDir)\$(InputName).obj I also added msvcrt.lib in the Additional Dependencies of the linker. Any idea ? visual-studio assembly visual-studio-2015 masm share|improve this question edited Sep 30 at 23:15 Guilherme Fidelis 34812 asked Aug 14 '15 at 19:39 panicq 485 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted Try using the following for the Command Line field: ml -c -Zi "-Fl$(IntDir)%(Filename).lst" "-Fo$(IntDir)%(Filename).obj" "%(FullPath)" and this for the Output field: $(IntDir)%(Filename).obj The old "Input" macros are deprecated in Visual Studio 2015 and have been replaced by new "item metadata macros" that use the %() syntax. Here's a screenshot showing where I've entered these lines. Note that I've changed to the "Configuration" and "Platform" pulldowns to "All Configurations" and "All Platforms" respectively so that these parameters are used no matter what sort of build is being performed. share|improve this answer edited Aug 14 '15 at 23:56 answered Aug 14 '15 at 21:23 Ross Ridge 17.9k22050 Hum, I still have my error + a new one Error 2 error MSB3073: The command "ml -c -Zi "-FlDebug\\.lst" "-FoDebug\\.obj" "" :VCEnd" exited with code 1. –panicq Aug 14 '15 at 21:45 You don't seem to be using t
Macro Assembler Version 6.14.8444Copyright (C) Microsoft Corp 1981-1997. All rights reserved.Assembling: mdir.asmmdir.asm(17) : fatal error A1000: cannot open file : \masm32\include\windows.inc"please help me how can i solve this problem? Posted on 2011-11-15 00:49:20 by Abhijit Re: MASM It means mdir.asm is not on the same drive/partition as masm32 installation. This is by design :twisted:Easy solution: move the file to C: (or wherever masm32 is)Hard (If you are willing):- remove all "\masm32\include" "\masm32\lib" from asm files (just the path part!!) in include/includelib lines- add /I"C:\masm32\include" to ml command-line and /LIBPATH:"C:\masm32\lib" to link command-line Posted on 2011-11-15 07:32:23 by drizz