Forum Home
Press F1
Thread ID: 5937	2000-09-29 06:21:00	A: Drive Error Press F1 to resume	Guest (0)	Press F1

Post ID	Timestamp	Content	User
6524	2000-09-29 06:21:00	I'm sorry if this is a long explaination of my problem, I could have written more... Recently, (notibly about the same time as when I installed Office 97) my computer started checking A: (a 3.5 inch disk drive) for no apparent reason at what seemed to be reqular intervals. I knew that Fast Find from Office could do this, but checking under control panel, it seemed to only be configured to check c:, so I left it (i have since removed it - to no avail). At the time I did not have any disks available to put in the drive to remind Windows that the drive was empty. BUT when I did need to use a disk, I used one of the disks I always use, one that I could guarantee had no viruses on. The drive read the contents of the didk okay, but when I tried to copy a file that was 1.407 megs onto the disk with 1.44 megs free, the computer froze up when it got near the end of copying the file. I rebooted and tried another disk, and the computer froze again. Next time I booted up and put a disk in, the drive made a lot of screeching noises and then said that the disk was not formatted, it then said that for every disk I put in, along with a lot of screeching noises (I have tryed these disks on our other computers, with no problems). So I restarted the computer once more... This time on boot up, just after the computer runs off the amount of ram available, The following message came up: A: Drive Error Press F1 to resume I pressed F1 and the drive made alot of noise and said: Searching for boot record from floppy... Eventually the computer got into windows after not finding a boot record on A: Both in windows 98 or Dos the drive now gives errors, and the same messages appear at every bootup. I have run Mcafee VirusScan evaluation version (I installed it specifically because of this problem) with the latest virus DAT files (27/09/00) and it found no viruses. I have also checked Device Manager and it says there are no conflicts. This is all I have done to try and remedy this. It could be hardware failure, but considering our computer is only 15 months old, I wouldn't expect it. If anyone has any idea, cure, or theory as to this problem, PLEASE help, as the use of the Disk drive is important to my familys work.	Guest (0)
1