Path: cdrom.com!barrnet.net!decwrl!hookup!europa.eng.gtefsd.com!howland.reston.ans.net!EU.net!news.funet.fi!ngw!news.funet.fi!not-for-mail
From: larry wilmott <lwilmott@FPC.COM>
Newsgroups: alt.cd-rom
Subject: Re: BC++ 4.0 for MSWin 3.1 CD-ROM problems - Help
Date: 25 Feb 1994 22:48:40 +0200
Organization: FUNET-NGW
Lines: 47
Sender: daemon@news.funet.fi
Distribution: alt
Message-ID: <9402252032.AA28729@fpc.com>
Reply-To: larry wilmott <lwilmott@FPC.COM>
NNTP-Posting-Host: news.funet.fi
Return-Path: <@UCCVMA.UCOP.EDU,@CUNYVM.CUNY.EDU:lwilmott@FPC.COM>
Comments: To: CDROM-L@UCCVMA.BITNET, hunter@sd.e.mdso.vf.ge.com
To: CDROM-L Redistribution <lst-alt-cd-rom@NGW.FUNET.FI>

> 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++!!).
> ...
> > Thanks for any comments.
>
> --
> Bryan K. Hunter

First:

Check SYSTEM.INI for 2 entries:

device=D:\BC4\BIN\WINDPMI.386
device=D:\BC4\BIN\TDDEBUG.386

where D: is the CD-ROM.  Copy the files to C:\BC4\BIN and modify SYSTEM.INI
 accordingly.

Second:

Remove D:\BC4\BIN from your path.

Third:

Create a batch file like this:

set opath=%path%
set path=%path%;d:\bc4\bin
win
set path=%opath%
set opath=

Use it whenever you are going to use BC4.

Hope this helps.
Larry Wilmott
lwilmott@fpc.com