You don't have to.
But let me understand what doesn't work, are you referring to the fact that ios gets reloaded when you start the game or it doesn't select 222 at all? What does it show in game options? And are perhaps options saved for that game? try discarding them, to see what is the global set default.

If you're referring to the fact that the ios gets reloaded, that will be fixed in future, the problem is even if you set ios=222-mload in config, it has to be reloaded to enable FAT support. When I will add the partition=fat1 option, if combined with ios=222-mload option it will start with the fat module loaded. So, until then, a little patience

Doesn't select 222 at all. There are no option saved for games. I have to set 222 manually for each games or they boot with 249 by default even if a set to use 222 in config.txt.

This post has been edited by laurozza: Oct 27 2009, 11:26 AM

Yes, and hopefully we'll be seeing a batch of TriiForce VC/WW forwarder ISO's coming out and given their relatively small size, it'll be possible to add them over the network instead of having to drag the HD back and forth. I also like the idea of being able to defrag the partition every now and then.

Hmm, then maybe it is the old forwarder problem.
Does it behave that way also if you run it from HBC?

From HBC no problem.

EDIT: i'm making more test on games on FAT32 partition...until now all seems perfect. Again thanks.

This post has been edited by laurozza: Oct 27 2009, 11:46 AM

ok, then it must be that you are using one old version of the nforwarder that forces the ios.

Can anyone in short explain the features of this .wbfs file format compared to .iso, ciso and Wiim's format. Or are there none because it is just the section of the game dd'ed from the BWFS drive?
There are already so many "small" .iso formas, what makes this one better?

It is the only one readable by a USB Loader to play games.

wbfs_file_1.2.zip
http://sharebee.com/d01f6166
included: sources and binaries for windows, linux and macosx.

Changes:
v1.2:
* On Windows allow to use device name instead of drive letter in the format:
\\?\GLOBALROOT\Device\Harddisk3\Partition2
This is useful if you don't have a drive letter assigned to a partition

Oggzee,

as you suspected it the actual cios does not support files bigger than 2gb. it gets stuck at
too bad
I guess we are stuck with 2gb files until hermes (hopefully) updates that.
or until the library is updated.

anyway thanks for pointing it out.. I was pretty close to convert my games to 4gb files.. it would have been such a waste of time

wbfs_file d:/destination/gameid.wbfs create e:/source/game.iso
works like a charm
so does : wbfs_file d:\destination\gameid.wbfs create e:\source\game.iso

but, if I may share my humble opinion, you should change this command.
because we need to KNOW the gameid to launch this command.
otherwise some noob will use it entering anything they like as a wbfs name and will complain the game is not recognized by the loader.

maybe something like
wbfs_file <source filename> convert_wbfs <destination directory>
i.e.
wbfs_file <source filename> convert_iso <destination filename or destination directory>

please note that for WBFS only the folder is given the name being automatically given , while for the ISO the filename can be given, otherwise if given only the directory it can be extracted from the wbfs file automatically....

once again these are only my two cents.
I am pretty sure in a couple of days we will start seeing a few managers that will wrap all that

Cheers,
R

edit :
I just tried converting from WBFS to iso... once again using two hard drive.
tried the create function... does not work.. it is only meant one way iso->wbfs
tried the extract_iso... seems to work but it is VERYYYY slow.. it is faster to add the game to a wbfs drive and to extract it

This post has been edited by redia: Oct 27 2009, 02:11 PM

That is not a cios problem but a libfat problem or could even be a bug on my side, i need to check (... depends on off_t size when building for ios and of my proper use of it), anyway, for now 2gb split is the max.


yeah i thought of that, maybe i'll add that too one day, should be trivial anyway


correct, create is only from iso to wbfs, it also say so in the help.


i'm not sure exactly what are you doing here, can you be more specific?
are you using drives or files and what drive and filesystem is source and destination..?

This post has been edited by oggzee: Oct 27 2009, 02:32 PM

Thanks oggzee, problem solved upgrading the forwarder.

lol.. I knew I was not clear.. sorry..
but it is good I was not because you can ignore my previous comment about the speed I took the ETA as granted..... lol
nevertheless the extraction is not working correctly.

I had an ISO, on a NTFS HD.
I converted it to a splitted WBFS file on a FAT32 HD
as mentioned it works like a charm using the create option.

now I want to do the opposite.. I want to convert a splitted WBFS file on a FAT32 HD to an ISO (on a NTFS drive. to burn it for example)
as mentioned previously the create option does not work.
so I tested

TEST 1 ... direct conversion



TEST 2 ... EXTRACT COMMAND from a WBFS FILE to a ISO FILE


TEST 3 ... USING a WBFS DRIVE as a temporary conversion tool


TEST 4 ... Tried to extract a game from my existing WBFS Drive which was added another manager


TEST 5 ... Tried to extract a game which was added using WBFS_FILE.exe from an ISO using an alternate WBFS manager


TEST 6 ... Tried to extract a game which was added using WBFS_FILE.exe from an WBFS FILE using an alternate WBFS manager


I hope this helps.

Cheers,
R

This post has been edited by redia: Oct 27 2009, 04:17 PM

Thanks redia for the extensive report!
I see now what's wrong, the ftruncate call behaves quite differently on windows than on linux so the fiel is not extended to the full size, i will fix this in a minute. The missing data is anyway not used and in the iso it's just filled with zeroes. So the produced iso can still be used, if you convert it again to wbfs and compare the contents you'll see that the produced wbfs file is the same.

sorry bout that ,ok ive ceen reading and woundering how to move a iso i got on my pc to a fat 32 for the loader

This post has been edited by goku1980: Oct 27 2009, 04:36 PM