Masm32 Fatal Error
Contents |
MASM Forum » General » The Campus » MASM : fatal error A1000: cannot open file : C:\masm32\aaa.asm « previous next » Print Pages: [1] fatal error a1000 cannot open file irvine32 inc Author Topic: MASM : fatal error A1000: cannot open file : C:\masm32\aaa.asm (Read
Kip Irvine
3795 times) Dark_Mark Regular Member Posts: 1 MASM : fatal error A1000: cannot open file : 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 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: 5999 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: 625 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
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 General Forums The Workshop fatal error A1000: cannot open file : Irvine32.inc « previous next » Pages: [1] Author Topic: fatal error A1000: cannot open file : Irvine32.inc (Read 14550 times) shadow_005 Guest fatal error A1000: cannot open file : Irvine32.inc « on: September 23, 2005, 02:30:44 PM » Hi, I also ought the book: Assembly Language For Intel-Based Computers. It uses a file called "Irvine32.inc". It's included on the CD-Rom. The book says that I have to put it in the "include" directory. http://masm32.com/board/index.php?topic=3908.0 So I put Irvine32.inc in the "\masm32\Include\" dir.But it didnt work so I also put the Irvine32.lib in the "\masm32\lib\" dir (as I read in these forums ). The error was gone but now I get this error when I use the Build All option:Code:Assembling C:\masm32\Hello.asmC:\masm32\Hello.asm(10) : fatal error A1000: cannot open file : Irvine32.inc_Assembly errorPress any key to continue...What did I do wrong? (I have full administrative rights in case it matters) Logged ramguru Guest Re: fatal http://www.masmforum.com/board/index.php?PHPSESSID=786dd40408172108b65a5a36b09c88c0&topic=2778.0 error A1000: cannot open file : Irvine32.inc « Reply #1 on: September 23, 2005, 02:53:54 PM » I think your problem is current directory which is not current... I'm not able to use batch file directly (from explorer with 2-click or TC window) anymore, instead I have to execute the batch from console (Run->"cmd") Logged shadow_005 Guest Re: fatal error A1000: cannot open file : Irvine32.inc « Reply #2 on: September 23, 2005, 03:25:07 PM » My current directory is "C:\masm32\"... I don't get it. I use masm V8.2 btw. Logged ramguru Guest Re: fatal error A1000: cannot open file : Irvine32.inc « Reply #3 on: September 23, 2005, 03:36:27 PM » I assumed you have "compile.bat" (something like that), but it seems you are using QEditor...and menu command "build all". Logged shadow_005 Guest Re: fatal error A1000: cannot open file : Irvine32.inc « Reply #4 on: September 23, 2005, 04:14:47 PM » Yes I use the QEditor... Is there another way to compile and to bypass that error (without using the QEditor if nessecary)?I am new to ASM. And my book is not telling me how to compile at all... Logged ramguru Guest Re: fatal error A1000: cannot open file : Irvine32.inc « Reply #5 on: September 23, 2005, 04:41:17 PM » I'm not sure... You can use IDE like RadASM or create batch file (like I did) and execute like
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 about Stack Overflow the company Business Learn more http://stackoverflow.com/questions/13772748/error1error-a1000-cannot-open-file-masm32-includes-masm32rt-inc about hiring developers or posting ads 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 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error 1 error A1000: cannot open file : \masm32\includes\masm32rt.inc up vote 0 down vote favorite I'm trying to setup a assembler program in VS2012, but whenever include masm32\includes\masm32rt.inc gets fatal error called it returns that error. If I use the absolute path, it works, but all the includes use masm32\includes\ as their incudepath. Is there a way to set \masm32 on the environment variables? assembly visual-studio-2012 masm masm32 share|improve this question edited Dec 8 '12 at 0:22 asked Dec 7 '12 at 23:39 localhost 2251521 What do you mean by "the absolute path... works"? A path beginning with a backslash is already an absolute path. –Neil masm32 fatal error Dec 7 '12 at 23:42 I mean that D:\masm32\includes\masm32rt.inc works. –localhost Dec 8 '12 at 0:22 Despite its name, MASM32 isn't part of Visual Studio, but an entirely separate library. –Bo Persson Dec 8 '12 at 12:34 Yes it is, I installed it on D:\masm32 but all the example source code and all the defalt includes .inc reference the folder as \masm32, but then I get that error connot open file. So I guess something isn't configured correctly –localhost Dec 8 '12 at 13:29 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote accepted MASM32 is NOT part of Visual Studio, MASM is. If you have MASM32 installed on one drive, but your projects/sources are on another drive, how can a relative path work???? i.e. include masm32\includes If this is the case, then you have to use absolute paths, i.e. D:\masm32\includes\masm32rt.inc I do not use VS, but it should have an option to set the include path, which it will then pass this path to the command line of ml to search for includes. share|improve this answer answered Dec 8 '12 at 16:26 Gunner 4,31721331 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name E