Quote Originally Posted by mister_e View Post
comment ALL CONFIG lines in your c:\pbp\xyz.INC file

Code:
;****************************************************************
        NOLIST
    ifdef PM_USED
        LIST
        "Error: PM does not support this device.  Use MPASM."
        NOLIST
    else
        LIST
        LIST p = 18F4550, r = dec, w = -311, w = -230, f = inhx32
        INCLUDE "P18F4550.INC"	; MPASM  Header
        ;__CONFIG    _CONFIG1L, _PLLDIV_5_1L & _CPUDIV_OSC1_PLL2_1L & _USBDIV_2_1L
        ;__CONFIG    _CONFIG1H, _FOSC_HSPLL_HS_1H
        ;__CONFIG    _CONFIG2H, _WDT_ON_2H & _WDTPS_512_2H
        ;__CONFIG    _CONFIG3H, _PBADEN_OFF_3H
        ;__CONFIG    _CONFIG4L, _LVP_OFF_4L & _ICPRT_OFF_4L & _XINST_OFF_4L
        NOLIST
    endif
        LIST
EEPROM_START	EQU	0F00000h
BLOCK_SIZE	EQU	32
This is weird, totally crazy

When I comment those lines, I can see that they are commented, but when I compile USBDemo.pbp it produces the same errors (118) and when I then take a look at that 18F4550.INC file again, the comment marks are gone

Then I thought that I shall make a small experiment. From file properties I changed it to read-only and the tried to compile USBDemo.pbp... The first thing that happens is "save as" 18F4550. Ok, now I now that PBP does write it over again and again. Next I unchecked the read-only feature and compiled USBDemo.pbp, et voila, for the very first time it compiled without errors

What did happen? Why do we have to go via read-only ???? to solve such a persistent problem... incredible... Can you explain this? Can you??? If you can , please do... Thank you :-)

I burned it to PIC and did not yet test anything else than plug and unplug it for several times and I'm really glad that the USB port is still alive, that is for the very first time in my USB history... well, DT's hex with my config was also working, but that is another story...

I will try the communication to my PC tomorrow.... Not too much sweet at once...

I'm glad at this point, very glad... Thank you Steve!

PS. What if such errors (118) pops up again at some stage? It's kind of difficult to believe that the aid is "go via read-only"?... ???