A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » General XP issues or comments
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

How to get back Win10 lost functionality from WinXP when opening 16 files at once?



 
 
Thread Tools Display Modes
  #1  
Old May 30th 17, 04:44 PM posted to microsoft.public.windowsxp.general,alt.comp.os.windows-10
Roy Tremblay
external usenet poster
 
Posts: 169
Default How to get back Win10 lost functionality from WinXP when opening 16 files at once?

How do we get back the Win10 lost functionality from WinXP when opening 16
files at once?

I just want to be able to select any number of *.ovpn files freely
available on the net to then right click and select "Open" so that they are
sent to the OpenVPN Daemon who will process them in a running-log window.

This use model worked fine on Windows XP but it no longer works on Win 10.

However, on Windows 10, you can only "Open" 15 contiguous files at a time:
https://s23.postimg.org/686mmlw17/open_dialog_15.gif

The moment you select 16 contiguous files, you lose the "Open" command:
https://s7.postimg.org/wtx6lvnd7/open_dialog_16.gif

The same Win10 anomoly occurs with disjoint files at the 15-to-16 junction:
https://s8.postimg.org/3uxyragn9/ope...5_disjoint.gif

All I'm asking is how to get Windows 10 to open 16 or more files at once:
https://s22.postimg.org/725sfq64h/op...6_disjoint.gif

--
NOTE: The use model works fine on Windows XP because only 1 file will be
successful, as any that are not successful will just hang in their
respective window and any that are successful after the first successful
connection will automatically close their running-log window. (Since the
running-log window is set to open in the same spot, I just position the
cursor on the [x] and close the stale running logs without moving the
mouse.)
Ads
  #2  
Old May 30th 17, 05:11 PM posted to microsoft.public.windowsxp.general,alt.comp.os.windows-10
Nil[_2_]
external usenet poster
 
Posts: 2,170
Default How to get back Win10 lost functionality from WinXP when opening 16 files at once?

On 30 May 2017, Roy Tremblay wrote in
alt.comp.os.windows-10:

All I'm asking is how to get Windows 10 to open 16 or more files
at once:


Try a batch file.
  #3  
Old May 30th 17, 07:29 PM posted to microsoft.public.windowsxp.general,alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default How to get back Win10 lost functionality from WinXP when opening16 files at once?

Roy Tremblay wrote:
How do we get back the Win10 lost functionality from WinXP when opening 16
files at once?

I just want to be able to select any number of *.ovpn files freely
available on the net to then right click and select "Open" so that they are
sent to the OpenVPN Daemon who will process them in a running-log window.

This use model worked fine on Windows XP but it no longer works on Win 10.

However, on Windows 10, you can only "Open" 15 contiguous files at a time:
https://s23.postimg.org/686mmlw17/open_dialog_15.gif

The moment you select 16 contiguous files, you lose the "Open" command:
https://s7.postimg.org/wtx6lvnd7/open_dialog_16.gif

The same Win10 anomoly occurs with disjoint files at the 15-to-16 junction:
https://s8.postimg.org/3uxyragn9/ope...5_disjoint.gif

All I'm asking is how to get Windows 10 to open 16 or more files at once:
https://s22.postimg.org/725sfq64h/op...6_disjoint.gif


http://www.thewindowsclub.com/print-...-files-windows

HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer
MultipleInvokePromptMinimum 15

The article says you might have to create that entry,
but I cannot imagine it is missing, as it is flagging
your activity right now.

Anyway, have a look.

Paul
  #4  
Old May 30th 17, 11:22 PM posted to microsoft.public.windowsxp.general,alt.comp.os.windows-10
Roy Tremblay
external usenet poster
 
Posts: 169
Default How to get back Win10 lost functionality from WinXP when opening 16 files at once?

Paul actually wrote:

http://www.thewindowsclub.com/print-...-files-windows

HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer
MultipleInvokePromptMinimum 15

The article says you might have to create that entry,
but I cannot imagine it is missing, as it is flagging
your activity right now.

Anyway, have a look.

Paul


Thanks Paul for looking that up.
- HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer
- Name : MultipleInvokePromptMinimum
- Type : DWORD
- Default : 15 (decimal)

It's an odd key based on this description in Microsoft KB KB2022295:
Context menus are shortened when more than 15 files are selected
https://support.microsoft.com/en-us/...s-are-selected

Quote:
A value of 16 is interpreted as "unlimited" for showing the *options* from
the context menu, however it does not allow the actual opening of the
documents selected if selecting more than 16. To allow the opening of more
than 16 documents, set this key to a decimal value greater than the amount
of documents you wish to open. Microsoft recommends only increasing this
value to a reasonable number in a controlled environment and only where
users really need this value increased.
The "MultipleInvokePromptMinimum" key doesn't exist anywhere in my default
Windows 10 registry, and certainly not in the location specified:
HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer\MultipleInvokePromptMinimum
https://s8.postimg.org/d2191mnx1/registry_multiple.gif

