CF0 icon information help

[ScottC2010]

I have A1200 with Kickstart/WB 3.2.2
I have a CF0 in DosDrivers - it works with fat95 in the l: directory but it doesn't pick up the fat95 I have in ROM (1MB 3.2.2 Custom ROM with WB.lib, icon.lib, FFS, compactflash.device, card.resource and fat95 in the extended part)

I go into the icon information of CF0 and it just has ACTIVATE=1 and nothing else so i am wondering how it is managing to pick up fat95 in L: but not the ROM (fat95 resides in the extended part of my ROM)

I tried Filesystem=fat95 below ACTIVATE=1 or should it be Filesystem=ROM:fat95? - but does not work

There is a button with gears on the icon info screen which says mountlist but does nothing - does anyone know what it is as i can't find any information on this

[Channel-Z]

When you edit CFO in a text editor what does it look like paste the results here may help get an accurate answer.

[Nor Bert]

Are you sure FAT95 is correctly "inserted" into the kickstart?
Is it visible in SCOUT or SYSINFO, for example?

Show the CF0 mountlist?

[FOL]

First I would say, is it seeing the extended part of ROM?
Do you have Workbench.library and icon.library in Libs: If so rename name them to !workbench.library and !icon.library. Reboot and see if it demands icon or workbench library. If it does, then its not seeing extended part of ROM.

Besides, I'm sure I read some where, its not a good idea to put FAT95 in rom, due to the code wanting to write back to itself?

[ScottC2010]

Originally Posted by SnoopDOS

When you edit CFO in a text editor what does it look like paste the results here may help get an accurate answer.

I've just tried this and I see l:fat95 - I have just set it to fat95 but the drive then disappears, but at least I can go on from here and try the next answer - thank you!

[ScottC2010]

Originally Posted by FOL

First I would say, is it seeing the extended part of ROM?
Do you have Workbench.library and icon.library in Libs: If so rename name them to !workbench.library and !icon.library. Reboot and see if it demands icon or workbench library. If it does, then its not seeing extended part of ROM.

Besides, I'm sure I read some where, its not a good idea to put FAT95 in rom, due to the code wanting to write back to itself?

WB.lib and icon.lib are in the extended rom - i have already removed them and everything boots fine

Maybe you could be right and fat95 isn't able to be used in ROM - unless someone else has tried this

[ScottC2010]

Originally Posted by Nor Bert

Are you sure FAT95 is correctly "inserted" into the kickstart?
Is it visible in SCOUT or SYSINFO, for example?

Show the CF0 mountlist?

I can see it in the ShowConfig (I don't have sys info etc on it yet but will do that soon)

It's in Residuals:
Type: Unknown
Priority 0
Version 3
Address: BBE38916
Flags -

[ScottC2010]

I can't see it in SysInfo

I can though if I go into shell and type version fat95 and it lists the version of the module on the rom (3.10)

[FOL]

Originally Posted by ScottC2010

WB.lib and icon.lib are in the extended rom - i have already removed them and everything boots fine

Maybe you could be right and fat95 isn't able to be used in ROM - unless someone else has tried this

It works in ROM fine, just pointless having it in ROM in my opinion as you can't boot from it on boot. You will always need external files to mount it.


Just very odd your issue. As its working when not in using ROM'ed filesystem.

[No.3]

I will never understand why people still use Fat95 when there is CrossDosFileSystem...

[Nor Bert]

Use the old CF0 mountlist (correct the access paths) , and you can't have fat95 and compactflash.device on the disk.
If the Amiga sees the card in FAT32, it will mean that you did the ROM right.

[derSammler]

Originally Posted by No.3

I will never understand why people still use Fat95 when there is CrossDosFileSystem...

Sounds like fat95 was there first, but it was not. fat95 was created because CrossDOS sucked.

Also, people have the right to choose, don't you think?

[ScottC2010]

Originally Posted by Boing-Ball

A couple of things…

1)… What did you use to create the Extended ROM with? Capitolines RatGui

2)… When You type info in a shell, is this showing CF0: as mounted? When I type cf0: it returns unknown command but it does show as mounted when you double click the cf0 in dos drivers

3)… Revision of Mainboard? I’m away now till Sunday so will look when back

4)… Nothing to do with the Gayle Reset issue? Have you tried Cardpatch and Cardreset in your Startup-Sequence?

not tried as fat95 in the l: directory works it is just when you point to fat95 in rom

[ScottC2010]

Originally Posted by No.3

I will never understand why people still use Fat95 when there is CrossDosFileSystem...

Will have a look at crossdos, I remember using it for floppies and worked well

[ScottC2010]

Originally Posted by Nor Bert

Use the old CF0 mountlist (correct the access paths) , and you can't have fat95 and compactflash.device on the disk.
If the Amiga sees the card in FAT32, it will mean that you did the ROM right.

Do you have a link to where I can get the old mountlist

[CCRider]

Originally Posted by derSammler

Sounds like fat95 was there first, but it was not. fat95 was created because CrossDOS sucked.

This changed since 3.1.4, AFAIK.

But then, some people still insists on KS 3.1 on beefed-up Amigas, so...

[Nor Bert]

Originally Posted by ScottC2010

Do you have a link to where I can get the old mountlist

As you wrote. Mountlist you have on your drive

Originally Posted by ScottC2010

I have A1200 with Kickstart/WB 3.2.2
I have a CF0 in DosDrivers - it works with fat95 in the l: directory

[No.3]

Originally Posted by derSammler

fat95 was created because CrossDOS sucked.

you really should invest some time and read the AOS 3.1.4 and AOS 3.2 release notes (as well the "backstage information" provided by Thor)...

[ScottC2010]

I am already using the CFD33

I think i will just remove fat95 from rom and put in L: - at least that works as i need it - but thanks for trying to diagnose!