XYplorer Beta Club

One more question. If you do NOT start on MyComputer then there is NO way to produce the crash, right?

admin wrote:One more question. If you do NOT start on MyComputer then there is NO way to produce the crash, right?

Correct.

Jeff Bellune wrote:

admin wrote:One more question. If you do NOT start on MyComputer then there is NO way to produce the crash, right?

Correct.

That would mean if I realize the disabling of redirection only after the first file browsing all would be fine. I only wonder why this first browsing (before disabling) should still show the expected folder when pointing to system32 ... well...

admin wrote:

Jeff Bellune wrote:

admin wrote:One more question. If you do NOT start on MyComputer then there is NO way to produce the crash, right?

Correct.

That would mean if I realize the disabling of redirection only after the first file browsing all would be fine. I only wonder why this first browsing (before disabling) should still show the expected folder when pointing to system32 ... well...

I agree - it is a mystery. I only hope that this intriguing mystery doesn't distract you from the very important task of making DP integrate seamlessly into the XY UI...

-Jeff

v7.90.0053... I tried a shot at it...

admin wrote:v7.90.0053... I tried a shot at it...

Sorry. No joy.

-Jeff

Jeff Bellune wrote:

admin wrote:v7.90.0053... I tried a shot at it...

Sorry. No joy.

-Jeff

You mean the same bug as before?

yea didn't help the crash, but it appears to have fixed the system32 fast switching problem when starting it with wow64 disabled (unless its just really fast now), also it seems to start alittle slower now with wow64 disabled, so possibly its still doing it before it shows the XY gui.

noir wrote:yea didn't help the crash, but it appears to have fixed the system32 fast switching problem when starting it with wow64 disabled (unless its just really fast now), also it seems to start alittle slower now with wow64 disabled, so possibly its still doing it before it shows the XY gui.

So my theory was wrong, resp. I have no idea what's going on.
Also the system32 startup behavior now and before is mysterious.

I'll set the code back to the (much simpler) previous state.

i think i found another bug that might be related disable wow64 then (you dont even need to restart xy) right click on a folder and click "Open" and it gives error

"class not registered."

open works fine with wow64 on.

noir wrote:i think i found another bug that might be related disable wow64 then (you dont even need to restart xy) right click on a folder and click "Open" and it gives error

"class not registered."

open works fine with wow64 on.

Confirmed here.

noir wrote:i think i found another bug that might be related disable wow64 then (you dont even need to restart xy) right click on a folder and click "Open" and it gives error

"class not registered."

open works fine with wow64 on.

You mean independent of starting on MyComputer??

yea doesnt matter where you start and it doesn't need mini tree either.

just plain old disable wow64 and right click "open".

noir wrote:yea doesnt matter where you start and it doesn't need mini tree either.

just plain old disable wow64 and right click "open".

Okay, that means the feature in its current state is crap. Gotta remove it.

confirmed that bug here too: