Request for test, windows users: ToME Launcher!

[darkgod]

No it'll download V1 and then upgrade it as I have not enabled V1.0.1 to download

[catwhowalksbyhimself]

Okay, just tried it again, and the launcher updated itself, then patched to new version without a problem.

[Graziel]

if it happens again that launcher stops responding, before running it again please upload launcher_log.txt somewhere on the net and post link here

[rusticdog]

if it happens again that launcher stops responding, before running it again please upload launcher_log.txt somewhere on the net and post link here

Here's the result for me. Note I can repeat this issue on every update of the launcher from V1 to V2. EDIT : Make that V1 to V4

Code: Select all

Available video driver: windows
Available video driver: dummy
[DO RESIZE] 700x350
[cURL] Creating cURL thread
[BSPatch] Creating BSPatch thread
Running lua loader code...

[Graziel]

bah sorry i forgot to tell it will output more info only on v4

[rusticdog]

bah sorry i forgot to tell it will output more info only on v4

Ah, right you are, I missed that. So the above is what I get when updating from V1 to V4. I guess I'll need to wait for a V5 though to see what happens when going 4 to 5 ?

[Crim, The Red Thunder]

empty folder downloaded 1.0 correctly, threw an error on patching to 1.0.1, updated fine from v1 to v4 without crashing, and then patched to 1.0.1 correctly. No flaws other then the 'no patchlist' error.

It does seem to be slower then downloading it myself however, but my net connection may have been acting up when I tried.

Tested on Windows XP with 512 meg of ram. (And if I can run it, ANYONE can.)

[dreadpatch]

Done downloading! When I ran it on an empty folder, it updated the patcher to v3, blank screened (had to "end process" it on task manager; it was not responding at this point) and it promptly downloaded ToME 1.0.0. When I copied the launcher to my existing ToME 1.0.0 folder, the launcher updated itself to v4, blank screened again, then downloaded and patched it to 1.0.1. Same thing happened when I opened the launcher again on the "empty folder" (that is, the one where I downloaded everything to an empty folder), it downloaded and applied the patch from 1.0.0 to 1.0.1.

Tested on Windows 7 64bit

EDIT: Forgot to post my launcher_logs here you go:
Ran from empty folder: http://pastebin.com/0Q2gzubh
Update from 1.0.0 to 1.0.1 http://pastebin.com/P7AVPw8z

EDIT2: I think I forgot to upload the logs from when it crashed. My bad ><

[Graziel]

can you see your task menager if there are 2 processes of launcher ? ie it will probably be 'patched-t-engine-launcher.exe' and 't-engine-launcher.exe'
if there are try to kill 't-engine-launcher.exe'.

[rusticdog]

can you see your task menager if there are 2 processes of launcher ? ie it will probably be 'patched-t-engine-launcher.exe' and 't-engine-launcher.exe'
if there are try to kill 't-engine-launcher.exe'.

Just the latter for me.

It's the RENAME_TO_AND_RUN that seems to be my issue. If I manually run the command(s) through DOS it will successfully terminate the launcher process, delete the old launcher, rename the patch file to the new...but always hangs on that first start when being triggered by the above.

Running patched-t-engine-launcher.exe manually starts as expected with no hang.

[Graziel]

can you try running this exe http://www.sendspace.com/file/301528 with that arg and see if it doesnt hang?

[rusticdog]

can you try running this exe http://www.sendspace.com/file/301528 with that arg and see if it doesnt hang?

Yup, that seems to work fine

[dreadpatch]

can you see your task menager if there are 2 processes of launcher ? ie it will probably be 'patched-t-engine-launcher.exe' and 't-engine-launcher.exe'
if there are try to kill 't-engine-launcher.exe'.

Was able to recreate the 'blank screen' crash from the launcher v1. I did check my task manager, there was only t-engine-launcher.exe there, so that's what I stopped. after that everything went smoothly. Same goes with the sendspace file. Before I forget, here is the launcher_log from the crash:

Code: Select all

Available video driver: windows
Available video driver: dummy
[DO RESIZE] 700x350
[cURL] Creating cURL thread
[BSPatch] Creating BSPatch thread
Running lua loader code...

EDIT: Tried opening it again, successfully updated from v4 to v5.

[rusticdog]

EDIT: Tried opening it again, successfully updated from v4 to v5.

Yup, mine just updated from 4 to 5 with no issues as well

[fipilos]

Everything works fine