- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,661
- Country
your syscheck is good.
try to set the IOS to 58 in the settings, it could help with detecting the drive.
Settings>Loader settings>Loader's IOS : 249 --> 58
keep the "game ios" to 249.
exit and reload the loader. it should now use IOS58 on boot.
it id didn't work, let me know.
you can edit the config manually
set the last option to : http://nintendont.gxarena.com/banners/
Manually, like on PC.Manually like on my PC or can I do it from within the loader? (No access to my system at the moment so I can't check it for myself right now)
Thanks.
Manually, like on PC.
(or maybe WiixPlorer text editor)
that option is not available from the loader.
It's stable for me, just wanted to point that detail about the power off menu on vWii. BTW I'm using all my old config files, maybe is that it?Cyan said:Ah? very strange. I tested it and only "shutdown" and "cancel" button were there. the themes shouldn't matters, it's detecting Wii or WiiU using the same function everywhere in the loader. Maybe it doesn't work for you? and maybe you are not the only one?
did you notice any instability other than the button still present? sj33 reported issue with missing game's titles.
Maybe there's really a memory issue and wiitdb is not read entirely..
I got missing titles for emuNAND, but I thought it was my Emu which was corrupted (the game doesn't work)
Well a user from the chat told me that the developer which was leading the vWii neek2o support suddenly left leaving the project on its current stage. So they don´t know if vWii neek2o will ever be implemented.
That user was not very well informed, OverJoy still has more plans with Neek2O but due to circumstances he didn't really had a lot of time (read almost no time) to work on it...
I am not making any promises here but hopefully we will see some new things @ Soon (lol, i felt like working this pun in)
Well at least you could clear up whatever information was mislead. Is it possible to read wbfs games off an ntfs partition if it's stored on a different usb HDD for example if I use a USB Flash Drive for my Uneek2O+DI setup and keep all of my games on a NTFS USB HDD would DI still read them? or would loading a usb loader be the only way to load games from NTFS under Uneek2o+DI
That user was not very well informed, OverJoy still has more plans with Neek2O but due to circumstances he didn't really had a lot of time (read almost no time) to work on it...
I am not making any promises here but hopefully we will see some new things @ Soon (lol, i felt like working this pun in)
That makes sense.Thanks for the reports
cheat codes for neek are not implemented yet.
Look at my blog in my signature to see what's working and what's not.
Both actually..Exiting neek ends on black screen, or exiting the game played on neek?
Uh that must be it, during my testing here and there with no results I kept going back and forth with the "Return To" option so I must have forgotten to mark it as "Off" when I finally got it working, thanks.If you are using "return to" -> OFF, then it returns to system menu.
if you are using "return to" -> anything other than OFF (meaning it's ON), it's currently force a reload to a channel installed on neek with titleID "NK2O".
if you don't have the NK2O installed, it will probably freeze on black screen.
the NK2O channel is used to exit neek and return to real NAND.
- launch game -> neek -> autoboot channel -> exit game -> reload NK2O -> exit to real NAND (reboot the console) -> if you have priiloader to return to USBGX it will reload it automatically.
Then, you didn't update to the latest version.
"boot/standard" is the old name, and you can't set it to 58.
You can find the latest version in my signature (1246).
replace the file on your SD card.
if you don't use the SD card files, then it's an issue.
The full channel is not updated anymore.
uninstall the full channel wad (titleID ULNR), and install the forwarder wad (TitleID UNEO).
It shouldn't.and this is bad.
it means sneek can still access real NAND.
unless it's a neek feature, but neek should never access real NAND. it's part of it's purpose to be 100% sandboxed.
game notification works like that:
when launching a game, a temporary file is written with the game name and the current time.
When you launch System menu next time (probably only on reboot, not if you shutdown) the system menu checks for temporary file and calculate the time difference from current time-launch time = play time, and write it to board menu.
in order to have sysnand write the playlog, the temporary file need to be present on the /nand/temp/ folder
but if you launched neek from HBC, nswitch doe not know your game so it can't write to NAND.
once sneek is launched, you select the game and the sneek system menu write the temp file on /sneekNAND/temp/
when you exit the game and return to sneek system menu, it checks the file and create a log on sneek's system menu board.
When you exit sneek by using nswitch (or neek2o channel), it reboot the console and you shouldn't have any temp file on your realNAND/temp/
what you can check :
in sneek, launch a game and exit. Look on the sneek's board if you have the playlog. if it's not present then the temporary file is not present in emuNAND/temp/ folder.
if not, exit to real nand by rebooting, and see if it write log again. it's bad if it does.
Very bad if you use neek on vWii, as it means vWii is still accessed and tempered by neek and a brick can occur. Knowing there's no mean to restore backup on vWii, it's really bad to use sneek/uneek/neek2o on vWii.
Are you sure you didn't boot using an USBLoader with playlog setting enabled?
in that case, the loader writes the temp file on real nand before launching neek.
when you reload real nand system menu, you get your "autoboot game" listed as played, even if you played many other games while in neek.
"played for 23h59" is the limit.
either you shutdown and reboot more than a day later, or the date used in the temp file was incorrect.
Maybe the temp file is deleted from the NAND at shutdown request, so if you shutdown neek without returning to realNAND the file got deleted from neek's nand only, but is still on real nand. But that's just if you never returned to realNAND from neek.
Another possibility :
You used (long time ago) USBLoader to play that game with playlog setting.
the loader writes the temp file.
but you are also using "return to loader", so you never return to system menu to write the playlog. (I will check if playlog is auto-disabled when using return to)
You shutdown the console and few days later you power it and as you have bootmii boot2 to autoboot HBC you still never go to system menu.
You launch nswitch and play on neek. You exit neek and bootmii returns to HBC again.
then you decide to launch system menu from HBC menu, and system menu find your very old temp file generated by usbloader and write the playtime as 24h.
I would need someone to test a game which needs gameconfig.txt
I removed the need to have Ocarina ON (just enable hooktype option and it will load the file)
Possible game:
ProjectM (I wanted to try myself, but found it's not working with PAL ...)
Kirby return to dream's land (I have the PAL and U codes, but not the game)
Any other games using this file?
If you have the games, please test neek2o preview 2 and tell me if it works.
here is the neek2o preview2.
It should be stable and there are warning and error messages added.
I didn't try to trigger all the possible error messages and situations, some of them could be wrong.
wrong message, messages displayed while things are correct, etc.
Please report any wrong messages you find.
neek2o preview 2