Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: Microsoft Cobol Compiler v 2.20 Removal  (Read 4998 times)

0 Members and 1 Guest are viewing this topic.

logamuthu

    Topic Starter


    Rookie

    Microsoft Cobol Compiler v 2.20 Removal
    « on: October 18, 2013, 10:37:16 PM »
    In my Windows 7 PC Microsoft Cobol Compiler v 2.20 seems to be

    integrated. Whenever, in .cmd, I go to my C:\COBOL folder and type

    "COBOL" Microsoft Cobol Compiler v 2.20 loads automatically. But it

    gives lots of errors like "Source File Cannot be opened" although the

    required .cob file is in the same folder. I have been unable to get

    any help for Microsoft Cobol Compiler v 2.20 in the web except

    comments that Microsoft Cobol Compiler v 2.20 was written for DOS

    COBOL and has serious limitations and better to be replaced.

    But I am unable to remove Microsoft Cobol Compiler v 2.20 from my system

    through Control Panel. Revo Uninstaller does not list it. Regedit has

    no entries for "Microsoft Cobol Compiler". I got a better COBOL

    compiler - Cobol.rar from Mediafire and installed it in my C:\COBOL

    folder bot even now whenever, in .cmd, I go to my C:\COBOL folder and

    type "COBOL" Microsoft Cobol Compiler v 2.20 loads automatically.

    I need help to uninstall Microsoft Cobol Compiler v 2.20 from my

    system so that I can use Mediafire COBOL compiler.

    [recovering disk space, attachment deleted by admin]

    DaveLembke



      Sage
    • Thanked: 662
    • Certifications: List
    • Computer: Specs
    • Experience: Expert
    • OS: Windows 10
    Re: Microsoft Cobol Compiler v 2.20 Removal
    « Reply #1 on: October 19, 2013, 04:01:14 PM »
    I'd delete the entire Cobol folder and start fresh.

    It is not really installed, it is just there, and should be able to be deleted without any problems. Then create a new folder and place the compiler you want in the clean folder by itself to avoid any conflict and it should fix this.

    Only other thought I have on this is if the PATH variable has Cobol redirected to execute from another location. Look at SET from command line and see if Cobol is listed in the Path Variable ... more info here: http://www.lagmonster.org/docs/DOS7/z-path.html * If Cobol is found in the current directory it will not use the Path info, however if Cobol is not located where the command is executed from, it will hit the Path and if there is an entry it will trigger it to start from some other location as the path info indicates.

    Didnt think anyone worked with Cobol anymore. I havent touched it in over 20 years. I ended up getting it on a used 8088 that I bought at a yard sale around 1991.

    logamuthu

      Topic Starter


      Rookie

      Re: Microsoft Cobol Compiler v 2.20 Removal
      « Reply #2 on: October 20, 2013, 12:27:48 PM »
      Thank you Dave!

      I have tried deleting and creating new COBOL folder in C: drive and copying Mediafire COBOL Compiler (COBOL.RAR 3.83 MB) there - it did not prevent Microsoft Cobol Compiler v 2.20 from reappearing in .cmd window.

      Shall try your Path - Variable suggestion and revert to you.

      Thanx again for this only reply (yours) I have received so far from 4 forums I have posted this!

      Prof.Dr.K.Loga muthu krishnan,MBBS.,MS.,FRCS.,PhD(Neuro).,FRSM(London).,
      Senior Consultant Neurosurgeon,
      Chennai,
      India.

      E-Mail:[email protected]

      EMail addy removed to prevent SPAM.
      « Last Edit: October 21, 2013, 05:58:22 AM by patio »

      DaveLembke



        Sage
      • Thanked: 662
      • Certifications: List
      • Computer: Specs
      • Experience: Expert
      • OS: Windows 10
      Re: Microsoft Cobol Compiler v 2.20 Removal
      « Reply #3 on: October 23, 2013, 12:35:40 PM »
      One other trick you can try is rename the cobol.exe or cobol.com to cobol1. matching file extension to the original cobol that you want to run, not the microsoft one, and see if that works. This would require you to enter COBOL1 at the command prompt vs COBOL and should explicitly launch other than the microsoft cobol compiler 2.20. This should fix this if you cant track down or fix the issue with PATH.