View Single Post
  #57  
Old October 22nd 09, 02:17 AM posted to microsoft.public.win98.gen_discussion,microsoft.public.win98.performance
PCR
External Usenet User
 
Posts: 4,396
Default CD-R erratically detected

J. P. Gilliver (John) wrote:
In message , PCR
writes:
J. P. Gilliver (John) wrote:

[]
While looking, it rattles the floppy drive before it "finds" the
writer (from within b4f, that is).


http://support.microsoft.com/?kbid=216752
Floppy Disk Drive Is Active When Opening or Saving Files
............Quote..................
To resolve this issue, change the command line reference in the
Properties of the shortcut, or delete the shortcut:

(1) Click Start, point to Find, and then click Files Or Folders.


Assuming this means the shortcut via which we start Burn4free, I know
where that is, as it's on the desktop.


Yea, look in that one & also in any in the folder(s) mentioned in its
Target field or any folders to do with the app..

[]
(4) Delete any reference to drive A or drive B on the Command
box or Working section, and then click OK. For example,
if the command line reads a:\edit.com, change the line to read
edit.com.

[]
Sort the Find box by folder. Look especially at .lnk's & .pif's in
folder(s) that pertain to burn4free & any in "C:\Windows\Recent". You


I don't think there will be any such reference, but I will certainly
look; thanks for the tip.


You are welcome.


may add a search for .pif's by adding ".pif" in the Named box,
separated by a comma from ".lnk".. Look in their Program tab. Delete
any .pif's in "C:\Windows\PIF".


I hadn't thought of .pifs either. (Aren't they just for DOS prog.s?)
Why delete the ones in ..\PIF; sounds like a good place for them!


All right. Maybe don't delete them all, just any mentioning A:\ or
B:\ -- & inform us of any others. (I have none in there.)

A complex Windows app may have DOS commands & .pif's in its folder(s).
(I don't have or know Burn4Free.)

C:\Windows\PIF\ is used to hold .pif's that Windows creates when they
cannot be put anywhere else. A .pif (shortcut to a DOS command) is
created when a DOS command is clicked to execute. Normally, the .pif
will be put into the folder of the command that is clicked. I suppose if
one is clicked on a write-protected A:\drive, Windows might put the .pif
into
C:\Windows\PIF\.


It isn't the _drive_ that's not being detected - that always shows
up in explorer; it's only the fact that there's a blank disc in it
that is so often missed.

Any ideas what's causing it, and what will improve it?


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR