Hello All!

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)
A 06:42:58 Error executing packer (errorlevel==12, permanent error)
1 06:42:58 Start packing...
4 06:42:58 EchoTossLogFile not found -> Scanning all areas
4 06:42:58 Scanning NetmailArea NETMAIL
7 06:42:58 Packing for 1:105/81 FidoNet Uplink, e9162100.pkt > ea7bc400.we0
6 06:42:58 cmd: zip -9 -j -q \ftn\outb\00690051.sep\ea7bc400.we0 \ftn\tmp\outb
\e9162100.pkt

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)
A 06:42:58 Error executing packer (errorlevel==12, permanent error)
7 06:42:58 Packing for 1:105/81 FidoNet Uplink, ea6b3200.pkt > ea7bc400.we0
6 06:42:58 cmd: zip -9 -j -q \ftn\outb\00690051.sep\ea7bc400.we0 \ftn\tmp\outb
\ea6b3200.pkt

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)
A 06:42:58 Error executing packer (errorlevel==12, permanent error)
D 06:42:58 Statistics
D 06:42:58 areas: 1 msgs: 0
D 06:42:58 exported: 0
E 06:42:58 Areas summary:
1 06:42:58 End

pack zip -9 -j -q $a $f

outbound \ftn\outb\
tempinbound \ftn\tmp\inb\
tempoutbound \ftn\tmp\outb\



Regards,

Rick

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

Hi Rick,

On 2022-08-03 06:36:06, you wrote to All:

7 06:42:58 Packing for 1:105/81 FidoNet Uplink, e9162100.pkt > ea7bc400.we0 6 06:42:58 cmd: zip -9 -j -q \ftn\outb\00690051.sep\ea7bc400.we0 \ftn\tmp\outb \e9162100.pkt

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)

The backslashes in the file name seem to be interpreted as escape characters and not as the directory/file name seperator.

Is this on a linux system?

--- GoldED+/LNX 1.1.5-b20180707

Could be...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Greetings Wilfred!

Wednesday August 03 2022 16:16, you wrote to me about an urgent matter!:

* Forwarded from area 'FIDOSOFT.HUSKY'
Hi Rick,

On 2022-08-03 06:36:06, you wrote to All:

7 06:42:58 Packing for 1:105/81 FidoNet Uplink, e9162100.pkt >
ea7bc400.we0 6 06:42:58 cmd: zip -9 -j -q
\ftn\outb\00690051.sep\ea7bc400.we0 \ftn\tmp\outb \e9162100.pkt

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)

The backslashes in the file name seem to be interpreted as escape characters and not as the directory/file name seperator.

Is this on a linux system?

no its on os2 or ArcaOs as it were... How or where can I get rid of the slashes? in hpt config the directories are correct, they exist etc.



----
Regards,


Rick Smith (Nitro)

... A job is nice, but it interferes with BBSing.
--- GoldED+/LNX 1.1.5-b20180707
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

Hi Rick,

On 2022-08-03 07:41:46, you wrote to me:

7 06:42:58 Packing for 1:105/81 FidoNet Uplink, e9162100.pkt >
ea7bc400.we0 6 06:42:58 cmd: zip -9 -j -q
\ftn\outb\00690051.sep\ea7bc400.we0 \ftn\tmp\outb \e9162100.pkt

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)

The backslashes in the file name seem to be interpreted as escape
characters and not as the directory/file name seperator.

Is this on a linux system?

no its on os2 or ArcaOs as it were... How or where can I get rid of the slashes? in hpt config the directories are correct, they exist etc.

Try a double slash \\ where you now have single slashes \ in your config file...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

Wednesday August 03 2022 16:49, you wrote to me:

* Forwarded from area 'FIDOSOFT.HUSKY'
Hi Rick,

On 2022-08-03 07:41:46, you wrote to me:

7 06:42:58 Packing for 1:105/81 FidoNet Uplink, e9162100.pkt

ea7bc400.we0 6 06:42:58 cmd: zip -9 -j -q

\ftn\outb\00690051.sep\ea7bc400.we0 \ftn\tmp\outb \e9162100.pkt

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)

Try a double slash \\ where you now have single slashes \ in your
config file...

Yeah that is what I first tried but them HPT complains about the \\... I need to find someone with a working config on os2 I think... I am probably missing something simple.

Regards,

