I've got this frankinstein of a puter. Compaq main board, celleron 700mhz chip, reg atx case. Running win 98_se, and have some resource conflics, but nothing that would cause the problem im having (or so I would belive). My floppy's not working. Yes It's recognized by win, and the light comes on when I attempt to read from it, but it will not read. I've tried replacing it to no avil. The resource conflics are between my mainboard resource controller and my 101 keyboard. Compaq's no help, and I cant find any drivers for this device. Win will not allow mw to assign any new resources for this device and states that only win can assign them. Got any suggestions, or drivers?
It's alive..........ALIVE!!!!Got a frankinstien of a puter? I do. Maby we can help 2gther
Page 1 of 1
New Topic/Question-
This topic is locked
3 Replies - 1260 Views - Last Post: 12 December 2001 - 01:35 AM
#1
drstrangepork
- New D.I.C Head
Reputation: 0
- Posts: 3
- Joined: 02-December 01
It's alive..........ALIVE!!!!
Posted 09 December 2001 - 04:44 AM
Is This A Good Question/Topic?
0
MultiQuoteReplies To: It's alive..........ALIVE!!!!
#2
codeman
- w3c fanatic
Reputation: 3
- Posts: 1,190
- Joined: 13-August 01
Re: It's alive..........ALIVE!!!!
Posted 09 December 2001 - 01:28 PM
Hmmmm...that happened to me once. Win thought I was a server and it wouldn't let access the floppy because "it was locked by my administrator". All I did was change the network settings. That might work. Welcome to </dream.in.code> :)
Was This Post Helpful?
0
#3
Vetritus03
- Microsoft.Whore
Reputation: 5
- Posts: 1,742
- Joined: 31-August 01
Re: It's alive..........ALIVE!!!!
Posted 09 December 2001 - 02:30 PM
might be a bad floppy controller. windows tried to access it but if it doesn't work after you've replaced the drive then it's either the controller on the main board or it could be the cable... or i suppose it could be a bad second drive... but i'm sure you tested it. make sure the floppy is enabled in the BIOS... i'm sure you've checked this as well.
you're right, windows will assign resources to this device and you can't do a whole lot about it. drives for floppies are built into windows so there's not going to be one for you to find. it's hard to fathom a resource conflict with a keyboard... this leads me to think you're having a mainboard issue. good luck d00d!
you're right, windows will assign resources to this device and you can't do a whole lot about it. drives for floppies are built into windows so there's not going to be one for you to find. it's hard to fathom a resource conflict with a keyboard... this leads me to think you're having a mainboard issue. good luck d00d!
Was This Post Helpful?
0
#4
drstrangepork
- New D.I.C Head
Reputation: 0
- Posts: 3
- Joined: 02-December 01
Re: It's alive..........ALIVE!!!!
Posted 12 December 2001 - 01:35 AM
Thank you Codeman, but unfortunatly for me it's not the problem. Appreciate the welcome...
Vetritus03 U could be correct about the board. I've already tried those things of which you speak. Yet there is one way to get it to work, that is if I change the cable setting to the slave of that controller. Unfortunatly this create's another problem. When I try to access (or use any app that attempts to access) my 3.5, the whole thing locks up. Could it be that compaq has a proprietary driver for this boards resource controller? If thats the case, that would explain my APM not recognizing any regular win driver.. I have a freind with the same board (orig compaq) maby I can get the nessesary drivers from him. You may have very well solved the problem, or at least put me on the correct line of thinking to solve the problem. Thank you.
By the way. Visited your site. Veary informative. Especialy interested in "Magic Lantern". The Idea of my virus detection not doing its job disturbs me. Not that I have anything to hide from the feebies, but a breach in security is still a breach none the less. Any suggestions on how to detect this sort of thing?
Vetritus03 U could be correct about the board. I've already tried those things of which you speak. Yet there is one way to get it to work, that is if I change the cable setting to the slave of that controller. Unfortunatly this create's another problem. When I try to access (or use any app that attempts to access) my 3.5, the whole thing locks up. Could it be that compaq has a proprietary driver for this boards resource controller? If thats the case, that would explain my APM not recognizing any regular win driver.. I have a freind with the same board (orig compaq) maby I can get the nessesary drivers from him. You may have very well solved the problem, or at least put me on the correct line of thinking to solve the problem. Thank you.
By the way. Visited your site. Veary informative. Especialy interested in "Magic Lantern". The Idea of my virus detection not doing its job disturbs me. Not that I have anything to hide from the feebies, but a breach in security is still a breach none the less. Any suggestions on how to detect this sort of thing?
Was This Post Helpful?
0
Page 1 of 1
| 