Willy2

The following text (in italics) was taken from OEC's Facebook feed: "We are looking for translators of OE Classic user interface into the following languages (in the order of priority for OE Classic development): - Finnish - Portuguese (European variant only) - Danish - Japanese - Chinese (Traditional) - Chinese (Simplified) - Hebrew - Arabic We are only looking for one translator for each language. Translators should be native speakers of the above languages and decently fluent in English and should have familiarity using Windows programs in those languages (to recognize the appropriate translation commonly used in the language)." (It looks like that the next FREE version of OEC (v3.3.xx ? or v4.0 ? ) will be released this or next week. Fingers crossed). - Doesn't the CCleaner forum allow to "hotlink" to a YouTube video/channel (see my previous post) ? Is there a reason for that ?

- Thanks !!!! - Indeed "Start up boost" is not needed. Edge starts up fast enough.

- Ah, this could also explain why Chrome (without CLEANMEM running) sometimes occupies A LOT OF memory (sometimes even 4 GB or more). Every now and then I switch off CLEANMEM to see how memory usage is without "cleaning the memory". - Although REAL PLAYER (still alive & kicking and still being updated) has a Chrome like way of storing temporary files it doens't generate that kind of warning(s). - I have a follow up question related to MS Edge. When I run CC then I regularly get a warning "MS Edge is running and needs to be closed" (something along those lines). This is odd because the Edge icon on the taskbar doesn't indicate that Edge is running at all. But when I open Task Manager then indeed Edge is running with say 5, 6, or 7 processes and about the same amount of processes of "MsEdgeWebview2.exe". - Is the running of these Edge processes in this way normal ? Or was Edge started by some other application ? Or are these background Edge processes automatically started ?

- This sounds completely bonkers to me. These files are located on disk so it seems to me that they can be analyzed. Or does e.g. Chrome read those files, put them in the memory for use in the program ? - Again, I am sorry but sounds so absurd to me.

When CC is analyzing one's diskdrive then the program will ask me 3 times if I allow CC to close 3 separate programs (MS Edge, MS Onedrive & Google Chrome). Does those 3 programs REALLY need to be closed when CC is only analyzing one's diiskdrive ? Suggestion: Move those questions to the part where the actual cleaning is happening.

- The company that develops OEC now has a YouTube channel with currently 2 instruction videos for OEC. I assume more videos will be posted in the future. Weblink: https://www.youtube.com/@InfobyteTV

- Update for the post of june 18, 2020: The weblinks provided in that post have been removed and moved to new locations: RAMMAP: RAMMap - Sysinternals | Microsoft Learn Video weblink: Defrag Tools: #6 - RAMMap | Microsoft Learn - Still no updates for Defraggler available or any plans for an update ? I am one of those geeks who use the program EVERY (!!!!) day.

- Some files can't be defragmented. e.g. files relateed to the "System Restore Points". Those files can be VERY large GBs and scattered over many fragments.

- That was very usefull information. Seems the entries for Real Player are good after all. - I also saw the following "\real*player\". Is this asterisk a typo ? Or has this been done deliberately ? Does CCleaner allow that syntax ?

I think the entries in "winapp.ini" for "REAL Player" need some (more) "tweaking" because it seems CC doesn't clean out some special folders used by REAL Player. Perhaps this is a "Permissions issue" ? When I went through "Winapp.ini" I came across some things that raised some question marks. What are the target folders of 1) "%Appdata%" 2) "%LocalAppdata%" and 3) "%CommonAppData%" ? I assume "%LocalAppdata%" points to the folder "Local" under "AppData" ? But the 2 other variables remain a mystery for me. Or are these only meant for Windows 10 and 11 ?

- Does anyone know who has thourough knowledge of the danish language and wants to become a translator for the OEC emailprogram ? - Outlook Express Classic has advanced to version v3.2.74. Based on what I read on Facebook the developers are in the final stages of preparing the next OEC FREE version.

- It's like the old versions of .NET software. They can exist next to each other. - Is SPECCY already able to detect .NET 5 on one's system ?

Had to improve the previous post in 2 ways. Am I correct that the "|" character indicates that CC should only look for files and not directories ? FileKey20=%LocalAppData%\Real\RealPlayer\EBWebview\Default\Code Cache\js\|*.*FileKey21=%LocalAppData%\Real\RealPlayer\EBWebview\Default\Cache\Cache_Data\|*.*FileKey22=%LocalAppData%\Real\RealPlayer\EBWebview\|*.*

- The latest version of REAL Player (v20.1.0.312, released in early May (???) 2022) has adopted a kind of Chrome like storage of (temporary) files. That requires some additional lines for "winapp.ini": FileKey20=%LocalAppData%\Real\RealPlayer\EBWebview\Default\Code Cache\js\*.* FileKey21=%LocalAppData%\Real\RealPlayer\EBWebview\Default\Cache\Cache_Data\*.* FileKey20=%LocalAppData%\Real\RealPlayer\EBWebview\*.* See also the picture attached:

- The developers of Outlook Express Classic regularly keep issueing new releases for the program. The latest version is v3.2.65 and was issued may 24, 2022. OE Classic - Easy to use Outlook Express replacement

