That command worked, running it now. I'll update when it's done.

Edited January 23Jan 23 by dragonorb13
clarification

Hmm. Net7 Launcher appears to be back to locking on v 1.9.9, though I'm *pretty* sure I saw a notice on one window or another that the current version of it was 2.4.5... Also getting the same error. Which is probably related to it not wanting to update past v1.9.9.

3 hours ago, dragonorb13 said:

back to locking on v 1.9.9

 

back to? you were having this problem before on Linux? (I don't see that in the thread above)

 

Typically I would refer you to this section of the troubleshooting page on the wiki:

 

https://net7wiki.bmsite.net/index.php?title=Troubleshooting#LaunchNet7_Not_Updating,_Stuck_at_v1.9.9

 

but in this case none of that should apply to you since you just used my script which should have created a brand new wine prefix and everything should be freshly installed.

 

Can you describe the details of the install process, for example:

1. Did it prompt you to remove an existing wine prefix, and if so, what did you answer? (e.g. "Permanently remove '/home/cs/.wine-enb' so this script can recreate it from scratch [y/n]?")
2. After the megan talking bit it should have started the launcher and gone through all the updates automatically, did that happen?
3. How are you starting the launcher after the install?

 

Can you provide a screenshot of your launcher window? (typically just hitting the print screen key above insert will take a screenshot on Linux)

Edited January 23Jan 23 by Codemonkeyx

Yeah, I actually had the problem before. I don't remember how I fixed it, but I managed to get it updated. But it didn't actually fix the problem I plopped in this thread for.

1) Yes, it requested exactly that. I hit Y.
2) It went through all of the EnB updates automatically, but I had to launch the N7 to update that on my own.
3) I'm just launching the N7 launcher off of my desktop. It runs the launcher up to the "launch game" button, then tosses the errors I originally notated.

Here's my launcher window:

10 hours ago, dragonorb13 said:

3) I'm just launching the N7 launcher off of my desktop.

 

This is on Linux Mint?  My script does not put a link to launch anything on the desktop. Did you try installing on Linux some other way previously? That shortcut is probably going to a bad install.

 

My script adds symlinks to ~/.local/bin:
 

$ ls ~/.local/bin/ | grep .wine-enb
lrwxrwxrwx 1 cs cs    81 Dec 29 02:37 enb -> /home/cs/.wine-enb/drive_c/Program Files/Net-7/bin/net7proxy.exe_wine_launcher.sh*
lrwxrwxrwx 1 cs cs   105 Dec 29 02:37 enb-cfg -> /home/cs/.wine-enb/drive_c/Program Files/EA GAMES/Earth & Beyond/EBCONFIG/net7config.exe_wine_launcher.sh*
lrwxrwxrwx 1 cs cs    90 Dec 29 02:37 enb-csc -> /home/cs/.wine-enb/drive_c/Program Files/EA GAMES/Earth & Beyond/CnSC.exe_wine_launcher.sh*
lrwxrwxrwx 1 cs cs    82 Dec 29 02:37 enb-launcher -> /home/cs/.wine-enb/drive_c/Program Files/Net-7/bin/LaunchNet7.exe_wine_launcher.sh*

 

Open a command prompt and run:

 

enb-launcher

 

It does also try to put stuff in the Gnome application menu, but whether that works or not is very distro dependent so best to just run the above command.

Yessir, Mint. Which otherwise works pretty well for just about everything, including a lot of games running through Steam. First run of enb-launcher gives me:

 

Configuring new '/home/zarius/.wine-enb/drive_c/users/zarius/AppData/Local/LaunchNet7/LaunchNet7.exe_Url_3lywl30pkun2mc4jsy5nabdkbl4zkwah/1.9.9.10/user.config'

 

After that, I just get the same result - open the N7 launcher at 1.9.9, gives the active Play button, and that returns the same error message. Repeat launches don't return that, but still give the error messages.

This is frustrating because I can run it on a VM, but the VM induces an irritating amount of lag... If I could get win xp/7 running properly on VM, it might  work fine, but I end up having to run win 10, and that's just uncooperative.

(Now that I think about it, I have a feeling that the way I got it working before was that I got it all working on the VM, then transferred the files to my linux install.)

Well, as a note, I was poking around out of irritated frustration, and slapped the "reset updates" button a few times. Eventually updated to 2.2.0, but still gives the same error message. Also gave me this through the terminal:

Configuring new '/home/zarius/.wine-enb/drive_c/users/zarius/AppData/Local/LaunchNet7/LaunchNet7.exe_Url_3lywl30pkun2mc4jsy5nabdkbl4zkwah/2.2.0.0/user.config'
Migrating previous ('/home/zarius/.wine-enb/drive_c/users/zarius/AppData/Local/LaunchNet7/LaunchNet7.exe_Url_3lywl30pkun2mc4jsy5nabdkbl4zkwah/1.9.9.10/user.config') into new ('/home/zarius/.wine-enb/drive_c/users/zarius/AppData/Local/LaunchNet7/LaunchNet7.exe_Url_3lywl30pkun2mc4jsy5nabdkbl4zkwah/2.2.0.0/user.config')
Migrating previous setting UsePacketOpt='False', replacing 'True'
Migrating previous setting FormMainPosition='845, 691', replacing '353, 358'

 

Edited January 23Jan 23 by dragonorb13

54 minutes ago, dragonorb13 said:

I have a feeling that the way I got it working before was that I got it all working on the VM, then transferred the files to my linux install.

 

Well I'm concerned that something that you did there is interfering with the install the script created.

 

51 minutes ago, dragonorb13 said:

slapped the "reset updates" button a few times. Eventually updated to 2.2.0

 

That's a good sign, and those other messages are normal and expected after updates are done, it's just trying to copy over any settings changes after those files get stomped by the update.

 

52 minutes ago, dragonorb13 said:

but still gives the same error message

 

Sorry, which error message is that, can you provide a screenshot?

 

Make sure you're only using:

 

enb-launcher

 

from the terminal to launch while we're working through this; I would just delete that desktop shortcut and whatever that is pointing to (e.g. whatever you copied from a Windows VM) as that is obviously broken.

Lemme just grab the full chain for you. I'm using just the enb-launcher terminal command as advised:

Launcher screen


Error pop up:


The actual error log:
backtrace.txt

This is the full sequence of things. After I hit the Close button on the Program Error window, it closes the launcher completely.

Edited January 23Jan 23 by dragonorb13

Try this:

 

WINEPREFIX=~/.wine-enb wine winecfg -v win7

 

Woo! That did the trick!

Just wanted to say the first script worked beautifully. I came searching here after the old trick I used to use on my steamdeck a few years ago (install the demo via lutris then net7 into that enb install) failed on my desktop and that script worked beautifully.