Jump to content

Search the Community

Showing results for tags 'gui'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • Official PlayStation News
    • PlayStation Scene News
    • Forum Related News
  • Help Forums
    • PlayStation - PS1
    • PlayStation 2 - PS2
    • PlayStation Portable - PSP
    • PlayStation 3 - PS3
    • PlayStation Vita - PS Vita
    • PlayStation 4 - PS4
    • PlayStationHaX Русское Сообщество
    • PlayStation 5 - PS5
  • Console Histories
    • PlayStation History
  • Other Consoles And Devices
    • Nintendo
    • Xbox
    • Computers
    • Single Board Computers
    • Mobile Phones And Tablets
    • Blu-Play
    • General Gaming Discussion
  • Off Topic
    • Off Topic
    • Member Introduction
    • PlayStationHaX Friends
    • Fun & Laughter
    • Cinema
    • Site Suggestions & Help
  • Rubbish
    • Rubbish
  • Club GregoryRasputin's Ra Ra Rasputin
  • ConsoleHax (NL)'s Welkom!
  • ConsoleHax (NL)'s Nieuws
  • The I Haven't Created A Club Yet Club's Topics
  • Nintendo Switch Club's Switch Tools
  • Nintendo Switch Club's Emulators, Games, and Ports
  • Nintendo Switch Club's Switch Help
  • Nintendo Switch Club's Switch News
  • PlayStationHaX España's YouTube Topics España
  • PlayStationHaX España's PlayStation News España


  • PlayStation
    • PS3
    • PS Vita
    • PSP
    • PS4
  • Nintendo
    • 3DS
    • Wii
    • Wii U
    • Switch
    • Retro
  • Xbox
  • Documents
  • PS3History


  • Game Consoles
  • Music
  • Movies
  • People
  • Geography
  • History
  • Math


  • Event
  • PlayStation Game Release
  • Microsoft Game Release
  • Nintendo Game Releases
  • Multi Format Game Releases

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL




