CF0 not mounting from startup-sequence

[gertsy]

I've never really worried about this issue on my A1200 as I only need to mount my PCMCIA CF Card reader when I use it but I looked at it today and can't see why it isnt mounting from the startup-sequence.
I'm using Torsten Jager's (luv that name) PCMCIA CF Card compactflash.device v1.27 (2009)
Works fine when I mount the mountlist manually or fire up the .info with c:mount being the default tool.

BUT .....

For some reason my s:/startup-sequence which is running :
"C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)"
Is not mounting the device..  I have to admit I'm lazy and haven't looked to deeply.  FAT95 driver issue ?

Any help appreciated.

LOL intrusive smiley face....

[motorollin]

What happens if you type the mount command from startup-sequence into a shell?

--
moto

[fitzsteve]

Why not just drop CF0 into Devs/Dos Drivers?  (Then it should auto mount)

Its probably in Storage/Dos Drivers Now?

[motorollin]

If I understood the OP correctly, it's already in DEVS: but doesn't auto-mount for some reason.

--
moto

[Matt_H]

Check the tooltypes. There might be a Mount=0 or an Enable=0, which should be changed to 1.

[gertsy]

Check the tooltypes. There might be a Mount=0 or an Enable=0, which should be changed to 1.

I thought you might have had it Matt_H. But it has an "Activate=1"

'ello Moto!!  If I do a mount from the shell she pops up like a bought one.

@fitzsteve It's in Dos Drivers already.  

BTW, My CD0: mounts fine as well.

Running the cmd from the startup-sequence in a shell fails to mount...  hmm syntax?

scratch scratch..

[motorollin]

I thought you might have had it Matt_H. But it has an "Activate=1"

'ello Moto!!  If I do a mount from the shell she pops up like a bought one.

@fitzsteve It's in Dos Drivers already.  

BTW, My CD0: mounts fine as well.

scratch scratch..

Is it definitely in DEVS:DOSDrivers rather than SYS:Storage/DOSDrivers?

[gertsy]

Is it definitely in DEVS:DOSDrivers rather than SYS:Storage/DOSDrivers?

Yep. It would seem its the cmd string not working as suggested.  Running the full cmd from the shell fails as well: C:Mount >NIL: DEVS\DOSDrivers\~(#?.info)
Note: I used back slashes here to stop smiley face conversion..

[motorollin]

So if you type the following into a shell, what happens? Any errors?

C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)

And what about:

Mount DEVS:CF0

And failing that

Mount CF0

--
moto

[motorollin]

Note: I used back slashes here to stop smiley face conversion..

You can also open and close a formatting tag between the colon and the D to stop it being identified as a smiley, while still seeing the correct text printed

--
moto

[gertsy]

So if you type the following into a shell, what happens? Any errors?

a) C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)

And what about:

b) Mount DEVS:CF0

And failing that

c) Mount CF0

--
moto

a) No Errors, quick flash on the HD light
b) Can't open file DEVS:MountList
c) Works

[motorollin]

a) No Errors, quick flash on the HD light
b) Can't open file DEVS:MountList
c) Works

Ok, the problem seems to be that CF0 only has an icon in DEVS:Dosdrivers, but no actual mount list. The icon contains enough info to mount the device when you double click the icon or mount cf0:, but the mount command in startup-sequence mounts everything except icons, so it never gets mounted.

The solution - create a mount list for the device in DEVS: Dosdrivers and it will mount automatically. Alternatively, add "mount cf0:" to startup-sequence.

--
moto

[gertsy]

Ok, the problem seems to be that CF0 only has an icon in DEVS:Dosdrivers, but no actual mount list. The icon contains enough info to mount the device when you double click the icon or mount cf0:, but the mount command in startup-sequence mounts everything except icons, so it never gets mounted.

The solution - create a mount list for the device in DEVS: Dosdrivers and it will mount automatically. Alternatively, add "mount cf0:" to startup-sequence.

--
moto

The file CF0 is the mountlist,,, yeah ?
My understanding of the tilda? ~ is like NOT, so as you wrote the command mounts anything thats not a .info file.
Let me try the cmd in a shell without the NIL redirect.

[motorollin]

The file CF0 is the mountlist,,, yeah ?
My understanding of the tilda? ~ is like NOT, so as you wrote the command mounts anything thats not a .info file.
Let me try the cmd in a shell without the NIL redirect.

Yes, CF0 is the mountlist and CF0.info is its icon. The icon alone can be enough if the tooltypes specify the info required and the default tool is c:mount. You're right, the tilde means "everything that's not an icon". But because, I suspect, your CF0 is only an icon, it gets ignored by the command. You can prove the point by typing "dir DEVS:Dosdrivers" into a shell, and if you've got CF0.info but not CF0, then the problem is as I explained.

--
moto

[gertsy]

I got it.  You put me on the right track.  I had an old mountlist for my CDRW which had an error.  DOSTYPE = _ needed a number.  As I don't use the CD Writer on my A1200 I just banned it to storage.

Bang !.  CF0: automounts on boot fine.

The things that come back to you once you give some deserved attention.  just needed to get myself into "debug" mode instead of user mode; a habit of the old.

Thanks for the help Moto, and all.

Cheers and have a great Christmas, or Holiday for those who don't partake.