|
|
No! That dialog! It's going to go "ScreeeeeePtwangWizWahahahaBleeepBleepBleepScreachWhiteNoise" at me!
And then drop the connection 40 minutes into the download ...
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I still use hyperterminal to configure - not so old - routers and switches.
"Five fruits and vegetables a day? What a joke!
Personally, after the third watermelon, I'm full."
|
|
|
|
|
Some robots in the industry still use a derivate of hyperterminal (connect, transfer program, backups, some management functions and the possibility to execute things per command line)
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Used it a while back, to get output from Temp Sensor controllers to write a syslog server. Dusted off an XP VM.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
I never liked Hyperterminal. Grotty little piece of crapware.
I've been using Putty now that I find that my preferred terminus emulator won't run on Win 10.
|
|
|
|
|
Ah, fond memories of reading the caller id data from a pbx serial port! I actually made a nice little phone log application out of it, tracking the call activity of a dozen or so collectors. I gave it away and let the owner eventually make some money from it. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
Did you ever notice that chestnut is a type of horse, and horse is a type of chestnut.
|
|
|
|
|
That's just nuts!
Technician
1. A person that fixes stuff you can't.
2. One who does precision guesswork based on unreliable data provided by those of questionable knowledge.
JaxCoder.com
|
|
|
|
|
Quit horsin' around, Mike! 
/ravi
|
|
|
|
|
Was that an eQuestrian Ravi?
Technician
1. A person that fixes stuff you can't.
2. One who does precision guesswork based on unreliable data provided by those of questionable knowledge.
JaxCoder.com
|
|
|
|
|
OK, I'll pony up - yes, it was. 
/ravi
|
|
|
|
|
Who let you two guys appaloosa in the lounge! 
I, for one, like Roman Numerals.
|
|
|
|
|
Those two are utterly draft, Percheron their sense of humor.
Software Zen: delete this;
|
|
|
|
|
I agree. Time they were reined in.
/ravi
|
|
|
|
|
They've been driving me buggy (and my name ain't Miss Daisy, neither).
Software Zen: delete this;
|
|
|
|
|
Clearly, they lack horse sense.
/ravi
|
|
|
|
|
That's a horse of a different color.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
hmm hmm hmmm roasting on an open fire 
|
|
|
|
|
|
When I try to tilt the angle of view on my notebook, it throws fit and lands on a BSOD, consistently.
I was unsure how this was happening. Just to observe the behaviour, I left my notebook intact on my desk without moving a bit for 2 weeks. There was no problem.
When I lifted the notebook, the slight movement on the lid, threw the notebook to crash, immediately.
I thought maybe the pressure at the bottom of the notebook(when I left) is crushing the circuitry or an HDD controller cable, something like that. But it's not.
It's confirmed with the final experiment: On the desk, without lifting the notebook, just pushed the lid back a bit. It lands right into this screen.
And far worse - If I pushed it further, the whole screen became a dump of noisy horizontal lines flickering like an ECG gone wild.
It's a PITA to think about giving the machine to the service centre..taking backups etc.
Any clue?
|
|
|
|
|
something is loose ..maybe the memory...
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Well notebooks must have a sensor that detects lid position, as most include a feature that activates sleep mode when lid is closed. So maybe that sensor is causing problems.
Perhaps on that note, you can try disabling any "sleep mode" features and see if it still happens? I get that you are not fully closing the lid, but still that sensor could be triggering some kind of check which is problematic.
|
|
|
|
|
 will try this out. thank you
|
|
|
|
|
It's just a guess, I honestly don't know enough about hardware, especially notebooks.
The problem is that activating "sleep mode" is going to be secondary to any IO feedback from the sensor anyway, so it might have already blue screened by the time it gets to that part anyway.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
