[anaria]

Originally Posted by BwE i find it funny not many people know about my validator, which is the plan.

I guess it's your Australijan sense of humour

Originally Posted by BwE i originally put it just on the wiki for the sole purpose for people who actually have the brain to go look for it there deserve to use it

People deserve what they are looking for, sure.

Good job anyway.

Few comments:
7MB+ is a bit big for such tool, any plan to split it in 2 parts like exe + data, so those who do not want to use it for patching, or eventually for later, can download only what they'd like?

On the job's PC (Win7 x64) the memory usage climbs to about 300MB !? But I did not try on my old small config (Win2k 256MB) so maybe it allocates dynamically??

Only WIN32? or ....?

[BwE]

Originally Posted by anaria 7MB+ is a bit big for such tool, any plan to split it in 2 parts like exe + data, so those who do not want to use it for patching, or eventually for later, can download only what they'd like? On the job's PC (Win7 x64) the memory usage climbs to about 300MB !? But I did not try on my old small config (Win2k 256MB) so maybe it allocates dynamically?? Only WIN32? or ....?

7mb is good considering it patches regardless of byte orientation.
Best I can do is make a version that doesn't patch which would make it 1-1.5mb.

300mb isn't much (plus I have never checked or noticed an issue).

Its for both 32 and 64bit.

[anaria]

Originally Posted by BwE 300mb isn't much (plus I have never checked or noticed an issue).

hmmm well it is, what if one do want to use an old crappy PIII with 256MB on a dirty workbench and not a brand new quadcore 6GB?

Originally Posted by BwE Its for both 32 and 64bit.

ok so it should run on any OSX and Linux... ah no you meant WinStuff 32/64 :P

Anyway it doesn't matter as you already plan to release the source sooner or later anyone would then port it to what he wants

By the way, do you plan to change the input parameter option as all your tools just read the first toto.bin file they find, it would be better if this can be overrode, no?

[BwE]

Originally Posted by anaria hmmm well it is, what if one do want to use an old crappy PIII with 256MB on a dirty workbench and not a brand new quadcore 6GB? ok so it should run on any OSX and Linux... ah no you meant WinStuff 32/64 :P Anyway it doesn't matter as you already plan to release the source sooner or later anyone would then port it to what he wants By the way, do you plan to change the input parameter option as all your tools just read the first toto.bin file they find, it would be better if this can be overrode, no?

Windows yes.

Input parameter option? All of my tools read the first .bin? No?

My NOR Validator will read automatically if there is only ONE .bin in the directory. If there is more than one it will prompt you to select which one.

[playerkp420]

What is 7MB, in this world of TB? LOL

You gonna add 3 musketeers patches, or you don't believe in that?

[BwE]

Originally Posted by playerkp420 What is 7MB, in this world of TB? LOL You gonna add 3 musketeers patches, or you don't believe in that?

I didn't due to keeping it @ 7mb and its lack of popularity

[anaria]

Originally Posted by BwE I didn't due to keeping it @ 7mb and its lack of popularity

Well it's just me and my nostalgia of this great multitask OS running from a floppy disk less than 880KB, it actually doesn't matter.

Also the fact that when we maintain soft for production we have to face some manager who do not want to invest a penny in new PCs if you can upgrade the test software running on an old PIII with 128 MB of RAM and a 20GB HDD, so you get the habit to build 100KB when you can instead Megsss.

Regarding a command line options it clearly seems that we do not have the same view, in my opinion the way it's done in your case is exactly what you would expect from a GUI, do things for the user then propose some options, but for a pure command line you need to allow the user to enter parameters like -i <input file> -o <output file> -whatyouwant option blabla so it can easily be used in a script/batch, otherwise it's a GUI with no window in a shell no more, but that's only my view of a command line and I do not force anyone to think the same
Sure we have different view as you are running a business and I'm just an employee. :P

[BwE]

Originally Posted by anaria Regarding a command line options it clearly seems that we do not have the same view, in my opinion the way it's done in your case is exactly what you would expect from a GUI, do things for the user then propose some options, but for a pure command line you need to allow the user to enter parameters like -i <input file> -o <output file> -whatyouwant option blabla so it can easily be used in a script/batch, otherwise it's a GUI with no window in a shell no more, but that's only my view of a command line and I do not force anyone to think the same Sure we have different view as you are running a business and I'm just an employee. :P

The original was all in the console. But I felt it to be tiresome to scroll up to read the result and I also felt the desire to be able to jump to sections of the flash.

I was going to also have a hex editor style gui also, but I could not be bothered to do it.

As for actual command line inputs, that is just pointless. You are after one thing, the flash to be validated. Anything else is just boring. Output name/location etc? Who cares, it does it for you - everything is simple because only simple people will use my program.

If you want something done your way you would have validated it yourself.

[anaria]

Originally Posted by BwE The original was all in the console. But I felt it to be tiresome to scroll up to read the result and I also felt the desire to be able to jump to sections of the flash. I was going to also have a hex editor style gui also, but I could not be bothered to do it. As for actual command line inputs, that is just pointless. You are after one thing, the flash to be validated. Anything else is just boring. Output name/location etc? Who cares, it does it for you - everything is simple because only simple people will use my program. If you want something done your way you would have validated it yourself.

Yeah well that sounds fair.
Sorry I'm a complex bad ass :D

Nop if I want something done my way I'll ask my code to do it for me as I'm a lazy fat ass and I have no brain able to do the job

[BwE]

Originally Posted by anaria Yeah well that sounds fair. Sorry I'm a complex bad ass :D Nop if I want something done my way I'll ask my code to do it for me as I'm a lazy fat ass and I have no brain able to do the job

rightio