Diskimage.device/SFS problem...(solved)

Hello,

I tried to install WW7 (four *.adf disks). Unfortunately I could not open them because disks were "uninitialized" or sth (ghosted icon). I thought that maybe my diskimage.device is not ok and installed (os4depot) a full package. Everything went fine but after restart a problem occured...after welcome screen...

Crash log for task "IDF1/SmartFilesystem 1.290 "
Generated by GrimReaper 53.5
Crash occured in module SmartFilesystem at address 0x018801E4
Type of crash: DSI (Data Storage Interrupt) exception

Register dump:
GPR (General Purpose Registers):
0: 018801DC 58D8BEB0 00000002 00000000 592F17DC 00000005 59098214 590C31C0
8: 00000001 00000064 00000018 59163831 0BCDC482 00000000 00000000 00000000
16: 02270000 7FE67A50 02270000 59063DC0 00000000 00000000 02007C00 02007C00
24: 5FCAF66C 5FC9C170 00000001 59163831 00000000 00000000 5FF659B0 020A9824


FPR (Floating Point Registers, NaN = Not a Number):
0: 0 0 0 0
4: 0 0 0 0
8: 0 0 0 0
12: 0 0 0 0
16: 0 0 0 0
20: 0 0 0 0
24: 0 0 0 0
28: 0 0 0 0

FPSCR (Floating Point Status and Control Register): 0x00000000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0002D030
Condition (cr) : 0x28422024
Instruction Pointer (ip) : 0x018801E4
Xtended Exception (xer) : 0x20000003
Count (ctr) : 0x0181633C
Link (lr) : 0x018801DC
DSI Status (dsisr) : 0x00000000
Data Address (dar) : 0x00007232



680x0 emulated registers:
DATA: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x018801E4 belongs to module "SmartFilesystem" (HUNK/Kickstart)

Stack trace:
native kernel module SmartFilesystem+0x00021624
native kernel module SmartFilesystem+0x000180dc
native kernel module SmartFilesystem+0x0000190c
native kernel module dos.library.kmod+0x0002295c
native kernel module kernel+0x0003bd20
native kernel module kernel+0x0003bda0


PPC disassembly:
018801dc: 7c7d1b79 mr. r29,r3
018801e0: 40a200f0 bne+ 0x18802D0
*018801e4: 81627230 lwz r11,29232(r2)
018801e8: 3b000001 li r24,1
018801ec: 7fc3f378 mr r3,r30

System information:

CPU
Model: AMCC PPC440EP V1.3
CPU speed: 799 MHz
FSB speed: 133 MHz


I have renamed diskimage.device (LoadWB with no startup-sequence) and with some messeges (unable to mount IDF0, IDF1......) my system starts.

Two questions:
1. How to revert it, what did I wrong?
2. Why adfs were "uninitialized", others reported the files are ok na had no promlems? I tried to mount them with DiskImageGUI and Shell...

Looks like you edited IDF1 (and probably others, too) to use SFS instead of OFS/FFS. ADF files are not formatted with SFS. That's the reason why they show as uninitialized for you.

I did not edit IDF1/IDF0...
OK, downloded and installed diskimage package again->DSI after reboot.
Hmmm, IDF0 and IDF1 deleted from devs/dosdrivers->no DSI during start.When run by clicking, no DSI but after inserting adf, disk is uninitialized....

Check for files in devs:dosdrivers without icons and see if you have a devs:mountlist file. Check the tooltypes they should be:

ACTIVATE=1
DEVICE=diskimage.device
UNIT=0

Make sure UNIT is the same as the IDF number and the default tool is C:Mount

@mr2

Is the line "MODULE Kickstart/FastFileSystem" included in your SYS:Kickstart/Kicklayout file and not commented out?

Maybe Diskimage could read the first bytes of a disk file and mount the correct filesystem automatically.
Just an idea.

Thanks everyone

This quote fits perfectly to the problem:

"Two things are infinite: the universe and human stupidity; and I’m not sure about th’universe!"*

Salass00 was right, of course. And the worst part is, that was the second thing I wanted to check out...and I FORGOT to do it! I'm getting old, old and stupid
Thanks again, now it works OK.


*The quote is attributed to Einstein