Announcement

Collapse
No announcement yet.

Resource file error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Resource file error

    Since I moved my PBDLL60 environment from C:\ to D:\, I can't compile resource files anymore.
    I've checked and modified all the necessary drive letters in PBEdit's option menu, but it did'nt help. Also checked the registry: everything OK.
    When using a DOS batch file for this job, a "file not found" error is reported. Has somebody experienced this phenomenon earlier?
    I've moved my PBDLL files using "cut & paste". Maybe there was some hidden file in the Bin directory, that I did'nt grab in this way?
    Everything else just works fine, including Win32.hlp, using F1 in the IDE. I'm rather desperate.

    ------------------
    mailto:Egbe[email protected][email protected]</A>
    www.basicguru.com/zijlema/

    [This message has been edited by Egbert Zijlema (edited March 16, 2001).]

    Egbert Zijlema, journalist and programmer (zijlema at basicguru dot eu)
    http://zijlema.basicguru.eu
    *** Opinions expressed here are not necessarily untrue ***

  • #2
    Have you change your PATH in AUTOEXEC.BAT?

    Peter.


    ------------------
    [email protected]
    [email protected]

    Comment


    • #3
      Is RC.EXE still in the path? since your BAT file fails too, this indicates something is missing somewhere!

      What is your batch file using/doing? The only "hidden" files would be the .GID files created by WINHLP32 when the help file(s) in the BIN directory are used. Losing these should not cause any problems since they will be recreated by WINHLP32 next time the HLP files are launched.

      Silly question, but I have to ask: Do your resource files include any absolute paths that need to be updated too? What about #include files and any other nested files?


      ------------------
      Lance
      PowerBASIC Support
      mailto:[email protected][email protected]</A>
      Lance
      mailto:[email protected]

      Comment


      • #4
        I rechecked all paths, including the one in AUTOEXEC.
        I cannot find the 'bug' or whatsoever. Here is the source of my .RC file. Exactly the same source compiled correctly when PBDLL was located on C:\. Now it does'nt. RC.EXE obviously cannot find the icons, although they are absolutely there and despite using absolute paths (which I don't do most of the time, because I'm compiling from the current directory).
        To play safe, I even re-installed PBDLL. Did'nt help.
        Code:
        #include "D:\PBDLL60\WINAPI\RESOURCE.H"
        
        #define ICON1 WM_USER + 1
        #define ICON2 WM_USER + 2
        #define ICON3 WM_USER + 3
        
        ICON1  ICON "D:\PBDLL60\SAMPLES\MSGBOX\EXIT.ICO"
        ICON2  ICON "D:\PBDLL60\SAMPLES\MSGBOX\FULLBIN.ICO"
        ICON3  ICON "D:\PBDLL60\SAMPLES\MSGBOX\EMPTYBIN.ICO"
        ------------------
        mailto:[email protected][email protected]</A>
        www.basicguru.com/zijlema/

        Egbert Zijlema, journalist and programmer (zijlema at basicguru dot eu)
        http://zijlema.basicguru.eu
        *** Opinions expressed here are not necessarily untrue ***

        Comment


        • #5
          Well folks,
          Where are you? As usual I had to bail myself out.
          By downloading another RC-compiler. The code in my previous posting, exactly the same, does compile with it.
          There are 2 possibilities: either the Microsoft thing that came with PBDLL is buggy or the other compiler understands my cripple code.


          ------------------
          mailto:[email protected][email protected]</A>
          www.basicguru.com/zijlema/

          [This message has been edited by Egbert Zijlema (edited March 16, 2001).]

          Egbert Zijlema, journalist and programmer (zijlema at basicguru dot eu)
          http://zijlema.basicguru.eu
          *** Opinions expressed here are not necessarily untrue ***

          Comment


          • #6
            Or something else. We'll let you know if we find out.

            ------------------
            Tom Hanlin
            PowerBASIC Staff

            Comment

            Working...
            X