MASM 6.11 not working on Vista
Max
I'm moving to Microsoft Vista but I need to use MASM 6.11 for my work and,
unfortunately, doesn't seem to work on Vista. The problem is the linker
that for some reasons, doesn't work, not show any message and close itself
immediately without make any operation. I can not use MASM32 that is
working under Vista because I have a lot of code made for MASM 6.11 that
have some parts not compilable by MASM32.
Someone know how to have MASM 6.11 working under Vista?
Thank you
Tim Roberts
>
>I'm moving to Microsoft Vista but I need to use MASM 6.11 for my work and,
>unfortunately, doesn't seem to work on Vista. The problem is the linker
>that for some reasons, doesn't work, not show any message and close itself
>immediately without make any operation. I can not use MASM32 that is
>working under Vista because I have a lot of code made for MASM 6.11 that
>have some parts not compilable by MASM32.
Do you have an example? ML is almost entirely upward compatible.
>Someone know how to have MASM 6.11 working under Vista?
I think you're saying that MASM actually works just fine for you, but the
linker does not. Which linker are you using? If you're building 32-bit
applications, you can use whatever linker you want.
Are you using Vista 64 or Vista 32?
--
Tim Roberts, ti...@probo.com
Providenza & Boekelheide, Inc.
Max
Thank you for your reply. I'm developing under Vista 32 and the version
of the linker is 5.31.009. I make 16 bit application. Maybe about my
example comparing MASM6.11 and MASM32 I didn't explaining well. The
problem is always in the linker, it seem that the linker used by MASM32
doesn't know some predefined "labels" (I don't know how to explain well)
and return me an error. However if I'll find a way to have my "old"
MASM6.11 linker working also under Vista 32 I think it will be the best
solution, if possible.......
Thank you
Tim Roberts <ti...@probo.com> wrote in
news:lgovd597fvgh3n76s...@4ax.com:
Tim Roberts
>
>Thank you for your reply. I'm developing under Vista 32 and the version
>of the linker is 5.31.009.
Are you aware that version of the linker is 20 years old?
>I make 16 bit application.
And are you aware that 16-bit applications do not work AT ALL in the 64-bit
systems?
>Maybe about my example comparing MASM6.11 and MASM32 I didn't explaining
>well. The problem is always in the linker, it seem that the linker used
>by MASM32 doesn't know some predefined "labels" (I don't know how to
>explain well) and return me an error.
The linker in MASM32 is the 32-bit linker. Although MASM can create either
16-bit or 32-bit object files, the linker (like most development tools) is
bit-specific. The segmented linker (which you are using) only does 16-bit
apps, and the incremental linker (the one in MASM32) only does 32-bit apps.
The segmented linker is a 16-bit app that uses the Phar Lap DOS extender. I
haven't seen any 16-bit apps fail to run in Vista, but I suppose it's
possible.
Max
> Are you aware that version of the linker is 20 years old?
Yes, I now :-)
>>I make 16 bit application.
>
> And are you aware that 16-bit applications do not work AT ALL in the
> 64-bit systems?
I'm sorry, I made a mistake in the explanation of my work. Me and my
colleague we develop BIOS that must to be 16 bit, no Windows application
> The linker in MASM32 is the 32-bit linker. Although MASM can create
> either 16-bit or 32-bit object files, the linker (like most
> development tools) is bit-specific. The segmented linker (which you
> are using) only does 16-bit apps, and the incremental linker (the one
> in MASM32) only does 32-bit apps.
>
> The segmented linker is a 16-bit app that uses the Phar Lap DOS
> extender. I haven't seen any 16-bit apps fail to run in Vista, but I
> suppose it's possible.
The problem is that we have a very large amount of asm source codes
compilable by MASM 6.11 but that return error if try to compile with
MASM32. In particular the linker return error in some predefined words that
doesn't know.Maybe is there some triks to "tell" to MASM32 linker to work
in 16 bit compatibility mode?
Thank you for your support
Tim Roberts
>
>The problem is that we have a very large amount of asm source codes
>compilable by MASM 6.11 but that return error if try to compile with
>MASM32. In particular the linker return error in some predefined words that
>doesn't know.Maybe is there some triks to "tell" to MASM32 linker to work
>in 16 bit compatibility mode?
I guess you didn't understand my paragraph above. MASM is the **ONLY**
development tool from Microsoft that handles both 16-bit and 32-bit
applications in a single binary. ALL of the other tools do one or the
other. The segmented linker does 16-bit binaries ONLY, and the incremental
linker does 32-bit binaries ONLY.
If the segmented linker doesn't fly in Vista, you may be reduced to running
XP in a VM.
There are other linkers that will do 16-bit binaries, although I have not
used any of them.