Wet under 4.1

Is anyone else having problems running Wet under 4.1? I get a GR on startup because it has a blank ICAO field that doesn't find the closest airport location to me.

@Valiant

Don't have those problems.

I no longer get an hourly report though.
I think that happened with the latest update of Wet though.
It occurs under 4.0 on my classic as well as 4.1 on the Sam.

@TiredOfLife
Same Here no problems running Wet, apart from the Forecast Tab won't update, tried different locations just in case it was a local "station" glitch, but still the same results no Data update.

@Valiant

Check the ICAO tooltype is commented out completely.
Check the DATA tooltype points to a location which contains nsd_cccc.txt

If all else fails, re-download and reinstall.

If that still doesn't work, send me a copy of your tooltypes and I'll try to reproduce the problem here.

@all

I'm aware of the forecast problem - the coding has changed slightly. I'm not quite sure why it stops all data from appearing in the table, but it should be, in theory, an easy thing to fix once I get round to it.

@Chris

Good news to a point, at least now I know it's not something I have done.

Look forward to the update.

Cheers.

Forecast is now fixed. Get the update from Aminet or via AmiUpdate.

Sorry for the delay.

Chris

@Chris

Cheers, I really have missed that feature.

@Chris

Mine seems to be working nicely.

But yes, only airport locations, I can not view the current temperature from another station closer to where I Live.

But for now, I am happy that it works atleast.

Cheers.

@Chris

Works fine here thank you

@Chris
Cheers for the update Chris

Gebrochen, if you have a SAT NAV / GPS which gives your Home position check if it also has Latitude and Longitude readings and input that into the Location in Wet, thats how I got a reading closer to home.
maybe check on one of the Map programs eg google maps, multimap etc they might give that reading as well

@Gebrochen

When I get around to it, I'm going to add some sort of crazy plugin system (probably ARexx-based) to enable data to be fetched from elsewhere. At the moment though, you are stuck with the internal one which only gets data from airports.

Try what AJS suggested - there are a lot of little runways around so there may be data available at a closer location than you think.

@Valiant

I too get a GR at start :-/ don't know if helps, but here is the crashlog:

Crash log for task "Wet"
Generated by GrimReaper 52.7
Crash occured in module Wet at address 0x7F3149D4
Type of crash: DSI (Data Storage Interrupt) exception

Register dump:
GPR (General Purpose Registers):
0: 7F3149D0 6A80F5B0 00000000 6A80F5D4 68D7615C 00000000 00000004 3FFFC000
8: 6A80F5D8 6A80F5D8 00000001 68D7615C 6A80F570 6A825130 6A820000 6A820000
16: 6B5ACDE0 6A81D8F0 6A80F980 6A820000 6B61F490 6B5ACDE0 6A81CF20 00000000
24: 00000000 6A81CD20 6A81CE20 6A820000 6A820000 00000000 00000000 68E23F84


FPR (Floating Point Registers, NaN = Not a Number):
0: nan 3.67963e+296 -1.39925e-309 1.25533e+58
4: 9.59132e+38 -1.36876e-231 5.87755e-39 1.05422e-79
8: 1.05423e-79 -4.17219e-309 5.20079e+08 -3.09891e-303
12: 3.85191e-32 4.16002e-32 0 0
16: 0 0 0 0
20: 0 0 0 0
24: 0 0 0 0
28: 0 6372 3959 -9.41667

FPSCR (Floating Point Status and Control Register): 0x82068000

SPRs (Special Purpose Registers):
Machine State (msr) : 0x0200F030
Condition (cr) : 0x24002024
Instruction Pointer (ip) : 0x7F3149D4
Xtended Exception (xer) : 0x20000000
Count (ctr) : 0x00000000
Link (lr) : 0x7F3149D0
DSI Status (dsisr) : 0x40000000
Data Address (dar) : 0x00000008


680x0 emulated registers:
DATA: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
FPU0: 0 0 0 0
FPU4: 0 0 0 0

Symbol info:
Instruction pointer 0x7F3149D4 belongs to module "Wet" (HUNK/Kickstart)

Stack trace:
module Wet at 0x7F3149D4 (section 5 @ 0xC9B4)
module Wet at 0x7F315190 (section 5 @ 0xD170)
module Wet at 0x7F317364 (section 5 @ 0xF344)
module Wet at 0x7F31AA3C (section 5 @ 0x12A1C)
module Wet at 0x7F320684 (section 5 @ 0x18664)
native kernel module newlib.library.kmod+0x00001f38
native kernel module newlib.library.kmod+0x00002bcc
native kernel module newlib.library.kmod+0x00002d48
_start()+0x170 (section 1 @ 0x170)

PPC disassembly:
7f3149cc: 4e800421 bctrl
7f3149d0: 40920054 bne- cr4,0x7F314A24
*7f3149d4: 801d0008 lwz r0,8(r29)
7f3149d8: b0010022 sth r0,34(r1)
7f3149dc: 813bd260 lwz r9,-11680(r27)

@jabirulo

Hmm, I wonder if that's the same problem Valiant was getting at the start of this thread?

Give the debug version a try (attached below) and post a new crashlog at http://crashlog.os4depot.net if it reappears.

Attach file:

---

Link only for registered users

@Chris

tried wet.debug V5.4 and got a GR

crashlog:
http://crashlog.os4depot.net/cl117

THX & Hope it helps

@jabirulo

That's where it's fetching the port number from the service list (actually I don't know why I didn't just hardcode it to 80), so I suspect it's your Internet prefs causing the problem.

Go into Internet Prefs
Click on Services
Scroll down to port 80
You should have a line which reads:
80 | tcp | www | http


If you don't, add it!

If you are using a TCP/IP stack which isn't Roadshow for some reason, you're on your own.

Chris

@Chris

you're right, just added such service and no more crashlog.
I've got that 'service' ficle since first OS4 beta versions
and didn't change it.

Maybe you can add a warning in the guide if such problem araise the user can check if he has that service added.


THX

@Valiant

It works great here on my ?A1-C with OS4.1

@jabirulo

I'll add some error checking to stop it crashing

@Chris

And if you want i can update/fix the spanish catalog.
With permission of its author (don't know if he's still on active)

Send me the wet.cd via PM

BYE & THX