Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Newbie: Link error - MSPDB60.DLL

197 views
Skip to first unread message

stephen.roberts4

unread,
Nov 19, 2000, 3:00:00 AM11/19/00
to
Executing "ml exampl1.asm" gives me a message:

"A required .DLL file, MSPDB60.DLL, was not found." (in a Message Box)

and

"C:\Program Files\Microsoft Visual Studio\VC98\ASM>ml exampl1.asm
Microsoft (R) Macro Assembler Version 6.15.8803
Copyright (C) Microsoft Corp 1981-2000. All rights reserved.

Assembling: exampl1.asm
MASM : fatal error A1020: cannot find link.exe"

(in the DOS window).

Link.exe is in the path, and the .obj file is created.

Please can someone point me in the right direction?


stephen.roberts4

unread,
Nov 19, 2000, 3:00:00 AM11/19/00
to

Tim Roberts

unread,
Nov 20, 2000, 3:00:00 AM11/20/00
to
"stephen.roberts4" <stephen.aus...@ntlworld.com> wrote:

>Executing "ml exampl1.asm" gives me a message:
>
>"A required .DLL file, MSPDB60.DLL, was not found." (in a Message Box)

And is MSPDB60.DLL in the path? In my Visual Studio setup, it is not; it
is located in the VB98 subdirectory. Try copying this to your
Windows\System directory.

>"C:\Program Files\Microsoft Visual Studio\VC98\ASM>ml exampl1.asm
>Microsoft (R) Macro Assembler Version 6.15.8803
>Copyright (C) Microsoft Corp 1981-2000. All rights reserved.
>
> Assembling: exampl1.asm
>MASM : fatal error A1020: cannot find link.exe"

>...


>Link.exe is in the path, and the .obj file is created.

Are you sure link.exe is in the path? Are there blanks in your path? It
might be that ML 6.15 is too stupid to handle blanks in the path. If your
path currently includes "\program files\microsoft visual studio\vc98\bin",
try writing a new path with the short name version. It will be something
like "\progra~1\micros~3\vc98\bin", but you'll have to look at 'dir
"\program files"' to find the right short name.

Microsoft made a huge mistake by allowing blanks in path names, and then
not supporting it correctly with all of their tools. I now force Visual
Studio to load into a directory called "\VS" to avoid problems like this.
--
- Tim Roberts, ti...@probo.com
Providenza & Boekelheide, Inc.

0 new messages