Can get tray icon, up but all is greyed out

[mad mikee]

Tried like everyone says:

1. Shutdown all D2OL procs (Services/etc)
2. Go to d2ol ...d2ol and start d2ol.exe (tried from explorer and cmd prompt)
3. See Icon in tray, right click and all I see clickable is EXIT.


Have played w/ control and general.prp, no change on clickability

WHAT AM I MISSING PLLLLEEEEEEAAAAAASSSSSEEEEEEE :brick:

Please confirm that what you tell us works since I'm sure a bunch of people will see any answers and run off and try them. Don't want everyone messed up on account of this.

/me goes back to search some more....

Thanks MikeE

[[XC] moddolicous]

If u wait it should eventually un-grey itself. Give it like a minute.

[[XC] DragonOrta]

yeah, D2ol has to start up. Once that happens, you can do what you want.

[mad mikee]

Attempts to click on anything get no response even when 'live'

Next!?

/edit of course I am doing this out here so all will learn from :am:

[mad mikee]

Rather than explain all the goodies I just found GO HERE :D

C:\XS_D2OL\D2OL1\D2OL\README.TXT
Covers:
* Property Settings (Tells you what to look for/change, but not what files they are in (usually ...\res\general.prp,)

* Multiple Node Controllers THIS IS WHERE THE CMDLINE/'Run' parameters are outlined (such as d2ol controller:java to get the gui back up again :D ) also the command line interact commands to D2OL, etc.

If I am reading this correctly - FLUSHING TASKS FLUSHES THE TASK LIST, NOT THE RESULTS TO GET THEM TO THE SERVER :mad:, which is why this line of inquiry was started :dammit:

And so ends tonight's lesson on D2oL - resurrecting the GUI after install :D

[Rodzilla]

FLUSHING TASKS FLUSHES THE TASK LIST, NOT THE RESULTS TO GET THEM TO THE SERVER :mad:, which is why this line of inquiry was started :dammit:

And so ends tonight's lesson on D2oL - resurrecting the GUI after install :D

:D Yep that's a problem! Hit manual upload instead ;)

[[KoG]^weaZel]

one thing I have noticed with D2OL, is that it will get borked quicker than the OS when there is an unstable OC. Meaning that if your overclock is NOT 100% 24/7 stable. Then D2OL feels the effects of it first. And as MikeE is experiencing when you try and open either the status or the main screen it will just be greyed out and not get any info on it. And yes I find all of this stuff out the hard way.

[Rodzilla]

^weaZel']one thing I have noticed with D2OL, is that it will get borked quicker than the OS when there is an unstable OC. Meaning that if your overclock is NOT 100% 24/7 stable. Then D2OL feels the effects of it first. And as MikeE is experiencing when you try and open either the status or the main screen it will just be greyed out and not get any info on it. And yes I find all of this stuff out the hard way.

This can be fixed by replacing all of the contents of the "jre" folder... I always get this. Something in there gets corrupt and it never starts the tray icon, never launches Gridwin or dockwin. But it's running in the task manager.

Just stop it and replace the jre folder and you should be AOK.

[[KoG]^weaZel]

Thanks for the info!

[Rodzilla]

hasn't failed me yet... I just wish that I knew exactly which file was getting borked...

[[KoG]^weaZel]

hasn't failed me yet... I just wish that I knew exactly which file was getting borked...

yeah it seems extra sensitive to minute instabilities in clockspeed.