Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

b2s tools should not allow to be run as admin #75

Closed
JockeJarre opened this issue Dec 23, 2023 · 24 comments
Closed

b2s tools should not allow to be run as admin #75

JockeJarre opened this issue Dec 23, 2023 · 24 comments

Comments

@JockeJarre
Copy link
Collaborator

If the tools are started as admin, they will try to store files in the windows32 folder.
To avoid this to happen, a requester will come up and say, this should not run as admin and then quit.
JockeJarre added a commit that referenced this issue Dec 23, 2023
@JockeJarre
b2s tools should not allow to be run as admin #75
bfd7f4d
@ivo71
Copy link

ivo71 commented Jan 8, 2024

I'm getting this error on the latest version as well (B2SServer-2.1.1-f5d3989-Release-win-x86.zip)

@JockeJarre
Copy link
Collaborator Author

JockeJarre commented Jan 8, 2024 •
edited

When does it happen?

This is a new "feature", there are many issues coming up because users are using the toolset wrong. Please check why your installation is starting as admin.
The only B2S program, which has to be started as admin, is B2SBackglassServerRegisterApp.exe, the rest should not!

B2SServer-2.1.1-f5d3989 is not a new release version... it is a build among others, we are testing new features...

@ivo71
Copy link

ivo71 commented Jan 9, 2024

I am using the 2.1.0 release and that works fine. I have set everything up with the baller installer and Rudy's guide, which everybody recommends. I can't see any files with the property of start as administrator turned on, so I am not sure how to turn it off. After finding out the 2.1.1 version gave that error, I simply copied 2.1.0 over it again and started the register app and clicked yes to both questions. Now the error is gone. When I copy and register 2.1.1 over the 2.1.0 version, the error is back again.

@JockeJarre
Copy link
Collaborator Author

Thanks for the confirmation. So you mean it is while running the register app, you get this error?
I will check how we can fix that!

@JockeJarre
Copy link
Collaborator Author

JockeJarre commented Jan 9, 2024 •
edited

I was trying here with the latest build B2SServer-2.1.1-fefecf7-Release-win version, but I do not get this coming up.
Can you please describe what you do with screenshots more exact?

@ivo71
Copy link

ivo71 commented Jan 10, 2024

  1. I am on 2.1.0 and all works fine
  2. I copy the contents of the zip of the latest version and overwrite the files in the tables directory.
  3. I start B2SBackglassServerRegisterApp.exe and click Yes, OK, Yes to answer the registering overwrite questions.
  4. I start a table or double click a b2s file and immediately a pop up appears with the error as shown in the photo (You should not start this as administrator).

When I do the same steps by copying 2.1.0 files over the 2.1.1 files and register them, the problem is gone and everything works fine.

I also tried the version you mentioned (B2SServer-2.1.1-fefecf7-Release-win) and it still has the same error.
B2S-error

@JockeJarre
Copy link
Collaborator Author

thanks for the info! I will check this.

So when running the table through VPX, this isn't a problem, only when you double click the backglass?

@ivo71
Copy link

ivo71 commented Jan 10, 2024 via email

@JockeJarre
Copy link
Collaborator Author

Ok, cause I trying to get more info, when it happens, and this was what you were describing...

Can you please also try double clicking the B2S_ScreenResIdentifier.exe, if you get the same problem here? And if yes, try the 2.1.0 version, if it is able to read and write the screenres.txt correctly.

thanks for the support

@ivo71
Copy link

ivo71 commented Jan 11, 2024

in 2.1. I tried to start B2S_ScreenResIdentifier.exe and it works, but the screens were a bit messy (1st photo).
Then I installed 2.1.1 again and it gave the same administrator error as mentioned in previous messages (I could now not start it).
Then I installed 2.1.0 again and I could start B2S_ScreenResIdentifier.exe again without the error, but the screens were now small and on 1 screen (2nd photo)
1a

1b

@ivo71
Copy link

ivo71 commented Jan 11, 2024

Note, I had my screen at 200% when I started the file, which may have caused the messy layout.

@JockeJarre
Copy link
Collaborator Author

Yes, you cannot switch back and fourth between different scaling, cause your file is saved for the other scaling.

B2S toolset do "support" other scaling than 100%, writing correct sizes and so on, but I have still not yet understood why the GUI looks like this... would be nice with an additional .NET dev to support the project...

Regarding beeing admin... the new build check if the executable is run as admin, shows the requester and then quits. It has to be something weird going on, on your system. I do not know yet what to check. Once I know, I will come back to you.

For playing, please use the official release for now, and I am happy if you can continue help me test these builds going forward... I'll report when there is anything new to try out.

@ivo71
Copy link

ivo71 commented Jan 11, 2024 via email

@Mrtr32
Copy link

Mrtr32 commented Jan 26, 2024

I think if you have an administrator computer account the b2sserver show the administrator warning and don't start
My test computer are built with Windows 7 x64 since 2011 and with your administrator right change, the b2sserver stopped working

@JockeJarre
Copy link
Collaborator Author

I think if you have an administrator computer account the b2sserver show the administrator warning and don't start My test computer are built with Windows 7 x64 since 2011 and with your administrator right change, the b2sserver stopped working

You can safely use the official release for now. I will remove some of the admin tests soon so you can test it. Will inform you soon!

BUT! The B2S_ScreenResIdentifier, does NOT support being run as admin, because windows then automatically defaults to the windows directory instead of saving the screenres file where you expect it to be.

