BB Navi install on 10k....please kill me.

Yes, the system driver update is also required for the SCPH-18000. Although it has a newer ROM, the ROM does not support its CXD9566R SSBUS I/F (I.e. it was likely a direct copy of the ROM
for the expansion bay model).

The card with the system driver update can be used for saves. Just save your data normally.

Of course it would be frustrating - you are trying to make the hardware do something that it cannot do. It has nothing to do with the PS2 or interface used, so changing the console would have no effect.

You wrote that you could not format the disks in uLaunchELF, on your SCPH-37000. But does uLaunchELF indicate that a HDD is connected? If not, please ensure that you put on a jumper and set the jumper to MASTER.

 

I formated the maxtor in ule but the seagate did not give me the option and this was only on the 10k. I have not run ule on the 37000. I guess if i can get the 1.0 util disc to run on the 37000 I could try to install it and see if the mem card would transfer to the 10k. And yes i have everything connected right on the 10k it just fails at 13% of the install.

 

Sorry, but I missed the part where you got it installed with your 37k. Congratulations!

Since you just could not install the PSBBN on your 10K, perhaps it has something to do with your discs. Which discs do you actually have, and which ones are actually burned copies?

Perhaps, you should confirm if your 37K is able to format the disks with uLaunchELF.

If you cannot get a copy of the system driver update installed, you could also simply install FMCB on your 10K.
The system driver update will only be installed if your console is a 10/15K.

 

I actually already had an internal drive for the 37000 for years that worked it is the one with the extra content. All of the Navi discs are copies. I Can get .30 and .20 to boot on the 10k, .32 and .10 are not working. The 10k has FMCB installed. The 10k also has not been able to boot a copy of the 1.0 utility disc.

 

Perhaps, the problem is that the copied discs are unable to read some files properly. After all, the 10K is old and you used burned discs.

 

I dunno it can read dvd9 even, I did just get a new laser for my 30001r so I might pop it in the 10k and see.

 

Being able to read pressed discs, does not mean that burned discs will be read equally well. There are several factors here, like the quality of your discs, the condition of your optical block (laser) and the quality of the burn.

The optical block from a SCPH-30001R is not compatible, if it is a SANYO SF-HD7.

Anyway, since you have successfully installed something onto the HDD with another console, why not just try it out on your SCPH-10000? If you already had FMCB installed for the SCPH-10000, with the SCPH-10000, then it should boot the PSBBN on the HDD unit.

 

There is a 400c in the 10k and the new laser i got is a 400c. Since the .30 and .20 installs fail at nearly the same point I doubt it is the laser I am starting to think thr pcmcia aspects are bad. What do I need to do with fmcb to fire up navi? Does the initial polling on boot up allow for it? Still doesn't answer all our question about this dev drive vs retail deal.

 

I don't know what you mean by "polling". But FMCB will initialize the ATA interface and boot whatever that is on it (the PSBBN, in your case).

It is possible for the network adaptor to be faulty. It seems like a common fault is the PCMCIA connector not being soldered properly to the PCB.
My old adaptor had that problem, although I didn't manage to have it fixed.

You installed something on it, so it should be identical to the retail one. It would make sense anyway, given that the HDD unit inside has the same model number as the retail one.

 

It runs Navi properly so I am guessing the pcmica must be ok. Have not tried the new laser to read the discs. It is curious why the install fails but everything works fine when you install it on another ps2.

 

Given that the HDD unit is fine, it should have just been unable to read your burned discs properly. The fact that it was unable to boot some of them, further illustrates this problem.

As you replaced the optical block before, it is not impossible for the callibration to be a little off. When SONY replaces the optical block, adjustment is done with some software .

 

SCPH-10000, SCPH-15000 and SCPH-18000 will need the memory card "System Driver". The utility disc will refuse to format the HDD or install the software if it fail installing the System driver on these units.

A tad annoying but oh well. 18k has updated kernel (fixed PS2Exec() ) so you could boot FFXI from a disc without need the memory card, at least.

 

If I remember correctly, the PS2 update disc (drivers and stuff) was for bugs in the ps2 kernel (such as things like this) and these bugs were removed on the worldwide releases of the bios, (the scph-3xxxx and afterwards) and that's why you don't hear about the ps2 update disc, other than the fact of it not updating the actual bios, just installing to the memory card, and the fact that the scph-1xxxx models using the bb unit and not the PS2 internal HDD.

 

I wouldn't say bugs. More like they changed mind about what the PS2exec() function was supposed to do when they thought they would need to be able to launch ELFs from within encrypted containers within apps (for booting crap from DNASLOAD, for example) and for that to work they have to patch the kernel.

That difference on what the PS2exec() function (it executes an loaded to RAM elf file) does is exactly why HD LOADER doesn't work on the SCPH-10000.

That isn't just a update disc. It's the HDD utility disc, which formats and installs the Magic Gate signed MBR the PS2 should boot from. It also happens to install the driver updates which give the early bios the capability of booting from a harddrive (it can't do it without the drivers as it doesn't know how to talk to the harddrive hardware by it's own).

For example the SCPH-18000 has the updated kernel but it can't boot the harddrive without the memory card drivers.

 

Other than providing patches that update the Protokernel's localization support (I.e. timezones) and missing deinitialization in ExecPS2, it also solves the inability of the Protokernel OSDSYS to pass arguments to the update.

There weren't really any actual bugs that mattered because the BOOT ROM was just a boot ROM, rather than an actual BIOS.

Speaking of bugs, the expansion-bay model cannot actually stop itself from booting a bad HDD. :/