Found 2 results

  1. Re-Release: PS3.Proxy.Server.GUI By CF3B5 Right, so Guys I recently made a thread on another forum RE-RELEASING an old tool (pretty ancient tool actually) was designed for the Wii, the PSP, and the PS3 It's a proxy. I managed to gather all of the files including the Extended Edition, and both of the .NET frameworks And it works on PS4on 3.55, right now. at this very moment. I don't know how helpful this is with the skfu proxy tool out and floating about. but i'm trying to be helpful by re-releasing what is probably one of the best tools out there And it still works. Everything is in one rar file because the installer doesn't do anything anymore. from what t i remember, it just tells you to go get a .NET framework which isn't on Microsoft's page anymore but included it and a batch file to download it and the updated one. I hope i'm not offending or pissing anyone off by doing this. it would be the last thing on my wish list. I also included the YetAnotherBypass (YAB) batches and executable though i'm lacking the src. Nice, huh? CREDIT GOES TO THE RESPECABLE DEVS WHO MADE THESE TOOLS POSSIBLE. https://mega.nz/#!rUojTBKY!FTP6qfa1BhivhzOnnPV-TCIjdNhamjknO6Y0uLKbOsE https://mega.nz/#!Cdg1BIAR!FTP6qfa1BhivhzOnnPV-TCIjdNhamjknO6Y0uLKbOsE https://mega.nz/#!fFZRwCIb!FTP6qfa1BhivhzOnnPV-TCIjdNhamjknO6Y0uLKbOsE https://mega.nz/#!WIYHxACC!FTP6qfa1BhivhzOnnPV-TCIjdNhamjknO6Y0uLKbOsE https://mega.nz/#!LRhhlJyL!FTP6qfa1BhivhzOnnPV-TCIjdNhamjknO6Y0uLKbOsE https://mega.nz/#!yIwABCKb!FTP6qfa1BhivhzOnnPV-TCIjdNhamjknO6Y0uLKbOsE
  2. Hello there! I've had enough of all these random "GUI creators" that gets praised to heavens for something that is so easy to make. So today, I will show you one way to create your very own GUI for virtually any console program! I will be using DiscU in this example, and will show you how to execute the extracting process from a GUI. Pre-requirements: A C# coding environment(Visual Studio Community for example, its free!)* Know a tiny bit of the principle of coding, e.g. know what string, int etc are. A GUI-less console application. A cup of coffee... Or a pot if you're easily stressed (this is a must for any programmer!) *I'm a terrible teacher, so I suggest you familiarize yourself with the interface first. Disclaimer: I am in no way a good programmer, and I haven't touched C# in at least a year. I am certain there are a lot of better ways to communicate with the console application, but the following method is what I think is the easiest. And I take no responsibility if you someone blow your computer up, cat catches on fire etc etc. Enough bullshit, lets start coding! The first thing you should do is creating a new Windows Form Application project. You should see something similar to this: Mmmm, yeah, thats not a very useful gui, now is it? We need to add some things to it! Open up the toolbox(ctrl+alt+x), if its not already open, and drag a Button onto the Form. You should end up with something similar to this: If you want, you can change the text on the button by using the properties-panel in the botton right corner. Right, but a single button wont be of much use, we need something else... Drag a ListBox onto the Form, just like the button, and add another button as well. You should end up with something like this: Ok, that'll do for now, Im only convering a very basic GUI after all... Right, time to add some code! Without code, them buttons wont do much(read: nothing) Doubleclick Button1(or whatever you named it) to bring up the code. First thing you want to do is look at the top, where you will see a bunch of "using xxx". We're going to add another library here called System.Diagnostics . Just add it under the last entry so you end up with this: using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Threading.Tasks; using System.Windows.Forms; using System.Diagnostics; Next, move your eyes down to the button1_click handler. What we want to do here is making the button open the File Browser. I'll explain in the code: private void button1_Click(object sender, EventArgs e) { OpenFileDialog browseFile = new OpenFileDialog(); //this will open the file browser, as the name suggest. "browseFile" is your own identifier for this action, and can be anything. browseFile.Title = "Select File"; //This changes the title of the File Browser, again, this can be anything. Also note that we are now calling "browseFile" as defined in the previous line. if (browseFile.ShowDialog() == DialogResult.Cancel) //This is quite simple, if you press cancel... return; //just ignore it and return to whatever. try //however, if you press anything other than cancel(such as 'open' or double-clicking a file) then we try the following: { listBox1.Items.Add(browseFile.FileName); //We add the selected file to our listBox } catch (Exception) //in case something goes wrong, we need to catch the error(exception) ... { MessageBox.Show("Error opening file", "File Error", MessageBoxButtons.OK, MessageBoxIcon.Exclamation); // ... by for example shoving a MessageBox in our faces. VS should give you enough info to understand what each argument is used for, but the naming is quite self-explanatory. } } At this point, you can compile your code and test the functionality of Button1 and the ListBox. If everythings right, it should look something like this after a file is selected: Now we get to the climax of this tutorial(or whatever you want to call it). Doubleclick button2(which hopefully isnt a lie on your end ) Now, the following is quite hard to explain(because Im a retard and cant explain for shit...), but I'll do my best to keep it simple... The first thing we need to do is creating a string with our desired console command. This should be the same as the console application uses through cmd.exe. In my case this would be "titlekey.bin game.wad commonkey.bin" which looks like this in code: string strCmdText = "disckey.bin " + listBox1.GetItemText(listBox1.SelectedItem) + " ckey.bin"; However, since the game path is unique for each game, we need the GUI to insert that unique path. This is why we created the file broswer and listbox earlier! The code above grabs the text of the currently selected item in the listbox, and uses that as the path to the game. The way our code works at this stage is that the text in the listbox is the whole filepath. This can be changed, and will then require a different method to get the file path. I will not cover that here though. The next step is to set up the info needed for the process that launches our console program with the given parameters. This can be done in many different ways, but I think this one is the easiest(and also most limited...) So, to create this process we're going to use System.Diagnostics . The completed line should look similar to this: System.Diagnostics.ProcessStartInfo p = new System.Diagnostics.ProcessStartInfo("DiscU.exe", strCmdText); //the "System.Diagnostics." isnt needed, but for the sake of readability I use them. p can be anything of your choosing, p is short and nice in this case though. The first argument in ProcessStartInfo(), where I have "DiscU.exe", is what process the gui should launch, and the 2nd argument is the paramenters the process should be launched with. This will obviously be our pre-defined string of commands, "strCmdText" defined in the previous line. Next is a barrage of settings that defines how the process should be launched: p.RedirectStandardInput = true; //this allows us to redirect the input to our chosing, such as a message box p.RedirectStandardOutput = true; //this allows us to redirect the output, similar to input p.UseShellExecute = false; //when this is true, it basically means we have no control over it once its launched. p.CreateNoWindow = false; //Self-explanatory, when set to true the console will launch in the background, invisible. This should be set to true before releasing the gui to the public, but while coding and learning, it can be useful to have it open. There are a lot more options for those that want, but those 4 is what I consider the bare minimum to use. Now, then, its finally time to launch our process! So, time to create our process with the info provided by the processInfo we just set up. System.Diagnostics.Process proc = new System.Diagnostics.Process(); //similar to when we defined 'p', we now define the actual process. 'p' is already taken(duh), so that can not be used. I chose "proc" because why not? proc.StartInfo = p; //then we assign all the settings from 'p' to the proc(ess) proc.Start(); //and BAM! our process is hereby started! ... But hold your horses, theres still more work to be done. Some sort of debugging is always useful, so lets add that, along with a few absolutely necessary things: string output = proc.StandardOutput.ReadToEnd(); //we create a string that will store everything the console application is spitting out ... proc.WaitForExit(); //this is needed. We need our GUI to wait for the poor console application to finish its work. Console.WriteLine(output); //and here we are writing the text to VS's own console for debugging. //textBox3.AppendText(output); //... or you can create a textbox or similar and put the text right in your GUI. Console.Read(); //and this one updates VS's console so we can read it with our eyeballs proc.Close(); // and for god sake, dont forget this! If you dont close the process after its done, it will quickly lead to a huge memory leak and a lot of strange behaviours in your code, and inevitebly crash, burn, and kill your cat. Dont forget it. Hurray!! We are done, we have successfully created a simple GUI for a console application! Now launch that baby and test it out!!! ............... What do you mean its not working? Of course it is! ... Oh... Right... Before we can launch it, we need to include the necessary files. This means the files of the console application. This can be done in a few different ways. You can include them in the project, which I will explain momentarily, or copy the files to your debug folder in your projects folder(Documents->VS 2015(or whatever version you use)->projects->nameofyourproject->nameofyourproject->bin->debug(or Release, if you compile a release-version). For DiscU, I need 4 files included - DiscU.exe, libeay32.dll, disckey.bin and ckey.bin The other option is to include them directly in the project. In the Solution Explorer, which should be to the top/middle right, rightclick on the root item(called <your project name>), go to 'Add', Select 'Existing Item', browse to the needed files and select them to add them. On each of them, make sure the properties are set to copy the files as illustrated in a perfectly drawn blue circle*COUGH*: NOW, compile your code and try again. This time it should work This marks the end of this lesson. And No - the GUI is not pretty, its not advanced, and its very limited. This is just a basic GUI to get you started with communicating with console applications. And as I said at the beginning, this is just one of many ways. But with some determination you can transform this simple GUI to something like this: I hope you enjoyed this silly article/tutorial/whatever more than I did writing it lol... It took about 5 times as long to write this as it did to code the GUI Happy coding!
  • Create New...