Rick

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

Hi Rick,

On 2022-08-03 13:22:30, you wrote to me:

7 06:42:58 Packing for 1:105/81 FidoNet Uplink, e9162100.pkt

ea7bc400.we0 6 06:42:58 cmd: zip -9 -j -q

\ftn\outb\00690051.sep\ea7bc400.we0 \ftn\tmp\outb \e9162100.pkt

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)

Try a double slash \\ where you now have single slashes \ in your
config file...

Yeah that is what I first tried but them HPT complains about the \\... I need to find someone with a working config on os2 I think... I am probably missing something simple.

Have you tried putting the path names between quotes? Or specify them in the linux way with / as directory seperator? Maybe husky does an auto convert for those to OS2 directory seperators?

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

03 Aug 22 06:36, Rick Smith wrote to All:

Hello All!

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)
A 06:42:58 Error executing packer (errorlevel==12, permanent error)
1 06:42:58 Start packing...
4 06:42:58 EchoTossLogFile not found -> Scanning all areas
4 06:42:58 Scanning NetmailArea NETMAIL
7 06:42:58 Packing for 1:105/81 FidoNet Uplink, e9162100.pkt > ea7bc400.we0 6 06:42:58 cmd: zip -9 -j -q \ftn\outb\00690051.sep\ea7bc400.we0 \ftn\tmp\outb \e9162100.pkt

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)

This is a klibc problem which can be "fixed" by setting UNIXROOT to a non-existing path.

The better solution is to use watcom build of hpt or not to use arcmail at all.

'Tommi

---
* Origin: rbb.fidonet.fi (2:221/1)

06 Aug 22 08:36, Tommi Koivula wrote to Rick Smith:

The better solution is to use watcom build of hpt or not to use
arcmail at all.

hpt-wc.exe available here by freq.

'Tommi

---
* Origin: =========================>>>> (2:221/1)

Hello Tommi!

Saturday August 06 2022 08:36, you wrote to me:

* Forwarded from area 'FIDOSOFT.HUSKY'

03 Aug 22 06:36, Rick Smith wrote to All:

Hello All!

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)
A 06:42:58 Error executing packer (errorlevel==12, permanent
error) 1 06:42:58 Start packing... 4 06:42:58 EchoTossLogFile
not found -> Scanning all areas 4 06:42:58 Scanning NetmailArea
NETMAIL 7 06:42:58 Packing for 1:105/81 FidoNet Uplink,
e9162100.pkt > ea7bc400.we0 6 06:42:58 cmd: zip -9 -j -q
\ftn\outb\00690051.sep\ea7bc400.we0 \ftn\tmp\outb \e9162100.pkt

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)

This is a klibc problem which can be "fixed" by setting UNIXROOT to a non-existing path.

The better solution is to use watcom build of hpt or not to use
arcmail at all.

I have set unixroot in my toss.cmd , I have your watcom exe problem still exists, I will post my config.

Regards,

Rick

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

Hello Rick!

06 Aug 22, Rick Smith wrote to Tommi Koivula:

A 06:42:58 Error executing packer (errorlevel==12, permanent
error) 1 06:42:58 Start packing... 4 06:42:58
EchoTossLogFile not found -> Scanning all areas 4 06:42:58
FidoNet Uplink, e9162100.pkt > ea7bc400.we0 6 06:42:58 cmd:
zip -9 -j -q \ftn\outb\00690051.sep\ea7bc400.we0 \ftn\tmp\outb
\e9162100.pkt

zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)

^^^^
Looks like a seperator problem.


II.1.1 Overview

This is the standard way of compiling Husky source code on Unix-style
operating systems. It will also work on OS/2 if you have the EMX compiler and
a more or less complete chain of GNU tools installed. [...]

If you compile Husky in this way, the default path of the configuration file and other specialties will be compiled into your executables based onto your individual needs, and shared libraries will be used if possible to decrease hard disk space requirements and improve flexibility.


In my old OS/2 configs i have c:\dir\cfg pathnames. I don't know if letterless is supported but with external tools you have interfaces into other software that may not be able to handle mixed or incomplete path names.

I have set unixroot in my toss.cmd

I'm not on latest source but once there was a DIRSEP definition in huskymak.cfg.

For initial installations i recommend static builds. More diskspace usage, more memory usage, but easy transferable to other VMs.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)