 |
 |
|
Intel PRO 100 Integrated Ethernet Patch |
|
|
|
|
|
|
| Holy Smoke...thank you Drake too |
|
|
By retrorandy - Posted on April 11, 2008 - 04:08:45 (#22701)
Current version when comment was posted: 1.0 |
|
|
Another 4 year old post/how to saves the day. I can't believe how smooth it is to surf the web on Firefox 2 in BeOS. It's unbelievable how this OS has no lag when loading pages. BeOS never ceases to amaze me. Such a shame this OS wasn't better supported with drivers. It so blows Windows out of the water.
|
|
| yeah! meccha holiday |
|
|
By peasant - Posted on June 21, 2003 - 03:27:59 (#7825)
Current version when comment was posted: 1.0 |
|
|
its working now. i'm on moz firebird writing this comment. thank you thank you thank you drake.
( ^v^).click*
|
|
| nothing happened |
|
|
By peasant - Posted on June 21, 2003 - 01:46:15 (#7822)
Current version when comment was posted: 1.0 |
|
|
i moved floppy to another directory and booted, but there's still floppy in the devices prefs.
|
|
| removing floppy |
|
|
By peasant - Posted on June 21, 2003 - 01:36:24 (#7821)
Current version when comment was posted: 1.0 |
|
|
can i just rename it to floppy.old or something?
|
|
| Remove The Floppy |
|
|
By MYOB - Posted on June 20, 2003 - 15:06:37 (#7815)
Current version when comment was posted: 1.0 |
|
|
delete /boot/beos/system/add-ons/kernel/drivers/bin/floppy
That will stop the Floppy driver
|
|
| no bios option |
|
|
By peasant - Posted on June 20, 2003 - 12:12:38 (#7812)
Current version when comment was posted: 1.0 |
|
|
i should have said that this is a laptop i'm installing into. and this one particularly have no accessible settings to its bios. just a boot media option, password security and nothing more. tell me how to remove the floppy please, if you can't think of any better idea.
thank you drake.
( ^_^)peasanT
|
|
| Floppy conflict |
|
|
By Drake - Posted on June 20, 2003 - 10:36:18 (#7811)
Current version when comment was posted: 1.0 |
|
|
You might try turning off plug and play os in your bios as BeOS can have some problems when this is active (Be does not need plug and play to sort out devices). If this doesn't help and no one makes any other suggestions then you could probably try the rather extreme method of completely removing the floppy driver.
|
|
| typo. sorry |
|
|
By peasant - Posted on June 20, 2003 - 08:33:23 (#7810)
Current version when comment was posted: 1.0 |
|
|
ignore the number below. the card id is "2449".
|
|
| partial success |
|
|
By peasant - Posted on June 20, 2003 - 08:32:40 (#7809)
Current version when comment was posted: 1.0 |
|
|
thank you thank you thank you. and btw, if you'd like the id, it is 2499.
i got net prefs. to recognize the card, but before that, when i was looking into the device property of the e'net card, there was an IRQ conflict (IRQ 6) with the Floppy. since i am using a usb floppy and the drive wasn't even connected, ever, when i am using beos. can you recommend a fix/workaround?
|
|
| patching |
|
|
By Drake - Posted on June 20, 2003 - 04:51:12 (#7807)
Current version when comment was posted: 1.0 |
|
|
As explained in the readme file this patch works by replacing PCI ID 1229 with the PCI ID of your card.
Find the PCI ID of your card by running the devices app in preferences. Select the device listed as ethernet. Open the info tab. One of the fields is your PCI ID note this down.
In the install.sh file bsubst is called with two strings. The first is a piece of code found in the driver supplied by Be Inc identifying PCI ID 1229. This is given as the 9th and 10th two digit numbers (29 12 the id is reversed). The second is the replacement code which should include the PCI ID you noted earlier.
As with the 1229 value this is reversed so take your PCI ID and seperate into two two digit values, take the first two digits and replace for the 10th pair in the second string and replace the 9th pair with the last two digits from your PCI ID.
Then following the instructions in the readme you should back up the original driver and then run install.sh in a terminal.
If the driver works for your device (which I believe it should for the VE) and you have coreectly replaced the values then you should now have a working driver.
|
|
| newbie |
|
|
By peasant - Posted on June 19, 2003 - 19:14:50 (#7802)
Current version when comment was posted: 1.0 |
|
|
i'm on an intel pro/100 VE ... can this patch be used ? if it reallycan, should i just run install.sh and then start the network prefs. and expect my card to be listed ? please provide step-by-step (roughly is ok) isntructions.
|
|
| Gigabyte 8IEXP Socket 478 Motherboard |
|
|
By zulaica - Posted on October 22, 2002 - 16:46:23 (#3715)
Current version when comment was posted: 1.0 |
|
|
i believe this is the same motherboard you have... i followed the instructions and the driver fails to initialize. i'm not sure what i'm doing wrong. :-/
|
|
| Intel 10/100 |
|
|
By chrish01 - Posted on September 7, 2002 - 17:30:36 (#3059)
Current version when comment was posted: 1.0 |
|
|
I replaced 103a in the script with 1039, and my network card is now recognized. but unfortunately, it still does not work. no matter what i do, (being dhcp to get info from my dhcp server, or static) it does not start. i cannot ping my local network, or outside network. im a CCNA, so i know my configuration is set HOW it is SUPPOSED to be set up.
if anyone has any ideas, let me know.
|
|
| Works Perfectlly! |
|
|
By IBeDuke - Posted on August 27, 2002 - 21:38:10 (#2871)
Current version when comment was posted: 1.0 |
|
|
Commate @BOX computer uses Intel 845G chipset with Intel Ethernet chipset integrated on the mainboard.
I applied this patch . . . and now cable internet access is working perfectly.
Thanks for posting this fix!!!
|
|
|
|
|
