Conference hydra::amiga_v1

    When both disks are in, does the Workbench show two disk icons, or only
    one?  If it's only one, then AmigaDOS really believes the disks *are*
    identical.  There are several known problems with having two identical
    disks online at once, some of them rather nasty.  Many disk copiers
    will modify a tag field in the disk header to avoid this situation, but
    some do not.  

    AmigaDos will modify the disk,I believe it's the time in microseconds
    that will allow it to tell two volumes with the same name apart.
    Turobcopy seems to make a virtual copy of the original. However
    id diskmaster can tell them apart,but Sid can't then it has to be
    something else.Could it be Sid does not look at the entire volume
    name.IE: It truncates the volume name before it reaches the byte
    that is used to tell the difference between volumes,or it simply
    does not read that info.
    							bill

    
    RE .1
    
    With both disks inserted, AMIGA DOS has 2 icons up on the screen.
    I believe it recognizes them both.  I realize that DOS sometimes
    gets confused here but I think this on is SID based.
    
    Frank
    

I suspect the problem isn't that the two disks have identical disk ids
(a disk id is the volume label plus the time in microseconds when the
volume was labeled).  The problem probably is that SID only keeps track
of the disks by label.  Since the label is just an ASCII string, it
doesn't contain enough information to differentiate between the two disks.
So, AmigaDOS just accesses the first disk in its list of disks that
has the given name.

The solution is for SID to really access df1: if you say access df1:.
It shouldn't say, "df1: is labeled mydisk:, so I'll access mydisk:
instead."

I've been playing with SID the last few days and like what I see so far
but I having a problem with NewCLI (actually Shell as stated in the docs).

When I open a NewCLI from within SID I lose my PATHs that were defined
in my startup.  It only has CURRENT and C: defined.  Outside of SID if
I open a new shell I have all my PATHs I defined.

Funny thing is this has always happened when I used UMast and I thought
it was just a quirk with UMast.  Now it happens with SID I suspect I
must be doing something wrong.

Can anyone shed some light on this for me?


Thanx,

...Ed

    I noticed the same problem with all versions of SID, even when there is
    a PATH statement in shell-startup.  BTW, MYMENU does the same thing.
    
    Also, has anyone gotten the floppies to display their directories in
    the window(s) upon insertion?  
    
    mark

>    I noticed the same problem with all versions of SID, even when there is
>    a PATH statement in shell-startup  BTW, MYMENU does the same thing. 

    I haven't found a problem.  Here is the line from my SID.Config
    (I use the ARP Shell).
    
    NewCLI=c:NewSHELL "NEWCON:0/100/640/150/AShell"
    
    and in s:Startup-Sequence
    
    Resident CLI L:Ash SYSTEM pure add; Activate ARP Shell
    Ashell From S:Shell-Boot
    
    Hope this helps
    Peter

I had to put a STACK 20000 (or so) command before starting up MyMenu
in my startup-sequence. Also, I added a 2 second wait after LoadWB abd startup 
of MyMenu

John

Re: .7

Thanks, I try this.  I too have ARP 1.3 installed but have not made ASH
resident.

I played with this problem yesterday and managed to resolve it a slightly
different way.  This may be of interest to those not running ARP as I suspect
it will work without it as well.

What I did was to create another S:Shell-Startup called S:SID.Shell-Startup 
which is a copy of the original but I've added my PATH command.  Then within
S:SID.config, change the CLI command to:

NewCLI=c:NewShell "NEWCON:0/0/640/200/SID's Shell" FROM S:SID.Shell-Startup

This corrected the PATH problem.  I suspect that SID is not correctly picking
up the PATHs from WorkBench the way a CLI started from WorkBench does.

...Ed

    Howdy SID 1.06 users,
    
    I am fooling around SID and I must say it is an excellent programme.
    It can do much more than other similar utilities like DiskMaster.
    
    I would gladly send my contribution to the shareware IF I can get 
    it to work properly.  But perhaps I did something wrong when 
    I installed it?.
    
    My bug is that about 1% of the time, only when I seek a directory,
    or a sub-directory, the screen go black.  The system "appears" to
    keep going, but it is hard to say.  It is not related to any particular
    directory, it happens as well on reading the hard disk or the DFx:.
    I tried to modify the stack size, up to 128Kb... no luck.
    
    The "fix" is to Ctrl Amiga-Amiga... Quite anoying if you were uploading
    a large file for the past hour and a half.
    
    I have a 1 Meg agnus, 5 meg of memory (8-up), A2090A/scsi and ST hard disk,
    in a B2000.  I run clockDJ and Virusx4.  Also an XT-bridgeboard is in
    the system.
    
    Anybody ever had such experience with this program? 
    Is yours working perfectly?
    Any known fix?
    Should I send my share and pray for an update/fix?
    
    Vince.

    Hi Vince,
    
    So how cold is Canada ;')
    
    I have the same problem with SID.  It is apparently a known bug if you
    have SID order your directories first then the files.  Try setting the
    switch in the config file "SeparateDirs=NO".  This resolved the problem
    for me.  There is supposed to be a new version in the works that is
    WB2.0 compatable and hopefully resolves this problem.
    
    
    
    Cheers,
    
    ...Ed 

    Hi Ed,
    Long time no see...
    
    Yes, pretty cold today  ;^(
    
    I'll try this and surely send my contribution if it works OK.
    I'd like the WB2.0 version.
    
    Nice earing from you,
    
    Vince.

    Hi all,
    
    	Using SID V1.06 I have not been able to get arc'ing or unarc'ing to
    work. This is on all type of archives (ARC, ZOO and LHARC etc.). SID
    displays the text "ERROR: Could not create new CLI for process!".
    
    Does anyone else have a similiar problem, or better still a solution to
    this problem?
    
    Chris

    Hi again,
    
    	Please ignore .14, problem fixed.
    
    I didn't have NEWCON: mounted. All works OK now.
    
    Chris.