techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

5.3K
active users

#fat12

0 posts0 participants0 posts today

Another bad retro diskette! At first glance, this one seemed pretty much gone. None of my disk imaging tools were able to read it. Windows Explorer just crashed.

Only a low level KryoFlux dump managed to uncover the physical cause behind this: A corrupt root directory beyond any chance of repair. Luckily, both the file allocation tables as well as most of the data clusters were still in good shape. I used a hex editor to manually recover all the files from the valid tracks. It worked!

I guess these games are nothing special, but it still made me happy to pull usable data and working files from such a destroyed file system!

Replied in thread

@torepang You forgot some more #cursedness:

- compiled against #MSVC and #Microsoft #Libraries, so it requires #VisualStudio on #Windows to be built and requires all apps to be linked against these libraries.

- no user accounts, everything runs on root with no password.

- SMF (Solaris) as Init & Config System.

- Keyboard is hardcoded German Neo-2 Layout.

- uses #LILO / #LOADLIN on a #FAT12 Filesystem for boot, requiring a #MSDOS Boot Floppy!

- Only supports #NTFS as filesysten.

- All manpages are in Simplified Chinese.

- System clock is local time, not Unix Time.

- Only supports #ISA & #PCI, not #PCIe or #USB!

- curl points to wget, wget points to curl.

- emacs points to neovim, nvim points to emacs.

- forced UTF-32 encoding fir everything.

- Filenames, Directories & Path must only contain Emojis and . (or / for paths).

- Files are not overwritten but instead a new copy is made and the latest version is symlinked to the original filename - like in Files-11 for VAX/VMS.
en.wikipedia.org/wiki/Files-11

...

- - -

Need some more ideas for a #cursed #Linux?

en.wikipedia.orgFiles-11 - Wikipedia
Continued thread

For anyone woundering "why do you use the latest @linux #Kernel release?"

Well, I want OS/1337 to be basically 'rolling release' in that I can't be bothered #backporting stuff and I just want to pull the #releases straight from said projects.

github.com/OS-1337/OS1337/blob

* Okay, I've not listed #syslinux & #mkdosfs and #dd which I used in making the #Floppy image but those basically don't really change much at all. We all know how #FAT12 works...

GitHubOS1337/build/0.CORE/build/sources.list.tsv at main · OS-1337/OS1337OS/1337 Project . Contribute to OS-1337/OS1337 development by creating an account on GitHub.

For now I'm only focusing on making something that generates FEFS24 images (24-bit pointers). That covers 99.99% of #Psion Flash and ROM SSDs.

I've only ever seen a handful of very early (1989) Type I Flash SSDs using FEFS32, and they were made by Psion themselves for the #MC200 and #MC400.

Once I've nailed FEFS24, FEFS32 will be much easier.

RAM SSDs use #FAT12, so that's a whole different ballgame. So far I've just used mtools to generate working FAT12 volumes.