lacentrix wrote:just MP and NS running, its a P3 but memory could be the issue only having 128meg .. is this a common prob?
lacentrix wrote:thanks, i thnk i may order some, can go gig so might as well.
-myke
G8tK33per wrote:I suspect it might be, if you're running XP the recommended minimum is 256 if I remember correctly. Besides, I'm sure that running MP is a resource hog in and of itself.
chow wrote:Hi,
I'm very new to all of this. I tried version 25 of the script and got the above error.
I tried the solutions proposed in this thread (installing MDAC 2.8, placing the icons in the programme dir -I put them in all directories of MapPoint and Network Stumbler by now), but it still gives the same error:
"An error was reported in your script.
"
"Microsoft VBScript runtime error.
"Type mismatch: 'foundBSS.Symbol'
"Line:738 char: 20
"SCode: 800A000D
The code around the error is this:
736 If useCustIcon then
737 If (CapFlags Mod 2) = 1 Then
738 if ((CapFlags / 16) Mod 2) = 1 Then
739 foundBSS.Symbol = cSymbol1
740 foundBSS.MoveTo(WEPPushpins)
MapPoints starts upon opening the script and I' even placed on the right spot on the map. Then the error appears ... I think when NS detects the APs in the neighbourhood.
I' m using NetworkStumbler 0.4 on a Sony Z600TEK with Windows 2000 Professional (UK-version, SP4), MapPoint 2004 Europe, a LinkSys WUSB54G (European version) and a Garmin eTrek Vista (European version). The speech part is working (if I disable MapPoint in the script, the script keeps working).
Did I miss something in this thread/on this board? I couldn't find a solution which worked for me.
Does anyone have an idea?
TIA, Cu,
Robert
bobbe wrote:The solution that he got did not work for me, or maybe I can't understand it, could someone explain this to me better?
It was originally posted on page 14, post #206
wrzwaldo wrote:load it into notepad and do a "find". I would start by looking for "foundBSS.Symbol"... But thats just me.
Users browsing this forum: No registered users and 1 guest