Sorry for the typo in the third block, I should have tested it first, but you can fix it up yourself.

The second "if not exists" name and the "echo" name should match the "file=" name of the makelink call below it.

It's not the makelink command missing, it's one of the files, the makelink command should have spat out the name of the missing file, so i'll fix it later.

BTW: The C: path is always valid.


In the mean time try this modified script instead...


; ============== begin =============

failat 11

if not exists libpng.so
if not exists libpng12.so
echo "libpng12.so not found"
else
makelink soft link=libpng.so file=libpng12.so
endif
endif

if not exists libbz2.so.1.0
if not exists libbz2.so.1.0.4
echo "libbz2.so.1.0.4 not found"
else
makelink soft link=libbz2.so.1.0 file=libbz2.so.1.0.4
endif
endif

if not exists libz.so
if not exists libbz2.so.1.0.4
echo "libz.so.1.2.5 not found"
else
makelink soft link=libz.so file=libz.so.1.2.5
endif
endif

if not exists libz.so.1
if not exists libz.so.1.2.5
echo "libz.so.1.2.5 not found"
else
makelink soft link=libz.so.1 file=libz.so.1.2.5
endif
endif

; ============== end =============

Copy the following and put it in a text file.
Name that file; "Fix_SOBJS_Softlinks" and place it in
your sobjs drawer.

Then just cd to the sobjs: drawer from a shell and execute the script whenever you lose the softlinks again. (":>

I think I have all of them listed, if not add any of your own...

; ============== begin =============

failat 11

if not exists libpng.so
makelink soft link=libpng.so file=libpng12.so
endif

if not exists libbz2.so.1.0
makelink soft link=libbz2.so.1.0 file=libbz2.so.1.0.4
endif

if not exists libz.so
makelink soft link=libz.so file=libz.so.1.2.5
endif

if not exists libz.so.1
makelink soft link=libz.so.1 file=libz.so.1.2.5
endif

; ============== end =============

Actually you're kinda right Simon, I have an added path
to S: on my setup, but the default install places shell
scripts in the S:Shell directory and there is also a
path there by default.
So "S:Shell" is the best place for it.

If you want to find the command from anywhere, not just in
the amidock then you can try the script below.
Open notepad and paste in what's between ==== lines.

;===================================
.KEY FILE/A
.BRA {
.KET }

if exists ${appdir/{FILE}}
echo ${appdir/{FILE}}
else
echo "*"{FILE}*" Not found in cache."
endif
;===================================

Now save it as "S:??" (thats S: plus two question marks)
and also set the +s script bit with; "protect S:?? +s"
(or choose your own name)

Now an example, if you have IBrowse installed, then
from a shell, just type; "?? ibrowse"
It will tell you where it is, (or not).

Have a look at the include file; dos/startup.h
It shows how to start a basic dos process up without c-lib
startup code or argument parsing.

Using the workbench message you can fetch the arguments
by using; wb_msg->sm_NumArgs and wb_msg->sm_ArgList to
walk through the struct WBArg * array arguments and using wa->wa_Name to get the (icon.library) diskobject; dobj = iicon->GetDiskObject( wa->wa_Name );
Then you can use iicon->FindToolType() to fetch the individual tooltype strings you require.

Look around for some example code.

wait 5
echo $_RunTime

In a shell type this;

Prompt "%N.%S <%E>"

You will now get the command execution time shown
in the prompt string when the command returns.

If you want it permanently, set it up in the s:shell-startup.

I could live with dd.mm.yyyy, however my penchant for
symetry is being violated.

For example, my details and avatar currently show;
Joined: 2007/6/5 23:51
so when combined with the time as HH:MM it provides a
logical linear temporal unit weighting.

But if you want it as DD.MM.YYYY then the time is in the
wrong format and on the wrong side of the date.

I know i'm being excessively pedantic, but that's just me.

Anything sensible and obvious will do for an international audience.

dd.mm.yyyy is rather generic.

yyyy.mm.dd is better for collation, but is somewhat esoteric, however, it is unambiguous.

I have a test program I used during development to test the notification system, it is now here...

http://members.westnet.com.au/colinwenzel/notify_test_program.lha

Start it in a shell with the destination path to monitor
as the argument, it will start three types of notifications and report when any events occured that trigger a notification.

Let me know what happens for you...

One thing I find completely unacceptable is the format
for the "Last Post" date.

Can you please change that to be something remotely sane,
ISO format yyyy-mm-dd would be a good idea, but please
get rid of that idiotic American month-first nonsence,
it is just way too illogical to even be considered
remotely usable by a multi-country user base.

The only time you can realise it's that stipid format
is when you find yourself trying to figure out what
the 13th month is... (":?

@abalaban

include/exec/alerts.h

#define AN_AsyncPkt 0x07000004UL /* Unexpected packet received */

What are you running to get this. ??

@Templario

To the setpatch line in your startup-sequence,
change it to read;
SetPatch ADDCHIPRAM=2 QUIET

Also, in the program, make sure you turn off
both of these;
Settings->Graphics->15Khz Video
Settings->Graphics->Amiga Blitter

@Mrodfr

Use "Snoopy" from OS4depot.

@freddix

IDOS->Read() is not a void function.

IDOS->Read() n'est pas une fonction vide.

@Mrodfr

Since they are just tiny ascii text files, the 'E' bit should have been unset for semantical reasons, so now it is.

The old cache files will be updated as time goes by, or after about 180 days when they will be flushed out automatically if not used again before then.

And for the original poster, the comment field contains two
numbers, the first (hex) one represents the checksum of the text inside the file, the second (decimal) part is the week number when it was written, so it won't even refresh any more often than once a week, or unless the path inside changes, that's all those numbers represent.

BTW: the libraries, devices and such that are loaded by ramlib (which handles disk based loadables through OpenLibrary() and OpenDevice() ) are excluded from having entries created in the cache, just incase you were wondering.

@Slayer
> Please colinw, stay out of any of my future threads...

Not the sort of reply I was expecting while just trying to help you out, so maybe this link will be more usefull than pointing you at some decent backup hardware...
http://www.darwinawards.com/

@Slayer

I think just one USB backup drive would have been
quite enough considering....

1) You don't have any backups at all.

2) You disabled the warning requester in DirOpus.

3) You also selected 2 directories instead of 1
and in doing so have deleted 25 gigs of data.

4) You used a filesystem that currently has no recovery tools.

5) You deliberately formatted with NORECYCLED option so there are no backups of deleted files.


I'd love to help you, but I just don't know what else to
say or do for you, seeing that you intensionally created this entire disaster by doing everything possible to lose data,
and to make doubly sure that it is impossible to ever get any of your stuff back.

Sorry, but you can't un-cook an egg....

@Slayer

I think you need one of these.....
http://www.seagate.com/www/en-us/prod ... freeagent/freeagent_desk/

I have a 500GB one that works a treat on my SAM's