Like Michael I am also trying to get this to work on arca.. We have got
it to build, run without error ie hpt toss pack scan all run without error. However hpt toss does not toss the inb packs ie .sa0 for today they just remain there, and no errors given. In fact the toss output
looks normal it just isnt tossing any packets. Is there anyone here actually running hpt on os2 where we could compare setups...?
* Forwarded from area 'fidosoft.husky'
On 2021-02-20 21:17:42, Rick Smith (1:105/10.1) wrote to All:
Like Michael I am also trying to get this to work on arca.. We
have got it to build, run without error ie hpt toss pack scan all
run without error. However hpt toss does not toss the inb packs
ie .sa0 for today they just remain there, and no errors given. In
fact the toss output looks normal it just isnt tossing any
packets. Is there anyone here actually running hpt on os2 where
we could compare setups...?
I have an eCS OS/2 virtual machine I can test it on. Please post your config :)
unpack "unzip -j -Loqq $a $f -d $p" 0 504b0304
20 Feb 21 23:39, Rick Smith wrote to andrew clarke:
My unpack line:
Unpack "c:\util\unzip.exe -C -j -o $a $f -d $p" 0 504b0304
I made mine like this it did not change anything the pkts still remain in inb.. no errors and hpt toss with run
completely clean of errors, it just shows 0 messages tossed.
Could it be in the build? I have to admit this was my first attempt at building it os2. here are the exe's that I
produced maybe I am missing something?
20 Feb 21 23:39, Rick Smith wrote to andrew clarke:
unpack "unzip -j -Loqq $a $f -d $p" 0 504b0304
Further information.
I rebuilt all the .exe's (just because why not)
This is the order I built
huskylib
smapi
fidoconf
areafix
hpt
here is the commands I used
cd huskylib\make
wmake -h -f makefile.watcom OS2=1 clean
wmake -h -f makefile.watcom OS2=1
cd ..\..
* Forwarded from area 'FIDOSOFT.HUSKY'
21 Feb 21 08:38, Rick Smith wrote to Tommi Koivula:
Did you try http://download.huskyproject.org/os2/husky-all-1.9-os2-libc066-2021021 3.zip ?These got me the closest yet... it essentially works with the some path tweaking, however the jam is still a little screwy which I just heard from andrew was just updated a couple hours ago.. Who is building these pre-builts? Will that person build a new set with the updated fix for jam? Because I think that will do it...
* Forwarded from area 'FIDOSOFT.HUSKY'
On 2021-02-21 08:38:12, Rick Smith (1:105/10.1) wrote to Tommi
Koivula:
I did notice yours is hpt-emx while ours is hpt-wc which I am we
built -wc because -emx didnt work correctly with .jam?
On 2021-02-14 15:10:28 UTC there was a change to the code that accidentally broke JAM on all systems, not just EMX.
A fix was committed to the huskyproject repo (smapi module) two hours
ago.
On 2021-02-22 18:30:32, Michael Pierce (1:105/81) wrote to Tommi Koivula:
just thought I'd let everyone know, the latest 'smapi' fix, broke hpt again, hpt wont 'see' the packets in anyway shape or form unzipping the bundles, hpt still does not see anything no errors in hpt.log
Thanks for this. I was able to reproduce it in OS/2.
The failing code that I removed was only relevant to 16-bit OS/2 1.x, which Husky has never supported anyway.
On 2021-02-22 18:30:32, Michael Pierce (1:105/81) wrote to Tommi
Koivula:
just thought I'd let everyone know, the latest 'smapi' fix, broke
hpt again, hpt wont 'see' the packets in anyway shape or form
unzipping the bundles, hpt still does not see anything no errors
in hpt.log
Thanks for this. I was able to reproduce it in OS/2.
The failing code that I removed was only relevant to 16-bit OS/2 1.x, which Husky has never supported anyway.
Seems we are so close to this working.... Here is how golded reports reading the messages hpt tosses may provide a clue?
---------- Tue 23 Feb 21, GoldED+/EMX 1.1.5-b20170303 (Apr 6 2017 17:43:20) ! 06:23:02 JamArea::load_message: can't read Jam msgtext
: 06:23:02 Info: Your msgbase is corrupted.
+ 06:23:02 Advice: Run a msgbase index rebuild/recover utility.
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 138:41:05 |
Calls: | 166 |
Files: | 5,389 |
Messages: | 223,229 |