![]() |
|
|||||||
| Register | Search | Today's Posts | Mark Forums Read |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
#1 (permalink) |
|
Posts: n/a
|
Problem w/ Orinoco & Ministumbler on iPAQ 3800 series
I'm working w/ ministumbler on a iPAQ 3835 using the single pcmcia sleeve. Every so often, the status will turn to "need to ru..." (can't read the rest).
Not sure what this is, and I'm looking for some additional information, because I need to eject & re-insert the card to get it to work. Thanks!!!!! |
|
|
|
#5 (permalink) |
|
Posts: n/a
|
It doesn't lock up, ministumbler just stops sending out probes, and says "need to ru..." in the status bar at the bottom of the window.
It's really quite odd..... It will happen at "random" times. Without any rhyme or reason.. it's just really weird....... FYI: My card/driver info: Orinoco Driver (build 570) Client: 2.06 Driver name: WLLUC46 Driver version: 7.42 Primary Firmware Version: 4.0 Station Firmware Version: 8.10 |
|
|
|
#6 (permalink) |
|
Posts: n/a
|
Im getting the same thing with my ipaq 3835 and my Wavelan silver card.
Orinoco Driver (build 570) Client: 2.06 Driver name: WLLUC46 Driver version: 7.42 Primary Firmware Version: 4.4 Station Firmware Version: 8.12 When I quit netstumbler and check the status of the card it reports the firmware versions as 0.0 until I either reinsert the card or put the ipaq to sleep and wake it up. It even does this at random times when im browsing the net or using AIM. |
|
|
|
#7 (permalink) |
|
Posts: n/a
|
Not seeing it on my 3870
David I'm using the same set up as you:Orinoco Driver (build 570)
Client: 2.06 Driver name: WLLUC46 Driver version: 7.42 Primary Firmware Version: 4.0 Station Firmware Version: 8.10 I've run my battery down in my 3870 without seeing what you are seeing. Are you using the Orinoco for anything else, while running MiniStumbler? David |
|
|
|
#8 (permalink) |
|
Posts: n/a
|
No, I'm not. The driver is trying to establish a connection, but as far as I know, that is the only thing that is attempting to use the card.
As an aside, perhaps it's the Win CE networking portion itself. I don't have my iPAQ in front of me (at the g/f's. Portable computer, but I forget it at home. Oh well ;-)) Perhaps it's the settings in the driver, or in the networking portion of the OS. Hmm, maybe we should post that info as well.. I just have a sneaking suspicion, that you (David) just happened to hit a "sweet spot", and we need to emulate your settings more closely. Ooh! Interesting aside... I'm also using a singe pcmcia sleeve. Are you (David) using a double? BTW, does anyone know the full text of the message? That may give us an additional idea as to the cause as well.. |
|
|
|
#9 (permalink) |
|
Posts: n/a
|
Well we've got a couple of variables here. Mine has the built in bluetooth, ( Hm I wonder if netstumbler could work with it, for finding bluetooth devices)So our firmware is not the same.
I've installed the 2002 service upgrade, have you? And yes I have a dual slot PCMCIA sleeve, so that's another. I have my card set up to connect to an AccessPoint, not the RG mode. And to download all setting from the Accesspoint. only hard setting I have is channel 10, seems to work best for me. Is there a chance that your sleeve could be separating from your iPaq? David |
|
|
|
#11 (permalink) |
|
Posts: n/a
|
Another possibility:
To the people who's stuff is working: Under the driver configuration -> tools Is "load/unload automatically" checked or unchecked To the people who's stuff is not working: Same question I just disabled it, and everything appears to be more stable. Going to run tests to see if it actually works. |
|
|
|
#12 (permalink) |
|
Posts: n/a
|
On mine it is checked, as is Suspend While Connected.
2 questions for you, do you have WEP enabled? If you pull your card, I seem to get all of the message. Did you upgrade your card in a notebook? Goes by to fast for me to read, but the first two words are what you are reporting. David |
|
|
|
#14 (permalink) |
|
Posts: n/a
|
Varian a question about your version
My card has seen at least three updates, and our drivers and firmware are reporting the same values. So looking for differences, WEP maybe one. When using netstumbler I have always had WEP disabled. My card is set to pull everything from the DHCP server, so when I go stumbling, it's getting nothing. (Out of range of my AP)My speed is medium (3)if I'm right, then the faster we work the card, the more likely we are to see your problems.
Varian; Do you have any idea how you have your values? You are showing the same build as me but have different Primary Firmware (4.4 instead of 4.0) and Station Firmware (8.12 instead of 8.10)Do you have beta software? or is your card very new? |
|