The above video goes away if you are a member and logged in, so log in now!
Path in SYSTEM.CNF to file on ISO9660
Path in SYSTEM.CNF to file on ISO9660 –
I have made DVD with ISO9660, UDF1.2 and Joliet tables.
All file names on disc contain characters which is supported by Joliet fs. In CNF file I have used a path to program from ISO9660 table (I not sure but I think CDVDMAN doesn't support any other fs, right?).
files on disc:
cdrom0:/APP/unofficial LaunchELF v4.21.elf
Content of SYS CNF
This DVD doesn't boot (freeze on PS2 Logo or return to OSDSYS). Why?
BOOT2 = cdrom0:\APP\UNOFFICIAL_LAUNCHELF_V4_21.ELF;1
VER = 1.00
VMODE = PAL
The second problem:
I have launched uLELF from mc0:/ (DEV1 or FMCB), insterted above compilation, drive "passed on" disc. But when I lunched ulelf from this disc and enter to Browser (ulelf browser) he freezed on black screen.
V6, modded by Ripper 2 Gold.
Im sorry for my English.
Because the names of the files must be with uppercase only and without free space on them.Making it in that way when PS2 load the SYSTEM.CNF he start to search for "UNOFFICIAL_LAUNCHELF_V4_21.ELF" not "unofficial LaunchELF v4.21.elf"
My mistake. I thought that those 3 tables refer to the same file.
All three tables do refer to the same physical files and folders, though they use slightly different names for them, as the names you used in composing the disc image are adapted to follow the differing rules of each filesystem table.
Originally Posted by Berion
For the booting it is important that the BOOT2 path in SYSTEM.CNF uses the correct pathname for the filesystem used by the Sony boot routines, which i too think is ISO9660. But the original versions of that filesystem do NOT allow for long names like you used. Such names will be abbreviated to the traditional 8+3 norm (8 char filename + '.' + 3 char extension). And to avoid any confusion about this I strongly recommend to always use '8+3' uppercase_only filenames for the boot elf, and any other file/folder to be accessed by Sony code. This way all three tables contain an identical name entry for that file. For your case a suitable filename would have been "ULEV4_21.ELF", which still contains all the relevant information.
I have myself composed homebrew DVD ISOs using long mixed_case names for some stuff (mainly subfolders and emulation ROM files), and this causes no problems at all for the booting, as long as the boot file itself uses the '8+3' standard. In uLE and most other homebrew software you can access the stuff using the Joliet (long mixed_case) names, though I suppose some software may suffer from '8+3' and upper_case limitations, if their drivers only 'see' the ISO9660 names.
As for why you got the BSOD in opening FileBrowser though, I am completely clueless, as the first screen in the FileBrowser does not require access to any physical media. It is just an internally generated list of the names of possible devices, not accessed in any way for making this list. So you could have utter garbage in the disc tray (or any other device), and that list should still work perfectly!
Are you sure that it was on initial entry to the FileBrowser that the BSOD occurred, and not rather when you attempted to open one of the device names in that primary list ?
Please repeat that test again, both with that version and with the new v4.25, and report on your results again.
Btw: The "Ripper 2 Gold" chip you have should in fact be a clone of the DMS3 chip. I used to have the same chip too, in one of my previous consoles.
Best regards: dlanor
Fault of this strange black screen is my mistake in LAUNCHELF.CNF (misc -> różne/).
Thanks for help and answers.