BlackBird
asked on
Can't access floppy disk
null
What motherboard and BIOS are you using. There are a few older MB/BIOS combinations which were manufactured before Win95 was released which have problems with the floppy controller. I had one myself on a Pentium MB with AMI BIOS. I was finally able to get an updated BIOS and it fixed the problem. If it's a name brand system, you might have some luck on their web site.
Blackbird, try renaming your config.sys and autoexec.bat file to config.xxx and autoexec.xxx respectively, then go into control panel, system, device manager, click the "+" sign to expand the floppy disk controller, highlight the entry, click remove and then restart Win95. Let me know what occurs.
Dennis
Dennis
ASKER
The motherboard is a TMC (Taiwan Mycomputer Corp.) circa 1993 with an AMI 486/33 BIOS. I have alrady done a deletion of the floppy controller from Device Manager and indeed upon restarting Windows, it detects new hardware (FDC) & installs the support for it but I still get the same symptoms.
BlackBird,
Another possibility...
Try booting in safe mode. Go to device manager. Check to see if there are multiple entrys for floppy drive. Although I can't explain why, I have seen this happen several times.
Ralph
Another possibility...
Try booting in safe mode. Go to device manager. Check to see if there are multiple entrys for floppy drive. Although I can't explain why, I have seen this happen several times.
Ralph
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Smeebud,
For the most part, I had tried everything you suggested to no avail. This problem was on a friend's machine that I didn't have frequent access to but subsequent to starting this question, I returned to add a network adapter to the machine. At this time I found that access to the CDROM was unavailable! Checking device manager (for all devices) showed only one thing, an exclamation mark on the CDROM controller. All devices showed no address, IRQ or DMA conflicts! (this includes the CDROM controller). Plowing ahead with the NIC installation and noting my choices for system resources I found that I needed to re-assign both the sound card & the CDROM controller. The sound card was at address 0220H, IRQ 10 & DMA 3 and I only changed the IRQ to 9 (2). The CDROM controller was at address 0300H, IRQ 11 & DMA 11 and I only changed the IRQ to 10. The NIC was then installed using address 0310H, IRQ 11 & DMA 5. At this point everything (including the floppy disks, both A & B) worked fine!!! My assummption is that there was indeed some resource conflict but Win95 just wasn't telling me about it (even though per the hardware manuals & physical examination of the hardware there were no conflicts). I still am not sure what really cleared the problem and if you have a possible explanation for it & would care to take the time, please email me at BEDearth@aol.com. Thanks for your input.
Bruce
PS, after the above, the user stated that printing from a DOS program speeded up tremendously.
For the most part, I had tried everything you suggested to no avail. This problem was on a friend's machine that I didn't have frequent access to but subsequent to starting this question, I returned to add a network adapter to the machine. At this time I found that access to the CDROM was unavailable! Checking device manager (for all devices) showed only one thing, an exclamation mark on the CDROM controller. All devices showed no address, IRQ or DMA conflicts! (this includes the CDROM controller). Plowing ahead with the NIC installation and noting my choices for system resources I found that I needed to re-assign both the sound card & the CDROM controller. The sound card was at address 0220H, IRQ 10 & DMA 3 and I only changed the IRQ to 9 (2). The CDROM controller was at address 0300H, IRQ 11 & DMA 11 and I only changed the IRQ to 10. The NIC was then installed using address 0310H, IRQ 11 & DMA 5. At this point everything (including the floppy disks, both A & B) worked fine!!! My assummption is that there was indeed some resource conflict but Win95 just wasn't telling me about it (even though per the hardware manuals & physical examination of the hardware there were no conflicts). I still am not sure what really cleared the problem and if you have a possible explanation for it & would care to take the time, please email me at BEDearth@aol.com. Thanks for your input.
Bruce
PS, after the above, the user stated that printing from a DOS program speeded up tremendously.
Blackbird,
Are you using doublespace or some other disk doubling utility? I have seen it cause mysterious floppy problems in the past. Might consider removing it... which probably means a total reformat and re-install of Win95. Good Luck.
Are you using doublespace or some other disk doubling utility? I have seen it cause mysterious floppy problems in the past. Might consider removing it... which probably means a total reformat and re-install of Win95. Good Luck.
I wish I could tell you what caused it.
Not being there makes it difficult.
95 [I love it] is crazy::))
Bud
Not being there makes it difficult.
95 [I love it] is crazy::))
Bud