Sorry to follow up on my own post - but I forgot to mention that I had
installed the IDE on my HardDisk .. this is the intermediate installation
option and runs only the Compiler etc from the CD.

ALso, I forgot to mention that you need to check the *.ini files and copy
some files from the CD to the directory on your HD and change the references.

e.g.:
 in system.ini:
  device=C:\BC4\BIN\WINDPMI.386
  device=C:\BC4\BIN\TDDEBUG.386

and the following is the listing for my c:\BC4\BIN

   32rtm.exe*     borhelp.dll*   dpmi32vm.ovl*  implib.exe*    turboc.cfg*
   bcc32.cfg*     borl2msg.dll*  epsilon.ckb*   internal.ckb*  windpmi.386*
   bcconfig.bcw*  brc.exe*       grep.com*      keymapr.exe*   worked1.dll*
   bcroot.inc*    brc32.exe*     grep2msg.dll*  locale.bll*    worked2.dll*
   bcw.exe*       brcc.exe*      hc.bat*        rc.exe*        worked3.dll*
   bcwdbk16.dll*  brcc32.exe*    hc31.err*      rc2msg.dll*    worked4.dll*
   bcwdbv16.dll*  brcwin.dll*    hc31.exe*      rcpp.err*      worked5.dll*
   bcwdef.bcw*    brief.ckb*     hc312msg.dll*  rcpp.exe*      worklib1.dll*
   bcwdef.dsw*    c.tok*         idebid.dll*    rlink32.dll*   worklib2.dll*
   bcwimprt.dll*  c32.tok*       idecrtl.dll*   rtm.exe*       workop32.dos*
   bcwobj.dll*    capdos.exe*    ideedit.dll*   tasm2msg.dll*  workop32.w32*
   bcwpages.dll*  capdos.pif*    idekbd.dll*    tbrowser.dll*  workopt.dos*
   bcwprj.dll*    classic.ckb*   ideowl.dll*    tddebug.386*   workopt.w32*
   bcwres.dll*    cm.dll*        idepane.dll*   tdw.ckb*       workres.dll*
   bcws16.dll*    cmcore.dll*    idewin.dll*    tlib.exe*      workshop.exe*
   bcws32.exe*    codegen.dll*   impdef.exe*    tlink.cfg*
   bhbc4.hdx*     dpmi16bi.ovl*  impl2msg.dll*  tlink32.cfg*

Hope this helps!


sundaram@egr.msu.edu (Divya Sundaram) writes:

>The way to get around this is to:

> (a) remove the line D:\BORLANDC\BIN (where D: is your
>  CDROM drive) from your Autoexec.bat.

> (b) if you intend to run BC++ 4.0 then run a batch file that
>  adds the directory to the path

> (c) in the program manager's BC++ group, look at the
>  "properties" of all the items in there ... many of
>  them contain references to the D:. You may want to
>  modify the executables - i.e. the IDE, and debugger
>  etc .. not the Help files (the help files use the
>  winhelp.exe program and use the CDROM help files as
>  arguments).


>hunter@sde.mdso.vf.ge.com (Hunter Bryan K) writes:

