Ticket #144 (closed defect: wontfix)
Floppy disk access when erasing recycle bin.
| Reported by: | Overwriter | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Eraser 6.0 |
| Component: | Core | Version: | 6.0.3.847 |
| Keywords: | floppy seek | Cc: | |
| Processor Architecture: | Blocked By: | ||
| Blocking: | Operating System: |
Description
XP Pro SP3 .net 3.5
Eraser V6 Beta 3
When I right click on the recycle bin and select erase, eraser tries to access my floppy disk for some reason.
Should this be happening ?
Blocking
| Id | Summary | Milestone |
|---|---|---|
| #144 | └ Floppy disk access when erasing recycle bin. | Eraser 6.0 |
Blocked by
| Id | Summary | Milestone |
|---|---|---|
| #144 | └ Floppy disk access when erasing recycle bin. | Eraser 6.0 |
Change History
comment:1 Changed 4 years ago by Joel
- Status changed from new to pending
- Keywords floppy seek added
- Version set to 6.0.3.847
- Milestone set to Eraser 6.0
comment:2 Changed 4 years ago by Overwriter
- Status changed from pending to new
Oh there you go giving me those tough choices again ! A bit like the HTML folder thing !
I guess with floppy drives dying out someone is going to use the “A” drive for something else that may have a recycle bin on it.
Is there no way to silently check to see if the A drive is a floppy drive or not ? Would it be possible to tell from the system hardware properties ?
I guess if it was known to be a floppy drive then Eraser wouldn’t need to check for a recycle bin on it. But then again someone may have strangely put one on there. AARRGGHHHH !
OK Joel leave it as it is, sorry !
mmm. It should. Because Eraser won't assume that your drives A and B do not have a recycle bin. I'm not sure how valid an assumption will be that drives A and B don't have a recycle bin. I know some people who would mount ZIP disks on drive B and they may actually have recycle bins in them.
What do you think? Should we make the assumption?