Printable View
Hello,
despite my efforts to install PBP with MPLAB IDE under Windows Vista I have been unsuccesful.
Can anybody tell me or point me to the right way to do this?
I've tried changing the system PATH and installed the PBTools, but so far I cannot see the melabs tool tool suite in the "Set Language Tool Locations" window.
I will really appreciate your help.
I am running MPLAB 7.50, PBP 2.46a and Vista Bussiness.
Thanks in advance, Gabriel
i'm having the same problem..I've been hoping someone would post a response to your question. By chance have you found a resolution?
Thanks,
Sam
VISTA http://www.mister-e.org/Pics/ROFL
Will be probably good enough in 2077
Did you tried it with MicroCodeStudio?
Did you contact Melabs?
Sorry... i don't have Vista... still afraid of :eek: For now, i will suggest you to trash it, and reinstall XP.
Actually yes, I made it work. The problem is that I don't remember what I did.Quote:
Originally Posted by millersamsr
I believe I set it to run (MPLAB and PBPW) as WinXP compatible, but I don't remember what else I did. I will check my computer with Vista later today and if I remember what I did I will post it here (right now I am at the WinXP computer).
Gabriel
i don't know how much how much this will help ...
Quote:
Originally Posted by http://www.melabs.com/support/mplab.htm
Yes, I believe that is what I did.
Gabriel
gabrielg74 and mister_e,
I had already tried both of your suggestions, but to no avail. I'll be contacting both MELabs and Microchip for suggestions.
Thank you both,
Sam
I remember now, when I tried to run the bat file it just opened briefly a DOS window, but nothing seemed to happen. Then I run it as Admin and then it worked.
Gabriel
I tried that multiple times, but..here is what I did to finally get it to work. I'm not sure which things did it and which had no affect, so I'll post everything.
I set compatibility to win98 for all executables
I ran command prompt as administrator, then ran the bat file.
Thanks for your persistance.
Sam
Mister_e, you've given Vista a serious hard knock there. Wondering if you might be willing to "elaborate" a bit on your dislikes about it.Quote:
Originally Posted by mister_e
It's just my own opinion based on many post i saw here and there + blend mix of local people i know here. But like everything... you hear more about bad comments than good.
I don't like to use MicroSoft product within at least 1-2 years after their initial Official release date. But it's me.
I havent used Vista properly yet and have no intention of installing it on any of my PCs. In fact I think only one of my PCs would actually meet the required specification.
I have seen the glitzy interface on PCs in the shops but at the moment XP Pro does everything I want my PC to do.
I have used a Vista machine once when I was trying to sort out a friends email problems. The first hurdle I encountered was that I couldnt see "Run" anywhere on the start menu.
Flash of inspiration..."WindowsKey + R" rings up the Run dialogue box. Type "cmd" and got a command prompt. Great :)
Type "Telnet"
'Telnet' is not recognized as an internal or external command,
operable program or batch file.
At that point I went to the XP machine in the same room to use Telnet :(
I have seen reports that sevral of the programs that are important to me will not run on Vista so for the time being I am steering well clear of it.
I dont see the point in upgrading just for the sake of it
Hi Keith,
See this link about Telnet and Vista.
http://www.techronical.com/2006/10/05/
Best regards,
Luciano
Thanks LucianoQuote:
Originally Posted by Luciano
I actually saw that last week but that was a week after I needed it.
Microsoft actually seem to be making PCs more difficult to use for anything other than mainstream tasks. Its bad enough that a basic install of XP puts "pretty" views of control panel etc. First thing I do is switch to classic view so that I can see what I am looking for. LOL
I know that DOS is dead but the command line still has its uses when you are trying to find out why you are having internet problems etc using ping, tracert, ipconfig etc. especially when the help Wizards dont help !!!
Regards
Keith
I have just bought a new laptop with Vista 32 home premium. Finally got around to installing my pic stuff and all seems to be ok
Downloaded and installed latest MPLab.
Downloaded and installed latest Microcodestudio.
Installed my PBP compiler V2.46
Loaded an old project compiled it, loaded in to MPlab and programmed and confirmed a pic via my picstart plus programmer.
Never had to run anything as administrator. Not really sure why you are having problems.
Try un-installing everything, dowloading the latest versions and try again.
As for Vista - I have had no problems with it, its the best OS I have used yet. Only lost one program so far and a Vista update will be out in the fall for it.
sorry I cant help, but it 'should' work.
Good luck.
Vista?? EEEUUUUUURRRRRRRGHHHHHH What a load of junk. Does things it THINKS you want it to with no regard for what you ACTUALLY want to do.
FACT!! Did you know that at the current rate of take-up, it will take until late in 2009 for Vista to overtake sales of XP and then it will only be 54% of the market.
Vista has been a disaster for Microsoft sales wise. Most IT professionals I know have rejected ANY idea of installing it until it is proved to be more stable.
One classic was an error message stating "A Critical ERROR has occured - Windows Vista has succesfully installed on your computer"! I have seen this quite a few times when a few people I know ran out and bought the latest "must have" junk from the Seattle Screw Crew.
Steer clear is the best advice, UNLESS it's the Business Pro version. Stay with XP Pro, far more stable.
Has anyone had any luck getting MPLAB to recognise PBP under Vista64 bit ?
I'm making no progress with it at all :(
Setting the compatibility to Win98 stopped MPLAB from loading so I tried XP SP2 and still couldn't see the language pack.
For anyone interested there is an effective workaround to run 32bit XP apps inside the Vista 64 bit environment. Microsoft has a free Virtual PC download. You can install that and then install XP as a virtual 32 bit OS inside a shell. Microsoft do state that Virtual PC is "unsupported" in Vista Home and Premium but "unsupported" is not the same as "does not work" :)
Update: gnash, gnash - the software all works but Virtual PC does not pass thru USB connections and I've got a USB programmer.
I believe VMWare supports USB...it did a few versions back.
Sam
I copied the PBP plugin files into the ...\Microchip\MPASM Suite folder and the run the BAT file as Administrator, after that it was registered in MPLAB IDE.
Keep PICing... :D
Hi all,
Yeh, I am in the same boat as well.
New laptop, Vista Home Premium.
Ive installed from cd Microcode Studio Plus 2.3.0.0
The Complier (PBP 2.45), Assembler (MPASM) and Programmer (Epic 2.44) have all been setup in ... View/Compile and Program options.... area.
When I run the Microcode Studio Plus program I get this little error message popup.....
" List index out of bounds (11) "
and the program closes.
I run it a second time and it loads up ok,
so I open a *.bas file and try a complie (with the correct chip file eg: p16f876a)
Then I get THIS error popup.....
" Cannot create file run.bat. "
:confused:
ANY advice will be most welcome,
regards
Shaun Woods
Lucky me I still not have that Beautiful Vista here ;)
More than often, people solve most problem by raising their software privilege to Administrator (run as administrator).
http://www.optimizingpc.com/vista/co..._software.html
And it's more likely due to an older version as per Mecanique
http://www.mecanique.co.uk/code-studio/history.html
Thanks for your help mister_e.
As soon as I get Vista running again, yes it went haywire etc. reformat was needed.
Might consider installing XP methinks
cheers
Woodzy
I have MCS, & PBP in vista 32 home edition, installed as admin ( I think you are supposed to intall all that way), works fine. It is not running in compatibility mode. HTH
JS
Just an update fellas. Finally got all working ok on Vista. Yep admin and untick the files and folders as read only.
SO, after working away quite nicely for a time.... and after adding extra code for ADC, etc. this compilation/assembly error raises it ugly head........
Error[113] f:\!_Woods\plc_pbp245\pbppic18.lib 1165 : Symbol not previously defined (ROLLOVER)
Using.....
Microcode Studio Plus v2.3.0.0
MPASM v03.90
PicBasic Pro 2.45
PIC18F452
Any tips, hints, etc would be muchly appreciated.
If you need more info, please ask.
regards
Shaun Woods
Looks like you forgot to define a variable or you have misspeelled something in you code.
Thanks mackrackit,
Yeh I found the culprit. Using an include "int.bas" for a continous clock.
Ive underlined the problem symbols i think.....Code:'FILENAME : INT.BAS
'PROGRAM : INCLUE for continuous clock
'DATE : 01NOV2005
DEFINE INTHAND ROLLOVER
wsave var BYTE $020 SYSTEM
wsave1 var BYTE $0a0 SYSTEM
wsave2 var BYTE $120 SYSTEM
wsave3 var BYTE $1a0 SYSTEM
ssave var BYTE BANK0 SYSTEM
psave var BYTE BANK0 SYSTEM
i_hour var BYTE
i_minu var BYTE
i_sec var BYTE
i_tic var BYTE
GOTO AFTERINT 'Jump past interrupthandler
asm
rollover
;*****************************************************************************************
;*****************************************************************************************
;
; If you are using a PIC with 2K or less,
; you MUST unremarke the lines that follow.
;
; movwf wsave ;only for PICs with 2k or less
; swapf STATUS,w ;only for PICs with 2k or less
; clrf STATUS ;only for PICs with 2k or less
; movwf ssave ;only for PICs with 2k or less
; movf PCLATH,w ;only for PICs with 2k or less
; movwf psave ;only for PICs with 2k or less
;
;*****************************************************************************************
;*****************************************************************************************
; interrupcode follows here
movlw 0x58
movwf TMR1L
movlw 0x9e ;restart timer from ffff - 9e58 => 5Hz if using 4MHz
movwf TMR1H
decfsz _i_tic,f
goto slutint
incf _i_sec,f
movlw 5 ;5 = 1Hz if using 4MHz (change to 10 for 8MHz and so on)
movwf _i_tic
movf _i_sec,w
sublw 60
btfss STATUS,Z ;check for 60 sec
goto slutint ;no
clrf _i_sec ;yes
incf _i_minu,f
movf _i_minu,w
sublw 60
btfss STATUS,Z ;check for 60 minutes
goto slutint ;no
clrf _i_minu ;yes
incf _i_hour
movf _i_hour,w
sublw 24
btfss STATUS,Z ;check for 24 hours
goto slutint ;no
clrf _i_hour ;yes
slutint
bcf PIR1,0 ;zero tmr1 interrupt flag
;end of interruptcode
; restorecode follows here
movf psave,w ;restore
movwf PCLATH
swapf ssave,w
movwf STATUS
swapf wsave,f
swapf wsave,w
retfie
endasm
AFTERINT:
INTCON = %00000000 'all interrupts off
PIR1 = %00000000 'zero tmr1 interrupt flag
PIE1 = %00000001 'enable timer1 interrupt
TMR1L = $58
TMR1H = $9e
i_hour = 0
i_minu = 0
i_sec = 0
i_tic = 5 'this value should be the same as the value of line 8 in the ISR
T1CON = %00110001 'timer1 on, prescaler=1/8
INTCON = %11000000 'interrupt on
'-----------------------------------------------------------------------------------------
fits in my main program like so.....
Cant understand getting a symbol not defined error when it defines it first line.Code:DEFIN: clear
DEFINE OSC 4 'set to 4MHz oscill@@
INCLUDE "int.bas"
INCLUDE "modedefs.bas"
blah....
blah....
blah....
gosub TICK
blah....
blah....
blah....
TICK: if i_sec.0 <> OSCbit then
return
endif
'etc.
cheers
Woodzy
Mystery solved ! :D
Thanks to a four year old post .......
http://www.picbasic.co.uk/forum/showthread.php?t=1090
dissimilar caps. Funny how mpasm is case sensitive.
A BBIIGG thanks to the forum mods keepin old threads alive. They are just as relevent today.
cheers
Woodzy