X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
NNTP-Posting-Date:	Mon, 14 Jul 2008 14:09:17 -0500
Date:	Mon, 14 Jul 2008 12:09:18 -0700
From:	Rob Gaddi <rgaddi AT technologyhighland DOT com>
User-Agent:	Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	Drag and Drop to Command Line
Message-ID:	<I6-dnUDsEJnAOebVnZ2dnUVZ_rPinZ2d@lmi.net>
Lines:	33
X-Usenet-Provider:	http://www.giganews.com
NNTP-Posting-Host:	66.117.134.49
X-Trace:	sv3-rMhH7O5Rzgt35Nuiejxh52RcnKB5GpNl9obeuYZfZY9mu+T7LQdFhIipRtW/+x0+aOq4MUpDDMeVt8f!X8IFkzVi0+xLkhN68IaIJ22o+25yXkJqybV6se8/stDKaBNTnPlW/y/f7r63C/lsbW/xHScVXNSy!7A==
X-Abuse-and-DMCA-Info:	Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info:	Otherwise we will be unable to process your complaint properly
X-Postfilter:	1.3.39
X-Original-Bytes:	2534
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi all --

This is probably an idiot newbie question, but if I Googled with it any 
longer I was going to have to buy it dinner, so I'm hoping someone here 
might have a suggestion/idea of what's going on.

I've written a very short assembler in C for a proprietary microengine 
that I'm working on.  Like any sensible assembler, it wants to take in 
the input filename on the command line, and if no further command line 
options are given, make some assumptions based on the input filename as 
to what the output filename should be.  I drive it from the command 
prompt and all is well.  I pass it long filenames, it works with long 
filenames, and creates outputs with long filenames.  Fine, perfect, all 
well and good.

But when I try to drag and drop from Explorer (under XP) onto the .EXE 
of the interpreter, for some reason it gets passed the short file name 
instead, and I get the appropriately mangled output file names. 
Ideally, this wouldn't happen; Windows seems happy to pass plenty of 
other programs long names from a drag and drop.  But it thinks that mine 
wants a short name instead.

Any ideas on why this is happening and how to fix it?  Is there some 
arcane setting in the .PIF file that I'm missing?  Some pragma flag that 
I should be setting to tell Windows that I'm a sensible, modern sort of 
program, and happy to take more than 11 characters of file name?

Thanks in advance,
Rob

-- 
Rob Gaddi, Highland Technology
Email address is currently out of order

- Raw text -