Searching \ for '[PIC] How to get Win XP to associate MPLAB 7.2 pro' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/languages.htm?key=mplab
Search entire site for: 'How to get Win XP to associate MPLAB 7.2 pro'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] How to get Win XP to associate MPLAB 7.2 pro'
2005\12\03@211957 by Marcel Duchamp

picon face
Just downloaded MPLAB 7.20 onto an XP system.

Everything *was* working ok... but now in Windows Explorer, I cannot
associate .mcp files with mplab.exe

Clicking on 'open with' and browsing to the mplab.exe appears to work
but then clicking on an mcp file opens the file with a text editor
instead of mplab.exe

Doing much the same via the
Windows Explorer/tools/folder options/filetypes,
after browsing to mplab.exe and clicking on it, the 'ok' button is
grayed out like Windows can't seem to see the mplabe.exe file I just
clicked on...

Any ideas? Is my system seriously bent?
ps: Just previously to the install, I removed all previous versions of
mplab...

2005\12\03@220735 by Spehro Pefhany

picon face
At 06:14 PM 12/3/2005 -0800, you wrote:
>Just downloaded MPLAB 7.20 onto an XP system.
>
>Everything *was* working ok... but now in Windows Explorer, I cannot
>associate .mcp files with mplab.exe
>
>Clicking on 'open with' and browsing to the mplab.exe appears to work but
>then clicking on an mcp file opens the file with a text editor instead of
>mplab.exe
>
>Doing much the same via the
>Windows Explorer/tools/folder options/filetypes,
>after browsing to mplab.exe and clicking on it, the 'ok' button is grayed
>out like Windows can't seem to see the mplabe.exe file I just clicked on...
>
>Any ideas? Is my system seriously bent?
>ps: Just previously to the install, I removed all previous versions of
>mplab...

I don't think the installation package puts MPLAB on the path by default.

On my installation, it's: "C:\Program Files\Microchip\MPLAB IDE\Core\"

If XP is the same as Win2K, you can edit the path in the System Properties
dialog.

Best regards,

Spehro Pefhany --"it's the network..."            "The Journey is the reward"
spam_OUTspeffTakeThisOuTspaminterlog.com             Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog  Info for designers:  http://www.speff.com
->> Inexpensive test equipment & parts http://search.ebay.com/_W0QQsassZspeff


2005\12\03@223919 by Scott Pierce

flavicon
face
In Windows Explorer, find a .mcw file you want to associate with
MPLAB.  Hold down the Shift button on your keyboard and right click on the
.mcw file.  A pop-up menu will appear.  Select the "Open With" option.  An
"Open With" dialog box will appear.  Click the "Browse" button, find where
the MPLAB.exe file is located, select it, then press the "Open"
button.  Back at the "Open With" dialog box, check the check box that says
"Always use the selected program to open this kind of file".  Click the
"OK" button.  Now when ever you double click on an MCW file, it'll be
opened with MPLAB.exe.

Scott Pierce



At 07:14 PM 12/3/2005, you wrote:
{Quote hidden}

>

2005\12\03@232801 by Marcel Duchamp

picon face
Thanks Scott and Spehro but no joy. I'll keep tinkering...



2005\12\04@000740 by Jinx

face picon face
I use XP Pro, and have .mcp files associated with MPLAB 6.4. r-c
on any .mcp file, Properties, Change, and select MPLAB from (on
my system anyway) \Program Files\MPLAB IDE\dlls\MPlab.exe.
Works OK here, don't know if/why 7.2 should be any different


2005\12\04@003827 by Scott Pierce
flavicon
face
Really?  That's what I did to get it to work.  Are you sure you checked the
check box that tells Windows to always use that application to open those
files?

Scott Pierce

At 09:22 PM 12/3/2005, you wrote:
>Thanks Scott and Spehro but no joy. I'll keep tinkering...
>
>
>
>

2005\12\04@083637 by olin piclist

face picon face
Marcel Duchamp wrote:
> Everything *was* working ok... but now in Windows Explorer, I cannot
> associate .mcp files with mplab.exe

I doubt that.  I bet Windows is making the association, but MPLAB ignores
the MCP files.  Why would you want to do that anyway instead of using the
MCW files as intended?


******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/products

2005\12\04@084541 by olin piclist

face picon face
Jinx wrote:
> Works OK here, don't know if/why 7.2 should be any different

Because it uses MCW files.

******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/products

2005\12\04@195308 by Chen Xiao Fan

face
flavicon
face

Marcel Duchamp wrote:
> Everything *was* working ok... but now in Windows Explorer, I cannot
> associate .mcp files with mplab.exe

Olin Wrote:
>I doubt that.  I bet Windows is making the association, but MPLAB ignores
>the MCP files.  Why would you want to do that anyway instead of using the
>MCW files as intended?

Olin is correct. I just tried this (I have an extra problem since I do
not have administrator in this computer at work, so -noswitch
command line option is necessary) and that is the case. .mcw will
be okay. .mcp will bring up MPLAB but there is nothing inside.
This is the case with MPLAB 7.10 but I think 7.20 will be the same.

The problem with .mcw file (the workspace file) is that it has
the absolute directory info. .mcp (project file) does not. Therefore
if people want to move the workspace to a different directory, they
have to open MPLAB, open the project file and then save the workspace.
This is the only reason I can think of why we want to associate .mcp
file with MPLAB.

