I don't intend to add any other file formats, although it shouldn't be hard.pzyro said:will .ciso files ever be supported?, it'd be a simpler way of saving disk space.
So we still need a manager for save space with .iso files?fig2k4 said:Bloodlust said:I love WBM, but is there an option to scrub the excess space of an ISO to the same size as a converted *.wbfs file? Is that how you define "sparse"?
http://en.wikipedia.org/wiki/Sparse_file
The ISO will still show as 4.37 gig or whatever in explorer, but the size used on disk will be the same as WBFS files or CISO.
To create/copy a sparse ISO, you'll need to use wbfs_file or WBM, since Windows explorer doesn't create sparse files. Like oggzee mentioned, it'll use the real 4.37 gig if you copy it using explorer.
That means the file is fragmented in more than 5000 places which is the current limit. It looks like the current method of creating sparse files makes the files highly fragmented, at least it seems that is the case with wbfs_file, but probably with WBM too.DIXES said:What's meaning of ntfs getf -37 error ? Thanks !!!
I use v50b, launching some .iso files. (Use WBM convert some .wbfs files to .iso files)
Yes. Although in my opinion it's easier to go with .wbfs files.laurozza said:So we still need a manager for save space with .iso files?
bonne chance!LordVolk said:ok I'm going through everythign to make sure I get allt he steps done properly. Wish me luck
802.11smf said:oggzee said:Heh, you wishsmf said:It's 802.11g, so up to 50mb/s. Quite what throughput/latency you'll get from smb is another thing.try measuring it...
edit: btw not sure if you were talking about bytes or bits, but the correct number is 54 Mbit/s, which makes for a maximum theoretical throughput of 6.75 MB/s, however actual numbers are much lower, in the range that WiiPower mentioned or even lower, anyway it's too slow. And I am certainly not adding that even if it would be fast enough.
It's probably just a crappy 'good enough' implementation, like nintendos usb drivers. It might be possible to improve it, but lots of work. Benchmarking the linux wifi driver would be interesting.
hackotedelaplaque said:I successfully tested cfg v50b with a USB Stick.
Good work on NTFS support.
However, since you still need a manager to compress isos (sparse file or *.wbfs) I see little interest in using NTFS over WBFS (and I like the idea of a proprietary file system and a "hidden disk" in Windows).
That said, I may go into NTFS if someone can answer a question about sparse files. Can I burn directly those compressed isos like normal ones (without additional convert step) ?
I see...thanks.oggzee said:Yes. Although in my opinion it's easier to go with .wbfs files.laurozza said:So we still need a manager for save space with .iso files?
Especially since now it seems that sparse file creation makes the files also highly fragmented.
The issue needs to be investigated further though...
STACK DUMP:
80b0f3b0 --> 80b4d7fc --> 80b40c04 --> 80b415dc -->
80b41e6c --> 80b41f6c --> 80b435f0 --> 80b436f4 -->
80b49abc