info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
How to make a double-click only affect the clicked-on file ?
19 views
Skip to first unread message
R.Wieser
Mar 30, 2017, 4:34:33 AM3/30/17
to
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
...
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
...
JJ
Mar 30, 2017, 8:19:34 AM3/30/17
to
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
> 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 :-(
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.
R.Wieser
Mar 30, 2017, 8:57:16 AM3/30/17
to
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 <jj4p...@vfemail.net> schreef in berichtnieuws
16h74peu3mzds$.1a45r74mf1tqp$.dlg@40tude.net...
> That's a keyboard problem.
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 <jj4p...@vfemail.net> schreef in berichtnieuws
16h74peu3mzds$.1a45r74mf1tqp$.dlg@40tude.net...
Lee
Mar 31, 2017, 12:23:25 AM3/31/17
to
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.
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.
J. P. Gilliver (John)
Mar 31, 2017, 2:57:20 AM3/31/17
to
In message <58dd00aa$0$709$e4fe...@news.xs4all.nl>, R.Wieser
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
<add...@not.available> 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 ...
[]
>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
J. P. Gilliver (John)
Mar 31, 2017, 3:25:52 AM3/31/17
to
In message <13a5fec8-b144-4577...@googlegroups.com>, Lee
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.
when the government fears the people there is liberty." - Thomas Jefferson
<mel...@my-deja.com> 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
>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?
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,
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
when the government fears the people there is liberty." - Thomas Jefferson
R.Wieser
Mar 31, 2017, 6:49:04 AM3/31/17
to
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
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) <G6JP...@255soft.uk> schreef in berichtnieuws
JCPyywPc...@soft255.demon.co.uk...
> Does it continue to the on-screen keyboard?
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
> 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!
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:
JCPyywPc...@soft255.demon.co.uk...
R.Wieser
Mar 31, 2017, 6:49:04 AM3/31/17
to
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).
> 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.
> 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.
> 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)
> 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'll keep that in mind as a last-ditch possibility.
Regards,
Rudy Wieser
-- Origional message:
Lee <mel...@my-deja.com> schreef in berichtnieuws
13a5fec8-b144-4577...@googlegroups.com...
> You provide your own work around, pressing the Alt key.
and GUI to much to have to do it every time (for a problem that pops up
sometimes).
> Full screen console means a big DOS box?
maximized GUI window. Like when you get (on an W98 system) when pressing
ALT-ENTER when in a windowed CLI.
> I usually don't use the big DOS box for anything.
> My vote is on some dodgy BIOS code that may have been fixed in the
> last available BIOS version for your machine perhaps.
(ignoring any-and-all BIOS routines for it)
> 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.
Regards,
Rudy Wieser
-- Origional message:
13a5fec8-b144-4577...@googlegroups.com...
J. P. Gilliver (John)
Mar 31, 2017, 2:38:13 PM3/31/17
to
In message <58de341f$0$732$e4fe...@news.xs4all.nl>, R.Wieser
Accessibility, or Start | Run | [type] osk.
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
<add...@not.available> 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 |
>J.P.
>
>> Does it continue to the on-screen keyboard?
>
>Win98se has one of those ? I was not aware of that ...
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
>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
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
Lee
Mar 31, 2017, 7:27:13 PM3/31/17
to
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.
> 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).
>
> > 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.
>
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.
>
> > 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)
>
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.
R.Wieser
Apr 1, 2017, 4:22:50 AM4/1/17
to
Lee,
> I assume you start with the START menu's DOS PROMPT shortcut,
> but then do you manually press ALT + ENTER?
Something like the first (I did put a shortcut to it on the desktop), though
I also placed a link into the context-menu of a folder. But no, I do not
(need to) press ALT-ENTER, I changed the DOS Prompt settings to start in
full-screen mode. I seldom use ALT-ENTER. I however do use ALT-TAB to
switch between the (full-screen) DOS prompt and the GUI ...
> You don't need to preload the windows keyboard buffer with this
> ALT button press which may be the root cause of the issue.
I'm not sure what you mean here ... Preloading ? How ? I'm not aware of
that (and than, what about the TAB key I also need to press ?).
> Earlier you asked for where are the settings if there are any?
I was aiming for GUI settings (as there the problem is most pronounced), but
I'm open to any help I can get. :-)
> One is close on exit checkbox tick, mine is ticked.
Same here.
> Another is screen start settings in full size or standard normal
> window, play with this to get ALTless full screen CLI perhaps.
As you can tell from my above response, already done. :-)
> 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
The only ones I've got enabled are ALT-TAB and ALT-ENTER -- The fewer
"special key combinations" that will throw me back to the GUI environment
(and disrupt my work in the CLI), the better.
> 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
I'm not sure I'm really a power-user. Its just that some stuff just seems
to work easier in a CLI than in a GUI. *Especially* when you have some
"dump output" you want to view/capture into a file.
> If I'm not mistaken NONE of the BIOS calls can be ignored in that manner
I'm afraid you're mistaken. You just have to make sure that you do not
have both active at the same time, as that most likely will cause clashes.
:-)
For example: the BIOS provides an interface to the serial port (INT 0x14).
But nothing stops you if you want to access the UART hardware itself (I/O
ports 3F8h-3FFh for COM1).
> 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
Not quite. The B in BIOS stands for "Basic", as in Bog-standard, no extras.
What you are referring to is the OS'es gate-keeper to the hardware, which
makes sure only a single program can access a certain piece hardware at a
time (imagine two programs in a multi-tasking environment trying to use the
same hardware at the same time. Yup: C(l|r)ash! :-) )
And yes, Win98se wasn't fully grown-out in this regard (which is why you can
still access hardware directly in it, even as a mere user)
> pretty sure now it's just the settings/method you are using
I'm all ears ! ... but are you sure about that ? A sometimes(!)-sticky
key being caused by a setting ?
> with a possible cure using an exit batch file perhaps
Well, although I rather dislike having to shell a shell (with the second
shell doing all the work and the first shell just waiting to run some
"clean-up" code), it could not hurt to take a peek at it, even just as a
method to determine if such a sticky key is actually the cause. Thanks for
the suggestion.
Now I only need to come up with a method to, in a DOS environment, check the
keys current status ...
> One last rememberance of mine is that there several DOS mode PIF
> file shortcuts scattered throughout the system.
Yup. Never bothered to take a look at those either (other than to conclude
that they would not open a CLI window for my use). But don't worry: I've
got a single PIF, with the others being shortcuts to it (other than the
origional one in the start menu, which never use and I left untouched -- you
never know when I could need it :-) )
Thanks for the suggestions.
84143a3f-9652-4d8d...@googlegroups.com...
> I assume you start with the START menu's DOS PROMPT shortcut,
> but then do you manually press ALT + ENTER?
I also placed a link into the context-menu of a folder. But no, I do not
(need to) press ALT-ENTER, I changed the DOS Prompt settings to start in
full-screen mode. I seldom use ALT-ENTER. I however do use ALT-TAB to
switch between the (full-screen) DOS prompt and the GUI ...
> You don't need to preload the windows keyboard buffer with this
> ALT button press which may be the root cause of the issue.
that (and than, what about the TAB key I also need to press ?).
> Earlier you asked for where are the settings if there are any?
I'm open to any help I can get. :-)
> 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
"special key combinations" that will throw me back to the GUI environment
(and disrupt my work in the CLI), the better.
> 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
to work easier in a CLI than in a GUI. *Especially* when you have some
"dump output" you want to view/capture into a file.
> If I'm not mistaken NONE of the BIOS calls can be ignored in that manner
have both active at the same time, as that most likely will cause clashes.
:-)
For example: the BIOS provides an interface to the serial port (INT 0x14).
But nothing stops you if you want to access the UART hardware itself (I/O
ports 3F8h-3FFh for COM1).
> 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
What you are referring to is the OS'es gate-keeper to the hardware, which
makes sure only a single program can access a certain piece hardware at a
time (imagine two programs in a multi-tasking environment trying to use the
same hardware at the same time. Yup: C(l|r)ash! :-) )
And yes, Win98se wasn't fully grown-out in this regard (which is why you can
still access hardware directly in it, even as a mere user)
> pretty sure now it's just the settings/method you are using
key being caused by a setting ?
> with a possible cure using an exit batch file perhaps
shell doing all the work and the first shell just waiting to run some
"clean-up" code), it could not hurt to take a peek at it, even just as a
method to determine if such a sticky key is actually the cause. Thanks for
the suggestion.
Now I only need to come up with a method to, in a DOS environment, check the
keys current status ...
> One last rememberance of mine is that there several DOS mode PIF
> file shortcuts scattered throughout the system.
that they would not open a CLI window for my use). But don't worry: I've
got a single PIF, with the others being shortcuts to it (other than the
origional one in the start menu, which never use and I left untouched -- you
never know when I could need it :-) )
Thanks for the suggestions.
84143a3f-9652-4d8d...@googlegroups.com...
Lee
Apr 5, 2017, 2:14:40 AM4/5/17
to
Sorry, got busy.
On Saturday, April 1, 2017 at 2:22:50 AM UTC-6, R.Wieser wrote:
> I seldom use ALT-ENTER. I however do use ALT-TAB to
> switch between the (full-screen) DOS prompt and the GUI ...
This reveal blows apart some prior advice. I was not aware you were doing windows WITH a full screen console minimized and pressing ALT key in combination with TAB now too...
Keyboard buffers exist on many platforms, you perhaps didn't spend any time on an Atari 8 bit or others of that ilk where each system's keyboard had the buffer set up and used in a vast array of foibles. Often when the OS has been loaded with custom software that uses a different technique than the maker to capture key presses, the keyboard buffer can be filled with presses not intended to be sent when the software has finished and run it's course. And at that point here come the last 5 keys or none of them or just one depending on make and model. Windows OS uses a keyboard buffer too, different from DOS most likely and to get into full screen mode with the 'set for it' full screen setting it is pressing it's own ALT-ENTER combo for you. Windows remembers this key press because it's in the buffer. Perhaps, perhaps not if they foresaw this issue and piddled with the buffer such that it doesn't show there at all. How can I know now what they did, how they did it so many years ago? Perhaps the ALT key is being stored after you press TAB and I can't know this either.
Upon exit then, DOS mode should clear that keypress for you, but only that one and most likely only if it's really there and again only if it's stacked correctly and not out of phase with any other buffered key press. Your trips into the GUI via ALT-TAB are blowing the order of the buffer stack such that it can't possibly wind up right. We can't even be sure of which one is blown.
> > You don't need to preload the windows keyboard buffer with this
> > ALT button press which may be the root cause of the issue.
>
> I'm not sure what you mean here ... Preloading ? How ? I'm not aware of
> that (and than, what about the TAB key I also need to press ?).
>
Excellent example of phase issues, I'm talking about one method and you are talking about a different method only revealed to me after my 2nd round of suggestions has confused you because you didn't let me know your methods in detail. So my advice can't possibly be correct and in order to follow, you have to go back and see where I'm speaking to an issue that isn't yours. Do that to the windows keyboard buffer and you have your problem complete with intermittent aspect too.
I suffer issues with windows only use of ALT-TAB as is, it's kind of a crap shoot and I only win sometimes. Combine that with firefox's inane approach to 'TAB winders is way more better than a new winder' where they confuse the order of open windows purposely to 'encourage' the use of their built in TABs insanity and I want to shoot somebody sometimes.
> > Earlier you asked for where are the settings if there are any?
>
> I was aiming for GUI settings (as there the problem is most pronounced), but
> I'm open to any help I can get. :-)
>
The issue appears to be two fold at the very least. You want ALTless function in windows with AND without the full screen console minimized. I suspect one simple solution doesn't exist for both uses. I was suggesting a one shot only method and just like fighting indians you can't use your last bullet on anybody else except yourself. That idea then can't possibly work out well.
>
> I'm not sure I'm really a power-user. Its just that some stuff just seems
> to work easier in a CLI than in a GUI. *Especially* when you have some
> "dump output" you want to view/capture into a file.
>
In my vernacular you are, it doesn't mean a buddha like knowledge of all things comparable to and 2nd only to God himself, it just means you do that often. End of definition.
> > If I'm not mistaken NONE of the BIOS calls can be ignored in that manner
>
> I'm afraid you're mistaken. You just have to make sure that you do not
> have both active at the same time, as that most likely will cause clashes.
> :-)
Sorry, then by definition it's not a legal BIOS call and no software you are likely to be using does illegal direct access as examples given. You can't sell hacks commercially, virus software is looking for these hacks. And principally to the point -- HACKS don't count by definition. DOS is using only proper and legal BIOS calls, until you load DeBug and use it to hack your way around for example. Windows also follows the rules. And those are the rules.
The BIOS is not capable of multitasking anything.
>
> > pretty sure now it's just the settings/method you are using
>
> I'm all ears ! ... but are you sure about that ? A sometimes(!)-sticky
> key being caused by a setting ?
>
Do you ever recall such a sticky key checkbox? I don't.
>
> Now I only need to come up with a method to, in a DOS environment, check the
> keys current status ...
>
Good luck finding both DOS keyboard buffer and windows buffer, really seems to be the only way that could work is to clear pending and present key presses on both. DOS for sure had it's keyboard buffer far in advance of the existence of windows and the 32 bit protected mode crowd when they showed up to play would insist on their own keyboard buffer, thus my belief that there will be two buffers to deal with.
>
> Thanks for the suggestions.
>
> Regards,
> Rudy Wieser
Certainly. If you find a solution please get back with it as it's going to be more than I know about now. Last thought is perhaps an ALT press monitor? Something that would alter it's icon color to indicate ALT has been pressed and/or is a pending key press? Vb script can be running in the background doing this one and only job - perhaps, I'm not entirely fluent in that to say for sure. ALT-TAB would be different than just ALT as a reminder. And this is a rather poor workaround as it still leaves you pressing ALT anyway which was the workaround you don't want.
Of course I can't find my own send_keys examples as they are on another computer not accessible at the moment. Main help came from the help file from vbs 5.6 itself.
Not a whole lot out there still intact, but I did find these two still working.
http://www.billsway.com/vbspage/
http://computerperformance.co.uk/
On Saturday, April 1, 2017 at 2:22:50 AM UTC-6, R.Wieser wrote:
> I seldom use ALT-ENTER. I however do use ALT-TAB to
> switch between the (full-screen) DOS prompt and the GUI ...
Keyboard buffers exist on many platforms, you perhaps didn't spend any time on an Atari 8 bit or others of that ilk where each system's keyboard had the buffer set up and used in a vast array of foibles. Often when the OS has been loaded with custom software that uses a different technique than the maker to capture key presses, the keyboard buffer can be filled with presses not intended to be sent when the software has finished and run it's course. And at that point here come the last 5 keys or none of them or just one depending on make and model. Windows OS uses a keyboard buffer too, different from DOS most likely and to get into full screen mode with the 'set for it' full screen setting it is pressing it's own ALT-ENTER combo for you. Windows remembers this key press because it's in the buffer. Perhaps, perhaps not if they foresaw this issue and piddled with the buffer such that it doesn't show there at all. How can I know now what they did, how they did it so many years ago? Perhaps the ALT key is being stored after you press TAB and I can't know this either.
Upon exit then, DOS mode should clear that keypress for you, but only that one and most likely only if it's really there and again only if it's stacked correctly and not out of phase with any other buffered key press. Your trips into the GUI via ALT-TAB are blowing the order of the buffer stack such that it can't possibly wind up right. We can't even be sure of which one is blown.
> > You don't need to preload the windows keyboard buffer with this
> > ALT button press which may be the root cause of the issue.
>
> I'm not sure what you mean here ... Preloading ? How ? I'm not aware of
> that (and than, what about the TAB key I also need to press ?).
>
I suffer issues with windows only use of ALT-TAB as is, it's kind of a crap shoot and I only win sometimes. Combine that with firefox's inane approach to 'TAB winders is way more better than a new winder' where they confuse the order of open windows purposely to 'encourage' the use of their built in TABs insanity and I want to shoot somebody sometimes.
> > Earlier you asked for where are the settings if there are any?
>
> I was aiming for GUI settings (as there the problem is most pronounced), but
> I'm open to any help I can get. :-)
>
>
> I'm not sure I'm really a power-user. Its just that some stuff just seems
> to work easier in a CLI than in a GUI. *Especially* when you have some
> "dump output" you want to view/capture into a file.
>
> > If I'm not mistaken NONE of the BIOS calls can be ignored in that manner
>
> I'm afraid you're mistaken. You just have to make sure that you do not
> have both active at the same time, as that most likely will cause clashes.
> :-)
The BIOS is not capable of multitasking anything.
>
> > pretty sure now it's just the settings/method you are using
>
> I'm all ears ! ... but are you sure about that ? A sometimes(!)-sticky
> key being caused by a setting ?
>
>
> Now I only need to come up with a method to, in a DOS environment, check the
> keys current status ...
>
>
> Thanks for the suggestions.
>
> Regards,
> Rudy Wieser
Of course I can't find my own send_keys examples as they are on another computer not accessible at the moment. Main help came from the help file from vbs 5.6 itself.
Not a whole lot out there still intact, but I did find these two still working.
http://www.billsway.com/vbspage/
http://computerperformance.co.uk/
R.Wieser
Apr 5, 2017, 3:06:38 AM4/5/17
to
Lee,
> I was not aware you were doing windows WITH a full screen console
> minimized and pressing ALT key in combination with TAB now too...
I mentioned in my initial post that I "switched from full-screen console to
the GUI" I'm not aware of another method of doing that than by using a
keyboard-shortcut, so I didn't spell the ALT-TAB method out. But maybe I
should have, just to be on the safe side.
> How can I know now what they did, how they did it so many years
> ago? Perhaps the ALT key is being stored after you press TAB and I
> can't know this either.
I do not know either, and was not out to getting an explanation for it
either (though I have absolute zero problems with getting to know why it
happens mind you. :-) ), I just tried to minimize the problem itself -- by
limiting how many items a double-click affects.
> The issue appears to be two fold at the very least. You want ALTless
> function in windows with
Nope, not at all. I'm not out for a "than just don't do that" solution.
Also, clicking the console windows button on the taskbar will also bring it
up in its previous, in my case, full-screen state.
> AND without the full screen console minimized.
As I mentioned in the above, how else do you leave a full-screen console
window (and no, ALT-ENTER (to window the console) and than mousing to the
desired dialog does not count. :-) )
But you're focussing on something I did not ask for.
What I *really* want to know (at least as a first thing) is if there is a
setting/method to limit the reach of a double-click. If that is available I
could not care less about the ALT (or any other) key appearing to be sticky.
Yes, a sticky ALT or CTRL key (c|w)ould than still bring up dialogs, but
none as potentionally dangerous as starting a slew of programs, scripts and
batch files I have in a particular folder.
000ee9fa-19ed-44cf...@googlegroups.com...
> I was not aware you were doing windows WITH a full screen console
> minimized and pressing ALT key in combination with TAB now too...
the GUI" I'm not aware of another method of doing that than by using a
keyboard-shortcut, so I didn't spell the ALT-TAB method out. But maybe I
should have, just to be on the safe side.
> How can I know now what they did, how they did it so many years
> ago? Perhaps the ALT key is being stored after you press TAB and I
> can't know this either.
either (though I have absolute zero problems with getting to know why it
happens mind you. :-) ), I just tried to minimize the problem itself -- by
limiting how many items a double-click affects.
> The issue appears to be two fold at the very least. You want ALTless
> function in windows with
Also, clicking the console windows button on the taskbar will also bring it
up in its previous, in my case, full-screen state.
> AND without the full screen console minimized.
window (and no, ALT-ENTER (to window the console) and than mousing to the
desired dialog does not count. :-) )
But you're focussing on something I did not ask for.
What I *really* want to know (at least as a first thing) is if there is a
setting/method to limit the reach of a double-click. If that is available I
could not care less about the ALT (or any other) key appearing to be sticky.
Yes, a sticky ALT or CTRL key (c|w)ould than still bring up dialogs, but
none as potentionally dangerous as starting a slew of programs, scripts and
batch files I have in a particular folder.
000ee9fa-19ed-44cf...@googlegroups.com...
Lee
Apr 5, 2017, 11:05:50 PM4/5/17
to
On Wednesday, April 5, 2017 at 1:06:38 AM UTC-6, R.Wieser wrote:
> Lee,
>
> Lee,
>
> But you're focussing on something I did not ask for.
>
It does appear so, I'll admit to more than some confusion about the issue.
>
> What I *really* want to know (at least as a first thing) is if there is a
> setting/method to limit the reach of a double-click. If that is available I
> could not care less about the ALT (or any other) key appearing to be sticky.
The 'reach' of that type of selection of files and invoking same is unlimited to my knowledge at least when it comes to copy/cut for pasting, unless I again am not on the subject at hand? I have only tried a large selection in XP though.
Playing around here with XP and I can not run more than a fraction of a screen's worth without a warning popping up asking if I really want to run all those files? But XP is not 98 and 98 may not have such oversight. And if it did, I wouldn't know where to find it. And I'm not really sure I am talking about the same thing you are. Yet.
>
> Yes, a sticky ALT or CTRL key (c|w)ould than still bring up dialogs, but
> none as potentionally dangerous as starting a slew of programs, scripts and
> batch files I have in a particular folder.
>
> Regards,
> Rudy Wieser
>
There are just too many key presses needed to do what is going on. One can select and highlight a file starting with g just by pressing the g key, but it usually scrolls into view, then by other valid keyboard shortcuts it just might be possible to fire up the lot of them. And I'm thinking now you possibly have some keyboard program or setting that is supplying these key presses? I've never done such work but I do recall reading about various keyboard set up strings that one can use to effect a change in the normal way the system uses the keyboard. You use a PS2 keyboard I assume?
Back from a cursory look about for something along the lines I was thinking and got sidetracked by a bunch of stuff such as this
http://www.bttr-software.de/freesoft/keyb.htm
ScanCode Show - of note, I believe you mentioned needing this
Quickey - flushing of keyboard buffer is available here (possibly)
StuffIt - might be useful for sending that ALT press you don't want to
You may have sticky keys turned on. And other Accessibility Options at work. Found under Help in windows it will show how to turn them off at least. Search emacs for some extra confusion, perhaps one of your text editors does emacs mode or some other program you use? It may come down to a faulty keyboard? I had misery for better than a year due to broken wires in my mouse cord, had it not been just happenstance that out of frustration I wrap the cord around and held it under my thumb and like magic the symptoms just disappeared, I would still be fighting that battle. My own keyboard flashes the LEDs above the numeric keypad when I pick it up - I suspect some wires here too. But no problems I can complain about yet.
R.Wieser
Apr 6, 2017, 3:54:18 AM4/6/17
to
Lee,
> In order for an otherwise innocent double click to invoke several files
> at once one normally has to have been in that folder before and single
> clicked on an object which highlights it.
There you mention something. Only now I realize that if the selection would
be done from the first item I should have been seeing a lot of open
folders -- which I don't. I have to check that next time it happens.
But yes, the folder I'm double-clicking an item in was already open before I
switched to-and-back-from the console window.
> then one needs to double click another item with the Shift key held down.
Indeed.
> The 'reach' of that type of selection of files and invoking same is
unlimited
> to my knowledge at least when it comes to copy/cut for pasting, unless I
> again am not on the subject at hand?
As far as I know you're right. Hence my question to apply a limiter. :-)
> But XP is not 98 and 98 may not have such oversight. And if it did, I
> wouldn't know where to find it.
What is it known as under XP / where is it located ? knowing how its named
could be a starting point for a round of googeling ...
> And I'm not really sure I am talking about the same thing you are. Yet.
I get the feeling we now are. By the way, thank you for *not* biting my
head of when I mentioned we weren't (I've got experiences otherwise ...
:-\ ).
> Yes, don't want that ever. I'll rename my more malignant batch files to
> txt files just for that reason.
:-) Most the scripts, executables and batch-files are *very* wanted ...
when used at the right time and correct arguments. Luckily I like to write
my stuff "idiot-proof", meaning that I most always make sanity-checks on the
provided arguments. But that doesn't make the risk any/much less, as some
of my scripts are *ment* to be executing on a mere double-click.
> There are just too many key presses needed to do what is going on.
Jup. And when using the keyboard the selecting is seperate(d) from
activating the selection.
> One can select and highlight a file starting with g just by pressing the g
key
I did not know about that, I just tried it. It did not appear to do
anything for me (on my Win98se 'puter).
> And I'm thinking now you possibly have some keyboard program or
> setting that is supplying these key presses?
Nope (you veered of the right pad again, my young padawan :-D ).
What happens is that, as I described earlier,when I double-click an item my
'puter responds as if I also have the SHIFT key down. Very simple, nothing
complex.
If I would need to put my suspicions into words than I would describe it as
if the keyboard-driver didn't detect (or ignored!) the keyboards "SHIFT-key
UP" message, and reports to the rest of the OS that its still down.
> You use a PS2 keyboard I assume?
Yep. One of the last ones in existence it seems. :-)
Thanks for the links. There is a problem with them though: I would need to
be able to have them do whatever they do *just after* I switch from te CLI
to the GUI (or the other way around), with no further actions needed on my
side (which either would make it cumbersome, or interfere with being able to
detect the problem). It looks like they are not upto such a job ...
> You may have sticky keys turned on.
Nope (IIRC I even disabled its interference). And its effect would be
rather permanent, and therefore easily detectable ...
> It may come down to a faulty keyboard?
Yes, I also thought of that. But in that case the problem would also stick
up its ugly head at other moments than after just having switched from the
CLI to the GUI, which does not seem to happen.
> I had misery for better than a year due to broken wires in my mouse cord
As the break is more-often-than-not in the first centimeter sticking outof
the mouse, I've been known to repair them by shortening the cord and
re-attach the wires (I've even replaced the switches of malfunctioning
buttons a number of times).
By the way: yesterday it happened again. This time I did not touch my
keyboard, but physically dis- and reconnected it again. The sticky key was
no more.
In other words: it does not seem to be a physical problem (might still be in
the keyboards electronics, but as the moment of appearing seems to be bound
to what I do in the OS I doubt that).
d54f430a-ebe8-448e...@googlegroups.com...
> In order for an otherwise innocent double click to invoke several files
> at once one normally has to have been in that folder before and single
> clicked on an object which highlights it.
be done from the first item I should have been seeing a lot of open
folders -- which I don't. I have to check that next time it happens.
But yes, the folder I'm double-clicking an item in was already open before I
switched to-and-back-from the console window.
> then one needs to double click another item with the Shift key held down.
> The 'reach' of that type of selection of files and invoking same is
unlimited
> to my knowledge at least when it comes to copy/cut for pasting, unless I
> again am not on the subject at hand?
> But XP is not 98 and 98 may not have such oversight. And if it did, I
> wouldn't know where to find it.
could be a starting point for a round of googeling ...
> And I'm not really sure I am talking about the same thing you are. Yet.
head of when I mentioned we weren't (I've got experiences otherwise ...
:-\ ).
> Yes, don't want that ever. I'll rename my more malignant batch files to
> txt files just for that reason.
when used at the right time and correct arguments. Luckily I like to write
my stuff "idiot-proof", meaning that I most always make sanity-checks on the
provided arguments. But that doesn't make the risk any/much less, as some
of my scripts are *ment* to be executing on a mere double-click.
> There are just too many key presses needed to do what is going on.
activating the selection.
> One can select and highlight a file starting with g just by pressing the g
key
anything for me (on my Win98se 'puter).
> And I'm thinking now you possibly have some keyboard program or
> setting that is supplying these key presses?
What happens is that, as I described earlier,when I double-click an item my
'puter responds as if I also have the SHIFT key down. Very simple, nothing
complex.
If I would need to put my suspicions into words than I would describe it as
if the keyboard-driver didn't detect (or ignored!) the keyboards "SHIFT-key
UP" message, and reports to the rest of the OS that its still down.
> You use a PS2 keyboard I assume?
Thanks for the links. There is a problem with them though: I would need to
be able to have them do whatever they do *just after* I switch from te CLI
to the GUI (or the other way around), with no further actions needed on my
side (which either would make it cumbersome, or interfere with being able to
detect the problem). It looks like they are not upto such a job ...
> You may have sticky keys turned on.
rather permanent, and therefore easily detectable ...
> It may come down to a faulty keyboard?
up its ugly head at other moments than after just having switched from the
CLI to the GUI, which does not seem to happen.
> I had misery for better than a year due to broken wires in my mouse cord
the mouse, I've been known to repair them by shortening the cord and
re-attach the wires (I've even replaced the switches of malfunctioning
buttons a number of times).
By the way: yesterday it happened again. This time I did not touch my
keyboard, but physically dis- and reconnected it again. The sticky key was
no more.
In other words: it does not seem to be a physical problem (might still be in
the keyboards electronics, but as the moment of appearing seems to be bound
to what I do in the OS I doubt that).
d54f430a-ebe8-448e...@googlegroups.com...
Lee
Apr 7, 2017, 7:26:30 AM4/7/17
to
On Thursday, April 6, 2017 at 1:54:18 AM UTC-6, R.Wieser wrote:
> Lee,
>
> Lee,
>
> > But XP is not 98 and 98 may not have such oversight. And if it did, I
> > wouldn't know where to find it.
>
> What is it known as under XP / where is it located ? knowing how its named
> could be a starting point for a round of googeling ...
>
Yeah... nameless widget as far as I know, these aspects would be a part of some nondescript dll support file running as a dependency to windows explorer. Which makes it pretty much unchangeable by the common man like me. But one might find a function call for it just the same, trouble would be guessing the correct name as you've already noted is the real task at hand.
> > wouldn't know where to find it.
>
> What is it known as under XP / where is it located ? knowing how its named
> could be a starting point for a round of googeling ...
>
On second thought there is fail mode in 98 related, maybe. I'll select 14 pictures highlighted and 'send to' MS PhotoEditor and each opens it's own window under MS PhotoEditor. But trying to send 30 or more goes sideways with an error report window that I have to click OK to close if I want to continue. Not the same thing and still not accessible to us for tweaking, but it is there by some unknown mechanism.
> I get the feeling we now are. By the way, thank you for *not* biting my
> head of when I mentioned we weren't (I've got experiences otherwise ...
> :-\ ).
>
> > One can select and highlight a file starting with g just by pressing the g
> key
>
> I did not know about that, I just tried it. It did not appear to do
> anything for me (on my Win98se 'puter).
>
>
> Thanks for the links. There is a problem with them though: I would need to
> be able to have them do whatever they do *just after* I switch from te CLI
> to the GUI (or the other way around), with no further actions needed on my
> side (which either would make it cumbersome, or interfere with being able to
> detect the problem). It looks like they are not upto such a job ...
>
> > It may come down to a faulty keyboard?
>
> Yes, I also thought of that. But in that case the problem would also stick
> up its ugly head at other moments than after just having switched from the
> CLI to the GUI, which does not seem to happen.
>
>
> By the way: yesterday it happened again. This time I did not touch my
> keyboard, but physically dis- and reconnected it again. The sticky key was
> no more.
Maybe it's the mouse one is not supposed to hot plug in or out like that, but I was thinking you are not supposed to do that with a keyboard either? In any case we appreciate your hardware sacrifice highly, a hack is a hack and who cares as long as it works with no casualties?
OR -- maybe this is what happens when one does that? I wouldn't know, whenever 98 tells me it detected no mouse and/or keyboard connected for that matter I will just pull the plug on it and fix that issue first. And suffer the safe mode reboot foolishness gladly. Please review no-no list, I'm thinking that one is on there somewhere.
>
> In other words: it does not seem to be a physical problem (might still be in
> the keyboards electronics, but as the moment of appearing seems to be bound
> to what I do in the OS I doubt that).
>
> Regards,
> Rudy Wieser
>
While I was fooling around in the 98 portion of this computer I came across some VBS script examples I can post for the send keys method mentioned before. I forgot I had done this untold ages ago, I'm getting old age pension BTW, so no youngster here - who thought the republicans in colorado no less would give me money for doing nothing?
ReStart.vbs follows
---------------------------
With WScript.CreateObject("WScript.Shell")
.SendKeys "^{ESC}"
WScript.Sleep 500
.SendKeys "{u}"
WScript.Sleep 500
.SendKeys "{r}"
WScript.Sleep 1000
.SendKeys "~"
End With
first opens the windows key (which may be the combo of ^ and ESC), second is the keyboard shortcut letter for shutdown box - u, third is keyboard shortcut letter for restart -r, final is enter for OK box, IIRC. Sleep lines are required because vbs script is far too fast for the sent keys to be recognized and kept separate from each other, won't work without the sleepy time in between. I believe 1000 value equates to one second, 500 then being 1/2 second.
Click on the desktop shortcut to that file which is in the Windows folder and like magic up comes the shutdown box and the restart selection is made for you and it shuts down, only to restart again. Unlike the other many desktop shortcut ways of doing the same thing, this method rewrites your ShellIconCache file with new additions and allows it to grow up to 5 megs I believe is the largest one I've seen in my other full time 98se box.
Shutdown.vbs follows
----------------------
With WScript.CreateObject("WScript.Shell")
.SendKeys "^{ESC}"
WScript.Sleep 500
.SendKeys "{u}"
WScript.Sleep 500
.SendKeys "{s}"
WScript.Sleep 1000
.SendKeys "~"
WScript.Sleep 500
.SendKeys "n"
End With
Not sure why the extra 'n' is sent afterwards but I needed it or it wouldn't be in there. Perhaps a no answer to some prompt that was causing troubles for me at one point?
So if vbs can detect the moment the full screen CLI is minimized then it can send an ALT key press or flush buffer operation (better option if available?) and the issue is no more. The vbs script would be placed in the start up folder and run invisibly always behind everything looking for only the full screen CLI being minimized, only then fire off the ALT press (or?) with a sleep before hand just to be sure it isn't ignored and just keeps on running waiting for the next time it can help. You can fight indians with this one, unlimited bullet supply, just keep your head down.
You will have to have Scripting Host installed, it usually is by default but the default version may be somewhat lacking. 5.6 was the highest version 98 had much luck with. All the old places that had these goodies are gone for good I fear, even XP updates have been round filed by MS servers. WayBack machine may be the only hope for us, but personally I've not had much luck figuring that one out. Do look for the 5.6 scripting documentation help file - it's filled with quite good information such as a FULL rundown of every possible keypress for use with send keys method for example.
http://download.microsoft.com/download/winscript56/Install/5.6/W982KMeXP/EN-US/scrdoc56en.exe
amazing it's still good possibly because 2K still uses it.
and found that here
http://www.robvanderwoude.com/wshstart.php
R.Wieser
Apr 7, 2017, 8:00:41 AM4/7/17
to
Lee,
> So how did you know it happened before you got bit in the
> backside by it?
I was, in file explorer, trying to find a document by typing its name.
Suddenly it started to "act wierd", responding to the keystrokes by dropping
menus from the toolbar.
> Maybe it's the mouse one is not supposed to hot plug in or
> out like that,
Although I seldom do, I've never had problems with it.
> While I was fooling around in the 98 portion of this computer I came
> across some VBS script examples I can post for the send keys method
> mentioned before.
Thanks. Although it doesn't solve the problem itself (and I need to be
lucky to become aware of the problem before it barfs all over my desktop),
it mightbe helpfull in making sure thats its not a physically stickey key --
If its a keyboard-handling driver-code problem (as I'm suspecting) than
sending a single "key up" messsage (for each of the offending keyss should
release them.
> So if vbs can detect the moment the full screen CLI is minimized then it
> can send an ALT key press or flush buffer operation (better option if
> available?) and the issue is no more.
I was also thinking along the same lines (great minds yadyadayda :-) ), but
as I was busy with figuring out something else I did not yet spend any time
on it.
> You will have to have Scripting Host installed,
It is. Can't even remember when it wasn't ... And thanks for the links.
Regards
a8d2336a-6a08-490f...@googlegroups.com...
> So how did you know it happened before you got bit in the
> backside by it?
Suddenly it started to "act wierd", responding to the keystrokes by dropping
menus from the toolbar.
> Maybe it's the mouse one is not supposed to hot plug in or
> out like that,
> While I was fooling around in the 98 portion of this computer I came
> across some VBS script examples I can post for the send keys method
> mentioned before.
lucky to become aware of the problem before it barfs all over my desktop),
it mightbe helpfull in making sure thats its not a physically stickey key --
If its a keyboard-handling driver-code problem (as I'm suspecting) than
sending a single "key up" messsage (for each of the offending keyss should
release them.
> So if vbs can detect the moment the full screen CLI is minimized then it
> can send an ALT key press or flush buffer operation (better option if
> available?) and the issue is no more.
as I was busy with figuring out something else I did not yet spend any time
on it.
> You will have to have Scripting Host installed,
Regards
a8d2336a-6a08-490f...@googlegroups.com...
Lee
Apr 8, 2017, 2:24:12 AM4/8/17
to
On Friday, April 7, 2017 at 6:00:41 AM UTC-6, R.Wieser wrote:
> Lee,
>
>
> Lee,
>
>
> I was, in file explorer, trying to find a document by typing its name.
> Suddenly it started to "act wierd", responding to the keystrokes by dropping
> menus from the toolbar.
>
Darn it, it doesn't sound like we can use that then. At least I've not a solid clue how. Yet.
> Suddenly it started to "act wierd", responding to the keystrokes by dropping
> menus from the toolbar.
>
So the search tool was open and you were typing in the file name when it started misbehaving?
>
> Thanks. Although it doesn't solve the problem itself (and I need to be
> lucky to become aware of the problem before it barfs all over my desktop),
> it mightbe helpfull in making sure thats its not a physically stickey key --
> If its a keyboard-handling driver-code problem (as I'm suspecting) than
> sending a single "key up" messsage (for each of the offending keyss should
> release them.
>
If only the system worked that way with key up reading.
So in my knowledge of the buffers known, NONE monitor for the key up situation, they only respond to key down. But they have vast array of methods for insuring that it's not an old key press or a glitch lasting too short of a time period to be physically possible to be an actual user pressing down on a key. Then a timer is also involved for the use of held down keys. But there is usually a memory location that is holding the current key press which gets sent to the buffer if other processes are in use that prevent the 'acceptance' of keys in real time and they are sent to the buffer and they are then served back to the system Last In, First Out order and the buffer count for total keys decremented for each key sent. These insights aren't much help, we would need to know where to do the hacking and I sure don't.
Perhaps someone has such a thing along the lines of a keyboard initializer, set it to go off when the focus changes every single time might possibly work. Just search name suggestions to maybe find a tool that will patch over this glitch.
So a pair sent such as windows key and then ESC separately should cause the system to exit from the mode in question, perhaps. If you are lucky enough to have it happen again try to determine the best key(s) sent to snap it out of this mode. Not sure what to even call this mode.
Sounds like in this particular mode, it's reading the keyboard directly then and talk of buffers is a lot of hot air then.
When I was in the mouse troubles mode I got in the habit of uninstalling the devices related via keyboard shortcuts and ALT was an essential key in those methods. XP has a rather handy 'scan for hardware changes' which would detect the removed devices and reinstall them without rebooting. And this did give vast amounts of relief although now I can't imagine how.
To get into keyboard input mood (pun on mode), the magic combo is CTRL-TAB, and I recall reading something about some settings that allows one to switch ALT-TAB for CTRL-TAB or both/either. Something along those lines but I wasn't looking for that then so I didn't really pay much attention, just the concept that these combos can be flipped by a setting. And others complaining of trying to use one and the other happens. It may yet be a setting. And perhaps one of the DOS mode shortcut properties where your options were cut back to only two legal combos IIRC - these settings may be a player in the issue. One can also swap mouse buttons around so it seems like this might have been a read on the accessibility options and there are several.
So after CTRL-TAB sets the mood, then Windows Key will kill it and then ESC to get away from the Start menu pop up. But then the focus is lost, it is what it is, at least something works for some kind of control.
To sum up those ramblings, it appears to be a random firing off of CTRL-TAB. ALT after that goes straight to the tool bar then. Does that sound feasible to you?
Fixing cars because I can and there seems to be a need for that, I often find others having the exact same problem with theirs that I have just run head first into. A forum search on that make, model and even year will often be my first move and it's saved me entire days of misery. I suggest you try to find a forum for your make and model of confuser and see if anyone in there also has your problem, rarely they actually come back with a solution too.
>
> > You will have to have Scripting Host installed,
>
> It is. Can't even remember when it wasn't ... And thanks for the links.
>
> Regards
> Rudy Wieser
>
>
J. P. Gilliver (John)
Apr 8, 2017, 4:19:44 AM4/8/17
to
In message <58e5f428$0$793$e4fe...@news.xs4all.nl>, R.Wieser
activates several files when you only wanted one), yes? Could it be that
something somewhere remembers the shift key condition when you switch to
console mode, and restores it when you return? Though I can't think how
you'd switch to console mode with the shift key down. But a possibility
to ponder. Not that it solves the problem, but it might narrow down
where to look!
[]
(I've read on in the thread). We old hands perhaps remember politer
(and/or perhaps just more patient) times ...
[]
because it works from boot which USB often don't, but because it doesn't
use up a USB socket, instead using a socket which would otherwise not be
being used at all. Though I gather some motherboards - and certainly all
laptops for quite a few years - no longer necessarily _have_ PS/2
sockets.)
[]
restored by plugging it in again (USB ones _do_ re-detect); I don't
think I've tried it with a keyboard.
This is what food eats."
<add...@not.available> writes:
>Lee,
>
>> In order for an otherwise innocent double click to invoke several files
>> at once one normally has to have been in that folder before and single
>> clicked on an object which highlights it.
>
>There you mention something. Only now I realize that if the selection would
>be done from the first item I should have been seeing a lot of open
>folders -- which I don't. I have to check that next time it happens.
>
>But yes, the folder I'm double-clicking an item in was already open before I
>switched to-and-back-from the console window.
A thought: the behaviour is as if you had the shift key held down (so it
>Lee,
>
>> In order for an otherwise innocent double click to invoke several files
>> at once one normally has to have been in that folder before and single
>> clicked on an object which highlights it.
>
>There you mention something. Only now I realize that if the selection would
>be done from the first item I should have been seeing a lot of open
>folders -- which I don't. I have to check that next time it happens.
>
>But yes, the folder I'm double-clicking an item in was already open before I
>switched to-and-back-from the console window.
activates several files when you only wanted one), yes? Could it be that
something somewhere remembers the shift key condition when you switch to
console mode, and restores it when you return? Though I can't think how
you'd switch to console mode with the shift key down. But a possibility
to ponder. Not that it solves the problem, but it might narrow down
where to look!
[]
>> And I'm not really sure I am talking about the same thing you are. Yet.
>
>I get the feeling we now are. By the way, thank you for *not* biting my
>head of when I mentioned we weren't (I've got experiences otherwise ...
>:-\ ).
I know what you mean. Nice to find civilized discourse for a change
>
>I get the feeling we now are. By the way, thank you for *not* biting my
>head of when I mentioned we weren't (I've got experiences otherwise ...
>:-\ ).
(I've read on in the thread). We old hands perhaps remember politer
(and/or perhaps just more patient) times ...
[]
>> You use a PS2 keyboard I assume?
>
>Yep. One of the last ones in existence it seems. :-)
It does, sometimes, doesn't it! (I always prefer to use PS2 - not only
>
>Yep. One of the last ones in existence it seems. :-)
because it works from boot which USB often don't, but because it doesn't
use up a USB socket, instead using a socket which would otherwise not be
being used at all. Though I gather some motherboards - and certainly all
laptops for quite a few years - no longer necessarily _have_ PS/2
sockets.)
[]
>By the way: yesterday it happened again. This time I did not touch my
>keyboard, but physically dis- and reconnected it again. The sticky key was
>no more.
Interesting; IME, any lack of detection of a PS/2 _mouse_ isn't usually
>keyboard, but physically dis- and reconnected it again. The sticky key was
>no more.
restored by plugging it in again (USB ones _do_ re-detect); I don't
think I've tried it with a keyboard.
>
>In other words: it does not seem to be a physical problem (might still be in
>the keyboards electronics, but as the moment of appearing seems to be bound
>to what I do in the OS I doubt that).
[]
>In other words: it does not seem to be a physical problem (might still be in
>the keyboards electronics, but as the moment of appearing seems to be bound
>to what I do in the OS I doubt that).
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
As the man said when confronted by a large dinner salad, "This isn't food.
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
This is what food eats."
R.Wieser
Apr 8, 2017, 4:42:04 AM4/8/17
to
Lee,
> So the search tool was open and you were typing in the file name
> when it started misbehaving?
I'm sorry, I see I was not too clear there. I just typed the filename while
the focus was on the explorer window on the right (containing all the
files). It behaves as a kind of auto-complete (jumping to the first file
matching the first typed char, than on typing the second char to the file
matching that one, and so on).
> To sum up those ramblings, it appears to be a random firing off
> of CTRL-TAB. ALT after that goes straight to the tool bar then.
> Does that sound feasible to you?
I have no idea if its feasable. But I think its simpler: when you hold ALT
down your keystrokes are regarded as "shortcut keys" and are send to the
toolbar. If the ALT key "sticks" (on the keyboard itself, or being
remembered by the OS as being down) they will (ofcourse) go to the toolbar
too.
But while that works for the ALT key, the problem that I'm having seems to
be related to the SHIFT key (holding ALT down while selecting a file in
explorer does not seem to do anything special).
And that makes me realize that I seem to have (at least) *two* keys that act
funny: SHIFT and ALT ...
> I suggest you try to find a forum for your make and model of confuser
> and see if anyone in there also has your problem
But I did ! :-) I was/am assuming that its a Win98 OS related problem
(probably something in the line of the ALT-TAB not always working properly
when switching to/from a full-screen CLI), so I posted it here.
> Perhaps someone has such a thing along the lines of a keyboard
> initializer, set it to go off when the focus changes every single time
> might possibly work.
I did something like it: I found a windows build-in function which informs
you when another program receives focus. I build a small program with which,
when that happens, checks if the shift, control and/or alt keys are (still)
down. If so, it pops up a message telling me so. Now lets see if it
catches the problem situation (I already had it appear when pressing ALT-F4
:-) ) ...
Regards,
ae75e7b3-3445-4e48...@googlegroups.com...
> So the search tool was open and you were typing in the file name
> when it started misbehaving?
the focus was on the explorer window on the right (containing all the
files). It behaves as a kind of auto-complete (jumping to the first file
matching the first typed char, than on typing the second char to the file
matching that one, and so on).
> To sum up those ramblings, it appears to be a random firing off
> of CTRL-TAB. ALT after that goes straight to the tool bar then.
> Does that sound feasible to you?
down your keystrokes are regarded as "shortcut keys" and are send to the
toolbar. If the ALT key "sticks" (on the keyboard itself, or being
remembered by the OS as being down) they will (ofcourse) go to the toolbar
too.
But while that works for the ALT key, the problem that I'm having seems to
be related to the SHIFT key (holding ALT down while selecting a file in
explorer does not seem to do anything special).
And that makes me realize that I seem to have (at least) *two* keys that act
funny: SHIFT and ALT ...
> I suggest you try to find a forum for your make and model of confuser
> and see if anyone in there also has your problem
(probably something in the line of the ALT-TAB not always working properly
when switching to/from a full-screen CLI), so I posted it here.
> Perhaps someone has such a thing along the lines of a keyboard
> initializer, set it to go off when the focus changes every single time
> might possibly work.
you when another program receives focus. I build a small program with which,
when that happens, checks if the shift, control and/or alt keys are (still)
down. If so, it pops up a message telling me so. Now lets see if it
catches the problem situation (I already had it appear when pressing ALT-F4
:-) ) ...
Regards,
ae75e7b3-3445-4e48...@googlegroups.com...
J. P. Gilliver (John)
Apr 8, 2017, 5:09:58 AM4/8/17
to
In message <58e8a25b$0$707$e4fe...@news.xs4all.nl>, R.Wieser
Another possible something that might need considering: keyboard
mapping. I know, for example, that in the USA, there are two keys marked
Alt, which (AFAIK) do the same thing there; in the UK, the right one is
marked Alt Gr, although I've never been too sure what it's for (possibly
generating things like é, though it doesn't for me - I generated that
with an excellent utility called AllChars, though I don't know if that
works in '98 - I'm using XP here). Anyway, keyboard mapping may be
relevant - I've certainly seen cases where different mapping applies
between Windows and DOS, and _I think_ console mode too. (Though I can't
think of any layout where [either of ]the _shift_ key[s] have a
different function under anything.)
[via Penny Mayes (ma...@pmail.net)]
<add...@not.available> writes:
>Lee,
>
>> So the search tool was open and you were typing in the file name
>> when it started misbehaving?
>
>I'm sorry, I see I was not too clear there. I just typed the filename while
>the focus was on the explorer window on the right (containing all the
>files). It behaves as a kind of auto-complete (jumping to the first file
>matching the first typed char, than on typing the second char to the file
>matching that one, and so on).
>
>> To sum up those ramblings, it appears to be a random firing off
>> of CTRL-TAB. ALT after that goes straight to the tool bar then.
>> Does that sound feasible to you?
>
>I have no idea if its feasable. But I think its simpler: when you hold ALT
>down your keystrokes are regarded as "shortcut keys" and are send to the
>toolbar. If the ALT key "sticks" (on the keyboard itself, or being
>remembered by the OS as being down) they will (ofcourse) go to the toolbar
>too.
>
>But while that works for the ALT key, the problem that I'm having seems to
>be related to the SHIFT key (holding ALT down while selecting a file in
>explorer does not seem to do anything special).
>
>And that makes me realize that I seem to have (at least) *two* keys that act
>funny: SHIFT and ALT ...
[]
>Lee,
>
>> So the search tool was open and you were typing in the file name
>> when it started misbehaving?
>
>I'm sorry, I see I was not too clear there. I just typed the filename while
>the focus was on the explorer window on the right (containing all the
>files). It behaves as a kind of auto-complete (jumping to the first file
>matching the first typed char, than on typing the second char to the file
>matching that one, and so on).
>
>> To sum up those ramblings, it appears to be a random firing off
>> of CTRL-TAB. ALT after that goes straight to the tool bar then.
>> Does that sound feasible to you?
>
>I have no idea if its feasable. But I think its simpler: when you hold ALT
>down your keystrokes are regarded as "shortcut keys" and are send to the
>toolbar. If the ALT key "sticks" (on the keyboard itself, or being
>remembered by the OS as being down) they will (ofcourse) go to the toolbar
>too.
>
>But while that works for the ALT key, the problem that I'm having seems to
>be related to the SHIFT key (holding ALT down while selecting a file in
>explorer does not seem to do anything special).
>
>And that makes me realize that I seem to have (at least) *two* keys that act
>funny: SHIFT and ALT ...
Another possible something that might need considering: keyboard
mapping. I know, for example, that in the USA, there are two keys marked
Alt, which (AFAIK) do the same thing there; in the UK, the right one is
marked Alt Gr, although I've never been too sure what it's for (possibly
generating things like é, though it doesn't for me - I generated that
with an excellent utility called AllChars, though I don't know if that
works in '98 - I'm using XP here). Anyway, keyboard mapping may be
relevant - I've certainly seen cases where different mapping applies
between Windows and DOS, and _I think_ console mode too. (Though I can't
think of any layout where [either of ]the _shift_ key[s] have a
different function under anything.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
Madness takes its toll. Please have exact change
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
[via Penny Mayes (ma...@pmail.net)]
R.Wieser
Apr 8, 2017, 7:47:01 AM4/8/17
to
John,
> Could it be that something somewhere remembers the shift key
> condition when you switch to console mode, and restores it when
> you return?
That would be a heck of a bug, but everything is possible I guess.
Personally I get the feeling that the "key up" message sometimes just
doesn't pass the boundary between the switching from full-screen CLI to the
GUI, and the "key down" state simply stays active there, only to bother me
when I switch back to it.
> Though I can't think how you'd switch to console mode with the
> shift key down.
.. and I only realized this only much further down the road :-\ :-)
I've been wondering about that too. But I realized that many other keys
could be remembered in their pressed position, but just not have any averse
effect -- other than having to, if it happens, press the key twice to have
it appear. Hmmm ...
> Not that it solves the problem, but it might narrow down where
> to look!
If you have any idea, don't hesitate to mention it ! From my POV it could
be anywhere between the computers keyboard-communication chip (I'm using a
PS2 keyboard) and the very application that is absorbing the keystrokes.
> Interesting; IME, any lack of detection of a PS/2 _mouse_ isn't
> usually restored by plugging it in again
No, but I imagine that the keyboard could be sending, when power is aplied,
a "waking up" sequence, which a driver could be using to initialise/reset
its own state.
Regards,
Rudy Wieser
-- Origional message:
> Could it be that something somewhere remembers the shift key
> condition when you switch to console mode, and restores it when
> you return?
Personally I get the feeling that the "key up" message sometimes just
doesn't pass the boundary between the switching from full-screen CLI to the
GUI, and the "key down" state simply stays active there, only to bother me
when I switch back to it.
> Though I can't think how you'd switch to console mode with the
> shift key down.
I've been wondering about that too. But I realized that many other keys
could be remembered in their pressed position, but just not have any averse
effect -- other than having to, if it happens, press the key twice to have
it appear. Hmmm ...
> Not that it solves the problem, but it might narrow down where
> to look!
be anywhere between the computers keyboard-communication chip (I'm using a
PS2 keyboard) and the very application that is absorbing the keystrokes.
> Interesting; IME, any lack of detection of a PS/2 _mouse_ isn't
> usually restored by plugging it in again
a "waking up" sequence, which a driver could be using to initialise/reset
its own state.
Regards,
Rudy Wieser
-- Origional message:
J. P. Gilliver (John) <G6JP...@255soft.uk> schreef in berichtnieuws
Ol6DrtW$yJ6Y...@soft255.demon.co.uk...
Lee
Apr 8, 2017, 9:19:20 AM4/8/17
to
On Saturday, April 8, 2017 at 2:42:04 AM UTC-6, R.Wieser wrote:
> Lee,
>
> Lee,
>
> > So the search tool was open and you were typing in the file name
> > when it started misbehaving?
>
> I'm sorry, I see I was not too clear there. I just typed the filename while
> the focus was on the explorer window on the right (containing all the
> files). It behaves as a kind of auto-complete (jumping to the first file
> matching the first typed char, than on typing the second char to the file
> matching that one, and so on).
>
Ok, I got it now. Thanks. When ever I've tried that or repeated same key presses it moves maybe three times and then it breaks entirely and autocomplete quits working, if indeed we can use that 'taken' name for this function. Autocomplete for me is suggestions in a drop down box while you needed to see what was under the drop down box most of the time.
> > when it started misbehaving?
>
> I'm sorry, I see I was not too clear there. I just typed the filename while
> the focus was on the explorer window on the right (containing all the
> files). It behaves as a kind of auto-complete (jumping to the first file
> matching the first typed char, than on typing the second char to the file
> matching that one, and so on).
>
> > To sum up those ramblings, it appears to be a random firing off
> > of CTRL-TAB. ALT after that goes straight to the tool bar then.
> > Does that sound feasible to you?
>
> I have no idea if its feasable. But I think its simpler: when you hold ALT
> down your keystrokes are regarded as "shortcut keys" and are send to the
> toolbar. If the ALT key "sticks" (on the keyboard itself, or being
> remembered by the OS as being down) they will (ofcourse) go to the toolbar
> too.
>
> But while that works for the ALT key, the problem that I'm having seems to
> be related to the SHIFT key (holding ALT down while selecting a file in
> explorer does not seem to do anything special).
>
> And that makes me realize that I seem to have (at least) *two* keys that act
> funny: SHIFT and ALT ...
>
> > I suggest you try to find a forum for your make and model of confuser
> > and see if anyone in there also has your problem
>
> But I did ! :-) I was/am assuming that its a Win98 OS related problem
> (probably something in the line of the ALT-TAB not always working properly
> when switching to/from a full-screen CLI), so I posted it here.
>
> > Perhaps someone has such a thing along the lines of a keyboard
> > initializer, set it to go off when the focus changes every single time
> > might possibly work.
>
> I did something like it: I found a windows build-in function which informs
> you when another program receives focus. I build a small program with which,
> when that happens, checks if the shift, control and/or alt keys are (still)
> down. If so, it pops up a message telling me so. Now lets see if it
> catches the problem situation (I already had it appear when pressing ALT-F4
> :-) ) ...
>
> Regards,
> Rudy Wieser
>
R.Wieser
Apr 8, 2017, 10:56:46 AM4/8/17
to
Lee,
> Thanks. When ever I've tried that or repeated same key presses it
> moves maybe three times and then it breaks entirely and autocomplete
> quits working
I noticed that the autocomplete jumps to the first intry matching the
entered chars, regardless of if its a folder or a file. If its a folder
than you need to use the cursor-keys to move past it and eventually other
possibly matching folders to have it search the files. Also, any
cursor-key movement or a few moments of not typing anything will reset the
auto-complete.
> Noooo.... Not based on OS but your make and model.
I myself have the idea that the problem is OS related. When I would
specify a make and model of my 'puter (don't know how to be honest, as I put
the thing together myself -- and not even all parts where new when I did) I
would actually be limiting the audience, and thus possible replies ...
> More information on your 'I build a small program' please, sounds
> very interesting.
:-) It wasn't build using scripting I'm afraid.
Since ever so long I've been using Assembly (the programming language) to
put (small) stuff together. As, under Windows, Assembly directly talks to
DLLs there is little I can't ask of them, and in turn the system. The
downside of using Assembly is that I have to write *everything* myself.
The upside is ofcourse that I *can* write everything myself. :-)
6f94f765-be1c-4b01...@googlegroups.com...
> Thanks. When ever I've tried that or repeated same key presses it
> moves maybe three times and then it breaks entirely and autocomplete
> quits working
entered chars, regardless of if its a folder or a file. If its a folder
than you need to use the cursor-keys to move past it and eventually other
possibly matching folders to have it search the files. Also, any
cursor-key movement or a few moments of not typing anything will reset the
auto-complete.
> Noooo.... Not based on OS but your make and model.
specify a make and model of my 'puter (don't know how to be honest, as I put
the thing together myself -- and not even all parts where new when I did) I
would actually be limiting the audience, and thus possible replies ...
> More information on your 'I build a small program' please, sounds
> very interesting.
Since ever so long I've been using Assembly (the programming language) to
put (small) stuff together. As, under Windows, Assembly directly talks to
DLLs there is little I can't ask of them, and in turn the system. The
downside of using Assembly is that I have to write *everything* myself.
The upside is ofcourse that I *can* write everything myself. :-)
6f94f765-be1c-4b01...@googlegroups.com...
Lee
Apr 8, 2017, 10:33:15 PM4/8/17
to
On Saturday, April 8, 2017 at 8:56:46 AM UTC-6, R.Wieser wrote:
> Lee,
>
>
> Lee,
>
>
> I noticed that the autocomplete jumps to the first intry matching the
> entered chars, regardless of if its a folder or a file. If its a folder
> than you need to use the cursor-keys to move past it and eventually other
> possibly matching folders to have it search the files. Also, any
> cursor-key movement or a few moments of not typing anything will reset the
> auto-complete.
>
By cursor keys do you mean arrow keys? Otherwise I know not what you mean. I was not aware of the time element in this game, thanks for that tip. I do know that if you repeat the key it will move down say from folder to folder of the same starting letter until it hits the files and will do the same there too. But eventually it quits me anyway and I've not had the patience to stick with this approach for very long at all. Not knowing about the time element might the reason for that though and will have to keep that in mind next time I attempt it. If one has the accessibility options working the arrow key functions can exist in the numeric keypad as well. And by default there are alternatives to left side CTRL-A (select all), CTRL-Z (undo), CTRL-X (cut), CTRL-C (copy), and CTRL-V (paste), but I disremember what they are exactly since I'm not left handed. One of the accessibility options is turned on by six repeat hits of the CTRL key too, even it's turned off IIRC. One could lose their mind trying to keep up with all the possibles of this topic.
> entered chars, regardless of if its a folder or a file. If its a folder
> than you need to use the cursor-keys to move past it and eventually other
> possibly matching folders to have it search the files. Also, any
> cursor-key movement or a few moments of not typing anything will reset the
> auto-complete.
>
> > Noooo.... Not based on OS but your make and model.
>
> I myself have the idea that the problem is OS related. When I would
> specify a make and model of my 'puter (don't know how to be honest, as I put
> the thing together myself -- and not even all parts where new when I did) I
> would actually be limiting the audience, and thus possible replies ...
>
> > More information on your 'I build a small program' please, sounds
> > very interesting.
>
> :-) It wasn't build using scripting I'm afraid.
>
> Since ever so long I've been using Assembly (the programming language) to
> put (small) stuff together. As, under Windows, Assembly directly talks to
> DLLs there is little I can't ask of them, and in turn the system. The
> downside of using Assembly is that I have to write *everything* myself.
> The upside is ofcourse that I *can* write everything myself. :-)
>
> Regards,
> Rudy Wieser
>
R.Wieser
Apr 9, 2017, 3:34:36 AM4/9/17
to
Lee,
> By cursor keys do you mean arrow keys?
Yep. Should have used that name. :-\
> I do know that if you repeat the key it will move down say from folder
> to folder of the same starting letter until it hits the files and will do
the
> same there too.
You know that I had to check that ? I either never knew or, more likely
forgot all about it. It seems to work only for the very first char though.
> Failing to buy a store bought computer assembled for you isn't a valid
> reason, you can offer up the motherboard model number instead.
It certainly isn't a valid reason not to give a motherboards model number,
but as I mentioned, I don't think its bound to the hardware, so specifying
it would 1) limit my audience and 2) make people think so and make them look
in the wrong direction(s).
... I've just tried to see if "systeminfo" would tell me what model and
make my motherboard is, but it doesn't seem to do so. It'll have to wait
until next time I'm taking the thing apart I guess (and maybe put it into a
textfile somewhere. :-) )
> I dabble in assembler myself, and not in the slightest concerned that
> you didn't go script kiddy on me either.
I thought that Assembly programmers where a dying breed, rather seldom to
find in the wild. :-)
But I seldom mention forthright which language I'm using, as I've seen
people stop responding to questions (mostly regarding the use of DLL
functions) when I did so.
> Still interested in more information but it's off topic
As far as I can tell this particular newsgroup allows for a *lot* of leeway.
As long as its not overtaking the groups origional purpose ofcourse ...
The relevant call is "SetWinEventHook" (in user32.dll) which I instruct to
listen to EVENT_SYSTEM_FOREGROUND only. When that one fires I use
"GetAsyncKeyState" to check the VK_ALT, VK_CTRL and VK_SHIFT keys and see if
any is pressed*. If so, I pop up a modal message-box. Currently thats
about all. I noticed that I could probably include a check if the
new-focussed window is a popup, and than ignore it.
*Though I'm currently not even sure if "GetAsyncKeyState" is the right call
to check for the sticky key ...
1cc491a9-824e-4d9d...@googlegroups.com...
> By cursor keys do you mean arrow keys?
> I do know that if you repeat the key it will move down say from folder
> to folder of the same starting letter until it hits the files and will do
the
> same there too.
forgot all about it. It seems to work only for the very first char though.
> Failing to buy a store bought computer assembled for you isn't a valid
> reason, you can offer up the motherboard model number instead.
but as I mentioned, I don't think its bound to the hardware, so specifying
it would 1) limit my audience and 2) make people think so and make them look
in the wrong direction(s).
... I've just tried to see if "systeminfo" would tell me what model and
make my motherboard is, but it doesn't seem to do so. It'll have to wait
until next time I'm taking the thing apart I guess (and maybe put it into a
textfile somewhere. :-) )
> I dabble in assembler myself, and not in the slightest concerned that
> you didn't go script kiddy on me either.
find in the wild. :-)
But I seldom mention forthright which language I'm using, as I've seen
people stop responding to questions (mostly regarding the use of DLL
functions) when I did so.
> Still interested in more information but it's off topic
As long as its not overtaking the groups origional purpose ofcourse ...
The relevant call is "SetWinEventHook" (in user32.dll) which I instruct to
listen to EVENT_SYSTEM_FOREGROUND only. When that one fires I use
"GetAsyncKeyState" to check the VK_ALT, VK_CTRL and VK_SHIFT keys and see if
any is pressed*. If so, I pop up a modal message-box. Currently thats
about all. I noticed that I could probably include a check if the
new-focussed window is a popup, and than ignore it.
*Though I'm currently not even sure if "GetAsyncKeyState" is the right call
to check for the sticky key ...
1cc491a9-824e-4d9d...@googlegroups.com...
Lee
Apr 9, 2017, 7:21:52 AM4/9/17
to
On Sunday, April 9, 2017 at 1:34:36 AM UTC-6, R.Wieser wrote:
> Lee,
>
> > I do know that if you repeat the key ...
> Lee,
>
>
> You know that I had to check that ? I either never knew or, more likely
> forgot all about it. It seems to work only for the very first char though.
>
Well that works both ways, you've been teaching me right along too. Yes, only working well on the first character.
> You know that I had to check that ? I either never knew or, more likely
> forgot all about it. It seems to work only for the very first char though.
>
>
> ... I've just tried to see if "systeminfo" would tell me what model and
> make my motherboard is, but it doesn't seem to do so. It'll have to wait
> until next time I'm taking the thing apart I guess (and maybe put it into a
> textfile somewhere. :-) )
> But I seldom mention forthright which language I'm using, as I've seen
> people stop responding to questions (mostly regarding the use of DLL
> functions) when I did so.
>
> > Still interested in more information but it's off topic
>
> As far as I can tell this particular newsgroup allows for a *lot* of leeway.
> As long as its not overtaking the groups origional purpose ofcourse ...
>
> The relevant call is "SetWinEventHook" (in user32.dll) which I instruct to
> listen to EVENT_SYSTEM_FOREGROUND only. When that one fires I use
> "GetAsyncKeyState" to check the VK_ALT, VK_CTRL and VK_SHIFT keys and see if
> any is pressed*. If so, I pop up a modal message-box. Currently thats
> about all. I noticed that I could probably include a check if the
> new-focussed window is a popup, and than ignore it.
>
> *Though I'm currently not even sure if "GetAsyncKeyState" is the right call
> to check for the sticky key ...
>
> Regards,
> Rudy Wieser
>
I am almost a master with the lowly 6502 on the mighty Atari 8 bit and very much a noob with x86 but have been able to monkey around with the source to aefdisk which went open source on GitHub just last year - the author is done with working on it so posted source of a derivative of the last free (with two defeated functions) and commercial version he was offering for decades. It was somewhat defective source and with help at msfn got the fix put in. MetaPad source is also out there somewhere, it needs a slap or two upside the head as well.
J. P. Gilliver (John)
Apr 9, 2017, 9:42:14 AM4/9/17
to
In message <1cc491a9-824e-4d9d...@googlegroups.com>, Lee
<mel...@my-deja.com> writes:
[]
IIRR, they (or at least some of them) involve some of the keys in the
"six-pack". I _am_ left-handed, but find the Ctrl+ options very
convenient: maybe because I once learnt to play piano I don't find use
of the little finger difficult.
(I also find Alt-space then C easier than Alt-F4, and Alt-space then x -
with Alt-space then enter to restore - easier than mouse, especially if
my hands are on the keyboard anyway.)
<mel...@my-deja.com> writes:
[]
>exist in the numeric keypad as well. And by default there are
>alternatives to left side CTRL-A (select all), CTRL-Z (undo), CTRL-X
>(cut), CTRL-C (copy), and CTRL-V (paste), but I disremember what they
>are exactly since I'm not left handed. One of the accessibility options
[]
>alternatives to left side CTRL-A (select all), CTRL-Z (undo), CTRL-X
>(cut), CTRL-C (copy), and CTRL-V (paste), but I disremember what they
>are exactly since I'm not left handed. One of the accessibility options
IIRR, they (or at least some of them) involve some of the keys in the
"six-pack". I _am_ left-handed, but find the Ctrl+ options very
convenient: maybe because I once learnt to play piano I don't find use
of the little finger difficult.
(I also find Alt-space then C easier than Alt-F4, and Alt-space then x -
with Alt-space then enter to restore - easier than mouse, especially if
my hands are on the keyboard anyway.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
User Error: Replace user, hit any key to continue.
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
J. P. Gilliver (John)
Apr 9, 2017, 9:42:15 AM4/9/17
to
In message <dc398d2d-94e9-45f7...@googlegroups.com>, Lee
[]
Belarc often has a reasonable stab at identifying the mobo. I _think_
that works under '9x, or at least I think older versions did.
[]
>> ... I've just tried to see if "systeminfo" would tell me what model and
>> make my motherboard is, but it doesn't seem to do so. It'll have to wait
>> until next time I'm taking the thing apart I guess (and maybe put it into a
>> textfile somewhere. :-) )
>
>Somehow I knew this would be the outcome. hee, hee. If it weren't for
>the fact that my 1997 $125 JDR ChainTec special came with a motherboard
>manual with the number on the front cover I wouldn't know it either.
[]
>> make my motherboard is, but it doesn't seem to do so. It'll have to wait
>> until next time I'm taking the thing apart I guess (and maybe put it into a
>> textfile somewhere. :-) )
>
>Somehow I knew this would be the outcome. hee, hee. If it weren't for
>the fact that my 1997 $125 JDR ChainTec special came with a motherboard
>manual with the number on the front cover I wouldn't know it either.
Belarc often has a reasonable stab at identifying the mobo. I _think_
that works under '9x, or at least I think older versions did.
0 new messages