Following Bills suggestion to compare the results of ifconfig with ipconfig and winipfcg under M$ I found more information available under Linux. I looked at the info for the network card in the M$ drivers. It was set up for half duplex under M$ (I changed it to full). I don't know if the software would affect hardware settings at this point. If I change it under M$ would it change under Linux?
BTW, the card is a Realtek RTL8029(AS) which gets seen in Linux as an NE2K-PCI.
More things to report... I transfered around 10 large files in the space of a couple of hours (even allowing for the crashes from M$). Transfer was a single file at a time. Under Linux three simultaneous files takes 18 - 21 hours.
After transferring the files (and getting numerous complaints about the C: drive running out of space although it was downloading to G:), I decided to muck around with the Network places icon. I mangage to set up access to the ftp server as a desktop window. I'll play around with it later. Any advice for getting something similar running under Linux?
Later Mike
Mike Pfaiffer wrote:
Following Bills suggestion to compare the results of ifconfig with ipconfig and winipfcg under M$ I found more information available under Linux. I
Mike, I am sorry, I gave you the wrong command. The Window's command in a DOS prompt Window is
netstat -e
It gives the Ethernet stats: errors, discards, etc.
looked at the info for the network card in the M$ drivers. It was set up for half duplex under M$ (I changed it to full). I don't know if the software would affect hardware settings at this point. If I change it under M$ would it change under Linux?
No.
-- Bill
On January 30, 2006 08:47 pm, Bill Reid wrote this amazing epistle:
Mike Pfaiffer wrote:
Following Bills suggestion to compare the results of ifconfig with ipconfig and winipfcg under M$ I found more information available under Linux. I
Mike, I am sorry, I gave you the wrong command. The Window's command in a DOS prompt Window is
netstat -e
It worked. I was going to post a copy of the results. M$ ran out of memory (on a 768MB machine, I'd like to know how) and wouldn't open a DOS Window. After a reset, the stats were reset as well. An hour into the process, before it ran out of RAM, it showed no errors.
It gives the Ethernet stats: errors, discards, etc.
looked at the info for the network card in the M$ drivers. It was set up for half duplex under M$ (I changed it to full). I don't know if the software would affect hardware settings at this point. If I change it under M$ would it change under Linux?
No.
I tried the card in full duplex. For a single file it said it would take a day and a half (pretty much like the speeds I am getting under Linux). Netstat didn't show any errors. There were a total of 39 discarded packets. I switched it back to half duplex and it was much happier. I started four download threads. When I started the first it said the estimated time for transfer was six minutes. After the fourth was started it increased the time to an hour. Now I know to do one file at a time under M$. There are more files to transfer tomorrow. I'll make sure I keep a DOS window open.
Right now I'm backing up my fathers M$ box to the Mac. For an old piece of hardware it is quite robust. Apparently OS X 10.3.X and newer resolve most of the problems of crashing. Lots of little annoying things but nothing major.
-- Bill
Later Mike
P.S. For a laugh, check out the current issue of the magazine (link is below - it's free again). One article describes the result of a grandmother connecting to DSL. Even if you don't want to read the article, check out the title and the first couple of paragraphs. ;-)
Mike Pfaiffer wrote:
On January 30, 2006 08:47 pm, Bill Reid wrote this amazing epistle:
Mike Pfaiffer wrote:
Following Bills suggestion to compare the results of ifconfig with ipconfig and winipfcg under M$ I found more information available under Linux. I
It worked. I was going to post a copy of the results. M$ ran out of memory (on a 768MB machine, I'd like to know how) and wouldn't open a DOS Window. After a reset, the stats were reset as well. An hour into the process, before it ran out of RAM, it showed no errors.
you mention using winipcfg, I'm assuming you're using windows 9x. This is a fairly wide spread problem (windows 9x, 512MB+ ram, and an AGP video card) http://support.microsoft.com/kb/q253912/
Theo
On February 1, 2006 10:17 pm, Theodore wrote this amazing epistle:
Mike Pfaiffer wrote:
On January 30, 2006 08:47 pm, Bill Reid wrote this amazing epistle:
Mike Pfaiffer wrote:
Following Bills suggestion to compare the results of ifconfig with ipconfig and winipfcg under M$ I found more information available under Linux. I
It worked. I was going to post a copy of the results. M$ ran out of memory (on a 768MB machine, I'd like to know how) and wouldn't open a DOS Window. After a reset, the stats were reset as well. An hour into the process, before it ran out of RAM, it showed no errors.
you mention using winipcfg, I'm assuming you're using windows 9x. This is a fairly wide spread problem (windows 9x, 512MB+ ram, and an AGP video card) http://support.microsoft.com/kb/q253912/
You hit the nail on the head with that one. Leave it to M$ to make a computer less capable when the user makes it more capable. I'll try the first two solutions they suggest. The third is unreasonable. Thanks for the info.
I started out trying to solve a Linux problem and now I have to solve M$ problems. <sigh>
Theo
Later Mike
Mike,
At the risk of sounding over dramatic, the NE2K was unquestionably the worst network card ever made.
The linux drivers home page for this card is here:
http://www.scyld.com/ne2k_pci.html
Quote: "No document about this hardware can be written without an initial flame: PCI NE2000 clones are a bad idea."
It goes on to explain that this hardware was made only as a cheap proof of concept and was never intended for production.
I'll let you read the rest of the gory details for yourself but the bottom line is you should get a different card.
Regards,
-
Bill Reid -
John Lange -
Mike Pfaiffer -
Theodore