Cannot Close Excel since installing Beta 3
Salamander 3.0 beta 3 x86 (& now seemingly Salamander 2.54 too)
Excel 2002
Win7 x64, Dell Laptop
Doulble-click an .XLS from within Salamander.
Excel opens, loading the wanted spreadsheet.
Click Excel's close button 'X'.
Nothing happens.
Close the file in Excel, Ctrl+W, works.
Click Excel's close button 'X'.
Nothing happens.
Close Salamander.
Click Excel's close button 'X'.
Nothing happens.
Kill Excel.
Excel closes & restarts (automatically).
Kill Excel.
Excel exits from memory.
---
Open Windows Explorer.
Doulble-click an .XLS from within Explorer.
Excel opens, loading the wanted spreadsheet.
Click Excel's close button 'X'.
Excel closes as expected.
---
salamand.exe
-> salmon.exe (as a child)
-> excel.exe (as a child)
At the first attempt to kill Excel, it is removed as a child to salamand.exe, then restarts with no parent, though still cannot be closed normally.
---
This is my fathers laptop.
He asked me about Beta 3 today & I said go ahead & install it.
Short time thereafter he noticed the issue.
Have to assume that all was well & working as expected prior to installing Beta 3 & that the issue is related to Beta 3?
Cannot Close Excel - Reolved, Unrelated
Cannot Close Excel - Reolved, Unrelated
Last edited by therube on 11 Sep 2013, 21:29, edited 1 time in total.
WinXP Pro SP3 or Win7 x86 | SS 2.54
Re: Cannot Close Excel
He also screwed around with MS .NET crap.
The programming end of it, different from the runtime (crap) that we all likely now have installed.
I'm running a System Restore & I'll see what comes of that...
The programming end of it, different from the runtime (crap) that we all likely now have installed.
I'm running a System Restore & I'll see what comes of that...
WinXP Pro SP3 or Win7 x86 | SS 2.54
Re: Cannot Close Excel
False alarm.
Running System Restore, then reinstalling Salamander Beta, & Excel is back to working properly.
So it looks to have been related to that .NET crap he installed.
Running System Restore, then reinstalling Salamander Beta, & Excel is back to working properly.
So it looks to have been related to that .NET crap he installed.
WinXP Pro SP3 or Win7 x86 | SS 2.54