Regards,
Xiaofan

2005\12\06@051650 by Michael Rigby-Jones

picon face


>-----Original Message-----
>From: .....piclist-bouncesKILLspamspam@spam@mit.edu [piclist-bouncesspamKILLspammit.edu]
>Sent: 04 December 2005 04:22
>To: Microcontroller discussion list - Public.
>Subject: Re: [PIC] How to get Win XP to associate MPLAB 7.2
>program icons
>
>
>Thanks Scott and Spehro but no joy. I'll keep tinkering...


I've had this problem if not being able to associate extensions, and despite searching google for literaly hours I only came up with simmilarly frustrated people being giving the same advice for using explorer, when it clearly stated that it doesn't work.  However, I found a fix eventualy.

The problem seems to be that the extension is already associated, but to a path that no longer exists.  It makes it impossible to change the association through explorer in some instances, so you need to crack open regedit. Search for the appropriate extension and either fix the path within regedit or delete the key and re-make the association through explorer.  Microchip changed the default installation directory (and in fact the whole directory structure) some time back and this seemed to be the start of my problems.

Regards

Mike

=======================================================================
This e-mail is intended for the person it is addressed to only. The
information contained in it may be confidential and/or protected by
law. If you are not the intended recipient of this message, you must
not make any use of this information, or copy or show it to any
person. Please contact us immediately to tell us that you have
received this e-mail, and return the original to us. Any use,
forwarding, printing or copying of this message is strictly prohibited.
No part of this message can be considered a request for goods or
services.
=======================================================================

2005\12\06@160521 by Barry Gershenfeld

face picon face

>Doing much the same via the
>Windows Explorer/tools/folder options/filetypes,

When you are in that dialog, you can delete the entire association.  Once
you do
that, the icon should be the default "I have no idea" style, and Explorer will
proudly announce it to be an "MCP File" --meaning it has no idea,
either.  But now
when you go and try to make the association you can be pretty sure that it will
be your answers that get put in there.

>Any ideas? Is my system seriously bent?

Rare for an MS product, but I've seen it happen.

As an aside, I don't use MPLAB this way because I have never seen it work
properly.  I can make MPLAB open but it loads the last project, not the one
I clicked on.   Of course I've been at this since MPLAB 5 so it could be
fixed by now.   I don't remember when I gave up.  I have an MPLAB icon on
the desktop, and I rely on File / Recent Projects to open my project.

If someone says it works now, I'll try it again.  MCP? MCW? They changed it?

Barry

2005\12\06@161801 by olin piclist

face picon face
Barry Gershenfeld wrote:
> As an aside, I don't use MPLAB this way because I have never seen it
> work properly.  I can make MPLAB open but it loads the last project,
> not the one
> I clicked on.   Of course I've been at this since MPLAB 5 so it could
> be
> fixed by now.   I don't remember when I gave up.  I have an MPLAB
> icon on
> the desktop, and I rely on File / Recent Projects to open my project.

I routinely run scripts that build firmware then run MPLAB to debug it.  All
you have to do is run MPLAB.EXE with the MCW file name and "/nospash".


******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/products

2005\12\06@163013 by Marcel duchamp

picon face
Barry Gershenfeld wrote:
{Quote hidden}

Yeah, it is mcw now apparently.  But that is a side issue; it has
*nothing* to do with my system not associating the files.  I have tried
what you mention above but the operation fails: windows acts like I have
pointed at nothing after pointing to the mplab.exe file.  It can be
associated with other exe's however; it worked to associate it with my
text editor program.  But when I point it at mplab.exe, no joy.

I'm looking into Mike Rigby-Jones suggestion of a registry snafu.

2005\12\06@171402 by Gerhard Fiedler

picon face
Barry Gershenfeld wrote:

> MCP? MCW? They changed it?

They confused it... :)

MPLAB has settings in (at least) three places (would be good if there were
a complete list somewhere):

- Application settings (common to all projects and workspaces)
These are for example the ICD2 settings (I think), the editor settings, the
recently loaded files lists.

- Workspace settings (common to all projects loaded into that workspace)
These are for example the chip model and configuration.

- Project settings (only for this one project)
These are the project files and possibly the compiler settings (I don't
build through MPLAB, so I don't really know that much here).

Anyway, whenever you load a project, MPLAB runs within a workspace. It can
be the default (then you never really know what workspace settings you
have, other than that they probably are the ones that were loaded last), or
it can be a specific one that you created by saving it with a specific name
in a specific location. Which is probably the sensible thing to do. Then
you have at least the chip configuration stored in that workspace file, and
you know that it's the right one.

That's probably why Olin loads workspace files -- that's where the
important stuff like the chip type is stored. Doesn't help you to load a
project file for a 16F666 into the default workspace where you have the
chip set to an 18F888 :)

It's probably helpful to keep in mind that settings get stored in (at
least) these three different places, even if you don't know exactly which
one gets stored where. And as a matter of rule, I think it's best to only
load workspace files. They then load automatically the project files that
are linked to them.

Workspace files are the .mcw files, project files are the .mcp files.

Gerhard

More... (looser matching)
- Last day of these posts
- In 2005 , 2006 only
- Today
- New search...