So I really think you should try to get rid of the installation where everything is running elevated. I beleive to know that it used to be the suggested solution to run as admin in the past, but that's no longer preferred.

And also remember that Windows 7 support ended about 4 years and 1 week ago, so there will come a day when the toolset will have a problem with Windows 7 in general.

@ivo71
Copy link

ivo71 commented Jan 26, 2024 via email

@JockeJarre
Copy link
Collaborator Author

I do not know if that can be a problem, I have UAC active and do not see this problem.
I will relax the tests, but still it isn't preferable to use admin rights everywhere

JockeJarre added a commit that referenced this issue Jan 29, 2024
@JockeJarre
relax b2s tools should not allow to be run as admin for B2SBackglassS…
746305b 
…erverEXE #75
@JockeJarre
Copy link
Collaborator Author

@ivo71 & @Mrtr32 I have now releaxed the admin check in the latest build. So now you should be able to test. Have fun!

@Mrtr32
Copy link

Mrtr32 commented Jan 29, 2024 •
edited

Work Great!

Thanks!

@ivo71
Copy link

ivo71 commented Jan 30, 2024 via email

JockeJarre added a commit that referenced this issue Jan 30, 2024
@JockeJarre
relax b2s tools should not allow to be run as admin for B2SBackglassS…
c20ddb5 
…erverEXE #75
@JockeJarre
Copy link
Collaborator Author

Hi, I have relaxed the admin check again in the screen_res_identifier.

This version just informs that admin should not be used, but does not exit.

@ivo71
Copy link

ivo71 commented Jan 30, 2024 via email

@JockeJarre
Copy link
Collaborator Author

We have seen some reports of people starting screen_res_identifier and getting a message that the file cannot be saved to c:\Windows... this was an attempt to make these problems disappear where they occur (50 cm behind the user's screen).
But maybe this isn't the right way to test... or I will add it as a text in the windows instead of a requester.

This is a interim build which is meant for testing, so thanks for testing!

JockeJarre added a commit that referenced this issue Mar 20, 2024
@JockeJarre
Revert "b2s tools should not allow to be run as admin #75"
6f13aef 
This reverts commit bfd7f4d.
JockeJarre added a commit that referenced this issue Apr 1, 2024
@JockeJarre
Revert "b2s tools should not allow to be run as admin #75"
103341c 
This reverts commit bfd7f4d.
JockeJarre added a commit that referenced this issue Apr 1, 2024
@JockeJarre
Squashed commit of the following:
61b3a16 
commit f006180
Author: Jarr3 <Richard.Ludwig+gh@gmail.com>
Date:   Mon Apr 1 13:55:07 2024 +0200

    Update b2s-backglass.yml, remove betterled

commit 0f0d345
Author: Jarr3 <Richard.Ludwig+gh@gmail.com>
Date:   Mon Apr 1 13:19:15 2024 +0200

    mergeBulbs once

commit 0a1265d
Author: Jarr3 <Richard.Ludwig+gh@gmail.com>
Date:   Mon Apr 1 13:16:13 2024 +0200

    Fix compile error

commit 0a49a63
Merge: fedb1b0 c20ddb5
Author: Jarr3 <Richard.Ludwig+gh@gmail.com>
Date:   Mon Apr 1 12:43:20 2024 +0200

    Merge branch '76-events-of-overlapping-pictures-get-merged'

commit fedb1b0
Author: Jarr3 <Richard.Ludwig+gh@gmail.com>
Date:   Wed Mar 20 08:01:13 2024 +0100

    Events of overlapping pictures get merged #76

commit 6f13aef
Author: Jarr3 <Richard.Ludwig+gh@gmail.com>
Date:   Wed Mar 20 07:49:06 2024 +0100

    Revert "b2s tools should not allow to be run as admin #75"

    This reverts commit bfd7f4d.

commit 107a1f9
Author: Jarr3 <Richard.Ludwig+gh@gmail.com>
Date:   Fri Mar 1 07:08:40 2024 +0100

    Revert Make StartAsEXE and DisableFuzzyMatching the default and only mode available #72

commit 1ead93e
Author: Jarr3 <Richard.Ludwig+gh@gmail.com>
Date:   Thu Feb 29 18:56:06 2024 +0100

    Update DB2S Not lights up at start, but only with PWM modified tables #81
    Increase documentation

commit 4cf6b0a
Author: Jarr3 <Richard.Ludwig+gh@gmail.com>
Date:   Wed Feb 28 19:17:05 2024 +0100

    DB2S Not lights up at start, but only with PWM modified tables #81
    Changed treshold to 64

commit ffdb408
Author: Jarr3 <Richard.Ludwig+gh@gmail.com>
Date:   Wed Feb 28 07:11:33 2024 +0100

    DB2S Not lights up at start, but only with PWM modified tables #81
    First test, mapping all values > 128 to boolean True

commit d468f07
Author: Jarr3 <Richard.Ludwig+gh@gmail.com>
Date:   Mon Feb 26 19:47:11 2024 +0100

    B2S.Server log plugin loading information and possible errors #82

commit b829c0a
Author: Jarr3 <Richard.Ludwig+gh@gmail.com>
Date:   Wed Feb 7 07:43:40 2024 +0100

    b2s_screenresidentifier: Add Comments hidded behind the taskbar #77
@JockeJarre
Copy link
Collaborator Author

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@JockeJarre @ivo71 @Mrtr32