-
August 28th, 2001, 12:25 AM
#1
Win2k and BSOD with Floppies...
I am having the strangest of problems. I have Win2k, and every time I try to access a floppy disk (3.5" or 5.25"), it gives me a mishandled exception error in hal.dll. I don't have the exact error because I don't like having to restart >:|
Anyway, has anyone heard of this?
System:
1.2GHz Athlon
EpoX 8K7A+
Generic floppy drives
HP CD Writer (No adaptec/roxio installed)
Acer 32X CD-ROM
Hercules KyroII
Hercules Gamesurround Fortissimo II
Netgear FA311 Network card
External 33.6 Hayes Modem
300W PS... should be plenty according to ratings and all on the supply (checked wattage vs. # of drives, etc.)
Quantum Mechanics: The dreams stuff is made of
-
August 28th, 2001, 02:13 AM
#2
Ok, checking around, My sound card, VIA USB Host Controller, Kyro and Network Card are all sharing IRQ11. I have no idea how to get this to not be. I have tried changing it in the BIOS, but when it reinstalls the drivers for the card, it puts it back to shared on IRQ11. I think that this is the root of all my problems. It looks like I have IRQ's 5,7 and 10 open... any ideas? The option to change anything from in the system is grayed out.
BTW, I'm running Windows 2000...
Quantum Mechanics: The dreams stuff is made of
-
August 28th, 2001, 02:43 AM
#3
Registered User
First I would try to load the System from the Floppy. This way I would know that nothing is wrong with the Drive or the FDD Cable.
Second, Are you in Win2k ACPI Mode?
Please reply,
Gabriel
Real stupidity beats Artifical Intelligence
Avatar courtesy of A D E P T
-
August 28th, 2001, 04:23 AM
#4
I seriously doubt if the sharing of IRQ 11 is causing your problem. If your mobo uses ACPI then this is normal behaviour.
More likely is that the Floppy Drive or FDD controller is faulty. Try booting from a floppy disk and test the floppy drive access at a command prompt.
-
August 28th, 2001, 05:00 AM
#5
Registered User
If the two floppy drives are ok, then it must be the floppy controller on the motherboard. I don't think re-assigning or sharing IRQs will improve the situation.
The wandering Odysseus of the web.
-
August 28th, 2001, 07:18 AM
#6
Banned
You didn't list any of your software. Do you use InoculateIT for Windows NT? If so, you need to update with the NT patch. I have seen this happen because the viurs software was installed clean with only signatures updated, but not the real time monitor patch.
Download here: <a href="http://support.ca.com/Download/patches/ilitnt.html" target="_blank">InoculateIT 4.5/6.0 for Windows NT Patches </a>
-
August 28th, 2001, 06:07 PM
#7
GAH! It seems as if the floppy controller is dead as a doornail. I have the BIOS set up correctly, leave a diskette in both drives, and it just doesn't like working. But everything else seems to be perfect. It starts trying to access the drive when the computer starts, it detects both drives. Any ideas why this might be happening?
Quantum Mechanics: The dreams stuff is made of
-
August 30th, 2001, 04:26 AM
#8
Registered User
100% a Problem with the FDD Cable.
Real stupidity beats Artifical Intelligence
Avatar courtesy of A D E P T
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks