| View previous topic :: View next topic |
| Author |
Message |
srisinger
Joined: 10 Oct 2008 Posts: 4
|
Posted: Tue Mar 03, 2009 4:57 pm Post subject: |
|
|
| I confirm: I began experiencing the same "feature" about two weeks ago. I have a cube-neighbor with almost the exact same setup as me (I helped set up his computer), but he does not get the folder window upon startup. I am getting the User documents folder... |
|
| Back to top |
|
 |
uk_dave
Joined: 15 Feb 2009 Posts: 88 Location: Huntsville, AL, USA
|
Posted: Fri Mar 13, 2009 11:28 am Post subject: |
|
|
Well the good news is I [unintentionally] got the issue of a windows explorer on launch of Emerge being open fixed. The bad news is that it took emergeTasks crashing to get this resolved.
EmergeTasks suddenly started giving me Dr. Watson errors upon starting the applet. Bottom line, I had to remove all of my HKCU registry settings for Emerge to successfully launch its applets and then I had to rebuild all my applet settings from scratch. Removing my existing registry settings did have the pleasant side affect of resolving the explorer window being open on start up.
So if someone else is having the same issue of the windows explorer being open on start up, you might try exporting your HKCU Emerge registry settings for back up, then remove your HKCU Emerge registry, and then restart Emerge. Don't know if this will work for anyone else but perhaps someone that is having this same issue can attempt to debug it for the rest of us. I would do it but my original registry is obviously corrupt and crashing my emerge applets and with a fresh registry I don;t have the issue.
Emerge consistently crashing had me scared I might have to remove emerge -- I had to resort to using the Windows shell while I was trying to resolve the issue. Windows shell -- ugh!! |
|
| Back to top |
|
 |
cjbgf1
Joined: 06 Oct 2009 Posts: 2
|
Posted: Tue Oct 06, 2009 9:38 am Post subject: |
|
|
| Decided to bump this. I am also having the same problem, has anyone found a solution to this yet? |
|
| Back to top |
|
 |
MeToo
Joined: 11 Oct 2005 Posts: 1677 Location: Faro, Portugal
|
Posted: Tue Oct 06, 2009 10:23 am Post subject: |
|
|
Hi cjbgf1
Welcome to the Emerge Desktop forum!
Which eD build are you using?
I think this was already fixed (although I can't be sure, since luckily I don't use Vista ) _________________
build 5.1.0.330
Win XP x86 SP3 |
|
| Back to top |
|
 |
cjbgf1
Joined: 06 Oct 2009 Posts: 2
|
Posted: Tue Oct 06, 2009 11:33 am Post subject: |
|
|
Using vista against my own will .
I have switched between development release 2585 and build 4.1.3 with the same results. |
|
| Back to top |
|
 |
ironhead Site Admin
Joined: 10 Oct 2005 Posts: 879
|
Posted: Thu Oct 08, 2009 10:57 pm Post subject: |
|
|
| I should hopefully have some time this weekend to commender my daughter's PC (running Vista) and see if I can recreate the issue... |
|
| Back to top |
|
 |
fozzy_ag
Joined: 18 Feb 2010 Posts: 2
|
Posted: Thu Feb 18, 2010 5:59 am Post subject: |
|
|
Hi!
I used Emerge Desktop on my old computer (XP) whichout any (bigger) problems. My new computer has Windows 7-64 bit now and at first ED didn-t save changes to the themes, which worked then for some reason after loading all emerge programs once (Task, Tray, Sysmon...)
After some days without problems and without knowingly/intentionally changing settings, the problem started that after each start in ED all files and folders from the C-drive were opened/started. When I change to Explorer this doesn-t happen.
I tried searching the registry for stored ED settings but couldn-t find any.
My version is 4.2.0.2771 (64), which I think is the latest version.
Is there a solution to this, since other people had the same problem?
Thanks and keep up the good work. I loved using ED on my old computer and would love to use it again. |
|
| Back to top |
|
 |
MeToo
Joined: 11 Oct 2005 Posts: 1677 Location: Faro, Portugal
|
Posted: Thu Feb 18, 2010 11:52 am Post subject: |
|
|
Hi fozzy_ag
Welcome to the Emerge Desktop forum!
I'm running eD in a Win7 x64 (build 7100) virtual machine and I can't replicate your problem.
There are no registry settings. eD is now completely XML based. You can check all your XML files by typing %emergedir% in emergeCommand
There is no reason for this to happen... Please save your current Theme, and switch to the Default theme to check if that still happens.
You should also check your startup items (explorer ignores left-overs but eD doesn't). I recommend using Mike Lin's Startup Control Panel (http://www.mlin.net/StartupCPL.shtml) _________________
build 5.1.0.330
Win XP x86 SP3 |
|
| Back to top |
|
 |
fozzy_ag
Joined: 18 Feb 2010 Posts: 2
|
Posted: Fri Feb 19, 2010 3:00 am Post subject: |
|
|
Thanks for the answer.
I found the xml files after searching the hard drive for "emerge".
Now the funny part, there was an entry in the registry (actually two) but it wasn-t from emerge (it was in an IE registry entry - don-t ask me why and which one exactly)
After deleting these and restarting with eD it worked perfectly.
Thanks again and I'm happy to have my nic eD esktop back. |
|
| Back to top |
|
 |
Dark Vortex
Joined: 05 Mar 2010 Posts: 8
|
Posted: Fri Mar 05, 2010 10:55 pm Post subject: same issue |
|
|
I'm using Windows 7 Ultimate x64, with the newest emerge build, and I'm also having the issue mentioned here. I'm not sure what's up. I've tried the other suggestions, but I can't find any listing in my registry for emerge, nor can I find anything strange in my start-up procs (using Autoruns). Any help would be appreciated. I have switched back to litestep for the item being, and I have no issues with that, but I need 64 bit access, which LS doesn't provide. I'd love some ideas. |
|
| Back to top |
|
 |
MeToo
Joined: 11 Oct 2005 Posts: 1677 Location: Faro, Portugal
|
Posted: Sat Mar 06, 2010 12:09 am Post subject: |
|
|
Hi Dark Vortex
Welcome to the Emerge Desktop forum.
If you are using the latest dev build, both (x86 and x64) are XML based, as I mentioned in the previous post, so it is normal that you don't find any registry keys.
Can you uncheck all startup items and then enable them one by one? _________________
build 5.1.0.330
Win XP x86 SP3 |
|
| Back to top |
|
 |
Dark Vortex
Joined: 05 Mar 2010 Posts: 8
|
Posted: Fri Mar 12, 2010 8:59 pm Post subject: |
|
|
I can't do every single one. There's literally 152 different start up items in Auto Runs (mostly .dll's and windows components), but out of my non-windows items that run, I have Symantec Anti-Virus that runs, Nvidia Driver Services (Raid, Display, and Chipset), and Sound Max (my audio driver software). Anything else I've killed off already (as I hate a slow start up).
Now, I have killed Emerge from the start up list, and of course nothing happened when I switched back to Litestep. However, when I switch back, it's still there. So not sure if this helps, but if you have any suggestions for a specific thing for me to test, I'm all ears.
Thanks again. |
|
| Back to top |
|
 |
MeToo
Joined: 11 Oct 2005 Posts: 1677 Location: Faro, Portugal
|
Posted: Mon Mar 15, 2010 10:59 am Post subject: |
|
|
Auto Runs is a little overkill
Please use Mike Lin's Startup Control Panel. You can even use the portable version.
Please disable all items and then re-enable one by one. That is the only way to find the "guilty" item and to fix that bug. _________________
build 5.1.0.330
Win XP x86 SP3 |
|
| Back to top |
|
 |
Dark Vortex
Joined: 05 Mar 2010 Posts: 8
|
Posted: Wed Mar 17, 2010 8:53 pm Post subject: |
|
|
I tried your option, and it only listed two options for start up. I don't think it properly supports Win 7 x64. It lists two start up programs, ccApp and SoundMaxPnP. The ccApp is part of my anti-virus, and the Sound Max PnP is for my sound card.
Both were disabled (one at a time), and neither seemed to fix the issue of everything opening in my root drive. It still says, "Failed to Execute "". " and then opens everything.
Any other ideas?
Thanks again. |
|
| Back to top |
|
 |
MeToo
Joined: 11 Oct 2005 Posts: 1677 Location: Faro, Portugal
|
Posted: Wed Mar 17, 2010 10:38 pm Post subject: |
|
|
Those are bad news for me It means that when/if I switch to Win7 x64 I will have to give up on my favourite Startup Manager...
You hadn't mentioned there was a "Failed to Execute" box. This means there is a leftover from some program that wasn't completely uninstalled.
Try this one (never tried it but it comes from Nirsoft, so it must be good!)
http://www.nirsoft.net/utils/what_run_in_startup.html _________________
build 5.1.0.330
Win XP x86 SP3 |
|
| Back to top |
|
 |
|