HDL 0.7e and Amplitude?

[pill]

Hi,

I read on several threads that the getstat/fileops (SOTC) match made Amplitude work, with no mode (apparently someone under the nick dabbage pointed that out).

Oh so happy I was! I tried my 0.7e fully patched and prepared for some music mixing off the HDD.

Though I only got to the first Loading screen and nothing happens. Nothing at all, no HD activity, it just stalls.

I tried various combinations (1+3+Suidoken, 1+3+6.. ) and even MDMA4 HDL but none of them work.

Can anyone actually confirm that it works?

[TnA]

Write me a PM and I´ll send you a PM of a Version, that 100%ly works.

Which Version did you have?

[pill]

I have the 1.7GB DVD, NTSC/UC I guess.

Am I the only one wanting to play this game or?

edit: I don't know what to think now...

[MasterSun1]

Umm, it definitely does work, as it was the first game I tried after installing 0.7e on my memory card.

[ps2dragon]

edit: Okay, I got confirmation by someone on irc that it's not true. Amplitude does not work with HDL .7e.

That's not true at all, I got it working fine with just the Suikoden V Patch. I originally tried with no MODES and it didn't work, but after enabling the Suikoden V Patch it works fine. I patched my uncompressed hd loader elf with lonwern's 0.7e patch. Been playing it a few times now, and still no problems...

[pill]

Okay then I guess we have to sort out the matter.

What version of the game are you saying is working? PAL, or NTSC/U? and when you said "first it didn't work", did you get a black screen or did it hang at the first loading screen?

I tried putting only the Suikoden V patch, it still freezes at the loading screen. Am I out of luck?

[ps2dragon]

Okay then I guess we have to sort out the matter.

What version of the game are you saying is working? PAL, or NTSC/U? and when you said "first it didn't work", did you get a black screen or did it hang at the first loading screen?

I tried putting only the Suikoden V patch, it still freezes at the loading screen. Am I out of luck?

I have the NTSC U/C version (SCUS_972.58). I can't get it to freeze anymore even when turning off the Suikoden V patch (No MODES Enabled). Since I can't replicate the problem I'm not 100% sure what it was, but it was either freezing during the intro movie, or getting a black screen after trying to start the game.

Maybe you and all the others who are having this problem have a corrupted image file?

I'm attaching everything you need to compare my game to your game:
- Amplitude_FileList.txt = My Amplitude FileList (already sorted in ascending order)
- Amplitude-ISO.sfv = Compare your ISO to my ISO. Should be in the same folder as your ISO when executed (of course).
- Amplitude-Extracted_Files.sfv = Compare your extracted ISO files to my extracted ISO files. Should be in the same folder as your extracted files when executed.

You will need hkSFV installed to run these .sfv files. You could also use QuickSFV, but I hear that program doesn't work if the file names, between the two files your comparing, are different. I'm not sure what other disadvantages there might be from using QuickSFV, so I just use hkSFV to be safe.

[pill]

Thanks for providing these files.

Both .sfv checks match 100% (surprisingly enough, especially on the iso ). So the issue lies somewhere else.

The next step is to make sure the .elf I use is good. It works on all other games, so I *think* it's not going to be a problem either, but just to make sure, can you tell me what patches you applied to your HDL? and at what speed you're running it?

I have another idea as well:

<storyteller mode ON>
First i had a 120GB drive. Hdl_dumb was limited to 28_bit drives (no larger than 120GB).

When I first sent Amplitude to my new drive (a WD 250GB one), HDL_dumb reported a wrong size, but I still had enough room to put the game, so I did.

After that, and only after that, did I did i remove the 28_bit limit.

