I thought I make them available so that everyone who's interested can play around with them. These are the system files required to create bootable discs for the FZ-35S (may work for the FZ-21S as well), including the required layout files for the sdk, which I created myself. Note, however, that these files are quite useless unless you know exactly what to do with them, and how. ;-) http://gtw3do.retro-net.de/misc/FZ35_System_Files.rar
Awesome, thanks. 2 questions. I'm assuming you need to make whatever it is your booting into operafs 1.) Does the sdk come with a tool to make opfs? 2.) Do you think you'll release the tool you wrote to make opfs?
What does the structure of a bootable disc look like? Is it something like mount/cdrom/system.m2/ and mount/cdrom/executable or maybe mount/cdrom/system.m2/executable ?? Is the system.m2 *required* to boot, or is only required if you're using folios? Am I correct in thinking that the m2 uses ELF's?
Wow thanks. So I guess my picture of how opera is supposed to work is not correct. I thought portfolio was stored in the rom. Where does it actually reside? The rest of the process makes sense, as I can see if the systemstartup script where it goes about mounting the drive. I guess my original question about the executable was rather vague. If I have launchme.m2 Can I just drop it alongside the system.m2 directory or do I have to actually put it *in* the system.m2 directory? Or maybe a better way to phrase is what is the relative path to launchme.m2, would it be "d:\launchme.m2" (if we were to look at it ms-dos style)? Also, can I infer from your post that filenames are case sensitive? Do you know how drivers were supposed to interfaced for programming? I understand that things were accessed through portfolio, but like with the hard drive. Did 3do include an api for accessing it in the m2 dev kit?
Another utility to convert to/from the Opera file system has been released: http://altmer.arts-union.ru/3DO/3do_utils.htm I haven't tested it yet.