The article you unearthed linked to this Microsoft
Which is also covered he
Open, Print, Edit context menu items missing in Windows 10/8/7
http://www.thewindowsclub.com/fix-op...g-in-windows-7

1) Go to: HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer
2) Create a new DWORD, MultipleInvokePromptMinimum
3) A value of 16 (decimal) means the menu will always show (but not work)
4) A value of 100 (decimal) means it will work for up to 100 files.
4) A value of 200 (decimal) means it will work for up to 200 files.

Here is the 32-bit DWORD setting set to 200 files:
https://s10.postimg.org/559xqrt5l/re...ltiple_200.gif

BTW: How do I know to create a 32-bit or 64-bit DWORD? They never say.

--
NOTE: I need to kill and restart explore.exe but I've been running the
Microsoft Windows Malicious Software Removal Tool for almost 24 hours and
it's not even half way yet, so I'm afraid to kill & restart explore.exe
from the task manager. So I will have to wait to test it out for keeps.
  #5  
Old May 30th 17, 11:39 PM posted to microsoft.public.windowsxp.general,alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default How to get back Win10 lost functionality from WinXP when opening16 files at once?

Roy Tremblay wrote:
Paul actually wrote:

http://www.thewindowsclub.com/print-...-files-windows

HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer
MultipleInvokePromptMinimum 15

The article says you might have to create that entry,
but I cannot imagine it is missing, as it is flagging
your activity right now.

Anyway, have a look.

Paul


Thanks Paul for looking that up.
- HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer
- Name : MultipleInvokePromptMinimum
- Type : DWORD
- Default : 15 (decimal)

It's an odd key based on this description in Microsoft KB KB2022295:
Context menus are shortened when more than 15 files are selected
https://support.microsoft.com/en-us/...s-are-selected

Quote:
A value of 16 is interpreted as "unlimited" for showing the *options* from
the context menu, however it does not allow the actual opening of the
documents selected if selecting more than 16. To allow the opening of more
than 16 documents, set this key to a decimal value greater than the amount
of documents you wish to open. Microsoft recommends only increasing this
value to a reasonable number in a controlled environment and only where
users really need this value increased.

The "MultipleInvokePromptMinimum" key doesn't exist anywhere in my default
Windows 10 registry, and certainly not in the location specified:
HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer\MultipleInvokePromptMinimum
https://s8.postimg.org/d2191mnx1/registry_multiple.gif

The article you unearthed linked to this Microsoft
Which is also covered he
Open, Print, Edit context menu items missing in Windows 10/8/7
http://www.thewindowsclub.com/fix-op...g-in-windows-7

1) Go to: HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer
2) Create a new DWORD, MultipleInvokePromptMinimum
3) A value of 16 (decimal) means the menu will always show (but not work)
4) A value of 100 (decimal) means it will work for up to 100 files.
4) A value of 200 (decimal) means it will work for up to 200 files.

Here is the 32-bit DWORD setting set to 200 files:
https://s10.postimg.org/559xqrt5l/re...ltiple_200.gif

BTW: How do I know to create a 32-bit or 64-bit DWORD? They never say.


The DWORD is in their picture of Regedit.

And I don't pretend to understand why Microsoft did this.
It's pretty bizarre.

If I want to select 60,000 items and "do something" using
the Context Menu, why shouldn't I be allowed to do it ?

Maybe they could have put up a dialog with:

"Did you really mean to name_of_command on these 60,000 items ?"
Cancel or OK

Paul


Paul
  #6  
Old May 30th 17, 11:55 PM posted to microsoft.public.windowsxp.general,alt.comp.os.windows-10
Roy Tremblay
external usenet poster
 
Posts: 169
Default How to get back Win10 lost functionality from WinXP when opening 16 files at once?

Paul actually wrote:

The DWORD is in their picture of Regedit.


Just to clarify, that was *my* picture of my edit to 200 files.
The Microsoft KB KB2022295 instructions just said to create a DWORD.
They didn't say whether to create a 32-bit or 64-bit DWORD.
I can't reboot or kill explore.exe until the MSRT completes which has been
running for almost 24 hours so I would hate to kill it now.

And I don't pretend to understand why Microsoft did this.
It's pretty bizarre.


I thank you for *finding* what the problem was.
I knew it was *something* but the search keywords were all generic until
you came up with the MultipleInvokePromptMinimum registry key.

With *that* keyword, stuff started popping up in the searches!

If I want to select 60,000 items and "do something" using
the Context Menu, why shouldn't I be allowed to do it ?

Maybe they could have put up a dialog with:

"Did you really mean to name_of_command on these 60,000 items ?"
Cancel or OK


Didn't Windows XP do that if you opened up an inordinate number of files?

Anyway, I agree 100% with you and I thank you for finding the registry key.

After 4 different Windows 10 hacks, I finally have the VPN setup on Windows
10 almost as efficient as it was on Windows XP.
  #7  
Old May 31st 17, 02:43 AM posted to microsoft.public.windowsxp.general,alt.comp.os.windows-10
Roy Tremblay
external usenet poster
 
Posts: 169
Default How to get back Win10 lost functionality from WinXP when opening 16 files at once?