Seeing the game froze, I was wondering if it got put on the HD the wrong way, so I deleted it and sent it back (since then I've been doing that like 20 times ). But no matter what, the game is still in the same location as the first time on HDL_dumb game list, as if the partition that got created the first time is always re-used, and the game is not going on the bottom of the list, as I would have expected it would go.

And annoyingly enough, I can't put several copies of the same game, since I uses toxicos partition naming (SLxx_xxx.xx) from day one and hdl_dumb says "game already exists".
<storyteller mode OFF>

So maybe my problem lies there. I'll try on my brother's ps2 tonight, and will see how it goes.

Did you use hdl_dumx to transfer the game, or winhiip?

---
EDIT: The same iso on a different HD with winhiip still hangs at the loading. I think I have to try another HDLoader. Or it's my PS2 that's not *compatible* with it (lol).

[ps2dragon]

The next step is to make sure the .elf I use is good. It works on all other games, so I *think* it's not going to be a problem either, but just to make sure, can you tell me what patches you applied to your HDL? and at what speed you're running it?

Here are the settings I used when using lonwern's HDL 0.7e patch:

• /C = Compatibility options update (press SELECT to access)
• /B = Bigger game list (fit more titles on screen)
• /L = LBA 48bit patch (allows full use of HDDs up to 2 terabytes)
• /IS = Patch splash image (512x448 24bit BMP, 32bit TGA & interleaved RAW)
• /IM = Patch main image (512x448 24bit BMP, 32bit TGA & interleaved RAW)
• /IB = Patch button image (128x64 24bit BMP, 32bit TGA & interleaved RAW)
• /IC = Patch colors (/IC colors.txt, see readme)
• /IT = Patch texts (/IT texts.txt, see readme)

I believe the default speed, since I didn't choose one, is "UDMA4 (66.6 MB/s)".

First i had a 120GB drive. Hdl_dumb was limited to 28_bit drives (no larger than 120GB).

When I first sent Amplitude to my new drive (a WD 250GB one), HDL_dumb reported a wrong size, but I still had enough room to put the game, so I did.

After that, and only after that, did I did i remove the 28_bit limit.

I don't understand what you mean by removing the 28-bit LBA limit. Was that done on the HDD or in HDLoader after you patched it, or do you mean the setting/options in WinHIIP?

Seeing the game froze, I was wondering if it got put on the HD the wrong way, so I deleted it and sent it back (since then I've been doing that like 20 times ). But no matter what, the game is still in the same location as the first time on HDL_dumb game list, as if the partition that got created the first time is always re-used, and the game is not going on the bottom of the list, as I would have expected it would go.

Yea, if your trying to eliminate the problem your having, then putting the game on a newly formatted HDD would be a better option.

And annoyingly enough, I can't put several copies of the same game, since I uses toxicos partition naming (SLxx_xxx.xx) from day one and hdl_dumb says "game already exists".
<storyteller mode OFF>

So maybe my problem lies there. I'll try on my brother's ps2 tonight, and will see how it goes.

"uses toxicos partition", what do you mean? Are you using HDLoader or ToxicOS? The only way you could be using anything related to ToxicOS is if you have a DMS modchip of some type. If you mean using the "Toxic OS" option in WinHIIP's options "Override Application Mode", or Formatting the drive in ToxicOS format, then don't do it unless you have a DMS Chip that uses ToxicOS. Those options are only for ToxicOS not HDLoader. The modes that show up for ToxicOS are not the same as the modes for HD Loader, at last that is what I (can't test it).

Did you use hdl_dumx to transfer the game, or winhiip?

I used WinHIIP v1.7.6, which is what I always use.
---

EDIT: The same iso on a different HD with winhiip still hangs at the loading. I think I have to try another HDLoader. Or it's my PS2 that's not *compatible* with it (lol).

Maybe this has something to do with you trying to use those ToxicOS options or formatting the HDD for ToxicOS. You should start off on a fresh drive formatted with WinHIIP in "HDLoader 48bit" mode.

[pill]

Thanks for the command line switches. I'll do exactly the same as you on a fresh uncompressed elf and see how it goes.

About the partition naming, it's nothing really. hdl_dumb uses a hdl_dumb.conf file that basically says how hdl_dumb should behave. toxicos_naming says that hdl_dumb (hdl_dump GUI) should store the isos as ToxicOs can recognize them. It's a compatibility option, nothing to be scared of (it just stores each game by its SLUSxx.xxx naming, hence prevents several copies of the same game). It's how it was set by default. No big deal then I guess.

I use a fully patched HDL 0.7e, not ToxicOs, I have a totally unmodded ps2

My HDD is formatted at HDL 48bit. All my other games work flawlessly. It's just that particular game that seems to be playing tricks on me.

My brother took his hdd back with him, he'll try to boot the game on another ps2 in a couple hours. We'll see if it behaves the same.

I'll let you know.

------------
EDIT:

I tried the exact same HDL as you, ps2dragon. Still hangs.
It hangs on my brother's ps2 with his HD as well.

I'm lost. Completely.