PetitTournesol / Edgeware

Elsavirus inspired fetishware, built from the ground up to use interchangeable packages for better user experience.
MIT License
128 stars 94 forks source link

Unable to run setup #42

Open PollyMaker opened 1 year ago

PollyMaker commented 1 year ago

Whenever I open the set-up, I press a key and the cmd window immediately closes. When run as administrator, it gives the error "cannot find 'C:\WINDOWS\system32/EdgeWare/start.pw'"

Sassy0P commented 1 year ago

When running as admin, it will change the current directory as explained in this stackoverflow post.

If you want to run as administrator, you could:

  1. Open "Command Prompt" as Administrator
  2. Execute the .bat in it. Either with the absolute path or by moving to its directory first.

But could you give your entire cmd output when not running as admin ? Might help to debug

PollyMaker commented 1 year ago

When ran normally, it gives this:

+==============[ Welcome to Edgeware Setup~ ]==============+ Python Version: Python 3.11.3 Edgeware is ready to start. Press any key to continue . . .

However when I press a key, it instantly closes the command prompt

Edit: Video link to show what's happening

Sassy0P commented 1 year ago

Thank you. So ye, it does seems like it's crashing, the question is now why. If you could share the in Edgeware/logs. And also give the output when you run the "debugScript.bat" and select the "start" option( 1, if I remember correctly)

PollyMaker commented 1 year ago

When I run the set-up batch file, it gives no log file. However, when I run the debugger, it runs the start option correctly, and also gives a log output. Though, another issue arises, and now whenever a sound plays, a horrid static sound accompanies it. Sun_May_21_23-03-33_2023-dbg.txt

Sassy0P commented 1 year ago

The setup should be only called once. Then it close and call the start.pyw which then should create desktop shortcuts etc. So it's normal that it is closing. But then you should have a popup for the config if it the first time(no config.cfg found to be specific)..

The audio problem is not a new one I think. Not sure what's the problem is exactly. Might be thread-locking problem.

So reducing the frequency might do it for the moment. What's your audioMod/Frequency ? You can check by launching the config.pyw(or via the debug script).