fatal error A1000: cannot open file

[Slugsnack]

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

[dedndave]

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

[dedndave]

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....

[Slugsnack]

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 !