Andreas Meyer wrote:
> > How do you mount them? With DOSDrivers in DEVS:DOSDrivers?
> Yes, I created two Icons and put them in DEVS:DOSdrivers.
Well, you can have them there. You only need to make sure that
Miami is started in s:startup-sequence before it gets to
the mount-line.
> I took them out and when I doubleclick them, I get a "Host cannot be
> reached" if the PC is not online. I dont get this requestor when they
> were mounted per dosdrivers.
If Miami was started you most likely would have.
> I�ll try to start Samba together with the drivers from the
> interface-events instead from within the "Events"-table in Miami.
That will work. A simple AmigaDOS script like
mount pix:
will work if you have a dosdriver named pix in sys:storage/dosdrivers.
Oh, don't forget to do protect miami:scripts/online.miami +s or
whatever your script is called.
> With 'BindDrivers' the dosdrivers are loaded
Binddrivers does no such thing. It loads drivers that are
placed in sys:expansion. On top of my head I can't recall
anything that actually uses that directory.
>after the libs: for P96
> are assigned and although I get a PAL-screen. AmigaOS is still
> mysterious for me after all this years. In the startup-sequence there
> is no assign for L:. Nevertheless the handlers are loaded and the
> c:-commands are executed. How where they initialised? By resident
> commands and libraries in the ROM?
Almost all system-assigns have a default-value. Libs: c: l: etc and
is initialised by the ROM. You only need to have assigns for them
in startup-sequence if you want to have say l: somewhere else.
You would have to change that rather early in the startup-sequence
if you want to avoid trouble though. I think it's only t:, env:
and clips: that needs to be set explicitly.
> Just curious... I wonder why the handler is looking for the stack and
> not the drivers.
Drivers for what? The network-card? As for why it's looking for the
stack I think it is because it's the easiest way (and Samba does
need it...).
All you need to do to check if a tcp/ip-stack is running is to
try to open the socket library from within your program and
check the return value. If you get a failure the stack hasn't
been started since the library is created in ram upon load.
It doesn't exist before that.
/Jonas
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
