| Comment by: cha05e90 (84.134.59.171) | At: 11 Dec 2011, 10:12 | File version: 2.5 |
Sent the crashlog to your GMail account.
|
| |
| |
| Comment by: OldFart (145.53.166.27) | At: 11 Dec 2011, 09:46 | File version: 2.5 |
@cha05e90:
Ai! I'm rather surprised to hear this.
Yes please send me a crashlog!
|
| |
| |
| Comment by: cha05e90 (84.134.30.103) | At: 10 Dec 2011, 20:47 | File version: 2.5 |
Ui - crashes with "Recoberable Alert" on both systems (SAM440ep/PegasosII, OS4.1u3) after closing the program with "Cancel". Afterwards the systems are unstable/unusable (cold reboot needed. Should I send you a crashlog?
|
| |
| |
| Comment by: OldFart (145.53.166.27) | At: 10 Dec 2011, 12:36 | File version: 2.5 |
Yep! I know that feeling. I too hate, really HATE, it when archives unpack and place their contents hither and tither at the unpacking location, which btw, for me is 'T:'. So, all in all I want this aspect solved first thing, but NOT in a manual way. I want to have the computer do that for me. Automagically. Without me interfering. I hate, really HATE, interfering with processes which should be performing of their own accord. ;-)
|
| |
| |
| Comment by: anonymous (83.149.3.78) | At: 10 Dec 2011, 10:14 | File version: 2.5 |
But users hate (really hate) create directories manually when unpack something :)
|
| |
| |
| Comment by: OldFart (145.53.166.27) | At: 09 Dec 2011, 10:35 | File version: 2.5 |
Ah, it's you again, eh? ;-)
What I meant to say is, that I have not found an easy and integrated way to achieve this. I hate, and i really HATE, a manual approach. That manual part is in the creation of a directory with a non-fixed (i.e. the '_V2.5') part in its name.
I may build a little tool for just doing that, now I think of it...
|
| |
| |
| Comment by: whose (46.115.32.208) | At: 08 Dec 2011, 22:23 | File version: 2.5 |
Huh? Too hard to make up a project directory and lha this? ;)
Just make a directory called "WBMakelink_V2.5" (e.g. in RAM:, or cd to the "Projects" directory, where the wbmakelink_V2.5 directory resides), copy executable and other files there and give the shell a
"lha a -rx wbmakelink.lha WBMakelink_V2.5"
and if you wnt to give it the directory icon, too, give it a last
"lha a wbmakelink.lha WBMakelink_V2.5.info"
I did this with all my projects until now, not very hard to do ;)
|
| |
| |
| Comment by: Thematic (80.186.9.136) | At: 10 Nov 2005, 15:09 | File version: 1.0a |
Well, SFS does not yet implement file links does it? Or was it hard links; I
just downloaded wbmakelink.lha and confirmed that the links are file links and
not something else, from the readme. So with FFS it should work fine.
|
| |
| |
| Comment by: FuZion (82.36.50.54) | At: 10 Nov 2005, 01:30 | File version: 1.0a |
Why's that? I like the sound of this. Why would SFS cause a problem?
|
| |
| |
| Comment by: Thematic (80.186.9.136) | At: 09 Nov 2005, 19:21 | File version: 1.0a |
Can this be used on SFS volumes? I don't think that would be wise..
|
| |
| |
Audio (347)