From: "Todd Beckering" Newsgroups: comp.os.msdos.djgpp Subject: bash command file and windows pifs Lines: 14 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: Date: Wed, 15 Nov 2000 18:48:25 GMT NNTP-Posting-Host: 12.75.128.167 X-Complaints-To: abuse AT worldnet DOT att DOT net X-Trace: bgtnsc05-news.ops.worldnet.att.net 974314105 12.75.128.167 (Wed, 15 Nov 2000 18:48:25 GMT) NNTP-Posting-Date: Wed, 15 Nov 2000 18:48:25 GMT Organization: AT&T Worldnet To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com I'm trying to associate a bash command file with a windows file type, and am having a problem. I set up the associating pif command line: bash_path my_command_file_path %1 but when I double click on a file, bash executes the file I click on (%1), instead of my command file. It looks like windows is executing: bash_path %1 I've used pifs for other command files, and they work fine, including parameters. It's the %1 that seems to throw a monkey wrench in things. Any pointers on how to do this? Thanks. I'm running Windows ME.