Problem mounting CF0 using resident compactflash.device

[Tallguy58]

Hi again.
Firstly great job on the compactflash.device.

I created a custom Kickstart 3.2.3 rom using this guide.
Flashed the Amiga 600 MantiCore FPGA with a 1MB containing compactflash.device, fat95 and ptable.library.
Renamed the integrated files with a _bak extension so they would not load up during startup. (Just in case)
Renamed the line in the following mountlist from Filesystem = l:fat95 to Filesystem = fat95.
Rebooted the system.

If you insert a fat32 formatted CF Card and then reboot it appears on the workbench as per normal.
If you insert a CF Card after the workbench has loaded this does not happen.
Workbench reports this device as mounted but when running the command DIR CF0: states that there is No Disk Present.
I have to run the following commands ASSIGN CF0: DISMOUNT and MOUNT DEVS:DOSDRIVERS/CF0 to access the CF Card.

Using the standard Kickstart 3.2.3 rom, with files compactflash.device, fat95 in their respective directories with the standard mountlist this problem does not occur.
I can insert a CF Card after the workbench has loaded and works very well.

FYI, I used the full 020 versions of the above mentioned files when creating the kickstart rom.

Thank you,
Alexander.

[pulchart]

I do not think renaming Filesystem = l:fat95 to Filesystem = fat95 is going to work. It must be a valid path (even if fat95 3.22 is in ROM). It will choose a ffs as default intead. What handler is in use can be verified by:

version cf0:

[Tallguy58]

Yes I understand but it seemed to work, as I stated above.
The compactflash.device and fat95 are resident so it should not matter if I have l:fat95 or fat95.
Unless there is a problem with my mountlist?

Thank you.

[pulchart]

I see. Can you try this compactflash.device 1.43-dev 18-05-2026? It drops an extra "just in case" guard I added that was silently unlinking ROM resident fat95's notify registration on the first card event. Just speculation for now.

[Tallguy58]

I tried your new 1.43-dev device driver and it didn't make any difference.
The system still hangs on boot up.
If I revert back to the standard kickstart 3.2.3 512kb rom the system freezes when mounting CF0: for the first time.
This is when the telmex atapi device is plugged in.
If I reboot without anything plugged in, A OK.

FYI, the previous 1.41 device driver did not have this problem.

Thank you.

[pulchart]

Pre-1.42 didn't probe PCMCIA at boot so on older versions there can't be a boot-time freeze caused by any attached card.

Just to make sure we stay aligned: you opened two separate issues
#46 (this ticket) about CF card mounting and
#47 about the Telmex CD/DVD interface.

Your latest reply here (on #46) describes the Telmex freeze. I need to keep them separated to debug them properly.

So for #46 specifically, with the Telmex CD/DVD interface NOT in the slot at all does CF card mounting/unmounting work correctly for you?

Let's keep all Telmex CD/DVD discussion in #47