@X303

not tested but: That might be that Pipe in WiP5 and 1.5.2 must be setup differently (at least at command level) WiP5 Pipe:file but 1.5.2 Pipe:/file is the same... in WiP Pipe seems to be a "real" devise but in 1.5.2 Pipe is an assignment to PipeFS:

Pipe works, it is the redirection (from file? wheater it is a pipe or not) that does not!

Looks that not only the pipe doesn't work with arexx, but is broken in general.

Try as example -> download libogg & unpack. Do ' sh configure'. You might see something like: configure[35]: can't create pipe - try again.

Hi,

I have some good news:
http://vmwaros.blogspot.it/2014/02/enhancing-bridge.html

ArosX WIP5

Back to the Rx Say (mentioned some posts above) who gives no output...

Is this RX SAY thing somehow connected with pipes?

because when I do this

Shell.1
Echo >pipe:/hi "Hello World"

Shell.2
Echo <Pipe:/hi

Shell.1 returns directly, nothing gets out from Shell.2
and the c:pipe command does not seem to work either.



/Late Edit

Due to differences in the Assign list (Opus4) there is only a Pipe: visible, in 1.5.2 there is PipeFS: (they differ in how they show up)

Due to this I tried Echo >Pipe:hi "Hello World".

File hi shows up in Pipe: but when doing Echo <Pipe:hi nothing shows in CLI, Investigating Pipe: in Opus4 reveals the file, it may be copied to Ram: (removing file from Pipe:) the hi file in RAM: could be read...

BUT when trying Echo <Ram:hi outputs nothing

So when Echo >Ram:hej "hello" then Echo <Ram:hej shows nothing either...

I did a bugtrack, but I will remove it because it does not seem to be the Pipe:

//Later Edit
It is NOT (I think) the redirection mechanism because
Echo >(CON or RAW)://///Wait "Hello" shows the correct text...
Echo <CON://///Wait returns without something, Copy CON://///Wait * did not work either (for testing) as wildcards are not allowed

//Last addition
But Echo >* "Hi" works, Type Pipe:hi works and Echo "`Type Pipe:hi`" gives a result similar to Echo <pipe:hi... So I guess it is possible to work around it.

My guess: There is a shared routine which all commands (and perhaps even Rexx) use to handle redirection to a console... This routine is for the moment wrong... Should be (for those who have insight) to track down common code used by commands and rexx... I guess one should start to look there.

azvareth wrote:
Quote:
the 'issue' is known.

Quote:

It has to do with rmb right click popup-menus. There's something broken in that departement (on aros at least).
It happens on other occasions as well (try fiddling right-clicking on an open window when an icon on the desktop is active for example).

The issue is already present in the bugtracker.

I did reply as of to ease the burden on bszili so that he does not look into it (again).

Quote:
try removing the lha datatype _only_. the new archive datatype works ok (just checked)

oh and, paolone, please be aware that the archive datatype includes all files ending with:
- .lha
- .lzh
- .lzx
- .tar
- .tar.gz
- .tar.bz2
- .tgz
- .zip

so do not use another datatype for those, if you want to keep the archive datatype working for these files.

PS: i have no idea why dopus5 refuses to start the tool of an archive when in icon mode. It completely freezed up dopus5 :/

Quote:
Already tried removing the lha datatype and replacing the new archive type with the old. Didn't help at all.

@paolone:
i still need to check the .iso's but at least i got proof as of why it fails:


Hence, it does not even try to read the archive default icon, only the lha one (which is missing) ergo it fails.

It seems that you installed both the archive and the lha datatype. I suspect that the lha datatype is taking precedence over the archive datatype.

(just to make sure: it could also be an internal error not recognizing properly or reading archive datatype wrong or something of that nature).

PS: I did not tried this myself, but you should be able to fix it by either removing the lha datatype (and see if that helps) or by adding the lha default icon. i have no insight of what you want to use in your final release.

for more information as of the why, please read this thread and especially pay attention to this post as well as this post.

I do hope it is my setup but with wip5 i keep noticing things like the attached picture.

The picture is from hexviewing a file with dopus4 (wanderer desktop) and doing a search, but i also noticed this behaviour sometimes with OWB (url dropdownbox).

anyone else bumped into it ?

Attach file:

---

  (0.00 KB)

Seeing paolone's and x303's reply there seems to be two issues:
1) default icon for files without icon uses wrong tool (which did work in regular 152)
2) adding an icon to a file which had none, does not add the proper tool. (which was also wrong in regular 152)