Yes, would like it changed, or have some way of determining the rejected files. However, the odd thing is that when you re-send a file that's been auto-deleted from the queue, say due to card full situation, you get an overwrite prompt. Why is this, if indeed the files were deleted from the queue? Tim -----Original Message----- From: bookport-bounce@xxxxxxxxxxxxx [mailto:bookport-bounce@xxxxxxxxxxxxx]On Behalf Of ROB MEREDITH Sent: Friday, 16 April 2004 11:36 PM To: bookport@xxxxxxxxxxxxx Subject: [bookport] Re: Possible bug Angie: It appears that your machine is not contrary. Unique perhaps, but not = contrary! Seriously, we delete all queued files when there is an error during the = send process. The primary reason is because it is possible to queue files = which will never go to the device. Perhaps for example, a user has a 128 = MB card, and they queue a 140 MB MP3 file. If we didn't delete all queued = files, they would be asked every time they connect, only to get an error. = Of course, they could use Brows or Delete if they wanted to in this = situation. I realize that this is a somewhat liberal solution to a problem that some = may never have, but it avoids stressing beginners or casual users if it = should occur. So, I ask of all of you, should an error during sending = queued files clear the queue? I can easily change this for the next = release if most people want it changed. Rob Meredith >>> matneyar@xxxxxxx 04/16/04 03:04AM >>> OK, Has this happened to anyone else? I had cued several files from web pages. Unfortunately, I forgot my card = was full. When I tried to send the files, I was reminded of this fact. I = deleted a bunch of stuff, expecting to be able to send the files then. = But,=20 Unfortunately, the cue was then empty! The files were gone! This wouldn't be such a big deal if they hadn't been web pages. Is this a pattern, or is this unique to my own little contrary machine? = <grin> Angie