right now I am getting the following error message
unzip: cannot find either C:DBINBOUND188f5900.tos or C:DBINBOUND188f5900.tos.zip
my unpack statement looks like unpack "unzip -j -Loqq $a $f -d $p" 0 504b0304
On 2.2.2021 1.33, Michael Pierce : All wrote:
right now I am getting the following error message
unzip: cannot find either C:DBINBOUND188f5900.tos or
C:DBINBOUND188f5900.tos.zip my unpack statement looks like unpack
"unzip -j -Loqq $a $f -d $p" 0 504b0304
How is your "unixroot="? Try removing it before running hpt or setting it to point to some non-existing drive. By default Klibc tries to run
'unzip' via sh shell. Not via %COMSPEC%.
right now I am getting the following error message
unzip: cannot find either C:DBINBOUND188f5900.tos or
C:DBINBOUND188f5900.tos.zip my unpack statement looks like unpack
"unzip -j -Loqq $a $f -d $p" 0 504b0304
How is your "unixroot="? Try removing it before running hpt or setting it
to point to some non-existing drive. By default Klibc tries to run 'unzip' via sh shell. Not via %COMSPEC%.
Is this the reason why there are no "\" in the path?
right now I am getting the following error message
unzip: cannot find either C:DBINBOUND188f5900.tos or C:DBINBOUND188f5900.tos.zip my unpack statement looks like unpack
"unzip -j -Loqq $a $f -d $p" 0 504b0304
any ideas??
>> >> right now I am getting the following error message
>> >> unzip: cannot find either C:DBINBOUND188f5900.tos or
>> >> C:DBINBOUND188f5900.tos.zip my unpack statement looks like
>> unpack
>> >> "unzip -j -Loqq $a $f -d $p" 0 504b0304
>>
>> TK> How is your "unixroot="? Try removing it before running hpt or
>> setting it
>>
>> Is this the reason why there are no "\" in the path?
Did you mean changing in config.sys? We tried that it didnt change anything...
01 Feb 21, Michael Pierce wrote to All:
right now I am getting the following error message
unzip: cannot find either C:DBINBOUND188f5900.tos or
C:DBINBOUND188f5900.tos.zip my unpack statement looks like unpack
"unzip -j -Loqq $a $f -d $p" 0 504b0304
any ideas??
Replace unzip with echo and add a redirection >>
show_the_real_thing.txt. Then replace echo with pwd to see the real working directory. Oh wait, pwd should be there where the txt file is found.
A workaround would be to create a unzip.cmd script that set all path manually and use that unzip.cmd in the packer definition. Bad idea
because other tools could fail with the broken path too.
Regards
Kai
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 368 |
Nodes: | 16 (2 / 14) |
Uptime: | 86:35:08 |
Calls: | 7,895 |
Calls today: | 1 |
Files: | 12,968 |
Messages: | 5,792,010 |