Ripes icon indicating copy to clipboard operation
Ripes copied to clipboard

Ripes won't open up

Open joaomiguelaj opened this issue 3 years ago • 5 comments

Hello, I installed ripes because I need it in college. For context, my OS is Windows11. I installed Visual C++ and I installed Ripes, but when I unzip it and try to open the application, I click it twice, but nothing happens, it shows on the mouse pointer that is loading but nothing opens.

I need your help, please! Thank you.

joaomiguelaj avatar May 15 '22 19:05 joaomiguelaj

Hi @joaomiguelaj

Which version are you running? If you open Ripes through a shell (i.e. open Ripes through PowerShell) is there any output printed in the terminal? I've yet to do any testing on Windows 11, so that might also be a reason for the issues...

mortbopet avatar May 16 '22 06:05 mortbopet

Hi @mortbopet

No output in the terminal.

joaomiguelaj avatar May 16 '22 10:05 joaomiguelaj

I have the same problem,I can't open it,too.And my OS is also Windows11.

Kecxelic avatar Jun 08 '22 12:06 Kecxelic

Locally I'm able to open v2.2.4 it on Windows 11, so i cannot reproduce the issue.
To get to the core of this, it might be good if you could try building Ripes on your own machine(s) and then running it in Debug mode... Hopefully that should give us more clues as to what is going on.

mortbopet avatar Jun 08 '22 12:06 mortbopet

Thank you for your letter. I just became a student of Computer Science ​for one year. I'm afraid I don't have enough ability to compile and run by myself. Now I'm trying to use the rsic-v support plug-in in vscode, I'm sorry that I can't find out the problem. In addition, I am really happy to be answered by an excellent programmer.

------------------ 原始邮件 ------------------ 发件人: "mortbopet/Ripes" @.>; 发送时间: 2022年6月8日(星期三) 晚上8:35 @.>; @.@.>; 主题: Re: [mortbopet/Ripes] Ripes won't open up (Issue #207)

Locally I'm able to open v2.2.4 it on Windows 11, so i cannot reproduce the issue. To get to the core of this, it might be good if you could try building Ripes on your own machine(s) and then running it in Debug mode... Hopefully that should give us more clues as to what is going on.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

Kecxelic avatar Jun 08 '22 12:06 Kecxelic