The person in this video burns Windows 11 down to ground. He gives several reasons why - in his opinion - Windows 11 is going to be a disaster. He points out that - bit by bit - Microsoft is forcing the user to no longer to own but rent the software one is using on one's computer. More and more users are forced to use "The Cloud" on a rental basis. More and more computer users won't be able to (really) own their own computer and their own data anymore. https://www.youtube.com/watch?v=LcafzHL8iBQ My knowledge of Windows 10 or 11 is close to zero. That's why I have the following questions: Do other people share the concerns/the worries this person is bringing forward ? Is Windows 11 indeed the "software monster" as portrayed in this video ? Is this really a big problem ?

- Right. When "System Restore" is active then running Defragler (think: moving files around) will trigger Windows to make an additional System Restore Point. Hence the loss of free diskpsace.

- OEC PRO version v3.2.58 released. I hope that the final version OEC v3.2 will be released (very) soon. https://www.oeclassic.com/

- When one switches from a HD to a a SSD one also should turn off the build-in Windows' Defragmentation feature/scheduler. (which I did).

Yes, the program code of DF needs a very decent overhaul of the program code. I noticed that DF still moves files (in my case *.mp4 files ) towards the beginning of the drive without my consent. (No, I turned off Windows Disk Defragmenting program). It seems that DF hasn't got "all its ducks in a row" and then moves the wrong files (towards the beginning of the drive). There could be a relationship with the High CPU usage when the user stops the program. Or perhaps DF takes the file from the memory (e.g. the socalled "Stand By" memory) of one's computer and then gets "confused" which files should be moved towards the beginning of the drive. Or perhaps interrupting DF messes up the info contained by DF in the memory. Or DF takes information from the file called "layout.ini". When I go through the content of this file then it also lists *.mp4 files that I have viewed in the (recent) past. There is more than one possibility why DF doesn't do a proper job .........................

- OEC version v3.2.51 released. I assume that there will be more releases the coming days. In each of these releases one or more bugs are fixed.

- New version of OEC PRO (v3.2.47) released. See my reply here: https://www.wilderssecurity.com/threads/oe-classic-discussions-and-updates.393261/page-21#post-3064973 The information below comes from OEC's Facebook page when OEC version v3.2.44 was released: "This update is a huge milestone for us - we've finished updating the program for a new compiler which brings us more modern features support which we'll be adding into OE Classic. Last compiler we were using was from 2010, so it is a huge step forward. This also took us a lot of time to make all the adjustments and tests to ensure everything works well. The update to the new compiler has revealed one major bug which could cause crash when exiting the program, which was completely hidden with the previous compiler even though the bug existed then as well. Another update is the support for High DPI monitors but this time - per monitor. Meaning - if you use 2 monitors and one of them is using lower DPI like 96 DPI, and another one higher DPI, when dragging the program from one to another monitor it will automatically readjust itself to higher or lower DPI, which wasn't the case previously. So it will make working with dual (or triple) monitors more comfortable. Some built in components were updated as well which again we couldn't do with the older compiler, so you'll notice some changes when dragging and dropping messages, more contrast for selected message in the list when message list is out of focus and more."

Quite simple. Next to the "X" (in the top right hand corner of the CCleaner GUI) there is a symbol to resize the GUI. Click on that and then drag & drop the borders of the GUI towards the centre of the screen.

- Another thing that nags me regarding this "high CPU usage" is the following: I can decide to click on "Stop" button in DF when the program is busy moving files//looking for a free spot to place a defragmented file/ ........... Then DF supposedly stops executing the program. Then I can decide to close the program using the "X" in top right hand side of GUI of DF. Here I then come across the thing that's nagging me. Then a window shows up with the message (something along the lines of) "DF is executing a task. Do you really want to stop the program?". That's odd, very odd because DF gave me the impression that - although that CPU was still very high - DF had stopped all its "operations". In other words: This message "....... Do you really want to stop the program ?" shouldn't be displayed at all because supposedly the program had finished executing the program code.

- In the past I reported more than once about (very) high CPU usage when DF is "Winding Down" after the user has stopped one or more operations in DF. Last week I came across another example how this High CPU has a detrimental / negative impact on the program's performance. I wanted to change the size of the drive map. But the program code was still too busy "Winding down" (with high CPU) that DF didn't redraw (/ recalculate ) the drive map until that "Winding Down" was finished. The amount of time it took the program to "Wind Down" was simply too long and I decided to close the program and re-start it. - I think that the focus of the developers of DF should be on (sharply) reducing the time this particularly annoying "Winding Down" takes. I think solving this problem should have "top priority", should be placed on top of the list with priorities for the DF program. This "Winding Down" problem - IMO - even warrants a separate update on its own. - In the past I also wrote computer programs. Back then I learned that there were very specific guidelines on how to terminate a program that could be running for a long time. That one program had to regularly check the state of one variable. And when that variable was in one particular state (e.g. the user had pressed one particular key) then a program should the change the conditions in a programming loop in such a way that the program would abandon a program loop ASAP.