From: Tim Roberts <t...@probo.com>
Subject: Re: MASM 6.11 not working on Vista
Date: Fri, 23 Oct 2009 21:31:21 -0700
Organization: Providenza & Boekelheide, Inc.
Message-ID: <g905e5lnk3cg5soq9b9kjkac9if1jajc68@4ax.com>
References: <hbmmpg$1ru$1@aioe.org> <lgovd597fvgh3n76s9qpp77jrc9md7jpqf@4ax.com> <hbp18g$lhl$1@aioe.org>
X-Newsreader: Forte Agent 5.00/32.1171
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: microsoft.public.masm
NNTP-Posting-Host: pool-74-107-146-223.ptldor.fios.verizon.net 74.107.146.223
Lines: 27
Path: g2news2.google.com!news2.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.alt.net!msrtrans!TK2MSFTFEEDS02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
X-Original-Lines: 1         
X-Original-Bytes: 1862

Max <non...@nohost.xxx> wrote:
>
>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.
-- 
Tim Roberts, t...@probo.com
Providenza & Boekelheide, Inc.