#27 Neek2o no longer boots directly from bootmii@boot2 (WD My passport drive)

[Anonymous]

Originally created by: wever1... (code.google.com)@gmail.com
Originally owned by: overjoy.... (code.google.com)@gmail.com

*Please report only one problem per issue.

What rev. of Neek2o is used?
[r85] and onward

What nand is used (4.1/4.2/4.3)(E/U/J/K)?
4.3E

In which way is Neek2o started (Priiloader/Channel/HBC)?
bootmii@boot2.

What steps will reproduce the problem?
1.compile and install rev87 or later of neek2o on a western digital 500GB 'My passport' USB drive, on a wii with bootmii@boot2
2.Plug it into the wii (turned off)
3.start the wii

What is the expected output?
neek2o starting

What do you see instead?
Televsion: black screen
USB LED: no reading
wii drive: continuous blue light flashing roughly every 0.75 second

Please provide any additional information below.

-this is HD specific. Until (and including) rev84, everything worked well on my drive. However: the same setup on another HD (rev84 of neek2o, same wii, same nand, same SD card and the same partitioning & cluster size on the HD) gives the same error as described.
-the workaround for boot2 users is to rename the \bootmii folder and use priiloader to load the neek2o channel on startup (bootmii @ ios users can just set it to that).
-this issue (and the workaround) also happens to gbatemp's Pissapino (source: http://gbatemp.net/topic/313314-neek2o/page__view__findpost__p__4307558)
The "It can coöperate with bootmii. It doesn't launch automatically every time on a bootmii as boot2 wii." also seems to indicate that this is a known issue.
-(personal theory) since the flashing of the DVD drive points to 'something missing' and the type of USB-drive is important, I'd say this has something to do with the initialisation process of the drive. The tested drives (that I know of) are USB-powered, so they only draw power after the wii is started. My guess is that neek2o asks for the files on the USB drive before the drive is ready to reply them.
(this would explain why starting neek2o AFTER the wii is started works without issues).
-> perhaps all that is needed to solve this issue is a slight delay when bootmii is started (note: creating a bootmii.ini file containing a bootdelay didn't work). It's not even impossible that a code improvement in rev85 or 85 (which I was unable to test, unfortunate enough) ironically causes the error.

[Anonymous]

Originally posted by: wever1... (code.google.com)@gmail.com

Update: on [r91] beta 2 (not publicly released), this issue seems to be gone with my main drive.

NOTE: this version has issues with priiloader

[Anonymous]

Originally posted by: overjoy.... (code.google.com)@gmail.com

Gonna close this one for now

Labels: -Type-Defect Type-Other
Owner: overjoy....@gmail.com
Status: Fixed

[Anonymous]

Originally posted by: Gwaeraur... (code.google.com)@gmail.com

I am having this issue with [r96]. It previously worked with no revisions installed, but because I had long loading times I was advised to download the latest revision. Then when I downloaded the latest through BootMii and installed it I got a black screen with a blue blinking light. Initially I thought "Maybe it's building a cache", but 2 hours later it's still doing it.

Mine is also a WD My Passport Drive.

(sorry for previous message post then delete. I had a typo in revision #)

[Anonymous]

Originally posted by: Gwaeraur... (code.google.com)@gmail.com

After downgrading it to "UNEEK+DI neek2o rev84" it was able to load again. It took about 2 minutes to load like it did before, and it was able to do so even with the EmuNAND in a subfolder. This time pressing the "Home" button and returning the the Wii Menu works to bring it back to the EmuNAND, but it takes just as long. On the downside, it froze up on me twice.

[r95] worked, but the first time using it and it just turned the wii off and then loading times were twice that of what it was in either [r84] or without any revisions installed. It also decided to load the "press A" screen that I long since turned off on my wii when loading up normally. Games loaded OK, but the Wii Memory Management menu is broken (which previously worked with no revisions installed). I then tried [r94], but it had the same exact issues. Finally I tried the oldest revision on the list - [r64] - and here it also turned off on first load, but then it took 2 minutes to load. There was no background music on the menu, but I was able to use the Wii memory menu to delete saved games from the EmuNAND. Unfortunately returning to the Wii Menu is broken in that revision for me.

All in all, I would have been better off with no revisions at all. Load times were two minutes, returning to the Wii menu was broken, but everything I needed to work did work.

[Anonymous]

Originally posted by: overjoy.... (code.google.com)@gmail.com

Is the partition you use for uneek2o the first and set active?
Also is the clustersize 32k?

2 mins is way to long for boot, unless your hdd is fragmented or really full

Why are you using a closed issue in the tracker that certainly has nothing todo with yours. I'm asking this, because I normaly never check issues again when I know they are  solved

[Anonymous]

Originally posted by: Gwaeraur... (code.google.com)@gmail.com

Oh, I added a comment here because the issue I had with the latest revision was exactly the same as the one reported so I thought it was a resurfaced issue and that I should use the same thread instead of starting a new one. Should I start a new post with all the problems I am having?

Mine is a 1 TB Western Digital HDD. Formatted to FAT32. Cluster size is 32 KB. There is only one partition on the hard drive and only one drive is inserted (no USB hubs at this time). I use the same drive for Wii and Gamecube backups with USB Loader GX 3.0 along with video files inside a "Media" folder so it is getting pretty full, but is defragmented. I made sure that the EmuNAND on the hard drive was never touched by USB Loader, and instead have a separate EmuNAND on the SD card to handle the Wii Game saves. If it's just because the drive is filled to capacity, how much free space is required for it to work effectively?

When the EmuNAND had no games on it the load time was 30 seconds. When the games are on it load time is consistently just over 2 minutes. (I am using Snort48+ to sort titles). When I used a copy in USB Loader GX the load times were instant, but the DLC was broken there which is why I installed Neek2o. Since load times were affected by number of games on the EmuNAND I wonder if maybe it's not caching?

With the later revisions I can return to the Wii Menu through the home button, but that also takes a full 2 minutes (even if I press it while already on the home menu) with the absolute latest taking twice as long to load initially, but only 2 minutes going back to the Wii Menu. Also, on most of the later revisions it the ability to delete saves from the EmuNAND is broken. The whole thing crashes just going into the menu, but I think it was [r70] that had this work for me.

On the bright side, all my games work with 100% compatibility and even though it takes 2 minutes to load the menu loading the games from the menu is very fast.

[Anonymous]

Originally posted by: overjoy.... (code.google.com)@gmail.com

I don't know of how many games we talk over here, but 2 mins sounds like a lot. but yeah.. The more games are installed the longer it takes for boot, but thats on real nand the same.

It also sounds like you have priiloader on your emulated nand.. If it's there, remove it. Later revs can't cooperate with it and it slows down booting. You don't need it anyway.

[Anonymous]

Originally posted by: Gwaeraur... (code.google.com)@gmail.com

For the number of games causing a problem I don't think that could be the reason because with only a disc channel and "Snort48+" it took 30 seconds each time, which is not how long a true NAND takes.

Oh, I didn't realize that PriiLoader would cause a problem! Unfortunately, I don't see it's name listed on the EmuNAND and I don't know it's Title ID. What exactly do I need to remove to delete it? This might actually be what the problem was!