Page 1 of 1

Awesome update! But..

Posted: Tue Mar 05, 2024 6:22 am
by HanzoDeceptor
Hi Wagnard!

Thank you for adding my last two requests (Form always on top & Purge command list). You are a good listener boss! :D

BUT..

Sadly, the only last working version for me is the ISLC v1.0.2.7. After that version, nothing will open. So i can't taste the new updated version. How ironic :lol:
1. Run CMD with Admin Privilege.
2. Type: LODCTR /R
(You may have to do this twice. Hopefully, you will get a message saying "Info: Successfully rebuilt performance counter setting from system backup store")
3. Reboot your PC.

If this does not work, we will check if you have disabled performance counter and re-enable it.

1. Run CMD with Admin Privilege.
2. Type: lodctr /q | find "Disabled"
3. Type: lodctr /e:PerfOS
4. Reboot your PC
lodctr option is not working either. Why?
Is this beautiful app leaving win 7 after v1.0.2.7?
Can you do something boss :D

Thank You!

Re: Awesome update! But..

Posted: Tue Mar 05, 2024 6:34 am
by HanzoDeceptor
Just info:
I tested and ran ISLC 1.0.3.1 via command line using ""C:\Users\PC\Desktop\islc\ISLC v1.0.3.1\ISLC.exe" -purge" and it did work and purge the memory. I monitor it inside the 1.0.2.7 version though :lol:

But after it purges the standby list, maybe 1 second after that, it raises the error (crashed). So, it did the job, but crashed after that before showing the main form.

Maybe this little information will help.

Thank you!

Re: Awesome update! But..

Posted: Thu Mar 07, 2024 10:43 am
by Wagnard
HanzoDeceptor wrote: Tue Mar 05, 2024 6:34 am Just info:
I tested and ran ISLC 1.0.3.1 via command line using ""C:\Users\PC\Desktop\islc\ISLC v1.0.3.1\ISLC.exe" -purge" and it did work and purge the memory. I monitor it inside the 1.0.2.7 version though :lol:

But after it purges the standby list, maybe 1 second after that, it raises the error (crashed). So, it did the job, but crashed after that before showing the main form.

Maybe this little information will help.

Thank you!
Found the bug, fix will be in the next version for windows 7. Sorry about that.


EDIT : 1.0.3.2 Released with the fix. Thanks again for reporting.

Re: Awesome update! But..

Posted: Fri Mar 08, 2024 4:13 am
by HanzoDeceptor
Still not working boss. I tried to reinstall dotnet 4.8 to make sure there is no error in my dotnet framework, but still the problem exists.
These  are the logs from the event viewer, just in case you want to know..


THIS IS FROM EVENT 1000, APPLICATION ERROR
=========================================
Faulting application name: Intelligent standby list cleaner ISLC.exe, version: 1.0.3.1, time stamp: 0xd5e1f0b8
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17965, time stamp: 0x506dcae6
Exception code: 0xe0434352
Fault offset: 0x000000000000bccd
Faulting process id: 0x648
Faulting application start time: 0x01da7137994be16f
Faulting application path: C:\Users\PC\Desktop\islc\ISLC v1.0.3.2\Intelligent standby list cleaner ISLC.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: d74b581f-dd2a-11ee-915c-364b50b7efda


THIS IS FROM EVENT 1026, NET RUNTIME
=====================================
Application: Intelligent standby list cleaner ISLC.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.EntryPointNotFoundException
at Intelligent_standby_list_cleaner_ISLC.Win32_SetProcessInformation.SetProcessInformation(IntPtr, PROCESS_INFORMATION_CLASS, IntPtr, Int32)
at Intelligent_standby_list_cleaner_ISLC.Win32_SetProcessInformation.SetProcessInfo(IntPtr, PROCESS_INFORMATION_CLASS, System.Object)
at Intelligent_standby_list_cleaner_ISLC.ProcessInformationWrapper.SwitchToHighQoS()
at Intelligent_standby_list_cleaner_ISLC.MainWindow.Main_Initialized(System.Object, System.EventArgs)
at System.Windows.FrameworkElement.RaiseInitialized(System.Windows.EventPrivateKey, System.EventArgs)
at System.Windows.FrameworkElement.TryFireInitialized()
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.InitializationGuard(System.Xaml.XamlType, System.Object, Boolean)

Exception Info: System.Windows.Markup.XamlParseException
at System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri)
at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext)
at System.Windows.Application.DoStartup()
at System.Windows.Application.<.ctor>b__1_0(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at Intelligent_standby_list_cleaner_ISLC.App.Main()

Re: Awesome update! But..

Posted: Fri Mar 08, 2024 6:41 am
by Wagnard
HanzoDeceptor wrote: Fri Mar 08, 2024 4:13 am Still not working boss. I tried to reinstall dotnet 4.8 to make sure there is no error in my dotnet framework, but still the problem exists.
These  are the logs from the event viewer, just in case you want to know..


THIS IS FROM EVENT 1000, APPLICATION ERROR
=========================================
Faulting application name: Intelligent standby list cleaner ISLC.exe, version: 1.0.3.1, time stamp: 0xd5e1f0b8
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17965, time stamp: 0x506dcae6
Exception code: 0xe0434352
Fault offset: 0x000000000000bccd
Faulting process id: 0x648
Faulting application start time: 0x01da7137994be16f
Faulting application path: C:\Users\PC\Desktop\islc\ISLC v1.0.3.2\Intelligent standby list cleaner ISLC.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: d74b581f-dd2a-11ee-915c-364b50b7efda

Updated, my bad I packed the old version :o

Download it again, you may have to clear your browser cache before downloading.

Re: Awesome update! But..

Posted: Fri Mar 08, 2024 1:48 pm
by HanzoDeceptor
Now ALL is GOOD!
ALL is PERFECT!
Thank you boss! :D

Re: Awesome update! But..

Posted: Tue Apr 09, 2024 1:26 am
by HudsonLambert
Thank you so much for the suggestion.