The above video goes away if you are a member and logged in, so log in now!
You aren't the only one having this problems.
I think fmcb 1.3 still makes hdloader work ok on v9.
With 1.1b are you using ffgriever's runme.elf ? If not would you mind trying booting hdloader with it and see if it gives black screen (the one failing on 1.4+)?
I will give it a try this weekend...I'm pretty sure I messed with it, but don't remember what happend. Do I just get 1.1b installed and then run the runme.elf from usb or something, or do I get 1.1b ilnstalled and then replace an elf it puts on my mc with a renamed runme.elf?
Originally Posted by suloku
EDIT: My spare mc revived, so now I can do some tests.
1.1b does boot my hdloader games, but when I replace runme.elf with ffgriever's it doesn't (all test without a disc in the tray), so the problem is indeed caused by ffgriever's fixes. Now I wish he released the src for runme.elf, I'm gonna ask him for it.
1.1b should place a file called runme.elf (ulaunchelf I think). Replace it with ffgrievers program, which will boot some BOOT.ELF locations.
File and info here:
I would try myself, but one of my mcs seems to be corrupted or completely gone.
Last edited by suloku; 09-20-2008 at 05:30 AM.
I got out my MC with 1.1b on it. Launched ULE from cdrom in my chipped console. Browsed the Mc to BESLES-00000 MP/ folder where there was BOOT-FREE-OSD.ELF (my hdloader.elf) and a RUNME.ELF. Deleted the runme.elf and replaced with the newer runme.elf (from ffgrievers) and now it boots to a red screen on all versions. Before it would just boot to hdloader and even launched games from hdl in my V9. [I guess I should mention the V9 unit I've been trying this with does not read any disks, cd or dvd, so I never have a disk in the drive. This is why I want to be able to boot into hdl on this unit.]
Last edited by Chad Edward; 09-20-2008 at 02:26 PM.
Red screen means runme.elf couldn't find BOOT.ELF file at any location.
For what you said your former runme.elf was indeed hdloader itself.
ffgriever explained me that on v9+ consoles this is a normal behaviour, your problem is that the patches your hdloader has match a setup that considers a disc always being in the drive.
Only way to do that on v9 is either use an older version of fmcb which doesn't use ffgrievers cdvd fix, modify latest fmcb to don't apply the fixes, or the easiest, properly patch an hdloader for a no disc setup.
Well, also in my v9 I can run hdloader games if I leave the tray opened before running hdloader.elf file, in that case the games run normally. I don't know if that will work on a console with a dead laser (o without laser).
I'm positive the BOOT-FREE-OSD.ELF was the hdloader elf not the runme.elf. I renamed it and replaced the old one so hdloader booted...Never messed with the runme.elf until last night on that MC I used. So this newer runme.elf is looking for a BOOT.ELF? I guess that explains the red screen, because 1.1b didn't install anything named boot.elf, and doesn't make a boot directory either. I do believe I have one V9 that does read cd's, I'll try it with a disk in for the heck of it.
Originally Posted by suloku
I manually (in dos) patch my hdloader.elf myself. I am absolutely certain it is not any of the patches as I've tried them all and every possible combination and none at all. The only way hdl works for me without any disk in with fmcb is with the N for no disk seek (for mc booting into dev1; formerly only possible with a modchip as far as I know). Is there anyway to maintain the functionality of 1.1b as far as HDL goes but get the language thing fixed?
I'd be happy with that because I only want to boot hdl without using any disks.
I tend to forget what the patch is properly named, sorry if that confused you. The hdloader I use doesn't have that patch, it works ok form me. It should work OK withouth disc in any fmcb versions.
Originally Posted by Chad Edward
Easiest way right now for you to acomplish what you want:
Use the hdloader w/o the no disk seek patch and runme.elf 1.1a. Runme.elf boots boot.elf (not BOOT-FREE-OSD.ELF) on the following locations:
(where "?" is regional code: A, E, I )
Complicated way of achieving your goal:
At this point you may want to save space at the mc, so the best option is to use that hdloader (the one working withno disc) as boot.elf and use fmcb 1.4c with a DVDLPE from a slim console (you know, the 75kb ones).
This may or may not help:
I noticed that fmcb 1.3 correctly finds my MC Id and use it to aptly patch and generate an osdmain.elf file. In fact, if I use an HEX editor to check the osdmain.elf, I can find a 32-byte MC id after the 38 E0 47 4A AC 51 25 1E byte sequence.
Now, if I try and install fmcb 1.5, 1.6 or 1.7, the osdmain.elf is built with the wrong MC id and it gives me a BSOD on boot. Not sure if that is similar to your problem. My MC is an original Sony, made in China. The way I solved the problem was to copy the valid 32-byte MC id from an old 1.3 osdmain.elf file generated in this particular MC and replace it in the fmcb 1.7 generated osdmain.elf instead of the 32-byte sequence after the 38 E0 47 4A AC 51 25 1E bytes.
I finally had the time to mess around quite a bit with it this weekend. I took my old MC that has 1.1b on it and replaced the RUNME.ELF with a newer? one I had. I don't know if it is the one you requested I try, but it was downloaded on Aug. 24th and it's size on disk is 118,784 bytes (larger than the original) Then I added a BOOT directory to that MC and placed hdloader.elf in there as BOOT.ELF. Then placed that MC into my V9 and it does load to hdloader and successfully launches games, but it apparently doesn't include the language fix I needed. Then per your suggestion, I tried 1.7 again on my V9's and I actually can successfully launch games from hdl IF I have the disk tray ejected before I launch hdl itself. So what do you suppose causes this problem with a V9 and the newer versions of fmcb?
Originally Posted by suloku
The hdloader I use doesn't have the "stop cdvd drive motor on loading" patch, which is I think causes the problem in v9+.
Having the tray opened on loading may interfere with that patch (if hdloader was patched with it), that's why it works.