D
Deleted User
Guest
Cyan why not use a different host - SourceForge likes to do stuff like own installers and ads - You can use my git if you want another host
It is
USBLoaderGX r1260
- removed SSL, and removed nintendont update feature (because it requires SSL), to fix network issue.
- fixed banner download
- added batch wad install (all wad from a folder, no sub-folder loaded)
- renamed the wad menu to "EmuNAND wad manager"
- removed all wad error and warnings messages while installing in "folder mode" to skip them and display how many wad where not processed at the end.
- Added game type and console name for VC channels in the Title list exporter
Sorry that I had to remove nintendont internal update. I liked having the loader create the folders and download file without using the SD on PC or using wiixplorer.
There are still things I didn't test (like banner download, or gamecube game delete).
I hope the banner download works.
let me know if you have issues with anything related to the changelog. (banners, wad batch install/uninstall, export gamelist)
I think I will push this version in the internal update, unless there's a last minute bug you guys will find.
I'll push it internally tomorrow. that will be the first internal update since moving to sourceforge, I hope it will work too.
I'll try to make a new installer.exe too, with link to forwarders instead of full channel (and link to sourceforge instead of googlecode)
when google announced the shutdown, there were only two possibility to migrate en entire repository (keeping all svn history, issues, comments, etc.) : github or sourceforge.Cyan why not use a different host - SourceForge likes to do stuff like own installers and ads - You can use my git if you want another host
@Clutz450:
Ah, this bug is still there? I wasn't sure.
it looks like this bug (only the ID instead of the name) is present since r1247, which is when I changed the sources to prevent listing channels without data (for example deleted channels from official NAND still have their ticket, and dumping such nand were displaying the game on the emuNAND even if it was deleted because).
I don't know why checking the data presence create an issue with the channel names.
I will have to check that.
I think you can trigger that issue by disabling titlecache (or else it will read names found inside).
I would like someone with that issue to do some tests, but I would also need that person to have a deleted channel on real nand with ticket still present (because that's the purpose of that change in r1247).
Maybe I'll do the tests myself.
@ngs428 :
that's odd, I didn't have a size at all for VC games.
The size is for Wii and gamecube games only.
I thought about adding size for EmuNAND, but you already have it? I'll have to take a look.
the character issue is because the file is saved as ANSI instead of UTF-8.
usually, text editors are automatically switching to UTF8 when detecting a 2bytes character.
But some program don't do that auto-detection and only rely on the BOM (signature at the start of the file).
I don't know which program you are using to open the csv. and I don't know if csv can have a BOM.
You can convert it (or add bom) with notepad++
open the file in notepad++ (it will detect utf8 automatically and display the text correctly as utf8)
select menu : encoding > convert to UTF8
(not the one saying "without bom", it's already without the utf8 signature, so you convert it with the signature)
save the file to add the BOM signature.
an alternative is to "convert to ANSI" instead of adding BOM.
encoding > convert to ANSI.
the export feature was added when only wii game was possible.
when we added support for other game type, we didn't check if all features were working.
I'll have a look if it's not to hard.
@Cyan Sadly, I don't have the old drive anymore (well, technically I do. But what failed in it was the controller board. So basically I still have the drive but it's a nice little paperweight. And the reason I didn't get a new enclosure and instead bought a pre-made HDD was because I thought it would be beneficial since my enclosure was usb 2.0. If I had known the compatibility was wrong I would've just bought a new cheap enclosure...)well, it could be related to the changed HDD, but I find it really strange, because the code to use the drive is the same.
do you still have the previous drive? Maybe we could compare them.
Could you reproduce the bug with it?
Could you do a SMART on the old one?
Could you do an usb analyze on both? (I think it's http://www.usblyzer.com/) but it's shareware 30 day free. I never used it so I don't know how it works (Fix94 did, but don't know if he could help,) Checking how many Device Descriptor, Configuration, Interfaces the drive use, etc.
I really don't know where it will lead us, that's just "data" for comparison.
I don't know if usblyzer work with win10
Connection Status Device connected
Current Configuration 1
Speed High (480 Mbit/s)
Device Address 4
Number Of Open Pipes 2
Device Descriptor Elements 1078
Offset Field Size Value Description
0 bLength 1 12h
1 bDescriptorType 1 01h Device
2 bcdUSB 2 0300h USB Spec 3.0
4 bDeviceClass 1 00h Class info in Ifc Descriptors
5 bDeviceSubClass 1 00h
6 bDeviceProtocol 1 00h
7 bMaxPacketSize0 1 09h Should be 64 bytes for high-speed devices
8 idVendor 2 1058h Western Digital Technologies, Inc.
10 idProduct 2 1078h
12 bcdDevice 2 1065h 10.65
14 iManufacturer 1 02h "Western Digital"
15 iProduct 1 03h "Elements 1078"
16 iSerialNumber 1 01h "575834314139353058333934"
17 bNumConfigurations 1 01h
Binary Device Object Store (BOS) Descriptor
Offset Field Size Value Description
0 bLength 1 05h
1 bDescriptorType 1 0Fh Binary Device Object Store (BOS)
2 wTotalLength 2 0016h
4 bNumDeviceCaps 1 02h
Device Capability Descriptor - USB 2.0 Extension
Offset Field Size Value Description
0 bLength 1 07h
1 bDescriptorType 1 10h Device Capability
2 bDevCapabilityType 1 02h USB 2.0 Extension
3 bmAttributes 4 0000F41Eh
0: Reserved ........ ........ ........ .......0
1: Link Power Management ........ ........ ........ ......1. Yes
31..2: Reserved 00000000 00000000 11110100 000111.. Reserved, should be zero
Device Capability Descriptor - SuperSpeed USB
Offset Field Size Value Description
0 bLength 1 0Ah
1 bDescriptorType 1 10h Device Capability
2 bDevCapabilityType 1 03h SuperSpeed USB
3 bmAttributes 1 00h
0: Reserved .......0
1: Latency Tolerance Messages ......0. No
7..2: Reserved 000000..
4 wSpeedsSupported 2 000Eh
0: Low-Speed ........ .......0 No
1: Full-Speed ........ ......1. Yes
2: High-Speed ........ .....1.. Yes
3: Super-Speed ........ ....1... Yes
15..4: Reserved 00000000 0000....
6 bFunctionalitySupport 1 01h Full-Speed and above
7 bU1DevExitLat 1 0Ah Less than 10 µs
8 wU2DevExitLat 2 07FFh Less than 2047 µs
Configuration Descriptor 1 Bus Powered, 896 mA
Offset Field Size Value Description
0 bLength 1 09h
1 bDescriptorType 1 02h Configuration
2 wTotalLength 2 002Ch
4 bNumInterfaces 1 01h
5 bConfigurationValue 1 01h
6 iConfiguration 1 00h
7 bmAttributes 1 80h Bus Powered
4..0: Reserved ...00000
5: Remote Wakeup ..0..... No
6: Self Powered .0...... No, Bus Powered
7: Reserved (set to one)
(bus-powered for 1.0) 1.......
8 bMaxPower 1 70h 224 mA
Interface Descriptor 0/0 Mass Storage, 2 Endpoints
Offset Field Size Value Description
0 bLength 1 09h
1 bDescriptorType 1 04h Interface
2 bInterfaceNumber 1 00h
3 bAlternateSetting 1 00h
4 bNumEndpoints 1 02h
5 bInterfaceClass 1 08h Mass Storage
6 bInterfaceSubClass 1 06h SCSI Transparent Command Set
7 bInterfaceProtocol 1 50h Bulk-Only Transport
8 iInterface 1 00h
Endpoint Descriptor 81 1 In, Bulk, 1024 bytes
Offset Field Size Value Description
0 bLength 1 07h
1 bDescriptorType 1 05h Endpoint
2 bEndpointAddress 1 81h 1 In
3 bmAttributes 1 02h Bulk
1..0: Transfer Type ......10 Bulk
7..6: Reserved 00......
4 wMaxPacketSize 2 0400h 1024 bytes
6 bInterval 1 00h
SuperSpeed Endpoint Companion
Offset Field Size Value Description
0 bLength 1 06h
1 bDescriptorType 1 30h SuperSpeed Endpoint Companion
2 bMaxBurst 1 0Fh Up to 16 packets at a time
3 bmAttributes 1 00h
4..0: MaxStreams ...00000
7..5: Reserved 000.....
4 wBytesPerInterval 2 0000h
Endpoint Descriptor 02 2 Out, Bulk, 1024 bytes
Offset Field Size Value Description
0 bLength 1 07h
1 bDescriptorType 1 05h Endpoint
2 bEndpointAddress 1 02h 2 Out
3 bmAttributes 1 02h Bulk
1..0: Transfer Type ......10 Bulk
7..6: Reserved 00......
4 wMaxPacketSize 2 0400h 1024 bytes
6 bInterval 1 00h
SuperSpeed Endpoint Companion
Offset Field Size Value Description
0 bLength 1 06h
1 bDescriptorType 1 30h SuperSpeed Endpoint Companion
2 bMaxBurst 1 0Fh Up to 16 packets at a time
3 bmAttributes 1 00h
4..0: MaxStreams ...00000
7..5: Reserved 000.....
4 wBytesPerInterval 2 0000h
Hi. Ill try to help you.Trying to find the best place to post this, sorry for duplicates but realized this seems to get more action and my problem involves usb loader gx.
Ok so I'm finally going to ask for some help here, been trying to get wiiware/vc games to running on hdd forever... I have wii and gc games working (mostly)
I thought neek2o was the best option since it has the highest compatibility, but I'm about done with trying that. It seemed to work for a second, until I added 700 some wads. I used this mega noob guide https://ccabz.wordpress.com/2013/01/16/neek2o-for-mega-noobs/ with the supplied US region nand. If I do end up trying neek2o again, is there a premade nand out there with the latest neek2o version? or an easy way to update that premade nand?
For now though, I think I'd be perfectly fine with just the cios nand emulation. I've tried it through wiiflow and now usbloadergx (which I like somewhat better), but neither method will actually launch any of the wiiware/vc games... just hangs and goes back to menu (whatever autoboot is set to in priiloader I think).
I'm wondering if the issue is cIOS versions? I used the d2x cIOS installer to update the ones on my real nand (per this guide https://sites.google.com/site/completesg/backup-launchers/installation), and made my emunand after that with the extract options in both wiiflow and then usb loader gx.
Does anyone have suggestions as to what the problem could be? Do you think I just need a different cIOS, or just need to set wiiflow or usbloader gx to use the right one?
Hopefully I supplied enough info. If not, just let me know what else would be helpful. Thanks for reading!
Hi. Ill try to help you.
The easiest way for you to do this would be to dump your nand to emunand from usbloader gx (features/dump nand to emunand) and compile uneek+di from modmii (Is it still active?).
You can search for the specifics in a previous post from @Cyan
Other than that, do you know the format and cluster size of your HDD?
Yes, ModMii still works for compiling neek. I thought the date for Google Code shutting down was the first but I was able to compile it and I've heard that the date for it shutting down is the 25th. So you at least have a few more weeks unless ModMii gets updated.The easiest way for you to do this would be to dump your nand to emunand from usbloader gx (features/dump nand to emunand) and compile uneek+di from modmii (Is it still active?).
Mmm try dumping the nand in USBLOADER GX (for that, I would recommend manually creating a "nand" folder on the root of your HDD and selecting that path in USBLOADER GX. IIRC the loader comes with the default setting of SD:\Nand\)Thank you for your reply! So, for now I would just like to set the neek stuff aside. It might be nice to have in the future, but I'd like to have this cIOS emunand working to start with. Then at least I have that to fall back on. It may be at the root of some larger problem as well since I seem to have the same issue with wiiflow and usbloadergx.
Once difference though, when launching a ww/vw title from wiiflow it takes me back to wii system menu. From usbloadergx I end up at homebrew menu. There doesn't appear to be a setting in usbloadergx that is affecting this... I could be missing it, but I messed with the return to option only a little.
Ok, so first thing first and then I have an issue with gamecube games in usbloadergx that I'd love to solve too.
The HDD I'm working with is an adata 500 gb usb3 with no extra power supply. I don't think the extra power that usb3 draws should be an issue, should it? It seems to work for everything else here. I think I followed correct guidelines when setting it up the partition. It is formatted as MBR, only one primary fat32 partition. Looking at the properties in minitool partition wizard says "sectors per cluster: 64" so I guess I chose 64k cluster size?
Anyway neek2o seemed to launch from the system menu forwarder wad when I initially set it up with like 30 game wads so I think the formatting is ok. Then I took it up to nearly 800 game wads and it seemed to just hang on a black screen with the wiimote still connected. I think the initial press A to continue black screen appeared after a while but then just hanging forever. I really think I want to skip neek for now though so onto the cIOS emunand, preferably through usbloadergx...
What could possibly be the issue though with launching a ww/vc title always going back to homebrew browser? I dumped the nand through usbloadergx and installed a few wads directly with it too.
Are there any super important things I need to have on my real nand before dumping it? I did install cIOS to it with the d2x cIOS installer. I followed the complete softmod guide here https://sites.google.com/site/completesg/backup-launchers/installation which installs:
I set them both as max revision number I think too. I think I read somewhere there was some issue with it thinking the nand was only in the root directory when that was done, but I never experienced that issue.
- cIOS 249 base 56 v10 beta53-alt
- cIOS 250 base 57 v10 beta52
After experiencing my issue with wiiflow, I even edited my nand I dumped with wiiflow in modmii and I think it replaced the 249 cIOS with one that now says version 14. I tried loading games from that edited emunand with both wiiflow and usbloadergx to the same results, back to menu.
Is there just some settings I need to change with how the loader selected the cIOS or do I need the proper cIOS on my real nand first?
I'm sorry for the massive post, just trying to give the right details on this... I think I'll save the gamecube games issue until after I solve this one! Thanks a ton to anyone who takes the time to read and help!
I actually had a HDD that ONLY WORKED with 32KB. I don't know why or how. But anything else would just blackscreen.Yes, ModMii still works for compiling neek. I thought the date for Google Code shutting down was the first but I was able to compile it and I've heard that the date for it shutting down is the 25th. So you at least have a few more weeks unless ModMii gets updated.
@Poglodyte About your issue. I forget the game number limit but the Neek system menu will not load up if you have too many games installed on your emunand. So it makes sense that you were able to load into it when you only had a few games and then it stopped working when you added a ton more. However, that only effects loading up the Neek system menu. You can still use USB Loader GX to launch a game into neek mode from the loader.
As for cIOS emulation and the issues you are having with that I don't have any idea right now. The best way for you to help us would be to post a syscheck using this guide here (https://gbatemp.net/threads/posting-a-system-check.300279/). There are only a handful of WiiWare games and and Virtual Console games that require neek so it seems odd to me that you can't get any of them working. But that syscheck you post will help narrow things down. You can also run your syscheck through ModMii and it will tell you if anything should be updated.
For your hard drive you should be fine with it set as FAT32 and 64k clusters. I know just about every other guide says you should do 32k clusters but I can tell you from experience that 64k works on USB Loader GX, Nintendont, cIOS emulation and neek2o. As far as it not being externally powered, as long as you are using a Wii and not a Wii U I think you should be fine.
As a last resort, if you still have all your WADs and Wii and GameCube games you could try formating your drive and SD card and just start over from scratch. I know it's not ideal but when I wad new to hacking I had a Wii that I just couldn't figure out what I did to make it stop working and after I redid everything it started working again. Hopefully it doesn't come to that though.
Ok. So go get ModMii and get going.I do want to do a clean mod on everything now that I understand things a little better, but I'd like to be sure I have everything in order before doing so. I've only tried modmii for the emunand and neek stuff so far. Is it the way to go for modding your real nand as well?
I thought neek2o was the best option since it has the highest compatibility, but I'm about done with trying that. It seemed to work for a second, until I added 700 some wads. I used this mega noob guide https://ccabz.wordpress.com/2013/01/16/neek2o-for-mega-noobs/ with the supplied US region nand. If I do end up trying neek2o again, is there a premade nand out there with the latest neek2o version? or an easy way to update that premade nand?
I had similar issues with neek2o, too long of a wait for large nands. A good workaround is to install Postloader on your neek2o nand and then configure it to use "neek2obooter.app" as the system menu. This allows Postloader to replace your neek2o system menu and it boots up right away, no more long wait.
MAC address? for what?f you want you can even give me the MAC address of your Wii