Usenet Explorer

https://learn.microsoft.com/en-us/windows/win32/fileio/determining-whether-a-directory-is-a-volume-mount-point "To determine if a specified directory is a mounted folder, first call the GetFileAttributes function and inspect the FILE_ATTRIBUTE_REPARSE_POINT flag in the return value to see if t...

So it looks like a normal path only mapped to a different path?

Can you refer me to what it is exactly?

Even if something later in kernel32.dll and not present in earlier systems it is still easy to maintain backward compatibility.

I just wonder if it is possible to detect from the program.

If you are talking about paths starting with \\ and you want to try it with the checkbox checked I can compile a version and send you a link. I just added &&strncmp(*folder,"\\\\",2) before &&::RemoveDirectory(*folder) so it won't proceed there But if it is a different meth...

>although it was always hit and miss When you saved to that folder previously and the files are still listed in the unpack pane and the files are not in that folder any more on program restart only then it will call RemoveDirectory on that folder which will fail if it is not empty (but apparently th...

The program only calls ::RemoveDirectory, it doesn't know anything about mounted folders, the rest is how the system handles that https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-removedirectorya The description mentions something about links. What can be done when the option i...

Hi Steve,

Is it something related to Edit menu->Properties->Unpack "Delete empty save folders" or it is something else?

I see it is checked by default.

When using the latest version you can check "Check for updates" and uncheck "Check for minor updates", so the letter updates will be totally skipped. Those check for updates options are relatively recent addition, but they already work as expected. As to the release notes regardi...

In the upcoming v7.8.3d it will display proper warnings, as of now it presumes it always opened the nzb file, but in this case of course it doesn't happen, since the file name supplied by the system is different from the actual file name so it is useless.

It is an up-to-date version for registered users, many latest version changes which are not entirely new features make it to the up-to-date versions even if they are not mere bug fixes, because it also indirectly helps to keep the latest version more reliable. https://www.usenetexplorer.com/download...

Try to clear the browser cache, those letter updates have the same file name. Google chrome maybe works correctly, at least I didn't notice a persistent problem.

is it possible to avoid nzb names with unicode characters? usenet itself doesn't support unicode. since if not to compile with unicode enabled it replaces unicode characters with ? (ascii 63 question sign), so when you click the file it basically gets the wrong name, cannot open the file which cause...

it is an unicode nzb filename then, i'll check what is possible.

I've revised the update code further, so it hopefully always directs to the most relevant download depending on the update settings.

The latest version can be left as it is since the changes matter only in the case of its future updates.

I've just fixed it. It has something to do with the up-to-date releases. v5.9x (orders back to 2005, the arrangement since around two years ago) downloaded the .zip file, so I only uploaded v7.7c zip files, but the v7.7 code redirected to the executable file extractor. Now I compiled and uploaded bo...

The minor version was accidentally left from the previous version at the check for updates webpage, it will now alert correctly.