This device seems to be giving me no end of problems, got the startup problems sorted out, but now it appears that with this enabled the machine wont shut down. Gets to the Shutting down Win 95 screen and goes no further. This wouldn't be a big problem except then it wants to run scandisk during startup next time round... grrr
any ideas or people who have had this problem as well ?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
sorry about that I managed to get it sorted out, but out of interest the machine spent all last night on the shutting down screen, but I am really starting to dislike 3com stuff as it seems that every 2nd day I am finding something that doesn't work with this particular card, look around for a while and eventually find some update driver that fixes that particular problem. anyway hopefully this is the end of my 3c905 problems
i am gonna take a shot in the dark.. you are running the 3c905b card and on a super socket 7 motherboard with a 100 MHz bus... how close am i? 3com does not know how to solve my problem so they requested i send the machine in for their escalation department to look at it... they have had the machine about a month and have not gotten anywhere... on top of that they needed my help with an issue... it is aggravating.. but they do offer good support... altho it is taking *too* long they are at least dealing with it... besides the other locations i have the cards installed in do not seem to be doing too bad with them.
I think the card is a b, but I am uncertain about the motherboard. But I tend to be finding that there are new updates to the drivers each time I come across a problem, but then the documentation with the new drivers never seems to indicate that problems might exist elsewhere. I have sorted out this problem with the as yet unsuported 4.01a drivers but am waiting for the next problem to rear its head.
I have 3com 905 B TX cards, and endless problems...
I use them on a intel endeavor motherboard (P133)
They are supposed to be very good, but so far:
-in win 98: BIOS doesn't give interrupt in 50% of the cases, so it is disabled.
- in linux: random error messages about IRQ blablabla
-100 Mbit connection won't go faster at all
I updated my bios to latest version, I updated the 3com drivers to latest version for W98,
but no difference. (by the way, I have to reinstall the drivers for this card 3/4 times
before it works...and NO, I did it the right way, I know what I'm doing ;-)
I don't know it anymore, but I will follow this discussion closely.
If I find solution will post it.
jaredc, Tim hasnt responded to your last inquiry so I will (No offense Tim, just trying to help). Some NIC Cards have drivers which do not release there resources properly when windows does a shutdown. Cards like these (I should say drivers) cause the problem you were describing (not shutting down). By clearing all network connections (deleting drive mappings, etc.), you essentially overcome the cards problem. Some 3Com card drivers exhibit this problem, but they are by no means the only ones. Just a little info.
Heath
Hello,
I had the exact same problems with the 3c905b-tx card. I was running windows 95 too. Here is what I did to fix the problem. I am using a cross-over cable between two systems, and my network is fine. One system has the 3c905b-tx card; the other has a 3c509.
I configured my 3c905b-tx to half-duplex mode and removed the automatic detection. I set the network speed to 10mbits. I am not sure if you have to do this, but I think it prevents intermittent problems if the other system does not have the same NIC card (my other system is only capable of communicating at 10mbits).
First, the 3com driver would not work under windows 95. I kept getting a device system failure (code 8). At first, I thought I was having a hardware problem. But I decided to install windows 98 on the system with the 3c905b-tx card, and guess what, no more problems. Either windows 95 has bugs (that can't be it!?), or the 3com drivers did not work under windows 95.
I had a heck of a time installing the windows 98 upgrade. First, I had to boot my system in dos mode. Then I had to rename the aolndi.dll file in the \windows\system\ directory to aolndi.old. That file was causing my upgrade to fail with a "Call to Undefined Dynalink" error. After that, the installation of the windows 98 system went smoothly.
Now my network works fine even when the other system is running Linux, instead of MicroHARD. Feel free to email me at rmgalante@blazenet.net if you have other questions. I'll try to help you with this card. It's not the card; it's the operating system. It took me 42 hours to figure this stuff out.
Rob
I did some browsing to the subject,
read these pages:
http://cesdis.gsfc.nasa.go
http://cesdis.gsfc.nasa.go
They're about the 3COM boomerang and vortex (3c905 (B) &3C509)
mainly aimed for linux, but also W95 and W98 and some different
motherboards.Lots of modern cards have ACPI power management capability,
which your BIOS can't handle if it's not a new one, which results
in crashes....
Jared,
I'm only asking you to try to ascertain whether or not you're experiencing the connection release problem as Heathprovost has kindly filled in on (ps - I was probably in bed when Jared posted his enquiry - give me a chance !).
There are a number of things you can do about this, so let me know !
Also - are you using /PERSISTENT:YES in your logon script ?
Are you assigning drives in logon script, or via the registry ?
Business Accounts
Answer for Membership
by: KevonPosted on 1999-02-08 at 13:40:22ID: 1554141
Can you give us the URL to the Experts-Exchange question that has the background of your question? It would be easier than asking a bunch of questions.
First question: How long do you let it wait before just shutting it off... what steps did you take to ensure that it actually was frozen?