Crash after few Minutes (Page 1 of 2)

I've got the same thing here on my Asus MyPAL A636.

Found a few hotspots, shuts down without warning.
When working, the radar is the same untill new hotspot found. So no updating screen while scanning.

Newest firmware and tried the beta also.
Same problem.

The A636 uses an ALPS CF8381PN Card for it's wifi.

Can someone help me, 'cause it's a great app!

Greetings,
Xaria

hello,

my english is not very good, but i have the same problem with asus a636.

thank you for your answer if you have the solution one day.

jlsoub@aol.com

Hmm sorry you are having problems but this is really weird. This seems to be the only PDA with this problem. When it just vanishes with no error its usually a serious memory error. I'll look and see if I can see what might cause it and I might post some test files for you to try.

Hello indiekiduk,

I too have similar problems with WiFiFoFum 2 on my Asus A636.
But I like to think positive and say it almost works.

I can start the programm only when I am near to an AP (when the integrated WiFi-manager can find an AP).
When I am out of reach of any AP the programm will show up for one or two seconds and then die without any error messages.

Once WFFF runs it will continue operation even when I leave the range of the AP.
The LastSeen time does not stop updating when leaving the range of the AP.
I can scroll or start other programms an then switch back to WFFF without any problem.
But as soon as I try to switch to radar view or just select tool/options the proramm dies sielently.

I tried do find out if the number of APs found could be a problem.
I could detect 37 APs during a 50 minute walk yesterday just carrying it with me and not trying to switch to radar view.
The LastSeen time of the last one that had been in reach always was updated until the next one was detected.
When I came home and selected tools/view the program again died silently.

The recorded log had 1850 lines, one line every one or two seconds (50 minutes/1850 = 1.6 seconds).
Only just before a new AP showed up there was a gap of 3 seconds.
I am quite sure that I was out of reach of any wlan most of time during my walk but the log shows one AP for each scan interval.

The settings I used were:
Scan interval: 1500 ms
Aggressive scanning: off
New network notifications: off
Autosave (when GPS valid): on

Could the integrated WiFi-manager be the cause for the problems?

I think to remember that the problems were smaller with the previous ROM-release of the A636:
When Aggressive scanning was turned on WFFF could be started even when not in the range of any AP.
But it was not as stable as WFFF 0.3.3.

I really hope you can solve the problems.
Please let me know if there is any further testing that I can do.

Best Regards

Hi all,
I have the same Wififofum issue with my Asus 636.  Also, a similar issue to Simpson 199 (see previous post in this thread).  I can connect to my home Wifi no problem.   However, when I try to connect to the public free Wifi it all falls over.  The Wifi manager tells my I am connected, but all I get is the login page (Internode here in Adelaide Australia).  Then nothing happens.  I can ping their site and get an OK?  Am I doing anything wrong?  I was hoping that Wififofum would sort out the problem but that doesn't work either.

Can somebody point me in the right direction about how to find out the firmware version in my unit and about where to find the upgrade and how to load it - I assume there is a thread somewhere.

Is there a forum specially for the Asus MyPal 636 somewhere?  There is a little bit on Wormholecreations.
http://www.wormholecreations.com.au/wc/ … asp?fid=39
Thank you, Mark

You mean a soft reset yeh ? You lose your data with a hard reset.

Does it freeze if you don't use the GPS?

I am running WFFF with iPaq 4150 and experiance the same, crash after fiew records.
I used firs version 2 (german with no GPS). It worked fine.
Then I connectet GPS Royaltek TBT-3000 via bluetooth. Erros messge came up: Erros connecting GPS!
The blue light was flashing!
So I installed the new Version 2.1.1 but CAB File (MSI not working).
I also added NET software, new version.
Result:
WFFF working without GPS fine, but as soon as I connect to GPS, ERROR Message like before.
I found in FAQ, that iPaq requires OpenNETCF.IO.seral.dll. Installed it in Progr\WiFiFoFum\ as requestet.

Oh wonder, it worked, some GPS Position were logged with detected AP's. But only a fiew Postions, then sreen was frozen.
Mus do soft Reset of PPC! Total crash, not working again, has done something to W-Lan in the iPaq.
Reload via ActivSync.
Workin for short time... then again.
Removing <open<net<<fc.<io.seral.dll and it worked again, but without GPS.
Any idea? Help needed

I recently bought the Asus A636 and had the same problems with wififofum 2.1.1 as described here.
Today I installed the old version 0.3.3 and it works much better.
It scanned a lot of networks, GPS is also working. The landscape mode is not so fine and the netstumler file is not compatible, I am very glad that it is working. It is the first wifi scanning program that works good on my A636.

Good day, people!
One more posting to prove that A636 problem really exists
On my PocketPC (A636 with latest firmware, Russian version) there are the same symptoms:
WiFiFoFum 2.1.1 dies quietly in several seconds, if started when there are no APs in proximity. Also, it has been "frozen" once and needed reset, when native Asus WiFi Manager was running and GPS was active - then the pocket machine responded to pings, but all the buttons except "reset" became inactive.
Eagerly waiting for bugfix - for A636 is a really nice machine with only two shortcomings - the first is that there is no *nix distribution for it, and the second you know
And one more wish - is it possible to supply .NETCF v2 downloads in CABs - for those, who have no Windows PCs with ActiveSync at all? Though it is possible to find such a NETCF distribution, it would be very helpful to have all the files needed in one place.

Last edited by gastur (19 Jul 06 16:06:33)

Hi..

On my Asus A636N Wififofum doesn't show any Access Point, strangely enough Ministumbler doesn't either...

ROM version V03.0618.NLD 0413

Network card is being recognized as CF8385PN1

regards,
Hans

Hi...

I don't have emailed with Asus about this problem. But i've found out a way to "reliable" operate WiFiFoFum...

1) Do a soft reset
2) Start "Sockets Wi-Fi Companion" (3 day demo available for download at socket)
3) If start screen of "Sockets Wi-Fi Companion" shows pda top left and antenna bottom left =>
4) ... now start WiFiFoFum and it will work.

You can exit "Sockets Wi-Fi Companion" and you'll see a blue antenna in the header (where clock is). You can start WiFiFoFum as long as you see that antenna. Most of the time the blue antenna will disappear after going to standby and wakeup the pda.

Conclusion:

Blue antenna visible => WiFiFoFum works
Blue antenna disappeared => WiFiFoFum crashes

It looks like that there's a problem with "sleep mode" of WLAN card?!?

But WM5 WLAN connectivity is still working even if socket and WiFiFoFum won't. So maybe there's just a "special call" from the software needed?!?

Kind regards,

Gerd

PS: Is there a special version available of WiFiFoFum which is logging it's network windows api calls to a debug file? This way it would be possible to track down the problem and report that to Asus.
PPS: Maybe only .Net 2 apps won't work?

I mailed Asus about the problem. The only answer they had was that they don't support wififofum.
My Asus died after a month. I send it back to repair.