OSDev.org

I present SfsTools, a set of user-space applications which can access and read/write SFS disk images. Please do try it out. Bug reports and general feedback is much appreciated. The code is located at https://code.google.com/p/sfstools/, a C# compiler will be needed to compile it.

Edit: binaries attached.

I was expecting a *nix-compatible tool, but no, it had to be .NET . What's the advantage of that over VB?

Combuster wrote:I was expecting a *nix-compatible tool, but no, it had to be .NET . What's the advantage of that over VB?

It's currently in a proof of concept stage. If there is enough interest, I will reimplement it in C. Nevertheless there is Mono for you *nix fans.

ru2aqare wrote:Nevertheless there is Mono for you *nix fans.

That is not a solution, that's a kludge..

Combuster was trying to communicate that he's already written a "Windows-only" SFS tool, so what does your project contribute?

And there are already other operating systems out there so what do any of us have to contriubte? Cut the guy some slack

Also, the "why C#?" sounds to me like the NIH syndrome. I don't know about the .NET framework (which Combuster mentioned but the author didn't) but C# *is* an awesome language, perhaps the best high-level language I've seen - look into it.

What about providing some binaries (they don't have to remain up-to-date, just so we can see an example)? I doubt a lot of people here are willing to download a C# compiler (if they have none) just to compile and try out your utility.

Creature wrote:What about providing some binaries (they don't have to remain up-to-date, just so we can see an example)? I doubt a lot of people here are willing to download a C# compiler (if they have none) just to compile and try out your utility.

Providing binaries is a sensible idea, I attached them to the original post.

Brynet-Inc wrote:Combuster was trying to communicate that he's already written a "Windows-only" SFS tool, so what does your project contribute?

Well, now you have *two* "Windows-only" tools. Other than that, mine has comments.

The source is there, if you want a *nix version that badly, just take it and start rolling your own. If there is enough interest in this, I will at some point make a C version too.

ru2aqare wrote:

Creature wrote:What about providing some binaries (they don't have to remain up-to-date, just so we can see an example)? I doubt a lot of people here are willing to download a C# compiler (if they have none) just to compile and try out your utility.

Providing binaries is a sensible idea, I attached them to the original post.

Brynet-Inc wrote:Combuster was trying to communicate that he's already written a "Windows-only" SFS tool, so what does your project contribute?

Well, now you have *two* "Windows-only" tools. Other than that, mine has comments.

The source is there, if you want a *nix version that badly, just take it and start rolling your own. If there is enough interest in this, I will at some point make a C version too.

What is the licensing and is there any p/invokes or such? Have you tried to compile and run it on a *nix system?

earlz wrote:What is the licensing and is there any p/invokes or such? Have you tried to compile and run it on a *nix system?

The code is licensed under the MIT license, as it is stated on the googlecode site. The code is 100% managed code, there are no P/Invoke calls. As for your question, I have currently no access to a *nix box, but I'd expect it to run without a hitch under Mono.

ru2aqare wrote:I have currently no access to a *nix box, but I'd expect it to run without a hitch under Mono.

You can also check it.