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. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
How to make a double-click only affect the clicked-on file ?
Hello All,
My old (bit still trusty) Win98se machine has got a quirk I am bothered with: sometimes (but always just after having switched from full-screen console to the GUI) when I, in the file exporer, double-click a file it behaves as if I have selected all files from start of the folder upto the clicked-on file, and tries to open or execute each-and-every-one of them. :-o :-( I have no idea why that it (selection of all those files) happens, but I think that a simple work-around could be to only have the (left) double-click affect the clicked-on file. My question: Is there a setting somewhere to make that happen ? If not, what other options do I have ? Regards, Rudy Wieser P.s. Sometimes, in the above described circumstances, my 'puter behaves (very noticable in console window) as if (I think) the ALT key has gotten stuck. Pressing that key always "un-sticks" it. And before you think "Its a keyboard problem!", the behaviour has persisted over at least 3 keyboards .... |
#2
|
|||
|
|||
How to make a double-click only affect the clicked-on file ?
On Thu, 30 Mar 2017 10:34:45 +0200, R.Wieser wrote:
Hello All, My old (bit still trusty) Win98se machine has got a quirk I am bothered with: sometimes (but always just after having switched from full-screen console to the GUI) when I, in the file exporer, double-click a file it behaves as if I have selected all files from start of the folder upto the clicked-on file, and tries to open or execute each-and-every-one of them. :-o :-( That's a keyboard problem. The SHIFT key button (either left or right) has become too sensitive due to its rubber or metal spring no longer able to push/pull the button connector back. By software, you can only work around it by disabling the problematic SHIFT key by remapping it to an unused virtual key code and/or scan code. To actually fix it assuming that it's still repairable, you'll have to take apart the keyboard and fix the mechanical issue. Too-sensitive or stuck keys are usually repairable and easier to fix than too-insensitive or dead keys. |
#3
|
|||
|
|||
How to make a double-click only affect the clicked-on file ?
JJ,
That's a keyboard problem. Yeah, that was my first thought too. But other than at the described moment I do not seem to experience that particular problem (like when using the ALT key in combination with the arrow keys to select text). So no, I don't think so. I wish it was a persistent problem though, as than simply replacing the keyboard would have provided the proof of that assumption ... Regards, Rudy Wieser -- Origional message: JJ schreef in berichtnieuws ... On Thu, 30 Mar 2017 10:34:45 +0200, R.Wieser wrote: Hello All, My old (bit still trusty) Win98se machine has got a quirk I am bothered with: sometimes (but always just after having switched from full-screen console to the GUI) when I, in the file exporer, double-click a file it behaves as if I have selected all files from start of the folder upto the clicked-on file, and tries to open or execute each-and-every-one of them. :-o :-( That's a keyboard problem. The SHIFT key button (either left or right) has become too sensitive due to its rubber or metal spring no longer able to push/pull the button connector back. By software, you can only work around it by disabling the problematic SHIFT key by remapping it to an unused virtual key code and/or scan code. To actually fix it assuming that it's still repairable, you'll have to take apart the keyboard and fix the mechanical issue. Too-sensitive or stuck keys are usually repairable and easier to fix than too-insensitive or dead keys. |
#4
|
|||
|
|||
How to make a double-click only affect the clicked-on file ?
In message , R.Wieser
writes: JJ, That's a keyboard problem. Yeah, that was my first thought too. But other than at the described moment I do not seem to experience that particular problem (like when using the ALT key in combination with the arrow keys to select text). So no, I don't think so. I wish it was a persistent problem though, as than simply replacing the keyboard would have provided the proof of that assumption ... [] Does it continue to the on-screen keyboard? I have a problem with this XP machine that seems dead certain to be a keyboard problem, but once it's been triggered, switching to the OSK doesn't cure it! -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf Science fiction is escape into reality - Arthur C Clarke |
#5
|
|||
|
|||
How to make a double-click only affect the clicked-on file ?
You provide your own work around, pressing the Alt key.
I found sendkeys via a vbs script to have many benefits with my 98 platform and it could be automatically sent by some clever piping means as well. My vote is on some dodgy BIOS code that may have been fixed in the last available BIOS version for your machine perhaps. Somehow they are not clearing the ALT pressed location in a timely manner and it's holding old data that says you are holding it down. You might try to uninstall the keyboard driver from the device mangler, and then rebooting, it's been known to work before in clearing up such mysteries. I can't say it's never happened to me because it seems it has. But it never took on a life of it's own and became a 'thing' here. Full screen console means a big DOS box? If so then it might be as simple as a better invocation string for the means whereby you get to full screen console mode. Or an alternate exit strategy that includes such a vbs send_keys script after or before it exits. But I have no useful suggestions from a certain lack of knowledge on the subject at large which would require a dip in that pool. And it's your problem. I usually don't use the big DOS box for anything. Been there once or twice but that's about it. |
#6
|
|||
|
|||
How to make a double-click only affect the clicked-on file ?
In message , Lee
writes: You provide your own work around, pressing the Alt key. I found sendkeys via a vbs script to have many benefits with my 98 platform and it could be automatically sent by some clever piping means as well. My vote is on some dodgy BIOS code that may have been fixed in the last available BIOS version for your machine perhaps. Somehow they are not clearing the ALT pressed location in a timely manner and it's holding old data that says you are holding it down. You might try to uninstall the keyboard driver from the device mangler, and then rebooting, it's been known to work before in clearing up such mysteries. I can't say it's never happened to me because it seems it has. But it never took on a life of it's own and became a 'thing' here. Full screen console means a big DOS box? Well, not so much a box, as truly full screen - as if you were in true DOS. (IIRR, Alt-Enter toggles.) Character mode (80 by 25 IIRR), no graphics. If so then it might be as simple as a better invocation string for the means whereby you get to full screen console mode. Or an alternate exit strategy that includes such a vbs send_keys script after or before it exits. But I have no useful suggestions from a certain lack of knowledge on the subject at large which would require a dip in that pool. And it's your problem. I usually don't use the big DOS box for anything. Been there once or twice but that's about it. -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf "When the people fear the government there is tyranny, when the government fears the people there is liberty." - Thomas Jefferson |
#7
|
|||
|
|||
How to make a double-click only affect the clicked-on file ?
J.P.
Does it continue to the on-screen keyboard? Win98se has one of those ? I was not aware of that ... Hmmm... Looking thru my start-menus folders does not turn up anything. A quick google doesn't give me a result either. Any idea where I can find it ? I have a problem with this XP machine that seems dead certain to be a keyboard problem, but once it's been triggered, switching to the OSK doesn't cure it! There is the slight possibility that a stuck shift/control/alt key might be firing a steady stream of key-down messages, interfeering with any other keyboard "attached" to the system. Next time you encounter that same problem see if unplugging the keyboard itself changes anything. .... and while I'm writing the above down it occurs to me that thats something I need to try too. :-) Regards, Rudy Wieser -- Origional message: J. P. Gilliver (John) schreef in berichtnieuws ... In message , R.Wieser writes: JJ, That's a keyboard problem. Yeah, that was my first thought too. But other than at the described moment I do not seem to experience that particular problem (like when using the ALT key in combination with the arrow keys to select text). So no, I don't think so. I wish it was a persistent problem though, as than simply replacing the keyboard would have provided the proof of that assumption ... [] Does it continue to the on-screen keyboard? I have a problem with this XP machine that seems dead certain to be a keyboard problem, but once it's been triggered, switching to the OSK doesn't cure it! -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf Science fiction is escape into reality - Arthur C Clarke |
#9
|
|||
|
|||
How to make a double-click only affect the clicked-on file ?
In message , R.Wieser
writes: J.P. Does it continue to the on-screen keyboard? Win98se has one of those ? I was not aware of that ... Ah. I'd forgotten - I'm on XP. It might: on XP, it's under Accessories | Accessibility, or Start | Run | [type] osk. Hmmm... Looking thru my start-menus folders does not turn up anything. A quick google doesn't give me a result either. Any idea where I can find it ? I have a problem with this XP machine that seems dead certain to be a keyboard problem, but once it's been triggered, switching to the OSK doesn't cure it! There is the slight possibility that a stuck shift/control/alt key might be firing a steady stream of key-down messages, interfeering with any other Yes, I had that thought too - but I have remembered that not only did I try an external USB keyboard, but also even bought a replacement internal one (it's a netbook). [Only partly to see if it cured this problem: it's also a white one, which is a lot easier to see than the black one that came with the (black) machine.] It didn't fix it. (My problem seems to be triggered by using the left Ctrl key, so I avoid touching it!) keyboard "attached" to the system. Next time you encounter that same problem see if unplugging the keyboard itself changes anything. ... and while I'm writing the above down it occurs to me that thats something I need to try too. :-) [] Do tell how you get on. -- J. P. Gilliver |
#10
|
|||
|
|||
How to make a double-click only affect the clicked-on file ?
On Friday, March 31, 2017 at 4:49:04 AM UTC-6, R.Wieser wrote:
Lee, You provide your own work around, pressing the Alt key. Yeah, but not a *good* work-around I'm afraid. I switch between the CLI and GUI to much to have to do it every time (for a problem that pops up sometimes). Understood there. I would call that a power user of the big DOS box although you've already indicated you would not call it that ever. Maximized window isn't what I was referring to either even though they may in fact be the same thing. We are on the same page, it just might not sound like it. Full screen console means a big DOS box? Nope, it means the CLI taking up the whole screen (like most games do), not maximized GUI window. Like when you get (on an W98 system) when pressing ALT-ENTER when in a windowed CLI. And here is our clue, your ALT press (in windows) from that is being maintained afterwards (via the keyboard buffer). And this begs the question just exactly how do you get to full screen console? I assume you start with the START menu's DOS PROMPT shortcut, but then do you manually press ALT + ENTER? You don't need to preload the windows keyboard buffer with this ALT button press which may be the root cause of the issue. Earlier you asked for where are the settings if there are any? Answer is under right click on the DOS PROMPT shortcut with several gotchas in there. One is close on exit checkbox tick, mine is ticked. Another is screen start settings in full size or standard normal window, play with this to get ALTless full screen CLI perhaps. Another is Windows shortcut key list allowed during CLI interface, all of mine are checked and I never mess with it so this is probably the original settings I'm looking at -- ALT + ENTER is in there, but I don't know if unchecking it is the thing to do or not. I doubt it but you never know. You may have to reboot for changes done in here to actually go into full effect too - if in doubt reboot as they say or should have. I usually don't use the big DOS box for anything. :-) Sometimes it feels to me I use it more than I use the GUI. Confirmed power user then. We are all addicted to the best Windows ever, just in a vast multitude of different ways. Hello, my name is Lee and I have an addiction. My vote is on some dodgy BIOS code that may have been fixed in the last available BIOS version for your machine perhaps. Are you sure ? Doesn't windows load its own low-level keyboard-driver (ignoring any-and-all BIOS routines for it) If I'm not mistaken NONE of the BIOS calls can be ignored in that manner, Basic In/Out System is what BIOS stands for and it's a 'get all your work done thru me' centralized standard from day one. Even protected mode windows calls are still done with interrupt calls thru the BIOS, just in a different section for protected mode. Keyboard use would just use a different set of interrupt calls from say the hard drive or screen. And it's quite likely that protected mode sections extend to the keyboard too. Ralf Brown's interrupt list is a mighty fine read for further details. But I've changed my mind as to BIOS update being a possible need in your case, pretty sure now it's just the settings/method you are using with a possible cure using an exit batch file perhaps. Other method may be to alter the string in the registry that fires up the CLI emulator, some batch files I use require certain switches for firing up the CLI part such that it will persist and work properly with some of the batch files I'm using, but the exact information to supply here is long forgotten since it's been so long since I built the batch files. /C or /K switches seem to be in the front of my mind but a run thru of the DOS help file might shed better light on the subject. I've even forgotten exactly where to look in the registry for this string anyway. For now you can mess with the shortcut properties which will probably be doing the exact same thing anyway. I use RegShot to confirm such suspicions often, but again been so long I would have to relearn my own methods for even using RegShot properly. One last rememberance of mine is that there several DOS mode PIF file shortcuts scattered throughout the system. You will have to work on the correct one, one operates the shutdown flash moment as windows dies IIRC. If you foul this one up you can get locked into CLI only and other problems as well. One is specifically for reboot to DOS mode choice and others I never did figure out. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Spybot opens when I double-click on a hosts file, how do I make itopen Notepad? | SlickRCBD[_2_] | General | 5 | July 21st 08 04:57 AM |
Programs won't run with double-click or from menus until batch file run | [email protected] | General | 5 | July 30th 05 05:24 AM |
double click to open file not working for Office | B.Long | Software & Applications | 0 | September 13th 04 01:35 PM |
Double click not working | Sue | General | 1 | July 20th 04 06:39 PM |
Problem with Mouse Click / Double-Click | Steve Clements | General | 11 | July 8th 04 03:35 AM |