Custom Query (39 matches)
Results (1 - 3 of 39)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1 | fixed | Connections listbox empty if too many available connections | ||
| #2 | fixed | xwlan widget / wlanstat crash on startup with damage profile | ||
| Description |
xwlan widget or wlanstat crashes on startup when profile data is somehow corrupted. No clue why profile got damaged. Tracked down to be a problem when the readprofile code tries to read from memory which does not belong to the current process. Popuplog.os2 entry - 05-22-2013 11:36:21 SYS3175 PID 052c TID 0001 Slot 00d9 E:\_WORK\XWLAN\TRUNK\TEMP\WLANSTAT.EXE c0000005 0002d866 P1=00000001 P2=25b83e66 P3=XXXXXXXX P4=XXXXXXXX EAX=25b83e66 EBX=00000000 ECX=00501010 EDX=000d2e58 ESI=1c79fb18 EDI=1c7976b0 DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f2 FSLIM=00000030 GS=0000 GSACC= GSLIM= CS:EIP=005b:0002d866 CSACC=f0df CSLIM=ffffffff SS:ESP=0053:000d260c SSACC=f0f3 SSLIM=ffffffff EBP=000d2a94 FLG=00212283 WLANSTAT.EXE 0002:0000d866 Work around - delete the damaged profile from os2.ini with an ini editor. Of course you've to know which one is broken. For this you can make a debug build of wlanstat, fire up idebug, step through profile.c and find the problematic one or delete every one :-) Better solution - use DosQueryMem? (thanks Dmik for the hint) and check data before reading. |
|||
| #3 | fixed | interface setup screwed up | ||
| Description |
The current code base sometimes does not correctly configure interfaces when switching profiles. It was observed that xwlan creates numerous interfaces (lan9, lan8, lan7....) instead of configuring the correct ones (lan0, lan1 in my case). As switching profiles usually works here, I think this could be a timing issue. Usually one interface is switched off and afterwards the other interface is configured. But once I saw that both interfaces lan0 and lan1 were configured at the same time for a short period. |
|||