>>I did this and played around with it a little (not having much time or
>>ambition to really get into the nitty gritty of it all) then decided to exit
>>windows.  Later I restarted windows (without the BC++ CD-ROM in the drive)
>>and was amazed to get an error from windows telling me that the CD-ROM
>>is not responding and it then refused to start windows.  I got the familiar
>>Abort, Retry, Cancel? prompt.  This continued until I place the BC++ CD in
>>the drive (but I didn't want to use BC++!!).

>>I followed the installation instructions to a T (they're basically idiot
>>proof).  Apparently, the installation routine binds the *.ini files for windows
>>so closely to the CD-ROM that you have to have it installed to even start
>>windows, regardless if you're interested in launching BC++.

>>Has anyone else had this problem?  I'm going to try it again this weekend,
>>I really haven't had enough time since I first tried it to try again.  Did
>>I miss something from the instructions?

>>If I can't get it to work tonight, I'll call the tech support.  Hopefully,
>>I just made a stupid mistake (I do, on occasion, make mistakes. I remember
>>about 10 years ago, I made a mistake then, gee it's been that long? :)
>>I'd rather not call the tech support unless I know that I'm not messing up
>>(don't want to sound like an idiot).

>>Thanks for any comments.

>>--
>>Bryan K. Hunter                               hunter@acc.vf.ge.com
>>Associate Software Design Engineer
>>Information Systems & Technologies, Martin Marietta Corporation
>>King of Prussia, Pa
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>"I'm not a software engineer, but I play one at work" - me

>><The opinions expressed above do not reflect those of my employer>

sundaram@egr.msu.edu (Divya Sundaram) writes:

>The way to get around this is to:

...
One other thing that would be advisable, would be to copy
the 2 device drivers that Windows attempts to load from
the CD-ROM into your BCC 4 directory and edit SYSTEM.INI
to reflect the new locations of WINDPMI.386 and TDDEBUG.386.
This "feature" is documented, but not too well.

The way to get around this is to:

 (a) remove the line D:\BORLANDC\BIN (where D: is your
  CDROM drive) from your Autoexec.bat.

 (b) if you intend to run BC++ 4.0 then run a batch file that
  adds the directory to the path

 (c) in the program manager's BC++ group, look at the
  "properties" of all the items in there ... many of
  them contain references to the D:. You may want to
  modify the executables - i.e. the IDE, and debugger
  etc .. not the Help files (the help files use the
  winhelp.exe program and use the CDROM help files as
  arguments).


hunter@sde.mdso.vf.ge.com (Hunter Bryan K) writes:

>I did this and played around with it a little (not having much time or
>ambition to really get into the nitty gritty of it all) then decided to exit
>windows.  Later I restarted windows (without the BC++ CD-ROM in the drive)
>and was amazed to get an error from windows telling me that the CD-ROM
>is not responding and it then refused to start windows.  I got the familiar
>Abort, Retry, Cancel? prompt.  This continued until I place the BC++ CD in
>the drive (but I didn't want to use BC++!!).

>I followed the installation instructions to a T (they're basically idiot
>proof).  Apparently, the installation routine binds the *.ini files for windows
>so closely to the CD-ROM that you have to have it installed to even start
>windows, regardless if you're interested in launching BC++.

>Has anyone else had this problem?  I'm going to try it again this weekend,
>I really haven't had enough time since I first tried it to try again.  Did
>I miss something from the instructions?

>If I can't get it to work tonight, I'll call the tech support.  Hopefully,
>I just made a stupid mistake (I do, on occasion, make mistakes. I remember
>about 10 years ago, I made a mistake then, gee it's been that long? :)
>I'd rather not call the tech support unless I know that I'm not messing up
>(don't want to sound like an idiot).

>Thanks for any comments.

>--
>Bryan K. Hunter                               hunter@acc.vf.ge.com
>Associate Software Design Engineer
>Information Systems & Technologies, Martin Marietta Corporation
>King of Prussia, Pa
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>"I'm not a software engineer, but I play one at work" - me

><The opinions expressed above do not reflect those of my employer>

Hunter Bryan K (hunter@sde.mdso.vf.ge.com) wrote:
:>>I recently received my Borland C++ version 4.0 CD-ROM and installed
:>>it for MS Windoze 3.1.  Because I don't feel like eating up about
:>>80MB of hard drive space I decided to do a minimal install (just install
:>>those files needed to launch it from the desktop with the CD-ROM in place).

:>>I did this and played around with it a little (not having much time or
:>>ambition to really get into the nitty gritty of it all) then decided to exit
:>>windows.  Later I restarted windows (without the BC++ CD-ROM in the drive)
:>>and was amazed to get an error from windows telling me that the CD-ROM
:>>is not responding and it then refused to start windows.  I got the familiar
:>>Abort, Retry, Cancel? prompt.  This continued until I place the BC++ CD in
:>>the drive (but I didn't want to use BC++!!).

:>>I followed the installation instructions to a T (they're basically idiot
:>>proof).  Apparently, the installation routine binds the *.ini files for windows
:>>so closely to the CD-ROM that you have to have it installed to even start
:>>windows, regardless if you're interested in launching BC++.

:>>Has anyone else had this problem?  I'm going to try it again this weekend,
:>>I really haven't had enough time since I first tried it to try again.  Did
:>>I miss something from the instructions?

:>>If I can't get it to work tonight, I'll call the tech support.  Hopefully,
:>>I just made a stupid mistake (I do, on occasion, make mistakes. I remember
:>>about 10 years ago, I made a mistake then, gee it's been that long? :)
:>>I'd rather not call the tech support unless I know that I'm not messing up
:>>(don't want to sound like an idiot).

:>>Thanks for any comments.

:>>--
:>>Bryan K. Hunter                               hunter@acc.vf.ge.com
:>>Associate Software Design Engineer
:>>Information Systems & Technologies, Martin Marietta Corporation
:>>King of Prussia, Pa
:>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:>>"I'm not a software engineer, but I play one at work" - me

:>><The opinions expressed above do not reflect those of my employer>

--
--
---------------------
Steve Harrold   swh@cup.hp.com
    HPG200/11
    (408) 447-5580
---------------------

I recently received my Borland C++ version 4.0 CD-ROM and installed
it for MS Windoze 3.1.  Because I don't feel like eating up about
80MB of hard drive space I decided to do a minimal install (just install
those files needed to launch it from the desktop with the CD-ROM in place).

I did this and played around with it a little (not having much time or
ambition to really get into the nitty gritty of it all) then decided to exit
windows.  Later I restarted windows (without the BC++ CD-ROM in the drive)
and was amazed to get an error from windows telling me that the CD-ROM
is not responding and it then refused to start windows.  I got the familiar
Abort, Retry, Cancel? prompt.  This continued until I place the BC++ CD in
the drive (but I didn't want to use BC++!!).

I followed the installation instructions to a T (they're basically idiot
proof).  Apparently, the installation routine binds the *.ini files for windows
so closely to the CD-ROM that you have to have it installed to even start
windows, regardless if you're interested in launching BC++.

Has anyone else had this problem?  I'm going to try it again this weekend,
I really haven't had enough time since I first tried it to try again.  Did
I miss something from the instructions?

If I can't get it to work tonight, I'll call the tech support.  Hopefully,
I just made a stupid mistake (I do, on occasion, make mistakes. I remember
about 10 years ago, I made a mistake then, gee it's been that long? :)
I'd rather not call the tech support unless I know that I'm not messing up
(don't want to sound like an idiot).

Thanks for any comments.

--
Bryan K. Hunter                               hunter@acc.vf.ge.com
Associate Software Design Engineer
Information Systems & Technologies, Martin Marietta Corporation
King of Prussia, Pa
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"I'm not a software engineer, but I play one at work" - me

<The opinions expressed above do not reflect those of my employer>