English Amiga Board - View Single Post - OSX High Sierra file system anomalies WB1.3

17 April 2018, 13:54

Hi All,
I'm having filesystem weirdness.
With a fresh DH0: install of wb1.3 (from amiga forever) - if I duplicate the WB Empty folder using WB's duplicate pull down menu option, I get a Copy of Empty directory and a Copy of Empty.info file as expected.
When rebooting, the files are still visible using the dir command, but do not display in WB. I am using the 1.3 kickstart from the Rudz kickstart archive and have tried fresh installs of FS UAE versions 2.8.2u1, 2.8.3, and 2.9.7dev2 64 bit versions.
Any clues?

EDIT: I have tried cleaning up the icons, it doesn't seem to be an issue of overlapping icons.

Any newly created icons are no longer visible in WB after reboot - though the .info files remain visible from the command line

EDIT2:
Snapshotting said icons resolves the issue - but new snapshots mess with other newly created icons, causing them to disapper.

EDIT3:
Switching to A1000 emulation (from A500) has resolved the issue.

17 April 2018, 13:54	#1
Nutjob Posts: n/a	OSX High Sierra WB1.3 Icons disappearing Hi All, I'm having filesystem weirdness. With a fresh DH0: install of wb1.3 (from amiga forever) - if I duplicate the WB Empty folder using WB's duplicate pull down menu option, I get a Copy of Empty directory and a Copy of Empty.info file as expected. When rebooting, the files are still visible using the dir command, but do not display in WB. I am using the 1.3 kickstart from the Rudz kickstart archive and have tried fresh installs of FS UAE versions 2.8.2u1, 2.8.3, and 2.9.7dev2 64 bit versions. Any clues? EDIT: I have tried cleaning up the icons, it doesn't seem to be an issue of overlapping icons. Any newly created icons are no longer visible in WB after reboot - though the .info files remain visible from the command line EDIT2: Snapshotting said icons resolves the issue - but new snapshots mess with other newly created icons, causing them to disapper. EDIT3: Switching to A1000 emulation (from A500) has resolved the issue. Last edited by Nutjob; 18 April 2018 at 09:37.