🚀 go-pugleaf

             I have a question concerning STACKER and BORLAND C++ FOR WINDOWS.
        I'm not sure if this is the right place to ask this question, but my 
        question is as follows.  I have run the installation program for
        STACKER on my hard drive that creates the main boot drive D: and the
        STACKER compressed drive C:.  My version of BORLAND C++ FOR WINDOWS was
        compressed on the STACKER compressed drive C:.  I try to use the 
        debugger that comes with the BORLAND package and I receive an error
        telling me that the file WINDEBUG.DLL can not be open.  The DLL is a 
        compressed format for the C++ Link Library (*.LIB).  I know that the
        STACKER can not handle compressed files.  I would like to know if any
        one using BORLAND C++ FOR WINDOWS has run into this problem.  I have 
        noticed that I can not open any of the DLL files that are currently 
        located on the STACKER compressed drive.  If any one has any solutions
        to this problem I would appreciate some answers.  Here are some of the 
        solutions that I have come up with so far.
        1.  Decrease the size of the STACKER compressed drive and increase the
            size of the uncompress drive moving the entire BORLAND C++ FOR
            WINDOWS to the uncompressed drive.  Problems that I have found in
            this solution is that I would not be getting as much disk space out 
            of my stacker drive.
        2.  This solution follows the same as the first, but opposed to moving
            the entire BORLAND C++ FOR WINDOWS to the uncompressed drive only
            move my DLL files to the uncompressed drive.  Questions and
            problems that have surfaced from this solution are 
               a) How do I redirect my pointers in BORLAND C++ to point at the
                  DLL files on the uncompressed drive.  Examples being the 
                  WINDEBUG.DLL.
               b) Are there any other DLL files that I would need to change
                  points to besides the WINDEBUG.DLL?  If so what are the files
                  and how would I set the pointers in BORLAND C++ to point to
                  the file currently located on the D: drive?
               c) A problem that I see occuring is that anytime I create a 
                  DLL file I would have to create it on the D: drive which 
                  means that I would have to have some space allocated for
                  DLL programs.  How much space would I need?
        3.  This solution involves changing the compressed DLLs to 
            uncompressed LIBs.  Changing all the active calls to DLL programs
            to LIB programs.  My question then surfaces how do I make the
            changes in the BORLAND C++ to tell it to look at the LIB file 
            instead of the DLL file?  Problems that I see is that the LIB
            files would take up more room on my stacker drive than the DLL's
            and I would not be able to use the DLL on the stacker drive.
        4.  The solution that I am looking for is a solution that would
            allow me to have BORLAND C++ FOR WINDOWS running on the STACKER
            compressed drive C: using the DLL files.
        Other questions that have arose not dealing with the solution are
        1.  Is there any way I could create the WINDEBUG file (DLL or LIB) 
            from the stacker drive with out having to do a complete reinstall 
            of the BORLAND C++?
        2.  If I need to move to the uncompressed drive would there be any
            problem moving the DLL files from the compressed to the
            uncompressed drive?  Would I still be unable to use the DLL files
            when moved from the compressed drive?