The MASM Forum Archive 2004 to 2012
Welcome, Guest. Please login or register.
April 03, 2020, 06:00:22 PM

Login with username, password and session length
Search:     Advanced search
128553 Posts in 15254 Topics by 684 Members
Latest Member: mottt
* Home Help Search Login Register
+  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] Print
Author Topic: fatal error A1000: cannot open file  (Read 14169 times)
Slugsnack
Member
*****
Posts: 463


fatal error A1000: cannot open file
« on: August 08, 2009, 03:59:18 PM »



does anyone 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 of "masm32" ????
of course, that has nothing to do with the include file
masm32 is set up to use a drive other than C:

you might try a simple program that only needs kernel32
something like - INVOKE ExitProcess,0 - and that's it
then, instead of including masm32rt.inc
include 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 required
at least you can test to see if it's a problem reading environment variables or a problem related to the way the files are declared
also, you might take a peek inside masm32rt.inc and see if there is anything odd there
that 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 - lol
you 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 thing
that is because ALLLLLL the masm32 files have "\masm32\" in the path names
if you were to remove all of them, you'd be ok, because the environment variables would kick in

here's your prob....
Logged
Slugsnack
Member
*****
Posts: 463


Re: fatal error A1000: cannot open file
« Reply #3 on: August 08, 2009, 05:56:35 PM »

dave, you're a beast. oh my god.. so observant.

btw the masm bits is for radasm like inside its folder : )

god you're good. LOVE YOU BRO !
Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP The MASM Forum Archive 2004 to 2012 | Powered by SMF 1.0.12.
© 2001-2005, Lewis Media. All Rights Reserved.
Valid XHTML 1.0! Valid CSS!