Here is a summary of what hacks are needed on Windows 10 to get the
efficient WinXP free public VPN use model to work on Win10 when you have
hundreds of sometimes unreliable freely available OpenVPN text files from
various public servers on the net.

HACK 1: Clicking on *.ovpn files opens them in the OpenVPN Daemon.
HACK 2: Turn off the nag screen that pops up every time an *ovpn is opened.
HACK 3: Set OpenVPN Daemon running-log files to open up in the same spot.
HACK 4: Add a 32-bit registry DWORD to open more than 15 files at a time.

1. Set the Windows 10 file association for *.ovpn
- Change from: *.ovpn starts with the OpenVPN GUI
- Change to: *.ovpn starts with the OpenVPN Daemon

2. Set the executable permissions for OpenVPN/bin/*.exe
- Right click on each of the *exe files in .\openvpn\bin\*.exe
- Set to: Run as administrator
- NOTE: You may only need to do this for one *exe in the bin directory
(but I wasn't sure which one because the OpenVPN Daemon (openvpn.exe)
also runs the OpenVPN Service (openvpnserv.exe) but there are other
executables in that bin directory (openssl.exe, openvpn-gui.exe,
& openvpnserv2.exe)

3. Set OpenVPN Daemon running logs to open up in the same spot!
- Doubleclick on an *.ovpn file to open up the OpenVPN Daemon log
- Right click in the top bar of that running log file
- Select "Properties" & go to the "Layout" tab
- Position the window as you want all of the windows to appear
- Uncheck the checkbox for "[ ]Let system position window"
- Press OK

4. Add a 32-bit DWORD to open more than 15 files at a time.
- HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer
- Name : MultipleInvokePromptMinimum
- Type : DWORD
- Default : 15 (decimal)
- Change to: 200 (decimal)

The use model is to simply select any number of freely available OpenVPN
*.ovpn text files downloaded off the net, right click on the selected set,
and hit "Open" from the pop-up menu, where only one will work. That puts
you on VPN. Any files that work after the first will just die, and any
files that fail will remain in a hung window. Close the hung windows by
clicking on the [x] box, all of which are lined up. (Don't close the one
window that is working, of course. Just move it to the side when you
encounter it in the stack.)
  #8  
Old May 31st 17, 08:42 AM posted to microsoft.public.windowsxp.general,alt.comp.os.windows-10
JJ[_11_]
external usenet poster
 
Posts: 744
Default How to get back Win10 lost functionality from WinXP when opening 16 files at once?

On Tue, 30 May 2017 18:39:10 -0400, Paul wrote:

And I don't pretend to understand why Microsoft did this.
It's pretty bizarre.

If I want to select 60,000 items and "do something" using
the Context Menu, why shouldn't I be allowed to do it ?

Maybe they could have put up a dialog with:

"Did you really mean to name_of_command on these 60,000 items ?"
Cancel or OK


Most likely reason is to prevent launching an application too many times at
once (assuming that the file association doesn't use DDE, and the
application allow itself to have multiple instances). It stresses and may
freeze the entire system temporarily, since it can deplete system resources
- making the system to become unstable and prone to crash. e.g. when there's
not enought system resources to display an error message, or even perform a
recovery procedure.
  #9  
Old June 1st 17, 02:22 AM posted to microsoft.public.windowsxp.general,alt.comp.os.windows-10
Roy Tremblay
external usenet poster
 
Posts: 169
Default How to get back Win10 lost functionality from WinXP when opening 16 files at once?

Roy Tremblay actually wrote:

The Microsoft KB KB2022295 instructions just said to create a DWORD.
They didn't say whether to create a 32-bit or 64-bit DWORD.
I can't reboot or kill explore.exe until the MSRT completes which has been
running for almost 24 hours so I would hate to kill it now.


Other than the question of whether to use a 32-bit DWORD or a 64-bit DWORD,
this problem is SOLVED!

I didn't even have to kill and restart explore.exe or reboot.

I selected fifty *.ovpn files, right clicked, and hit "Open".
Out of those fifty, only one worked so I killed the other 40 or so.
About 10 worked actually, but only the first one wins.
The other 9 of the 10 that worked just die.

So I think I have finally reproduced on Win10 the very efficient WinXP use
model which is really easy to run with hundreds of unreliable OpenVPN
files.
  #10  
Old June 15th 17, 02:50 PM posted to microsoft.public.windowsxp.general,alt.comp.os.windows-10
Char Jackson
external usenet poster
 
Posts: 10,449
Default How to get back Win10 lost functionality from WinXP when opening 16 files at once?

On Thu, 1 Jun 2017 01:22:25 +0000 (UTC), Roy Tremblay
wrote:

Other than the question of whether to use a 32-bit DWORD or a 64-bit DWORD,
this problem is SOLVED!

So I think I have finally reproduced on Win10 the very efficient WinXP use
model which is really easy to run with hundreds of unreliable OpenVPN
files.


What kind of performance do you see via your VPN tunnel?

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 04:37 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.