Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!ub!ubvmsd.cc.buffalo.edu!v056ped5
From: v056ped5@ubvmsd.cc.buffalo.edu (Brian M McNamara)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Turbo Profiler bugs reported to Borland
Message-ID: <43272@eerie.acsu.Buffalo.EDU>
Date: 30 Oct 90 06:43:43 GMT
References: <16799@shlump.nac.dec.com>
Sender: news@acsu.Buffalo.EDU
Reply-To: v056ped5@ubvmsd.cc.buffalo.edu
Organization: University at Buffalo
Lines: 22
Nntp-Posting-Host: ubvmsd.cc.buffalo.edu
News-Software: VAX/VMS VNEWS 1.3-4.3

In article <16799@shlump.nac.dec.com>, routley@tle.enet.dec.com writes...
>I have submitted the following Turbo Profiler bug report to Borland.
>          1. Difficulty Aborting Print to Non-existant Printer
>             When (accidentally) trying to print to a non-
>             existant printer, it is extremely difficult to abort
>             the print operation.
> 
	[...lots deleted...]

This is a problem I have noticed with many programs. It appears to be
more of a DOS problem in the way that the computer interprets the
command to print in relation to the (abort,ignore,retry) thing. I 
can't remember how many times I have lost programming work, word 
processing work, even game progress, to this problem which only can
be solved by rebooting.

I have also seen this problem occur with some programs when trying to access
a non-existent or not ready drive.

Does anyone have any suggestions?

Brian