[guerrierodipace]

Originally Posted by donkey-punch How can I get this to work with windows 7 64 bit? I opened a cmd prompt dragged and dropped the exe into it and then dragged and dropped the dump into cmd prompt, but it just opens a new cmd prompt for a split second and nothing happens.

you have to write commands inside the prompt not "drag in"

[donkey-punch]

Originally Posted by guerrierodipace you have to write commands inside the prompt not "drag in"

So what is the .exe for that @judges uploaded?

[guerrierodipace]

Originally Posted by donkey-punch So what is the .exe for that @judges uploaded?

you have to open it via "cmd" command

from wikipedia:
Cygwin is a Unix-like environment and command-line interface for Microsoft Windows. Cygwin provides native integration of Windows-based applications, data, and other system resources with applications, software tools, and data of the Unix-like environment. Thus it is possible to launch Windows applications from the Cygwin environment, as well as to use Cygwin tools and applications within the Windows operating context.

You can't use like win ".exe" you must use "command prompt" in windows

[donkey-punch]

Originally Posted by guerrierodipace you have to open it via "cmd" command from wikipedia: Cygwin is a Unix-like environment and command-line interface for Microsoft Windows. Cygwin provides native integration of Windows-based applications, data, and other system resources with applications, software tools, and data of the Unix-like environment. Thus it is possible to launch Windows applications from the Cygwin environment, as well as to use Cygwin tools and applications within the Windows operating context. You can't use like win ".exe" you must use "command prompt" in windows

Ok so could you set me an example of the commands I need to put in the cmd prompt. I have it opened and when I drag and drop the exe into it and hit enter it brings up a list of options option: -P give percentage of bytes and so on. SO what do I need to do next.

[guerrierodipace]

Originally Posted by donkey-punch Ok so could you set me an example of the commands I need to put in the cmd prompt. I have it opened and when I drag and drop the exe into it and hit enter it brings up a list of options option: -P give percentage of bytes and so on. SO what do I need to do next.

Don't use drag and drop!!!!!

look my screenshot here
http://www.ps3hax.net/showpost.php?p...3&postcount=22

push shift and right button mouse inside the folder (on blank space) and open command prompt here,after then write:
anaria_norvalidator.exe namedump.bin

[haz367]

damn..i'm a noob..nvm...thx again

[donkey-punch]

Originally Posted by guerrierodipace Don't use drag and drop!!!!! look my screenshot here http://www.ps3hax.net/showpost.php?p...3&postcount=22 push shift and right button mouse inside the folder (on blank space) and open command prompt here,after then write: anaria_norvalidator.exe namedump.bin

super star Thanks for the help
************* [ - Post Merged - ] *************
Ok I have checked a few bad dumps I had on my laptop with this tool and I have checked good ones and this thing really seems to work. So is this safe to use or is this still to early to confirm safe and should I keep checking dumps manually?

[madman158]

Originally Posted by donkey-punch super star Thanks for the help ************* [ - Post Merged - ] ************* Ok I have checked a few bad dumps I had on my laptop with this tool and I have checked good ones and this thing really seems to work. So is this safe to use or is this still to early to confirm safe and should I keep checking dumps manually?

I will keep checking dumps just to be safe but it does look to be real soild.

[6ar]

This is great!! You're the best, hope it becomes THE 'official' application to check dumps

[afzoo3hax]

Originally Posted by anaria Hi Guys, I'm no dev nor a PS3 expert, but

This alone qualifies you to be an expert. At least as far as these best-efforts verification tools go. It is pretty darn awesome.

There are probably more little bugs and wiggle room for extra detection and rejection improvement. Even so, it already seems good enough (in quality) as any of the other verification tools that are officially referred to at the PS3DevWiki.

Here is a list of possible next steps you might consider:

* Add your tool to "other verification tools" section of "Verifying FLash Dumps" PS3 wiki page. Or indeed as one of the primary tools!

* If you want to propose the changes, but without it being official just yet. Then you can always add your stuff temporarily into the "Talk" Tab until other Wiki people will formally approve it.

* You might have no suitable place to permanmently host the download (and your latest source code too!). This is important to have a good permanment link for the official Wiki to point to. BwE might be able to offer your tool a coveted place next to the other verification tools on his website (betterwayelectronics dot com). You should really ask him about that.

* You can talk to BwE and many of the others who oversee the official PS3DevWiki by logging in to the #ps3downgrade channel. But you must first log in to EFNet irc servers!! (otherwise you will be alone and see nobody on there).

* Stay logged in to irc and collect for people posting their failed dumps. With a failed dump you can improve upon the rejection capabilities of your tool. For example to detect bad address lines.

* Command line switches should be added in the --help.

* Maybe Judges' win32 build are worth to include too. If it doesn't depend on Cygwin. Otherwise write that as a dependency requirement for windows, i suppose ? Or maybe BwE can help you convert this to a proper standalone Windows binary for you. I have no idea.

And 1 Last request: This is an important issue, so I hope you will consider it.

* Our Problem: All these verification tools is they are great: but they are not trusted. None of us users know how much of the verification they actually are doing. Where? In that same table we all go to. Help us know exactly how comprehensive your tool is. And build a stronger trust of the automation when using it.

* Suggestion: Go back to the big table of offsets in PS3DevWiki. And add a new column to the very right of that table. Make the title of the column the same name of your cmd line tool "NORDumpTool".

* For each row (offset location) in that list, if your automated tool checks for it, then to make a [X] or brief notes to indicate it is supported. We want to clearly see exactly which of the offsets that we usually manually check for - were also automatically checked for. Then we can manually check ourselves any remaining (not supported or newly added) offset.

And thanks again!