2.60 + MCSP problems

[HenrikOlsson]

Hi,
I've finally received my copy of 2.60 but I'm having some trouble making it work with MicroCodeStudioPlus.

I installed it to C:\Program\PBP260, launched MCSP, went to Compile and Program Options and pointed it to the above folder. Help -> About says Compiler not installed....

I deleted the PBP260 folder, moved my old PBP folder to another drive and reinstalled 2.60 in C:\PBP (the default location), launched MCSP but this time let it find PBP automatically - which it did. Help -> About still says Compiler not installed though.

I tried compiling a program anyway but then I got a message saying it found MPASM in different folder than what it expected and that it (MPASM) needs to be in the default PBP folder for PBP v2.30 and less - I don't even own a version that old. It gives me the option to move the required files automatically but I feel something is wrong here so I haven't tried it.

I have MPLAB 8.36 installed and MELABS support site says:

PBP 2.60 or later is required for a successful compile in MPLAB 8.20 and later.Which I interpret as MPLAB 8.36 should be fine with PBP v2.60.


I switched from MPASM to PM for the assembler and tried to compile a program for a 16F88 but got an Fatal: Out Of Error (pbpw.exe)

For the record this is the code for the F88 I tried compiling:

Start:
Pause 10
Goto Start
END

Has anyone experienced this before and/or can point me in the right direction?

[Acetronics2]

Hi, Henrik

I had some little ( compared to yours ) surprises with PBP2.60 installation.

I took the following lessons:

1) place MPLAB and PBP into their DEFAULT locations ...
2) Do not use MCS+ AND MPLAB for the moment ( I got "garbage" into MPLAB after having used MCS ...) so, wait and see ...
3) Point MCS+ MANUALLY to your PBP2.60 folder ... Auto detection is somewhat fuzzy if you had installed multiple PBP into different locations ...

Now, There's the langage tool to be modified somewhat in MPLAB. Download RELEVANT instructions from Melabs ...


I did not open MCS+ from the time I had trouble ... and MPLAB works like a charm !!!

Coincidence ??? I do not want to know !!!

Begin by removing MPLAB 8.36 and PBP from the "add/remove programs" panel of Windows ( you also can make some room with older MPLAB versions ...)

Alain

[HenrikOlsson]

Thanks for the reply Alain,
I'm not really using MPLAB, I only have it installed to get MPASM so the language pack etc shouldn't matter since I'm not running PBP from inside MPLAB, should it?

Both MPLAB and PBP are installed to their default locations, C:\PBP and C:\Program\Microchip\MPASM Suite. They weren't at first since it has always worked before but I removed and reinstalled to their default loactions so now they are. And I have pointed MSC+ manually to BOTH the PBP folder and the MPASMSuite folder but it's still the same.

/Henrik.

PS. C:\Program is the default on Swedish WinXP while it is C:\Program Files on English versions.

[Darrel Taylor]

Do you also get an NTVDM error?

See the images ...
http://www.pbpgroup.com/files/MCS_Error/MCS_Error.htm

Notice the second and forth images.
<br>

[HenrikOlsson]

Hi Darrel,
No, as of yet I haven't. I get exactly what you have in the 2nd and 4th screenshot. And, as I said I've pointed MCS+ to the PBP and MPASM folders manually.

Thanks!
/Henrik.

[Darrel Taylor]

OK, that's good, I think...

The problem comes from not being able to run programs in a 16-bit Virtual Machine.
And there seems to be several reasons why it can happen.

Here are two tests recommended by Microsoft (http://support.microsoft.com/kb/220155) ...

Open the run command line (Start | Run) or WinLogo+R.
Enter the command sysedit.

If it does not start the system configuration utility ... it may still be an NTVDM error.

If it does start, try to open edit.com from the Run command line.

If it can not open the editor, it may be a Windows on Windows problem.<hr>
In my case, when I took those images, I had a problem with one of my video cards, and the driver was causing problems.

After replacing the video card and installing the new driver, the problem magically disappeared. But there can be many causes.

I had 2.50 at the time, but it's a Windows/MCS problem, not a PBP problem.
You can still compile from the command line or with a batch file.
(As long as there isn't an associated .pif file).
<br>

[HenrikOlsson]

Hi Darrel,
Both the System Editor and the edit.com starts fine from the Run command line.
"Nothing" have changed on the computer except installing v2.60 and there's nothing strange in the device manager.

Crap, first a 5 week waiting time to get 2.60 and now this....guess I'll have to resort to the old command line compile then. I haven't tried un/reinstalling MCS+ yet, I'll do that and I'll also try on another computer tomorrow.

/Henrik.

[Acetronics2]

Hi, Henrik

Stupid question, I know ... but ...

Is yout Win XP up to date ???


BTW ... why not launch the PBRegister.bat file ( in the PBP folder ) ???

fixed some issues for me !

Alain

[HenrikOlsson]

Hi Alian,
Yes XP is up to date - it worked fine with 2.47 but after installing 2.60 it's a no-go.

I don't seem to have a file called PBRegister.bat, only .bat file I've got in the PBP directory is PBPMPLAB.bat which is supposed to be used when running PBP within MPLAB - which I don't.

/Henrik.

[Acetronics2]

Strange ...

Here it is.

Alain

[HenrikOlsson]

Thanks Alain,
Where did you find that one? It's trying register Suite_PicBasicPro.dll and Suite_PicBasic.dll, two more files which I don't have on my system... Aargh...

[Acetronics2]

Damn ....

Really very bad crack Download !!! ... look for a better one !!!

Noooooo, I'm Joking !!!

I do not remember where, but this file was available from the Melabs site ...

Alain

[HenrikOlsson]

Hi,
I just tried on two other computers and it works fine on both so it must be something with the particular machine.... In an effort to solve it I uninstalled MCSP but now I can't reinstall it from the CD. It says it can't decompress the neccassary files. I'm really not up for a reinstall of this machine :-(

[mackrackit]

You said XP is up to date. What service pack are you up to?

[HenrikOlsson]

Hi,
I'm running SP3.