Xref: utzoo comp.os.msdos.programmer:953 comp.sys.ibm.pc.misc:1740
Path: utzoo!attcan!uunet!sjsca4!poffen
From: poffen@sj.ate.slb.com (Russ Poffenberger)
Newsgroups: comp.os.msdos.programmer,comp.sys.ibm.pc.misc
Subject: MS Linker (5.1) searches drive C:
Message-ID: <1990Sep17.173137.11206@sj.ate.slb.com>
Date: 17 Sep 90 17:31:37 GMT
Reply-To: poffen@sj.ate.slb.com (Russ Poffenberger)
Organization: Schlumberger Technologies, San Jose, CA.
Lines: 28


In attempting to use MSC 6.0, after compiling a program, then trying to link,
under certain circumstances, the linker (Segmented Executable Linker Ver 5.10
that comes with MSC 6.0) blindly attempts to search drive C:

Normally this isn't a problem, except that I have three floppy drives, so my
hard disk starts at D:. I must have a floppy in drive C: to avoid a drive not
ready message, even if it is just a blank formatted one.

If I link a simple application, say the ubiquitious hello.c program, specifying
just the hello.obj module, the executable as hello.exe, no map or def files,
it works OK. If I try to mention a def file with just the name and heapsize
parameters, then it looks on drive C:.

I need to use a def file for most of my application because they are Windows
application and you need a def file.

I have checked my path, there is no reference to drive C: anywhere. The same is
true for the LIB and TMP environment variables.

Has anyone else seen this?

Thanks.

Russ Poffenberger               DOMAIN: poffen@sj.ate.slb.com
Schlumberger Technologies       UUCP:   {uunet,decwrl,amdahl}!sjsca4!poffen
1601 Technology Drive		CIS:	72401,276
San Jose, Ca. 95110             (408)437-5254