TWO DRIVES???
çddf,faa,afa,aaf,faf,ffa,aff
¾     WHY SOMETHING DON'T WORK
          ON TWO DRIVES?

²           written by:
    Ranger of Ladybird Design



¹Well...   sometimes  some  productions
don't  work  on  two  drives,  what we
doing  in this situations?  We fucking
authors,  we  fucking coders.  There's
not  a  big problem if something don't
need  a  lot disks changes, but what's
happened  if  there's  a  lot of disks
changing,  and you've two disks drive,
but you can not use it!?

¢Coders    do    it    sometimes   some
productions  don't  work on other than
Df0:, by why?  Because this is easier?
NO!   No  way!   But  why  they do it?
Hmm...  I really don't know, but maybe
you know, eh?

Coders!   First  of  all, if you doing
something in the dos, for example disk
magazine,   then  there's  very  easy!
Imagine this situation, you've article
name:

Art001: dc.b  "Df0:articles/001",0

But  why  the  hell you do it?  Please
change Df0:  to disk name, and there's
no more problem!

Art001: dc.b  "Dk1:articles/001",0

If  you  change  it for this then this
file  will  be  load from disk, called
"Dk1",  and  it's dosen't matter where
is this disk!!!

¶But  if you must do it something in no
dos  then...   this  is  also so easy!
Give  me explain this...  At first you
must  make  a little test of your disk
drivers, and if test is okay then just
load  from  external drive!  Where's a
problem?   Eh,  maybe  you  can't make
this test?  Okay, here's a little code
routine for you:

DriveTest:
      move.l $4.w,a6
      moveq  #0,d0
      lea    ResourceName(pc),a1
      jsr    -498(a6)
      move.l d0,a0
      tst.l  52(a0)
      beq    DF1_okay:
Only_Df0:
      rts

DF1_okay:
      ;...include your loading
      ;   routines in this place!

ResourceName:
      dc.b    "disk.resource",0

Okay,  I  hope  never  again  look for
something  work only on Df0:, and is a
lot of disk changes!  hehe!  See Ya!


						Ç08