I wonder why almost all usb loaders (except NeoGamma) don't work with new drives with 4096 physical sectors.
Is there any chance for a fix?
Thanks in advance
Is there any chance for a fix?
Thanks in advance
fig2k4 said:Standard libWBFS uses hardcoded values for the sector size (512) in the read a write sector routines. I noticed that you use a USBStorage_ReadSectors() function in NeoGamma, which uses the real sector size.
I haven't checked the source of other loaders, but if they use the same hardcoded values then it would explain why it works in NeoGamma and not others.
It's one thing I changed when I converted libWBFS to my Delphi code for WBM. I haven't had a drive to test it, but having a variable hd_sec_sz, then using 512 in the read and write routines is obviously wrong.
SaintSeiya said:I tried USB Loader GX, Configurable USB Loader (ios 249 selected with Configurator and saved in the config file) but both give me ''Exception (ISI) occurred'', Uloader 4.1 says: USB Device Sectors Size must be 512 bytes.
Only NeoGamma works perfectly.
Any idea?
WiiPower said:SaintSeiya said:I tried USB Loader GX, Configurable USB Loader (ios 249 selected with Configurator and saved in the config file) but both give me ''Exception (ISI) occurred'', Uloader 4.1 says: USB Device Sectors Size must be 512 bytes.
Only NeoGamma works perfectly.
Any idea?
What cIOS are you using? And did you try with the lastest versions configurable usb loader and GX with completely cleared config, no pictures on sd card and stuff?
WiiPower said:Ok, let's fix this. On configurable usb loader, you can use a wbfs formatted usb pen using IOS249. If you try the same with your wbfs formatted HDD, you get the exception?
If yes, gather all information that could be relevant and describe it as precise as you can in the configurable usb loader thread. Don't forget to tell that the same HDD works with the same cIOS on NeoGamma. I hope oggzee will pick this up then and fix it.
PS: Once it would be fixed on configurable usb loader, the other loaders devs could copy the necessary change of course
oggzee said:Can you make a screenshot of the error and also let me know exactly when does it happen?
Is it during the intro screen or usb init or when?
Also can you add the option debug=1 and let me know after which step the exception occurs?
I will then make another debug version which should give me more details...
Also, were you using normal cfg boot.dol or cfg-fat.dol, can you try both?
What I suspect is the error might be caused when trying to mount fat partitions from USB, not when mounting WBFS partition... but that's a blind guess, that's why i'm asking for more details. Without those it's hard to start fixing it...oggzee said:Can you make a screenshot of the error and also let me know exactly when does it happen?
Is it during the intro screen or usb init or when?
Also can you add the option debug=1 and let me know after which step the exception occurs?
I will then make another debug version which should give me more details...
Also, were you using normal cfg boot.dol or cfg-fat.dol, can you try both?
That's correct and that's what i will try.ViRGE said:Perhaps I'm missing something here, but why do the loaders care about 4K drive sectors? All of these hardware vendors should be doing 512B4K translation (including read-modify-write for unaligned write operations) in their drive's firmware, so that the (S)ATA controller and the operating system see the drive as yet another 512B sector drive. The loaders shouldn't be seeing 4K sectors.
oggzee said:@SaintSeiya:
@tadija:
Can you try this:
cfg52t2.dol (test)
It will print some hdd info like number of sectors, sector size, hdd size.
Can you make a screenshot of that.
Then press any button and let me know if it works or not, it will try to force the 512 sector size.
Please do post a screenshot of the hdd info screen too as requested, so that i can see the numbers, or write them down.SaintSeiya said:wbfs error: hd sector size doesn't match
I'm uploading a video of that.